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

Bug#994170: marked as done (lintian crashes for some source package)



Your message dated Mon, 13 Sep 2021 14:47:10 -0700
with message-id <CAFHYt564wqMES1Nj5G60PmHfU-JV033=Gpsc3ipruLkTzzWOXg@mail.gmail.com>
and subject line Re: Bug#994170: lintian crashes for some source package
has caused the Debian Bug report #994170,
regarding lintian crashes for some source package
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.)


-- 
994170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994170
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.105.0
Severity: important

Dear Lintian maintainers,

For some reason lintian crashes on the source package at
https://people.debian.org/~ballombe/lintian

(which is very similar to gap-gapdoc in the archive, which works fine).

with
$ lintian gap-gapdoc_1.6.4-1.dsc

Warning in processable gap-gapdoc_1.6.4-1.dsc: Use of uninitialized
value $base in pattern match
(m//) at /usr/share/lintian/lib/Lintian/Check/Fields/Source.pm line 54.
Warning in processable gap-gapdoc_1.6.4-1.dsc: Use of uninitialized
value $stem in string ne at
/usr/share/lintian/lib/Lintian/Check/Fields/Source.pm line 56.
Warning in processable gap-gapdoc_1.6.4-1.dsc: Use of uninitialized
value $stem in concatenation
(.) or string at /usr/share/lintian/lib/Lintian/Check/Fields/Source.pm
line 56.
Warning in processable gap-gapdoc_1.6.4-1.dsc: Source field does not
match package name gap-gapdoc !=  at
/usr/share/lintian/lib/Lintian/Check/Fields/Source.pm line 56.
warning: cannot run fields/source check on package
source:gap-gapdoc_1.6.4-1
skipping check of source:gap-gapdoc_1.6.4-1
remove_tree failed for
/tmp/lintian-pool-Kfy3jT_NB3/gap-gapdoc/gap-gapdoc_1.6.4-1_source:
cannot
remove directory: Directory not empty at /usr/share/perl5/Path/Tiny.pm
line 1732.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here. 

--- End Message ---
--- Begin Message ---
Version: 2.106.0

Hi,

On Mon, Sep 13, 2021 at 1:15 AM Bill Allombert <ballombe@debian.org> wrote:
>
> https://people.debian.org/~ballombe/lintian

Thank you for making the sources available. Lintian's development
version no longer crashes with them. Instead, it produces the
following hints:

$ ../../git/bin/lintian gap-gapdoc_1.6.4-1.dsc
I: gap-gapdoc source: debian-rules-parses-dpkg-parsechangelog (line 4)
I: gap-gapdoc source: no-dh-sequencer
I: gap-gapdoc source: older-debian-watch-file-standard 3
I: gap-gapdoc source: out-of-date-standards-version 4.5.0 (released
2020-01-20) (current is 4.6.0.1)
I: gap-gapdoc source: quilt-patch-missing-description
debian/patches/doc-makefile
I: gap-gapdoc source: quilt-patch-missing-description
debian/patches/makedocrel-chdir
I: gap-gapdoc source: unnecessary-source-date-epoch-assignment (line 14)
I: gap-gapdoc source: unnecessary-source-date-epoch-assignment (line 4)
X: gap-gapdoc source: debian-watch-does-not-check-gpg-signature
P: gap-gapdoc source: package-uses-old-debhelper-compat-version 12
P: gap-gapdoc source: silent-on-rules-requiring-root
P: gap-gapdoc source: trailing-whitespace debian/changelog (line 56)
P: gap-gapdoc source: trailing-whitespace debian/changelog (line 85)
X: gap-gapdoc source: upstream-metadata-file-is-missing

> $ lintian gap-gapdoc_1.6.4-1.dsc

I believe you encountered Bug#994088 ("dsc files from cwd are not
processed correctly"). From the command you listed above—thank you for
the attention to detail—you probably ran Lintian on a dsc in your
current working directory.

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

Kind regards
Felix Lechner

--- End Message ---

Reply to: