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

Bug#540852: marked as done (Describe use of 'urgency' (other than in the context of a security fix))

Your message dated Fri, 13 Jul 2018 10:05:01 +0000
with message-id <E1fduwf-000HGh-G7@fasolo.debian.org>
and subject line Bug#540852: fixed in developers-reference 3.4.20
has caused the Debian Bug report #540852,
regarding Describe use of 'urgency' (other than in the context of a security fix)
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.)


-- 
540852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540852
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: developers-reference
Version: 3.4.1
Severity: normal

I was recently trying to learn how to select correct values for the
"urgency" field in debian/control for a package. I found that Debian
Policy describes legal values for this field, (low, medium, high,
emergency, or critical), but no real guidance on how to choose one of
the fields. And perhaps that's correct since the usage isn't a matter
of policy.

So I looked to the Developer's Reference for documentation on how to
set this field, and failed to find it, (later Enrico Zini pointed out
that I missed section "5.8.5.4. Preparing packages to address security
issues" which does mention "* The upload should have urgency=high.").

But for other than security issues, no guidance is provided.

Finally, I found a mailing list post that does provide some guidance:

http://article.gmane.org/gmane.linux.debian.devel.mentors/29417

This recommends using low for normal stuff (with a 10-day transition
to testing), medium for release-critical issues (with a 5-day
transition), and high for security fixes (a 2-day transition).

Would it make sense to add a section to Developer's Reference with
these details? Perhaps a new subsection under "6.2. Best practices for
debian/control"?

If so, let me know and perhaps I can prepare a patch for this.

Thanks,

-Carl

--- End Message ---
--- Begin Message --- 
Source: developers-reference
Source-Version: 3.4.20

We believe that the bug you reported is fixed in the latest version of
developers-reference, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 540852@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Raphaël Hertzog <hertzog@debian.org> (supplier of updated developers-reference package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 13 Jul 2018 11:23:40 +0200
Source: developers-reference
Binary: developers-reference developers-reference-de developers-reference-fr developers-reference-ja developers-reference-ru developers-reference-it
Architecture: source
Version: 3.4.20
Distribution: unstable
Urgency: medium
Maintainer: Developers Reference Maintainers <debian-policy@lists.debian.org>
Changed-By: Raphaël Hertzog <hertzog@debian.org>
Description:
 developers-reference - guidelines and information for Debian developers
 developers-reference-de - guidelines and information for Debian developers, in German
 developers-reference-fr - guidelines and information for Debian developers, in French
 developers-reference-it - guidelines and information for Debian developers, in Italian
 developers-reference-ja - guidelines and information for Debian developers, in Japanese
 developers-reference-ru - guidelines and information for Debian developers, in Russian
Closes: 540852 544135 604193 773544 774837 798106 834070 874291 878033 883742 888978 896191
Changes:
 developers-reference (3.4.20) unstable; urgency=medium
 .
   [ Raphaël Hertzog ]
   * Team upload.
   * Reduce the large package tracker section to a few small paragraphs
     pointing to the real documentation hosted on
     https://qa.pages.debian.net/distro-tracker/
   * Apply typo/rewording patch from Paul Hardy. Closes: #878033
   * Update IRC channel list with better examples. Closes: #773544
   * Be more specific in the recommendation to use gender-neutral
     constructions. Thanks to Johannes Schauer <j.schauer@email.de>
     for the initial patch. Closes: #774837
   * Bump the minimal size of the GPG key to 2018 bits and put link
     to keyring.debian.org. Closes: #798106
   * Recommend using "which" to test availability of a command.
     Thanks to Axel Beckert for the patch. Closes: #883742
   * Point out that a non-working email is a policy violation. Improve
     MIA explanations. Closes: #604193, #544135
     Thanks to Caitlin Matos for the patch.
   * Replace some backticks with normal quotes in japanese translation
     to fix a build failure with LaTeX 2018. Closes: #896191
     Thanks to Hilmar Preuße for the patch.
   * Simplify generation of PUBDATE by relying on SOURCE_DATE_EPOCH.
   * Drop Marc 'HE' Brockschmidt <he@debian.org> from Uploaders.
 .
   [ Ansgar Burchardt ]
   * security uploads should go to *.security.upload.d.o (closes: #874291)
 .
   [ Julien Cristau ]
   * Update Vcs-* control fields.
   * Fix upload host name (ssh.upload.debian.org, not ssh.debian.org);
     closes: #888978.  Thanks, Thorsten Alteholz!
 .
   [ Sean Whitton ]
   * Include link to Riseup's "OpenPGP Best Practices" (closes: #834070)
   * Add section "Selecting the upload urgency" to best-pkging-practices
     (Closes: #540852).
 .
   [ Aurélien COUDERC ]
   * Fix CSS text color to avoid the HTML version being unreadable when
     using a light on dark default browser stylesheet.
   * d/control: Bump Standards-Version to 4.1.5, no change needed.
Checksums-Sha1:
 ac0259aeb579d2b642fcadef0564f6b45b85a56c 2091 developers-reference_3.4.20.dsc
 92f88160a7ea832cf57a14d6d289739cca721c27 657112 developers-reference_3.4.20.tar.xz
 36282caa7e00761e861c6544737dcae079c58a4a 6037 developers-reference_3.4.20_source.buildinfo
Checksums-Sha256:
 da7a75f91f9e8a2769483676da6d3a3dcee2423d0dbe550b47076db74993a37b 2091 developers-reference_3.4.20.dsc
 50518eabe0627b301624129da698e8b8688c0300f8cf708a817ddd1a3be7582d 657112 developers-reference_3.4.20.tar.xz
 59921cf0ebfc005821010fb130be36c52578bb46cc9440d4189e724fead4b5ec 6037 developers-reference_3.4.20_source.buildinfo
Files:
 ff251472824f335d82bbbe9b87523edf 2091 doc optional developers-reference_3.4.20.dsc
 aaaa86b0147307f960caeffd5d824a7c 657112 doc optional developers-reference_3.4.20.tar.xz
 ec817eec4c2f50ae1f01f41464db9418 6037 doc optional developers-reference_3.4.20_source.buildinfo

-----BEGIN PGP SIGNATURE-----
Comment: Signed by Raphael Hertzog

iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAltIc8YACgkQA4gdq+vC
mrmSMggAov/gFn6QOu1Kl/ASQMKYCRvdmSV0e+3ISLh7K5jrWNL/LpW9BfE7m8Vg
/goPD8VgscZyKylvGGieq9JSJQlZXzs8WeD5yHBpF3IuKVmX7lY9Dia1r2Y11Hhp
0cXrfL1hP985CWcfjHIfi4sosLGMsSj9qbs+Krinq+4Vu7T5ZRt0hoHSPP6oiHfn
m84AJq7HyEUG4WhY9WQfTs4nl2W02izTg+HV4NGMgrw+P7x+h6DBg7xfs/8jAvte
PmEEadqxlxbHrIydLTd4c8ygOELhtFRFX7P5u2MpOajxapO9E61hKc0JeGMW9ZUu
YdN959zjqEL5/FuxLJMYNpjm0HEOVQ==
=w4G9
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: