Bug#1076489: src:developers-reference: fails to migrate to testing for too long: autopkgtest regression

2024-07-16 Thread Paul Gevers
Source: developers-reference Version: 13.6 Severity: serious Control: close -1 13.7 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30

Bug#1039102: debian-policy: make systemd units mandatory for packages shipping system services

2024-04-07 Thread Paul Gevers
Hi, On Sat, 09 Sep 2023 18:51:52 -0700 Russ Allbery wrote: """ +``systemd`` uses dependency and ordering information contained within the ++enabled unit files to decide which services to run and in which order. """ ^ is that "+" before "enabled" really intended? It looks weird to me. Paul

Bug#944920: Revise terminology used to specify requirements

2019-12-10 Thread Paul Gevers
Dear Policy Editors, On 21-11-2019 13:59, Paul Gevers wrote: > [Disclaimer: the words below are as a member of the release team, but > not necessarily those of the team. We haven't discussed this yet.] We have had a discussion, and there were no objections against my vision below. &

Bug#944920: Revise terminology used to specify requirements

2019-11-21 Thread Paul Gevers
Dear Russ, [Disclaimer: the words below are as a member of the release team, but not necessarily those of the team. We haven't discussed this yet.] On 17-11-2019 20:47, Russ Allbery wrote: > Let me copy the release team. How would you all prefer to handle the > relationship between

Bug#880920: Document Rules-Requires-Root field

2018-06-15 Thread Paul Gevers
h -- thanks! Thanks. I think this is easier to read. > On Fri, Jun 15 2018, Paul Gevers wrote: > >> Hi Sean, >> >> On 15-06-18 14:43, Sean Whitton wrote: >>> On Thu, Jun 14 2018, Paul Gevers wrote: >>> >>>>> + - A space separated list o

Bug#880920: Document Rules-Requires-Root field

2018-06-15 Thread Paul Gevers
Hi Sean, On 15-06-18 14:43, Sean Whitton wrote: > On Thu, Jun 14 2018, Paul Gevers wrote: > >>> + - A space separated list of keywords described below. These must insert "keywords" here? ^ >>> + always contain a fo

Bug#880920: Document Rules-Requires-Root field

2018-06-14 Thread Paul Gevers
I want to second this text, but have some questions. > diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst > index 0771346..3519d99 100644 > --- a/policy/ch-controlfields.rst > +++ b/policy/ch-controlfields.rst > @@ -1020,6 +1022,118 @@ This field is automatically added to

Bug#891216: seconded 891216: Requre d-devel consultation for epoch bump

2018-06-13 Thread Paul Gevers
I second the diff below. Paul diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst index 0771346..166cdd8 100644 --- a/policy/ch-controlfields.rst +++ b/policy/ch-controlfields.rst @@ -552,9 +552,10 @@ The three components here are: omitted, in which case zero is assumed.

Bug#845255: debian-policy: Include best practices for packaging database applications

2017-08-07 Thread Paul Gevers
Hi, As promised, I send the converted dbapp-policy documentation to this bug. Credits go to Osamu, any bug is mine. Paul http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd; [ ]> Best practices for packaging database applications Sean Finney This draft describes a set of

Bug#845255: debian-policy: Include best practices for packaging database applications

2017-07-24 Thread Paul Gevers
Hi Mathias, On 23-07-17 18:25, Mathias Behrle wrote: > As the bug title says, those recommendations are best practices and for me > there > is no need to put them into policy. There is lots of best practices in policy. It is written as "xyz *should* abc". > There can always be good reasons to

Bug#845255: Inclusion of best practices for packaging database applications in Debian policy

2017-06-25 Thread Paul Gevers
Hi Debian developers, This e-mail is meant for maintainers of applications that use databases and for those of you that are interested in how packages should handle those. In bug 845255ยน I started the discussion for inclusion of the "best practices for packaging database applications" in the

Bug#845255: debian-policy: Include best practices for packaging database applications

2017-05-29 Thread Paul Gevers
Hi all, I hate to ping bugs, but is there anything I can do to help this move forward? (The policy 4.0.0 release reminded me of this bug). On Mon, 21 Nov 2016 21:17:55 +0100 Paul Gevers <elb...@debian.org> wrote: > It has been a while since the first version of the "

Bug#845255: debian-policy: Include best practices for packaging database applications

2016-11-21 Thread Paul Gevers
Package: debian-policy Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 It has been a while since the first version of the "Best practices for packaging database applications" was drafted by Sean Finney as the creator of dbconfig-common. The discussion on the document has died

Re: package versions with snapshots/branch updates

2016-05-30 Thread Paul Gevers
Hi, On 30-05-16 09:42, Rene Engelhard wrote: > On Sun, May 29, 2016 at 12:40:32PM +0500, Andrey Rahmatullin wrote: >> On Sun, May 29, 2016 at 12:00:28AM +0200, Rene Engelhard wrote: > e.g. if you have a package 1.0 and add a complete branch update as a patch > (or upgrade to a snapshot)

Bug#679562: developers-reference: note that it is possible for Release Team to override urgency

2012-07-07 Thread Paul Gevers
On 05-07-12 01:58, Charles Plessy wrote: thank for your patience. I think that the patch you sent nicely enhances the chapter 5.13. Thanks. On the typograhy side, it is very minor, but since you added a bullet point to the list in 5.13.2, you can make the now previous bullet point finish by

Bug#679562: developers-reference: note that it is possible for Release Team to override urgency

2012-07-04 Thread Paul Gevers
On 02-07-12 02:52, Charles Plessy wrote: I just read through the section 5.13 again (The testing distribution). I see that details about britney are given in 5.13.2.5. I agree that this is a better place. Also, it would not be completely consistent to describe in 5.13.2 how to use the

Bug#679562: developers-reference: note that it is possible for Release Team to override urgency

2012-07-01 Thread Paul Gevers
On 29-06-12 23:14, Martin Zobel-Helas wrote: Hi, you either want to install aspell, or you might want to contact debian-l10-english for a review of your patch. I am sorry for this stupid mistake. Please find a new patch attached. Paul Index: pkgs.dbk

Bug#679562: developers-reference: note that it is possible for Release Team to override urgency

2012-07-01 Thread Paul Gevers
+transitions may be switched off altogether. The Debian Release team can override +the urgency; I am not sure what is meant by overriding the urgency. The Release team can directly control the migration time for a package, but this is not exactly done by replacing the urgency by another

Bug#679562: developers-reference: note that it is possible for Release Team to override urgency

2012-06-29 Thread Paul Gevers
Package: developers-reference Version: 3.4.8 Severity: wishlist Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 During the NM process my AM and I discovered that it is not documented that the Release team can override the urgency of a package. I informed with the Release team how to