Path: csiph.com!xmission!3.eu.feeder.erje.net!feeder.erje.net!news.szaf.org!fu-berlin.de!bofh.it!news.nic.it!robomod From: Jai kadam Newsgroups: linux.debian.maint.python,linux.debian.devel.mentors Subject: Re: Guidence regarding package testing and patching Date: Fri, 05 Dec 2025 19:30:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Dec 5 18:29:11 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-5.099 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 X-Forwarded-Encrypted: i=1; AJvYcCUMlBp/1UHjRuqLCtrvbnNq1CM3mWnrQnmawa9FaETepXy/oRxkpy+R57mYMib+vbNYgvW6xJosaw51KAtL@lists.debian.org X-Gm-Message-State: AOJu0Yyb0aSedKQZs5qwpzLGBxxSA8fP+326w6n9EIiyjT2eIo4OsKz7 BvZKA83gzRhFwo9P+6vcGGNHYDj3Ua6UEclCW0dSmG9QghsGvVTY4mDl6sLBQJ9Ypm4FnNCJQmv eDAzhY09nObCfMW4lZ63C2T/UB2fQjvs= X-Gm-Gg: ASbGnctj2K5P0noT7xZkLbPLKWQX/JdeVKEMvYp6HT/pv9NqP59UxQ6CLt5tZCBOKq0 mzr1Z3U6I3KmS5AcBiC3OHXJk91xxG6Uit0Y7rjsz1ChqJS4DFryG1hJfaHCAbu1gLrfn8SM7fD yIAZ39NTuvZ78ueDdSP+8lmJKnfj3gl6nleDWf7C0whQ3wkwSUr8XQiKK9dgkAvMiDsHp3XWUwB oC4Tff34bDWPpGxV0rDGSDdZr7Oxp/EI4LWVdIcSEDCdu913WDLNLk6EwIgmzPgPhfjNs4BqQbz BcmGSabM/aNW7hTJ+xCgp34= X-Google-SMTP-Source: AGHT+IFkp3Ji8MQ7xleNvSqNZic5ochPaub6EhVJARpw97sWugmeEbcygCNLgW7FPyHsHgPccJXkI+7+JiEwYGs2t/I= X-Received: by 2002:a05:701a:c967:b0:11b:9152:b3ad with SMTP id a92af1059eb24-11e0329e413mr23388c88.31.1764959329599; Fri, 05 Dec 2025 10:28:49 -0800 (PST) MIME-Version: 1.0 X-Gm-Features: AWmQ_blCqXaYlq5n14M1snitGc8dbV8yiUAX197FH2TaL62kXViFLMphmxRfMYE Content-Type: multipart/alternative; boundary="000000000000e244c60645389d41" X-Mailing-List: archive/latest/23477 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAJcuXADa+3O7UzxZYkNSGnNHXUEXs9NdrerhVF=USSQKonk-SA@mail.gmail.com Approved: robomod@news.nic.it Lines: 280 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Fri, 5 Dec 2025 23:58:38 +0530 X-Original-Message-ID: X-Original-References: <914e4295e638fb478a4d450df243fb876f72c22d.camel@gmail.com> <1835172.cot9YJUmRx@soren-desktop> <16652957.1uztYCDPK9@soren-desktop> Xref: csiph.com linux.debian.maint.python:17243 linux.debian.devel.mentors:48189 --000000000000e244c60645389d41 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 5 Dec, 2025, 11:48=E2=80=AFpm Soren Stoutner, wr= ote: > 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 yo= u 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 T= ime Andrey > > > > > > 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 > > > > >> > > > > >> detailed. > > > > >> > > > > >> It's very detailed > > > > > > > > > >By manual you mean "man gbp" or something else? > > > > > > > > I mean gbp-push(1), you could learn that it exists from "SEE ALSO" = of > > > > gbp(1). > > > > > > 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: > > > > > > 1. The key to understanding this is that =E2=80=9Cgbp push=E2=80=9D = will push the > > > following > > > things: > > > > > > 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. > > > > > > 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. > > > > > > 3. The following workflow accomplishes this: > > > > > > 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). > > > > Noted! :) > > > > > 4. When ready to release: > > > > > > a. dch -r (this changes the target from UNRELEASED to unstable, edit > to > > > experimental if desired). > > > > This is same as dch --release rigth ? Si it also adds the commit messag= es > > Yes, =E2=80=9Cdch -r=E2=80=9D and =E2=80=9Cdch --release=E2=80=9D are the= same. > > > b. gbp buildpackage (build the package with the final changelog). > > > > > c. Upload the package. > > > d. gbp tag (this creates the debian/X.Y-Z tag, typically one only do= es > > > this > > > after the package has been accepted into Debian). > > > e. gbp push (this pushes the debian/X.Y-Z tag). > > > > 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 > multiple git commands to do the same things, which would be to push the > pristine-tar branch (if in use), the upstream branch, and the upstream > tag. > If these things are not done at this step, other people who clone the > repository cannot build the changes you have just made. When reviewing > 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 > review > the most recent changes). > 3. gbp buildpackage. > > If you don=E2=80=99t get step 3.e and 3.f right, "gbp buildpacakge" will = fail for > me. > Oh i see cause debian-branch will have the previous version of code cause gbp never uploads it while in unreleased state and we only do dch -r when we get a green flag from a mentor or maintianer of the package which then sets it to unstable and then when we run gbp tag and gbp push all work is done. Is my understanding rigth ? > -- > Soren Stoutner > soren@debian.org > --000000000000e244c60645389d41 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, 5 Dec, 2025, 11:48=E2=80= =AFpm Soren Stoutner, <soren@debian.= org> wrote:
Resending as I r= ealized 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, <soren@debian.o= rg> wrote:
> > On Thursday, December 4, 2025 12:45:30=E2=80=AFPM Mountain Standa= rd Time Andrey
> >
> > 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
> > > >>
> > > >> detailed.
> > > >>
> > > >> It's very detailed
> > > >
> > > >By manual you mean "man gbp" or something else= ?
> > >
> > > I mean gbp-push(1), you could learn that it exists from &quo= t;SEE ALSO" of
> > > gbp(1).
> >
> > To add a bit more information about the behavior of "gbp pus= h=E2=80=9D and =E2=80=9Cgit
> > push=E2=80=9D
> > and when to use them and mix their uses:
> >
> > 1.=C2=A0 The key to understanding this is that =E2=80=9Cgbp push= =E2=80=9D will push the
> > following
> > things:
> >
> > a.=C2=A0 The pristine-tar branch (if in use).
> > b.=C2=A0 The upstream branch.
> > c.=C2=A0 Any new tags on the upstream branch.
> > d.=C2=A0 The debian branch, but only if the changelog does not ta= rget
> > UNRELEASED.
> > e.=C2=A0 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= .
> >
> > 2.=C2=A0 What we want to avoid is pushing a debian/X.Y-Z tag on t= he debian
> > branch
> > before X.Y-Z has actually been accepted into Debian.
> >
> > 3.=C2=A0 The following workflow accomplishes this:
> >
> > a.=C2=A0 gbp import-orig --uscan (this updates pristine-tar if us= ed, the
> > upstream
> > branch, the debian branch, and creates a new upstream tag).
> > b.=C2=A0 dch=C2=A0 (adjust the changelog version number according= ly, but leave the
> > target as UNRELEASED).
> > c.=C2=A0 gbp buildpackage (make sure the package builds).
> > d.=C2=A0 <Fix any problems>.
> > e.=C2=A0 gbp push (this pushes pristine-tar if in use, the upstre= am branch, and
> > the
> > new upstream branch tag, but not the debian branch because the ch= angelog
> > targets UNRELEASED).
> > f.=C2=A0 git push (this pushes the debian branch).
>
> Noted! :)
>
> > 4.=C2=A0 When ready to release:
> >
> > a.=C2=A0 dch -r (this changes the target from UNRELEASED to unsta= ble, edit to
> > experimental if desired).
>
> This is same as dch --release rigth ? Si it also adds the commit messa= ges

Yes, =E2=80=9Cdch -r=E2=80=9D and =E2=80=9Cdch --release=E2=80=9D are the s= ame.

> b.=C2=A0 gbp buildpackage (build the package with the final changelog)= .
>
> > c.=C2=A0 Upload the package.
> > d.=C2=A0 gbp tag (this creates the debian/X.Y-Z tag, typically on= e only does
> > this
> > after the package has been accepted into Debian).
> > e.=C2=A0 gbp push (this pushes the debian/X.Y-Z tag).
>
> 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.=C2=A0 Otherw= ise, you need to use
multiple git commands to do the same things, which would be to push the pristine-tar branch (if in use), the upstream branch, and the upstream tag.= =C2=A0
If these things are not done at this step, other people who clone the
repository cannot build the changes you have just made.=C2=A0 When reviewin= g
packages that other people have submitted to mentors I do the following.
1.=C2=A0 gbp clone (if I haven=E2=80=99t already cloned the repository). 2.=C2=A0 gbp pull (this pulls all three branches and the tags, so that I ca= n review
the most recent changes).
3.=C2=A0 gbp buildpackage.

If you don=E2=80=99t get step 3.e and 3.f right, "gbp buildpacakge&quo= t; will fail for me.
Oh i see= cause debian-branch will have the previous version of code cause gbp never= uploads it while in unreleased state and we only do dch -r when we get a g= reen flag from a mentor or maintianer of the package which then sets it to = unstable and then when we run gbp tag and gbp push all work is done.
<= div dir=3D"auto">
Is my understanding rigth ?
--
Soren Stoutner
so= ren@debian.org
--000000000000e244c60645389d41--