[DRE-maint] Bug#892183: ruby-rbpdf: FTBFS and Debci failure with Ruby 2.5

2018-08-31 Thread Hashem Nasarat
I made some good progress with packaging a new version of ruby-rbpdf: https://salsa.debian.org/hnasarat-guest/ruby-rbpdf/network/master Now to find a sponsor? ___ Pkg-ruby-extras-maintainers mailing list

[DRE-maint] Bug#892183:

2018-08-31 Thread Hashem Nasarat
I packaged a new version which fixes this bug and also addressed some other small issues kanashiro on irc mentioned that they'd help me with sponsorship, but just for documentation, here's the package out for review. https://mentors.debian.net/package/ruby-rbpdf

[DRE-maint] diaspora-installer 0.7.4.0+nmu1 MIGRATED to testing

2018-08-31 Thread Debian testing watch
FYI: The status of the diaspora-installer source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 0.7.4.0+nmu1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple

[DRE-maint] roodi is marked for autoremoval from testing

2018-08-31 Thread Debian testing autoremoval watch
roodi 5.0.0-1 is marked for autoremoval from testing on 2018-09-22 It is affected by these RC bugs: 907149: roodi: FTBFS in buster/sid FTBFS in buster/sid (failing tests) ___ Pkg-ruby-extras-maintainers mailing list

[DRE-maint] ruby-json-jwt_1.6.2-1+deb9u1_amd64.changes ACCEPTED into proposed-updates->stable-new

2018-08-31 Thread Debian FTP Masters
Mapping stable-security to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 18 Aug 2018 23:32:06 +0530 Source: ruby-json-jwt Binary: ruby-json-jwt Architecture: source all Version: 1.6.2-1+deb9u1 Distribution: stretch-security Urgency: medium

[DRE-maint] Processing of ruby-cairo_1.15.14-1_amd64.changes

2018-08-31 Thread Debian FTP Masters
ruby-cairo_1.15.14-1_amd64.changes uploaded successfully to localhost along with the files: ruby-cairo_1.15.14-1.dsc ruby-cairo_1.15.14.orig.tar.gz ruby-cairo_1.15.14-1.debian.tar.xz ruby-cairo-dbgsym_1.15.14-1_amd64.deb ruby-cairo_1.15.14-1_amd64.buildinfo

[DRE-maint] ruby-cairo_1.15.14-1_amd64.changes ACCEPTED into unstable

2018-08-31 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 31 Aug 2018 18:41:32 +0900 Source: ruby-cairo Binary: ruby-cairo Architecture: source amd64 Version: 1.15.14-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By:

[DRE-maint] ruby-rugged_0.27.4+ds-1~bpo9+1_amd64.changes ACCEPTED into stretch-backports, stretch-backports

2018-08-31 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 21 Aug 2018 17:12:14 +0530 Source: ruby-rugged Binary: ruby-rugged Architecture: source amd64 Version: 0.27.4+ds-1~bpo9+1 Distribution: stretch-backports Urgency: medium Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] ruby-sanitize_4.6.6-1~bpo9+1_amd64.changes ACCEPTED into stretch-backports, stretch-backports

2018-08-31 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 25 Aug 2018 10:44:46 +0530 Source: ruby-sanitize Binary: ruby-sanitize Architecture: source all Version: 4.6.6-1~bpo9+1 Distribution: stretch-backports Urgency: medium Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] Processing of ruby-gollum-rugged-adapter_0.4.4.1-2~bpo9+1_amd64.changes

2018-08-31 Thread Debian FTP Masters
ruby-gollum-rugged-adapter_0.4.4.1-2~bpo9+1_amd64.changes uploaded successfully to localhost along with the files: ruby-gollum-rugged-adapter_0.4.4.1-2~bpo9+1.dsc ruby-gollum-rugged-adapter_0.4.4.1.orig.tar.gz ruby-gollum-rugged-adapter_0.4.4.1-2~bpo9+1.debian.tar.xz

[DRE-maint] ruby-gollum-rugged-adapter_0.4.4.1-2~bpo9+1_amd64.changes is NEW

2018-08-31 Thread Debian FTP Masters
binary:ruby-gollum-rugged-adapter is NEW. binary:ruby-gollum-rugged-adapter is NEW. source:ruby-gollum-rugged-adapter 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