Comment 2 for bug 245594
Revision history for this message
| Emmet Hikory (persia) wrote Re: Please add binNMU capabilities to Soyuz | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Let us instead agree that binary uploads external to Soyuz are forbidden in Ubuntu by policy. While the term used might have been "binNMU", what is sought is a means by which a rebuild may be triggered without source changes. Could there not be a means similar to the existing facilty to rebuild a package that failed to build to rebuild a package when the current binary packages are deemed unsuitable, although the source package is acceptable?
When this is done in Debian, the notation +bN is used as an additional version number for the binary package (with the same version for the source package), where N indicates the number of successful rebuilds the package has undergone. Perhaps a similar mechanism might be used to reversion binary packages internal to Soyuz when such a rebuild was requested.
The permissions model for requesting such rebuilds should probably match that used for requesting rebuilds of packages that failed to build from source.