Drupal Core still shows 5.1 in update status

I moved my modules and themes to sites/all and admin/logs/updates doesn't show anything.

I moved my modules and themes to sites/all and admin/logs/updates doesn't show anything.

Same problem here.

How did everyone install 5.2? Did you re-install from a new core tarball, did you just apply the security patches, or are you using a direct checkout from CVS?

Downloaded from http://drupal.org/drupal-5.2 and did the update following the instructions from UPGRADE.txt

same problem here

Just to confirm, everyone in this issue is really using 5.x-2.0-rc?

I just tried the following steps:

1. Downloaded both the 5.1 and 5.2 core tarballs from ftp.d.o
2. Installed a completely clean 5.1 core site using the default profile
3. Downloaded the 5.x-2.0-rc update_status tarball
4. Enabled update_status, and visited the available updates page. Correctly told me:
   • Core is currently installed as 5.1
   • Site is missing a security update
   • 5.2 core is available

   (See screenshot attached here)

5. Untar'ed the drupal-5.2.tar.gz into my core folder
6. Reloaded the available updates page, which correctly told me:
   • Core is currently installed as 5.2
   • Site is up to date

   (See screenshot attached to next followup).

Therefore, I have no idea what the bug is, since I can't reproduce it at all in the most basic test case. All I can think of is that somehow the .info files for some of your core modules aren't actually being updated when you "upgrade" your sites to 5.2.

Given that I can't reproduce, I'm moving this to a support request. Don't know what else to do, unless someone can provide similarly detailed instructions on how to reproduce the problem, or provide me with access to an affected site so I can try to debug there or something. :(

p.s. core's status report at admin/logs/status is also correct in both cases, though I'm not going to attach screenshots of those.

for posterity, here's the screenshot of the admin/logs/updates after the upgrade to 5.2 core. looks as expected...

Ok. I've found my problem... I have two self created modules. In their info-file the project was set to "drupal". So update_status included these 2 modules in his check for Drupal core updates.

I've changed the project in these info-files to something else and everything is fine now...

Well, that definitely explains it. ;) This code is written to assume accurate information in the .info files. If some of the .info files are lying, there's really not much update_status can do about it...

great, I'm going to call this fixed, then. yes, there are evil, buggy modules in contrib that put stupid things in their .info files, but there's really not much update_status.module can do about that...