RFS: ruby-arel 9.0.0-1 (and some questions)

2018-02-08 Thread Georg Faerber
Dear Debian Ruby people, While trying to upload a new upstream release of schleuder, I've ran into the following problem while testing the package with ruby2.5: 1) Schleuder::LoggerNotifications notifies admins of multiple text-messages Failure/Error: list = create(:list,

ruby-gpgme_2.0.16-1_source.changes ACCEPTED into unstable

2018-02-08 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 07 Feb 2018 22:37:24 +0100 Source: ruby-gpgme Binary: ruby-gpgme Architecture: source Version: 2.0.16-1 Distribution: unstable Urgency: medium Maintainer: Ruby packages maintenance

Processing of ruby-gpgme_2.0.16-1_source.changes

2018-02-08 Thread Debian FTP Masters
ruby-gpgme_2.0.16-1_source.changes uploaded successfully to localhost along with the files: ruby-gpgme_2.0.16-1.dsc ruby-gpgme_2.0.16.orig.tar.gz ruby-gpgme_2.0.16-1.debian.tar.xz ruby-gpgme_2.0.16-1_source.buildinfo Greetings, Your Debian queue daemon (running on host

Update for vagrant-libvirt package

2018-02-08 Thread Jon Bernard
Hello, I prepared an upstream update and bugfix [1] for the vagrant-libvirt package. My changes are in a salsa fork [2]. Since it changes three branches (upstream, pristine-tar, and master) I'm not sure if submitting a salsa pull request is the best workflow. Any input on this would be much