Path: csiph.com!weretis.net!feeder8.news.weretis.net!srl.newsdeef.eu!news.corradoroberto.it!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Jai kadam Newsgroups: linux.debian.maint.python Subject: Re: Guidence on package development Date: Wed, 03 Dec 2025 21:20:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Dec 3 20:10:59 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-5.179 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, FREEMAIL_FROM=0.001, FVGT_m_MULTI_ODD=0.02, HTML_MESSAGE=2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .gmail. - helo: .mail-pl1-x633.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Gm-Message-State: AOJu0YxPH++zq0k2XpSh/tN0rshkSV4/lN5cW+3ZK4VOd5z1/kEq2sav 9DilDf/Z81qEdPSvR9DHIej9yhJIE3KsccijAgFiu0JFLzQ5JmOixyDoKUNUKspS6snWdyUnrxS rdkoARvMcZDz+CLEkL0RUg6o7cqFvvsA= X-Gm-Gg: ASbGnctvrB5E89opq0ye9r+5JpBbKmGfkvy3gZ5uy7wUcvidyv1CBo7NZlazE8jO+Zd ow9h0MfnTypZe3YpkLvmBOtnKlRoHKX5U2JA1gsQb+cqyv8r/VmjAqn3eiyT/XklewZ41ayI+IT GCGtxptkR7x5nsZZoUTM9eLJ5XlH5nZitmhout6y684so73UTwYpFNr7txELejkUjfGFsnppzGe BhrO5XhG05rnbbLGPfjzgf8jlK+t828ZOg+g5LtpfG8IVQ1Ijpe06OKmgSmDLDfKtbTAvgDMwea +5EHidDePgzLwMqcde/Ybhvgb+FH X-Google-SMTP-Source: AGHT+IGesyAc0HR8joe3P7IanbOPRRipryhyGZiqNloxWVLI+W5HPWOCvt6ghTYa7ardsOPALZ4bFo8R5cBCsrdP7pU= X-Received: by 2002:a05:7022:2529:b0:11b:a3a7:65cd with SMTP id a92af1059eb24-11df646938cmr300239c88.12.1764792639983; Wed, 03 Dec 2025 12:10:39 -0800 (PST) MIME-Version: 1.0 X-Gm-Features: AWmQ_blQSjoQ28kxV0d1YEBpBO0r9rAr4lC1mGsakY8cJsq8ByCJqjphIZrr1Z0 Content-Type: multipart/alternative; boundary="000000000000689687064511cefd" X-Mailing-List: archive/latest/23451 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAJcuXAB=unK7cSw=CWtauG6==yRzpZRDs=9tbrD8Hmg5BNX=6g@mail.gmail.com Approved: robomod@news.nic.it Lines: 141 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Thu, 4 Dec 2025 01:40:27 +0530 X-Original-Message-ID: X-Original-References: Xref: csiph.com linux.debian.maint.python:17218 --000000000000689687064511cefd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks for the clarification, but this thing is really scratching my mind why are we making chages in a already debinized repo? If a version 2 of a package is in upstream why would someone patch the already debinized repo instead of patching the new upstream and debianzing it ? And that signature was a mistake =F0=9F=98=85 Thank you On Thu, 4 Dec, 2025, 1:26=E2=80=AFam Andrey Rakhmatullin, = wrote: > On Thu, Dec 04, 2025 at 12:52:38AM +0530, jvk wrote: > > > >-- > >jvk > > You shouldn't write *after* your dash-dash-space signature line. > > >1.Clone the salsa package repo > >2.use the "gbp import-orig --uscan" to get the actual latest upstream > >repo from github or from where the original git remote is hosted > >3.use "dch -i" to edit changelog > > [1]Querry: The repo which we clone is a debinzed repo right? > >So when we dch -i we are changing changlog of debianized repo , is this > >correct? > > Yes. > > > [2]Querry: Should we make changes in this repo? > > As opposed to? > > > [3]Querry: Have I misunderstood something ? Am i supposed to > >unzip the tarball which "gbp import-orig --uscan" and make changes in > >that directory? > > No, you are not supposed to touch that tarball directly. > > >4. use "gbp pq import" this adds a patch queue brach ig? > >5. make chages in code (patches) > >6. git add. > >7. git commit -m "patch message Gbp-Pq: Name fix-the-foo.patch" > >8. use "gbp pq export" this > > These steps are only needed if you need to add a patch. > > >9.use "gbp buildpackage --git-pbuilder" builds the package with > >pathches > >10.use "autopkgtest" test the built package > > > >[4]Querry: how to upload the finished work and where to upload? a nice > >member suggested me to you my namespace in salsa debian. > > Yes, you were told to push changes into your fork of this repo. For now > this is the only place you should publish your changes. > > -- > WBR, wRAR > --000000000000689687064511cefd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks for the clarification, but this thing is really s= cratching my mind why are we making chages in a already debinized repo? If = a version 2 of a package is in upstream why would someone patch the already= debinized repo instead of patching the new upstream and debianzing it ?=C2= =A0

And that signature was a m= istake =F0=9F=98=85

Than= k you

On Thu, 4 Dec, 2025, 1:26=E2=80=AFam Andre= y Rakhmatullin, <wrar@debian.org&= gt; wrote:
On Thu, Dec 04, 2025 at = 12:52:38AM +0530, jvk wrote:
>
>--
>jvk <jaivkadam@gmail.com>

You shouldn't write *after* your dash-dash-space signature line.

>1.Clone the salsa package repo
>2.use the "gbp import-orig --uscan" to get the actual latest = upstream
>repo from github or from where the original git remote is hosted
>3.use "dch -i" to edit changelog=C2=A0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[1]Querry: The repo which we clone is a debi= nzed repo right?
>So when we dch -i we are changing changlog of debianized repo , is this=
>correct?

Yes.

>=C2=A0 =C2=A0 =C2=A0 =C2=A0[2]Querry: Should we make changes in this re= po?

As opposed to?

>=C2=A0 =C2=A0 =C2=A0 =C2=A0[3]Querry: Have I misunderstood something ? = Am i supposed to
>unzip the tarball which "gbp import-orig --uscan" and make ch= anges in
>that directory?

No, you are not supposed to touch that tarball directly.

>4. use "gbp pq import" this adds a patch queue brach ig?
>5. make chages in code (patches)
>6. git add.
>7. git commit -m "patch message Gbp-Pq: Name fix-the-foo.patch&quo= t;
>8. use "gbp pq export" this

These steps are only needed if you need to add a patch.

>9.use "gbp buildpackage --git-pbuilder" builds the package wi= th
>pathches
>10.use "autopkgtest" test the built package
>
>[4]Querry: how to upload the finished work and where to upload? a nice<= br> >member suggested me to you my namespace in salsa debian.

Yes, you were told to push changes into your fork of this repo. For now this is the only place you should publish your changes.

--
WBR, wRAR
--000000000000689687064511cefd--