Bug#855650: marked as done (is it worth trying to unblock slimit/0.8.1-2 ?)
Your message dated Tue, 21 Feb 2017 19:58:02 +0100
with message-id <20170221185802.dgfdh23ld2c6dtov@betterave.cristau.org>
and subject line Re: Bug#855650: is it worth truing to unblock slimit/0.8.1-2 ?
has caused the Debian Bug report #855650,
regarding is it worth trying to unblock slimit/0.8.1-2 ?
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.)
--
855650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855650
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
Hello Release Team,
reading the RC bugs against DPMT, i noticed the one[1] against slimit: i think
there was a "naive" upload[2] already in the deep freeze, which started to
provide a py3k package (something i think is really interesting to have for
stretch).
That upload sadly introduced [1], so what i would like to know from you is: is
it worth spending time to fix [1]? will you accept an unblock with the
(hypotetic) -3 release when -2 contains some major changes you might not want to
see in stretch?
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855510
[2] https://packages.qa.debian.org/s/slimit/news/20170208T070018Z.html
thanks for considering,
Sandro
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Mon, Feb 20, 2017 at 16:58:20 -0500, Sandro Tosi wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: unblock
>
> Hello Release Team,
> reading the RC bugs against DPMT, i noticed the one[1] against slimit: i think
> there was a "naive" upload[2] already in the deep freeze, which started to
> provide a py3k package (something i think is really interesting to have for
> stretch).
>
> That upload sadly introduced [1], so what i would like to know from you is: is
> it worth spending time to fix [1]? will you accept an unblock with the
> (hypotetic) -3 release when -2 contains some major changes you might not want to
> see in stretch?
>
No, sorry.
Cheers,
Julien
--- End Message ---
Reply to: