there are no safeguards against epoch changes in uploads to primary archives (Ubuntu itself, linaro etc)

Reported by Scott Kitterman on 2011-06-05
24
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned

Bug Description

Adding or increasing an epoch in Ubuntu is virtually always a wrong thing to do. It would be good if Ubuntu origin uploads that add/increase an epoch were diverted to New where an archive admin could review them and determine if this is one of the rare cases when it would appropriate of not before it's accepted. See:

https://lists.ubuntu.com/archives/ubuntu-devel/2011-June/033389.html

Luke Faraone (lfaraone) on 2011-06-05
Changed in launchpad:
status: New → Confirmed
summary: - Have Soyuz send uploads adding or increasing an epoch to new
+ there are no safeguards against epoch changes in uploads to primary
+ archives (Ubuntu itself, linaro etc)
Changed in launchpad:
status: Confirmed → Triaged
importance: Undecided → Low
William Grant (wgrant) on 2011-06-06
tags: added: soyuz-upload
Julian Edwards (julian-edwards) wrote :

This should be worked into the new policy framework (see lp/soyuz/adapters/copypolicy.py) being used for the derivations work. It was the intention from the start that the upload processor should then use these policy objects instead of the hard-coded nonsense it has right now.

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

Other bug subscribers