Re: Guidence on package development

Andrey Rakhmatullin <[email protected]> Thu, 4 Dec 2025 00:56:18 +0500

Newsgroups	gmane.linux.debian.devel.python
Message-ID	<[email protected]>

On Thu, Dec 04, 2025 at 12:52:38AM +0530, jvk wrote:
>
>--
>jvk <[email protected]>

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

signature.asc (application/pgp-signature, 894 B)