[DRE-maint] Bug#853753: gitlab-shell: fails after update - git auth ?

I have the same issue remote: GitLab: The project you were looking for could not be found. using http://snapshot.debian.org/archive/debian/20161031T154133Z/pool/main/g/gitlab-shell/gitlab-shell_3.6.6-1_all.deb Fixes the issue, but breaks apt You might want to run 'apt --fix-broken install'

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

Your message dated Thu, 2 Feb 2017 22:43:46 +0100 with message-id <20170202214346.ga25...@percival.namespace.at> and subject line Re: ruby-em-synchrony: FTBFS: mysql_install_db: [ERROR] unknown option '--force' has caused the Debian Bug report #841586, regarding ruby-em-synchrony: FTBFS:

[DRE-maint] Bug#853251: gitlab: git push fail - GitLab: API is not accessible

I can confirm that this bug affects our production servers as well. Unfortunately the suggested temporary fix (commenting out) doesn't seem to work. This might be because we are setting our DB to postgres in the gitlab-debian.conf. Regards, Emmanuel On Mon, 30 Jan 2017 12:50:21 -0700 "Justin F.

[DRE-maint] Bug#843474: ruby-ethon: FTBFS: [BUG] Segmentation fault at 0x007f2767e0d800

Control: severity -1 normal Control: tags -1 + unreproducible moreinfo > ruby-ethon fails to build from source in unstable/amd64: Builds for me just fine in sbuild (multiple builds). More info needed. Best, -ch ___ Pkg-ruby-extras-maintainers mailing

[DRE-maint] Processed: Re: Bug#843474: ruby-ethon: FTBFS: [BUG] Segmentation fault at 0x007f2767e0d800

Processing control commands: > severity -1 normal Bug #843474 [src:ruby-ethon] ruby-ethon: FTBFS: [BUG] Segmentation fault at 0x007f2767e0d800 Severity set to 'normal' from 'serious' > tags -1 + unreproducible moreinfo Bug #843474 [src:ruby-ethon] ruby-ethon: FTBFS: [BUG] Segmentation fault at

[DRE-maint] Processed: retitle 841586 to ruby-em-synchrony: FTBFS: mysql_install_db: [ERROR] unknown option '--force'

Processing commands for cont...@bugs.debian.org: > retitle 841586 ruby-em-synchrony: FTBFS: mysql_install_db: [ERROR] unknown > option '--force' Bug #841586 [src:ruby-em-synchrony] ruby-em-synchrony: FTBFS: ERROR: Test "ruby2.3" failed: Invalid gemspec in [em-synchrony.gemspec]: No such file or

[DRE-maint] Bug#843474: marked as done (ruby-ethon: FTBFS: [BUG] Segmentation fault at 0x007f2767e0d800)

Your message dated Fri, 03 Feb 2017 11:47:36 +1300 with message-id <1486075656.549803.868609728.78dc2...@webmail.messagingengine.com> and subject line Re: Bug#843474: ruby-ethon: FTBFS: [BUG] Segmentation fault at 0x007f2767e0d800 has caused the Debian Bug report #843474, regarding ruby-ethon:

[DRE-maint] Bug#843474: ruby-ethon: FTBFS: [BUG] Segmentation fault at 0x007f2767e0d800

Christian Hofstaedtler wrote: > Control: severity -1 normal > Control: tags -1 + unreproducible moreinfo > > > ruby-ethon fails to build from source in unstable/amd64: > > Builds for me just fine in sbuild (multiple builds). More info needed. Same here; closing in BCC. Regards, --

[DRE-maint] Processing of ruby-gir-ffi_0.11.1-1_amd64.changes

ruby-gir-ffi_0.11.1-1_amd64.changes uploaded successfully to localhost along with the files: ruby-gir-ffi_0.11.1-1.dsc ruby-gir-ffi_0.11.1.orig.tar.gz ruby-gir-ffi_0.11.1-1.debian.tar.xz ruby-gir-ffi_0.11.1-1_all.deb ruby-gir-ffi_0.11.1-1_amd64.buildinfo Greetings, Your Debian

[DRE-maint] ruby-gir-ffi_0.11.1-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 Feb 2017 18:38:36 +0900 Source: ruby-gir-ffi Binary: ruby-gir-ffi Architecture: source all Version: 0.11.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] Bug#853962: vagrant-mutate: completely broken

Package: vagrant-mutate Version: 1.2.0-2 Severity: grave Justification: renders package unusable $ vagrant mutate ubuntu/trusty64 libvirt /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:184:in `rescue in load_yml': can not load translations from /usr/lib/ruby/locales/en.yml: #

[DRE-maint] Processing of vagrant-mutate_1.2.0-3_source.changes

vagrant-mutate_1.2.0-3_source.changes uploaded successfully to localhost along with the files: vagrant-mutate_1.2.0-3.dsc vagrant-mutate_1.2.0-3.debian.tar.xz vagrant-mutate_1.2.0-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

[DRE-maint] Bug#853962: marked as done (vagrant-mutate: completely broken)

Your message dated Thu, 02 Feb 2017 16:33:33 + with message-id and subject line Bug#853962: fixed in vagrant-mutate 1.2.0-3 has caused the Debian Bug report #853962, regarding vagrant-mutate: completely broken to be marked as done. This means that you

[DRE-maint] vagrant-mutate_1.2.0-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 Feb 2017 11:47:08 -0200 Source: vagrant-mutate Binary: vagrant-mutate Architecture: source Version: 1.2.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] ruby-eventmachine 1.0.7-4 MIGRATED to testing

FYI: The status of the ruby-eventmachine source package in Debian's testing distribution has changed. Previous version: 1.0.7-3 Current version: 1.0.7-4 -- 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-http 1.0.2-4 MIGRATED to testing

FYI: The status of the ruby-http source package in Debian's testing distribution has changed. Previous version: 1.0.2-3 Current version: 1.0.2-4 -- 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-minitar 0.5.4-3.1 MIGRATED to testing

FYI: The status of the ruby-minitar source package in Debian's testing distribution has changed. Previous version: 0.5.4-3 Current version: 0.5.4-3.1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will