Hi Ben,
Ben Hutchings wrote:
> > https://salsa.debian.org/lintian/lintian/-/commit/192e15ae2eda7535622d44d2f3f382783b110ee5
> [...]
>
> This didn't fix the issue. It is still reproducible by building linux
> for amd64 and then running lintian over the resulting .changes file.
>
> Running
Processing control commands:
> reopen -1
Bug #1003456 {Done: Axel Beckert } [lintian] Excessive memory
use with large binaries
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer
Control: reopen -1
Control: found -1 2.115.0
On Fri, 2022-03-11 at 20:39 +, Felix Lechner wrote:
> Control: tag -1 pending
>
> Hello,
>
> Bug #1003456 in lintian reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message below and you
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1007257: fixed in lintian 2.115.0
has caused the Debian Bug report #1007257,
regarding Please upgrade missing-systemd-timer-for-cron-script to a warning
to be marked as done.
This means that you claim that
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 20 Jun 2022 13:23:02 +0200
Source: lintian
Architecture: source
Version: 2.115.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers
Changed-By: Axel Beckert
Closes: 657390 932634
lintian_2.115.0_source.changes uploaded successfully to localhost
along with the files:
lintian_2.115.0.dsc
lintian_2.115.0.tar.xz
lintian_2.115.0_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#996740: fixed in lintian 2.115.0
has caused the Debian Bug report #996740,
regarding lintian: Exempt autotools-generated files from tags for long source
lines
to be marked as done.
This means that you claim
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#999768: fixed in lintian 2.115.0
has caused the Debian Bug report #999768,
regarding lintian: false report: adopted-extended-field XS-Autobuild
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#995286: fixed in lintian 2.115.0
has caused the Debian Bug report #995286,
regarding lintian: new-package-should-not-package-python2-module false positive
for python-*-doc packages
to be marked as done.
This
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#989381: fixed in lintian 2.115.0
has caused the Debian Bug report #989381,
regarding lintian: spelling-error-in-copyright is triggering on names
to be marked as done.
This means that you claim that the
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#999810: fixed in lintian 2.115.0
has caused the Debian Bug report #999810,
regarding lintian: dh-sequence-sphinxdoc is valid prerequisite for dh_sphinxdoc
to be marked as done.
This means that you claim that
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#941656: fixed in lintian 2.115.0
has caused the Debian Bug report #941656,
regarding lintian: changelog-file-missing-explicit-entry: false positives with
successive stable uploads
to be marked as done.
This
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#941656: fixed in lintian 2.115.0
has caused the Debian Bug report #941656,
regarding lintian: changelog-file-missing-explicit-entry not working properly
to be marked as done.
This means that you claim that
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#963099: fixed in lintian 2.115.0
has caused the Debian Bug report #963099,
regarding lacks-unversioned-link-to-shared-library false positive
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 20 Jun 2022 14:34:14 +
with message-id
and subject line Bug#1012090: fixed in lintian 2.115.0
has caused the Debian Bug report #1012090,
regarding riscv support in lintian tag binary-from-other-architecture
to be marked as done.
This means that you claim that the
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#657390: fixed in lintian 2.115.0
has caused the Debian Bug report #657390,
regarding lintian: Please make build-arch and build-indep required targets
to be marked as done.
This means that you claim that the
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#932634: fixed in lintian 2.115.0
has caused the Debian Bug report #932634,
regarding lintian: false-positive embedded-library libyaml due to matching
string (defined in data/binaries/embedded-libs) with
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1006859: fixed in lintian 2.115.0
has caused the Debian Bug report #1006859,
regarding lintian: warn about devhelp version 1 files
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1006390: fixed in lintian 2.115.0
has caused the Debian Bug report #1006390,
regarding Incorrect entry in SEE ALSO section of lintian(1)
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1007140: fixed in lintian 2.115.0
has caused the Debian Bug report #1007140,
regarding please have a check for chown user.group
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1005184: fixed in lintian 2.115.0
has caused the Debian Bug report #1005184,
regarding lintian: package-does-not-install-examples should not look in tests
to be marked as done.
This means that you claim that
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1005046: fixed in lintian 2.115.0
has caused the Debian Bug report #1005046,
regarding lintian: [false positive] very-long-line-length-in-source-file for
pictures and sounds
to be marked as done.
This means
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1005762: fixed in lintian 2.115.0
has caused the Debian Bug report #1005762,
regarding lintian: Update known Java version up to 19
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1004660: fixed in lintian 2.115.0
has caused the Debian Bug report #1004660,
regarding [PATCH] lintian-annotate-hints: line-wrapping broken when stdin is
not a terminal
to be marked as done.
This means that
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1004239: fixed in lintian 2.115.0
has caused the Debian Bug report #1004239,
regarding tag-display-limit can be overriden via configuration file
to be marked as done.
This means that you claim that the
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1004231: fixed in lintian 2.115.0
has caused the Debian Bug report #1004231,
regarding ancient outdated parts in lintian.txt.gz do reduce trust in docs
to be marked as done.
This means that you claim that the
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1003817: fixed in lintian 2.115.0
has caused the Debian Bug report #1003817,
regarding lintian: fpos for update-debian-copyright
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1003913: fixed in lintian 2.115.0
has caused the Debian Bug report #1003913,
regarding lintian: False positive:
package-contains-documentation-outside-usr-share-doc
to be marked as done.
This means that you
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1004240: fixed in lintian 2.115.0
has caused the Debian Bug report #1004240,
regarding more flexibility wrt command line and confiuration file
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1003941: fixed in lintian 2.115.0
has caused the Debian Bug report #1003941,
regarding lintian: FP executable-in-usr-lib for /usr/lib/cgi-bin/
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1003668: fixed in lintian 2.115.0
has caused the Debian Bug report #1003668,
regarding lintian: FP missing-build-dependency-for-dh-addon with
pybuild-plugin-pyproject
to be marked as done.
This means that
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1003456: fixed in lintian 2.115.0
has caused the Debian Bug report #1003456,
regarding Excessive memory use with large binaries
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1003353: fixed in lintian 2.115.0
has caused the Debian Bug report #1003353,
regarding lintian: Cannot use brackets in suppression rules?
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1003272: fixed in lintian 2.115.0
has caused the Debian Bug report #1003272,
regarding lintian: chokes on overrides with "(" but no ")"
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1002828: fixed in lintian 2.115.0
has caused the Debian Bug report #1002828,
regarding lintian: please add rakudo as known interpreter
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1003131: fixed in lintian 2.115.0
has caused the Debian Bug report #1003131,
regarding debug-suffix-not-dbg references incorrect section of dev ref
to be marked as done.
This means that you claim that the
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1001655: fixed in lintian 2.115.0
has caused the Debian Bug report #1001655,
regarding Avoid hardcoding depends on specific lzip implementations
to be marked as done.
This means that you claim that the
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1000977: fixed in lintian 2.115.0
has caused the Debian Bug report #1000977,
regarding lintian: bogus elf-error in debug symbols
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#1000234: fixed in lintian 2.115.0
has caused the Debian Bug report #1000234,
regarding lintian: Compare Debhelper prerequisites accurately w/r/t multiarch
acceptor
to be marked as done.
This means that you
Axel Beckert pushed new tag 2.115.0 at lintian / lintian
--
View it on GitLab: https://salsa.debian.org/lintian/lintian/-/tree/2.115.0
You're receiving this email because of your account on salsa.debian.org.
Processing control commands:
> tag -1 pending
Bug #1003353 [lintian] lintian: Cannot use brackets in suppression rules?
Ignoring request to alter tags of bug #1003353 to the same tags previously set
--
1003353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003353
Debian Bug Tracking System
Hi Andreas,
Andreas Beckmann wrote:
> On 19/06/2022 16.27, Axel Beckert wrote:
> > please explain what makes you think that this issue is present in
> > lintian 2.114.0 as currently in Debian Unstable.
>
> The BTS does not understand made up versions (i.e. versions not in the
> archive),
Yes,
Processing control commands:
> tag -1 sid
Bug #1003353 [lintian] lintian: Cannot use brackets in suppression rules?
Added tag(s) sid.
--
1003353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 sid
On 19/06/2022 16.27, Axel Beckert wrote:
please explain what makes you think that this issue is present in
lintian 2.114.0 as currently in Debian Unstable.
The BTS does not understand made up versions (i.e. versions not in the
archive), so this bug shows up e.g. as a RC
44 matches
Mail list logo
