Re: morph's abandoned packages (list)

[Thomas Goirand <zigo@debian.org>]

On 3/30/24 02:08, Bo YU wrote:
> hi!
>
> On Sat, Mar 30, 2024 at 8:20 AM Thomas Goirand <zigo@debian.org> wrote:
> > On 3/29/24 21:18, Timo Röhling wrote:
> > > Hi Thomas,
> > >
> > > * Thomas Goirand <zigo@debian.org> [2024-03-17 23:09]:
> > > > Anyone is welcome to join, it's just that I'm using git tag workflow,
> > > > so it doesn't fit in the DPT, but that's the only thing.
> > > I am not familiar with that workflow and could not find any
> > > documentation. Can you give me a quick overview what I should do
> > > differently from the "regular" DPT workflow?
> > >
> > > Cheers
> > > Timo
> >
> > I'm not using pristine-tar, or gbp import-orig, and don't use upstream
> > tarballs, but git only. Everything is done in a single (debian) branch.
> Just share the workflow of DPT I always follow[0]:
> ```
> $ uscan   # Download your package's upstream original tarball
> $ tar -xvf srcpkgname_1.0.orig.tar.gz
> $ cd srcpkgname_1.0
> $ git init
> $ git checkout -b upstream
> $ git add .
> $ git commit -m "import srcpkgname_1.0.orig.tar.gz"
> $ git tag -s upstream/1.0
> $ pristine-tar commit ../srcpkgname_1.0.orig.tar.gz upstream
> $ git checkout -b debian/master
> ```
> And upgrade upstream release[1]. These should be enough.
> If given team maintenance, I would like to suggest to follow this.
>
> [0]: https://wiki.debian.org/Python/GitPackaging#Creating_a_new_package
> [1]: https://wiki.debian.org/Python/GitPackaging#New_upstream_release
I would not do this way, but use gbp import-orig instead. I'm not sure 
why the wiki recommends, IMO wrongly, to do things by hand. Indeed, all 
of this:

$ git checkout -b upstream
$ git add .
$ git commit -m "import srcpkgname_1.0.orig.tar.gz"
$ git tag -s upstream/1.0

can be replaced by by this simple command:
$ gbp import-orig ../srcpkgname_1.0.orig.tar.gz

Cheers,

Thomas Goirand (zigo)