DEP-14 discussion and our packaging workflow

[Martin Steigerwald]

Aurélien COUDERC - 20.08.24, 21:53:32 CEST:
> there's an ongoing discussion in d-devel about formally adopting DEP-14
> and I thought I would post a comment there about our debian-only
> packaging workflow because I feel it's being overlooked.
> 
> Not that we're doing anything against what's written in dep-14 (we would
> probably have to rename our default branches from "master" but I
> consider that a non-issue), but most if not all participants in the
> discussion seem to expect that the upstream source *will* be in the
> repo in some form.

I am not (yet) packaging for Qt/KDE stuff. However from my experiences with 
git-buildpackage with my fio package… it added quite an additional 
complexity. I meanwhile got used to it… but I several times especially in 
the beginning I had gbp related error messages that took me a lot of time 
to figure out and to fix. If it works, it can be convenient. I do not (yet?) 
use its Debian changelog from git log function, mostly because I am not 
yet sure that it would actually save me time. Changelog sometimes has 
commits where I fix an error I made while packaging a new version and these 
do not need to be mentioned in changelog.

I am using it with pbuilder/cowbuilder and have no experiences with using 
git-buildpackage with sbuild.

I did not (yet) review DEP-14, there may of course be other approaches in 
there.

-- 
Martin