newly-initialised distroseries not considered dirty on first publisher run

Bug #991874 reported by Colin Watson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Unassigned

Bug Description

Last year, some work was done on simplifying the process of creating new distroseries. I believe this was mainly for derived distributions, but it also had the effect of making Ubuntu's new-release-cycle process simpler. One of the changes to our process was the removal of the requirement to do careful-apt publisher runs after initialising the new distroseries in order to create initial Packages and Sources files:

  https://wiki.ubuntu.com/NewReleaseCycleProcess?action=diff&rev1=83&rev2=84

However, when I initialised quantal, I found that the publisher did not automatically create indexes under dists/ for it, and I had to run publish-distro.py -A manually, just like in the old days.

Looking through #launchpad-ops logs for 2011-10-13, it turns out that this didn't work when we initialised precise either. Maybe we can make this work properly for R!

Colin Watson (cjwatson)
tags: added: new-release-cycle-process
summary: - newly-initialised distroseries was not considered dirty on first
- publisher run
+ newly-initialised distroseries not considered dirty on first publisher
+ run
Revision history for this message
Colin Watson (cjwatson) wrote :

In case it helps, here's the log output from the publisher run that I believe should have created quantal indices but didn't.

Changed in launchpad:
status: New → Triaged
importance: Undecided → Critical
Revision history for this message
Julian Edwards (julian-edwards) wrote :

I subscribed jtv since he did the work for this originally. I'm pretty sure I saw it working on DF at some point too, so it could just be a production config issue?

Changed in launchpad:
importance: Critical → High
tags: added: derivation
William Grant (wgrant)
tags: added: phone-rtm
Revision history for this message
Colin Watson (cjwatson) wrote :

This definitely worked when we initialised utopic, and looking back through some IRC logs it appears to have worked for at least trusty and possibly saucy too. So, whatever happened, I think this is fixed now. We'll reopen if it happens again.

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

Other bug subscribers

Remote bug watches

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