Bug#1003353: tagging 1012326, tagging 1012690, tagging 1012464, tagging 1001317, tagging 1012221, tagging 1011807 ...

To: Axel Beckert <abe@debian.org>, 1003353@bugs.debian.org
Subject: Bug#1003353: tagging 1012326, tagging 1012690, tagging 1012464, tagging 1001317, tagging 1012221, tagging 1011807 ...
From: Andreas Beckmann <anbe@debian.org>
Date: Mon, 20 Jun 2022 08:59:31 +0200
Message-id: <[🔎] c1c95a89-02b2-fcfd-4cc6-a3750150963f@debian.org>
Reply-to: Andreas Beckmann <anbe@debian.org>, 1003353@bugs.debian.org
In-reply-to: <[🔎] 20220619142737.s6tbtuvmv37wihsm@sym.noone.org>
References: <1655106153-2826-bts-anbe@debian.org> <[🔎] 20220619142737.s6tbtuvmv37wihsm@sym.noone.org> <20220108200235.54ecnfu5cbefqkov@begin>

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 thearchive), so this bug shows up e.g. as a RC bug in stable.So limiting this bug with an incorrect version to sid+ was the smallerlie ...


Andreas

Reply to:

References:
- Bug#1003353: tagging 1012326, tagging 1012690, tagging 1012464, tagging 1001317, tagging 1012221, tagging 1011807 ...
  - From: Axel Beckert <abe@debian.org>

Prev by Date: Processed: Bug#1003353 marked as pending in lintian
Next by Date: Processed: Re: tagging 1012326, tagging 1012690, tagging 1012464, tagging 1001317, tagging 1012221, tagging 1011807 ...
Previous by thread: Processed: Re: tagging 1012326, tagging 1012690, tagging 1012464, tagging 1001317, tagging 1012221, tagging 1011807 ...
Next by thread: Processed: Re: tagging 1012326, tagging 1012690, tagging 1012464, tagging 1001317, tagging 1012221, tagging 1011807 ...
Index(es):
- Date
- Thread