Your message dated Wed, 01 Jan 2014 17:24:10 +0000
with message-id <[email protected]>
and subject line Bug#722375: Removed package(s) from unstable
has caused the Debian Bug report #722375,
regarding RM: posixlock
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 [email protected]
immediately.)
--
722375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722375
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libposixlock-ruby
Severity: normal
Usertags: ruby18-removal, update-ruby-policy
Hi Tomas Pospisek,
As you may know, during the Wheezy release cycle, the pkg-ruby-extras
team¹ has worked to update the Ruby libraries/modules/gems packages to
follow a new policy, much easier for the maintainers (as we no longer
require a separate package for each interpreter version), to the
archive (as it strongly reduces code duplication), and much more
sensical to the users (as they no longer require to fiddle with which
among many almost-identical binary packages to install).
While we achieved a quite good success level during the Wheezy cycle²,
we decided to act only on the packages maintained by the group — There
are many Ruby library packages maintained by kind people (like
yourself!) which have not yet adopted this new style. According to our
records, you are currently maintaining the package:
libposixlock-ruby
I am sending this report as part of a mass-bug-filing.³ Some useful
information you might find useful:
• Guidelines for Ruby packaging⁴
https://wiki.debian.org/Teams/Ruby/Packaging#Guidelines_for_Ruby_packaging
• Ruby team release goals for Jessie⁵
https://wiki.debian.org/Teams/Ruby/Jessie
• About the Ruby team — Please consider joining!⁶
https://wiki.debian.org/Teams/Ruby
• Part of the new policy involves running the package's tests. Here is
a swift introduction on what it means and how to do it:
https://wiki.debian.org/Teams/Ruby/Packaging/Tests
Thanks a lot for your attention!
--
¹ alioth.debian.org/projects/pkg-ruby-extras/
² http://pkg-ruby-extras.alioth.debian.org/wheezy/
³ https://lists.debian.org/debian-devel/2013/09/msg00196.html
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
libposixlock-ruby | 0.0.1-2 | all
libposixlock-ruby1.8 | 0.0.1-2 | amd64, armel, armhf, hurd-i386, i386, ia64,
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x, sparc
posixlock | 0.0.1-2 | source
------------------- Reason -------------------
RoM/RoQA; FTBFS with ruby 1.9.1; unmaintained upstream
----------------------------------------------
Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it). Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors (ftp.debian.org
included) until the next dinstall run at the earliest.
Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.
We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected].
The full log for this bug can be viewed at http://bugs.debian.org/722375
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)
--- End Message ---
