[DRE-maint] Bug#1016028: vagrant-libvirt: allow_existing for disks is broken with recent versions of libvirt

Hi, anonym (2022-07-25): > The attached patch fixes this, and is in fact already merged > upstream, but not released yet. Update: the fix was released in 0.10.0 upstream (and 0.10.1 was released since). Cheers! ___ Pkg-ruby-extras-maintainers mailing

[DRE-maint] Processed: tagging 1016028

Processing commands for cont...@bugs.debian.org: > tags 1016028 + fixed-upstream Bug #1016028 [vagrant-libvirt] vagrant-libvirt: allow_existing for disks is broken with recent versions of libvirt Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assist

[DRE-maint] Processed: tagging 1016028

Processing commands for cont...@bugs.debian.org: > tags 1016028 + upstream Bug #1016028 [vagrant-libvirt] vagrant-libvirt: allow_existing for disks is broken with recent versions of libvirt Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 10

[DRE-maint] ruby-github-linguist 7.22.1-1 MIGRATED to testing

FYI: The status of the ruby-github-linguist source package in Debian's testing distribution has changed. Previous version: 7.12.2-5 Current version: 7.22.1-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day y

[DRE-maint] Bug#1015084: marked as done (ruby-rubame: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: pairs = client.recvfrom(20000))

Your message dated Wed, 17 Aug 2022 22:53:34 + with message-id and subject line Bug#1015084: fixed in ruby-rubame 0.0.3~git20131224.f3c78ba-3 has caused the Debian Bug report #1015084, regarding ruby-rubame: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: pairs = client.recvfrom(2) to

[DRE-maint] ruby-rubame_0.0.3~git20131224.f3c78ba-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 17 Aug 2022 23:48:09 +0200 Source: ruby-rubame Architecture: source Version: 0.0.3~git20131224.f3c78ba-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Valentin Vidic Closes: 10

[DRE-maint] Processing of ruby-rubame_0.0.3~git20131224.f3c78ba-3_source.changes

ruby-rubame_0.0.3~git20131224.f3c78ba-3_source.changes uploaded successfully to localhost along with the files: ruby-rubame_0.0.3~git20131224.f3c78ba-3.dsc ruby-rubame_0.0.3~git20131224.f3c78ba-3.debian.tar.xz ruby-rubame_0.0.3~git20131224.f3c78ba-3_source.buildinfo Greetings, Your

[DRE-maint] Bug#1017524: jekyll: Could not find 'mercenary' (~> 0.3.3)

*for migrating ruby-rouge 3.30 from experimental to unstable Sorry for the mistake :) -- Vivek K J Debian Contributor https://vivekkj.codes/ ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alio

[DRE-maint] ruby-omniauth-ldap_2.2.0-1~fto11+1_amd64.changes ACCEPTED into bullseye-backports-staging, bullseye-backports-staging

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 17 Aug 2022 14:14:39 +0530 Source: ruby-omniauth-ldap Binary: ruby-omniauth-ldap Architecture: source all Version: 2.2.0-1~fto11+1 Distribution: bullseye-backports-staging Urgency: medium Maintainer: Debian Ruby T

[DRE-maint] Bug#999721: marked as done (ruby-omniauth-openid-connect: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue

Your message dated Wed, 17 Aug 2022 09:05:27 + with message-id and subject line Bug#999721: fixed in ruby-omniauth-openid-connect 0.10.0-1 has caused the Debian Bug report #999721, regarding ruby-omniauth-openid-connect: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/

[DRE-maint] ruby-omniauth-openid-connect_0.10.0-1_source.changes ACCEPTED into experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 16 Aug 2022 17:39:21 + Source: ruby-omniauth-openid-connect Architecture: source Version: 0.10.0-1 Distribution: experimental Urgency: medium Maintainer: Debian Ruby Team Changed-By: Mohammed Bilal Closes:

[DRE-maint] ruby-omniauth-ldap_2.2.0-1~fto11+1_amd64.changes is NEW

binary:ruby-omniauth-ldap is NEW. binary:ruby-omniauth-ldap is NEW. source:ruby-omniauth-ldap 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),

[DRE-maint] Processing of ruby-omniauth-openid-connect_0.10.0-1_source.changes

ruby-omniauth-openid-connect_0.10.0-1_source.changes uploaded successfully to localhost along with the files: ruby-omniauth-openid-connect_0.10.0-1.dsc ruby-omniauth-openid-connect_0.10.0.orig.tar.gz ruby-omniauth-openid-connect_0.10.0-1.debian.tar.xz ruby-omniauth-openid-connect_0.10.0-1_

[DRE-maint] Bug#999718: marked as done (ruby-omniauth-ldap: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block i

Your message dated Wed, 17 Aug 2022 08:40:15 + with message-id and subject line Bug#999718: fixed in ruby-omniauth-ldap 2.2.0-1 has caused the Debian Bug report #999718, regarding ruby-omniauth-ldap: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubyg

[DRE-maint] ruby-omniauth-ldap_2.2.0-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 16 Aug 2022 19:24:06 +0530 Source: ruby-omniauth-ldap Architecture: source Version: 2.2.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Mohammed Bilal Closes: 999718 Changes:

[DRE-maint] Processing of ruby-omniauth-ldap_2.2.0-1_source.changes

ruby-omniauth-ldap_2.2.0-1_source.changes uploaded successfully to localhost along with the files: ruby-omniauth-ldap_2.2.0-1.dsc ruby-omniauth-ldap_2.2.0.orig.tar.gz ruby-omniauth-ldap_2.2.0-1.debian.tar.xz ruby-omniauth-ldap_2.2.0-1_amd64.buildinfo Greetings, Your Debian queue d