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

Bug#729379: marked as done (O: ruby-mp3info -- a pure ruby library for access to mp3 files)

Your message dated Tue, 24 Dec 2013 11:34:34 +0000
with message-id <E1VvQFu-0002DR-6c@franck.debian.org>
and subject line Bug#732850: Removed package(s) from unstable
has caused the Debian Bug report #729379,
regarding O: ruby-mp3info -- a pure ruby library for access to mp3 files
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.)


-- 
729379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729379
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: normal

The current maintainer of ruby-mp3info, Gustavo Franco <stratus@debian.org>,
is retiring.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
http://www.debian.org/devel/wnpp/index.html#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: ruby-mp3info
Binary: libmp3info-ruby1.8
Version: 0.5-2
Maintainer: Gustavo Franco <stratus@debian.org>
Build-Depends: debhelper (>> 4.0.0), ruby
Architecture: all
Standards-Version: 3.6.2.1
Format: 1.0
Files:
 760f9ef722c9e7968cd16e20de1f6246 592 ruby-mp3info_0.5-2.dsc
 0dec5c7144d9a432f48314e9c46bf600 19614 ruby-mp3info_0.5.orig.tar.gz
 5ef924f67e4601c94915d463d5b10cb2 1714 ruby-mp3info_0.5-2.diff.gz
Checksums-Sha1:
 3dc14971a073ef8cece32f1e97df492f499ed906 592 ruby-mp3info_0.5-2.dsc
 4a5b92965c51613b8f46f7440ee040d87ef0c947 1714 ruby-mp3info_0.5-2.diff.gz
 562b6437b4629f77903c5cd755474a931ba47cc0 19614 ruby-mp3info_0.5.orig.tar.gz
Checksums-Sha256:
 5ffe42cb3b7cd5bb22b82947b979b06b8b974cb71a10456eecd2e1b931d927b7 592 ruby-mp3info_0.5-2.dsc
 41136fbc5c08d23cfe5742d296fed8fe90d4de339afae2582d9ac796b8204255 1714 ruby-mp3info_0.5-2.diff.gz
 03e672f9f296df7d8cb7a3a2d663bb2135e04951541be846ea3505ae7b274179 19614 ruby-mp3info_0.5.orig.tar.gz
Directory: pool/main/r/ruby-mp3info
Priority: source
Section: ruby

Package: libmp3info-ruby1.8
Source: ruby-mp3info
Version: 0.5-2
Installed-Size: 48
Maintainer: Gustavo Franco <stratus@debian.org>
Architecture: all
Depends: libruby1.8
Description-en: a pure ruby library for access to mp3 files
 libmp3info-ruby gives you access to low level informations on mp3
 files (bitrate, length, samplerate, etc...) using ruby programming
 language. It can read, write, remove id3v1 tag and read id3v2.
Description-md5: b4482fe8ea225448207e8ef1bf796d36
Tag: devel::lang:ruby
Section: ruby
Priority: optional
Filename: pool/main/r/ruby-mp3info/libmp3info-ruby1.8_0.5-2_all.deb
Size: 14644
MD5sum: e7b155e7f42d4e507fd5e283e06b0d94
SHA1: 1e51a3b66a01688928e873ece93ed8062fbe9cfe
SHA256: 61d12e8434a04960b42dd79632a15148bc40070eb7097ff4e7843844f0fe6b46

--- End Message ---
--- Begin Message --- 
Version: 0.5-2+rm

Dear submitter,

as the package ruby-mp3info has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see http://bugs.debian.org/732850

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)

--- End Message ---
Reply to: