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

Bug#542747: marked as done ([checks/changes-file] check mismatch between Distribution and Changes in *.changes)

Your message dated Tue, 3 Apr 2018 23:34:39 +0100
with message-id <20180403223439.GA6408@espresso.pseudorandom.co.uk>
and subject line Re: Bug#542747: [frontend] check mismatch between Distribution and Changes in *.changes
has caused the Debian Bug report #542747,
regarding [checks/changes-file] check mismatch between Distribution and Changes in *.changes
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.)


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

While we can't easily check for mismatches between the *.changes file
and the debian/changelog file in the source package, the latter is
copied into *.changes as the Changes field.  We can therefore check
whether the distribution in the first line of the Changes field matches
the Distribution.

I think we only want to do this check if the first line of the Changes
file says UNRELEASED, since there are valid use cases for a mismatch
otherwise.  But in the UNRELEASED case, that means that someone forgot
to update debian/changelog and only modified what went into the
Distribution header, which deserves a tag.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686-bigmem (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lintian depends on:
ii  binutils              2.19.51.20090723-1 The GNU assembler, linker and bina
ii  diffstat              1.47-1             produces graph of changes introduc
ii  dpkg-dev              1.15.3.1           Debian package development tools
ii  file                  5.03-1             Determines file type using "magic"
ii  gettext               0.17-6             GNU Internationalization utilities
ii  intltool-debian       0.35.0+20060710.1  Help i18n of RFC822 compliant conf
ii  libapt-pkg-perl       0.1.24             Perl interface to libapt-pkg
ii  libipc-run-perl       0.84-1             Perl module for running processes
ii  libparse-debianchange 1.1.1-2            parse Debian changelogs and output
ii  libtimedate-perl      1.1600-9           Time and date functions for Perl
ii  liburi-perl           1.37+dfsg-1        Manipulates and accesses URI strin
ii  man-db                2.5.5-3            on-line manual pager
ii  perl [libdigest-sha-p 5.10.0-24          Larry Wall's Practical Extraction 

lintian recommends no packages.

Versions of packages lintian suggests:
pn  binutils-multiarch            <none>     (no description available)
ii  libtext-template-perl         1.45-1     Text::Template perl module
ii  man-db                        2.5.5-3    on-line manual pager

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 2.5.51

On Thu, 23 Feb 2017 at 13:44:07 +0000, Simon McVittie wrote:
> On Thu, 20 Aug 2009 at 23:07:38 -0700, Russ Allbery wrote:
> > While we can't easily check for mismatches between the *.changes file
> > and the debian/changelog file in the source package, the latter is
> > copied into *.changes as the Changes field.  We can therefore check
> > whether the distribution in the first line of the Changes field matches
> > the Distribution.
> 
> This has come up on -devel again, which reminded me that this didn't get
> merged.

It was merged a few months later, in June 2017 (but unfortunately
mislabelled as closing Bug #540294 - I'm not sure where that bug number
came from, it seems to have been my mistake).

    smcv

--- End Message ---
Reply to: