Open venthur opened 2 months ago
Thanks for reporting this! It is indeed git-buildpackage that emits this nag:
± gbp buildpackage -S
gbp:error: upstream/3.3.1 is not a valid treeish
This is correct behavior by git-buildpackage as it thinks that the 'master' branch is the Debian packaging branch but it is in reality the upstream branch.
What is the Debian branch for this package?
Looking at https://github.com/venthur/dotenv-cli/branches there is no separation between upstream and Debian package. However the format is not native (but quilt) and versioning scheme has Debian-specific revisions.
± cat debian/source/format
3.0 (quilt)
Looking at the tags it seems that this indeed should be a native package and not have Debian revisions at all? The git history is not linear and is written in a way that is hard to read, gitk screenshot attached.
Correct,
as I said. I happen to be upstream and Debian Developer at the same time, so it is convenient for me to have the debian dir directly in the "upstream" code. The package is not "native" as it is obviously not a debian-only package. E.g. the dotenv
command is generally useful for developers.
Not sure why gbp is failing here, I have never used gpb for any of my packages.
Cheers!
The git-buildpackage failure is due to it not finding the upstream branch. It is correct for it to fail, as you are have no upstream branch/tag, but instead only Debian releases, yet the package is not marked as being 'native'.
It is correct for it to fail, as you are have no upstream branch/tag, but instead only Debian releases, yet the package is not marked as being 'native'.
Yes, but again, this is not a "native" package as per Debian's definition:
A native Debian package is the rare Debian binary package format. It may be used only when the package is useful and valuable only for Debian. Thus, its use is generally discouraged.
It does say further down:
A native Debian package has no separation between the upstream code and the Debian changes and consists only of the following:
But this is just a consequence of the first statement.
In my case, the package is definitely not native -- as it is not a Debian only package. It just happens to fulfill the second part as I am upstream and Debian package maintainer at the same time.
This might be an edge case, but a case that is not handled well by gbp
. pdebuild
+ cowbuilder
seem to have no issue with this setup and build the package just fine.
Trying to
debcraft release
on one of my projects yields this error and it is unclear what it means or what to do with it:The logs mentioned in the last line is just a single empty file. The package I'm trying to release is: https://github.com/venthur/dotenv-cli -- just run it on latest
master
equivalent to the latest tag3.3.1
. I'm not consciously usinggbp
or anything to maintain that package in git. However, I am upstream and DD at the same time.