On Tue, 2020-05-05 at 13:02 -0500, Justin Forbes wrote: > > > So when I'm trying to fix an urgent issue in a package that tries to > > keep its spec file elsewhere, I usually just fix it in dist-git and > > issue apologies later. I don't see a way this is ever going to not be > > the case unless you give all provenpackagers commit rights to the > > 'upstream' repo, or have a completely automated PR merging system that > > also triggers a downstream build, or something like that. > > With the model that the kernel has switched to, this would technically > still work. Of course by default, if we didn't pay attention, the next > time we do a build it would literally overwrite anything you changed. This is pretty standard in this situation, yeah. Often the fix we're putting in is literally a backport from upstream, so this isn't really an issue, because the next time someone does a build from upstream it'll likely be a new version that includes the change anyway. Otherwise if it's something that feels like it'd be "fragile" I try to send a PR or at least file an issue to get the change ported back upstream. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ 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
