[DRE-maint] Bug#926220: itamae: execution error

2019-04-02 Thread Hideki Yamane
package: itamae version: severity: important tags: patch We cannot exec itamae with below error # itamae Traceback (most recent call last): 4: from /usr/bin/itamae:4:in `' 3: from /usr/lib/ruby/vendor_ruby/thor/base.rb:444:in `start' 2: from /usr/lib/ruby/vendor_ruby/tho

[DRE-maint] Processed: Bug #926220 in itamae marked as pending

2019-04-02 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #926220 [itamae] itamae: execution error Added tag(s) pending. -- 926220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___

[DRE-maint] Processing of itamae_1.9.10-2_source.changes

2019-04-02 Thread Debian FTP Masters
itamae_1.9.10-2_source.changes uploaded successfully to localhost along with the files: itamae_1.9.10-2.dsc itamae_1.9.10-2.debian.tar.xz itamae_1.9.10-2_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) _

[DRE-maint] itamae_1.9.10-2_source.changes ACCEPTED into unstable

2019-04-02 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 02 Apr 2019 17:57:32 +0900 Source: itamae Architecture: source Version: 1.9.10-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Hideki Yamane Closes: 926220 Changes

[DRE-maint] Bug#926220: marked as done (itamae: execution error)

2019-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Apr 2019 09:33:58 + with message-id and subject line Bug#926220: fixed in itamae 1.9.10-2 has caused the Debian Bug report #926220, regarding itamae: execution error to be marked as done. This means that you claim that the problem has been dealt with. If this is not

[DRE-maint] Bug#926227: obs-api: Admin user should not have a well-known password

2019-04-02 Thread Simon McVittie
Package: obs-api Severity: important Tags: upstream Control: block 926198 by -1 Installing obs-api currently creates an "Admin" user with the well-known password "opensuse", which the user is expected to change before doing anything else. I think the Admin user's password should either be set to

[DRE-maint] Processed: obs-api: Admin user should not have a well-known password

2019-04-02 Thread Debian Bug Tracking System
Processing control commands: > block 926198 by -1 Bug #926198 [obs-api] obs-api: Permissions and database setup should be done in maintainers scripts, not in a post-installation one 926198 was not blocked by any bugs. 926198 was not blocking any bugs. Added blocking bug(s) of 926198: 926227 --

[DRE-maint] Bug#926232: obs-api: should not install files owned by 'nobody'

2019-04-02 Thread Simon McVittie
Package: obs-api Version: 2.7.1-10 Severity: normal Tags: upstream Prompted by #926198, I looked at /usr/share/obs/api/script/rake-tasks.sh and found that it has: chown nobody:www-data /etc/obs/api/config/database.yml chown nobody:www-data /var/log/obs/backend_access.log chown nobody:www-data /va

[DRE-maint] Bug#926235: obs-api: Configure OBS to use its own certificate path by default

2019-04-02 Thread Simon McVittie
Package: obs-api Version: 2.7.1-10 Severity: wishlist The Debian default configuration for obs-api uses the "snakeoil" self-signed certificate generated by the ssl-cert package, with OBS-specific certificates commented out: > # SSLCertificateFile /srv/obs/certs/server.crt > # SSLCertifica

[DRE-maint] Bug#926232: marked as done (obs-api: should not install files owned by 'nobody')

2019-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 2 Apr 2019 12:28:14 +0100 with message-id <20190402112814.GA20879@horizon> and subject line Re: Bug#926232: obs-api: should not install files owned by 'nobody' has caused the Debian Bug report #926232, regarding obs-api: should not install files owned by 'nobody' to be mark

[DRE-maint] Bug#853164: Default tasks max seems too low

2019-04-02 Thread Simon McVittie
Control: tags -1 + pending On Mon, 30 Jan 2017 at 13:02:56 +0100, Sjoerd Simons wrote: > Starting from systemd v231 each service gets 15% of the maximum amount of > tasks > of the system. Which should be enough for most services, but when running a > set of worker instances this can spike up duri

[DRE-maint] Processed: Re: Bug#853164: Default tasks max seems too low

2019-04-02 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + pending Bug #853164 [obs-worker] Default tasks max seems too low Added tag(s) pending. -- 853164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

[DRE-maint] Bug#926247: ruby-hangouts-chat: access network during build?

2019-04-02 Thread Gianfranco Costamagna
Package: ruby-hangouts-chat Version: 0.0.5-1 Severity: serious Hello, look like the client is trying to reach googleapis.com during build, see the build log: ┌──┐ │ Run tests for ruby2.5 from debian/ruby-tests.rake

[DRE-maint] Bug#903448: Bug#903448: ruby-websocket-parser, ruby-websocket: error when trying to install together

2019-04-02 Thread Andreas Beckmann
Control: clone -1 -2 Control: reassign -2 ruby-websocket 1.2.8-1 Control: retitle -2 ruby-websocket: needs Breaks+Replaces: ruby-websocket-parser (<= 1.0.0-1) On 2019-03-29 18:30, Antonio Terceiro wrote: > ruby-websocket-parser is using a namespace that it is no supposed to. > websocket_parser wa

[DRE-maint] Processed: Re: Bug#903448: ruby-websocket-parser, ruby-websocket: error when trying to install together

2019-04-02 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #903448 [ruby-websocket-parser] ruby-websocket-parser: hijacks namespace from ruby-websocket Bug 903448 cloned as bug 926254 > reassign -2 ruby-websocket 1.2.8-1 Bug #926254 [ruby-websocket-parser] ruby-websocket-parser: hijacks namespace from ruby-

[DRE-maint] Processing of ruby-cool.io_1.5.4-1_source.changes

2019-04-02 Thread Debian FTP Masters
ruby-cool.io_1.5.4-1_source.changes uploaded successfully to localhost along with the files: ruby-cool.io_1.5.4-1.dsc ruby-cool.io_1.5.4.orig.tar.xz ruby-cool.io_1.5.4-1.debian.tar.xz ruby-cool.io_1.5.4-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.d

[DRE-maint] ruby-cool.io_1.5.4-1_source.changes REJECTED

2019-04-02 Thread Debian FTP Masters
Source-only uploads to NEW are not allowed. binary:ruby-cool.io is NEW. source:ruby-cool.io is NEW. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. _

[DRE-maint] Processing of ruby-cool.io_1.5.4-1_amd64.changes

2019-04-02 Thread Debian FTP Masters
ruby-cool.io_1.5.4-1_amd64.changes uploaded successfully to localhost along with the files: ruby-cool.io_1.5.4-1.dsc ruby-cool.io_1.5.4.orig.tar.xz ruby-cool.io_1.5.4-1.debian.tar.xz ruby-cool.io-dbgsym_1.5.4-1_amd64.deb ruby-cool.io_1.5.4-1_amd64.buildinfo ruby-cool.io_1.5.4-1_amd64.de

[DRE-maint] ruby-cool.io_1.5.4-1_amd64.changes is NEW

2019-04-02 Thread Debian FTP Masters
binary:ruby-cool.io is NEW. binary:ruby-cool.io is NEW. source:ruby-cool.io 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 be patie

[DRE-maint] Bug#926278: Please build a separate binary package to ship rubygems

2019-04-02 Thread Moritz Muehlenhoff
Package: libruby2.5 Version: 2.5.5-1 Severity: wishlist rubygems are currently a part of libruby2.5. Can you please split them into a separate binary package like ruby2.5-rubygems (which libruby2.5 would still depennd upon)? With jruby we have a second Ruby implementation in the archive (which em

[DRE-maint] Processed: user debian...@lists.debian.org, usertagging 920725, tagging 924799, tagging 926103, tagging 925564 ...

2019-04-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 920725 piuparts There were no usertags set. Usertags are now: piuparts. > tags 924799 + experimental Bug #924799 {Done: Dmitry Shachnev }

[DRE-maint] ruby-rails-assets-perfect-scrollbar 1.4.0-2 MIGRATED to testing

2019-04-02 Thread Debian testing watch
FYI: The status of the ruby-rails-assets-perfect-scrollbar source package in Debian's testing distribution has changed. Previous version: 1.4.0-1 Current version: 1.4.0-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple