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

Bug#491585: marked as done (lintian does not complain on UNRELEASED in the changelog)

Your message dated Sun, 20 Jul 2008 22:37:19 +0200
with message-id <20080720203719.GT11882@mail-vs.djpig.de>
and subject line Re: Bug#491585: lintian does not complain on UNRELEASED in the changelog
has caused the Debian Bug report #491585,
regarding lintian does not complain on UNRELEASED in the changelog
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.)


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

  Hello,

  lintian does not complain anymore on a distribution UNRELEASED in
the changelog, see:

19:35 vincent@tanyaivinco ~/packages/result lintian stormbaancoureur_2.1.5-2.1_amd64.changes    
W: stormbaancoureur-data: debian-copyright-line-too-long line 4
W: stormbaancoureur: debian-copyright-line-too-long line 4
19:35 vincent@tanyaivinco ~/packages/result cat stormbaancoureur_2.1.5-2.1_amd64.changes | grep Distribution
Distribution: UNRELEASED

  This definitely was detected before - and I came to rely upon it. I'm unable
to check if it applies only to this particular build or if it is more
general. In any case, it is painful.

  I keep the files around in case you need them, but I can't attach
them all, they are too big.

  Regards,

	Vincent

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) (ignored: LC_ALL set to en_GB)
Shell: /bin/sh linked to /bin/dash

Versions of packages lintian depends on:
ii  binutils            2.18.1~cvs20080103-7 The GNU assembler, linker and bina
ii  diffstat            1.45-2               produces graph of changes introduc
ii  dpkg-dev            1.14.20              Debian package development tools
ii  file                4.25-1               Determines file type using "magic"
ii  gettext             0.17-3               GNU Internationalization utilities
ii  intltool-debian     0.35.0+20060710.1    Help i18n of RFC822 compliant conf
ii  libparse-debianchan 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.35.dfsg.1-1        Manipulates and accesses URI strin
ii  man-db              2.5.2-2              on-line manual pager
ii  perl [libdigest-sha 5.10.0-11.1          Larry Wall's Practical Extraction 

lintian recommends no packages.

Versions of packages lintian suggests:
pn  binutils-multiarch            <none>     (no description available)
pn  libtext-template-perl         <none>     (no description available)
ii  man-db                        2.5.2-2    on-line manual pager

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Sun, Jul 20, 2008 at 09:12:11PM +0200, Vincent Fourmond wrote:
> Adam D. Barratt wrote:
> > Vincent Fourmond wrote:
> >>  lintian does not complain anymore on a distribution UNRELEASED in
> >> the changelog, see:
> > This is intentional; from 1.23.49's changelog:
> > * frontend/lintian:
> >     + [FL] Don't issue a warning about Distribution: UNRELEASED in
> >       .changes files.  It can be annoying to have to ignore this error
> >       during testing and dupload/dput/dak/etc... all will error out
> >       on it anyway.  Suggested by martin f krafft.  (Closes: #382327)
> 
>   Sorry for the noise, I should have checked the changelog first. What
> should be done of this bug ? close or wontfix ?

Let's close it. If it comes up again we can reconsider.

Gruesse,
-- 
Frank Lichtenheld <djpig@debian.org>
www: http://www.djpig.de/

--- End Message ---
Reply to: