[DRE-maint] Bug#894754: vagrant: Invalid gemspec in rbnacl-libsodium stack level too deep
Control: reassign -1 ruby-rbnacl Control: retitle -1 ruby-rbnacl: doesn't really provide 'rbnacl-libsodium'? On Wed, Apr 04, 2018 at 11:13:57PM +, Nicholas Capo wrote: > I'm sorry. > It seems I did have additional gems installed. > > After removing all gems, and `ruby*` apt packages (and reinstalling > vagrant), vagrant works again! > > When I then did `sudo gem install overcommit` which installed > childprocess-0.9.0 as a dependency, vagrant broke again. > > Feel free to close this issue. > > Sorry to have bothered you, > > Nicholas > > P.S. It seems to be an interaction either with having multiple version of > childprocess or maybe just childprocess > 0.5.9. ok, that helps. I realized that there is still something wrong with rbnacl-libsodium, though. I can list it, but can't really use it. ~$ gem list rbnacl-libsodium *** LOCAL GEMS *** rbnacl-libsodium (1.0.16) ~$ ruby -e 'gem "rbnacl-libsodium"' Traceback (most recent call last): 3: from -e:1:in `' 2: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:65:in `gem' 1: from /usr/lib/ruby/2.5.0/rubygems/dependency.rb:322:in `to_spec' /usr/lib/ruby/2.5.0/rubygems/dependency.rb:310:in `to_specs': Could not find 'rbnacl-libsodium' (>= 0) among 227 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/home/terceiro/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all', execute `gem env` for more information signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#892548: dhelp: /usr/sbin/dhelp_parse broken with ruby 2.5
Control: unmerge 892548 Control: reassign 892548 dhelp On Wed, Apr 04, 2018 at 11:30:11PM +0200, gregor herrmann wrote: > On Wed, 04 Apr 2018 00:48:59 +0300, Коля Гурьев wrote: > > > Unfortunately, I can't reproduce this error. However, I've faced the > > other error related to dhelp's cron script. It fails to build a document > > index, and so search doesn't work. But at least the dhelp_parse utility > > can rebuild its documentation directory, and a home page is still > > available. It seems some of the next warnings aren't linked to dhelp. > > Indeed, I can confirm that "my" original output is gone, and I now > see what you've copied below. From that output my evaluation is that dhelp has issues with ruby2.5, even after the lack of dbm support has been fixed. I'm returning this bug to dhelp. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#894754: vagrant: Invalid gemspec in rbnacl-libsodium stack level too deep
Control: tag -1 + moreinfo unreproducible On Tue, Apr 03, 2018 at 04:17:51PM -0500, Nicholas Capo wrote: > Package: vagrant > Version: 2.0.2+dfsg-3 > Severity: normal > > Dear Maintainer, > > When running any `vagrant` command the following is error appears and the > command seems to never complete. > > ``` > $ vagrant status > Invalid gemspec in [/usr/share/rubygems-integration/all/specifications/rbnacl- > libsodium.gemspec]: stack level too deep > ``` > > At one point I typed Ctrl+C quickly and got this (possibly related) stack > trace: > > ``` > $ vagrant status > Invalid gemspec in [/usr/share/rubygems-integration/all/specifications/rbnacl- > libsodium.gemspec]: stack level too deep > [...] > ``` I can't reproduce this on my system, nor in a clean system with only vagrant installed. > I have tried removing `ruby-rbnacl` (which removes `vagrant`) and > reinstalling, > but the issue persists. > ``` > $ sudo apt autoremove --purge ruby-rbnacl [...] > $ sudo apt install vagrant > $ vagrant status > Invalid gemspec in [/usr/share/rubygems-integration/all/specifications/rbnacl- > libsodium.gemspec]: stack level too deep > ^C > ``` > > I do not beleive I have any gems installed (other than what comes from apt), > but here is the list just in case: > > ``` > sudo gem list [...] > ``` I need more than that. please share the output of: find /var/lib/gems gem list rbnacl-libsodium ruby -e 'gem "rbnacl-libsodium"' also, do you have vagrant plugins installed from outside of Debian? signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[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 >bootstraptest.tmp.rb:3:in `once': stack level too deep (SystemStackError) >from bootstraptest.tmp.rb:7:in `block in once' >from bootstraptest.tmp.rb:3:in `once' >from bootstraptest.tmp.rb:7:in `block in once' >from bootstraptest.tmp.rb:3:in `once' >from bootstraptest.tmp.rb:7:in `block in once' >from bootstraptest.tmp.rb:3:in `once' >from bootstraptest.tmp.rb:7:in `block in once' >from bootstraptest.tmp.rb:3:in `once' > ... 97 levels... >from bootstraptest.tmp.rb:3:in `once' >from bootstraptest.tmp.rb:7:in `block in once' >from bootstraptest.tmp.rb:3:in `once' >from bootstraptest.tmp.rb:11:in `' > > So, it appears the test causes a stack overflow on hppa. > > It is not uncommon for hppa to require twice the stack space x86 needs. > Is there a way to increase the stack allocation for hppa (e.g., using ulimit)? > Otherwise, I would say the test needs to be skipped on hppa. I don't think working around this in the tests is the correct solution to the issue. There was a similar problem on ppc64el recently, maybe you can find a similar solution for hppa: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881772 I don't have the cycles to go after this myself, but I'll be happy to take a patch (but please also send it upstream). signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#889848: marked as done (ruby2.5: Please include upstream patch to fix FTBFS on ia64)
> Date: Wed, 07 Feb 2018 22:09:23 +0100
> From: John Paul Adrian Glaubitz
> To: Debian Bug Tracking System
> Subject: ruby2.5: Please include upstream patch to fix FTBFS on ia64
> Message-ID:
> <151803776351.18433.12367250620839726943.report...@z6.physik.fu-berlin.de>
> X-Mailer: reportbug 7.1.8
>
> Source: ruby2.5
> Version: 2.5.0-4
> Severity: normal
> Tags: patch
> User: debian-i...@lists.debian.org
> Usertags: ia64
>
> Hello!
>
> ruby2.5 currently FTBFS on ia64 with:
>
> gcc -g -O2 -fdebug-prefix-map=/<>=. -Wformat
> -Werror=format-security -fPIC -D_FORTIFY_SOURCE=2 -fno-strict-overflow
> -fvisibility=hidden -fexcess-precision=standard -DRUBY_EXPORT -Wdate-time
> -D_FORTIFY_SOURCE=2 -I. -I.ext/include/ia64-linux-gnu -I./include -I.
> -I./enc/unicode/10.0.0 -o cont.o -c cont.c
> cont.c: In function 'cont_save_machine_stack':
> cont.c:478:7: error: 'rb_thread_t {aka struct rb_thread_struct}' has no
> member named 'machine'
> th->machine.register_stack_end = rb_ia64_bsp();
>^~
> cont.c:502:50: error: 'rb_thread_t {aka struct rb_thread_struct}' has no
> member named 'machine'
> size = cont->machine.register_stack_size =
> th->machine.register_stack_end - th->machine.register_stack_start;
> ^~
> cont.c:502:83: error: 'rb_thread_t {aka struct rb_thread_struct}' has no
> member named 'machine'
> size = cont->machine.register_stack_size =
> th->machine.register_stack_end - th->machine.register_stack_start;
>
> ^~
> cont.c:503:42: error: 'rb_thread_t {aka struct rb_thread_struct}' has no
> member named 'machine'
> cont->machine.register_stack_src = th->machine.register_stack_start;
> ^~
> Makefile:375: recipe for target 'cont.o' failed
>
> This has already been fixed upstream [1]. I am attaching the backported patch
> for ruby2.5. It would be nice if it could be included in the next upload.
Well, it seems that the issue is deeper than getting it to build. it segfaults
beatifully while building documentation ... unfortunately I don't have the
cycles to go after this, but I will happily take a tested patch (which should
also be sent upstream, of course).
Generating RDoc documentation
./miniruby -I./lib -I. -I.ext/common ./tool/runruby.rb --extout=.ext --
--disable-gems "./bin/rdoc" --root "." --page-dir "./doc" --encoding=UTF-8
--no-force-update --all --ri --op ".ext/rdoc" "."
Parsing sources...
0% [ 1/871] /<>/doc/NEWS-1.8.7
0% [ 2/871] /<>/doc/NEWS-1.9.1
0% [ 3/871] /<>/doc/NEWS-1.9.2
0% [ 4/871] /<>/doc/NEWS-1.9.3
0% [ 5/871] /<>/doc/NEWS-2.0.0
0% [ 6/871] /<>/doc/NEWS-2.1.0
0% [ 7/871] /<>/doc/NEWS-2.2.0
0% [ 8/871] /<>/doc/NEWS-2.3.0
1% [ 9/871] /<>/doc/NEWS-2.4.0
1% [10/871] /<>/doc/contributing.rdoc
1% [11/871] /<>/doc/contributors.rdoc
1% [12/871] /<>/doc/dtrace_probes.rdoc
1% [13/871] /<>/doc/extension.ja.rdoc
1% [14/871] /<>/doc/extension.rdoc
1% [15/871] /<>/doc/globals.rdoc
1% [16/871] /<>/doc/keywords.rdoc
1% [17/871] /<>/doc/maintainers.rdoc
2% [18/871] /<>/doc/marshal.rdoc
2% [19/871] /<>/doc/regexp.rdoc
2% [20/871] /<>/doc/security.rdoc
2% [21/871] /<>/doc/standard_library.rdoc
2% [22/871] /<>/doc/syntax.rdoc
2% [23/871] /<>/doc/syntax/assignment.rdoc
2% [24/871] ...d/ruby2.5-TpDw3s/ruby2.5-2.5.1/doc/syntax/calling_methods.rdoc
2% [25/871] ...by2.5-TpDw3s/ruby2.5-2.5.1/doc/syntax/control_expressions.rdoc
2% [26/871] /<>/doc/syntax/exceptions.rdoc
3% [27/871] /<>/doc/syntax/literals.rdoc
3% [28/871] /<>/doc/syntax/methods.rdoc
3% [29/871] /<>/doc/syntax/miscellaneous.rdoc
3% [30/871] ...by2.5-TpDw3s/ruby2.5-2.5.1/doc/syntax/modules_and_classes.rdoc
3% [31/871] /<>/doc/syntax/precedence.rdoc
3% [32/871] /<>/doc/syntax/refinements.rdoc
3% [33/871] NEWS
3% [34/871] README.ja.md
4% [35/871] README.md
4% [36/871] addr2line.c
4% [37/871] array.c
4% [38/871] bignum.c
4% [39/871] class.c
4% [40/871] compar.c
4% [41/871] compile.c
4% [42/871] complex.c
4% [43/871] cont.c
5% [44/871] debug.c
5% [45/871] debug_counter.c
5% [46/871] dir.c
5% [47/871] dln.c
5% [48/871] dln_find.c
5% [49/871] dmydln.c
5% [50/871] dmyenc.c
5% [51/871] dmyext.c
5% [52/871] doc/NEWS-1.8.7
6% [53/871] doc/NEWS-1.9.1
6% [54/871] doc/NEWS-1.9.2
6% [55/871] doc/NEWS-1.9.3
6% [56/871] doc/NEWS-2.0.0
6% [57/871] doc/NEWS-2.1.0
6% [58/871] doc/NEWS-2.2.0
6% [59/871] doc/NEWS-2.3.0
6% [60/871] doc/NEWS-2.4.0
7% [61/871] doc/contributing.rdoc
7% [62/871] doc/contributors.rdoc
7% [63/871] doc/dtrace_probes.rdoc
7% [64/871] doc/extension.ja.rdoc
7% [65/871] doc/extension.rdoc
7% [66/871] doc/globals.rdoc
7% [67/871] doc/keywords.rdoc
7% [68/871] doc/maintainers.rdoc
7% [69/871] doc/marshal.rdoc
8% [70/871] do
[DRE-maint] Accepted ruby-did-you-mean 1.2.0-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 31 Mar 2018 14:00:01 -0300 Source: ruby-did-you-mean Binary: ruby-did-you-mean Architecture: source Version: 1.2.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Antonio Terceiro Description: ruby-did-you-mean - smart error messages for Ruby > 2.3 Changes: ruby-did-you-mean (1.2.0-2) unstable; urgency=medium . * debian/rules: add a sanity check to make sure gemspec version is taken from source dir * did_you_mean.gemspec: add patch to force loading version from source directory Checksums-Sha1: 6ef75ced0f44677ac9ed3a3937b46d15f52efb1f 2089 ruby-did-you-mean_1.2.0-2.dsc 0cc794c7b5a6aec1ac67bb366ea8ec17197a5158 3068 ruby-did-you-mean_1.2.0-2.debian.tar.xz 951b22c194010b4cbc16a3cd67b929a11c89555a 6492 ruby-did-you-mean_1.2.0-2_source.buildinfo Checksums-Sha256: e260ebe0784608c5ab44a4abc011f230a10330e8576bf7e101a49f1f04c2d7a0 2089 ruby-did-you-mean_1.2.0-2.dsc f3f471b29597687339f0d135d8fe2f825fcd2c80d53e0ca03471cbdef37ba49c 3068 ruby-did-you-mean_1.2.0-2.debian.tar.xz fa5146a252578cfbb82a0acd51d37dfffae07eb7d90e8b4b81a64885b4687a12 6492 ruby-did-you-mean_1.2.0-2_source.buildinfo Files: bd8e370f288e8a6e81e846e5107dddbd 2089 ruby optional ruby-did-you-mean_1.2.0-2.dsc 9e9159a8db591faaff22885b1805e4a6 3068 ruby optional ruby-did-you-mean_1.2.0-2.debian.tar.xz 3327b9063b4282ae5b6bb58858d63d32 6492 ruby optional ruby-did-you-mean_1.2.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlq/vzQACgkQ/A2xu81G C97kJw//Z1ZHsGCW59NjCX6kRxcD0MQPIvKEV/2A9sPWbIJfyQzhILfqbveDoJP+ rq5HD7Oub8YGSxuannDx9zF9swghOCbVvrST1FqCUipd120wfmGMmwsH9DmWOkFU 1qiK8Pdp6alTDMRFGIPZZxpJi78raaX/ozMBbzQAv+8pZUaZ5pUJ6m9aT8YBF3Mv ScstBazWZfHZ4xGAeDagtHhrH6vCi2kN3rPGAVVy02KLNwEcWuP0PcHwi31ncllT zmNHmvXXGdshU82I7XGbHk08um/Ng+0fJ0dIe7LNtRWcHRRX+jFVE133wg5lhonw TczXiWAI42c16GfNUkdubgxh88OcqEGkAZW9G1nab2ioZntCGM5wNB2cVj/J3iej Q/OHvR/RJiEgsb1YgVNxU4bTegHMhtOl2NXt1/vAKctWTAHww/jEluwVvrEeJlNj 9VE1hwZAwJV02nNziJ9reJ2Jk5W/XbTyG6vbdZ6bh7sp4ZTGxXgH6Pp6QFDpNIB1 AxIdh4N029fXxMdvW9dfCVHknABP2PPlgBz1b94LGxJRopcV++oTY47AtSRuU9Z4 07GUbGO42rUIZk5rnBPKu2qg0XG5Eb8gjikzrEiPEkylpsnMDP5d3bfDBZmydfpN StS017H2QVMa/5IXzoFF6bhgVz8TW4je3x8MuXWYoXehoFPFY7w= =JnIO -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted ruby-did-you-mean 1.2.0-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 31 Mar 2018 13:37:04 -0300 Source: ruby-did-you-mean Binary: ruby-did-you-mean Architecture: source Version: 1.2.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Antonio Terceiro Description: ruby-did-you-mean - smart error messages for Ruby > 2.3 Changes: ruby-did-you-mean (1.2.0-1) unstable; urgency=medium . [ Antonio Terceiro ] * New upstream version 1.2.0 * Point Vcs-* to salsa repository * Skip tests on Ruby < 2.5 * debian/ruby-tests.rake: skip experimental tests * Refresh packaging with `dh-make-ruby -w` * Bump debhelper compatibility level to 11 * Bump Standards-Version to 4.1.3, no changes needed * Use https in debian/watch . [ Cédric Boutillier ] * Run wrap-and-sort on packaging files Checksums-Sha1: 1b7ae95323a749e22d7bb743b9e8bbac50b47ae6 2089 ruby-did-you-mean_1.2.0-1.dsc a63572b92c81f1cce8e081439b96a2afdf05871d 28429 ruby-did-you-mean_1.2.0.orig.tar.gz 84c0a03b9ed6bcbf06bfd5e26086092346d944cf 2488 ruby-did-you-mean_1.2.0-1.debian.tar.xz 1a0175faf71de9824c189d8581d6dd5ec6a8407a 6492 ruby-did-you-mean_1.2.0-1_source.buildinfo Checksums-Sha256: 08360ca887eb1e36cfb8c301e94b64e7fa98453af8f0eff8eb4943644cadc5f8 2089 ruby-did-you-mean_1.2.0-1.dsc 5fae26639087b732e1e375fd36dd90fda808cdf50d12324f0c4a0c4d544131b6 28429 ruby-did-you-mean_1.2.0.orig.tar.gz 6296843d3c336efb0117009675ab7a49420fd101dd9cb4e0c2fd9b73eec9732c 2488 ruby-did-you-mean_1.2.0-1.debian.tar.xz a7d43a976affe9ffc60f448503cf6f12dd877dac07a97638efeb1d94261f5b6d 6492 ruby-did-you-mean_1.2.0-1_source.buildinfo Files: dcb01c6fefa93693dfac6d44088bc0db 2089 ruby optional ruby-did-you-mean_1.2.0-1.dsc 359e187fd38cd84e95fcc6ebb9081795 28429 ruby optional ruby-did-you-mean_1.2.0.orig.tar.gz ed5826f9ee6c59fc348df907e092cbbf 2488 ruby optional ruby-did-you-mean_1.2.0-1.debian.tar.xz a4760b811f6b3580a4141c2371260cc1 6492 ruby optional ruby-did-you-mean_1.2.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlq/uaAACgkQ/A2xu81G C95Bow//Zwwz9ZGclJnb03gI94gru28DPCkFohD+xzv79KMIrM2aMrqdrdRjp4dF fdse+l6iLIFecWnKKUnBBnNSLwyqKZkIkQirxcK9Gt6eRYG2YvOcY3sc6dM6mEo/ WVQx3sfTUxEg+IflVjgEOfC7Qz2or4S7xon8xjlnAcZGcBzgY7hqbWfRKibR+VUQ WpSnT4f4vcsN/Sa6Hfa0u3SCxtd2s1vS2woYGZ0X5McDWoEAYPaqxIi6Mhr76SE2 DLB4nIJoP0hunzxX1o8v7B5FCNXO6cHa3fFSKT++prRYbfrpQ0SneeghQHYgC2Cg YWOzrOKKXgaqjk1UwAJDBxgKAGyz6qwH47etmxkEEbHfYEldFezlJ88aiAFCuy5X 1ohT5YHzXTZjtof+nD0KTwceDCno5Rx1hT7w3RdFPmY/WqV9u6q46Hi4FD6CKMxr zQCPUbVU6pHvkcnOnKiahtrO+G9nhhOHnvvpeM1aRRvdXp2x1BDYaPJFByXtxpz4 Vr6WMLWl2/XDt8+uawaprearTI8HhogKSFPSRyA45geUg2I5QHV4ZmVgXrH7RpNz TzSknY8NQ1qmKf3wrEKHr6+RBJaok1HiqLvi6J70N2H+wdmqsQK1k1fauKtsm+5m cFuKVhs1SRUXmibodRlWhoXL/HUpROrSiNO0Mwg9K8FBlhluM70= =u7bx -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted ruby2.5 2.5.1-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 31 Mar 2018 13:22:48 -0300 Source: ruby2.5 Binary: ruby2.5 libruby2.5 ruby2.5-dev ruby2.5-doc Architecture: source Version: 2.5.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Antonio Terceiro Description: libruby2.5 - Libraries necessary to run Ruby 2.5 ruby2.5- Interpreter of object-oriented scripting language Ruby ruby2.5-dev - Header files for compiling extension modules for the Ruby 2.5 ruby2.5-doc - Documentation for Ruby 2.5 Closes: 889848 892099 Changes: ruby2.5 (2.5.1-1) unstable; urgency=medium . * New upstream version 2.5.1. . According to the release announcement, includes fixes for the following security issues: . - CVE-2017-17742: HTTP response splitting in WEBrick - CVE-2018-6914: Unintentional file and directory creation with directory traversal in tempfile and tmpdir - CVE-2018-8777: DoS by large request in WEBrick - CVE-2018-8778: Buffer under-read in String#unpack - CVE-2018-8779: Unintentional socket creation by poisoned NUL byte in UNIXServer and UNIXSocket - CVE-2018-8780: Unintentional directory traversal by poisoned NUL byte in Dir - Multiple vulnerabilities in RubyGems * Refresh patches. . Patches dropped for being already applied upstream: . - 0005-Fix-tests-to-cope-with-updates-in-tzdata.patch - 0006-Rubygems-apply-upstream-patch-to-fix-multiple-vulner.patch * Add patch to fix FTBFS on ia64 (Closes: #889848) * Add simple autopkgtest to check for builtin extensions that are build against external dependencies (ssl, yaml, *dbm etc) * Add build-dependency on libgdbm-compat-dev (Closes: #892099) * debian/tests/excludes/any/TestTimeTZ.rb: ignore tests failing due to assumptions that don't hold on newer tzdata update. Upstream bug: https://bugs.ruby-lang.org/issues/14655 * debian/libruby2.5.symbols: update with new symbol added in this release Checksums-Sha1: ffab60462ff0106f896effb97b0c6fc5f6fd6d6b 2396 ruby2.5_2.5.1-1.dsc e95ff19092f2026b161e6e6d7759489d646e10aa 15669354 ruby2.5_2.5.1.orig.tar.gz bb278f38ac79739b01c7b73e18659b5c237475c6 101248 ruby2.5_2.5.1-1.debian.tar.xz e47b70daaaff8144f9efc0988dfb430815c7 6419 ruby2.5_2.5.1-1_source.buildinfo Checksums-Sha256: 7435915706d3ec3ee701e2e48186a3561e7b7d72f2534ea1db81f707f848d6a8 2396 ruby2.5_2.5.1-1.dsc d690140ba5b91b23d990dad9170fca8ef8e9e5ac8b62f1eb7a84ecf1edce2ed3 15669354 ruby2.5_2.5.1.orig.tar.gz b6a1bcae7ef73639d50819d39047cc4c2f491644f3399b5fb5cbbf793264fe45 101248 ruby2.5_2.5.1-1.debian.tar.xz 4aa400cfb4a70229125e6b442eecb5531807c82bba6afcc0ef16c0cffd86cb34 6419 ruby2.5_2.5.1-1_source.buildinfo Files: efa9d5f75ab65e7c7676035379a16128 2396 ruby optional ruby2.5_2.5.1-1.dsc 2a2c44e4d1c573006c17d9d0ef82afe3 15669354 ruby optional ruby2.5_2.5.1.orig.tar.gz 63021d08b85b26cdf3e09c85149d1023 101248 ruby optional ruby2.5_2.5.1-1.debian.tar.xz 417dac07bcca2522f2ae9814c99ee09b 6419 ruby optional ruby2.5_2.5.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlq/thoACgkQ/A2xu81G C97YWhAAqPXn/o4XFgcJa6Tlk5pT1yKiCuPYPx24mIALLypiaUfuHEFChIxOF9NI TBf44lSHz/tzq/2yKux0SdQtCbgfUaN8eihVUdBhPE+k+RsXsIv3mNN1o33szv+N tkuCZPfHaDHpH9E7Ibvma6NByMqhHZNOYvhmCNdP6aiM75jSbwP3gjR8Fo8/kSNA 3p2NL4qEInkyUqKfmmp1g0s41nvBxT6BiXoY4WKtZPbY7+TDNjT0IjK+zlnodLVH cKYYPHRH0UoIuKh6+uF/HwvUtmQPJ98zOH9LSBl27mfEwKfS5ZvQqaKdSABYs+5S nYsFQ6rNewqRJXaGiRRB80Xy3br402sZRSgl3SOaH/KVNBGt3E9UwKpXzpWBN7G4 w3D2237IMhSjFPyqePeTs++/j5IYetgz1vSL+T9njAtd9wZM7UE1GwHLXMEPxc+Y tfbthz4d+pMTLaK0WK4TftPOT+0mKUD7qVVa2IyW7DWeQPrzg0cWExz7zw0lBFDN pmHd5YKfGtNwXxZ2txK8+1KHiySvJOV0c0bFMs5y3y4iBINVgBiReXsGTe5U81D7 +uMxEASH9X4FiQ9QCqYLzJbB0llq6uzulJuKWCAyCZUT2ZfOwZhbtt0OshFGhTOD GsMM1qePltBHCD9hsIYbFc2n4iQ/CRvM1BYuXSo52nSrlUSgS7I= =A45a -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted ruby-rblineprof 0.3.7-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 30 Mar 2018 19:49:51 -0300 Source: ruby-rblineprof Binary: ruby-rblineprof Architecture: source Version: 0.3.7-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Antonio Terceiro Description: ruby-rblineprof - line-profiler for ruby Changes: ruby-rblineprof (0.3.7-2) unstable; urgency=medium . * Team upload. * Remove usage of ruby-debugger-ruby-core-source. It is only used for Ruby 1.9 or earlier, which are gone from Debian for a while. - Add patch to drop dependency on debugger-ruby_core_source from gemspec - debian/control: drop any dependency on ruby-debugger-ruby-core-source * Refresh packaging with `dh-make-ruby -w` - Bump debhelper compatibility level to 11 - Bump Standards-Version to 4.1.3; no changes needed - Change Vcs-* to point to salsa.debian.org - Use https in debian/watch Checksums-Sha1: 68d61d594c72ccd10ed12546ad8b63e62ff0e90d 2056 ruby-rblineprof_0.3.7-2.dsc 3ae3e7451b2534e6c8d0fe08ddc8d3e26a96d250 2472 ruby-rblineprof_0.3.7-2.debian.tar.xz 30e9c7e3a8c77d384162703e779fb8ebd5278f44 6498 ruby-rblineprof_0.3.7-2_source.buildinfo Checksums-Sha256: b79b33d2cc7abe9393502c10672d917524568861445125eee4e8d81e776aa3df 2056 ruby-rblineprof_0.3.7-2.dsc 275e8a4a0ba40e9d3e5f938369476e9e73784ebda9f2f7ffdfa2e695ee225c52 2472 ruby-rblineprof_0.3.7-2.debian.tar.xz 5b77c4b79ac97fe352c44974dbced47642b045aa04c5dada0d0ecae952c1e61e 6498 ruby-rblineprof_0.3.7-2_source.buildinfo Files: 34f7a94571772d6f71177f4d10bc7146 2056 ruby optional ruby-rblineprof_0.3.7-2.dsc bbfe30fa47d88d4288ceb96cbaef9802 2472 ruby optional ruby-rblineprof_0.3.7-2.debian.tar.xz 036d9280a156851c30c022b7ccce171e 6498 ruby optional ruby-rblineprof_0.3.7-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlq+wR4ACgkQ/A2xu81G C95ZSg//e4EvbM3OYhONLKbHUIX9LANo8PH3C7CN878g45bior6mCT6qN/WhOpnx YF04Yml7SdFSRKK43pAAw8+auDhVXD9Mxw2Xs8tfCD+xIcIu2nrCYMkl0wmaxCO0 /xYgoDV9EGgu36BVLTTFYSzW5jLwFYge0dOrAb4hoXJ9z+KqSgMz2FAZXapsadgg qZFn3dcQyN7xgGqZOOMRdYYarE2j9hXn9DpffljDPc0woOw+APtNu1eLFUwEEAPv Y8zk9niRU1MLp0V5HZ8m2PHDJsgT4HmvwvE3+ZlkSehhxsEaHPTjdrYMuZcxzrP7 /ez9zRrlCvE8UnxdI15/Tcunc/KwoDbv0dQ90C0K7yJTZKBUK+jHL/rHXz5u774T Ozj70nLoA3qCfVxbUz8VE36tbjRTW4NxlU/jDlo2Rkww+PdsqafEth7L4U6+IAmt UEiD/S1zWoPoxgdAgAB1IHbV6fftdzD5HdTJEpgb+XnemDWqyOoB2x2ZiUBwDWqo lCseeGP34XBnV2EWcCf+WVOITmMHFXW1/jEoq8g2Ia3xCA+cvtgAz3QcTzmFw+qh oEM0/TfGAC0vgGZurl2wZKd5NrWHY/AXqWftzQGqoqWsA+BHGjr5t8N1b5kHl1RM P5RXoOihdWbQhpFYMZFnOZps4eNrhUQ/yKDc7OXfnkES2QVNKx4= =CliY -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#894305: package build-depends on legacy ruby2.3-dev
On Thu, 29 Mar 2018 01:11:20 +0800 Matthias Klose wrote: > Package: src:ruby-debugger-ruby-core-source > Version: 1.3.8+ds-1 > Severity: serious > Tags: sid buster patch > > the package build-depends on legacy ruby2.3-dev which is going to be removed. > Is > there are reason not to use the unversioned b-d? > > patch at > http://launchpadlibrarian.net/362398716/ruby-debugger-ruby-core-source_1.3.8+ds-1_1.3.8+ds-1ubuntu1.diff.gz I don't think this patch fixes anything. This package is fundamentally broken and useless, and is in the archive just to satisfy a pointless dependency. I did an entire analysis of the situation back when this package is ITP'ed, but AFAICT I was completely ignored: https://lists.debian.org/debian-ruby/2017/09/msg00016.html Now, we have a hardcoded dependency on ruby2.3-dev, which is a blocker for the removal of ruby2.3. I just made an upload of ruby-rblineprof removing the dependency on ruby-debugger-ruby-core-source, and will request the removal of ruby-debugger-ruby-core-source from the archive. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted ruby-rmagick 2.16.0-4 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 28 Mar 2018 23:11:36 -0300 Source: ruby-rmagick Binary: ruby-rmagick ruby-rmagick-doc Architecture: source Version: 2.16.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Antonio Terceiro Description: ruby-rmagick - ImageMagick API for Ruby ruby-rmagick-doc - ImageMagick API for Ruby (documentation) Changes: ruby-rmagick (2.16.0-4) unstable; urgency=medium . * Team upload. * Add patch to disable one more failing test * Refresh packaging * Bump debhelper compatibility level to 11 * Bump Standards-Version to 4.1.3; no changes needed * Update Vcs-* to point to salsa.debian.org * use https in debian/watch Checksums-Sha1: 5664074c7fd1a9387a40358b77d12ff0f29d19ec 2262 ruby-rmagick_2.16.0-4.dsc d4ef2517f60337c0344153774555d9bdbea1bc7a 10748 ruby-rmagick_2.16.0-4.debian.tar.xz d7bb4bcb74760f82e633531b68a3fcf87252704d 11927 ruby-rmagick_2.16.0-4_source.buildinfo Checksums-Sha256: a94b1ec90c9d6d3efb86db94f91af4b4dda63c3f90bdda80d3af1c3892096df9 2262 ruby-rmagick_2.16.0-4.dsc 8de3830bfc7a442bd89b3226b9eec3e198a2a172177e229ee491ea571097de7a 10748 ruby-rmagick_2.16.0-4.debian.tar.xz bf4a9438450aa6822ae9eeb0ecf52b860c5c015a71d019e09bdfc0564a9bfbb4 11927 ruby-rmagick_2.16.0-4_source.buildinfo Files: 76e1868a378676c79093e7e7c2f9f998 2262 ruby optional ruby-rmagick_2.16.0-4.dsc 722fc874b26c736dae36bf1779d8db04 10748 ruby optional ruby-rmagick_2.16.0-4.debian.tar.xz 0fd55d8d23c56dfaef517ef47d60c4a6 11927 ruby optional ruby-rmagick_2.16.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlq8TGMACgkQ/A2xu81G C95O5xAAzrV5rUty+Dqend3A5cxhADzB9antpWHZzwC86PWEtEEhYfHaxHjjrUn/ RThI3KmG397FV7HWlr0cuGScL5rBpJAwW/HLpQ1/EIvcWNdLsxvkSBR7m4K51Cpv 7bkt7cdQ+zjkXDYNHYowTjH73h+OAHg+hpnl0AvQWxe1C3parSNPzzKNufcz6oT1 gT4aVJMGQz0m+5le/+0X3hKLWIxTalm2PSNF5SVookLtElvbevuRKqe+cnOkRiTh TXIwYwkNRT471CD3CDmOKSsf+68Uz7jHJSHbASGaRqIU+s4uH9pFSAkBFcWEgPl/ gu5u7P3pmZR+q3gACM2GqPJjL8jbF2OB6CKGyPjk8LsYNOO1p5zb3OuNhn5xDzgV wBCxRfdyxeJa029gXkgaOFgJdaiaHlqsxxQn9phmrLQ7DSLKhWhldDx1ZEc8/jw4 plM15Kn6ivSyZ9nT/e0c3P3Bf8nn0xzYlc8oqTJdPJgvFbHZlieEIPt/T06Lt7im Zln6564mZHtcbuXZI6f+2ZholqAdk+QJMCVZgH/a2MQPVrOkGSuB88krL4rsjeKO BR7Gz2M0v+e6BEwbj4RjMGVRn1pwCRz5rRsV/cf2239gQZZ4XH2CHitlbIIGe3d2 uZsTdQjpyBXyKj9hTfubDkxBNTYqajMq6WpGWPzVqEVf3/XKsTI= =bjBl -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted puma 3.11.3-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 28 Mar 2018 18:53:22 -0300 Source: puma Binary: puma Architecture: source Version: 3.11.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Antonio Terceiro Description: puma - threaded HTTP 1.1 server for Ruby/Rack applications Closes: 859542 Changes: puma (3.11.3-1) unstable; urgency=medium . * Team upload * Remove myself from Uploaders: * New upstream version 3.11.3 * Build against libssl-dev instead of libssl1.0-dev (Closes: #859542) * Refresh packaging files with `dh-make-ruby -wo .` * Bump debhelper compat to 11 * Change Vcs-* to point to salsa.debian.org * Use standard debian/ruby-tests.rake * drop build-dependency on ruby-hoe * Refresh patches * New patches: - 0006-test-helper.rb-drop-bundler-usage.patch - 0007-test-test_cli.rb-disable-test-that-fails-randomly.patch * Replace 0001-test_puma_server_ssl-update-for-newer-versions-of-Op.patch with 0001-test_puma_server_ssl-disable-test-that-takes-too-lon.patch Checksums-Sha1: 4eeeb87108ebe280ac726cf9c3227f6bec2ca798 1905 puma_3.11.3-1.dsc be489d39a60c6d1959381eb9d872b19a2fecd1a1 207993 puma_3.11.3.orig.tar.gz 33bd4fae9eae14fc42c2b66f4179e20e21c52d3a 4032 puma_3.11.3-1.debian.tar.xz 83b24fc426a4416456d76c0334c689a576fd2de6 6497 puma_3.11.3-1_source.buildinfo Checksums-Sha256: aeba8f77d9b62b3dede417177a3b16a503840440e3aca8b98bd05b807fd5f5c9 1905 puma_3.11.3-1.dsc fad1db13588fe5818925940aea9a25f6ef16062b6f75701c7ecf2c722cb803d3 207993 puma_3.11.3.orig.tar.gz f65eaab3be5f39ba5c4f2e4a0b80e329106180e5d1a53ac67135dcf234077ae0 4032 puma_3.11.3-1.debian.tar.xz 0a87aafef4721a5b63dbbc5935c68e944b00ac93b95b595dca23c8aa5bbd499f 6497 puma_3.11.3-1_source.buildinfo Files: 6da7f4c8c43579af6d9428952bbc1c16 1905 ruby optional puma_3.11.3-1.dsc 3460f3df4ac80a34504020bae4ff39e4 207993 ruby optional puma_3.11.3.orig.tar.gz 2a4bbb5e9180f08c5c9829653f5c9a34 4032 ruby optional puma_3.11.3-1.debian.tar.xz 662817463f46a569adc9ef1170e569e3 6497 ruby optional puma_3.11.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlq8H14ACgkQ/A2xu81G C95oKhAA0iPdnPMVa/A52B3v3Hx0Lx/n0rs5n5Hc6/hfTS4ljqx5B5omNDNv+37s tXdFV/B30n9wWmPv+GVw/jXV87adJrhHzSSyNBIaKvJMRBo4U8YlQsTDdQwQqVos ZhhkOJvvMR04EWbw7TJoTuTxny7CYh1povrqip0is8pgXlY8qMNghMhd5FOcxjs7 roBG/kcjlkotTFivF/XjPwbJrQGUv9hfV73H9aXVR5HTleKjnnaYZkKX8AnKv3F9 UTTuhpTKH8EjH+CXyMdLyVMuUMKdTNLBXAN80D/JA7C1p4uss8SNIaZCLgV3OyL8 kXnDVf+9ZaaVtMy1mXYSshtf+HETRnADuq72vaj/rPOUAV+Y64NOsO8bZlk/2Y/I 1IKef+GOuWTI4mAN/eCDcZkiGq7ZfMi+osEI2kkWPpgsR5ybcj2HUccb2e/TNuOY eBkgc3y8fhAlB+i6oU9OPK234vXLZZ/shU/cNo4pKzXCD5DmkfhGvLxzLRTrUFRX KTWX0Dq7BpiIfTROzrXMD3jSy0oS31Sn1Z/5mRwBp+kS7a20lC1pgzJjAY66qHWf qc9mgfMsfy8GAhRgqfMVICxD6tTvmfbvES3/Du5UQDeK9vpyI4FQWhX2aCPj0g1w bkMLUIF4MUTAu4kPTRCoJwWnZ0ARcrkA1LK88dYEVrkQ7iBuB7c= =RhUg -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted vagrant 2.0.2+dfsg-3 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 26 Mar 2018 16:14:19 -0300 Source: vagrant Binary: vagrant Architecture: source Version: 2.0.2+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Antonio Terceiro Description: vagrant- Tool for building and distributing virtualized development enviro Closes: 890662 Changes: vagrant (2.0.2+dfsg-3) unstable; urgency=medium . * Specify minimal version of ruby-net-ssh required (Closes: #890662) Checksums-Sha1: ddf5547db22c71e4699904d01b5f06b7dc3c139a 2296 vagrant_2.0.2+dfsg-3.dsc bc7dd19cf18fb56d1bb399561ca75f685f98c017 12112 vagrant_2.0.2+dfsg-3.debian.tar.xz ade58ede541b32dfbec5f4e201ce25af1c4f5cf8 7185 vagrant_2.0.2+dfsg-3_source.buildinfo Checksums-Sha256: ef7896fb0ce9d8e03c0c210f833b2989a348fa3f4845b28d219514e63baa6191 2296 vagrant_2.0.2+dfsg-3.dsc 58bf79f7c8a4fad6dc4fe1a0a9ceba520605bc6b61d2ec16328b6eb16aa6592c 12112 vagrant_2.0.2+dfsg-3.debian.tar.xz b04fbce7b3f3b70a5f3df6e1e5b6fb334eef44f7882a4d9e006d1516f0ecada6 7185 vagrant_2.0.2+dfsg-3_source.buildinfo Files: b2bf9720bd7c8eb927c57d4ad6c9bd6c 2296 admin optional vagrant_2.0.2+dfsg-3.dsc 377e64b87458cf5eea8aaf65eeb5dc44 12112 admin optional vagrant_2.0.2+dfsg-3.debian.tar.xz 3aceae166abcb4fa2b903c12c9d90557 7185 admin optional vagrant_2.0.2+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlq5RyEACgkQ/A2xu81G C96hKQ/+NVTTCxLaG7hoUc4i+bPP7D++FsCuXDKYB8CzK7aDrI8TrFduUYfH7po5 WqvNPNAfNYD5YkuuIDN1/AMh6O5+9D2mpAiOWPg4MXbfxaXtEINWQQJOGeVz/XdI 0f6fVYH2Rl+vkmC7uSrqamsQo4O4sPzzZvVyEIMvl6+gP677/eIBFzdE2/QpVDrv MnTgO3A6qprS0egJZWIRVyBm1D6a824CJsK7L6l2rDtvkrr0zKdpTGPFip3pfp3v HF2evRbX/3YNgC6b0JUJTHX/XHLhIE7E81kQvaEu3wZVORgT1+YiFMn6V8WQmJJF zKUy2WCQmjcCd7zui/5f1iEs3ECcaWf96ykQms+rWMXP/5x7G+Eh6Thh0wZLkk5w N9WV5NzHg1wcLq2ktpt6gQ+Ap4RshkXpw043FG1VbCSh8iXArrFfqd5hsawZHt2n yPojUe+/V1Q+NcCsYQrztKCb0r/7yg+r1/bHwpLCI9PCEQMFrNIE7p2SNiuLIvrK CWy3BD0q3TaLsTP1ti0TfGvhgl9RRo+FLCPDKsTKbqiz4J5r2+WqpEbjVfcVioY8 LCwBQQ1DWsBQG9ds9HPKbGYDb6wvFJ5u2KrXHrLK6TVrNX5yAmZj2l7b94FHIyjJ b4GtvLa2bNbKMwqT/FA7F6Q499i/917QqS07MDhhfQAg3ykNmwA= =HM0S -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted gem2deb 0.38.1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 22 Mar 2018 14:33:24 +0800 Source: gem2deb Binary: gem2deb gem2deb-test-runner Architecture: source Version: 0.38.1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Antonio Terceiro Description: gem2deb- Debian Ruby packaging suite gem2deb-test-runner - Debian Ruby packaging suite - tool to run tests Closes: 892131 Changes: gem2deb (0.38.1) unstable; urgency=medium . * dh_ruby_fixdepends: don't touch dependencies of packages that do not already depend on ruby (Closes: #892131) Checksums-Sha1: 3cc840cd9e8fbe6243c671e427f4f26a53b345b4 2288 gem2deb_0.38.1.dsc 2544b19cd224db6a5b0dc6acf87063eda74216e3 67896 gem2deb_0.38.1.tar.xz 22002171fc6e7990fe69ad53be082caaf549b577 8851 gem2deb_0.38.1_source.buildinfo Checksums-Sha256: 1fb02ff43179cec01e537c5e8d9c4aa1b58b47f7805535cf51c23eee9db1360d 2288 gem2deb_0.38.1.dsc 5c8ae25d4779af0dc50894df133504e9f3b4321a7fb09251e33f53f353472853 67896 gem2deb_0.38.1.tar.xz da784f158b139fe3b738fe8385d4549849dd917aff24b26688becf9c0a442601 8851 gem2deb_0.38.1_source.buildinfo Files: 63d8a8868deacb5151e74e8a05021dca 2288 ruby optional gem2deb_0.38.1.dsc 5d7ef7e803d80fcf5e09ad531f8c6e0d 67896 ruby optional gem2deb_0.38.1.tar.xz 74fa752e1d11633ac7687d463872c0c1 8851 ruby optional gem2deb_0.38.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlqzUikACgkQ/A2xu81G C95hww//ScZvqAOUxtxCUxLxMgAP1toGuPicx6fvzDOoO+Y8yBMXxNk+y2djb0gd NTcG6CD3ED8sI/jxV7Lci6rvTyw01B7nMU1dyzHHj07quvNraxtDRDi7EIgVIFL0 DvWyccnv/EHpXZ6ph36K8rMvwMB13Q9p1QWyEOxRp8/kmb7Zdh9iXVldvQwrtmJn r5iQf7H51ni+RclzdgV29g/6EPPSx6qZ8qda1A5Ja3kiBtFbY70fQJpx2mwngddv blQO+Tq4y7uYxWvIE+Dar0/SB1/Zcyph5WVLvTRu0Jk2Z4TnGfNafTtWE4D1dyTU qInpJBRQpTvI84LmhicqBv+mwGLXT7sp48OfMcycWWR8msCVuG4FUmNB3EL5/loA Rx390IBXCU4kl3uPW2wImDj2S9adGETtbaeXN9dKHqsUpZJgdwuwHoRxSkxRQZnT BJsQX4nDwIcxprcnfQdIy/LLZJKDwHF9cLUjCdkyQ46CCYIr2JMhT9T7lldP2BFI 4JPllcNi9tLdj3NaE40OREcLdMcwoJdlx6hyt+HVc542AXksokiH5drVKqHFF66y NOLJXbEL50AxQa5waN8Zz5UWI9bYr4rRhQ6jInmpMqnKDRbJVjdPGsYYnH+a3e98 cbf0LPb9sCdgU36MtuaJWWjoGT0asembaZXibKfUs+6f+y2F0UU= =RANS -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted ruby-prof 0.17.0+dfsg-3 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 09 Mar 2018 18:20:58 -0300 Source: ruby-prof Binary: ruby-prof Architecture: source Version: 0.17.0+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Antonio Terceiro Description: ruby-prof - Fast Ruby profiler Changes: ruby-prof (0.17.0+dfsg-3) unstable; urgency=medium . * Team upload * debian/ruby-tests.rake: exclude *all* test classes that involve timing tests Checksums-Sha1: 5e37586f8910a74f27fb4e7f04e44a4d3d60e2cf 2043 ruby-prof_0.17.0+dfsg-3.dsc 7fed1c4ce9a05c3a94354d2e15b852ef8bdb3636 8880 ruby-prof_0.17.0+dfsg-3.debian.tar.xz 41ef5eea655475720355b6844b8b16c2e4355cc4 6668 ruby-prof_0.17.0+dfsg-3_source.buildinfo Checksums-Sha256: 25908ee120eb8301b684e41655071343c96264ebcb4d1f0642ae607afbb7116c 2043 ruby-prof_0.17.0+dfsg-3.dsc 13562f0890488e1f138dc1b80592506632ee5b7c1285dca220a404541aea06a5 8880 ruby-prof_0.17.0+dfsg-3.debian.tar.xz 8442991e77c32e58d8b25feb859296ce9e5af0b4d0ca09ea5c083451f4e08685 6668 ruby-prof_0.17.0+dfsg-3_source.buildinfo Files: 4ae47b41a6485e45f27d7eff0ddcf4b0 2043 ruby optional ruby-prof_0.17.0+dfsg-3.dsc 91e1debbd6e2cd1999887e1ed59a37c5 8880 ruby optional ruby-prof_0.17.0+dfsg-3.debian.tar.xz 0df039d219a841f7238d288eb2541eb9 6668 ruby optional ruby-prof_0.17.0+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlqi/RMACgkQ/A2xu81G C946pxAAwEw3nqGVizSTtOojamUdUijaOlGKl/BGXkHaf6fAP+Zgl9gMGGlUAyJr VJv4ff3e3GhUtLmotRQ73Xez0PSrP2PStnITqplFhKXd2A+gI0zcpcjMDVzEu9CE 0t/FHifrUgCsr/qzE7pgOwO/fXNY341l8ERt+k/eKYEbpHx+Tea1aokC3n2HEsDh /fpChm9rH2c2PU+Z2uQ8/jGcMD1Kcu9Muz63OUaSdRgMjyuZL5bjiKbJnF08GaYO O9KKBPXIzCVTGvBEfPBT6cpXs10adUUlLLFykHog3oz5PrrvDfGDYkLsBJNcsYxD XVOk3EPbDzioret3B3oMOXIAH3D4/EJNuL4X98J+BQRWysWf+7flMckYd+XkEGhy AGZbw5pc/y4nCUHtHaTQ/WStx8eHF8XrycR+FeKx/IgRJ8FdZHAb4gpoVH2EwLfJ D97Ef/Snl3vOL/sbs18+Jaf2+Dn8y+YgZKje+wrUloJJzZA/IqwvcWcOVbGX1Bq5 ZZwE3moP+rd4Q3rAIXLJBC7cbOkmbYxvjwMezxDb8r9vEemgB9BJhctUAntFD4Dg UBgigS5QO3f2aYYfW4EyZ30PepZwf5Mp7BLwFQUqTlaySD9ec1Vs9d7JX9oeq3/a ct0nMT0iRxgzaBTS462Wwl3iVYMOywXbK/RBFXCi+P7QpYJYX18= =0xQS -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted ruby-prof 0.17.0+dfsg-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 09 Mar 2018 11:16:02 -0300 Source: ruby-prof Binary: ruby-prof Architecture: source Version: 0.17.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Antonio Terceiro Description: ruby-prof - Fast Ruby profiler Changes: ruby-prof (0.17.0+dfsg-2) unstable; urgency=medium . * Team upload * debian/ruby-tests.rake: avoid timing tests that can fail randomly * Refresh packaging files after new dh-make-ruby run Checksums-Sha1: bdd5a421ee546f28e8184b710728bbde17fd5a85 2043 ruby-prof_0.17.0+dfsg-2.dsc b17894cbb24910446c2d26e6ca9ffb033f1d1428 8828 ruby-prof_0.17.0+dfsg-2.debian.tar.xz 49215cec7a0536590eece8d375df5be302cd0f7a 6668 ruby-prof_0.17.0+dfsg-2_source.buildinfo Checksums-Sha256: 937fffaf3873062ee35eeb66c8b57daa1bb3fe2836c22ac2b1fe4ebd47dcbcaa 2043 ruby-prof_0.17.0+dfsg-2.dsc 00466862952a185ce9994a58ca37604de77d48ed464ada716eced3c02bbf8924 8828 ruby-prof_0.17.0+dfsg-2.debian.tar.xz bd5631a99982419752f2f1fb253a2e58ba40879db6433de89805f62692885d92 6668 ruby-prof_0.17.0+dfsg-2_source.buildinfo Files: b755ec7e91414725a0e1af93715a4988 2043 ruby optional ruby-prof_0.17.0+dfsg-2.dsc 96f2077d859c14efc2539d231de7cf19 8828 ruby optional ruby-prof_0.17.0+dfsg-2.debian.tar.xz 3c343b622ceddc46786afa8eabddfe59 6668 ruby optional ruby-prof_0.17.0+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlqinccACgkQ/A2xu81G C97xxhAAlYZ1oCZJ1/mqXtgDqAgF18kfON1p5nYxu9L8cD6Nr5rju9k8lT96lnAK 4VSpNcl2ThU4Ikz3lhavcLpb++ljh1M0G8UgdK/FmDv5Fxms2pGfOBbs6i48lFql q5xZL7DWnMInCsk//sJXeEjsAv++WydWXJjr/pWFzrQcabie82E0zJv5gb5w1el2 9iNKvmYzphMfKvnAFewUMr0aM9vzsHYHcV0ZQSy8eEp1hgwGlun8G6KHXuAPP4tc fhBXMMU6+EvUH+uXdFv5Y1OcvSmatTsCHrxeX2WoGZVhkQdkA2Lvsr5q9KPgd8Z6 zFb7wiBUxmZcpP7a0EEWX/w9WuziRM17FYGhwyXKqDwN5esPYgRVwLp1dV3+pZV3 qhaKL316y1ENL7J1J+deOZ9v42wS3na5AN6hiCoEFVmLUTjcj3fcCIHhaM2Hfp2G +e9kiVSQGkYmSdhmuCZl1obJVKMVv0yqGaSUPnMG351DQ7MMAOpbVC/de5rPdbi+ Oiv4exwomj5Kf+WSYr/mr3aSZ45zhuQzmaVfFky6r+62wFO6JO9oY+XX7RTSSdbY se5u+nROZU6MMvfzSHvZtTW+2hRk3Ytma24WHcRbg1McjbK0BdEJ/5G90wkdM15/ xGClRXC6VjUevIVJkRYpS2Y4kOVfo5zWCfytAtdWVrOhFb+pKNw= =KC0x -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted ruby-vmstat 2.3.0-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 05 Mar 2018 17:15:04 -0300 Source: ruby-vmstat Binary: ruby-vmstat Architecture: source Version: 2.3.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Antonio Terceiro Description: ruby-vmstat - library to gather system information Changes: ruby-vmstat (2.3.0-2) unstable; urgency=medium . * Team upload. * Disable test that expects a single loopback device. You cannot know how many of those people have. Checksums-Sha1: 6e5ccd279e9c7b7c032a743bc516fa8edb008437 2089 ruby-vmstat_2.3.0-2.dsc ef48837d35d981e20a7e7b480e11fab3f32df138 3016 ruby-vmstat_2.3.0-2.debian.tar.xz 33b603dd60592ef32775a1c78a511e9e2bde2f04 6961 ruby-vmstat_2.3.0-2_source.buildinfo Checksums-Sha256: 26111e1a7e70e45c4a970e5471b2d3035b7ee2acb466117038210b3bfcdeb920 2089 ruby-vmstat_2.3.0-2.dsc 437699114fb73d9ade5a71cf77dd4fea41024cfd9a66b0b8e7d5594521e1a3ba 3016 ruby-vmstat_2.3.0-2.debian.tar.xz 4f7f931be1bd2ea92ea90afbd6be213b09ce4896977929f81b13ed3f11de07e8 6961 ruby-vmstat_2.3.0-2_source.buildinfo Files: f7a8de91c90eb29f954236daacf4e7a6 2089 ruby optional ruby-vmstat_2.3.0-2.dsc ff18f6839cc7c99eeba98a2a1815b029 3016 ruby optional ruby-vmstat_2.3.0-2.debian.tar.xz 1de23fcde42d50021b1c33206c56a202 6961 ruby optional ruby-vmstat_2.3.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlqdpdwACgkQ/A2xu81G C94A+A//ZpD5Wql4B54wgXjD6xUUQyAC5fQxZYEZe9wQ0LtRTNpDKD5NOaTfBs+K 2ltT0lh1wIllvjcNsnyPtbopDNHJ3T0sNNm19bzz1OcLz6GNshX+XkwPG1Szil+M 4cXyycAI+1SeUhNjBmLrfq0GG2yxInsw2kHQgJ6hPs3p5KcangvQMoXDcj/4uI84 cpjcUwvW4dWNDXnckrGR7WN4b9EFTTYdH3CG6E7ogoQddqb+LCU2hVJuWjXlMNa3 gONSgUT/bNulzXpyTP3N20Ck5dxBJdks5HXaTRIYrXFAae3oTaWRRfstzrTJ867j 335hAbe9r9kr3TuydaUsnqCHz7UnOXXNoq7FKnSNIhGmUmqLt630Vy4lok0oykYb FwBrE0GaGzjFAMTq+LDut/4B3aMbwrMsI2eku3yUNehIJJe7ys4AoBg+czH+K6OD DyuxT0I2u15+FIqSr1suyzREAat3Z8vuHNopw63/fBoHbiUX8lzN62pzxzRsBOWh RqIEZdsfERpqTC4t7by57AWWnxnvEXf9B4/cJazc7vbKsSGUFWfr79Rd9B6bCuJ5 ex4Zgl/RhdjaZX1Agm3TCTiuH7F3IBSkvU0VyyYQs85Xt9VE0JRBRFRWTMqHunjG 7UozJukWMvsv9UYCi/LocrXIoM3SitLiVhM7XD8YzxFXhKWLSqU= =eskH -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted ruby-soap4r 2.0.5-4 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 05 Mar 2018 10:17:46 -0300 Source: ruby-soap4r Binary: ruby-soap4r Architecture: source Version: 2.0.5-4 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Antonio Terceiro Description: ruby-soap4r - SOAP library for the Ruby programming language Closes: 889713 Changes: ruby-soap4r (2.0.5-4) unstable; urgency=medium . * Team upload * Add remove-ruby2.5-warnings.patch: to silence deprecation warnings under ruby2.5 (Closes: #889713) Checksums-Sha1: 39828683a884a11acdb5f1dfff8c630cf3c144d1 1980 ruby-soap4r_2.0.5-4.dsc bf053979b8e5c2b8ad59321d80f0eb6044ec7749 4728 ruby-soap4r_2.0.5-4.debian.tar.xz 80addd97bd223de472a3284c0e92704e76e3195e 6677 ruby-soap4r_2.0.5-4_source.buildinfo Checksums-Sha256: 685b5ff6e9ffedafbb070924e23b11d6bf0699c98bf6023170558e183b90b328 1980 ruby-soap4r_2.0.5-4.dsc ae01c8d42bfd628bbd18315b4c2d25627ad3a2e9cd8335cc5f1ed5056cc31c71 4728 ruby-soap4r_2.0.5-4.debian.tar.xz b9ddac48baf772295257e2330105af4f8c16377138e6f575446aa8844ad02711 6677 ruby-soap4r_2.0.5-4_source.buildinfo Files: 22e1dcc8cd9143fe6e535a742e44b6d6 1980 ruby optional ruby-soap4r_2.0.5-4.dsc c77ddf196495550f78cf3c14350d9bbb 4728 ruby optional ruby-soap4r_2.0.5-4.debian.tar.xz 479653cab3eb03e9256084cc41b84678 6677 ruby optional ruby-soap4r_2.0.5-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlqdRBAACgkQ/A2xu81G C97hTw/+Pc1l39uJSwibYUtNUI68r8NqZGlgMhISmBy6C2tSApeVRQUiufKk9vp1 0F4zJGPU2WLyWq7JcxH/Akgwv9Fda6+EE0Jx7n7JRrFxmDoDy5wiYo5dHbAAzLxC U4DuaiLtIpkfaKKHXyghZ0zTCWtNST3ebK22kZWyG+5PzDX9ZS4n0HFEtqYZ+XPx 1MIP4gMIQZB9HocgRO2n7fNfMnsgR7g8sLG89zQ1D9jExPxWjSxhJpS6ZIJNdYEO +BKpM6uWSI3HY8sI79N/QMzvGkEElw8oH/QQzZwlUf8SA0Mzb3r7+xbQSwuldFD3 4SWAFXgort8hxjUtwbKx+4at7CGUcKUj+KX3lR1wWwh1CHQbDgujWe9qb72TuSTz H59pivtWJI0XLrjj7DqWchwk6oGOIVteqh9AjVe0UYl1bc+Ecwu2090nHaTeFz26 pe5EopOX0kj/Bgn9X3RcIPBs57dSkaHcsxoO2XR5qogLgIgLSQWwzeV+scnpztk4 D6exardtFMDUCqqzJcYux2Fe0UYgei3RSBNoHIHRAVmMqJbnU0xrWCRpJQIEhqg2 pQu/7/dlh+enXW+3ifNPB7Yx9uXiwO+tmPAVJ3/0uJ2HQ5PATEThKz/FSfFGeUdQ t5JArya137tVWtnNbak8FJZe6KqtaW0O3K4+1SyhlDwJS8Gha+8= =L+uo -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted ruby2.5 2.5.0-6 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 04 Mar 2018 13:30:49 -0300 Source: ruby2.5 Binary: ruby2.5 libruby2.5 ruby2.5-dev ruby2.5-doc Architecture: source Version: 2.5.0-6 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Antonio Terceiro Description: libruby2.5 - Libraries necessary to run Ruby 2.5 ruby2.5- Interpreter of object-oriented scripting language Ruby ruby2.5-dev - Header files for compiling extension modules for the Ruby 2.5 ruby2.5-doc - Documentation for Ruby 2.5 Changes: ruby2.5 (2.5.0-6) unstable; urgency=medium . * debian/rules: explicitly pass --runstatedir, --localstatedir, and --sysconfdir to ./configure Checksums-Sha1: 584df6885302094978d2de34037cb394d7fd5d83 2376 ruby2.5_2.5.0-6.dsc 15bacf7c0ac04c2c3729dd87fe336b5419a09dc8 116200 ruby2.5_2.5.0-6.debian.tar.xz 4a4021b6995fc51d008d9fc95a25166a1eb600b0 6414 ruby2.5_2.5.0-6_source.buildinfo Checksums-Sha256: 2c3b878d7e9fe196619df7647c8d6ed47e77e502b6322ebc89e826fbbe8e48a4 2376 ruby2.5_2.5.0-6.dsc f2d5cc0df80259c6b2ec9c99b71dd7fcd9ec17cdf3c7db9496db9b7349f65e91 116200 ruby2.5_2.5.0-6.debian.tar.xz 75d5861bf9e43de2144de609b15eea6088398dddf3ab3708aa3168311b41bf2d 6414 ruby2.5_2.5.0-6_source.buildinfo Files: 32a637a875c55588363f52245babef3e 2376 ruby optional ruby2.5_2.5.0-6.dsc a5003ffd7a9744e295e06bc22234c181 116200 ruby optional ruby2.5_2.5.0-6.debian.tar.xz f4506240be8d88eb9f4ef51cc599438f 6414 ruby optional ruby2.5_2.5.0-6_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlqcI2EACgkQ/A2xu81G C94VdBAAj7OU9PQh2MwTVifLo2n18w641VcSLCQOI2Z+Cjk5mMFZoZjNMpdZBhzm HhUBT7nZaju5K611KU+hbK5i/BZmS4AFdkkFIbOmMHmybTtjbBCyay/6VBWbixp9 tF2QQUOS/whNkGBxXzqRx+/7k1Iop4r3yKJoykEE9scAw8h7zP+u8XMJyUYcAYWp U2BJ5/AHqjsjK5JEnBEeayYF3DIpJaxs4f7Fqi3NciKPD6LY4LfhXS/l7IWMf9J8 NDEd+t69WbxszROALUg9WnCnAU5yYIdUbCZoSArQEfxm0qDNbZZX/7vMerdLAHKv IC4AETS4dhSRz5xYGF312B2fgeFWbBwasPlC0Sfpx5nUkCFDXVS4nJlP1KON7JyK TgCpPIu1sK7awilIFV1jHeU2IzFbApyviiP0MBwuisWQL91hPJ/2PHnmaXIox7FE r/alPUDts8QqGj3WWQJ07o1NQJFZGCqwoTvZJ8N34CxOsGfcMSuCcJ1nWEureofT 24VaejMRb8/G6don1ArMEg08VW/rc1D2usCOBDVpZ2JoqWjKVF/BjBrku3juJgVg H3hlbjUY9pf91rmsesurxAuTpYcJadoQwcr4TnyM1DdKeF/3w3LclXI4eZzf5MIA 3Qmpp3NDMlsgBklQc5g6sP9DZKUqjfx0LLDB2R9uj6vrCqX65D0= =N8oD -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted vagrant 1.9.1+dfsg-1+deb9u1 (source all) into proposed-updates->stable-new, proposed-updates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Feb 2018 21:54:18 -0300 Source: vagrant Binary: vagrant Architecture: source all Version: 1.9.1+dfsg-1+deb9u1 Distribution: stretch Urgency: medium Maintainer: Antonio Terceiro Changed-By: Antonio Terceiro Description: vagrant- Tool for building and distributing virtualized development enviro Closes: 889873 Changes: vagrant (1.9.1+dfsg-1+deb9u1) stretch; urgency=medium . * 0008-Convert-atlas-references-to-vagrant-cloud.patch: backport upstream patch to download boxes from app.vagrantcloud.com instead of the deprecated atlas.hashicorp.com (Closes: #889873) Checksums-Sha1: 907571918d85deb946d3bba30ac4982aa9349739 2021 vagrant_1.9.1+dfsg-1+deb9u1.dsc 14070f25f585c3233c3af5a9046f5aee0c3946e7 15548 vagrant_1.9.1+dfsg-1+deb9u1.debian.tar.xz d7193dd2ad58ae5ac18e47198c854b884088bb83 397346 vagrant_1.9.1+dfsg-1+deb9u1_all.deb 50af92ff5d54b7745129f35085fa86718aacc125 6821 vagrant_1.9.1+dfsg-1+deb9u1_amd64.buildinfo Checksums-Sha256: 8a961d792f2dd9214be9eec3b7d8a231b7346681b0881c99f44caa0c994d87d6 2021 vagrant_1.9.1+dfsg-1+deb9u1.dsc 59854de725168e856dc3cec761d11348d5a99fb3bfdb25c5fe35808db3c49219 15548 vagrant_1.9.1+dfsg-1+deb9u1.debian.tar.xz c2bbc223f61fe826850eb3123b9fb5c03d253b5b80817c816404b07f1d1dff1d 397346 vagrant_1.9.1+dfsg-1+deb9u1_all.deb 2528b62fc8976d0f7526cd4acb4747cf77bb3fb4b4f828a9c36769c1e3232b59 6821 vagrant_1.9.1+dfsg-1+deb9u1_amd64.buildinfo Files: 13492d5bbdd9265be789824a928b71a0 2021 admin optional vagrant_1.9.1+dfsg-1+deb9u1.dsc 5af9eeab6bef80847b4e37d56ea391b0 15548 admin optional vagrant_1.9.1+dfsg-1+deb9u1.debian.tar.xz f14b2985eef5d16b307bc49a9d53df54 397346 admin optional vagrant_1.9.1+dfsg-1+deb9u1_all.deb 32732ae715e755de5bb25c54057ebd5e 6821 admin optional vagrant_1.9.1+dfsg-1+deb9u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlqWp9AACgkQ/A2xu81G C97BIw/+I4UeObmHtJgNcKxE+Nw9YrSfrbmts0dViqi+0R8DRlPw3q1FiWFk/O68 N3A2EYBzesrrzNC49dv8MEuYsB7H7HdTWwvpQUh5hcJ3HAWtL1heOzlNMV4rjxlq Uv090YDIdKHTG+Hw9FuJ1Ga90pKDhi0zLOkN2k5fW1RUMWl83E6jHLrGqYu/sC6H jspi7wjwrw7zpDIVeAhrXi1U7uIJOrqKoWT3tBECMRsYaO7lH9hrcmABHQlx2KDD Fx9EzOEL/2pixApsYkZOHhKuT7g1S7ItC/CU2kHiTp73T5OXgHBV1bDqxrgChUKP RtLwwaJMq+OuyiAqg+Os6BTfuQ33zltJk/3vCVoDevhOYxdjSTvUUIxvxNJlwhAW d658f4dAXkfDNTPpC1hovqx6kaOVA9e7LlowvstDk2njg6CrVU6FCIROkPyBjQ/w JaroDn1pgM2ywWh96CPwGEQ/wjf+XZgqy+cxXrzmKoEggE6+U1QC1jYxf0X5DhPW zO76dORtqo6hzl5sr/hfGa03blc2p8npKx7dW/yunXR44O7VmUSj3yEXDTczP9VX YtlMV3TkjmOIAvlKOyRgi6dGYBMfF/73d+nK4rZDqCecFZq5OuhpRPXJagj/buHJ piuiqRqhJhw8OYQpWHYlOiTevOOtNEWDB6xTNLsoly4I/kJhbUQ= =nJ++ -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted ruby-backports 3.11.1-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Mar 2018 10:29:16 -0300 Source: ruby-backports Binary: ruby-backports Architecture: source Version: 3.11.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Antonio Terceiro Description: ruby-backports - backports of new features for older versions of Ruby Changes: ruby-backports (3.11.1-1) unstable; urgency=medium . * Team upload * New upstream version 3.11.1 - fixes warnings under ruby2.5 * debian/rules: ignore test failures under ruby2.3 Checksums-Sha1: 7a2a887adb90d0b5537351d1188d23f4283e32ff 2093 ruby-backports_3.11.1-1.dsc 9dc39036fbe28abdee1adda293e6899d2f61cc37 159551 ruby-backports_3.11.1.orig.tar.gz ccfe4c1ac20b14f3538c71b683e18b102edf92ad 7984 ruby-backports_3.11.1-1.debian.tar.xz 745f9ccf9857f53b1d5e4179c320062bcc14d43e 6888 ruby-backports_3.11.1-1_source.buildinfo Checksums-Sha256: d761ca268c0d86b72b536fc6ab4d43fe7eb18fdfd4b3caaee01e423a38825af4 2093 ruby-backports_3.11.1-1.dsc 05a12adc09991e05114117a382a1f60a24efd118b8964b99ae4ae162c651c4ca 159551 ruby-backports_3.11.1.orig.tar.gz 3a77120f10904708f129b8c0e1da57a07623cd557df8a181a0a495a3731d9efb 7984 ruby-backports_3.11.1-1.debian.tar.xz 7f2fddc616077ae92f9628634b33d9a0056b79fee352c87c375426672cee7a96 6888 ruby-backports_3.11.1-1_source.buildinfo Files: 6224eb7cd0b9a88097643b38f7e0344d 2093 ruby optional ruby-backports_3.11.1-1.dsc 729ad961f5765f688dedb9a1d006a410 159551 ruby optional ruby-backports_3.11.1.orig.tar.gz e96a5673b6645e7c0ee4337a3aa58183 7984 ruby optional ruby-backports_3.11.1-1.debian.tar.xz 87d788cbb2112973598a4f9cc1560512 6888 ruby optional ruby-backports_3.11.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlqYAwgACgkQ/A2xu81G C94INw/+NMUt/8P8iQxyXZdIwXvBzWA2/OLmbPTa0GBmz5xosDlCj606x4wMvSfD tw5dMPrfneUKLR5I26kxDheU2sEld0MNYoX85TBHlNwBwsXB+qklqJM/4qV9mA4u ctswTl9f6VEKFUchuo07l3gMz6l2x3G5JBwg9u2ms0DFTwJWL94heTtKuFN9exm5 exfuuCMLH288+fa7VbQXjYbYwdARtX1NjZcqZJKHihJmlTvIyGCBDI8q2LF+O3tX QyzbAUfQK/lkWEcB3mq8aSFYJCX7IoejyEK2kriLVfenAGd3e+XFFJp8AczESfMt xiM59oOJWE4+iLjGoZSimjHRaElkqHrzU5xmBee99vApebPPfW/bClLfVje67kgK iUVAf8mbLtSoHo1DVlp+YEjXpJTFmYW6FFqEYtfjKuU2y+3pJSJJmvjsL1wCdFHx opS3yhVPvdOfLlbKS2w0pEzo08m5Arj9XO3ut/ROmGimiK9ZAAj0WmDvHyRgWXVB R9/Eb9yBuXLaLb95N5Aci0iQCGqNaWKoEkeHW4NJxwmUkj5+WSS3bpxFcQdvkD6C yt3AWZls7YCE5JfUm1Sf8dg/50nUpGrrirZ6IC4Pv/KaCqbf3/nZQ7ab+PJDPZi8 6E9YpQ4Nt48Rc4VjV6q3swhf76MyrA7djOeDBsJXMtObYHtoivs= =XSg+ -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted ruby-sinatra 1.4.8-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 01 Mar 2018 10:22:13 -0300 Source: ruby-sinatra Binary: ruby-sinatra Architecture: source Version: 1.4.8-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Antonio Terceiro Description: ruby-sinatra - Ruby web-development dressed in a DSL Changes: ruby-sinatra (1.4.8-1) unstable; urgency=medium . * Team upload * New upstream version 1.4.8 - fixes warnings with ruby2.5 * Refresh patches * debian/ruby-tests.rake: remove useless -rubygems option from tests invocation Checksums-Sha1: af96974dfb9b323f0d1932d5651b5b17ca08798e 2461 ruby-sinatra_1.4.8-1.dsc 517d5bf24324e78a153550faae3c040ceeed238e 370411 ruby-sinatra_1.4.8.orig.tar.gz d1b289ae3ee6528b6cd9ab714c72fb17a4839a60 4928 ruby-sinatra_1.4.8-1.debian.tar.xz 22a1e35e97b71c5ef49c12f7d13f6d4ec21fbe6a 7943 ruby-sinatra_1.4.8-1_source.buildinfo Checksums-Sha256: 7dfa8ee350371aeb164008ace583865958f3affab05641dea34cc7d5b1d13cbf 2461 ruby-sinatra_1.4.8-1.dsc 92d62aebb6879d5646c617cdb4bc5b32f5a13f198e56d8d7fb2085ec5b323032 370411 ruby-sinatra_1.4.8.orig.tar.gz dd6a656c9071d9b36598be3210229e1360a5aae439d61a144db4c112da3079ba 4928 ruby-sinatra_1.4.8-1.debian.tar.xz b29b2e97dc82c4c4b8606ac46578b519081729c9d59e309ddee85c82919dd50c 7943 ruby-sinatra_1.4.8-1_source.buildinfo Files: 5586da406f38c7a8cf6fad951f57cc84 2461 ruby optional ruby-sinatra_1.4.8-1.dsc ff90965b9789da56bb7ac506121ebd04 370411 ruby optional ruby-sinatra_1.4.8.orig.tar.gz 933bdf865cbb6d813e17af1a66da1329 4928 ruby optional ruby-sinatra_1.4.8-1.debian.tar.xz edd8d75be0416ee459fed8201b87321a 7943 ruby optional ruby-sinatra_1.4.8-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlqX/+4ACgkQ/A2xu81G C97Xxw//SGRhrI7ORai3yPD0CwMs/tmP4DfTuNUQhn+wUVkfMt5IL9JtJk68Hgy1 SwtEI9IHWiM7V9HGQrHYlBOFAvrHi28bXXQjcWcjbIZHgdvdTuPryxXvNEkN49TW hun8DSHovgezl6hnRnjmAitKHWy+Nab0RlssLjgOuHoo3C5qsEbrvZp/Z0eMFWKd x2FIyIGPwfUMWgmQnsihf/j060/i9L/5dFzLqhAc6iF2Nsw+dw0rfceFcO8a9K/n 4+TU8fq62TkQ+tVVLXHu649cnRncDSdLNmmdLBf9ynQ8YJKrLjFfBhsr8XtDspx9 SGDZBjf9QSi/HcxsVLnysmXlGR4xkWuirEW9b+VDm6ECiazxjzi+bQKy1j6gs6Rh oK+7oYhZuTfkqlfAmXYr21bv3ZPAJi6aReWkfG3AjfejNcf72GcTDsP/66haJFHA hTSA7IlGZWlbziDQAKDpa6G3chShVNI0WhlyHZ8oNqJeGCGi/NVuMD0rLxFh5fjv W9abiYgyMIk50R6rl7QaBM2t3ckRIUqo7gKU0B3RrH4w1YAaWlJsHYP87uvLYOUy vZjAa5BKIak2fi1t36kkAmZXXGi4pKMcuaogWlw3YVsmcD6AFVLKA2TGPxZP5Nd0 zDlvZZaXJ94dLJ0+utObWb74EE+aCUDXtt7mvq505iIx6EzABHU= =2nRm -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted vagrant-libvirt 0.0.43-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 26 Feb 2018 16:14:07 -0300 Source: vagrant-libvirt Binary: vagrant-libvirt Architecture: source Version: 0.0.43-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Antonio Terceiro Description: vagrant-libvirt - Vagrant plugin that adds an Libvirt provider to Vagrant Closes: 891498 Changes: vagrant-libvirt (0.0.43-2) unstable; urgency=medium . * 0001-gemspec-relax-dependencies.patch: make dependency on fog-core use >= instead of ~> (Closes: #891498) Checksums-Sha1: 1924e93ad18887e2e5e50d777337f45e437118ac 2310 vagrant-libvirt_0.0.43-2.dsc fd83e0a48f2aa3661a10051cb47950248bfcf173 4048 vagrant-libvirt_0.0.43-2.debian.tar.xz 015075b3940c8ee57fdfe6fa2fbc65fe79848658 9330 vagrant-libvirt_0.0.43-2_source.buildinfo Checksums-Sha256: 51b8fb23d923484a6a56c7f52fc8947068f699afc376b33d31b5baf932628d9f 2310 vagrant-libvirt_0.0.43-2.dsc 8590690edab1892e22e76e22c74f1a49e337da7de198c23997b369db42769a47 4048 vagrant-libvirt_0.0.43-2.debian.tar.xz a55dda886668aa4226e286fc30f613cfcb6cda887cf32f27d0c5a4572523a4c0 9330 vagrant-libvirt_0.0.43-2_source.buildinfo Files: ca992db6eb9e5e48a9f511322a99bd57 2310 ruby optional vagrant-libvirt_0.0.43-2.dsc 63684d5b8880174127612c1ca1856842 4048 ruby optional vagrant-libvirt_0.0.43-2.debian.tar.xz c69be71d1ee1142a12ac0be3546673a5 9330 ruby optional vagrant-libvirt_0.0.43-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlqUXRYACgkQ/A2xu81G C962jA/+OaMgL1aC+XemzerFXEGSd9fAatAGR+wO9GMXl6W5y2h89XC6iEV0Rf1a 4Zf9r7stdOKnqzqbdXMDfpILe328PSJhiN/r7tVmxjMHw2QhE6hwy5i4wLIKBCBO X7fiWZF477DdksSRR8EZLLs2mQ2lCNAOUDUW4cDxTmAtUmX3J3oPtYggdXzUULHv WlsLFGavPWGY6w8nXFyrjJfvztg19vaJaJW0DHz5B6bX84eQOnEXKz1k4tPX74Xm ag+m28iomWbzGgwvVKc3Fkn4k2HXxEx0qwU+lceQjlbnH+3adP23ucpxfd3D4bxp A/wYfzLuzO25YjNCqrzuGa23FBqy8vwB7A9B/bRWZC958NHlN12si9Ik7zvdv+ut i0aRtAXjo32jmS5tq4nGOf6C73iLeZyEnslYhtYuJ7vvqBj1Qke339xAse9WQaPu c+wEN0YPTR4ywtZsPLlcPeq/M4vMjnYwhjuKpoCm1nV4PHaUK4nd9WM89zDVioB6 5yjwqkhdzXPt4aMSgHH3gTSgtMUyHCIolvVT60KuwmQ6MGkzCf1V73CSWRW6aA1I yuhRPopTmOmrqUxbeaLzqprw7QyQRLYHmvJsseG84o6e6549Be+1mWjjOP3OTqHl cKYuodxOTCqZsJV0GBz1H6v2lwYngbUtd0iV32FLQi+oxP4tFKg= =NQV2 -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#889873: vagrant: unable to download images (moved from atlas.hashicorp.com to app.vagrantup.com)
Control: tag -1 + pending Control: block -1 by 891484 On Sat, Feb 10, 2018 at 01:39:33PM -0500, James McCoy wrote: > On Thu, Feb 08, 2018 at 09:02:03AM +0100, Lucas Nussbaum wrote: > > It seems that Hashicorp decided to migrate from e.g. > > https://atlas.hashicorp.com/alpine/alpine64 > > to > > https://app.vagrantup.com/alpine/boxes/alpine64 > > > > This breaks images download, making this package essentially > > unfortunately: > > > > $ vagrant init alpine/alpine64 > > A `Vagrantfile` has been placed in this directory. You are now > > ready to `vagrant up` your first virtual environment! Please read > > the comments in the Vagrantfile as well as documentation on > > `vagrantup.com` for more information on using Vagrant. > > A workaround is to change the default server URL in the Vagrantfile, as > suggested in the upstream bug report. > > https://github.com/hashicorp/vagrant/issues/9442#issuecomment-363080565 I prepared a stable update for this (#891484) signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted gem2deb 0.37 (source) into unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 25 Feb 2018 14:46:15 -0300
Source: gem2deb
Binary: gem2deb gem2deb-test-runner
Architecture: source
Version: 0.37
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
Changed-By: Antonio Terceiro
Description:
gem2deb- Debian Ruby packaging suite
gem2deb-test-runner - Debian Ruby packaging suite - tool to run tests
Changes:
gem2deb (0.37) unstable; urgency=medium
.
[ Georg Faerber ]
* debian/compat:
- Bump debhelper compat level to 11.
* debian/control:
- Add myself as uploader.
- Bump Standards-Version to 4.1.3, no changes needed.
- Bump required debhelper version to >= 11~.
- Use salsa.d.o in Vcs-{Browser,Git} fields.
- Drop obsolete Testsuite field.
* debian/copyright:
- Use HTTPS in link to copyright format spec.
- Point homepage link to salsa.d.o.
* dh-make-ruby:
- Bump Standards-Version to 4.1.3.
- Bump debhelper compat level to 11.
- Use salsa.d.o in Vcs-{Browser,Git} fields.
- Use HTTPS in link to copyright format spec.
.
[ Samuel Henrique ]
* dh-make-ruby:
- Use HTTPS in debian/watch template.
Checksums-Sha1:
e4117737a8cc560153e0517f78761af5b43a4ce3 2285 gem2deb_0.37.dsc
823ab316c0682976929daff66d1e6f8ec105872c 67628 gem2deb_0.37.tar.xz
48148c562ef6112fde820a1204923e836b8d95df 8997 gem2deb_0.37_source.buildinfo
Checksums-Sha256:
51f0109df581e93f282bc5ac4ced21b58fa4ed3f92c2df34e779604ab102c251 2285
gem2deb_0.37.dsc
b40ef1381bf343184cce08351e3f4eb41b5a538babaab4868c92ae5dafadee8c 67628
gem2deb_0.37.tar.xz
8e04ea64776d36f9c92130aef2918a58a3c4da6ce8a76754dc20961968028d5b 8997
gem2deb_0.37_source.buildinfo
Files:
7a6619bbdd5265e2b16bad590d8d0846 2285 ruby optional gem2deb_0.37.dsc
202a6036af6754c2fe1ec4149faa33ea 67628 ruby optional gem2deb_0.37.tar.xz
90bb5946a8a9e6a79060ad1da2e1e374 8997 ruby optional
gem2deb_0.37_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlqS9zQACgkQ/A2xu81G
C94BZw//brfiqeavr6GlbaInkCIF3FGkNA/GgVbIW4UCFgVLcMBos20Li0MfQ2eS
t9UGaA0ojKGTZ5TuQj4YOFJn2HA/xLfG76ThzIOBmZHGPfVkQL4CfM0gj2PFGYSU
KXzBDSXXP2zbQjpeNhahkVFQQPeuTYWFxnimAYsKeMrW6Z2fPtctN/38RxcEFdo3
xcWvb9apvbRFPlJdJLloInPGcbzMa2dtOID/1nWWmGLdaNHyhc8Ha6Y+TlKbphis
IYs4xqifqdsBNaK7/bQdtIpFGsoSKI9hRQhGhBUx872mkJZX+7gtH5LexDr3yrBT
SGnJN6dDTTpv8pXabq9GEjJD1KV3O4fzcktlP2NFWDKqmKEIjJFn+Y3aqhTUeUqV
ad2kvxrJ/SG01UTTQuZMptQBPAwonbKuAvMkvVeICygbAia+9lRaqmRu6pZI9oZ4
Knl9mg2INeZ/fbMVjUKytxfCmfmrG6OTMqWkZeIWUgALoywGpH90G3r9uekPdw8w
CXQwBy99cYKXyyt5jC7P4CIRGm97QNlFY8n19SuZ3/O+dG0mok00BRW3DbygDcMc
8iXASpHdBmvNyJ1RvA25unDQHu17OVczMBA9qVsbmmeUiT8XUj1MDm4CCfmuM/9R
V89pNqg1JCb7FoJD4g5JB37iwSDedrwLnPQ/YXOu7H5wsSpCcQ8=
=L6jJ
-END PGP SIGNATURE-
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted ruby-json 2.1.0+dfsg-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Feb 2018 14:33:06 -0300 Source: ruby-json Binary: ruby-json Architecture: source Version: 2.1.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Antonio Terceiro Description: ruby-json - JSON library for Ruby Changes: ruby-json (2.1.0+dfsg-2) unstable; urgency=medium . * Team upload. * Remove myself from Uploaders: * Disable jruby support (see #890046) * debian/watch: switch to https * debian/rules: build under C.UTF-8 locale Checksums-Sha1: 83adb57b816b4139c0315db21db429aee9236639 2115 ruby-json_2.1.0+dfsg-2.dsc 4d6344238b55d0cf53003bd3b849ba88ea8b2814 8780 ruby-json_2.1.0+dfsg-2.debian.tar.xz 30a08937cb0178fc53762c1991d6c5965e7eed3c 6650 ruby-json_2.1.0+dfsg-2_source.buildinfo Checksums-Sha256: 7cc205fce44409cef871d9b1cb62830aa7906c5a759409805b0ca648abb68668 2115 ruby-json_2.1.0+dfsg-2.dsc 370060b240c47de46e2ef7fc28e9e57a6abf7c00ba9bc3aef4c4f97aa2cb8b8c 8780 ruby-json_2.1.0+dfsg-2.debian.tar.xz 92cc9ccc9c4e9c238c84c17edcc344359f4e2f9518e8ff5f2de295722af49bc5 6650 ruby-json_2.1.0+dfsg-2_source.buildinfo Files: 65996d10544adeaf9bc01f9fe6bb0282 2115 ruby optional ruby-json_2.1.0+dfsg-2.dsc 8dcdb1195cd89a96a82c099759d6d10f 8780 ruby optional ruby-json_2.1.0+dfsg-2.debian.tar.xz f2a49a8dee01fa2e696f946c8cc21c8c 6650 ruby optional ruby-json_2.1.0+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlqS8+oACgkQ/A2xu81G C9449hAAhLNxhmsPy08To/eneHXkXq05hMB64V+MQbvXqwrBoVlrlRknE1SQK89i d8WLzkQsw1d8EU3T3JnuAMSgMaSsmrD81C3VAIi9dq62dlOpnSIEQNmRy6rUbekE cZRg+8+TZqqU1SEN0ncwSPebAbFWRmJ03tW75JPneDJSomaq94FT4EgHD3XwTwpT BzSSCBF/TAT+WtunZoFPkhEGqnSvwH7NoemRwNcW1md+w/MttYcAPSoFGxPph/CD p/PoV51xJYS/6tEvZuL0+lDrz2/rYUaAiaf+6DzFg9ToSP4ZrG1LseT4vCxUBS8P DFNBujoA/8xAGFMucmSus5wIYrog87elusoKy5KwtQa1HjA0ZVdONasLMoLL1kN+ zA9rqOXYtqNGvNQC+Rmk8i1AfMz67uzCkPfxA9Yy9ikI+d/GABHCdbKyGPo0a26r iCa3ShQmCYD/oXf07Ew2zwgL+3NT8z7kS77e9KTDsDAjUbjK9UwYb1zyfarGOZT7 AWFSS0Pt410QYT8Uamta7b4jcCi4+nuWPjW7WVuaLqsfmt+tDfaUp0e3kL9k02+Q fn9XwoWRn3/wurneJTgljqeUlY3vYtxxYbvG3qrHPUhxDoD5xvCX0j2M1qkWHv5R fGaN9707wBivZQd9egaum/CGFKZCSDz8heFDCxmdTMeucKAwdc8= =LW+7 -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#890046: ruby-json: disabling jruby support
Control: retitle -1 jruby support broken on several architectures Control: severity -1 normal Hi, ruby-json currently FTBFS, and is blocking the Ruby transition, as reported in bug #890046 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890046) All failures are related to the jruby support, but this same version has been in testing for ages, so somehow jruby became broken since then. In order to unblock the migration, I'm uploading ruby-json 2.1.0+dfsg-2 with the jruby support removed, because I don't have the cycles available to hunt down 3 different issues with jruby, including the fact that system() is broken on arm64 (#891449). However, I don't have anything against having jruby support back in once these issues have been fixed. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#890046: no build artifacts included in ruby-json, built for jruby
On Sat, 10 Feb 2018 15:04:25 +0100 Matthias Klose wrote: > there are no build artifacts included in ruby-json, built for jruby. Except > for > an additional README. yes, there are: $ dpkg -L ruby-json | grep jar /usr/lib/ruby/vendor_ruby/json/ext/generator.jar /usr/lib/ruby/vendor_ruby/json/ext/parser.jar signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Accepted ruby-thread-safe 0.3.6-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 23 Feb 2018 16:06:32 -0300 Source: ruby-thread-safe Binary: ruby-thread-safe Architecture: source Version: 0.3.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Antonio Terceiro Description: ruby-thread-safe - thread-safe collections and utilities for Ruby Changes: ruby-thread-safe (0.3.6-1) unstable; urgency=medium . * Team upload . [ Cédric Boutillier ] * Use https:// in Vcs-* fields * Run wrap-and-sort on packaging files . [ Antonio Terceiro ] * Remove myself from Uploaders: * New upstream version 0.3.6 * Refresh packaging files with `dh-make-ruby -w` * Bump Standards-Version to 4.1.3 (no changes needed) * Add ruby-simplecov and ruby-coveralls to Build-Depends, to avoid having to patch simplecov/coveralls usage out * Drop all patches, not needed anymore * Point Vcs-* to salsa * debian/watch: switch to https:// Checksums-Sha1: 3da34175c6318c7a1872f2b9752abf5be8952251 2135 ruby-thread-safe_0.3.6-1.dsc 25b768427ddaed570dbc3f23e7f8f17ab038d5e1 117999 ruby-thread-safe_0.3.6.orig.tar.gz 0781d248d0c8ff4d73b302206d62b1df1c24b42c 5684 ruby-thread-safe_0.3.6-1.debian.tar.xz 9d001a2755a0f5c8e76f544b7b723d73aae9082c 7599 ruby-thread-safe_0.3.6-1_source.buildinfo Checksums-Sha256: 23051a85263ce2e6e64cfd524cd5182252297f62e00c02fd43067471bbcc05ba 2135 ruby-thread-safe_0.3.6-1.dsc 1c7c3cc2511df5107d26012eb641c16a4afdf2bfef6cf2ba19d721e6ab74b62a 117999 ruby-thread-safe_0.3.6.orig.tar.gz ed84f2afa59aff5490978e3d9194d88502eaa67f0c117203183a2cdfd11761ef 5684 ruby-thread-safe_0.3.6-1.debian.tar.xz 04b81d64d24ef484ab78e64fb3830338c6c97b245d461e5bc7c6ffb3f979fc01 7599 ruby-thread-safe_0.3.6-1_source.buildinfo Files: 7f00b1c308eced154450c6aedb395cef 2135 ruby optional ruby-thread-safe_0.3.6-1.dsc 6259bf7dd2ef49dd191f182cfc730204 117999 ruby optional ruby-thread-safe_0.3.6.orig.tar.gz f3fa7c12b7da707b6dc83394d32894b0 5684 ruby optional ruby-thread-safe_0.3.6-1.debian.tar.xz 6b679194b153f0a2624235a9b44f206b 7599 ruby optional ruby-thread-safe_0.3.6-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlqQaGoACgkQ/A2xu81G C96oDw//WxviHppo2p4byrqzRP/X3SxAUo5kjmtU4srcffcBNi41S/biXk2AybHL UKp13m9G6eBpRUsEs6SO/Gq3zTWyKvReXA1Qy2mn+WtSiq9DH3D3Y7Gf/xfoo0Xc XIycB18RgE6CSmVua5AmZ99aigKLh43dFUk/43xFKoKkeRhhg0Scig0eVTx4/kxN CYqfbqiTRHnm6OYDQSZpapvW16a1xkA63rKNL9/+AjY714qgSf6uOXGylDjH4ltO Akj1VvO7dODfqgOBHp9EHKNwYK5lMr9PnXxoa8gBilu8jry7QqbmT9K31fxc4j8x NShiMKDl8Rsfg1Dqg7Ilw1FGzlpwc4wAaKKvEf8Gy1CrNd66205wEynQeKrbUhDC kxguzRP+Y2gCp1kK4Ncq74QxwRsNPTzFHWClWUmiFaJOZ4KF2rc194XNNlShmrEx owkWURDPsHeSpns2h+tKMXFt2puswJIZRHDuoHGqBvGXRyVyz3h8ZSbMIejnsrAo 2Bat5hnoH5abERpvAVgYJ311x9o4Ps8z69VCa+JKDxUd8LA8xgmrdgGU6TbB7iqq eVEIo3tQqytHd8o0JUJYEDFbZf/4pwHuuHhMjeCvSH4lbV3/IfsQP9ahbmhkTtBw L50PjXnTmhOsLOuvrb2VHnAm+IegNxvfW3CH4Oo/kHGLxf4/EJI= =kQmx -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#889021: ruby-ffi-yajl: FTBFS with ruby2.5: 'rb_cFixnum' undeclared
Source: ruby-ffi-yajl Severity: serious Justification: Fails to build from source User: debian-r...@lists.debian.org Usertags: ruby2.5 I am filing this at severity serious as I am about to enable building for ruby2.5 in unstable. ┌──┐ │ Build native extensions for ruby2.5 │ └──┘ /usr/bin/ruby2.5 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb /<> debian/ruby-ffi-yajl "make clean" make[2]: Entering directory '/<>/ext/ffi_yajl/ext/dlopen' make[2]: Leaving directory '/<>/ext/ffi_yajl/ext/dlopen' "make clean" make[2]: Entering directory '/<>/ext/ffi_yajl/ext/dlopen' make[2]: Leaving directory '/<>/ext/ffi_yajl/ext/dlopen' current directory: /<>/ext/ffi_yajl/ext/dlopen /usr/bin/ruby2.5 -r ./siteconf20180131-9818-r8yepd.rb extconf.rb -g -O2 -fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -L. -Wl,-z,relro -Wl,-z,now -fstack-protector -rdynamic -Wl,-export-dynamic checking for dlfcn.h... yes checking for dlopen() in -ldl... yes creating Makefile current directory: /<>/ext/ffi_yajl/ext/dlopen make V=1 "DESTDIR=" clean make[2]: Entering directory '/<>/ext/ffi_yajl/ext/dlopen' rm -f rm -f dlopen.so *.o *.bak mkmf.log .*.time make[2]: Leaving directory '/<>/ext/ffi_yajl/ext/dlopen' current directory: /<>/ext/ffi_yajl/ext/dlopen make V=1 "DESTDIR=" make[2]: Entering directory '/<>/ext/ffi_yajl/ext/dlopen' gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 -I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. -DHAVE_DLFCN_H -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -g -O2 -fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -o dlopen.o -c dlopen.c rm -f dlopen.so gcc -shared -o dlopen.so dlopen.o -L. -L/usr/lib/x86_64-linux-gnu -L. -Wl,-z,relro -Wl,-z,now -fstack-protector -rdynamic -Wl,-export-dynamic -Wl,-z,relro -Wl,-z,now -Wl,--compress-debug-sections=zlib-lruby-2.5 -ldl -lpthread -lgmp -ldl -lcrypt -lm -lc make[2]: Leaving directory '/<>/ext/ffi_yajl/ext/dlopen' current directory: /<>/ext/ffi_yajl/ext/dlopen make V=1 "DESTDIR=" install make[2]: Entering directory '/<>/ext/ffi_yajl/ext/dlopen' /bin/mkdir -p . ./.gem.20180131-9818-oj2q1e/ffi_yajl/ext exit > .sitearchdir.-.ffi_yajl.-.ext.time /usr/bin/install -c -m 0755 dlopen.so ./.gem.20180131-9818-oj2q1e/ffi_yajl/ext make[2]: Leaving directory '/<>/ext/ffi_yajl/ext/dlopen' rm -f /<>/debian/ruby-ffi-yajl/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.5.0/mkmf.log "make clean" make[2]: Entering directory '/<>/ext/ffi_yajl/ext/encoder' make[2]: Leaving directory '/<>/ext/ffi_yajl/ext/encoder' "make clean" make[2]: Entering directory '/<>/ext/ffi_yajl/ext/encoder' make[2]: Leaving directory '/<>/ext/ffi_yajl/ext/encoder' current directory: /<>/ext/ffi_yajl/ext/encoder /usr/bin/ruby2.5 -r ./siteconf20180131-9818-17gzwda.rb extconf.rb -g -O2 -fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -L. -Wl,-z,relro -Wl,-z,now -fstack-protector -rdynamic -Wl,-export-dynamic checking for yajl/yajl_tree.h... yes creating Makefile current directory: /<>/ext/ffi_yajl/ext/encoder make V=1 "DESTDIR=" clean make[2]: Entering directory '/<>/ext/ffi_yajl/ext/encoder' rm -f rm -f encoder.so *.o *.bak mkmf.log .*.time make[2]: Leaving directory '/<>/ext/ffi_yajl/ext/encoder' current directory: /<>/ext/ffi_yajl/ext/encoder make V=1 "DESTDIR=" make[2]: Entering directory '/<>/ext/ffi_yajl/ext/encoder' gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 -I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -g -O2 -fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -o encoder.o -c encoder.c encoder.c: In function 'Init_encoder': encoder.c:380:20: error: 'rb_cFixnum' undeclared (first use in this function); did you mean 'rb_isalnum'? rb_define_method(rb_cFixnum, "ffi_yajl", rb_cFixnum_ffi_yajl, 2); ^~ rb_isalnum encoder.c:380:20: note: each undeclared identifier is reported only once for each function it appears in encoder.c:381:20: error: 'rb_cBignum' undeclared (first use in this function); did you mean 'rb_cFixnum'? rb_define_method(rb_cBignum, "ffi_yajl", rb_cBignum_ffi_yajl, 2); ^~ rb_cFixnum Makefile:242: recipe for target 'encoder.o' failed make[2]: *** [encoder.o] Error 1 make[2]: Leaving directory '/<>/ext/ffi_yajl/ext/encoder' ~ ↓ mkmf.log ~ find_header: checking for yajl/yajl_tree.h... yes "gcc -o conftest -I/usr/include/x86_64-linux-gnu/ruby-2.5
[DRE-maint] Bug#882361: ruby-bundler: phones home and recommends `gem install`
Package: ruby-bundler Version: 1.15.1-1 Severity: normal The latest bundler is 1.16.0, but you are currently running 1.15.1. To update, run `gem install bundler` 8<8<8<- $ cat Gemfile source 'https://rubygems.org' system 'find /tmp/bundler' gem 'rake' $ bundle --local find: ‘/tmp/bundler’: No such file or directory find: ‘/tmp/bundler’: No such file or directory find: ‘/tmp/bundler’: No such file or directory Using rake 12.0.0 Using bundler 1.15.1 Bundle complete! 1 Gemfile dependency, 2 gems now installed. Use `bundle info [gemname]` to see where a bundled gem is installed. The latest bundler is 1.16.0, but you are currently running 1.15.1. To update, run `gem install bundler` 8<8<8<- Note the last two line. bundler is hitting the internet to check for a newer version, which is already not OK, and it is and asking the user to override the Debian package with `gem install bundler`. This should be patched out. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ruby-bundler depends on: ii ruby 1:2.3.3 ii ruby-molinillo0.5.0-2 ii ruby-net-http-persistent 2.9.4-1 ii ruby-thor 0.19.4-1 ii rubygems-integration 1.11 ruby-bundler recommends no packages. ruby-bundler suggests no packages. -- no debconf information signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
Re: [DRE-maint] Wheezy update of ruby-yajl?
On Tue, Nov 07, 2017 at 07:11:06PM +0100, Ola Lundqvist wrote: > Dear maintainers, > > The Debian LTS team would like to fix the security issues which are > currently open in the Wheezy version of ruby-yajl: > https://security-tracker.debian.org/tracker/CVE-2017-16516 > > Would you like to take care of this yourself? I don't have plans to work on this. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#846083: autopkgtest fails HandlebarsAssets::HandlebarsProcessorTest#test_render
On Mon, Nov 28, 2016 at 05:05:39PM +0530, Pirate Praveen wrote: > package: ruby-handlebars-assets > version: 1:0.23.1-1 > severity: important > > RUBYLIB=. GEM_PATH= ruby2.3 -S rake -f debian/ruby-tests.rake > Run options: --seed 29929 this tests flapping on ci.debian.net are very annoying. I took a quick look, and my guess is that the test suite is broken and will fail depending on the order in which test runs are executed. Fixing the random seed for the test suite should fix this. Please consider applying the attached patch diff -Nru ruby-handlebars-assets-0.23.2.orig/debian/ruby-tests.rake ruby-handlebars-assets-0.23.2/debian/ruby-tests.rake --- ruby-handlebars-assets-0.23.2.orig/debian/ruby-tests.rake 2017-09-30 07:45:44.0 -0300 +++ ruby-handlebars-assets-0.23.2/debian/ruby-tests.rake 2017-10-03 15:17:58.81880 -0300 @@ -1,3 +1,7 @@ +# tests fail randomly depending on which order they are executed; They should +# always pass with a fixed seed, and this one is known to work: +ENV['SEED'] = 61834 + require 'rake/testtask' Rake::TestTask.new(:test) do |test| test.libs << '/usr/lib/ruby/vendor_ruby' @@ -7,11 +11,4 @@ test.warning = false end -# Run only autopkgtests -if ENV['ADTTMP'].nil? - task :default do -puts 'skipping tests (run only as autopkgtest)' - end -else - task :default => [:test] -end +task :default => [:test] signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
Re: [DRE-maint] Wheezy update of rbenv?
On Sat, Jul 22, 2017 at 06:24:45PM +0200, Guido Günther wrote: > Dear maintainer, > > (This is rather low impact so tagging no-dsa would be fine too but I > wanted to check with you guys first). > > The Debian LTS team would like to fix the security issue which is > currently open in the Wheezy version of rbenv: > https://security-tracker.debian.org/tracker/CVE-2017-147 > > Would you like to take care of this yourself? sorry, I don't have enough bandwidth to handle wheezy. That said, rbenv is a development tool, used to switch between different locally-installed versions of the Ruby interpreter. I doubt anyone is using rbenv from Debian on wheezy ... did any of LTS sponsors actually demonstrated interest in this? If not, I think this wouldn't be a good use or your time either. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#869253: vagrant-libvirt: Unable to resolve dependency to latest ruby-nokogiri 1.8.0
Control: close -1 0.0.40-1 On Sat, Jul 22, 2017 at 10:57:01AM +0900, Kentaro Hayashi wrote: > Package: vagrant-libvirt > Version: 0.0.37-1 > Severity: normal > > Dear Maintainer, > >* What led up to the situation? > > Recently, ruby-nokogiri package is updated from 1.6.0.1 to 1.8.0. > It causes broken dependency to use vagrant. > >* What exactly did you do (or not do) that was effective (or > ineffective)? > > I already installed vagrant-libvirt, then apt update (ruby-nokogiri > was updated). > After upgrading packages, then do the following command. > > $ vagrant status > >* What was the outcome of this action? > > $ vagrant status > Vagrant failed to initialize at a very early stage: > > The plugins failed to initialize correctly. This may be due to manual > modifications made within the Vagrant home directory. Vagrant can > attempt to automatically correct this issue by running: > >vagrant plugin repair > > If Vagrant was recently updated, this error may be due to incompatible > versions of dependencies. To fix this problem please remove and > re-install > all plugins. Vagrant can attempt to do this automatically by running: > >vagrant plugin expunge --reinstall > > Error message given during initialization: Unable to resolve dependency: > 'vagrant-libvirt (> 0)' requires 'nokogiri (~> 1.6.0)' > >* What outcome did you expect instead? > > vagrant-libvirt supports ruby-nokogiri 1.8.0 or later and > > $ vagrant status works. > > It seems that runtime dependency issue will not be resolved even though > newer 0.0.40 package is shipped This was explicitly patched in 0.0.40-1. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#867599: gem2deb fails to install pure ruby part when a gem has both pure ruby and native libs
On Sat, Jul 08, 2017 at 11:15:04AM -0300, Antonio Terceiro wrote: > Control: severity -1 wishlist > Control: retitle -1 gem2deb: support installing Ruby code not in lib/ > > On Sat, Jul 08, 2017 at 01:48:19PM +0530, Pirate Praveen wrote: > > On 07/08/2017 11:53 AM, Pirate Praveen wrote: > > > On 07/08/2017 07:44 AM, Antonio Terceiro wrote: > > >> if the pure ruby libraries were not being installed, you would get a > > >> LoadError (i.e. a `require` statement failed), but that's not what is > > >> happening here. > > > For tests, the pure ruby libs are available in the source tree. > > > > > > If I move the src/ruby/lib folder (I have locally installed ruby-grpc > > > deb), then it fails with `require': cannot load such file -- grpc > > > (LoadError) > > > > I think gem2deb expects libraries only in lib. > > From what I see from the source code, grpc is a library with multiple > language bindings; packaging it as a Ruby package is wrong. there is > even already a grpc source package in Debian. you should send a patch to > that package to generate a ruby-grpc binary package from there, instead > of creating a new ruby-specific package. > > your ruby-grpc has a lot of embedded code copies under third_party/, > which has been already solved in grpc source package. > > also, we can't possibly make gem2deb "just work" in such packages > because they deviate a lot from what a standard ruby package looks like. > > > s.require_paths = %w( src/ruby/lib src/ruby/bin src/ruby/pb ) mentions > > it in grpc.gemspec but I don't know if gem2deb can reply on that. > > gem2deb could be made to work with it, but I don't expect to get to it > any time soon. Thinking about it, we kind of already support this: when you use --gem-install, this typo of thing should Just Work™. > For now, I suggest that you > > - drop your ruby-grpc > - send a patch to the existing grpc source to produce a ruby-grcp binary > from it I suggest that you use --gem-install when sending your patch to grpc, it should do the right thing. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#867599: gem2deb fails to install pure ruby part when a gem has both pure ruby and native libs
Control: severity -1 wishlist Control: retitle -1 gem2deb: support installing Ruby code not in lib/ On Sat, Jul 08, 2017 at 01:48:19PM +0530, Pirate Praveen wrote: > On 07/08/2017 11:53 AM, Pirate Praveen wrote: > > On 07/08/2017 07:44 AM, Antonio Terceiro wrote: > >> if the pure ruby libraries were not being installed, you would get a > >> LoadError (i.e. a `require` statement failed), but that's not what is > >> happening here. > > For tests, the pure ruby libs are available in the source tree. > > > > If I move the src/ruby/lib folder (I have locally installed ruby-grpc > > deb), then it fails with `require': cannot load such file -- grpc > > (LoadError) > > I think gem2deb expects libraries only in lib. From what I see from the source code, grpc is a library with multiple language bindings; packaging it as a Ruby package is wrong. there is even already a grpc source package in Debian. you should send a patch to that package to generate a ruby-grpc binary package from there, instead of creating a new ruby-specific package. your ruby-grpc has a lot of embedded code copies under third_party/, which has been already solved in grpc source package. also, we can't possibly make gem2deb "just work" in such packages because they deviate a lot from what a standard ruby package looks like. > s.require_paths = %w( src/ruby/lib src/ruby/bin src/ruby/pb ) mentions > it in grpc.gemspec but I don't know if gem2deb can reply on that. gem2deb could be made to work with it, but I don't expect to get to it any time soon. For now, I suggest that you - drop your ruby-grpc - send a patch to the existing grpc source to produce a ruby-grcp binary from it signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#867533: test failure when updating to 3.9.0
On Sat, Jul 08, 2017 at 11:59:00AM +0530, Pirate Praveen wrote: > On 07/08/2017 07:47 AM, Antonio Terceiro wrote: > > > > This seems wrong. If you get a failure after trying to update the > > package to 3.9.0, by definition the bug cannot be against version 3.8.2 > > (which does not exist in Debian BTW, you missed the Debian revision > > number). > > > > IMO the BTS should be used for bugs that are not present in the Debian > > archive. > > But we do file bugs to updating new upstream releases against the > existing versions. How this is different? If I retitle the bug to > "update to latest upstream release", would it be okay? It would sound better, yes. "the version in the archive is not recent enough" is an issue with a package that is in debian; "this new version that is not in the archive does not work" is not. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#867533: test failure when updating to 3.9.0
On Fri, Jul 07, 2017 at 10:32:53AM +0530, Pirate Praveen wrote: > package: ruby-parser > version: 3.8.2 > > When trying to update ruby-parser to latest upstream release (3.9.0), > tests failed. Log below. This seems wrong. If you get a failure after trying to update the package to 3.9.0, by definition the bug cannot be against version 3.8.2 (which does not exist in Debian BTW, you missed the Debian revision number). IMO the BTS should be used for bugs that are not present in the Debian archive. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#867599: gem2deb fails to install pure ruby part when a gem has both pure ruby and native libs
Control: tag -1 + moreinfo On Fri, Jul 07, 2017 at 10:43:20PM +0530, Pirate Praveen wrote: > package: gem2deb > version: 0.34 > > gem2deb is not installing the pure ruby libraries of grpc (ruby-grpc is > in alioth) and tests fail. yes it is installing the pure ruby libraries > ──┐ > │ Run tests for ruby2.3 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-grpc/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0:. > GEM_PATH=debian/ruby-grpc/usr/share/rubygems-integration/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all > ruby2.3 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby2.3 /usr/bin/rspec --pattern > ./src/ruby/spec/\*\*/\*_spec.rb --format documentation > /<>/src/ruby/lib/grpc/errors.rb:48:in `': > uninitialized constant GRPC::Core (NameError) if the pure ruby libraries were not being installed, you would get a LoadError (i.e. a `require` statement failed), but that's not what is happening here. gem2deb does install the Ruby code even when there is a C extension, and there are several automated tests for that. If it didn't, we wouldn't be learning that this late in the game. I don't think this is a bug in gem2deb, but you can convince me otherwise. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
Re: [DRE-maint] ruby-openssl_2.0.4-1_amd64.changes REJECTED
On Sun, Jul 02, 2017 at 05:00:09PM +, Thorsten Alteholz wrote: > > requested by maintainer .. ACK; I have just uploaded a fixed package thanks signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
Re: [DRE-maint] ruby-openssl_2.0.4-1_amd64.changes is NEW
On Sun, Jul 02, 2017 at 10:31:59AM -0300, Antonio Terceiro wrote: > On Sat, Jul 01, 2017 at 11:39:28PM +, Debian FTP Masters wrote: > > binary:ruby-openssl is NEW. > > binary:ruby-openssl is NEW. > > source:ruby-openssl is NEW. > > Hi, > > I just realized I missed a few copyright holders in debian/copyright. I intend > to upload a -2 with the following changes right after the pacakge is accepted > (or if it's rejected): Not only that, it was also missing an alternate license. The full change I have the following diff staged in git for the next upload (or another NEW upload): diff --git a/debian/copyright b/debian/copyright index 2847877..561e9ee 100644 --- a/debian/copyright +++ b/debian/copyright @@ -3,12 +3,16 @@ Upstream-Name: openssl Source: https://https://github.com/ruby/openssl Files: * -Copyright: © Yukihiro Matsumoto . -License: Ruby +Copyright: © Yukihiro Matsumoto + © 2000-2003 GOTOU Yuuzou + © 2010 Hiroshi Nakamura + © 2001-2003 Michal Rokos + © 2004-2007 Technorama Ltd. +License: Ruby or BSD-2-clause Files: debian/* Copyright: 2017 Antonio Terceiro -License: Ruby +License: Ruby or BSD-2-clause Comment: the Debian packaging is licensed under the same terms as the original package. License: Ruby @@ -67,3 +71,25 @@ License: Ruby IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. + +License: BSD-2-clause + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions + are met: + 1. Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + 2. Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. + . + THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND + ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE + FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + SUCH DAMAGE. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
Re: [DRE-maint] ruby-openssl_2.0.4-1_amd64.changes is NEW
On Sat, Jul 01, 2017 at 11:39:28PM +, Debian FTP Masters wrote: > binary:ruby-openssl is NEW. > binary:ruby-openssl is NEW. > source:ruby-openssl is NEW. Hi, I just realized I missed a few copyright holders in debian/copyright. I intend to upload a -2 with the following changes right after the pacakge is accepted (or if it's rejected): diff --git a/debian/copyright b/debian/copyright index 2847877..a2f694e 100644 --- a/debian/copyright +++ b/debian/copyright @@ -3,7 +3,11 @@ Upstream-Name: openssl Source: https://https://github.com/ruby/openssl Files: * -Copyright: © Yukihiro Matsumoto . +Copyright: © Yukihiro Matsumoto + © 2000-2003 GOTOU Yuuzou + © 2010 Hiroshi Nakamura + © 2001-2003 Michal Rokos + © 2004-2007 Technorama Ltd. License: Ruby signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#866198: this patch fixed dh-make-ruby
On Wed, Jun 28, 2017 at 01:19:02PM +0530, Pirate Praveen wrote:
>
> After comparing citrus.gemspec, this patch made dh-make-ruby to work.
> I'm not sure if original gemspec is valid ruby syntax.
>
> diff -ru mustermann-1.0.0/mustermann.gemspec
> mustermann-1.0.0+debian/mustermann.gemspec
> --- mustermann-1.0.0/mustermann.gemspec 2017-06-28 12:54:46.0
> +0530
> +++ mustermann-1.0.0+debian/mustermann.gemspec2017-06-28
> 13:10:06.138765241 +0530
> @@ -1,4 +1,4 @@
> -$:.unshift File.expand_path("../lib", __FILE__)
> +$:.unshift(File.expand_path("../lib", __FILE__))
AFAICS these lines have exactly the same effect.
I also don't get how exactly this is a bug in gem2deb.
signature.asc
Description: PGP signature
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#865667: ruby-prof FTBFS: ERROR: Test "ruby2.3" failed.
Control: tag -1 + unreproducible Control: severity -1 important On Fri, Jun 23, 2017 at 06:36:37PM +0300, Adrian Bunk wrote: > Source: ruby-prof > Version: 0.16.2+dfsg-2 > Severity: serious > Tags: buster sid > > Some recent change in unstable makes ruby-prof FTBFS: > > https://tests.reproducible-builds.org/debian/history/ruby-prof.html > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-prof.html > > ... I just tried 10 times in a row here with sbuild, and all of them built succesfully. can you try again? signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#861676: ruby-prof: broken symlink: /usr/share/doc/ruby-prof/fonts/Lato-RegularItalic.ttf -> ../../../fonts/truetype/lato/Lato-RegularItalic.ttf
Control: severity -1 normal Hi, On Tue, May 02, 2017 at 05:23:34PM +0200, Andreas Beckmann wrote: > Package: ruby-prof > Version: 0.16.2+dfsg-2 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package ships (or creates) > a broken symlink. > > >From the attached log (scroll to the bottom...): > > 0m20.4s ERROR: FAIL: Broken symlinks: > /usr/share/doc/ruby-prof/fonts/Lato-RegularItalic.ttf -> > ../../../fonts/truetype/lato/Lato-RegularItalic.ttf > > ^^ > > The fonts-lato package ships > > /usr/share/fonts/truetype/lato/Lato-Italic.ttf >^^^ > instead. Can you clarify exactly why you think a dangling symlink should warrant severity serious? signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#860747: dh_ruby: please inject versioned dependency on ruby metapackage
Control: reopen -1 Control: reassign -1 ruby-all-dev Control: retitle -1 ruby-all-dev: include upper bound on generated ruby dependencies On Wed, Apr 19, 2017 at 03:53:57PM -0400, Aaron M. Ucko wrote: > Hi, Antonio. Thanks for the quick response! > > Antonio Terceiro writes: > > > ruby-fast-xs is broken on m68k because it is a very old binary, from before > > this was implemented, and AFAICT it can't be built anymore because something > > else is not available. > > The ruby-fast-xs version in play at the time (now superseded by a +b3 > build against ruby 2.3) had, per > https://buildd.debian.org/status/fetch.php?pkg=ruby-fast-xs&arch=m68k&ver=0.8.0-3%2Bb2&stamp=1456486333&raw=0, > > Depends: libc6 (>= 2.1.3), libgmp10, libruby2.2 (>= 2.2.0~1), ruby (>= 1:2.2) > > However, there was (and still is) no upper bound on the ruby > metapackage's version, allowing for mismatches. Ah fair enough, I missed that bit. These dependencies are specified in ruby-all-dev, so I am reassigning accordingly. It should be just a matter of including the << dependency there. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#859463: ruby-unf-ext FTBFS on ppc64el: unf/table.hh:13539:25: error: narrowing conversion of '-52' from 'int' to 'char' inside { } [-Wnarrowing]
On Tue, Apr 04, 2017 at 02:26:00PM +, Niels Thykier wrote:
> On Mon, 03 Apr 2017 23:38:48 +0300 Adrian Bunk wrote:
> > Source: ruby-unf-ext
> > Version: 0.0.7.2-2
> > Severity: serious
> >
> > ruby-unf-ext FTBFS on ppc64el (originally reported by Frederic Bonnard):
> >
> > ...
> > unf/table.hh:13539:25: error: narrowing conversion of '-51' from 'int' to
> > 'char' inside { } [-Wnarrowing]
> > unf/table.hh:13539:25: error: narrowing conversion of '-123' from 'int' to
> > 'char' inside { } [-Wnarrowing]
> > unf/table.hh:13539:25: error: narrowing conversion of '-50' from 'int' to
> > 'char' inside { } [-Wnarrowing]
> > unf/table.hh:13539:25: error: narrowing conversion of '-105' from 'int' to
> > 'char' inside { } [-Wnarrowing]
> > unf/table.hh:13539:25: error: narrowing conversion of '-52' from 'int' to
> > 'char' inside { } [-Wnarrowing]
> > ...
> >
> >
> > Complete log is attached.
>
> This is caused by ppc64el having "char" being unsigned by default.
> Beyond the table that needs to be converted/dealt with, there are about
> 20 -Wsign-conversion issues in the code that smells like they may cause
> issues as well.
>
> That said, a short term fix may be to revert:
> https://github.com/knu/ruby-unf_ext/commit/1e2d2bc29798342ab2616eb3d74ea36c793a33e4
Nope. That was actually done after the current upstream release that we
have in Debian, actually tyring to _fix_ the issue. The actual fix comes
a little later in
https://github.com/knu/ruby-unf_ext/commit/8a6a735b51ef903200fc541112e35b7cea781856
I even proposed to revert that:
https://github.com/knu/ruby-unf_ext/pull/27
Upstream seems to be cooking a new release, to be released at any time
now I assume. With or without that special case for ARM, the code buids
OK under ppc64el.
I will probably upload that, since the resulting upstream diff looks
quite unproblematic (if they accept my proposal, the chunk for
ext/unf_ext/extconf.rb will disappear from the final diff):
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8c20624..60c99a6 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,7 @@
+## 0.0.7.3 (2017-04-06)
+
+- Fix compile issues on ARM and GCC 6.
+
## 0.0.7.2 (2016-02-01)
- Version bump just for adding Windows binaries for Ruby 2.3.
diff --git a/ext/unf_ext/extconf.rb b/ext/unf_ext/extconf.rb
index 9068085..746d7ca 100644
--- a/ext/unf_ext/extconf.rb
+++ b/ext/unf_ext/extconf.rb
@@ -6,6 +6,17 @@ else
have_library('stdc++')
end
+case RUBY_PLATFORM
+when /\Aarm/
+ # A quick fix for char being unsigned by default on ARM
+ if defined?($CXXFLAGS)
+$CXXFLAGS << ' -fsigned-char'
+ else
+# Ruby < 2.0
+$CFLAGS << ' -fsigned-char'
+ end
+end
+
create_makefile 'unf_ext'
unless CONFIG['CXX']
diff --git a/ext/unf_ext/unf/normalizer.hh b/ext/unf_ext/unf/normalizer.hh
index b19b99c..d20244b 100644
--- a/ext/unf_ext/unf/normalizer.hh
+++ b/ext/unf_ext/unf/normalizer.hh
@@ -17,9 +17,9 @@ namespace UNF {
public:
Normalizer()
- : nf_d(TABLE::NODES, TABLE::CANONICAL_DECOM_ROOT, TABLE::STRINGS),
- nf_kd(TABLE::NODES, TABLE::COMPATIBILITY_DECOM_ROOT, TABLE::STRINGS),
- nf_c(TABLE::NODES, TABLE::CANONICAL_COM_ROOT, TABLE::STRINGS),
+ : nf_d(TABLE::NODES, TABLE::CANONICAL_DECOM_ROOT, (const char
*)TABLE::STRINGS),
+ nf_kd(TABLE::NODES, TABLE::COMPATIBILITY_DECOM_ROOT, (const char
*)TABLE::STRINGS),
+ nf_c(TABLE::NODES, TABLE::CANONICAL_COM_ROOT, (const char
*)TABLE::STRINGS),
nf_c_qc(TABLE::NODES, TABLE::NFC_ILLEGAL_ROOT),
nf_kc_qc(TABLE::NODES, TABLE::NFKC_ILLEGAL_ROOT),
ccc(TABLE::NODES, TABLE::CANONICAL_CLASS_ROOT)
diff --git a/ext/unf_ext/unf/table.hh b/ext/unf_ext/unf/table.hh
index 2b45703..ecfe147 100644
--- a/ext/unf_ext/unf/table.hh
+++ b/ext/unf_ext/unf/table.hh
@@ -6297,7 +6297,7 @@ const unsigned NODES[]={
0xFF00,0xFF00,0xFF00,0xFF00,0xFF00,0xFF00,0xFF00,0xFF00,0xFF00,0xFF00,
0xFF00,0xFF00,0xFF00,0xFF00,0xFF00};
-const char STRINGS[]={
+const signed char STRINGS[]={
-27,-113, -81, -27, -66,-105, -27,-106, -74, -25,-108, -77, -26, -70,-128,
-27,-112,-120, -25, -87,
-70, -25, -90,-127, -26,-116,-121, -23,-127,-118, -26,-115,-107,
-26,-118,-107, -26, -68,-108, -27,
-112, -71, -27, -93, -80, -24, -78, -87, -25, -75,-126, -27,-120, -99,
-26,-106, -80, -27, -66,-116,
diff --git a/lib/unf_ext/version.rb b/lib/unf_ext/version.rb
index f9d0c50..7c77497 100644
--- a/lib/unf_ext/version.rb
+++ b/lib/unf_ext/version.rb
@@ -1,5 +1,5 @@
module UNF
class Normalizer
-VERSION = "0.0.7.2"
+VERSION = "0.0.7.3"
end
end
diff --git a/unf_ext.gemspec b/unf_ext.gemspec
index 28f6eda..c00426c 100644
--- a/unf_ext.gemspec
+++ b/unf_ext.gemspec
@@ -25,15 +25,16 @@ Gem::Specification.new do |gem|
]
if RUBY_VERSION < "1.9"
+gem.add_development_dependency("rake", [">= 0.9.2.2", "< 11"])
gem.add_development_dependency('i18n', '< 0.7.0')
# Cap dependency on activesupp
[DRE-maint] Bug#834686: ruby-httpclient: diff for NMU version 2.7.1-1.1
On Wed, Mar 29, 2017 at 10:08:11PM +0200, Paul Gevers wrote: > Control: tags 834686 + patch > > Dear maintainer, > > I've prepared an NMU for ruby-httpclient (versioned as 2.7.1-1.1). The > diff is below (sorry for in-line, nmudiff failed to work properly for me). > > Due to the nature of the bug and the current freeze, I'll upload after > sending this e-mail. Thanks! I have imported your .dsc on top of the git repository. Are you also going to request the unblock, or do you want me to do it? signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#858195: compass-bootstrap-sass-plugin: Wrong install path, and code not registered with Compass
Control: severity -1 important On Wed, Mar 29, 2017 at 03:51:50PM +0200, Jonas Smedegaard wrote: > Quoting Antonio Terceiro (2017-03-28 20:01:37) > > Control: severity -1 wishlist > [...] > > While I agree with you that it _could_ work transparently, there is > > nothing broken in the package. And I don't think this is something we > > should be doing different from upstream. > > Do you still believe there was nothing broken in the package? No. Actually, it was _you_ who said that the original invocation as documented by upstream worked with the version in testing: $ compass create --using bootstrap-sass --require bootstrap-sass I tested that again, and it turns out it doesn't. > Please consider acknowledging that the former path was buggy, so that > there is a chance of getting a fix included with Stretch. Sure. I was going to request an unblock either way. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#858195: compass-bootstrap-sass-plugin: Wrong install path, and code not registered with Compass
On Wed, Mar 29, 2017 at 10:21:26AM +0200, Jonas Smedegaard wrote: > Quoting Antonio Terceiro (2017-03-29 03:16:32) > > That said, I am willing to support this, but I don't agree it's an RC > > issue. > > > > I tried changing /usr/share/compass/frameworks/bootstrap-sass to > > /usr/share/compass/frameworks/bootstrap as you said, but that doesn't > > exactly make it work: > [...] > > > Any ideas? > > Attached patch is what I use. It might not apply as-is - I use it > together with a couple other patches to address the other issues > mentioned initially in this bugreport about the odd packaging into two > binary packages. Ah, I see. this patch is needed to workaround the "old" Ruby installation layout. Most Ruby packages nowadays, specially the ones related to static assets, kind of assume the Rubygems layout, which is supported by our tools, and could even be the default at some point. If you need similar patches in all compass packages, you might be interested in switching to the Rubygems layout. With that you just symlink the Rubygems package location into the compass directory and things just work. Something link this: version = $(shell dpkg-parsechangelog -SVersion | cut -d - -f 1) override_dh_auto_install: dh_auto_install dh_link -p compass-bootstrap-sass-plugin \ /usr/share/rubygems-integration/all/gems/bootstrap-sass-$(version) \ /usr/share/compass/frameworks/bootstrap-sass That could even be modularized in a dh_compass_plugin or something like that. I will upload a fixed version soon. Note however that the name of the package is bootstrap-sass, and that -sass suffix is needed to make things just work. Changing that would require renaming stuff under lib/, what would not be sane. The correct usage is: compass create myproject --using bootstrap-sass > Would you perhaps be interested in moving this package to the Sass team, > and maintain the package there? That helps coordinate the interaction > between the Sass/Compass libraries (Compass is dead upstream, so there > will likely soon be some restructuring to relax dependencies). > > I can also offer to take over maintenance of this package, if you don't > mind that move but are not interested in joining that other team. It's used by other Ruby packages, so I would rather have it stay in the Ruby team. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#858195: compass-bootstrap-sass-plugin: Wrong install path, and code not registered with Compass
On Tue, Mar 28, 2017 at 10:20:30PM +0200, Jonas Smedegaard wrote: > Debian use /usr/share/compass as _shared_ location for Compass libraries > - upstream has no such default location. > > Your reasoning is the equivalent of installing C libraries in /usr/lip > and arguing that one should always explicitly feed the compiler the path > (not rely on default path being /usr/lib on Debian systems). I disagree with your analogy. There is a set of well known places where you can put libraries so that compilers find them automatically, and those are known to _everyone_ that does or use libraries, not only in Debian. In this case, there is a convention that only exists in Debian, and AFAICT forces every single package to be patched. Is there any movement in the direction of having this adopted upstream? That said, I am willing to support this, but I don't agree it's an RC issue. I tried changing /usr/share/compass/frameworks/bootstrap-sass to /usr/share/compass/frameworks/bootstrap as you said, but that doesn't exactly make it work: | $ compass create myproject --using bootstrap | directory myproject/ | directory myproject/fonts/bootstrap/ | directory myproject/javascripts/ | directory myproject/javascripts/bootstrap/ | directory myproject/sass/ | directory myproject/stylesheets/ |create myproject/config.rb |create myproject/sass/styles.scss |create myproject/sass/_bootstrap-variables.scss |create myproject/javascripts/bootstrap.min.js |create myproject/javascripts/bootstrap.js |create myproject/javascripts/bootstrap/dropdown.js |create myproject/javascripts/bootstrap/collapse.js |create myproject/javascripts/bootstrap/modal.js |create myproject/javascripts/bootstrap/tooltip.js |create myproject/javascripts/bootstrap/transition.js |create myproject/javascripts/bootstrap/alert.js |create myproject/javascripts/bootstrap/carousel.js |create myproject/javascripts/bootstrap/popover.js |create myproject/javascripts/bootstrap/button.js |create myproject/javascripts/bootstrap/scrollspy.js |create myproject/javascripts/bootstrap/affix.js |create myproject/javascripts/bootstrap/tab.js |create myproject/javascripts/bootstrap-sprockets.js |create myproject/fonts/bootstrap/glyphicons-halflings-regular.woff2 |create myproject/fonts/bootstrap/glyphicons-halflings-regular.woff |create myproject/fonts/bootstrap/glyphicons-halflings-regular.eot |create myproject/fonts/bootstrap/glyphicons-halflings-regular.svg |create myproject/fonts/bootstrap/glyphicons-halflings-regular.ttf | error myproject/sass/styles.scss (Line 2: File to import not found or unreadable: bootstrap-compass. | Load paths: | Compass::SpriteImporter | /tmp/test-compass/myproject/sass | /usr/share/compass/frameworks/compass/stylesheets | /usr/share/compass/frameworks/bootstrap/stylesheets) | Compilation failed in 1 files. ^^ note this bit here | | * | Congratulations! Your compass project has been created. | | You may now add and edit sass stylesheets in the sass subdirectory of your project. | | Sass files beginning with an underscore are called partials and won't be | compiled to CSS, but they can be imported into other sass stylesheets. | | You can configure your project by editing the config.rb configuration file. | | You must compile your sass stylesheets into CSS when they change. | This can be done in one of the following ways: | 1. To compile on demand: | compass compile [path/to/project] | 2. To monitor your project for changes and automatically recompile: | compass watch [path/to/project] | | More Resources: | * Website: http://compass-style.org/ | * Sass: http://sass-lang.com | * Community: http://groups.google.com/group/compass-users/ | | | To import your new stylesheets add the following lines of HTML (or equivalent) to your webpage: | | | Any ideas? signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#858195: compass-bootstrap-sass-plugin: Wrong install path, and code not registered with Compass
Control: severity -1 wishlist Hi, On Sun, Mar 19, 2017 at 06:13:06PM +0100, Jonas Smedegaard wrote: > Package: compass-bootstrap-sass-plugin > Version: 3.3.5.1-3 > Severity: grave > Justification: renders package unusable > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > The most basic way to initialize a Compass project using this library > should be using the following command: > > $ compass create --using bootstrap > > That fails, however: > > No such framework: "bootstrap" > > > Inspecting package contents it turns out that Sass files are shipped > twice, none of them below /usr/share/doc/compass-bootstrap-sass-plugin > as explected: > > * compass-bootstrap-sass-plugin includes them below > /usr/share/compass/frameworks/bootstrap-sass > * ruby-bootstrap-sass ships them below > /usr/share/ruby-bootstrap-sass/assets > > The correct path would be /usr/share/compass/frameworks/bootstrap - i.e. > without the -sass suffix. > > Adapting the simplest Compass command for the renamed project path gets > further but still fails: > > directory fonts/bootstrap/ > directory javascripts/ > directory javascripts/bootstrap/ > directory sass/ > directory stylesheets/ >create config.rb >create sass/styles.scss >create sass/_bootstrap-variables.scss >create javascripts/bootstrap.js >create javascripts/bootstrap.min.js >create javascripts/bootstrap-sprockets.js >create javascripts/bootstrap/carousel.js >create javascripts/bootstrap/popover.js >create javascripts/bootstrap/scrollspy.js >create javascripts/bootstrap/modal.js >create javascripts/bootstrap/transition.js >create javascripts/bootstrap/button.js >create javascripts/bootstrap/alert.js >create javascripts/bootstrap/collapse.js >create javascripts/bootstrap/tab.js >create javascripts/bootstrap/tooltip.js >create javascripts/bootstrap/dropdown.js >create javascripts/bootstrap/affix.js >create fonts/bootstrap/glyphicons-halflings-regular.svg >create fonts/bootstrap/glyphicons-halflings-regular.eot >create fonts/bootstrap/glyphicons-halflings-regular.woff >create fonts/bootstrap/glyphicons-halflings-regular.woff2 >create fonts/bootstrap/glyphicons-halflings-regular.ttf > error sass/styles.scss (Line 2: File to import not found or unreadable: > bootstrap-compass. > Load paths: > Compass::SpriteImporter > /usr/local/src/COUCH/omni/styling./sass > /usr/share/compass/frameworks/compass/stylesheets > /usr/share/compass/frameworks/blend-modes/stylesheets > /usr/share/compass/frameworks/blueprint/stylesheets > /usr/share/compass/frameworks/bootstrap-sass/stylesheets > /usr/share/compass/frameworks/breakpoint/stylesheets > /usr/share/compass/frameworks/color-schemer/stylesheets > /usr/share/compass/frameworks/fancy-buttons/stylesheets > /usr/share/compass/frameworks/h5bp/stylesheets > /usr/share/compass/frameworks/layoutgala/stylesheets > /usr/share/compass/frameworks/normalize-scss/stylesheets > /usr/share/compass/frameworks/sassy-maps/stylesheets > /usr/share/compass/frameworks/singularitygs/stylesheets > /usr/share/compass/frameworks/slickmap/stylesheets > /usr/share/compass/frameworks/susy/stylesheets > /usr/share/compass/frameworks/toolkit/stylesheets > /usr/share/compass/frameworks/yui/stylesheets) > Compilation failed in 1 files. > > > This next failure is due to the ruby code is not registering the path > with Compass, requiring to do that explicitly: > > $ compass create --using bootstrap-sass --require bootstrap-sass > > That works. > > In short, this Compass library is installed in the wrong path, and its > ruby code is not registered with Compass. Quoting the bootstrap-sass README: | If you are creating a new Compass project, you can generate it with bootstrap-sass support: | | ```console | $ bundle exec compass create my-new-project -r bootstrap-sass --using bootstrap | ``` Ignoring tthe `bundle exec` bit that is not needed with Debian packages, you are supposed to use `--require bootstap-sass` explicitly. While I agree with you that it _could_ work transparently, there is nothing broken in the package. And I don't think this is something we should be doing different from upstream. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#855931: ruby-eventmachine: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
On Mon, Mar 06, 2017 at 01:12:12PM +0100, Lucas Nussbaum wrote: > On 04/03/17 at 12:49 +0530, Pirate Praveen wrote: > > On Thu, 23 Feb 2017 14:28:20 +0100 Lucas Nussbaum wrote: > > > During a rebuild of all packages in stretch (in a stretch chroot, not a > > > sid chroot), your package failed to build on amd64. > > > > I could not reproduce it on a freshly created stretch chroot with sbuild. > > > > sbuild -d stretch ruby-eventmachine_1.0.7-4.dsc > > Hi, > > Well, I just gave it another try, and I could reproduce it... ruby-eventmachine is one the packages whose tests will go crazy on EC2, probably due to some weirdness in how exactly EC2 VM's are configured. Most likely something kernel-related. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#856269: ruby-zip: diff for NMU version 1.2.0-1.1
On Tue, Feb 28, 2017 at 08:08:21AM +0100, Salvatore Bonaccorso wrote: > Control: tags 856269 + pending > > Dear maintainer, > > I've prepared an NMU for ruby-zip (versioned as 1.2.0-1.1) and > uploaded it to DELAYED/5. Please feel free to tell me if I > should delay it longer. thanks - I have just imported the diff to the git repository are you also doing a stable update? signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#855700: updated to 0.0.37
On Wed, Feb 22, 2017 at 11:47:52AM +0100, Hans-Christoph Steiner wrote: > I have updated this package to 0.0.37 to git, which seems to fix this > issue. I'd love to get this into stretch. The diff is not large, if > you remove the whitespace changes. the diff indeed seems reasonable. I would suggest that you upload that to unstable, and open a regular unblock bug. you can explain that to fix an earlier bug, I had to upload a git snapshot, and that this new version has almost no functional changes wrt the latest upload. then, besides attaching the full diff, you can explain that almost all changes are formatting/whitespace, and also provide a filtered diff containing only the chunks that are actual functional changes. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-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: # (I18n::InvalidLocaleData) from /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:181:in `load_yml' from /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:165:in `load_file' from /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:15:in `block in load_translations' from /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:15:in `each' from /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:15:in `load_translations' from /usr/lib/ruby/vendor_ruby/i18n/backend/simple.rb:57:in `init_translations' from /usr/lib/ruby/vendor_ruby/i18n/backend/simple.rb:40:in `available_locales' from /usr/lib/ruby/vendor_ruby/i18n/config.rb:43:in `available_locales' from /usr/lib/ruby/vendor_ruby/i18n/config.rb:49:in `available_locales_set' from /usr/lib/ruby/vendor_ruby/i18n.rb:278:in `locale_available?' from /usr/lib/ruby/vendor_ruby/i18n.rb:284:in `enforce_available_locales!' from /usr/lib/ruby/vendor_ruby/i18n.rb:151:in `translate' from /usr/share/rubygems-integration/all/gems/vagrant-1.9.1/lib/vagrant/errors.rb:103:in `translate_error' from /usr/share/rubygems-integration/all/gems/vagrant-1.9.1/lib/vagrant/errors.rb:72:in `initialize' from /usr/lib/ruby/vendor_ruby/vagrant-mutate/box_loader.rb:257:in `exception' from /usr/lib/ruby/vendor_ruby/vagrant-mutate/box_loader.rb:257:in `fail' from /usr/lib/ruby/vendor_ruby/vagrant-mutate/box_loader.rb:257:in `find_input_dir' from /usr/lib/ruby/vendor_ruby/vagrant-mutate/box_loader.rb:119:in `load_from_boxes_path' from /usr/lib/ruby/vendor_ruby/vagrant-mutate/box_loader.rb:36:in `load' from /usr/lib/ruby/vendor_ruby/vagrant-mutate/mutate.rb:44:in `execute' from /usr/share/rubygems-integration/all/gems/vagrant-1.9.1/lib/vagrant/cli.rb:42:in `execute' from /usr/share/rubygems-integration/all/gems/vagrant-1.9.1/lib/vagrant/environment.rb:274:in `cli' from /usr/share/rubygems-integration/all/gems/vagrant-1.9.1/bin/vagrant:122:in `' from /usr/bin/vagrant:22:in `load' from /usr/bin/vagrant:22:in `' -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vagrant-mutate depends on: ii qemu-utils 1:2.8+dfsg-2 ii ruby1:2.3.3 vagrant-mutate recommends no packages. vagrant-mutate suggests no packages. -- no debconf information signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#853075: ruby-minitar: diff for NMU version 0.5.4-3.1
Hi, On Mon, Jan 30, 2017 at 09:42:19AM +0100, Salvatore Bonaccorso wrote: > Hi Markus, > > On Mon, Jan 30, 2017 at 09:28:35AM +0100, Markus Frosch wrote: > > On 30.01.2017 07:08, Salvatore Bonaccorso wrote: > > > I've prepared an NMU for ruby-minitar (versioned as 0.5.4-3.1) and > > > uploaded it to DELAYED/5. Please feel free to tell me if I > > > should delay it longer. > > > > Thanks Salvatore, I'm perfectly fine with that. Thanks indeed. I have just imported the NMU in the git repository and pushed to alioth signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#849972: yard: please make the output reproducible
On Tue, Jan 10, 2017 at 06:03:02PM +, Chris Lamb wrote: > tags 849972 + patch > thanks > > I've attached upstream's patch if that makes it any easier for you to > apply to the Debian package… ;) I'll upload the new upstream release shortly signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#848766: reel: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: response = http.request(request)
On Sun, Jan 08, 2017 at 05:50:15PM -0500, micah anderson wrote: > Antonio Terceiro writes: > > >> Relevant part (hopefully): > >> > Failure/Error: response = http.request(request) > >> > > >> > OpenSSL::SSL::SSLError: > >> >SSL_connect returned=1 errno=0 state=unknown state: sslv3 alert > >> > unsupported certificate > > Hmm, I built the reverse depends on ruby-certificate-authority and found > this failure in reel, and patched it in 0.6.1-3 to fix this error. I'm > surprised its back, that means something didn't go right with my patch. > I'll have a look at it. Thanks. Let me know if you need help. > > Micah, was there a specific reason to package an unreleased snapshot of > > ruby-certificate-authority? The changelog doesn't really say anything. > > The last official upstream tagged release and gem publish was august > 2012. The upstream author bumped the version to 2.0 in Sept. 2012, and > there have been a number of important fixes (including security) since > then. There is also a request in the github issue tracker for a new > release in May 2014, no response. > > I spoke with the original packager (Sebastien Badia) about updating this > to the current master which fixes those issues, and he gave the go ahead > if we resolved all the reverse-deps. OK. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#848766: reel: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: response = http.request(request)
On Mon, Dec 19, 2016 at 10:19:26PM +0100, Lucas Nussbaum wrote: > Source: reel > Version: 0.6.1-3 > Severity: serious > Tags: stretch sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20161219 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. > > Relevant part (hopefully): > > Failure/Error: response = http.request(request) > > > > OpenSSL::SSL::SSLError: > >SSL_connect returned=1 errno=0 state=unknown state: sslv3 alert > > unsupported certificate > > # /usr/lib/ruby/2.3.0/net/http.rb:933:in `connect_nonblock' > > # /usr/lib/ruby/2.3.0/net/http.rb:933:in `connect' > > # /usr/lib/ruby/2.3.0/net/http.rb:863:in `do_start' > > # /usr/lib/ruby/2.3.0/net/http.rb:852:in `start' > > # /usr/lib/ruby/2.3.0/net/http.rb:1398:in `request' > > # ./spec/reel/https_server_spec.rb:70:in `block (3 levels) in > (required)>' > > # ./spec/reel/https_server_spec.rb:115:in `with_reel_https_server' > > # ./spec/reel/https_server_spec.rb:62:in `block (2 levels) in > (required)>' > > # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in > > `instance_exec' > > # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in `block in run' > > # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:496:in `block in > > with_around_and_singleton_context_hooks' > > # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:453:in `block in > > with_around_example_hooks' > > # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `block in run' > > # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:602:in > > `run_around_example_hooks_for' > > # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `run' > > # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:453:in > > `with_around_example_hooks' > > # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:496:in > > `with_around_and_singleton_context_hooks' > > # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:251:in `run' > > # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:627:in `block > > in run_examples' > > # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:623:in `map' > > # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:623:in > > `run_examples' > > # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:589:in `run' > > # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `block (3 > > levels) in run_specs' > > # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `map' > > # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `block (2 > > levels) in run_specs' > > # /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1835:in > > `with_suite_hooks' > > # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:112:in `block in > > run_specs' > > # /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:77:in `report' > > # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:111:in `run_specs' > > # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:87:in `run' > > # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run' > > # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke' > > # /usr/bin/rspec:4:in `' With the help of CI data, I could trace this to the upload of ruby-certificate-authority (0.2.0~6dd483bf-1). Downgrading to it 0.1.6-2 makes the reel test pass. Micah, was there a specific reason to package an unreleased snapshot of ruby-certificate-authority? The changelog doesn't really say anything. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#824907: ruby-reek: Fails to load library from main script
On Thu, Jan 05, 2017 at 02:19:19PM +0800, Andrew Lee wrote: > Package: ruby-reek > Followup-For: Bug #824907 > > Thanks for reporting such issue. After replace require_relative with > relative paths with "require 'reek'" and such in bin/reek. I still > got: > /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in > `require': cannot load such file -- private_attr/everywhere > (LoadError > > Does this means it missing dependency on the private_attr gem? That too. The reek version in Debian is completely outdated, is missing some dependencies, and some of the dependencies are not packaged yet. Also since it's a tool and not a library the package should be called `reek` instead of `ruby-reek`. The latest version dropped a few dependencies, so it will have less missing dependencies in Debian. In its current state reek is completely broken and since we are already in soft freeze it won't be able to be part of stretch anyway. With all that said, and given that no other package depends on it, I think we should just remove it from Debian for the time being. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#847548: vagrant-cachier: FTBFS: cat: /usr/share/vagrant/version.txt: No such file or directory
Control: reassign -1 vagrant Control: found -1 1.9.0+dfsg-1 On Fri, Dec 09, 2016 at 09:33:11AM +0100, Chris Lamb wrote: > Source: vagrant-cachier > Version: 1.2.1-3 > Severity: serious > Justification: fails to build from source > User: reproducible-bui...@lists.alioth.debian.org > Usertags: ftbfs > X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org > > Dear Maintainer, > > vagrant-cachier fails to build from source in unstable/amd64: > > […] > > > ┌──┐ > │ dh_ruby --install finished >│ > > └──┘ > > dh_vagrant_plugin > mkdir: created directory 'debian/vagrant-cachier/usr/share/vagrant-plugins' > mkdir: created directory > 'debian/vagrant-cachier/usr/share/vagrant-plugins/plugins.d' > cat: /usr/share/vagrant/version.txt: No such file or directory > debian/rules:11: recipe for target 'override_dh_auto_install' failed > make[1]: *** [override_dh_auto_install] Error 1 > make[1]: Leaving directory '«BUILDDIR»' > debian/rules:8: recipe for target 'binary' failed > make: *** [binary] Error 2 > dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit > status 2 > > […] > > The full build log is attached. Argh. This is a regression in vagrant. Other vagrant plugins will probably FTBFS in the same way. I will upload a fix soon. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#847420: gitlab fails to start (shows only 502) after upgrade of ruby-grape-entity
On Thu, Dec 08, 2016 at 10:23:42AM +0530, Pirate Praveen wrote: > Control: severity -1 normal > > On 2016, ഡിസംബർ 8 8:42:57 AM IST, Johannes Schauer wrote: > > > >When I now enter my gitlab instance I only get a 502 error with the > >message "Whoops, GitLab is taking too much time to respond". > > > >Since the last time I changed the version of a ruby package you told me > >to run assets:precompile, I ran the following command: > > > >runuser -u gitlab -- sh -c 'cd /usr/share/gitlab && export $(cat > >/etc/gitlab/gitlab-debian.conf) && rake assets:precompile > >RAILS_ENV=production' > >Could not find grape-entity-0.5.1 in any of the sources > >Run `bundle install` to install missing gems. > > > >Given the error above, I suspect that the new ruby-grape-entity version > >is the culprit here. > > I think its just the old Gemfile.lock expecting the older version. We should > truncate Gemfile.lock in postinst. You need to both discard Gemfile.lock on upgrades of dependencies as well, using dpkg triggers. redmine does this for a while, you might want to check it out. the same applies to precompiling assets ... signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#591419: librmagick-ruby should not be installable with imagemagick
On Mon, Dec 05, 2016 at 09:18:07AM +0100, Nish Aravamudan wrote: > > However, I fail to see how this would fix the issue, since it won't help > > with the very problem that a new version of ImageMagick that has no > > SONAME bump breaks ruby-rmagick. > > So you're right that it does not "fix" the issue of ImageMagick itself > -- given that is something (as you've responded in the other bug) that > src:imagemagick needs to fix. > > > There is a new version of ruby-rmagick which claims support for > > ImageMagick 6.9, and apparently shifts the dependency from libmagickcore > > to libmagickwand ... this might be the correct fix. This wouldn't fix the issue either, I was wrong. > However, what the above patch does is, at least for libMagickCore itself > (and that could be adjusted for libMagickWand as well) is ignore the ABI > values from the symbols file -- that's not entirely 'correct', but what > it means is that if the ABI is not correctly describing minimum version, > we will insert a dependency on the version of imagemagick actually used > to build the package at build-time. That does mean the dependency may be > strictly higher than it needs to be, but it also helps accurately > reflect that ruby-rmagick should be rebuilt (so it forces an imagemagick > transition of sorts on every version bump?). Although perhaps the shell > snippet should make the dependency strictly = (rather than >=). A >= dependency would be useless, because a new package with a ABI break would satisfy that dependency just fine. A strict dependency (= v) would make ruby-rmagick immediately uninstallable when *any* later version comes along, not only one that has an ABI break. So even security fixes, or regular new upstream versions that do not break the ABI, would invalidate the dependency chain of ruby-rmagick. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#591419: librmagick-ruby should not be installable with imagemagick
On Fri, Dec 02, 2016 at 11:12:21AM -0800, Nishanth Aravamudan wrote:
> Package: ruby-rmagick
> Version: 2.15.4+dfsg-2
> Followup-For: Bug #591419
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu zesty ubuntu-patch
>
> I think this should do what is expected. Basically, AIUI, there is a
> more-than-ABI-specifiable (due to issues upstream and possibly in the
> Debian package itself (cf.:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846385) dependency
> between ruby-rmagick and the version of imagemagick compiled against. To
> that end, add an overriding dependency at build-time.
>
> I think what's actually needed currently in ruby-rmagick's case in
> Debian is a rebuild against the bumped version of imagemagick; if that's
> done, the autopkgtests would pass. But expressing this dependency
> explicilty would have caught that and prevented imagemagick from
> changing in Debian until ruby-rmagick had been rebuilt?
>
> Comments more than welcome and appreciated.
>
> Thanks!
> -Nish
>
> ## REPLACE THIS WITH ACTUAL INFORMATION -
> ## Please add all necessary information about why the change needed to go in
> ## Ubuntu, quote policy, spec or any other background material and why it can
> ## and should be used in Debian too. If the patch is composed of multiple
> ## independent pieces, please send them as separate bug reports.
> ## REPLACE THIS WITH ACTUAL INFORMATION -
>
>
> * d/{control,rules}: use a new substitution variable to specify the
> hard-dependency on the version of ImageMagick built against
> (Closes: #591419). Thanks to Adam Conrad for the shell code.
>
> Thanks for considering the patch.
>
> *** /tmp/tmp6FrTwc/ruby-rmagick_2.15.4+dfsg-2ubuntu1.debdiff
> diff -Nru ruby-rmagick-2.15.4+dfsg/debian/control
> ruby-rmagick-2.15.4+dfsg/debian/control
> --- ruby-rmagick-2.15.4+dfsg/debian/control 2016-08-16 07:29:37.0
> -0700
> +++ ruby-rmagick-2.15.4+dfsg/debian/control 2016-12-01 15:36:05.0
> -0800
> @@ -28,7 +28,8 @@
> XB-Ruby-Versions: ${ruby:Versions}
> Depends: ruby | ruby-interpreter,
> ${misc:Depends},
> - ${shlibs:Depends}
> + ${shlibs:Depends},
> + ${imagemagick:Depends}
> Description: ImageMagick API for Ruby
> RMagick is an interface between the Ruby programming language and the
> ImageMagick image processing library.
> diff -Nru ruby-rmagick-2.15.4+dfsg/debian/rules
> ruby-rmagick-2.15.4+dfsg/debian/rules
> --- ruby-rmagick-2.15.4+dfsg/debian/rules 2016-08-16 07:29:37.0
> -0700
> +++ ruby-rmagick-2.15.4+dfsg/debian/rules 2016-12-01 15:36:05.0
> -0800
> @@ -12,3 +12,11 @@
> find debian/*/usr/share/doc/ruby-rmagick-doc/ \
> -type f -executable -exec \
> chmod -x '{}' ';'
> +
> +override_dh_gencontrol:
> + $(eval IMAGEMAGICK_DEP := \
> + $(shell find debian/ruby-rmagick/ -name RMagick2.so -exec ldd
> '{}' ';' | \
> + awk '/\/libMagickCore/ {print $$3}' | xargs dpkg -S | \
> + awk '{print $$1}' | sed 's/:$$//' | xargs dpkg-query -W \
> + -f='$${Package} (>= $${Version})'))
> + dh_gencontrol -- -Vimagemagick:Depends='$(IMAGEMAGICK_DEP)'
Hi, thanks for the patch.
However, I fail to see how this would fix the issue, since it won't help
with the very problem that a new version of ImageMagick that has no
SONAME bump breaks ruby-rmagick.
There is a new version of ruby-rmagick which claims support for
ImageMagick 6.9, and apparently shifts the dependency from libmagickcore
to libmagickwand ... this might be the correct fix.
signature.asc
Description: PGP signature
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#591419: Same librmagick problem again
On Thu, Dec 01, 2016 at 11:03:46AM -0800, Nish Aravamudan wrote: > > * the second one is that librmagick-ruby is very easily broken by > > newer versions of imagemagick, which is actually very hard to track. > > This will need some thinking; possibly a solution would be a strict > > versioned dependency along if only binNMUs for each imagemagick > > release ? > > What happened to this idea? I think this is the (a?) reason ruby-rmagick > is currently failing its autopkgtests, using an imagemagick at runtime > that it is not built against? > > We have seen this on Ubuntu as well, and I wonder if it would be > appropriate to just extract the libmagickcore version used at build-time > and override the shlib-depends for that package with specifically the > built-using version? Thanks to Adam Conrad for this suggestion. > > I can work on a patch, if it would be acceptable. patches are *always* welcome signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#796020: reconsidering the removal of ruby-hpricot
Control: severity -1 important On Fri, 2 Sep 2016 09:43:04 -0300 Antonio Terceiro wrote: > On Tue, Aug 18, 2015 at 06:26:06PM +0200, Christian Hofstaedtler wrote: > > Package: ruby-hpricot > > Version: 0.8.6-5 > > Severity: serious > > Justification: obsolete > > > > ruby-hpricot is obsolete. > > > > Upstream has this to say: > > > > > # Hpricot is over. > > > > > > After years of lack of a proper maintainer for one of why's jewels, it > > > has been > > > decided to finally close the book on hpricot. Most users have migrated to > > > alternatives > > > and there is simply no time or energy to continue with the current > > > codebase. > > > > > > If you feel that you have the time and wish to take it over, I suggest > > > you instead > > > think about making the hpricot-like API within nokogiri 100% compatible, > > > that is a better > > > use of your time. > > > > > > But if you still feel like "No damnit, I wanna work on hpricot itself > > > still!" then fork > > > this repo and start work. Send @evanphx or @nicksieger a message if you > > > feel like you > > > want to take over the gem name with new releases under the hpricot name. > > > > > > Thanks to \_why for all the fun. We'll never forget it. > > > > If your package depends on ruby-hpricot, please move away from it > > immediately. > > > > We're not going to have ruby-hpricot in stretch. > > ruby-hpricot has now only 2 reverse dependencies: ruby-ronn and > ruby-fast-fs. However, the number of packages build-depending on > ruby-ronn only grows, and is currently at 54¹ > > ¹ comitup coquelicot cura-engine dbab elektra foodcritic foremancli > gazebo git-extras haproxyctl ignition-math2 ignition-math2 > ignition-transport ignition-transport jq maim npm pacapt pgloader > python-lua qiime r10k ruby-coveralls ruby-ghi seqprep shapelib slt > unburden-home-dir vcsh comitup coquelicot dbab elektra foodcritic > foremancli gazebo git-extras haproxyctl ignition-math2 > ignition-transport jq maim npm pacapt pgloader r10k ruby-coveralls > ruby-ghi seqprep shapelib unburden-home-dir vcsh pgcharts pycsw > > ruby-hpricot is indeed dead upstream, but so is a lot of software in > Debian. Also, being dead upstream does not mean not being useful, or > necessarily being broken. > > So I think we should give up on removing ruby-hpricot until at least one > of the following happen: > > - ruby-ronn gets rewritten to not use ruby-hpricot (unlikely since ronn > is dead upstream itself) > - something else can replace ruby-ronn and we manage to make reverse > (build) dependencies switch to it. > - ruby-hpricot gets broken by a future update to Ruby in a way that is > unfixable and we have no other option. since I heard no objections, I am therefore downgrading this bug to make it non-RC. I will be glad if/when we can remove ruby-hpricot from Debian, but for now it is just not viable. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#843962: rails: gitlab activerecord problems
On Fri, Nov 11, 2016 at 11:31:45AM +0200, Yavuz Selim Komur wrote: > Package: rails > Version: 2:4.2.7.1-1 > Severity: important > > Dear Maintainer, > > > > ruby-activerecord > >* What led up to the situation? >all gitlab versions. first time get like below > > Started GET "/api/v3/projects/all?private_token=[FILTERED]" for > xxx.xxx.xxx.xxx at 2016-04-1 2 12:39:52 +0300 > > NoMethodError (undefined method `[]=' for > # > Did you mean? []): >/usr/lib/ruby/vendor_ruby/active_record/serialization.rb:14:in > `serializable_hash' >/usr/lib/ruby/vendor_ruby/carrierwave/orm/activerecord.rb:65:in > `serializable_hash' > > > after gitlab-8.13.3 > Completed 500 Internal Server Error in 149ms (ActiveRecord: 8.3ms) > > NoMethodError (undefined method `sha' for > "619cd3b08008fb388ca0426241c52a487620302c":String): > app/models/repository.rb:1081:in `update_branch_with_hooks' > -- > > Sorry for my This does not look like an issue in rails at all. Would you ellaborate on why you think that? signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#832247: closed by Antonio Terceiro (Bug#832247: fixed in origami-pdf 2.0.0-1)
On Sat, Oct 29, 2016 at 09:18:10AM +1100, Ben Finney wrote: > On 28-Oct-2016, Debian Bug Tracking System wrote: > > >* Change Section: to `utils` (Closes: #832247) > > Thank you for fixing the source package. Which is the bug report for > fixing the archive? #842855 signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#842737: ohai: FTBFS: Could not find 'addressable' (>= 0) among 31 total gem(s) (Gem::LoadError)
Control: reassign -1 ruby-chef-config Control: found -1 12.14.60-1 Hi, thanks for the bug report On Mon, Oct 31, 2016 at 08:05:04PM +, Chris Lamb wrote: > > GEM_PATH=debian/ohai/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all > ruby2.3 -e gem\ \"ohai\" > /usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not > find 'addressable' (>= 0) among 31 total gem(s) (Gem::LoadError) > Checked in > 'GEM_PATH=debian/ohai/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all', > execute `gem env` for more information > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1438:in `block in > activate_dependencies' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1427:in `each' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1427:in > `activate_dependencies' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1409:in `activate' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1441:in `block in > activate_dependencies' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1427:in `each' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1427:in > `activate_dependencies' > from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1409:in `activate' > from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:68:in `block > in gem' > from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in > `synchronize' > from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in `gem' > from -e:1:in `' this is actually caused by the new upload of chef; ruby-chef-config is missing a dependency on ruby-addressable. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#841487: ruby-kaminari: All the files under app/ are missing
On Fri, Oct 21, 2016 at 02:29:43PM +0800, Andrew Lee wrote: > Package: ruby-kaminari > Version: 0.17.0-2 > Severity: important > > Dear Maintainer, > > I am fixing search function in obs-api package. And I noticed an error > says: Missing partial kaminari/_paginator. > > And I check our binary package, kaminari/_paginator isn't exist there. > I checked the ruby-kaminari source package from git and found all the > files under app/ doesn't ship in the binary package. > > These are: > app/views/kaminari/_gap.html.slim > app/views/kaminari/_page.html.erb > app/views/kaminari/_page.html.haml > app/views/kaminari/_gap.html.erb > app/views/kaminari/_next_page.html.erb > app/views/kaminari/_next_page.html.slim > app/views/kaminari/_paginator.html.haml > app/views/kaminari/_first_page.html.haml > app/views/kaminari/_last_page.html.slim > app/views/kaminari/_prev_page.html.slim > app/views/kaminari/_next_page.html.haml > app/views/kaminari/_page.html.slim > app/views/kaminari/_last_page.html.haml > app/views/kaminari/_last_page.html.erb > app/views/kaminari/_prev_page.html.erb > app/views/kaminari/_paginator.html.erb > app/views/kaminari/_paginator.html.slim > app/views/kaminari/_first_page.html.slim > app/views/kaminari/_first_page.html.erb > app/views/kaminari/_gap.html.haml > app/views/kaminari/_prev_page.html.haml From a quick look, I think it needs to ship both app/ and config/. It's probably better to install it using the rubygems layout, something like this in debian/rules should do: export DH_RUBY = --gem-install export DH_RUBY_GEM_INSTALL_WHITELIST_APPEND = config signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#840909: ruby-gdk-pixbuf2: cannot overwrite Pixbuf.pixels with substitution
On Sun, Oct 16, 2016 at 11:52:15AM +0900, Shyouzou Sugitani wrote: > Package: ruby-gdk-pixbuf2 > Version: 3.0.9-1 > Severity: normal > > Dear Maintainer, > > I'm trying to make ninix-aya work with Ruby-GNOME2 3.0.9. > But I found that I cannot overwrite Pixbuf.pixels with substitution. > > pix = GdkPixbuf::Pixbuf.new(:file => "test.png") > pix.pixels[0] > => 0 > pix.pixels[0] = 255 > => 255 > pix.pixels[0] > => 0 > > In 2.2.5 I can modify GdkPixbuf through pixels. > Is there any API change? It will be probably more effective for you to make that query upstream. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#838216: Could not find 'chef-zero' (~> 4.5) - did find: [chef-zero-5.0.0] (Gem::LoadError)
Control: reassign -1 chef Control: found -1 12.10.24-1 On Sun, Sep 18, 2016 at 10:00:58PM +0530, Pirate Praveen wrote: > package: chef,chef-zero > version: 12.10.24-1 > severity: serious > > Update of chef-zero without testing reverse dependency compatibility > caused the issue. > > adt-run [18:55:42]: test command1: gem2deb-test-runner > --check-dependencies --autopkgtest > adt-run [18:55:42]: test command1: [--- > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby2.3 > │ > └──┘ > > GEM_PATH= ruby2.3 -e gem\ \"chef\" > /usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not > find 'chef-zero' (~> 4.5) - did find: [chef-zero-5.0.0] (Gem::LoadError) This also makes chef FTBFS because we check dependencies during the build. I am reassign to chef because clearly that is where this will need to be fixed. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
Re: [DRE-maint] backporting vagrant to jessie
On Wed, Sep 14, 2016 at 12:27:03PM +0200, Hans-Christoph Steiner wrote: > > Hey all, > > Thanks for packaging vagrant and all that ruby stuff! I have gotten > vagrant working to set up nested QEMU-KVM instances, so that we can run > tests that set up a QEMU-KVM guest in jenkins.debian.net, which itself > is a QEMU-KVM guest instance. I have this all working well in stretch, > but jessie does not have vagrant-libvirt, so its a showstopper. > > I have already backported everything that vagrant-libvirt needs on my > machine. I tried backporting vagrant itself, and got an error that > seems beyond me. I don't know ruby at all. > > # dpkg -i vagrant_1.8.5+dfsg-2_all.deb > Selecting previously unselected package vagrant. > (Reading database ... 24076 files and directories currently installed.) > Preparing to unpack vagrant_1.8.5+dfsg-2_all.deb ... > Unpacking vagrant (1.8.5+dfsg-2) ... > dpkg: dependency problems prevent configuration of vagrant: > vagrant depends on ruby-bundler (>= 1.12.5); however: > Package ruby-bundler is not installed. > > dpkg: error processing package vagrant (--install): > dependency problems - leaving unconfigured > Processing triggers for man-db (2.7.0.2-5) ... > Errors were encountered while processing: > > The following packages have unmet dependencies: > ruby-bundler : Breaks: bundler (< 1.11.2-1~) but 1.7.4-1 is to be installed > vagrant : Depends: ruby-bundler (>= 1.12.5) but 1.11.2-1~bpo8+1 is to > be installed it seems you missed that yo you also need to backport bundler? signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#837672: autopkgtest fails even when there are multiple gemspec files and DH_RUBY_GEMSPEC is set
On Tue, Sep 13, 2016 at 05:37:20PM +0530, Pirate Praveen wrote: > package: gem2deb-test-runner: > version: 0.32 > > adt-run [09:07:02]: test command1: gem2deb-test-runner --autopkgtest > --check-dependencies 2>&1 > adt-run [09:07:02]: test command1: [--- > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby2.3 > │ > └──┘ > > /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:120:in `load_gemspec': > More than one .gemspec file in this directory: > concurrent-ruby-edge.gemspec, concurrent-ruby-ext.gemspec, > concurrent-ruby.gemspec (RuntimeError) > from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:33:in `block in > initialize' > from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:32:in `chdir' > from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:32:in `initialize' > from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:77:in `new' > from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:77:in > `do_check_dependencies' > from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:67:in `run_tests' > from /usr/bin/gem2deb-test-runner:61:in `' > adt-run [09:07:02]: test command1: ---] > adt-run [09:07:02]: test command1: - - - - - - - - - - results - - - - > - - - - - - > command1 FAIL non-zero exit status 1 > adt-run [09:07:02]: summary > command1 FAIL non-zero exit status 1 > > > Full log > https://ci.debian.net/data/packages/unstable/amd64/r/ruby-concurrent/latest-autopkgtest/log.gz you can't expect gem2deb-test-runner to pick up DH_RUBY_GEMSPEC being set in debian/rules when running under autopkgtest ... but we should probably have a DRY way to declare that. maybe we could expec debian/$pkg.gemspec to be a symlink to the _correct_ gemspec, or maybe some other way. Either way I cannot promise a solution for that any time soon. if you want to work around that for now, I suggest setting DH_RUBY_GEMSPEC in an explicit debian/tests/control ... Test-Command: DH_RUBY_GEMSPEC=foo.gemspec gem2deb-test-runner --autopkgtest --check-dependencies 2>&1 signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#836536: ruby-concurrent: FTBFS too much often (failed examples)
On Mon, Sep 12, 2016 at 11:12:26AM +0530, Balasankar C wrote: > On Sat, 3 Sep 2016 21:49:13 +0200 (CEST) Santiago Vila > wrote: > > BTW: I think the "Randomized with seed xxx" above is a bad idea. > > Maintainers often ask bug reporters for "a way to reproduce the error". > > But if the build is based on random variables, this becomes an > > impossible task. Please consider modifying the build system so that > > those random things are always the same. > > I believe I have fixed this in the latest upload, in which I specified the > order to run the tests. I tried building it 5 times in a cowbuilder > environment > and didn't hit any failures. Please reopen the bug if this problem persists. I think that in general 5 times is probably not enough. the last package I fixed that failed randomly would fail 6% of the time (i.e. ~3 times out of 50 attempts in my tests). signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#829362: ruby-ronn: please make the output reproducible
On Sun, Sep 04, 2016 at 08:30:39PM -0300, Antonio Terceiro wrote: > > + return Time.at(ENV['SOURCE_DATE_EPOCH'].to_i).gmtime if > > ENV['SOURCE_DATE_EPOCH'] > > otherwise, if SOURCE_DATE_EPOCH is passed, the date is _already_ in UTC (`utc` > and `gmtime` are synonyms in the ruby date class). s/ruby date class/ruby Time class/ signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#829362: ruby-ronn: please make the output reproducible
On Sun, Sep 04, 2016 at 10:19:35PM +0100, Chris Lamb wrote:
> > yeah that was a typo, but again, ronn does not do locales (at all)
>
> Looking into this, it appear's that ruby's strftime is locale independent,
> rather than something ronn-specific. This the opposite behaviour to every
> other strftime that I've come across, hence the confusion.
Last time I checked strftime in any language will only format according
to the locale defined by environment variables if and only if the
program calling strftime has initialized the locale system with
setlocale().
> However, you are still missing:
>
> - date.strftime
> + date.utc.strftime
one of the things that was making the test crash was this. in Ruby, `Date`
objects do not have a `utc` method.
> … for when building close to month changes with respect to TZ.
let's see
> --- a/lib/ronn/document.rb
> +++ b/lib/ronn/document.rb
> @@ -165,6 +165,7 @@ module Ronn
> # the current time.
> def date
>return @date if @date
if the date has been passed explicitly in the command line (with `ron --date
...`), it will be a fixed date and thus will not vary according to $TZ.
ronn parses the date with
options['date'] &&= Date.strptime(options['date'], '%Y-%m-%d')
so let's do that
$ TZ=UTC ruby -rdate -e 'puts Date.strptime("2016-10-01", "%Y-%m-%d")'
2016-10-01
$ TZ=Asia/Tokyo ruby -rdate -e 'puts Date.strptime("2016-10-01", "%Y-%m-%d")'
2016-10-01
Also, Date objects in Ruby do not store either hours or timezones. Only Time
objcts do that.
> + return Time.at(ENV['SOURCE_DATE_EPOCH'].to_i).gmtime if
> ENV['SOURCE_DATE_EPOCH']
otherwise, if SOURCE_DATE_EPOCH is passed, the date is _already_ in UTC (`utc`
and `gmtime` are synonyms in the ruby date class).
>return File.mtime(path) if File.exist?(path)
>Time.now
> end
I believe the patch as it currently is solves any reproducibility issues. if
you can find a concrete and reproducible case where it does not, please report
a new bug.
signature.asc
Description: PGP signature
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#835749: This package can be removed
On Sun, Sep 04, 2016 at 08:29:59PM +0530, Pirate Praveen wrote: > This was packaged as a dependency for gitlab and recent versions of > gitlab does not need it any more (it was removed from Gemfile, but > debian/control was not updated). > > There are no other reverse dependencies, so this can be removed, once I > upload a new version of gitlab which does not depend on it (already > committed in git, will upload after the current version in unstable gets > migrated to testing or another rc bug forces me to do another upload). please request the removal after gitlab is uploaded, then. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#829362: ruby-ronn: please make the output reproducible
On Sun, Sep 04, 2016 at 04:28:59PM +0100, Chris Lamb wrote: > [Re-adding 829...@bugs.debian.org to CC, and quoting in full] > > Antonio Terceiro wrote: > > > On Sat, Sep 03, 2016 at 05:32:38PM +0100, Chris Lamb wrote: > > > > I tried that, but with this patch the build failed. > > > > > > Please elaborate? > > > > Tests failed. I don't have the logs anymore, but they did. > > If you happen to apply it again, please retain them. > > > > > IMO all the other changes are not really warranted. > > > > > > Oh? Could you comment on why you believe this to be not necessary? > > > > > > > > > https://github.com/rtomayko/ronn/pull/98/files#diff-a87e9e80c3a7693175aa8c08bdb48452L70 > > > > > > (It seems self-evidently not reproducible, and I almost certainly added > > > it to the patch to fix a particular package...) > > > > ruby-ronn does not do locales: > > > > $ cat debian/coveralls.mkd | ronn | grep 2016 > > .TH "COVERALLS" "1" "September 2016" "" "" > > $ cat debian/coveralls.mkd | LANG=pt_BR.UFT-8 ronn | grep 2016 > > .TH "COVERALLS" "1" "September 2016" "" "" > > "UFT-8"? Again, it seems highly unlikely I patched this without good > reason. yeah that was a typo, but again, ronn does not do locales (at all), so your changes to remove the usage of %B don't accomplish anything. maybe if I copy and paste the locale names you will believe me :-) $ cat debian/coveralls.mkd | LANG=C ronn | grep 2016 .TH "COVERALLS" "1" "September 2016" "" "" $ cat debian/coveralls.mkd | LANG=pt_BR.UTF-8 ronn | grep 2016 .TH "COVERALLS" "1" "September 2016" "" "" $ cat debian/coveralls.mkd | LANG=fr_FR.UTF-8 ronn | grep 2016 .TH "COVERALLS" "1" "September 2016" "" "" signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#829362: ruby-ronn: please make the output reproducible
On Fri, Sep 02, 2016 at 08:03:06PM +0100, Chris Lamb wrote: > Antonio Terceiro wrote: > > > So do we want to replace the earlier patch with this one? > > Hm, the patch to #829362 (which modifies the patch) is kinda ugly and > almost impossible to mentally parse. Sorry about that. > > So, considering this cleaner patch: > > https://github.com/rtomayko/ronn/pull/98/files > > … I believe we need all of these changes so, yes, we should replace > it. The following hunk demonstrates that it absorbs the previous patch: > > > https://github.com/rtomayko/ronn/pull/98/files#diff-a87e9e80c3a7693175aa8c08bdb48452L70 I tried that, but with this patch the build failed. I rewrote it into a much less invasive version: --- a/lib/ronn/document.rb +++ b/lib/ronn/document.rb @@ -165,6 +165,7 @@ module Ronn # the current time. def date return @date if @date + return Time.at(ENV['SOURCE_DATE_EPOCH'].to_i).gmtime if ENV['SOURCE_DATE_EPOCH'] return File.mtime(path) if File.exist?(path) Time.now end IMO all the other changes are not really warranted. With the resulting ruby-ronn binary, I tried both ruby-coveralls and foodcritic, which are listed in the issue page¹, and they became reproducible. ¹ https://tests.reproducible-builds.org/debian/issues/unstable/timestamps_in_manpages_generated_by_ronn_issue.html, signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#829362: ruby-ronn: please make the output reproducible
Hi, On Fri, Sep 02, 2016 at 11:04:07AM +0100, Chris Lamb wrote: > Dear Maintainer, > > > Source: ruby-ronn > > Version: 0.7.3-4 > > Tags: patch > > There hasn't seem to be any update here in a while and this package > is affecting the reproducibility status of many packages. > > Would you consider applying this patch and uploading? :) Another reproducibility patch has been applied to close #807201, and this one does not apply on top of 0.7.3-4; in fact it looks like a modified version of that one. So do we want to replace the earlier patch with this one? signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#796020: reconsidering the removal of ruby-hpricot
On Tue, Aug 18, 2015 at 06:26:06PM +0200, Christian Hofstaedtler wrote: > Package: ruby-hpricot > Version: 0.8.6-5 > Severity: serious > Justification: obsolete > > ruby-hpricot is obsolete. > > Upstream has this to say: > > > # Hpricot is over. > > > > After years of lack of a proper maintainer for one of why's jewels, it has > > been > > decided to finally close the book on hpricot. Most users have migrated to > > alternatives > > and there is simply no time or energy to continue with the current codebase. > > > > If you feel that you have the time and wish to take it over, I suggest you > > instead > > think about making the hpricot-like API within nokogiri 100% compatible, > > that is a better > > use of your time. > > > > But if you still feel like "No damnit, I wanna work on hpricot itself > > still!" then fork > > this repo and start work. Send @evanphx or @nicksieger a message if you > > feel like you > > want to take over the gem name with new releases under the hpricot name. > > > > Thanks to \_why for all the fun. We'll never forget it. > > If your package depends on ruby-hpricot, please move away from it > immediately. > > We're not going to have ruby-hpricot in stretch. ruby-hpricot has now only 2 reverse dependencies: ruby-ronn and ruby-fast-fs. However, the number of packages build-depending on ruby-ronn only grows, and is currently at 54¹ ¹ comitup coquelicot cura-engine dbab elektra foodcritic foremancli gazebo git-extras haproxyctl ignition-math2 ignition-math2 ignition-transport ignition-transport jq maim npm pacapt pgloader python-lua qiime r10k ruby-coveralls ruby-ghi seqprep shapelib slt unburden-home-dir vcsh comitup coquelicot dbab elektra foodcritic foremancli gazebo git-extras haproxyctl ignition-math2 ignition-transport jq maim npm pacapt pgloader r10k ruby-coveralls ruby-ghi seqprep shapelib unburden-home-dir vcsh pgcharts pycsw ruby-hpricot is indeed dead upstream, but so is a lot of software in Debian. Also, being dead upstream does not mean not being useful, or necessarily being broken. So I think we should give up on removing ruby-hpricot until at least one of the following happen: - ruby-ronn gets rewritten to not use ruby-hpricot (unlikely since ronn is dead upstream itself) - something else can replace ruby-ronn and we manage to make reverse (build) dependencies switch to it. - ruby-hpricot gets broken by a future update to Ruby in a way that is unfixable and we have no other option. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#834963: ruby-protected-attributes: FTBFS too much often (failing tests)
Control: tags -1 + patch pending Control: forwarded -1 https://github.com/rails/protected_attributes/pull/89 err, fixing the metadata update signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#834963: ruby-protected-attributes: FTBFS too much often (failing tests)
Close: tags -1 + patch pending Close: forwarded -1 https://github.com/rails/protected_attributes/pull/89 On Sun, Aug 21, 2016 at 01:41:27AM +0200, Santiago Vila wrote: > Package: src:ruby-protected-attributes > Version: 1.1.3-1 > Severity: serious > > Dear maintainer: > > I tried to build this package in stretch with "dpkg-buildpackage -A" > (which is what the "Arch: all" autobuilder would do to build it) > but it failed: > > > [...] [snip] > > > Because this source package only generates "Arch: all" packages, this > is the same as a FTBFS bug in the usual sense, and the fact that I was > doing "dpkg-buildpackage -A" does not mean anything special. Thanks for the bug report. I have found the issue, and submitted a patch upstream. I will upload a fixed package in a few days. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#835588: gm2deb test failure in jessie when backporting
Control: tag -1 pending
On Sat, Aug 27, 2016 at 03:15:53PM +0530, Pirate Praveen wrote:
> package: gem2deb
> version: 0.32
> severity: wishlist
>
> I'm trying to backport gem2deb 0.32 to jessie and one test fails.
>
> test: timestamps should use date from changelog if available. :F
>
> Failure: test: timestamps should use date from changelog if available.
> (MetaDataTest)
> /home/pravi/gem2deb-0.32/test/unit/metadata_test.rb:235:in `block (2
> levels) in '
> <2015-11-20 00:00:00 UTC> expected but was
> <2015-11-21 00:00:00 UTC>
>
> diff:
> ? 2015-11-20 00:00:00 UTC
> ? 1
>
Insteresting. It's an issue that only manifests depending on the hour of
the day, and on some timezones.
8<8<8<-
$ ruby test/unit/metadata_test.rb
Loaded suite test/unit/metadata_test
Started
...
Finished in 1.288412217 seconds.
35 tests, 42 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0
notifications
100% passed
27.17 tests/s, 32.60 assertions/s
$ TZ=Asia/Kolkata ruby test/unit/metadata_test.rb
Loaded suite test/unit/metadata_test
Started
.F
===
Failure:
test: timestamps should use date from changelog if available. (MetaDataTest)
test/unit/metadata_test.rb:235:in `block (2 levels) in '
/usr/lib/ruby/vendor_ruby/shoulda/context/context.rb:413:in `instance_exec'
/usr/lib/ruby/vendor_ruby/shoulda/context/context.rb:413:in `block in
create_test_from_should_hash'
<2015-11-20 00:00:00 UTC> expected but was
<2015-11-21 00:00:00 UTC>
diff:
? 2015-11-20 00:00:00 UTC
? 1
===
.
Finished in 1.269540744 seconds.
35 tests, 42 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0
notifications
97.1429% passed
27.57 tests/s, 33.08 assertions/s
8<8<8<-
Gem::Specification.date= in jessie seems to hot handle timezones correctly.
8<8<8<-
$ cat /tmp/testtime.rb
require 'time'
gemspec = Gem::Specification.new
gemspec.date = Time.parse('Fri, 20 Nov 2015 18:46:52 -0200')
puts gemspec.date
8<8<8<-
on sid:
8<8<8<-
$ cat /etc/debian_version
stretch/sid
$ ruby /tmp/testtime.rb
2015-11-20 00:00:00 UTC
$ TZ=Asia/Kolkata ruby /tmp/testtime.rb
2015-11-20 00:00:00 UTC
8<8<8<-
on jessie:
8<8<8<-
$ cat /etc/debian_version
8.5
$ ruby /tmp/testtime.rb
2015-11-20 00:00:00 UTC
$ TZ=Asia/Kolkata ruby /tmp/testtime.rb
2015-11-21 00:00:00 UTC
8<8<8<-
A fix is to use `Date` instead of `Time`. It's fixed in git, but I won't upload
just because of this.
signature.asc
Description: PGP signature
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#834155: rails: CVE-2016-6316: Possible XSS Vulnerability in Action View
Hi,
On Fri, Aug 12, 2016 at 05:18:55PM +0200, Salvatore Bonaccorso wrote:
> Source: rails
> Version: 2:4.1.8-1
> Severity: important
> Tags: security upstream patch
>
> Hi,
>
> the following vulnerability was published for rails.
>
> CVE-2016-6316[0]:
> Possible XSS Vulnerability in Action View
>
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
>
> For further information see:
>
> [0] https://security-tracker.debian.org/tracker/CVE-2016-6316
> [1] http://seclists.org/oss-sec/2016/q3/260
> [2]
> https://groups.google.com/forum/#!msg/rubyonrails-security/I-VWr034ouk/gGu2FrCwDAAJ
>
> Please adjust the affected versions in the BTS as needed.
AFAICT you got the versions right already. This issue affects stable,
while the other does not.
For stable, I have prepared a security update, have successfully tested
it on a sample application based on the upstream advisory description.
Attached you will find both the debdiff (rails.diff) and the actual
backported patch (CVE-2016-6316.patch); the later is easier to read than
the diff-in-diff part of the former.
For unstable, both issues will be fixed by 2:4.2.7.1-1 (being uploaded
RSN)
diff --git a/debian/changelog b/debian/changelog
index aa08ba6..2e09ba0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+rails (2:4.1.8-1+deb8u3) jessie-security; urgency=high
+
+ * Security update
+ * CVE-2016-6316: Possible XSS Vulnerability in Action View
+(Closes: Bug#834155)
+
+ -- Antonio Terceiro Mon, 22 Aug 2016 13:35:11 -0300
+
rails (2:4.1.8-1+deb8u2) jessie-security; urgency=high
* Security updates:
diff --git a/debian/patches/CVE-2016-6316.patch b/debian/patches/CVE-2016-6316.patch
new file mode 100644
index 000..4381974
--- /dev/null
+++ b/debian/patches/CVE-2016-6316.patch
@@ -0,0 +1,45 @@
+From: Andrew Carpenter
+Date: Thu, 28 Jul 2016 16:12:21 -0700
+Subject: ensure tag/content_tag escapes " in attribute vals
+
+Many helpers mark content as HTML-safe without escaping double quotes -- including `sanitize`. Regardless of whether or not the attribute values are HTML-escaped, we want to be sure they don't include double quotes, as that can cause XSS issues. For example: `content_tag(:div, "foo", title: sanitize('" onmouseover="alert(1);//'))`
+
+CVE-2016-6316
+
+Author: Andrew Carpenter
+Backported-by: Antonio Terceiro
+---
+ actionview/lib/action_view/helpers/tag_helper.rb | 2 +-
+ actionview/test/template/tag_helper_test.rb | 18 ++
+ 2 files changed, 19 insertions(+), 1 deletion(-)
+
+--- a/actionview/lib/action_view/helpers/tag_helper.rb
b/actionview/lib/action_view/helpers/tag_helper.rb
+@@ -169,7 +169,7 @@ module ActionView
+ def tag_option(key, value, escape)
+ value = value.join(" ") if value.is_a?(Array)
+ value = ERB::Util.h(value) if escape
+- %(#{key}="#{value}")
++ %(#{key}="#{value.gsub(/"/, '"'.freeze)}")
+ end
+ end
+ end
+--- a/actionview/test/template/tag_helper_test.rb
b/actionview/test/template/tag_helper_test.rb
+@@ -116,6 +116,16 @@ class TagHelperTest < ActionView::TestCa
+ end
+ end
+
++ def test_tag_does_not_honor_html_safe_double_quotes_as_attributes
++assert_dom_equal 'content',
++ content_tag('p', "content", title: '"'.html_safe)
++ end
++
++ def test_data_tag_does_not_honor_html_safe_double_quotes_as_attributes
++assert_dom_equal 'content',
++ content_tag('p', "content", data: { title: '"'.html_safe })
++ end
++
+ def test_skip_invalid_escaped_attributes
+ ['&1;', 'dfa3;', '& #123;'].each do |escaped|
+ assert_equal %(), tag('a', :href => escaped)
diff --git a/debian/patches/series b/debian/patches/series
index 2712fbb..5ecf424 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -9,3 +9,4 @@ CVE-2016-0752.patch
CVE-2016-0753.patch
CVE-2016-2097.patch
CVE-2016-2098.patch
+CVE-2016-6316.patch
From: Andrew Carpenter
Date: Thu, 28 Jul 2016 16:12:21 -0700
Subject: ensure tag/content_tag escapes " in attribute vals
Many helpers mark content as HTML-safe without escaping double quotes -- including `sanitize`. Regardless of whether or not the attribute values are HTML-escaped, we want to be sure they don't include double quotes, as that can cause XSS issues. For example: `content_tag(:div, "foo", title: sanitize('" onmouseover="alert(1);//'))`
CVE-2016-6316
Author: Andrew Carpenter
Backported-by: Antonio Terceiro
---
actionview/lib/action_view/helpers/tag_helper.rb | 2 +-
actionview/test/template/tag_helper_test.r
[DRE-maint] Bug#834907: gitlab: dependency on rails is too strict; breaks on every update
Package: gitlab Version: 8.9.0+dfsg-9 Severity: serious Justification: breaks on every rails update I am working on a rails security update (4.2.6 -> 4.2.7.1), and while testing reverse dependencies, gitlab breaks again: Verifying we have all required libraries... Could not find gem 'rails (= 4.2.6)' in any of the gem sources listed in your Gemfile or available on this machine. dpkg: error processing package gitlab (--configure): subprocess installed post-installation script returned error exit status 7 dpkg: dependency problems prevent configuration of autopkgtest-satdep: autopkgtest-satdep depends on gitlab (>= 0~); however: Package gitlab is not configured yet. dpkg: error processing package autopkgtest-satdep (--configure): dependency problems - leaving unconfigured This is not acceptable. Please make gitlab have sane dependencies. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#795484: ruby-rmagick: please make the build reproducible
On Tue, Aug 16, 2016 at 07:57:25PM +0100, Chris Lamb wrote: > Hi Antonio, > > > this patch looks rather invasive. I will upload a reproducible package > > with a more localized change soon. > > .. on the other hand, exposing the ability for other folks to seed the > pseudo random generator seems useful enough to keep, no? probably, but I would rather have that introduced upstream first. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#831244: ruby-eventmachine: FTBFS: Build hangs minutes of inactivity
On Sun, Jul 31, 2016 at 10:21:39PM +0200, Christian Hofstaedtler wrote: > * Lucas Nussbaum [160731 20:17]: > > During a rebuild of all packages in sid, your package failed to build on > > amd64. > > So I tried debugging this a bit; for me the 'TestFileWatch' test > hangs, both with our 1.0.7-3 and also if I update that to 1.2.0.1. > > Now from what I see the test uses inotify; if our test builds use > overlayfs, maybe that just does not support inotify (properly). if it's a single test that hangs we can probably report the bug upstream and skip it for now? signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#830987: libjs-handlebars: missing source
On Sat, Jul 23, 2016 at 10:05:18AM +0530, Pirate Praveen wrote: > On Wed, 13 Jul 2016 15:44:34 +0100 Ansgar Burchardt wrote: > > I briefly looked into the package due to the discussion on -devel@ and > > the ctte bug.  The source for the javascript code seems to be missing: > > it contains generated lexer/parser code, see the upstream source at > > > >   https://github.com/wycats/handlebars.js/blob/v1.3.0/src/handlebars.l > > > > (Just search for "yytext" in handlebars-v1.3.0.js > > or vendor/assets/javascripts/handlebars.js for ruby-handlebar-assets.) > > > > That seems to be a bit more than just concatenating files. > > > > Ansgar > > > > > > Ansgar, > > Can I upload it to contrib till ctte decides? I could then reduce the > severity and let it migrate to testing. A proper fix can take a long > time and I'd like to see diaspora (which depends on > ruby-handlebars-assets) in stretch, at least in contrib. contrib also requires the package to be free software, which implies having proper source code. what contrib allows beyond what is allowed in main is requiring non-free software to work. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#827835: XMLParser Ruby module: fails to build with Expat 2.2.0
Dear Yoshida, For several years he have shipped your XMLParser Ruby module in Debian, and it is even used by a tool that is very important to the Debian community (apt-listbugs). Recently it was detected that XMLParser fails to build, and I suspect that is related to a new version of Expat (2.2.0). The details can be found in the Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827835 Do you think you would be able to look at this? Thanks in advance! signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#830353: ruby-kgio: FTBFS: ERROR: Test "ruby2.3" failed.
Control: retitle -1 ruby-kgio: FTBFS on Amazon EC2: ERROR: Test "ruby2.3"
failed.
Control: severity -1 important
On Fri, Jul 08, 2016 at 06:53:29PM +, Eric Wong wrote:
> Lucas Nussbaum wrote:
> > The full build log is available from:
> >
> > http://people.debian.org/~lucas/logs/2016/07/07/ruby-kgio_2.10.0-1_unstable_reb.normal.log
> >
> > A list of current common problems and possible solutions is available at
> > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> >
> > About the archive rebuild: The rebuild was done on EC2 VM instances from
> > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> > failed build was retried once to eliminate random failures.
>
> Thanks for the report. Can you try the patch below?
Didn't help.
I can't, however, reproduce this locally on my workstation.
I remember hitting this type of issue with kgio whenever I did rebuilds of all
Ruby packages on an Amazon EC2 instance, and then couldn't reproduce it
locally.
If you want to give a closer look I can give you access to the VM I use for
these builds, where I can consistently reproduce this.
> I'd be interested to know what non-standard sysctl knobs are set
> for kernel socket buffer sizes (in /proc/sys/net/{core,ipv4}/*mem*)
$ tail -n 1000 /proc/sys/net/{core,ipv4}/*mem*
==> /proc/sys/net/core/optmem_max <==
20480
==> /proc/sys/net/core/rmem_default <==
212992
==> /proc/sys/net/core/rmem_max <==
16777216
==> /proc/sys/net/core/wmem_default <==
212992
==> /proc/sys/net/core/wmem_max <==
16777216
==> /proc/sys/net/ipv4/igmp_max_memberships <==
20
==> /proc/sys/net/ipv4/tcp_mem <==
2954019 3938693 5908038
==> /proc/sys/net/ipv4/tcp_rmem <==
40961258291216777216
==> /proc/sys/net/ipv4/tcp_wmem <==
40961258291216777216
==> /proc/sys/net/ipv4/udp_mem <==
2954019 3938693 5908038
==> /proc/sys/net/ipv4/udp_rmem_min <==
4096
==> /proc/sys/net/ipv4/udp_wmem_min <==
4096
> You can also increase the 20M to 30M or whatever (otoh, that
> means using more memory during tests :<)
>
> I'm not comfortable calling setsockopt to set SO_{SND,RCV}BUF
> knobs since that can trigger VM deadlock bugs on some older
> kernels, too.
>
> Anyways, most of the kgio functionality is in Ruby 2.3 nowadays
> and kgio can probably go away when support for 2.2 can be
> dropped in gems.
In Debian we don't even have 2.2 anymore. The only things using kgio are
unicorn and rainbows. Maybe if their dependency on kgio could be skipped on
Ruby 2.3, we could drop kgio from Debian.
signature.asc
Description: PGP signature
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#831347: diaspora: bogus dependency on ruby-rails-autolink
Package: diaspora Version: 0.5.9.1+debian-1 Severity: important ruby-rails-autolink is RC buggy (#808517), and maybe abandoned upstream. the diaspora code seems to have moved away from it on 0.5.0~git.20141112.b4a24bd49e so the diaspora dependency is probably not warranted. we should probably rid of ruby-rails-autolink completely after diaspora drops the dependency. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Antonio Terceiro signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#829254: asset:precompile error when updating diaspora to 0.5.9.1
On Thu, Jul 07, 2016 at 07:44:00AM +0530, Pirate Praveen wrote: > > > On 2016, ജൂലൈ 7 1:38:54 AM IST, Antonio Terceiro wrote: > >This is a very shitty way of making things work. So your approach is, > >instead of fixing the Debian package, adding an embedded copy of the > >upstream sources? > > No, you are just shouting baseless things that does not help at all. > First, if I had fixed it the way you imply, I'd have closed this bug. > Second, this was only one method of troubleshooting. > > Did you check the git commits before replying? It would be better if > people were helping fix things. It took 3-4 days of troubleshooting > and this is how you are rewarded at the end of finding the root cause? Fair enough, I misinterpreted what I read then. I am sorry for that. -- Antonio Terceiro signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#829254: asset:precompile error when updating diaspora to 0.5.9.1
On Wed, Jul 06, 2016 at 11:18:09PM +0530, Pirate Praveen wrote: > [will drop debian-ruby from further updates] > > On Wednesday 06 July 2016 09:07 PM, Pirate Praveen wrote: > > I was able to successfully install 0.5.5.1 in unstable but 0.5.7.1 in > > experimental is failing with same error. So it could be either new code > > in diaspora or one of the changed dependencies that is causing error. I > > will try to reproduce the error in unstable by adding new dependencies > > in experimental once by one. If you know a better way, let me know. > > > > I tracked down the issue to handlebars_assets. After updating > handlebars_assets to 0.23.0, diaspora 0.5.5.1 is also failing with the > same error. > > So I replaced ruby-handlebars-assets deb package with handlebars_assets > gem and it is also working. This is a very shitty way of making things work. So your approach is, instead of fixing the Debian package, adding an embedded copy of the upstream sources? signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#829224: ruby-redis-actionpack: FTBFS: Could not find 'pkg-config' (~> 1.1.7) among 32 total gem(s) (Gem::LoadError)
Control: forcemerge 829175 829224 Control: forcemerge 829175 829225 Control: forcemerge 829175 829226 Control: forcemerge 829175 829227 Control: forcemerge 829175 829229 Control: forcemerge 829175 829234 All these issues have been fixed at their source which was ruby-nokogiri. 1.6.8-1 missed a dependency and that was fixed in 1.6.8-2. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#827052: gem2deb can't handle git usage in devise gemspec
Control: tag -1 + moreinfo On Sat, Jun 11, 2016 at 10:22:23PM +0530, Pirate Praveen wrote: > Package: gem2deb > version: 0.30.1 > > This is the error I see, > > Invalid gemspec in [devise.gemspec]: No such file or directory - git > /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:137:in `gsub!': invalid > byte sequence in US-ASCII (ArgumentError) > from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:137:in `block in > load_modified_gemspec' > from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:136:in `each' > from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:136:in > `load_modified_gemspec' > from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:113:in `load_gemspec' > from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:33:in `block in > initialize' > from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:32:in `chdir' > from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:32:in `initialize' > from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:73:in `new' > from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:73:in > `do_check_dependencies' > from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:66:in `run_tests' > from /usr/bin/gem2deb-test-runner:53:in `' > ERROR: Test "ruby2.3" failed. Exiting. can't reproduce; just built ruby-device from git [(4.1.1-1) UNRELEASED] with sbuild and it worked just fine signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#826674: gem2deb: FTBFS: test: running dh-make-ruby against a directory should get the package name correctly. :F
On Tue, Jun 07, 2016 at 09:17:06PM +0200, Andreas Beckmann wrote: > Source: gem2deb > Version: 0.30.2 > Severity: serious > Justification: fails to build from source > > Hi, > > gem2deb FTBFS everywhere: > https://buildd.debian.org/status/package.php?p=gem2deb&suite=unstable > > test: running dh-make-ruby against a directory should get the package name > correctly. :F > === > Failure: test: running dh-make-ruby against a directory should get the > package name correctly. (DhMakeRubyTest) > /«PKGBUILDDIR»/test/unit/dh_make_ruby_test.rb:109:in `block (2 levels) in > ' > <["ruby-simplegit"]> expected but was > <[]> > > diff: > ? ["ruby-simplegit"] > === > : (0.058675) At first I could not reproduce this, and was only able to when I moved my ~/.sbuildrc away. It includes only the following: $build_source = 1; $build_arch_all = 1; I still have no idea why any of those would make the build fail, since gem2deb just moved to providing only arch:any packages. in $build_source should never make any difference, and neither should $build_arch_all. I am still puzzled. signature.asc Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
