Am Do., 20. Feb. 2025 um 13:28 Uhr schrieb Richard W.M. Jones <rjones@xxxxxxxxxx>: > > On Thu, Feb 20, 2025 at 01:17:02PM +0100, Miro Hrončok wrote: > > Hello. > > > > With the recent discussions about provenpackagers in Fedora, I > > recently got an idea. > > > > One of the common needs for provenpackagers is to simply "bump and > > rebuild" a set of dependencies. > > > > All packagers are already able to build anything (except a very > > specific and small set of specially-signed packages). However, to > > bump the package, they need commit rights. For that reason, > > provenpackager rights are often required. > > > > With the wide adoption of %autorelease, such bump commits are empty, > > which should be easy to verify. Wide, well, ... > > What if we allowed all packagers to push empty commit to any > > package? That should eliminate *some* need for provenpackager > > access. We would also communicate in our policies that such bumps do > > not require prior agreement with the maintainers to avoid confusion > > about "what are we allowed to do". > > Seems like a sensible proposal. Some possible modifications: Good so far. > - Limit this only to rawhide? > > - If we don't restrict it only to Rawhide, should we encourage the > packager to preserve ffwd to the rawhide branch, if that is > currently the case? [Whatever the technical term for that is.] > That is an issue due to how we use git to drive builds without a common guideline for branch usage (fast forward merges only, arbitrary merges, merge down vs up, cherry-picks with diverging branches,...). For example: Package A in F42 has a mass rebuild commit on top of F41. Packager B wants to bump both with an empty commit for a rebuild. Does maintainer of A want non-diverging branches at the expense of a bogus "f42 mass rebuild" commit in the f41 branch? Also, %autorelease does not quite fly with merges yet (release numbering, exclusion of bogus commits from changelog). Michael -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
