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

Bug#890142: marked as done (debian-policy: Please provide a backport of the package)

Your message dated Mon, 12 Feb 2018 07:30:44 -0700
with message-id <87h8qmi8kr.fsf@iris.silentflame.com>
and subject line Re: Bug#890142: Acknowledgement (debian-policy: Please provide a backport of the package)
has caused the Debian Bug report #890142,
regarding debian-policy: Please provide a backport of the package
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.)


-- 
890142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890142
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: debian-policy
Version: 4.1.3.0
Severity: wishlist


Hello

The machines I use to develop Debian run stable, with unstable
schroots/pbuilders.

While I can configure /etc/apt/preferences to install debian-policy
from unstable (and I've done it for every previous machine I had) it
will be a lot cleaner just to install the package from backports.

debian-policy has only one dependency and it is present in stable.

I've never done a backport myself, but if you policy folks don't see any
problem with the idea I'm willing to do the backport myself.

thanks!

--- End Message ---
--- Begin Message --- 
Hello,

On Mon, Feb 12 2018, gustavo panizzo wrote:

> Sorry for the noise policy folks, I'll use
>
> curl
>https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt |
>less
>
>
> for the time being
>
> After Buster is released I'll start to provide the backport, I think
> is better to spend my Debian time doing something else than
> backporting sphinx

Let's close this bug, then.

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: