We need a way to remove superseded librarian binaries from obsolete distroseries

Bug #651092 reported by Julian Edwards on 2010-09-29
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned

Bug Description

This is currently done with some SQL, but we'd much rather do it in code.

tags: added: soyuz-core
description: updated
Jonathan Lange (jml) wrote :

Specifically, if it's something we do as a matter of course, then there should be exactly zero human intervention required to do this.

On Wednesday 29 September 2010 14:40:55 you wrote:
> Specifically, if it's something we do as a matter of course, then there
> should be exactly zero human intervention required to do this.

It's a matter of course after checking with the platform team. I'd be happy
to put a button on the series page and let them do it if the LOSAs ask for
space reclamation.

Robert Collins (lifeless) wrote :

How about a reminder screen showing
 - space saved
 - series status

or some such?

-Rob

Stuart Bishop (stub) wrote :

If we are doing this more pro actively, there should be no need tp set
the expiry date into the past. The stay of execution gives us a chance
to reverse any blunders without resorting to the backups.

--
Stuart Bishop <email address hidden>
http://www.stuartbishop.net/

Julian Edwards (julian-edwards) wrote :

On Wednesday 29 September 2010 16:55:04 Stuart Bishop wrote:
> If we are doing this more pro actively, there should be no need tp set
> the expiry date into the past. The stay of execution gives us a chance
> to reverse any blunders without resorting to the backups.

Hell YES. :-)

Julian Edwards (julian-edwards) wrote :

On Wednesday 29 September 2010 16:53:21 Robert Collins wrote:
> How about a reminder screen showing
> - space saved
> - series status
>
> or some such?

Including an indication of "wasted" space would be great.

Jonathan Lange (jml) wrote :

If the platform team approve, perhaps we don't even need to have a button for them to push. We could do something like setting the expiry date in the future once a package enters the appropriate state.

Julian Edwards (julian-edwards) wrote :

If we could add built-in obsolescence that'd be great. If we get a messaging
system sorted too, it could kick off a number of different jobs to do with
that ;)

Jonathan Lange (jml) wrote :

Judging from the query, it's not something that needs a messaging system. Just setting 'expires' on the librarian records when the status, archive, distroseries etc are all aligned properly. Hardly blue-sky.

On Wednesday 29 September 2010 17:37:38 you wrote:
> Judging from the query, it's not something that needs a messaging
> system. Just setting 'expires' on the librarian records when the status,
> archive, distroseries etc are all aligned properly. Hardly blue-sky.

We need an event generated at the point the series becomes obsolete that runs
some soyuz jobs that sets the publishing records to "obsolete", and then
expires the librarian files. I don't really care too much how the event is
propagated but it's yet more weight for a messaging system.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers