Your message dated Wed, 12 Feb 2014 07:42:30 -0500
with message-id <[email protected]>
and subject line Re: Bug#738706: New default urgency of medium makes
apt-listchanges less useful
has caused the Debian Bug report #738706,
regarding New default urgency of medium makes apt-listchanges less useful
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 [email protected]
immediately.)
--
738706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738706
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: devscripts
Version: 2.13.5
Severity: normal
Hi,
I notice that the default urgency of new uploads is 'medium' as opposed to
'low', due to #730343.
Unfortunately, this makes apt-listchanges less useful than it has been so
far.
apt-listchanges is run by apt before upgrading packages. It displays the
changes in the packages to be upgraded by extracting Debian changelog
entries that are more recent than the installed versions of the affected
packages. The list is ordered so that changelogs for packages that had any
critical urgency upload come first, followed by packages with at least one
upload of urgency 'high', then 'medium', then 'low'.
So far I often only read the first part of the list, down to 'medium'
urgency upgrades; 'low' urgency stuff could generally be safely ignored.
With the new default, it can be expected that many maintainers will not
bother updating the urgency to 'low', so that trivial things like manpage
typo fixes will wind up being uploaded with an urgency of 'medium',
polluting the apt-listchanges output.
Was changing the default urgency really the best way of solving whatever
problem it was meant to solve? (I confess I don't understand the issue
reported in #730343.)
Andras
--
Windows 98 supports true multitasking: it can boot and crash simultaneously.
--- End Message ---
--- Begin Message ---
On Wed, Feb 12, 2014 at 09:59:26AM +0100, Andras Korn wrote:
> With the new default, it can be expected that many maintainers will not
> bother updating the urgency to 'low', so that trivial things like manpage
> typo fixes will wind up being uploaded with an urgency of 'medium',
> polluting the apt-listchanges output.
The release team decided[0] that "it should be acceptable for most
uploads to unstable to be uploaded with medium urgency, to reduce the
delay for testing migrations."
[0]: http://lists.debian.org/[email protected]
Your example is exactly the kind of thing that doesn't need to age in
unstable before migrating to testing. If the maintainer is making
changes that could use more run time before migration, they can set the
urgency to low.
> Was changing the default urgency really the best way of solving whatever
> problem it was meant to solve? (I confess I don't understand the issue
> reported in #730343.)
You would have to talk to the release team about that. We simply
adjusted dch's behavior to be inline with what they were requesting.
Cheers,
--
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <[email protected]>
signature.asc
Description: Digital signature
--- End Message ---
_______________________________________________
devscripts-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/devscripts-devel
