[DRE-maint] ruby-health-check 2.6.0-1 MIGRATED to testing

FYI: The status of the ruby-health-check source package in Debian's testing distribution has changed. Previous version: 2.4.0-1 Current version: 2.6.0-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you

[DRE-maint] ruby-rack-attack 4.4.1-1 MIGRATED to testing

FYI: The status of the ruby-rack-attack source package in Debian's testing distribution has changed. Previous version: 4.3.1-1 Current version: 4.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

[DRE-maint] bundler 1.15.1-1 MIGRATED to testing

FYI: The status of the bundler source package in Debian's testing distribution has changed. Previous version: 1.13.6-2 Current version: 1.15.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] Bug#867643: Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")

On 08/07/17 at 19:37 +0200, Georg Faerber wrote: > Hi, > > Unfortunately, I can't reproduce this locally. Besides the sbuild > options used which are shown in the log file, is there a .sbuildrc in > place, with non-default options? If so, could you share it? Have you tried diffing your log with

[DRE-maint] Bug#867647: marked as done (ruby-rest-client: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: return http.request(req, body, ))

Your message dated Sat, 8 Jul 2017 21:34:01 +0200 with message-id <20170708193401.om6iklu6vqlib...@xanadu.blop.info> and subject line has caused the Debian Bug report #867647, regarding ruby-rest-client: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: return http.request(req, body, ) to be

[DRE-maint] ruby-rest-client_2.0.2-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 08 Jul 2017 20:31:17 +0200 Source: ruby-rest-client Binary: ruby-rest-client Architecture: source Version: 2.0.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] Processing of ruby-rest-client_2.0.2-1_source.changes

ruby-rest-client_2.0.2-1_source.changes uploaded successfully to localhost along with the files: ruby-rest-client_2.0.2-1.dsc ruby-rest-client_2.0.2.orig.tar.gz ruby-rest-client_2.0.2-1.debian.tar.xz ruby-rest-client_2.0.2-1_source.buildinfo Greetings, Your Debian queue daemon

[DRE-maint] ruby-json-jwt_1.7.2-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 08 Jul 2017 23:56:28 +0530 Source: ruby-json-jwt Binary: ruby-json-jwt Architecture: source Version: 1.7.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] Processing of ruby-json-jwt_1.7.2-1_source.changes

ruby-json-jwt_1.7.2-1_source.changes uploaded successfully to localhost along with the files: ruby-json-jwt_1.7.2-1.dsc ruby-json-jwt_1.7.2.orig.tar.gz ruby-json-jwt_1.7.2-1.debian.tar.xz ruby-json-jwt_1.7.2-1_source.buildinfo Greetings, Your Debian queue daemon (running on host

[DRE-maint] Bug#867643: Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")

Hi, Unfortunately, I can't reproduce this locally. Besides the sbuild options used which are shown in the log file, is there a .sbuildrc in place, with non-default options? If so, could you share it? Additionally, I've got a question regarding the network configuration of the VM on which the

[DRE-maint] ruby-mocha_1.2.1-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 06 Jul 2017 23:56:21 +0200 Source: ruby-mocha Binary: ruby-mocha ruby-mocha-doc Architecture: source Version: 1.2.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] ruby-net-ssh-multi_1.2.1-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 08 Jul 2017 17:02:05 +0200 Source: ruby-net-ssh-multi Binary: ruby-net-ssh-multi Architecture: source Version: 1.2.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] Processing of ruby-mocha_1.2.1-1_source.changes

ruby-mocha_1.2.1-1_source.changes uploaded successfully to localhost along with the files: ruby-mocha_1.2.1-1.dsc ruby-mocha_1.2.1.orig.tar.gz ruby-mocha_1.2.1-1.debian.tar.xz ruby-mocha_1.2.1-1_source.buildinfo Greetings, Your Debian queue daemon (running on host

[DRE-maint] Processing of ruby-net-ssh-multi_1.2.1-3_source.changes

ruby-net-ssh-multi_1.2.1-3_source.changes uploaded successfully to localhost along with the files: ruby-net-ssh-multi_1.2.1-3.dsc ruby-net-ssh-multi_1.2.1-3.debian.tar.xz ruby-net-ssh-multi_1.2.1-3_source.buildinfo Greetings, Your Debian queue daemon (running on host

[DRE-maint] ruby-jbuilder_2.3.1-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 08 Jul 2017 16:38:09 +0200 Source: ruby-jbuilder Binary: ruby-jbuilder Architecture: source Version: 2.3.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] Processing of ruby-jbuilder_2.3.1-2_source.changes

ruby-jbuilder_2.3.1-2_source.changes uploaded successfully to localhost along with the files: ruby-jbuilder_2.3.1-2.dsc ruby-jbuilder_2.3.1-2.debian.tar.xz ruby-jbuilder_2.3.1-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

[DRE-maint] Bug#867643: Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")

On 08/07/17 at 12:16 +0200, Georg Faerber wrote: > Hi Lucas, > > Thanks for the report: > > On 17-07-08 08:28:30, Lucas Nussbaum wrote: > > > > [...] > > > > About the archive rebuild: The rebuild was done on EC2 VM instances > > from Amazon Web Services, using a clean, minimal and up-to-date >

[DRE-maint] Processed: Re: Bug#867533: test failure when updating to 3.9.0

Processing control commands: > retitle -1 update ruby-parser to latest upstream release Bug #867533 [ruby-parser] test failure when updating to 3.9.0 Changed Bug title to 'update ruby-parser to latest upstream release' from 'test failure when updating to 3.9.0'. -- 867533:

[DRE-maint] Bug#867533: test failure when updating to 3.9.0

Control: retitle -1 update ruby-parser to latest upstream release On 07/08/2017 07:20 PM, Antonio Terceiro wrote: > It would sound better, yes. "the version in the archive is not recent > enough" is an issue with a package that is in debian; "this new version > that is not in the archive does not

[DRE-maint] Processed: user debian...@lists.debian.org, usertagging 865572, found 865572 in 0.3.3-1, found 865572 in 0.7.3-2 ...

Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 865572 piuparts There were no usertags set. Usertags are now: piuparts. > found 865572 0.3.3-1 Bug #865572 [ruby-autoparse,ruby-signet]

[DRE-maint] Processed: Re: Bug#867599: gem2deb fails to install pure ruby part when a gem has both pure ruby and native libs

Processing control commands: > severity -1 wishlist Bug #867599 [gem2deb] gem2deb fails to install pure ruby part when a gem has both pure ruby and native libs Severity set to 'wishlist' from 'normal' > retitle -1 gem2deb: support installing Ruby code not in lib/ Bug #867599 [gem2deb] gem2deb

[DRE-maint] Bug#867599: gem2deb fails to install pure ruby part when a gem has both pure ruby and native libs

Control: severity -1 wishlist Control: retitle -1 gem2deb: support installing Ruby code not in lib/ On Sat, Jul 08, 2017 at 01:48:19PM +0530, Pirate Praveen wrote: > On 07/08/2017 11:53 AM, Pirate Praveen wrote: > > On 07/08/2017 07:44 AM, Antonio Terceiro wrote: > >> if the pure ruby libraries

[DRE-maint] Bug#867533: test failure when updating to 3.9.0

On Sat, Jul 08, 2017 at 11:59:00AM +0530, Pirate Praveen wrote: > On 07/08/2017 07:47 AM, Antonio Terceiro wrote: > > > > This seems wrong. If you get a failure after trying to update the > > package to 3.9.0, by definition the bug cannot be against version 3.8.2 > > (which does not exist in

[DRE-maint] Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 867031 confirmed Bug #867031 [schleuder] schleuder: fails to upgrade wheezy -> jessie -> stretch -> buster Added tag(s) confirmed. > End of message, stopping processing here. Please contact me if you need assistance. -- 867031:

[DRE-maint] Bug#867643: Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")

Hi Lucas, Thanks for the report: On 17-07-08 08:28:30, Lucas Nussbaum wrote: > > [...] > > About the archive rebuild: The rebuild was done on EC2 VM instances > from Amazon Web Services, using a clean, minimal and up-to-date > chroot. Every failed build was retried once to eliminate random >

[DRE-maint] Bug#867599: gem2deb fails to install pure ruby part when a gem has both pure ruby and native libs

On 07/08/2017 01:48 PM, Pirate Praveen wrote: > On 07/08/2017 11:53 AM, Pirate Praveen wrote: >> On 07/08/2017 07:44 AM, Antonio Terceiro wrote: >>> if the pure ruby libraries were not being installed, you would get a >>> LoadError (i.e. a `require` statement failed), but that's not what is >>>

[DRE-maint] Bug#867599: gem2deb fails to install pure ruby part when a gem has both pure ruby and native libs

On 07/08/2017 11:53 AM, Pirate Praveen wrote: > On 07/08/2017 07:44 AM, Antonio Terceiro wrote: >> if the pure ruby libraries were not being installed, you would get a >> LoadError (i.e. a `require` statement failed), but that's not what is >> happening here. > For tests, the pure ruby libs are

[DRE-maint] Bug#865133: marked as done (ruby-redcarpet FTBFS on 32bit: Failure: test_utf8_only_header_anchors(HTMLRenderTest))

Your message dated Sat, 08 Jul 2017 07:50:37 + with message-id and subject line Bug#865133: fixed in ruby-redcarpet 3.4.0-2 has caused the Debian Bug report #865133, regarding ruby-redcarpet FTBFS on 32bit: Failure:

[DRE-maint] ruby-redcarpet_3.4.0-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 08 Jul 2017 09:25:10 +0200 Source: ruby-redcarpet Binary: ruby-redcarpet Architecture: source Version: 3.4.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] Processing of ruby-redcarpet_3.4.0-2_source.changes

ruby-redcarpet_3.4.0-2_source.changes uploaded successfully to localhost along with the files: ruby-redcarpet_3.4.0-2.dsc ruby-redcarpet_3.4.0-2.debian.tar.xz ruby-redcarpet_3.4.0-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

[DRE-maint] Processed: Bug#865133 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 865133 pending Bug #865133 [src:ruby-redcarpet] ruby-redcarpet FTBFS on 32bit: Failure: test_utf8_only_header_anchors(HTMLRenderTest) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. --

[DRE-maint] Processed: fix found versions

Processing commands for cont...@bugs.debian.org: > notfound 867533 3.8.2 Bug #867533 [ruby-parser] test failure when updating to 3.9.0 There is no source info for the package 'ruby-parser' at version '3.8.2' with architecture '' Unable to make a source version for version '3.8.2' No longer

[DRE-maint] Bug#867654: ruby-omniauth-crowd: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: http.request(req)

Source: ruby-omniauth-crowd Version: 2.2.3-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): >

[DRE-maint] Bug#867655: ruby-gemnasium-gitlab-service: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: @connection.request(request)

Source: ruby-gemnasium-gitlab-service Version: 0.2.6-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part

[DRE-maint] Bug#867533: test failure when updating to 3.9.0

On 07/08/2017 07:47 AM, Antonio Terceiro wrote: > > This seems wrong. If you get a failure after trying to update the > package to 3.9.0, by definition the bug cannot be against version 3.8.2 > (which does not exist in Debian BTW, you missed the Debian revision > number). > > IMO the BTS should be

[DRE-maint] Bug#867656: ruby-mixlib-install: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: res = http.request(request)

Source: ruby-mixlib-install Version: 1.1.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): >

[DRE-maint] Bug#867653: ruby-license-finder: FTBFS: ERROR: Test "ruby2.3" failed: /etc/ssl/certs/T?RKTRUST_Elektronik_Sertifika_Hizmet_Sa?lay?c?s?_H5.pem (No such file or directory)

Source: ruby-license-finder Version: 2.1.2-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): >

[DRE-maint] Bug#867650: berkshelf: FTBFS: ERROR: Test "ruby2.3" failed: Did you mean? Berkshelf::NullFormatter (NameError)

Source: berkshelf Version: 4.3.5-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Did you

[DRE-maint] Bug#867651: ruby-rubymail: FTBFS: ERROR: Test "ruby2.3" failed.

Source: ruby-rubymail Version: 1.1.0-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): >

[DRE-maint] Bug#867647: ruby-rest-client: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: return http.request(req, body, )

Source: ruby-rest-client Version: 1.8.0-3 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): >

[DRE-maint] Bug#867644: ruby-puppet-syntax: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output[2]).to match('Found 2 errors. Giving up')

Source: ruby-puppet-syntax Version: 2.2.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): >

[DRE-maint] Bug#867645: ruby-influxdb: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: http.request(req)

Source: ruby-influxdb Version: 0.2.3-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): >

[DRE-maint] Bug#867646: gist: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: http.request request

Source: gist Version: 4.5.0-3 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): >

[DRE-maint] Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")

Source: schleuder Version: 3.1.1-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): >

[DRE-maint] Bug#867649: ruby-flowdock: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: resp = self.class.delete(api_url(path), :basic_auth => {:username => @api_token, :password => ''}, :headers =

Source: ruby-flowdock Version: 0.7.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): >

[DRE-maint] Bug#867642: capistrano: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(out).to match(/\bCapistrano Version\b/)

Source: capistrano Version: 3.4.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170707 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): >