Hello,

> I have been working with the dpkg maintainers on a solution, which
> will not happen anytime soon. The underlying problem is that
> dpkg-buildpackage issues a build error when there is simply nothing to
> do.
> 
> Fixing that is complicated because source packages nowadays permit the
> building of undeclared artifacts. There is no longer a way to tell
> from a source package if a build should be attempted. Either way, I
> will triage your bug later today.
> 
> Thank you for your patience and for your help in trying to make
> Lintian better for everyone.
> 

wow I though the solution was "easy" thanks for keeping it running and rocking!

feel free to take your time, I was making sure this bug was not "disappeared" :)

I'm not sure if src:file migration to testing is stalled by this bug...

grep-excuses file
file (1:5.38-3 to 1:5.38-4)
    Maintainer: Christoph Biedl
    7 days old (needed 5 days)
    Migration status for file (1:5.38-3 to 1:5.38-4): Waiting for test results, 
another package or too young (no action required now - check later)
    Issues preventing migration:
    autopkgtest for binutils: amd64: <span style="background:#99ddff">Test in 
progress (will not be considered a regression)</span>, arm64: <span 
style="background:#99ddff">Test in progress</span>
    autopkgtest for lintian/2.46.0: amd64: <span 
style="background:#87d96c">Pass</span>, arm64: <span 
style="background:#ff6666">Reference test in progress, but real test failed 
already</span>
    Additional info:
    Piuparts tested OK - https://piuparts.debian.org/sid/source/f/file.html
    7 days old (needed 5 days)


G.

Reply via email to