Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Andrey Rakhmatullin Newsgroups: linux.debian.maint.python Subject: Re: Guidence on package development Date: Wed, 03 Dec 2025 21:00:01 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Dec 3 19:56:37 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-10.978 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FVGT_m_MULTI_ODD=0.02, GMAIL=1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .debian. - helo: .durkon.wrar. - helo-domain: .wrar.) FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -3.5 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="hU2fmf2taJBGW4YZ" Content-Disposition: inline X-Mailing-List: archive/latest/23450 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/aTCV4oeGfm_CWWeY@belkar.wrar.name Approved: robomod@news.nic.it Lines: 76 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Thu, 4 Dec 2025 00:56:18 +0500 X-Original-Message-ID: X-Original-References: Xref: csiph.com linux.debian.maint.python:17216 --hU2fmf2taJBGW4YZ Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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=C2=A0 > [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=20 this is the only place you should publish your changes. --=20 WBR, wRAR --hU2fmf2taJBGW4YZ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmkwleItFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh 5rEP/iKeWMEjZyQZI5bXHH7sO2Oey7CKhF8UNr0Qcu3BFHjWOYse/kNAqHtHNX1f v7r9Xmmtd8FMNReLwOkPdNlg0Mu08ZZWXp0t9uh85rF1p7Vl1rtZHwD4nLPT5ufU 7g+SdIX8TUgkdzIUAxPmyt5DahOQCD0QSpYrDR6+HTGkeBa/lYDFOY0pT+FuBoO/ KesGjX3eGq9ErGU2c7mRwA+xi8uKIDjMjqbcJl9rGL8vCOCLEHK8QJWSUsQDokUX y5UGHT5yhikdC1lD9eRblSIbMf61icjmNkS/ICNW6sTE7blqwXW1DGFkAjK7dh9g 66WKMFrAoqOWwInbIJx7hYwK7nfOwI1D3mJw8m+gvPR1RTX9ctY9LuamxLYdQAIo pD1qU9M9ESi9MZ+BlEIR4WybnkOSVatmPV8azMSI7p8iv9yYDgX6mASZHxNDwqC3 hfdYDEdJjfebvuyM8VnXmgALZ7QQ5zOM9rIpoKUiVIIHzqLIgT/G/M3ObwrSepYb li8o6gsshJ5ExmuAvfWT3kN9Gh7o3FX9F/DOelYRU2oV4DpprOMfz/qRhGd2guSQ fpa4kv8ulD+e0IdlzrvXUtB1cY7o3WxW9CHe8Oawiz14tpoAHo+bG7flfybta6SV AdfPKa/TV1q2KU40POontFBocKK+bB0hwGc6mXYx8lJwcYNR =otzv -----END PGP SIGNATURE----- --hU2fmf2taJBGW4YZ--