speed up deployment of changelogs

Bug #401043 reported by Rolf Leggewie
34
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Undecided
Unassigned
Ubuntu
Fix Released
Undecided
Michael Vogt

Bug Description

It happens quite often to me that aptitude has a package for updating the system, but "C" on the package will fail to display the changelog. The reason is that publishing the package seems to be much quicker than publishing the changelog. I wonder if the latter can't be expedited.

Changed in launchpad-foundations:
status: New → Invalid
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Francis, is it *SOO* difficult to provide at least a short comment?

This issue is very valid, so if LP foundations isn't the proper place, my apologies, but at least say so. For Christ sakes, this attitude of "close and forget" is bothering me to no end.

Revision history for this message
Jacob Peddicord (jpeddicord) wrote :

Marking this against Soyuz since I would assume it handles this. If this is wrong I apologize in advance. :)

Changed in ubuntu:
status: New → Invalid
Revision history for this message
Julian Edwards (julian-edwards) wrote :

This is not a Soyuz bug :)

I chatted to mvo about this and what happens is that there's a cron job that scrapes the archive every 4 hours and populates changelogs.ubuntu.com.

This can be made considerably more efficient if it uses the Launchpad API instead, using a combination of:
    Archive.getPublishedSources(created_since_date=xxxx)
which returns a collection of SourcePackagePublishingHistory items, each of which has a changes_file_url property that is the unmodified changes file for the upload.

Michael advised to leave the bug filed on Ubuntu for now, assigned to him. Bug Squad members, please leave it for him.

Changed in soyuz:
status: New → Invalid
Changed in ubuntu:
assignee: nobody → Michael Vogt (mvo)
status: Invalid → Confirmed
Revision history for this message
Julian Edwards (julian-edwards) wrote :

BTW, for future reference, it's best to change the bugtask target if you can rather than marking it invalid and adding a new one. There's a bug in Launchpad which means that invalid bug tasks still get email every time the bug is updated.

Revision history for this message
Michael Vogt (mvo) wrote :

I put the beginning of a fix for this into lp:~mvo/+junk/lp-archive-crawler and we should discuss this at UDS. Either we use code like this or we just use launchpad directly without pre-caching the data.

Revision history for this message
Mohamed Amine Ilidrissi (ilidrissi.amine) wrote :

Just a quick note to say that this is still an issue.

Revision history for this message
Michael Vogt (mvo) wrote :

This is fixed now, the changelogs.ubuntu.com server runs a launchpadlib script now every 15 minutes. Because it looks at source packages it will usually update the changelog way before the binary is availalbe on the archive server.

Changed in ubuntu:
status: Confirmed → Fix Released
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Great! Thank you very much, Michael.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

The problem seems to have reappeared recently.

Changed in ubuntu:
status: Fix Released → New
Revision history for this message
Michael Vogt (mvo) wrote :

Hello Rolf, sorry for the long delay. When you say it reappeared recently, do you have some specific packages that I can look for?

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Rolf Leggewie (r0lf) wrote :

fortunately, the examples are now much rarer than previously. Good work. I just stumbled across another one, so I'll let you know here. enigmail has seen another release to lucid. But http://changelogs.ubuntu.com/changelogs/pool/universe/e/enigmail/enigmail_1.4.1-0ubuntu0.10.04.1/changelog isn't there, yet.

Changed in ubuntu:
status: Incomplete → Confirmed
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Haven't run into this recently. Setting to fix released.

Changed in ubuntu:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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