[DRE-maint] Processing of ruby-jwt_0.1.8-1_amd64.changes

2013-10-14 Thread Debian FTP Masters
ruby-jwt_0.1.8-1_amd64.changes uploaded successfully to localhost along with the files: ruby-jwt_0.1.8-1.dsc ruby-jwt_0.1.8.orig.tar.gz ruby-jwt_0.1.8-1.debian.tar.gz ruby-jwt_0.1.8-1_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org)

[DRE-maint] Processing of ruby-gelf_1.4.0-2_amd64.changes

2013-10-14 Thread Debian FTP Masters
ruby-gelf_1.4.0-2_amd64.changes uploaded successfully to localhost along with the files: ruby-gelf_1.4.0-2.dsc ruby-gelf_1.4.0-2.debian.tar.gz ruby-gelf_1.4.0-2_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org)

[DRE-maint] ruby-gelf_1.4.0-2_amd64.changes ACCEPTED into unstable

2013-10-14 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 12 Oct 2013 20:57:25 +0200 Source: ruby-gelf Binary: ruby-gelf Architecture: source all Version: 1.4.0-2 Distribution: unstable Urgency: low Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] Bug#720224: marked as done (ruby-gelf: FTBFS with ruby2.0: ERROR: Test ruby2.0 failed.)

2013-10-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2013 09:34:01 + with message-id e1vvexj-0001vf...@franck.debian.org and subject line Bug#720224: fixed in ruby-gelf 1.4.0-2 has caused the Debian Bug report #720224, regarding ruby-gelf: FTBFS with ruby2.0: ERROR: Test ruby2.0 failed. to be marked as done. This

[DRE-maint] [Bug 1239686] [NEW] Internal error while trying to login in Redmine 2.3.1-1

2013-10-14 Thread Anton Statutov
Public bug reported: 1) OS: Ubuntu 13.10 2) Package: redmine 2.3.1-1 3) What's expected: I'm authorized. 4) What's happened: Internal error and 'NoMethodError' error (see attachment) ** Affects: redmine (Ubuntu) Importance: Undecided Status: Confirmed ** Attachment added: Error

[DRE-maint] [Bug 1239686] Re: Internal error while trying to login in Redmine 2.3.1-1

2013-10-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: redmine (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239686 Title: Internal error while trying to login

[DRE-maint] ruby-bourne 1.5.0-1 MIGRATED to testing

2013-10-14 Thread Debian testing watch
FYI: The status of the ruby-bourne source package in Debian's testing distribution has changed. Previous version: 1.4.0-1 Current version: 1.5.0-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

[DRE-maint] ruby-crack 0.4.1-1 MIGRATED to testing

2013-10-14 Thread Debian testing watch
FYI: The status of the ruby-crack source package in Debian's testing distribution has changed. Previous version: 0.3.2-1 Current version: 0.4.1-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

[DRE-maint] yard 0.8.7.2-1 MIGRATED to testing

2013-10-14 Thread Debian testing watch
FYI: The status of the yard source package in Debian's testing distribution has changed. Previous version: 0.8.6.1-1 Current version: 0.8.7.2-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

[DRE-maint] Bug#725672: apt-listbugs: version 0.1.10 fails to dowload bugs from the BTS

2013-10-14 Thread Adam Majer
Package: ruby-soap4r Version: 2.0.5-2 Followup-For: Bug #725672 irb(main):001:0 require 'xsd/xmlparser/libxmlparser' NameError: uninitialized constant XML::SaxParser from /usr/lib/ruby/vendor_ruby/xsd/xmlparser/libxmlparser.rb:18:in `class:LibXMLParser' from

Re: [DRE-maint] Bug#722375: Updating the Ruby packaging policy for your package «libposixlock-ruby»

2013-10-14 Thread Gunnar Wolf
Tomas Pospisek dijo [Fri, Oct 11, 2013 at 03:46:32PM +0200]: according to popcon there are a few user using the package. I don't know if the number there is statistically relevant - or in other words if those users really *are* using the package. If we leave the package in Debian as is, then