Bug#301011: #301011 - more verbose instructions on new upstream package
Holger Levsen <[email protected]> Wed, 13 May 2026 10:37:02 +0000
| Newsgroups | gmane.linux.debian.devel.policy |
|---|---|
| Message-ID | <agRUTujhXPKnbLYX__15839.9955181935$1778668767$gmane$org@layer-acht.org> |
hi serafi, On Tue, May 12, 2026 at 11:07:32PM +0200, Serafeim (Serafi) Zanikolas wrote: > tags 301011 + patch once again, thanks for the patch! I only have one issue with it: (and some minor ones) > +To update a package for a new upstream release: [...] > +2. Diff the old and new upstream sources (e.g. with ``diff -urN`` or ``git`` > + equivalent) to get a feel for the scope of the changes, where work is actively > + being done (and thus where new bugs may appear), and also keep an eye out for > + anything suspicious. this doesnt sound like one should review the whole diff, which is what we should recommend to do first, if possible and only if thats not possible because the changes are too big, one should fall back to strategies like the above. also it might be useful to give suggestions how to filter out .po files etc > +3. Port the old Debian packaging to the new version. This basically involves > + merging ``debian/patches`` from the old package to the new one and incrementing > + the ``debian/changelog``. i'd reverse the order: increment d/changelog and (if applicable) merge/update d/patches. > +6. If any changes were made to the build system (hopefully you'd know from steps > + 1 and 2), update the ``debian/rules`` and ``debian/control`` build > + dependencies if necessary. drop the hopefully? > +7. Build the new package in a chroot, e.g. using ``pbuilder``. A chroot ensures > + that all required build dependencies are listed in ``debian/control``, and > + eliminates the possibility of interference of any third party packages in > + your system. chroot is a specific tool. "isolated environment" is a better more general term, also sbuild's unshare mode doesnt need a chroot :) in general i would probably recommend sbuild over pbuilder these days, and definitly\ I would mention both. that said, this is very good patch already, thank you! -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ It's not climate change nor climate crisis, it's climate disaster.
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAmoEVEoACgkQCRq4Vgaa qhy4AA/9Fj5q9odT1dlY4f3Huhker6Iqz3x/93iFKN+hH76vdhWQi9rBKhdO0+OM EPONEAHvnly0ZUqAIdWnrWJECDgVOLqJEiCiCtRectE+IfnNyg3b2kpFgx9nxmxj hubGppnu3jCriJL5PE4E97VB7klWJKJAX3EXjaZQ/szm0h6he8rN4Ky/JeIIOCJM N1iZLn2qhgbhCFoaj6/kM4zrrn//+Kzg1hUUz5GkCu0QSMI6AeMZWOXsiaUu+uzx dBiBnJSYpwixfHhyZWZkekTQiQF2PY7erfLFtu9tX0g+Ovoy8uej6ZE2YgIjHk2I kCjdDDJ54WShhHFnqRljNIgBV62QsBtObh3g17lMKmCoewfeB9kozwsjn5YzMm30 7DmvKIZDBvoNqdAYIEH9NPQ7nGoLdyAy2CHPBjZmE8D7rN73m8EjoB3+m6dFokaB uLUb1uLxM3dsxpxTalvYjpjw3Q/F7+aJK3GLvAtAAIhg5JTte0OimBiC1NgrsUhG 1dhDARapAl8CKDs1VyYWsGUZ2uMqC+nBR6TsDtmWAXWom6/Wp+JYgi3LxWm3xPYR RA5lb442fzseV1/1xRby1PaB6v0wrTqyo8Zgu3fkB59adAuGhB3Vns19XFcNJGi9 P+eIiS/WJpNYxBFLleHMHOhw47cwNG1pbEOlQOt+MlycXlQfVvQ= =4iQA -----END PGP SIGNATURE-----