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

Bug#765405: marked as done (RM: stud/0.3-6)

Your message dated Tue, 14 Oct 2014 21:04:30 +0200
with message-id <m3a94ylbgh.fsf@neo.luffy.cx>
and subject line Re: Bug#765405: RM: stud/0.3-6
has caused the Debian Bug report #765405,
regarding RM: stud/0.3-6
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.)


-- 
765405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765405
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: rm

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi!

Please, remove stud from testing. It is dead upstream since quite some
time and has a low popcon. Moreover, it has maintained replacements
like stunnel and haproxy available in the archive.

Request of removal from unstable has just been filed.

Thanks!

- -- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJUPXD9AAoJEJWkL+g1NSX5rzYP/itK9Q93rStPv3A2oBOzBbTi
8LrOoo9ORcbeh5Sn3+mnv4WVvvI39OvMH3/4qATZphi5XENwFPEw/koN3VrNAiba
Xjzvk44SLuZ0JwZd3RBbXgerPnmFvv960hPA/UGn+eM9GqDnwAzrrEfSqrxq1Wke
ymIuHOeEvIdkaBe+eHcN2qIhtCNZVGR1wwUygCmWRpGgr8megdjzGyLoxTS9qDKB
b1T+S5iDiDuXSHIYrbu6DP/f6re6Q+iYGbz5cR2+HzPVFZMGCjA0bi9B/5USfTdJ
kocxNIKN3cyzD4/zkHIiJnpd4zD5iy65GY5/050HoXuDSzCFEOQwPdUuyt6gBOmh
CA6jLeK6H+bQFAOG1mWUClq4sVGbeLU+N7wPlNHWD0z3pMncao0L4d4s2vO7dcYT
4AvSWw4hhhl/KQbE4bWP2u+rTeZty+Qf3G/rncFIhKrTFgBzM6//2Uh5RHkfIQSy
6a1YVO/Zk352Zc5/VYlXEjmPHmTQa5yij8XIplfR/MDa1pmsjFSz2qaLxjW6hSk5
U/IwZgXZ5BLbYrkLwub0FvG467H1WAoWOhPZnKsiUehIquMh8EgeF4fIiY/jVjX+
yCNsJUvDE5Zg57lLU3HOAeYjEBluiL2UMSe7AFoWwyMmmsbXQRcskYWt3U0JxT+h
+bbbwa+ktrUqxbaFEjMe
=UG5P
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
 ❦ 14 octobre 2014 19:58 +0100, "Adam D. Barratt" <adam@adam-barratt.org.uk> :

>> Please, remove stud from testing. It is dead upstream since quite some
>> time and has a low popcon. Moreover, it has maintained replacements
>> like stunnel and haproxy available in the archive.
>> 
>> Request of removal from unstable has just been filed.
>
> Is there a particular urgency to the removal from testing? In the
> absence of an RC bug blocking it, the package in unstable will simply
> become a candidate for re-migration after removal.
>
> otoh, once the removal from unstable is actioned by ftp-master it will
> automatically propagate to testing.

No, no urgency. For some reason, I thought that removal from testing
need to be asked separately to the release team. Let's close the bug.
-- 
Format a program to help the reader understand it.
            - The Elements of Programming Style (Kernighan & Plauger)

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: