[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1002614: marked as done (no longer report source-is-missing for binary file in source)

Your message dated Thu, 13 Jan 2022 10:08:14 -0800
with message-id <CAFHYt57NpmdQ4PBpaURgdkAsECFKfUe7hXvT-YZY1RroLBmnkw@mail.gmail.com>
and subject line Re: Bug#1002614: no longer report source-is-missing for binary file in source
has caused the Debian Bug report #1002614,
regarding no longer report source-is-missing for binary file in source
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1002614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002614
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lintian
Version: 2.111.0
Severity: important
X-Debbugs-Cc: zhsj@debian.org

When I packaging kata-containers, which has a binary file in orig tarball.
The I got rejected by ftp-master since they found lintian emitted
"source-is-missing" error.

However when I run lintian on testing, I didn't get such error. So this seems
a regression?

I have put the package in https://people.debian.org/~zhsj/temp/lintian-bug/
The binary file is at src/runtime/virtcontainers/pkg/firecracker/swagger_linux_amd64.

--- End Message ---
--- Begin Message --- 
Hi,

On Wed, Jan 12, 2022 at 7:40 PM Shengjing Zhu <zhsj@debian.org> wrote:
>
> File name is src/runtime/virtcontainers/pkg/firecracker/swagger_linux_amd64.

I cannot reproduce the issue.

With Lintian version 2.111.0 checked out (but on a stable system) the
dsc you so kindly made available via people.d.o provoked the following
messages. They include the source-is-missing tag in question:

➤ ../../git/bin/lintian kata-containers_2.3.0\~rc1+ds1-1.dsc
Use of uninitialized value $step in concatenation (.) or string at
/lcl/lechner/lintian/git/bin/../lib/Lintian/Version.pm line 89.
E: kata-containers source: source-is-missing
src/runtime/virtcontainers/pkg/firecracker/swagger_linux_amd64
I: kata-containers source: patch-not-forwarded-upstream
debian/patches/0003-Remove-Realtime-option.patch
X: kata-containers source: debian-watch-does-not-check-gpg-signature
P: kata-containers source: source-contains-prebuilt-binary
src/runtime/virtcontainers/pkg/firecracker/swagger_linux_amd64
P: kata-containers source: very-long-line-length-in-source-file
docs/design/arch-images/kata-2-metrics.drawio line 1 is 2267
characters long (>512)
P: kata-containers source: very-long-line-length-in-source-file
docs/design/arch-images/kata-metrics-sequence-diagram.drawio line 1 is
2219 characters long (>512)
P: kata-containers source: very-long-line-length-in-source-file
docs/design/architecture.md line 108 is 619 characters long (>512)
P: kata-containers source: very-long-line-length-in-source-file ...
use --no-tag-display-limit to see all (or pipe to a file/program)

> For the record of the rejection, unfortunately it's not archived. But if you have
> irc log on #debian-ftp, it was replied on UTC 2021-12-25 12:02.

Thank you for that reference, I reviewed your interaction but there
was no indication which Lintian version the Archive Team used (I
believe they are still on2.94.0~bpo10+1).

Either way, it may not matter because the current development head,
too, provokes the tag:

➤ ../../git/bin/lintian kata-containers_2.3.0\~rc1+ds1-1.dsc
E: kata-containers source: source-is-missing
[src/runtime/virtcontainers/pkg/firecracker/swagger_linux_amd64]
I: kata-containers source: adopted-extended-field (in section for
source) XS-Go-Import-Path [debian/control:57]
I: kata-containers source: patch-not-forwarded-upstream
[debian/patches/0003-Remove-Realtime-option.patch]
P: kata-containers source: source-contains-prebuilt-binary
[src/runtime/virtcontainers/pkg/firecracker/swagger_linux_amd64]
P: kata-containers source: very-long-line-length-in-source-file line 1
is 2219 characters long (>512)
[docs/design/arch-images/kata-metrics-sequence-diagram.drawio]
P: kata-containers source: very-long-line-length-in-source-file line 1
is 2267 characters long (>512)
[docs/design/arch-images/kata-2-metrics.drawio]
P: kata-containers source: very-long-line-length-in-source-file line
108 is 619 characters long (>512) [docs/design/architecture.md]
P: kata-containers source: very-long-line-length-in-source-file ...
use --no-tag-display-limit to see all (or pipe to a file/program)
X: kata-containers source: debian-watch-does-not-check-gpg-signature
[debian/watch]

Did you perhaps disable the cruft check locally with '-X cruft' in
order to avoid the complications of Bug#993613? [1] That check
likewise issues source-is-missing. [2] At the moment, we also do that
for the website as you can see in the command-line option for your
run. [3] You would not have seen the tag there, either.

Closing this bug. Please feel free to reopen if the action was taken in error.

Kind regards
Felix Lechner

[1] https://bugs.debian.org/993613
[2] https://lintian.debian.org/tags/source-is-missing
[3] https://lintian.debian.org/sources/kata-containers

--- End Message ---
Reply to: