Launchpad itself

product release finder set all release dates to the date the file was found

Bug #67909 reported by Stuart Bishop
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

The product release finder set all the release dates to CURRENT_TIMESTAMP. We should write a single use script to examine the archives we downloaded, extracting the most recent timestamp from the stored files and updating the release date of the ProductRelease.

Stuart Bishop (stub)
Changed in launchpad:
importance: Undecided → Wishlist
Revision history for this message
James Henstridge (jamesh) wrote :

The ProductRelease table has a "datecreated" column. The plan discussed in bug 4557 was to add a second "releasedate" column that could be NULL and is user editable.

So this bug would be about filling in the dates based on the downloaded tarballs.

Stuart Bishop (stub)
affects: launchpad-foundations → launchpad-registry
Revision history for this message
Curtis Hovey (sinzui) wrote :

This was fixed in March 2009.

Changed in launchpad-registry:
assignee: nobody → Edwin Grubbs (edwin-grubbs)
status: New → Fix Committed
Revision history for this message
Michael Kuhn (suraia) wrote :

Are you sure? The product release finder still sets "datereleased = datetime.now(pytz.UTC)".
All my recent releases were imported with the current timestamp instead of the release timestamp (extracted from the tarball, Last-Modified header, or whatever).

Edwin Grubbs (edwin-grubbs)
Changed in launchpad-registry:
status: Fix Committed → Triaged
Revision history for this message
Edwin Grubbs (edwin-grubbs) wrote :

I'm not sure why I had re-opened this. This was fixed in March 2009.

Changed in launchpad-registry:
status: Triaged → Fix Committed
Edwin Grubbs (edwin-grubbs)
Changed in launchpad-registry:
status: Fix Committed → Fix Released
Revision history for this message
Christian Reis (kiko) wrote :

Sorry for preemptively reopening this, but I believe that https://edge.launchpad.net/linux/+series shows that this bug isn't quite fixed -- or at least the symptom has reappeared for some unrelated reason. If you look at the releases that PRF created across all those series, they all have the date of the PRF run that created them, and not the dates of the release tarballs it found. Ironically the dates of the actual tarballs are correct, since if you look at https://edge.launchpad.net/linux/ you'll see that the date of 2.6.31.tar.gz is correctly set to 2009-10-10.

Changed in launchpad-registry:
status: Fix Released → Triaged
importance: Low → High
Curtis Hovey (sinzui)
tags: added: prf
removed: feature
Edwin Grubbs (edwin-grubbs)
Changed in launchpad-registry:
assignee: Edwin Grubbs (edwin-grubbs) → nobody
importance: High → Low
Curtis Hovey (sinzui)
summary: - product release finder set all release dates to 23/10/2006
+ product release finder set all release dates to the date the file was
+ found
Curtis Hovey (sinzui)
tags: added: product-release-finder
removed: prf
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.