On Wed, 5 May 2021, Felix Lechner wrote:
> > X: klibc source: non-consecutive-debian-revision 2.0.8-6 -> 2.0.8-6.1
>
> Where may I find your NMU for klibc, please?
I haven’t uploaded it yet, let’s give bwh a chance to do it first ;)
Attached.
bye,
//mirabilos
--
Sometimes they [people] care
Hi,
On Wed, May 5, 2021 at 12:57 PM Thorsten Glaser wrote:
>
> X: klibc source: non-consecutive-debian-revision 2.0.8-6 -> 2.0.8-6.1
Where may I find your NMU for klibc, please?
I believe the issue your are seeing was fixed in this unreleased commit:
Package: lintian
Version: 2.104.0
Followup-For: Bug #942013
X-Debbugs-Cc: t...@mirbsd.de
This bug is still pertinent:
X: klibc source: non-consecutive-debian-revision 2.0.8-6 -> 2.0.8-6.1
N:
P: non-consecutive-debian-revision
-- System Information:
Debian Release: 11.0
APT prefers
Package: lintian
Version: 2.85.0
Followup-For: Bug #942013
This bug still persists (popped up again, apparently; I never saw
it before).
-- System Information:
Debian Release: bullseye/sid
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'),
Control: reopen 942013 !
Hi Chris,
Thanks for your efforts to solve this issue, but it persists.
On 2019-10-16:
X: fbcat source: non-consecutive-debian-revision 0.3-1 -> 0.3-1.1
dpkg -l | grep lintian
ii lintian 2.27.0 allDebian package checker
Thanks in advance.
Cheers,
Eriberto
Package: lintian
Version: 2.25.0
Severity: normal
When doing an NMU, lintian doesn't recognise a revision number as consecutive.
X: gitmagic source: non-consecutive-debian-revision 20160304-1 -> 20160304-1.1
I think that this issue is related to same source code portion affecting
#941656.
6 matches
Mail list logo
