On Wed, May 22, 2024 at 12:32:32AM +0200, Salvo Tomaselli wrote: > And what's the advantage? When an nmu happens the person doing it normally > doesn't bother to push to salsa anyway. Yes, because it's unfortunately too expensive to: - make sure the repo exists and is uptodate - somehow find out what workflow does the repo imply - if it's an unfamiliar one then somehow learn it - check if there are no commits on top of the previous upload and if there are any then how to merge them with the NMU changes - check that your commit builds correctly at least when doing more than one NMU per week or whatever. The nmudiff(1) interface is standardized, one command does everything, you are still required to use it, and you need to remember that MRs don't give notifications so you have an additional reason to use it, and importing a nmudiff should be easy for the maintainer.
> At most I get a patch in the > bugreport, or I have to diff the packages and import the diff. Sending the nmudiff to the bugreport is mandatory per the devref NMU procedure (though of course that procedure itself is not a policy and not everyone follows it). -- WBR, wRAR
signature.asc
Description: PGP signature
