[DRE-maint] Bug#812897: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: ruby-sidetiq |0.6.3-5 | source, all --- Reason --- ROM; Package is no longer maintained by upstream and does not work with latest version of it's

[DRE-maint] ruby-pathname2 1.7.4-1 MIGRATED to testing

FYI: The status of the ruby-pathname2 source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 1.7.4-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day

[DRE-maint] ruby-hashdiff 0.2.3-1 MIGRATED to testing

FYI: The status of the ruby-hashdiff source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 0.2.3-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day

[DRE-maint] ruby-css-parser 1.3.6-1 MIGRATED to testing

FYI: The status of the ruby-css-parser source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 1.3.6-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a

[DRE-maint] ruby-rpam-ruby19 1.2.1-1 MIGRATED to testing

FYI: The status of the ruby-rpam-ruby19 source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 1.2.1-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a

[DRE-maint] ruby-minitar 0.5.4-3 MIGRATED to testing

FYI: The status of the ruby-minitar source package in Debian's testing distribution has changed. Previous version: 0.5.4-2 Current version: 0.5.4-3 -- 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] Processing of ruby-sentry-raven_0.15.3-1_amd64.changes

ruby-sentry-raven_0.15.3-1_amd64.changes uploaded successfully to localhost along with the files: ruby-sentry-raven_0.15.3-1.dsc ruby-sentry-raven_0.15.3.orig.tar.gz ruby-sentry-raven_0.15.3-1.debian.tar.xz ruby-sentry-raven_0.15.3-1_all.deb Greetings, Your Debian queue daemon

[DRE-maint] ruby-sentry-raven_0.15.3-1_amd64.changes REJECTED

Hi, raven-ruby-0.15.3/lib/raven/okjson.rb is not licensed under Apache-2 Thanks! Thorsten === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.

[DRE-maint] ruby-sentry-raven_0.15.3-1_amd64.changes is NEW

binary:ruby-sentry-raven is NEW. source:ruby-sentry-raven is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are

Re: [DRE-maint] ruby-sentry-raven_0.15.3-1_amd64.changes is NEW

On 2016, ജനുവരി 30 9:24:55 PM IST, Debian FTP Masters wrote: >binary:ruby-sentry-raven is NEW. >source:ruby-sentry-raven is NEW. > >Your package has been put into the NEW queue, which requires manual >action >from the ftpteam to process. The upload was

[DRE-maint] Bug#813271: diaspora-installer: fails to install: post-installation script returned error exit status 127

Package: diaspora-installer Version: 0.5.3.0+debian1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the

[DRE-maint] Bug#813265: ruby-bcat: postrm called with unknown argument `upgrade'

Package: ruby-bcat Version: 0.6.2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed the maintainer scripts of your package don't support all the ways they are going to be called. See policy 6.5 at