maemo.org Bugzilla – Bug 8694
Package information in package interface changes between new and old info
Last modified: 2010-03-12 11:42:52 UTC
You need to log in before you can comment on or make changes to this bug.
SOFTWARE VERSION: EXACT STEPS LEADING TO PROBLEM: 1. Open http://maemo.org/packages/package_instance/view/fremantle_extras-testing_free_armel/cell-modem-ui/0.4-2/ 2. Observe package icon, description, bugtracker EXPECTED OUTCOME: Verify information is coming from 0.4-2 (ie. bug tracker points to bugs.maemo.org; icon shows two devices; package description talk about Tablet mode/Phone mode) ACTUAL OUTCOME: Randomly information is coming from 0.3-0 version (bug tracker points to garage; icon is red telephone; package description says Enabling/disabling phone) REPRODUCIBILITY: random OTHER COMMENTS: Is this some Akamai caching issue, or package interface just randomly picking if the info should come from 0.3-0 or 0.4-2. Anyways, its annoying as hell and affects QA testing. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729)
Confirmed by Venomrush and Emmanuele Cassioli in said URL, so its not just my bad eyes :) I don't know their emails, so no CC.
This is negatively impacting my packages' Extras-testing experience. I have been given the thumbs-down on a package for having an incorrect bugtracker URL... But my bugtracker URL has been correct for several versions already, and it worked fine for me. Then I discovered that if you keep refreshing the page, it will alternate, apparently randomly, between new and old package information! So there's something seriously wrong here! See the comments on my package instance page for more information: http://maemo.org/packages/package_instance/view/fremantle_extras-testing_free_armel/easy-deb-chroot/0.9.46-1fremantle1/
This seems to be related to content cache on the server side. You probably saw different results because one time you were logged in and one time you weren't. Content cache is done per user and then there is the anonymous cache too. My guess is that the anonymous cache doesn't get expired properly. Will need to investigate this some more.
I found some issues in the importers which would cause most recent version from extras-devel and extras, for example, to update on each run. As these importers run 10 minutes or more apart, you could see the information change between these intervals. Now made the importers a bit smarter, so this should not happen anymore. Please reopen if you still see this issue.