Hi Guido, you're lightning fast answering as usual. I appreciate that.
On Sat, Jan 22, 2022 at 02:04:46PM +0100, Guido Günther wrote: > you say > > > Subject: Re: Bug#1004178: creates and pushes tag for unreleased > > package > > gbp-push does not _create_ any tags by itself so the tag must have > been there already (see log below). The log was created after the tag was already there. But my shell history proves that I didnt create the tag myself. > > aide (0.17.4-2~0) UNRELEASED; urgency=medium > > gbp-push checks for `UNRELEASED` in the changelog. You want to check why > this doesn't happen for your package (see the `is_released()` call in > `gbp/scripts/push.py`. I have grepped through all files delivered by git-buildpackage 0.9.25. The string is_released is in none of them. Are you talking about is_releaseable? The code that fills changelog.distribution seems to be in gbp/deb/changelog.py, which seems to use dpkg-parsechangelog -l's output. dpkg-parsechangelog -l returns "Distribution: UNRELEASED" so it looks like the external tool is working. Sorry, this is beyond my little python skills for the time being. How would I debug this best without actually pushing tags to salsa? Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
