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

Bug#430354: marked as done (lintian: Please support historical changelogs)

Your message dated Sat, 10 Jan 2009 20:16:59 -0800
with message-id <87wsd2zdc4.fsf@windlord.stanford.edu>
and subject line Re: Bug#430354: lintian: Please support historical changelogs
has caused the Debian Bug report #430354,
regarding lintian: Please support historical changelogs
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.)


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

Hi,

The dhcp3 source package has one malformed (by current standards)
changelog entry (the very first one). I learned at Debconf, that the
format wasn't always defined, so I'm assuming this entry is from that
era.

It'd be nice not to get Lintian complaints about it.

regards

Andrew

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)

Versions of packages lintian depends on:
ii  binutils               2.17-3            The GNU assembler, linker and bina
ii  diffstat               1.43-2            produces graph of changes introduc
ii  dpkg-dev               1.13.25           package building tools for Debian
ii  file                   4.17-5etch1       Determines file type using "magic"
ii  gettext                0.16.1-1          GNU Internationalization utilities
ii  intltool-debian        0.35.0+20060710.1 Help i18n of RFC822 compliant conf
ii  libparse-debianchangel 1.0-1             parse Debian changelogs and output
ii  man-db                 2.4.3-6           The on-line manual pager
ii  perl [libdigest-md5-pe 5.8.8-7           Larry Wall's Practical Extraction 

lintian recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Frank Lichtenheld <djpig@debian.org> writes:
> On Sun, Jul 01, 2007 at 10:01:01AM -0700, Russ Allbery wrote:
>> Andrew Pollock <apollock@debian.org> writes:

>>> The dhcp3 source package has one malformed (by current standards)
>>> changelog entry (the very first one). I learned at Debconf, that the
>>> format wasn't always defined, so I'm assuming this entry is from that
>>> era.  It'd be nice not to get Lintian complaints about it.

>> This is somewhat difficult to fix just because of how changelog
>> checking is implemented, but it also raises questions of how far back
>> lintian should check and when it should start ignoring problems.  I'm
>> guessing that changing this may require changes to the Perl module we
>> use to parse changelogs as well.

> FWIW, Parse::DebianChangelog tries to identify the start of old legacy
> entries and stops parsing there. In this case however there is really no
> sign whatsoever that the format might change.

I reviewed this bug as part of a Lintian bug cleanup again, and I'm going
to go ahead and close it.  We've had it tagged as wontfix for a little
while based on Frank's feedback on Parse::DebianChangelog's attempts to
discover a transition to an older format, and Policy by my reading doesn't
actually make any allowances for historic changelog formats even in old
entries.

I'm certainly sympathetic to your desire to keep history as-is (although
in this case I think I'd personally just make up some trailer lines), but
if you want to keep the changelog file as-is, I think this is an
appropriate use of an override.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>

--- End Message ---
Reply to: