[DRE-maint] Bug#894272: Gitlab: Bug#894272: Some problems fixed.

On April 1, 2018 5:24:05 AM GMT+05:30, "David López Zajara" wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA256 > > >Hi, > >After latest updates (Including gitlab-workhorse), login page are >working >now. > >I've recovered the old database and repositories now.

[DRE-maint] Accepted ruby-mail-gpg 0.3.3-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 01 Apr 2018 17:33:01 +0200 Source: ruby-mail-gpg Binary: ruby-mail-gpg Architecture: source Version: 0.3.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] ruby-mail-gpg_0.3.3-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 01 Apr 2018 17:33:01 +0200 Source: ruby-mail-gpg Binary: ruby-mail-gpg Architecture: source Version: 0.3.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] Processing of ruby-mail-gpg_0.3.3-1_source.changes

ruby-mail-gpg_0.3.3-1_source.changes uploaded successfully to localhost along with the files: ruby-mail-gpg_0.3.3-1.dsc ruby-mail-gpg_0.3.3.orig.tar.gz ruby-mail-gpg_0.3.3.orig.tar.gz.asc ruby-mail-gpg_0.3.3-1.debian.tar.xz ruby-mail-gpg_0.3.3-1_amd64.buildinfo Greetings, Your

[DRE-maint] Bug#881773: ruby2.5: FTBFS on hppa: recursive once test fails

On Sat, Mar 31, 2018 at 04:42:36PM -0400, John David Anglin wrote: > Source: ruby2.5 > Version: 2.5.x > Followup-For: Bug #881773 > > Dear Maintainer, > > In the 2.5.1 build, test #361 fails as follows: > > #361 test_insns.rb:389:in `block in ' F 0.090 > stderr output is not empty >

[DRE-maint] Bug#889848: marked as done (ruby2.5: Please include upstream patch to fix FTBFS on ia64)

We currently have a broken binutils on ia64, so ruby2.5 most likely got miscompiled. Please ignore this crash. Adrian On Apr 1, 2018, at 6:11 AM, Antonio Terceiro wrote: >> Date: Wed, 07 Feb 2018 22:09:23 +0100 >> From: John Paul Adrian Glaubitz

[DRE-maint] ruby-lumberjack_1.0.13-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 01 Apr 2018 21:16:32 +0900 Source: ruby-lumberjack Binary: ruby-lumberjack Architecture: source all Version: 1.0.13-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] Accepted ruby-lumberjack 1.0.13-1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 01 Apr 2018 21:16:32 +0900 Source: ruby-lumberjack Binary: ruby-lumberjack Architecture: source all Version: 1.0.13-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] Processing of ruby-lumberjack_1.0.13-1_amd64.changes

ruby-lumberjack_1.0.13-1_amd64.changes uploaded successfully to localhost along with the files: ruby-lumberjack_1.0.13-1.dsc ruby-lumberjack_1.0.13.orig.tar.gz ruby-lumberjack_1.0.13-1.debian.tar.xz ruby-lumberjack_1.0.13-1_all.deb ruby-lumberjack_1.0.13-1_amd64.buildinfo Greetings,

[DRE-maint] ruby-xmlrpc_0.3.0-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 31 Mar 2018 15:03:47 -0300 Source: ruby-xmlrpc Binary: ruby-xmlrpc Architecture: source all Version: 0.3.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers

[DRE-maint] ruby-omniauth-saml 1.10.0-1 MIGRATED to testing

FYI: The status of the ruby-omniauth-saml source package in Debian's testing distribution has changed. Previous version: 1.7.0-1 Current version: 1.10.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] Bug#882006: redmine: "no_notification" option is not honored in mail_handler.rb

Quack, I had a look at your problem and the current code. I can see in `create_user_from_email` that the code is much different now (in 3.4.4): if handler_options[:no_notification] user.mail_notification = 'none' end So I think you problem is solved now. Could you have a

[DRE-maint] Bug#836369: marked as done (redmine: install after purge fails due to missing ucf(r) call during postrm)

Your message dated Mon, 02 Apr 2018 12:14:24 +0900 with message-id <1823e513f64ab133399c86da5765d...@duckcorp.org> and subject line Re: redmine: install after purge fails due to missing ucf(r) call during postrm has caused the Debian Bug report #836369, regarding redmine: install after purge