[DRE-maint] Bug#845169: marked as done (ruby-carrierwave: FTBFS in testing (unknown option '--initialize-insecure'))

Your message dated Tue, 29 Nov 2016 09:52:33 +0530 with message-id and subject line disabled in 0.10.0+gh-4 has caused the Debian Bug report #845169, regarding ruby-carrierwave: FTBFS in testing (unknown option '--initialize-insecure') to be

[DRE-maint] Processed: fixed by disabling tests

Processing commands for cont...@bugs.debian.org: > fixed 845169 0.10.0+gh-4 Bug #845169 [src:ruby-carrierwave] ruby-carrierwave: FTBFS in testing (unknown option '--initialize-insecure') Marked as fixed in versions ruby-carrierwave/0.10.0+gh-4. > End of message, stopping processing here. Please

[DRE-maint] Bug#846180: gitlab not restarted after redis-server upgrade

Package: gitlab Version: 8.13.6+dfsg1-2 Severity: normal Dear Maintainer, I just installed an upgraded version of redis-server (but not of gitlab itself), and after the upgrade gitlab was no longer running. The following reproduces this easily for me: $ for i in "" -mailroom -sidekiq

[DRE-maint] Bug#846179: gitlab: Use notify on ready under systemd instead of hack with sleep + check commandline

Package: gitlab Version: 8.13.6+dfsg1-2 Severity: normal Dear Maintainer, The current systemd service file for gitlab-sidekiq contains a hack to delay the systemd service startup until sidekiq is actually ready by sleeping for up to 32 seconds (in increments of 4 seconds) until sidekiq's

[DRE-maint] Bug#841133: ruby-gruff: FTBFS: Tests hang after segmentation fault

Package: ruby-gruff Version: 0.6.0-1 Followup-For: Bug #841133 This bug does not only happen at build time, it makes Gruff completely unusable :-( $ irb >> require 'gruff' => true >> g=Gruff::Bar.new '100x100' /usr/lib/ruby/vendor_ruby/gruff/base.rb:968: [BUG] Segmentation fault at

[DRE-maint] Bug#845169: ruby-carrierwave: FTBFS in testing (unknown option '--initialize-insecure')

Hi, On Tue, 29 Nov 2016 00:42:00 +0530 Pirate Praveen wrote: > On Mon, 21 Nov 2016 00:42:58 + Santiago Vila wrote: > > Maybe some build-depends needs to be versioned? > > It was building fine with mysql-5.7 in unstable, this version is not yet >

[DRE-maint] ruby-json-pure_2.0.2+dfsg-1_amd64.changes is NEW

binary:ruby-json-pure is NEW. binary:ruby-json-pure is NEW. source:ruby-json-pure 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

[DRE-maint] Processing of ruby-json-pure_2.0.2+dfsg-1_amd64.changes

ruby-json-pure_2.0.2+dfsg-1_amd64.changes uploaded successfully to localhost along with the files: ruby-json-pure_2.0.2+dfsg-1.dsc ruby-json-pure_2.0.2+dfsg.orig.tar.gz ruby-json-pure_2.0.2+dfsg-1.debian.tar.xz ruby-json-pure_2.0.2+dfsg-1_all.deb

[DRE-maint] Bug#841543: marked as done (ruby-carrierwave: FTBFS: mysql_install_db: [ERROR] unknown option '--force')

Your message dated Mon, 28 Nov 2016 19:49:48 + with message-id and subject line Bug#841543: fixed in ruby-carrierwave 0.10.0+gh-4 has caused the Debian Bug report #841543, regarding ruby-carrierwave: FTBFS: mysql_install_db: [ERROR] unknown option

[DRE-maint] ruby-carrierwave_0.10.0+gh-4_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Nov 2016 00:44:06 +0530 Source: ruby-carrierwave Binary: ruby-carrierwave Architecture: source Version: 0.10.0+gh-4 Distribution: unstable Urgency: high Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] Processing of ruby-carrierwave_0.10.0+gh-4_source.changes

ruby-carrierwave_0.10.0+gh-4_source.changes uploaded successfully to localhost along with the files: ruby-carrierwave_0.10.0+gh-4.dsc ruby-carrierwave_0.10.0+gh-4.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

[DRE-maint] Bug#845169: ruby-carrierwave: FTBFS in testing (unknown option '--initialize-insecure')

On Mon, 21 Nov 2016 00:42:58 + Santiago Vila wrote: > Maybe some build-depends needs to be versioned? It was building fine with mysql-5.7 in unstable, this version is not yet migrated to testing. I think I will disable the tests until mysql-5.7 can enter testing. These

[DRE-maint] Bug#845656: marked as done (autopkgtest failure: rspec ./spec/finders/labels_finder_spec.rb:34 # LabelsFinder#execute with no filter returns labels from projects the user have access)

Your message dated Mon, 28 Nov 2016 19:03:45 + with message-id and subject line Bug#845656: fixed in gitlab 8.13.6+dfsg1-3 has caused the Debian Bug report #845656, regarding autopkgtest failure: rspec ./spec/finders/labels_finder_spec.rb:34 #

[DRE-maint] gitlab_8.13.6+dfsg1-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 28 Nov 2016 23:52:13 +0530 Source: gitlab Binary: gitlab Architecture: source Version: 8.13.6+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] Processing of gitlab_8.13.6+dfsg1-3_source.changes

gitlab_8.13.6+dfsg1-3_source.changes uploaded successfully to localhost along with the files: gitlab_8.13.6+dfsg1-3.dsc gitlab_8.13.6+dfsg1-3.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) ___

[DRE-maint] Bug#846151: gem2deb: doesn't handle DFSG re-packed upstream tar file version

Package: gem2deb Version: 0.32 Severity: normal Hello, I have an upstream source that has a non-DFSG IETF licensed RFC in it. I downloaded the tar and repacked it to remove that file. Then I ran gem2deb on it, but it failed because I renamed the tar to have +dfsg: micah@muck:new$

[DRE-maint] ruby-gnome2 3.1.0-1 MIGRATED to testing

FYI: The status of the ruby-gnome2 source package in Debian's testing distribution has changed. Previous version: 3.0.9-2 Current version: 3.1.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-handlebars-assets 2:0.23.1-1 MIGRATED to testing

FYI: The status of the ruby-handlebars-assets source package in Debian's testing distribution has changed. Previous version: 2:0.23.0-3 Current version: 2:0.23.1-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times

[DRE-maint] ruby-dbus 0.13.0-1 MIGRATED to testing

FYI: The status of the ruby-dbus source package in Debian's testing distribution has changed. Previous version: 0.11.0-1 Current version: 0.13.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] Bug#846115: jekyll: FTBFS randomly (failing tests)

Package: src:jekyll Version: 3.1.6+dfsg-3 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed:

[DRE-maint] Bug#846083: autopkgtest fails HandlebarsAssets::HandlebarsProcessorTest#test_render

package: ruby-handlebars-assets version: 1:0.23.1-1 severity: important RUBYLIB=. GEM_PATH= ruby2.3 -S rake -f debian/ruby-tests.rake Run options: --seed 29929 # Running: ..F. Finished in 10.527074s, 2.6598 runs/s, 4.7497 assertions/s. 1) Failure:

[DRE-maint] ruby-rpam-ruby19_1.2.1-1~bpo8+1_amd64.changes ACCEPTED into jessie-backports, jessie-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 23 Nov 2016 11:10:32 +0100 Source: ruby-rpam-ruby19 Binary: ruby-rpam-ruby19 Architecture: source amd64 Version: 1.2.1-1~bpo8+1 Distribution: jessie-backports Urgency: medium Maintainer: Debian Ruby Extras

[DRE-maint] Bug#846052: passenger-config/status cannot find instance registry

Package: passenger Version: 5.0.30-1 Severity: normal Dear Maintainer, I have just upgraded to passenger 5, and now I want to restart my application the 'new' way by using passenger-config. I have tried this both through capistrano, and on the command line, and I get the following error message: