Package autosync does not remember manual syncs from different distroseries

Bug #162660 reported by Loïc Minier
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Hi,

I'd love if Soyuz would continue autosyncing Debian packages from experimental when a version was autosynced once. Either forever as an override (which needs to be removable), or until a higher version reaches unstable (we would then need to resync from experimental to track experimental again).

Thanks!

Tags: lp-soyuz
Changed in soyuz:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Robert Collins (lifeless) wrote :

Possibly part of derivative distros

Changed in launchpad:
importance: Wishlist → Low
summary: - Allow autosync to follow experimental
+ Package autosync does not remember manual syncs from different
+ distroseries
Revision history for this message
Colin Watson (cjwatson) wrote :

We could in principle do this client-side for Ubuntu now that we're doing auto-syncs over the API. I wonder if we really want this in all cases, though; I can easily imagine cases where you sync from experimental once but the next version along is far too scary.

I could imagine instituting a process whereby developers can ask archive admins to change the default auto-sync source for a package. Of course, if we did that, we'd then have to have somewhere to store that information, which ideally would be Launchpad; so maybe this does come back to the derivative distributions feature after all.

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.