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

Bug#647028: marked as done (lintian: warn when changelog contains UNRELEASED even if .changes contains something valid)

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 lintian: warn when changelog contains UNRELEASED even if .changes contains something valid
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.5.3
Severity: wishlist

I build my package with sbuild and it writes the Distribution
field in the .changes according to the parameter given on the command
line.

I recently had the case that I have left UNRELEASED in debian/changelog
and built my package with sbuild and lintian did not warn me.

I'm not sure what the proper solution is. Ideally it would detect the
mismatch beween the .changes and the changelog in the source package but
I guess it's not easy.

-- System Information:
Debian Release: wheezy/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (150, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lintian depends on:
ii  binutils                       2.21.90.20111025-1 
ii  bzip2                          1.0.5-7            
ii  diffstat                       1.54-1             
ii  file                           5.09-2             
ii  gettext                        0.18.1.1-5         
ii  intltool-debian                0.35.0+20060710.1  
ii  libapt-pkg-perl                0.1.25             
ii  libclass-accessor-perl         0.34-1             
ii  libdpkg-perl                   1.16.2~49.gbp8cc36f
ii  libemail-valid-perl            0.185-1            
ii  libipc-run-perl                0.90-1             
ii  libparse-debianchangelog-perl  1.2.0-1            
ii  libtimedate-perl               1.2000-1           
ii  liburi-perl                    1.59-1             
ii  locales                        2.13-21            
ii  locales-all [locales]          2.13-21            
ii  man-db                         2.6.0.2-2          
ii  patchutils                     0.3.2-1            
ii  perl [libdigest-sha-perl]      5.12.4-6           
ii  unzip                          6.0-5              

lintian recommends no packages.

Versions of packages lintian suggests:
ii  binutils-multiarch     <none>               
ii  dpkg-dev               1.16.2~49.gbp8cc36f  
ii  libhtml-parser-perl    3.69-1               
ii  libtext-template-perl  1.45-2               
ii  man-db                 2.6.0.2-2            
ii  xz-utils               5.1.1alpha+20110809-3

-- 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: