Re: New lintian release?
Hi,
Axel Beckert wrote:
> Louis-Philippe Véronneau wrote:
> > I feel significant changes have been made on the git HEAD and a new lintian
> > release would be a good idea.
>
> Definitely. Also because I consider it to be (close to) a toolchain
> package. It's though (luckily 😎) not on
> https://release.debian.org/testing/essential-and-build-essential.txt
Close to doing an upload. So let's check:
> > 1. it seems "t/scripts/run-private-scripts.t" is broken again?
[…]
> That error seems to be a real error when calling
> private/generate-tag-summary. So the error is not in
> t/scripts/run-private-scripts.t but in private/generate-tag-summary
> and t/scripts/run-private-scripts.t found that issue. Which is good! 😎
>
> Not sure which file it can't find, though. On a first glance, only git
> commands seem to be executed via IPC::Run3 from
> private/generate-tag-summary, so I assume it can't find "git" — which
> on the other hand would be very weird.
>
> What output does running "private/generate-tag-summary" shows for you?
>
> Anyway, I've built the package and ran the testsuite several times
> today locally as well as on Salsa CI and I didn't see this error.
So I tend to ignore this issue for now. But I'd still be interested in
what caused this.
> > 2. BTS #1026920 should probably fixed before we upload
Fix pending and verified.
> Ok. I wonder if that will really make it for bookworm.
It's at least in unstable since 12th of January. Hence also Salsa CI
autopkgtest failed — once only, then I fixed it. :-)
> IMHO neither of them are a blocker for an upload. I'd rather consider
> that second half of the RC bug #1025868 to be more of a blocker, even
> if not a complete blocker.
Fixed and with it hopefully and finally the whole #1025868. The issue
was actually a false positive on arm64 and a false negative on all
other architecture I tested (amd64, i386, armhf) as the test itself
was broken. I just remove that single test from the test suite. Other
tests for that tag still exist.
> Actually I even think we could upload now as the Salsa CI test stage
> is green again for a few commits, but I first would like to look at
> least through the recently opened bug reports, too.
Done now, depending on what actually counts as "recently". ;-)
> and also do a bit more local testing.
Done, too. Also brought up a few things despite I wasn't actually
searching for them. But running lintian from git HEAD when working on
other packages helped indeed.
> I also assume we will do at least two uploads before the freeze
> anyway, a first big one (2.116.0) and then probably some more minor
> fixups (2.116.1) or so.
Still the plan, despite even closer to the freeze. :-/
Regards, Axel
--
,''`. | Axel Beckert <abe@debian.org>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Reply to: