On Fri, 5 Jan 2024 16:44:03 +0100 Guido =?iso-8859-1?Q?G=FCnther?=
wrote:
What we need to figure out is a way to distinguish "old" style
repos (default upstream and master (or what gbp.conf provides) with
newly created ones (default debian/latest and upstream/latest or what
gbp.conf provides).
Thanks Guido of for the inside about backwards compatibility issues. I did
not realize that git-buildpackage doesn't have way did is distinguish when
it is running on an existing repository and when on a 'fresh' repository.
Maybe we can engineer something to give it that capability automatically,
Hi,
On Fri, Jan 05, 2024 at 12:25:24PM +0800, Otto Kekäläinen wrote:
> Hi and Happy New Year!
>
> Using 'debian/latest' instead of 'master' by default in
> git-buildpackage would still make sense.
It does. Thanks for looking into this. I'll add some details below:
>
> I started drafting a PR
Hi and Happy New Year!
Using 'debian/latest' instead of 'master' by default in
git-buildpackage would still make sense.
I started drafting a PR at
https://github.com/agx/git-buildpackage/pull/93 to implement this, but
it takes a while to read through and understand all the 500+ mentions
of
Package: git-buildpackage
Version: 0.7.5
Severity: wishlist
We should default to branch layout that uses debian/sid as default
packaging branch and upstream/latest for the upstream sources when
creating new repositories with import-dsc or import-orig.
5 matches
Mail list logo
