Le Sun, Nov 16, 2025 at 05:50:51PM +0200, Adrian Bunk a écrit : > > A better workflow would be something like: > - a dh_copyright creates and updates debian/copyright > - the build aborts on non-trivial changes[1] > - the maintainer reviews the changes when the build aborted > (including after the initial packaging) > - a more thorough review happens after the initial upload in NEW
I like this approach. In a much weaker form, I have implemented it in the routine-update tool, where git attributes are used to diff the copyright statements in the current and previous package versions for strings like copyright or license: https://salsa.debian.org/debian/routine-update/-/blob/b20ee49d73717b82a73979a6ac8b2038dd74b71b/routine-update#L1026-1031 if [ "$COPYRIGHT_DIFF" == 1 ]; then echo "I: Copyright diff" printf '* diff=copyrightcheck\n' > debian/routineUpdateTmpGitattributes git -c 'core.attributesFile=debian/routineUpdateTmpGitattributes' -c diff.copyrightcheck.textconv='! f() { grep -i -e copyr -e licen -e © -e \(c\) -e gpl\ $1 || true ; } ; f' diff --textconv "$STARTING_COMMIT_ID"..HEAD rm -f debian/routineUpdateTmpGitattributes fi Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from home https://framapiaf.org/@charles_plessy - You do not have my permission to use this email to train an AI -
