Posted by brianshumate on April 9, 2008 at 10:37pm
Jump to:
| Project: | Drupal.org infrastructure |
| Component: | Packaging |
| Category: | bug report |
| Priority: | normal |
| Assigned: | dww |
| Status: | closed (fixed) |
Issue Summary
Just a quick oddness here.
1. Noticed a release announcement for 6.2 on www.drupal.org
2. Manually checked available update status in my 6.1 installation
3. Expected to see notice about core being out of date (e.g. 6.2 available as an update)
3. The update module instead shows Drupal core to be up to date at 6.1 despite availability of 6.2
(see the attached screenshot taken at approximately 2008-04-09 18:25 EDT for example)
Apologies in advance if this is the result of some other issue and, not an issue with the module itself. My thoughts are that if an update is announced on the website, it should already have been appearing in the updates list prior to the announcement of availability.
Thanks for the goodness! :-)
| Attachment | Size |
|---|---|
| update-module.png | 37.9 KB |
Comments
#1
*sigh*. This is another example of #184418: update(_status) results stale for up to 6 hours. This is supposed to be handled manually for core security updates, and is documented as such, but it seems when 6.2 went out earlier today, this step was either forgotten or done out of order. I just regenerated the .xml files that update.module uses, and now everything is working as expected.
#2
Thanks for the info and fix!
#3
Automatically closed -- issue fixed for two weeks with no activity.