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

Bug#940994: marked as done (lintian: changelog-file-missing-explicit-entry false positive for versions like flatpak_1.2.5-0+deb10u1)



Your message dated Fri, 27 Sep 2019 15:36:40 +0000
with message-id <E1iDsIS-0004kc-Kq@fasolo.debian.org>
and subject line Bug#940994: fixed in lintian 2.24.0
has caused the Debian Bug report #940994,
regarding lintian: changelog-file-missing-explicit-entry false positive for versions like flatpak_1.2.5-0+deb10u1
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.)


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

I'm currently preparing an upload of a new upstream stable-branch version
of flatpak for buster (see #940818). It is a new upstream version released
directly to the buster branch, not a backport or update of a pre-existing
package with the same upstream version number (bullseye/unstable already
have a newer upstream branch for flatpak).

My understanding is that the conventional version number for such
things looks like 1.2.5-0+deb10u1, analogous to the convention of using
versions like foo_7.8.9-0.1 to NMU new upstream versions. The release
team seems to agree that this is correct versioning: for example see
dbus in (old)oldstable.

lintian currently emits:

    changelog-file-missing-explicit-entry 1.2.4-1 -> 1.2.5-0 (missing) -> 1.2.5-0+deb10u1

To accommodate the 0+deb10u1 convention, I think there should be an
exception to this tag, preventing it from being emitted for revision
numbers that "are based on" revision 0.

Thanks,
    smcv

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lintian depends on:
ii  binutils                     2.32.51.20190909-1
ii  bzip2                        1.0.8-2
ii  diffstat                     1.62-1+b1
ii  dpkg                         1.19.7
ii  dpkg-dev                     1.19.7
ii  file                         1:5.37-5
ii  gettext                      0.19.8.1-9
ii  gpg                          2.2.17-3
ii  intltool-debian              0.35.0+20060710.5
ii  libapt-pkg-perl              0.1.36+b1
ii  libarchive-zip-perl          1.66-1
ii  libcapture-tiny-perl         0.48-1
ii  libcgi-pm-perl               4.44-1
ii  libclass-accessor-perl       0.51-1
ii  libclone-perl                0.41-1+b1
ii  libdpkg-perl                 1.19.7
ii  libemail-valid-perl          1.202-1
ii  libfile-basedir-perl         0.08-1
ii  libfile-find-rule-perl       0.34-1
ii  libio-async-loop-epoll-perl  0.20-1
ii  libio-async-perl             0.74-1
ii  libipc-run-perl              20180523.0-1
ii  liblist-compare-perl         0.53-1
ii  liblist-moreutils-perl       0.416-1+b4
ii  libmoo-perl                  2.003004-2
ii  libpath-tiny-perl            0.108-1
ii  libtext-levenshtein-perl     0.13-1
ii  libtimedate-perl             2.3000-2
ii  libtry-tiny-perl             0.30-1
ii  libtype-tiny-perl            1.004004-1
ii  liburi-perl                  1.76-1
ii  libxml-simple-perl           2.25-1
ii  libyaml-libyaml-perl         0.80+repack-2
ii  man-db                       2.8.7-3
ii  patchutils                   0.3.4-2+b1
ii  perl [libdigest-sha-perl]    5.28.1-6
ii  t1utils                      1.41-3
ii  xz-utils                     5.2.4-1+b1

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b5

Versions of packages lintian suggests:
ii  binutils-multiarch     2.32.51.20190909-1
ii  libhtml-parser-perl    3.72-3+b3
ii  libtext-template-perl  1.55-1

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.24.0

We believe that the bug you reported is fixed in the latest version of
lintian, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 940994@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lamb <lamby@debian.org> (supplier of updated lintian package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 27 Sep 2019 08:15:59 +0000
Source: lintian
Architecture: source
Version: 2.24.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers <lintian-maint@debian.org>
Changed-By: Chris Lamb <lamby@debian.org>
Closes: 940994
Changes:
 lintian (2.24.0) unstable; urgency=medium
 .
   [ Felix Lechner ]
   * Do not emit changelog-file-missing-explicit-entry when maintainer
     revision is 0 (eg. 1.2.5-0+deb10u1). (Closes: #940994)
   * Remove internal support for checking whether binary packages are
     "native".
   * Various code cleanups, splitting checks/fields.pm into smaller
     components, moving numerous tags, etc.
Checksums-Sha1:
 b2dd59f1cf5163b42132c963c390feae12bc9171 3920 lintian_2.24.0.dsc
 cc6bb3903d283714fc38201ee043fbaa6b7919aa 1765164 lintian_2.24.0.tar.xz
 055d8de59d6f78f0999686f0eb74bb7693bb3e24 16551 lintian_2.24.0_amd64.buildinfo
Checksums-Sha256:
 7f8af10f908ef7f8471bbdb8182033dc225e90b56501b6da07f5c71ff851da0b 3920 lintian_2.24.0.dsc
 52d562c45ea8038f8a6716b634e5372dcaa768c9cc64064cddc39957d497e850 1765164 lintian_2.24.0.tar.xz
 f12221414754c819afcbc3012a0d1bdedde185eafbafef8000402b2935e6e22c 16551 lintian_2.24.0_amd64.buildinfo
Files:
 3acdf2a2b804869c6c5e49f169e5e444 3920 devel optional lintian_2.24.0.dsc
 5da45313c9d16c67cc315337db16d1c8 1765164 devel optional lintian_2.24.0.tar.xz
 64c5550c9f5fd5618eefc0f91a88bf8f 16551 devel optional lintian_2.24.0_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl2OKP0ACgkQHpU+J9Qx
HlhYiBAAuoJ3hKixEl4nka2huVtqpQBdXq4VPgbqrKDOJuVeunWPsmg2coxeA8Pt
W2TH/M0LCkBmy+Qf832osS98/232UWGW9UxfQtOo08I1LcALkNpIE0Pdw64nXpZD
uyc4JRwTw21xx+3KHm/tJL18WJft3p2LsWKNvEjPmKX6sTfrxRzzuLKN0BqrGU9/
EBslWLiFwg4FbcFVm43/Alv247RovieuM9tNd+CrhdyrrYj/evRej+vspqzXAvms
hWLxxCJ/fPix1AaB7B9U8mJEr7u+EydDM4Rwlo/BWTuJB/Y8rQwMmWRGqS5uzeJT
yP1O5zG6t2yVmYN3bIZfAEf2SKXaoJoTPRV1NOrNqrjh/upv7mFU9E5QdvAowxi6
3Q0kC2Z0FbSnNG85p9THV/BVFC0tGeR/p9hKvBWaC68JMVt7zrhb5VEk9FgSdgo7
E4ToQzImxyASzM94p5rIhDmZ+e/0pRG4mgVeyJpigcxJ+khkfXAwSiLOV5n/4iKB
BIfOeFVGHkuy+DP+Usin/Qk3dnFQ8p+J59KXc1SE6Xc4leyeYldVeKzzPSdMDYJ3
+LISsrlOxs7hyIs9d/4HawW2SBsSv1/LDuubaYZazBVZGey67NGy02fVH1hbC2Nc
HXAbo6yjcuxpr+WvLUoKNFB53OUOnG77QM3qAKDN/zopZL7FgE4=
=A5r0
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: