there are no safeguards against epoch changes in uploads to primary archives (Ubuntu itself, linaro etc)
Bug #793299 reported by
Scott Kitterman
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
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:/
| 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 |
| tags: | added: soyuz-upload |
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #1 |
To post a comment you must log in.
This should be worked into the new policy framework (see lp/soyuz/