Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I just updated profile_pictures to 6.x-1.2 using CVS and the "profile_pictures.info" file still says the version is 6.x-1.0. So drupal continues to say it needs to be updated, even though CHANGELOG.txt says this is the correct version.
If you download the tar ball, then the .info file has this in it:
; Information added by drupal.org packaging script on 2010-04-09
version = "6.x-1.0"
core = "6.x"
project = "profile_pictures"
datestamp = "1270845607"
; Information added by drupal.org packaging script on 2010-07-06
version = "6.x-1.2"
core = "6.x"
project = "profile_pictures"
datestamp = "1278416108"
But if you get the module through CVS, then the file only has the top section:
; Information added by drupal.org packaging script on 2010-04-09
version = "6.x-1.0"
core = "6.x"
project = "profile_pictures"
datestamp = "1270845607"
So drupal keep thinking it still needs to be upgraded.
Comments
Comment #1
bamakojeff CreditAttribution: bamakojeff commentedSorry, I didn't explain that well at all. Need more caffeine before I write. :-)
Would you please remove the "Information added by drupal.org packaging script on 2010-04-09" section from the .info file? Then when it comes in through CVS it won't have that information and the CVS Deploy module should correctly supply it.
Sorry again for the unhelpful first post!
Comment #2
yeputons CreditAttribution: yeputons commentedFixed #884200: CVS .info file incorrect by yeputons (repoted by bamakojeff): removed drupal.org packaging script information from profile_pictures.info