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

Bug#462589: marked as done (Description doesn't make sense (and dpkg no longer generates it) for source-only *.changes files)

Your message dated Thu, 20 Mar 2008 20:50:02 -0700
with message-id <87skykwxat.fsf@windlord.stanford.edu>
and subject line Re: Bug#462589: Description doesn't make sense (and dpkg no longer generates it) for source-only *.changes files
has caused the Debian Bug report #462589,
regarding Description doesn't make sense (and dpkg no longer generates it) for source-only *.changes files
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.)


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

Hi,

since dpkg-dev is moving quite quickly these days, I postponed its
upgrade, and only hit today the following:
| E: graphviz_2.16.1-1_source.changes: no-description-in-changes-file

Since dpkg/1.14.16, we have:
| * Some code refactoring on dpkg-genchanges and bug fixes in the generation
|   of the Description: field. As a result, source only uploads will no more
|   have Description fields.

I presume it'dbe safe to turn off this check when checking a source-only
upload (if you don't detect source-only uploads yet, I guess that the
/_source.changes$/ pattern should do the job.

Cheers,

-- 
Cyril Brulebois

--- End Message ---
--- Begin Message --- 
Raphael Hertzog <hertzog@debian.org> writes:

> Note that we have had several reports of things that failed following
> that change (and I was thinking that Description fields in .changes were
> almost not used...) and thus we decided to revert the behaviour for the
> upcoming 1.14.17 and we know include descriptions of all packages in any
> case.
>
> mentors.debian.net uses it for example to show a short description of
> any package uploaded for review/sponsoring. It also broke something in
> Ubuntu.

In that case, it sounds like we should just close this Policy bug and not
change Policy, and dpkg will be changed to match again.  Doing so now.
Thanks!

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

--- End Message ---
Reply to: