Package: lintian
Version: 2.114.0
Severity: wishlist
I discovered that in several of my autopkgtest scripts, and in various
other packages in the archive, the following pattern appears:
...
cd somewhere
...
for py in $(py3versions -r 2>/dev/null)
...
Unfortunately, this silently fails, as no
Processing commands for cont...@bugs.debian.org:
> unarchive 943536
Bug #943536 {Done: Felix Lechner } [lintian]
lintian: Stop shipping profile 'debian/ftp-master-auto-reject'
Unarchived Bug 943536
> reopen 943536
Bug #943536 {Done: Felix Lechner } [lintian]
lintian: Stop shipping profile
Hi Daniel,
On Mon, Dec 13, 2021 at 2:00 PM Daniel Baumann
wrote:
>
> all of them, except lzd, do implement --test.
Looking at your documentation [1] does that mean Lintian can only
offer the alternatives except lzd?
Or, is there another way to assess the actual nature or integrity of a
file
Hi Marc,
On Mon, Dec 13, 2021 at 4:33 AM Marc Haber
wrote:
>
> I wondering whether the missing leading backslash in the path is
> correct.
You probably meant a regular slash, and not a backslash. Lintian has
used such relative-looking path names since before it found me. The
only exception I
Hi Felix
On 12/13/21 21:18, Felix Lechner wrote:
We only use the '--test' functionality. Is that implemented by all
alternatives?
all of them, except lzd, do implement --test.
Also, do we still need to determine the proper name of the executable,
as introduced in this commit?
there are
Processing control commands:
> forcemerge 941656 -1
Bug #941656 [lintian] lintian: changelog-file-missing-explicit-entry not
working properly
Bug #941656 [lintian] lintian: changelog-file-missing-explicit-entry not
working properly
Marked as found in versions lintian/2.104.0.
Bug #1001651
Control: forcemerge 941656 -1
Control: severity 941656 important
Hi,
On Mon, Dec 13, 2021 at 11:00 AM Cyril Brulebois wrote:
>
> W: debian-installer source: changelog-file-missing-explicit-entry
> 20210731+deb11u1 -> 20210731 (missing) -> 20210731+deb11u2
Your case from stable was already
Processing commands for cont...@bugs.debian.org:
> retitle 941656 lintian: changelog-file-missing-explicit-entry not working
> properly
Bug #941656 [lintian] lintian: changelog-file-missing-explicit-entry false
positive for 2 consecutive NMUs (-X.1, -X.2)
Changed Bug title to 'lintian:
Hi Daniel,
On Mon, Dec 13, 2021 at 11:36 AM Daniel Baumann
wrote:
>
>if only decompression is used:
>'lzip | lzip-decompressor'
We only use the '--test' functionality. [1] Is that implemented by all
alternatives?
Also, do we still need to determine the proper name of the executable,
as
Package: lintian
Version: 2.114.0
Severity: wishlist
Hi,
in #967083, someone requested that the lintian depends on lzip should be
changed into an alternative depends on 'lzip | clzip' with the
justification, that the submitter prefered clzip as his
lzip-implementation-of-choice (for memory
Package: lintian
Version: 2.104.0
Severity: important
Hi,
This is similar to #941656, but I wanted to have it tracked separately,
with a slightly higher priority, as that's affecting people performing
regular uploads to stable.
I would expect this to apply to backports and security as well but
On Sun, Oct 06, 2019 at 06:55:39AM +0200, Andreas Metzler wrote:
> > I just uploaded ddd_3.3.12-5.2.dsc and I get this warning:
> > W: ddd source: changelog-file-missing-explicit-entry 1:3.3.12-5.1 ->
> > 1:3.3.12-5 (missing) -> 1:3.3.12-5.2
>
> > Yet the changelog file has all the entries and
Package: lintian
Version: 2.114.0
Severity: minor
Hi,
in sudo, I get
E: sudo: python3-script-but-no-python3-dep /usr/bin/python3 (does not satisfy
python3:any | python3-minimal:any)
[usr/share/apport/package-hooks/source_sudo.py]
and
E: sudo-ldap: python3-script-but-no-python3-dep
13 matches
Mail list logo
