Path: csiph.com!news.neodome.net!feeder.usenet.ee!newsfeed.xs3.de!newsfeed.bofh.team!srl.newsdeef.eu!news.corradoroberto.it!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Soren Stoutner Newsgroups: linux.debian.devel.mentors,linux.debian.maint.python Subject: Re: Guidence regarding package testing and patching Date: Fri, 05 Dec 2025 19:20:01 +0100 Message-ID: References: X-Original-To: Jai kadam , Debian Mentors , Debian Python X-Mailbox-Line: From debian-mentors-request@lists.debian.org Fri Dec 5 18:18:44 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-114.41 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=unavailable autolearn_force=no Organization: Debian Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWIg4F7bGiws7ReTkyy kYoXFRrd6/4yMA0PAAACaklEQVQ4y22TwXabMBBFJaPuNZGSNZZp1uhM6BpkJeu4VFk3bsL/f0Lf CHC6qHyOgbl68zTDoIwaVfh3tUopTUGpbFToDiFnY9IY2oMAZYMiS4R9SfbSXepSS5EcFAa/muIU aRj8mkoUqrEraFzhYegBmqig0LyCIyM8DAwPlpBqmJVYaD2UeWZ3abVjsqKIojg+hY4omsyIcNSi qIBM6jJWOveS6kvBeVvHJ+VYzJUW88RmA12UiBx3HEcUMRuzIZI6tBQovTrPclNB3AuUXoXvs0XY C3B2baJpW4Dn2ZpVMInCirkxoyhM1qpK5nFrO65QvCrCqql2DyPgvm94iMQz5/PmISuEotxQGMD5 M5G1N9CjXJ5HQH96BZG2xx6AzejYZccxT4Re3Zr4bPKkCcGcz5Or3dVEABkAUY/znnVcQVVkrXVU vomoEJFe7x4nQuaZmZELL6qnXZGIB5YV/Q2IogtSmyNybEcBX2+QCLOAQYm+gmoORUrYzV7dc6R2 T1WPm45oVEQqsjtoIovHyTmcyxMhVVxTqapomZyLlAmTKC9AmjgamXXGZo+epNrXO3wGGiPRHbKL FnMy2RRgRb1gzFXXGjhICp8wqaTtdtyQH6nWTfkatJvJJoUCbOjSC7wR9/naEVognxrOFdLh7Ugx QpA/0QT4pRV0+u2dqsXD5y9EBDjVAJS3ZZLxmZblgmsU8x7mBeCKg48Py7WU2IiH1epbEbC8K9Ms y0cpcySVUcdQVrBY+rEsv+XpYgFKXT8B3v2yATxv8fKK2EfC358tsIMLYqfD401xA0j1EY4P/wWf IbhlOWyBv4OQsywBM8MAAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2413549.mCEkglpsDN"; micalg="pgp-sha512"; protocol="application/pgp-signature" X-Debian-User: soren X-Mailing-List: archive/latest/117365 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/16652957.1uztYCDPK9@soren-desktop Approved: robomod@news.nic.it Lines: 140 Sender: robomod@news.nic.it X-Original-Date: Fri, 05 Dec 2025 11:18:23 -0700 X-Original-Message-ID: <16652957.1uztYCDPK9@soren-desktop> X-Original-References: <914e4295e638fb478a4d450df243fb876f72c22d.camel@gmail.com> <1835172.cot9YJUmRx@soren-desktop> Xref: csiph.com linux.debian.devel.mentors:48187 linux.debian.maint.python:17242 --nextPart2413549.mCEkglpsDN Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8"; protected-headers="v1" From: Soren Stoutner Subject: Re: Guidence regarding package testing and patching Date: Fri, 05 Dec 2025 11:18:23 -0700 Message-ID: <16652957.1uztYCDPK9@soren-desktop> Organization: Debian MIME-Version: 1.0 Resending as I realized I had accidentally dropped the debian-python list. On Friday, December 5, 2025 11:07:44=E2=80=AFAM Mountain Standard Time you = wrote: > On Fri, 5 Dec, 2025, 10:59=E2=80=AFpm Soren Stoutner, = wrote: > > On Thursday, December 4, 2025 12:45:30=E2=80=AFPM Mountain Standard Tim= e Andrey > >=20 > > Rakhmatullin wrote: > > > On Fri, Dec 05, 2025 at 01:12:14AM +0530, Jai kadam wrote: > > > >> >> You can also consult its manpage to learn what does it do. > > > >> > > > > >> >I see, I read the man page just now after your suggestion it's not > > > >>=20 > > > >> detailed. > > > >>=20 > > > >> It's very detailed > > > > > > > >By manual you mean "man gbp" or something else? > > >=20 > > > I mean gbp-push(1), you could learn that it exists from "SEE ALSO" of > > > gbp(1). > >=20 > > To add a bit more information about the behavior of "gbp push=E2=80=9D = and =E2=80=9Cgit > > push=E2=80=9D > > and when to use them and mix their uses: > >=20 > > 1. The key to understanding this is that =E2=80=9Cgbp push=E2=80=9D wi= ll push the > > following > > things: > >=20 > > a. The pristine-tar branch (if in use). > > b. The upstream branch. > > c. Any new tags on the upstream branch. > > d. The debian branch, but only if the changelog does not target > > UNRELEASED. > > e. Check for a new tag in the debian branch for the latest changelog > > entry > > and push it, but only if the changelog does not target UNRELEASED. > >=20 > > 2. What we want to avoid is pushing a debian/X.Y-Z tag on the debian > > branch > > before X.Y-Z has actually been accepted into Debian. > >=20 > > 3. The following workflow accomplishes this: > >=20 > > a. gbp import-orig --uscan (this updates pristine-tar if used, the > > upstream > > branch, the debian branch, and creates a new upstream tag). > > b. dch (adjust the changelog version number accordingly, but leave the > > target as UNRELEASED). > > c. gbp buildpackage (make sure the package builds). > > d. . > > e. gbp push (this pushes pristine-tar if in use, the upstream branch, = and > > the > > new upstream branch tag, but not the debian branch because the changelog > > targets UNRELEASED). > > f. git push (this pushes the debian branch). >=20 > Noted! :) >=20 > > 4. When ready to release: > >=20 > > a. dch -r (this changes the target from UNRELEASED to unstable, edit to > > experimental if desired). >=20 > This is same as dch --release rigth ? Si it also adds the commit messages Yes, =E2=80=9Cdch -r=E2=80=9D and =E2=80=9Cdch --release=E2=80=9D are the s= ame. > b. gbp buildpackage (build the package with the final changelog). >=20 > > c. Upload the package. > > d. gbp tag (this creates the debian/X.Y-Z tag, typically one only does > > this > > after the package has been accepted into Debian). > > e. gbp push (this pushes the debian/X.Y-Z tag). >=20 > That is use gbp push only once at the very end , right? No, you also use =E2=80=9Cgbp push=E2=80=9D in step 3.e above. Otherwise, = you need to use=20 multiple git commands to do the same things, which would be to push the=20 pristine-tar branch (if in use), the upstream branch, and the upstream tag.= =20 If these things are not done at this step, other people who clone the=20 repository cannot build the changes you have just made. When reviewing=20 packages that other people have submitted to mentors I do the following. 1. gbp clone (if I haven=E2=80=99t already cloned the repository). 2. gbp pull (this pulls all three branches and the tags, so that I can rev= iew=20 the most recent changes). 3. gbp buildpackage. If you don=E2=80=99t get step 3.e and 3.f right, "gbp buildpacakge" will fa= il for me. =2D-=20 Soren Stoutner soren@debian.org --nextPart2413549.mCEkglpsDN Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmkzIe8ACgkQwufLJ66w tgNGTQ//VpQp0bDh0OUksCqMgqexktix2AkgAh/AZMq2rH4h05aR9ySKDY1OYhqw vw77QZ/EUjcCDW7PtTMz61ZI68qvujZf8sv0FmGFwumLTpItQTgZ4xl05f7vpcfC rNsG7zn2HfMDDwlc/cCIoeCLPXH3Xyd1DSfoIVuWcw5D9J51WCBDYC+U25WO1EhH Qdzf+slDcqoinmtNPTOZCWbxIPLbPu9miiA5e5mDTibqQEifiNAJPWPYmI/vVgW7 omKDoG6LL+DMqT4mO6f2u4WLyscu7kmo+W8fjJ0C8Lko9hs5NQOLqkBe97lFifem izIbPF2JXQdOh2OVzYKOBedKUOcqRzYSxjWkhubtadBDk6Rr9pKqmQMZjnobUpCO ZJepqnSU/PtG6xPYhMSHLVlpJlpjCgXQq8HevUSZG4f4gxUK+OFnp7O4PkV32R9T FiwdFQmCZz8jJoTNWlLsBzHp+BLYyVxNjIF1fUkPTRIsQOsvbIub9VYvboySnTTR XpCflHT+XjD+Tcd7ZADRNnDwg8T6aAibiaKN22tthTY7S6V/GUdhLptrLvRMcpmL YQtynDnuISD8UDRFuSGcXrxAb9IvRQ1D0II9lYsqxLSHEbzq06rDsj1r7jyIH+cX n0o/Qg2TkauwBM4GbV+DMKXqqXEf8iLAfDIN/fG8dQEvbGCKlxI= =JZWU -----END PGP SIGNATURE----- --nextPart2413549.mCEkglpsDN--