Bug#1063630: [DRE-maint] Bug#1063630: Upload?
Sorry for having left this aside for so long. Nothing is blocking this upload, which will help fix RC bug #1073364. I am uploading this right now. Cédric
Bug#1070652: [DRE-maint] Bug#1070652: ruby-json: breaks how-can-i-help
Hi! I am reassigning this bug to the `how-can-i-help` package. Indeed, the script `/usr/bin/how-can-i-help` uses implicitly the OpenStruct class, without requiring explicitly 'ostruct'. The class was loaded transitively from the json gem it seems. Adding below line 35 the following line: require 'ostruct' fixes the bug. Cheers, Cédric Quoting Vincent Lefevre (2024-05-06 17:41:49) > Package: ruby-json > Version: 2.7.2+dfsg-1 > Severity: grave > Justification: renders package unusable > This new ruby-json version breaks how-can-i-help: > [...] > Unpacking ruby-json:amd64 (2.7.2+dfsg-1) over (2.6.3+dfsg-1+b2) ... > Setting up ruby-json:amd64 (2.7.2+dfsg-1) ... > /usr/bin/how-can-i-help:155:in `': uninitialized constant OpenStruct > (NameError) > proxy_uri = $proxy_url.nil? ? OpenStruct.new : URI.parse($proxy_url) > ^^ > -- System Information: > Debian Release: trixie/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, > 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), > (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > Kernel: Linux 6.6.15-amd64 (SMP w/12 CPU threads; PREEMPT) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, > TAINT_UNSIGNED_MODULE > Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > Versions of packages ruby-json depends on: > ii libc6 2.38-7 > ii libruby1:3.1+nmu1 > ii libruby3.1t64 3.1.2-8.3 > ruby-json recommends no packages. > ruby-json suggests no packages. > -- no debconf information--- /tmp/how-can-i-help 2024-05-07 01:08:00.390399139 +0200 +++ /usr/bin/how-can-i-help 2024-05-07 00:59:24.082457226 +0200 @@ -33,6 +33,7 @@ require 'fileutils' require 'time' require 'etc' +require 'ostruct' include Debian
Bug#1054749: ruby-android-key-attestation: bug in ruby-pry-byebug 3.9.0, fixed in 3.10.1
Package: ruby-android-key-attestation Followup-For: Bug #1054749 Hi, This bug is in fact in ruby-pry-byebug, version v3.9.0-1. It was fixed by the upload of 3.10.1-1. This is a duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054737 signature.asc Description: PGP signature
Bug#1028403: wtype: descriptions refers to the 'wdotool' name instead of wtype
Package: wtype Version: 0.4-2 Severity: minor Dear Maintainer, Looking at the description of the package, I see that it mentions 'wdotool', whereas the package and the tool under /usr/bin are called wtype, and there is no indication of wdotool. Thanks for maintaing that tool! Best wishes, Cédric signature.asc Description: PGP signature
Bug#1017524: [DRE-maint] Bug#1017524: status?
Hi, I recently looked at failures in jekyll. Jekyll is broken in several ways in unstable due to version constraints on the dependencies. One can easily relax the version dependency on mercenary in the gemdeps (no changes needed). One would need a newer version of jekyll to fix most of them. But the blocking point seems that even the latest jekyll release requires ruby-liquid < 5, whereas we have 5.4. There is some issue opened upstream to try to use liquid 5.x, https://github.com/jekyll/jekyll/issues/9094 but there are some missing pieces... Not being a user of jekyll myself, I could not test yet if the code in jekyll indicated in this issue is enough to make it work with liquid 5.x, if we simply relax the version dependency in gemdeps. Cheers, Cédric
Bug#1024204: imv: typo in description
Package: imv Version: 4.3.0-1.1+b2 Severity: minor Dear Maintainer, The package indicates two executables in the second paragraph: `imv-x11` and `x11-wayland`. The second one should be `imv-wayland`. Thanks! Best, Cédric signature.asc Description: PGP signature
Bug#1021262: failing test disabled in 0.2.21-2
Hi, I disabled the failing test on all arches except amd64 on 0.2.21-2, until the issue is fixed upstream. Since the package now builds, and other tests are passing, I am changing the severity of the bug to 'normal'. Thanks, Cédric signature.asc Description: signature
Bug#1016272: transient bug in latex
This bug seems caused by a transient bug due to a non-UTF8 character in
one of the included files by latex(?). This problem was present with
texlive-latex-base 2022.20220722-1, but after the recent upgrade to
2022.20220923-1, the problem has disappeared, and all tests pass.
For the record, please find attached one of the latex files produced
with kramdown which was causing the problematic character, together with
the output of the failing compilation log with latex from
texlive-latex-base/2022.20220722-1, and the succeeding compilation with
texlive-latex-base/2022.20220923-1.
Best wishes,
Cédric
\documentclass{scrartcl}
\usepackage[utf8x]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{listings}
\usepackage{hyperref}
\setcounter{footnote}{0}
\hypersetup{colorlinks=true,urlcolor=blue}
\begin{document}
This is a % simple
paragraph.
This is a % simple
paragraph.
This is a % simple {:/other} paragraph
.
This is a paragraph.
This is a \{:/comment\} simple \{:/\} paragraph.
This is a \{::comment\} paragraph.
\end{document}
This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian)
(preloaded format=latex)
restricted \write18 enabled.
entering extended mode
(./latex.tex
LaTeX2e <2022-06-01> patch level 5
L3 programming layer <2022-07-15>
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrartcl.cls
Document Class: scrartcl 2022/07/04 v3.37 KOMA-Script document class (article)
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrkbase.sty
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrbase.sty
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile.sty
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile-hook.sty
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlogo.sty)))
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)))
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/tocbasic.sty)
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrsize11pt.clo)
(/usr/share/texlive/texmf-dist/tex/latex/koma-script/typearea.sty))
(/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
(/usr/share/texlive/texmf-dist/tex/latex/ucs/utf8x.def))
(/usr/share/texlive/texmf-dist/tex/latex/ucs/ucs.sty
(/usr/share/texlive/texmf-dist/tex/latex/ucs/data/uni-global.def))
(/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty)
(/usr/share/texlive/texmf-dist/tex/latex/listings/listings.sty
(/usr/share/texlive/texmf-dist/tex/latex/listings/lstmisc.sty)
(/usr/share/texlive/texmf-dist/tex/latex/listings/listings.cfg))
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
(/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty)
(/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty)
(/usr/share/texlive/texmf-dist/tex/generic/pdftexcmds/pdftexcmds.sty
(/usr/share/texlive/texmf-dist/tex/generic/infwarerr/infwarerr.sty))
(/usr/share/texlive/texmf-dist/tex/generic/kvsetkeys/kvsetkeys.sty)
(/usr/share/texlive/texmf-dist/tex/generic/kvdefinekeys/kvdefinekeys.sty)
(/usr/share/texlive/texmf-dist/tex/generic/pdfescape/pdfescape.sty)
(/usr/share/texlive/texmf-dist/tex/latex/hycolor/hycolor.sty)
(/usr/share/texlive/texmf-dist/tex/latex/letltxmacro/letltxmacro.sty)
(/usr/share/texlive/texmf-dist/tex/latex/auxhook/auxhook.sty)
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/nameref.sty
(/usr/share/texlive/texmf-dist/tex/latex/refcount/refcount.sty)
(/usr/share/texlive/texmf-dist/tex/generic/gettitlestring/gettitlestring.sty
(/usr/share/texlive/texmf-dist/tex/latex/kvoptions/kvoptions.sty)))
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
(/usr/share/texlive/texmf-dist/tex/generic/intcalc/intcalc.sty)
(/usr/share/texlive/texmf-dist/tex/generic/etexcmds/etexcmds.sty)
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/puenc.def)
(/usr/share/texlive/texmf-dist/tex/latex/url/url.sty)
(/usr/share/texlive/texmf-dist/tex/generic/bitset/bitset.sty
(/usr/share/texlive/texmf-dist/tex/generic/bigintcalc/bigintcalc.sty))
(/usr/share/texlive/texmf-dist/tex/latex/base/atbegshi-ltx.sty))
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hdvips.def
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/pdfmark.def
(/usr/share/texlive/texmf-dist/tex/latex/rerunfilecheck/rerunfilecheck.sty
(/usr/share/texlive/texmf-dist/tex/latex/base/atveryend-ltx.sty)
(/usr/share/texlive/texmf-dist/tex/generic/uniquecounter/uniquecounter.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-dvips.def)
No file latex.aux.
(/usr/share/texlive/texmf-dist/tex/latex/ucs/ucsencs.def)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/color.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-def/dvips.def)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/dvipsnam.def)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/mathcolor.ltx))
Package hyperref Warning: Rerun to get /PageLabels entry.
(/usr/share/texlive/texmf-dist/tex/latex/bookmark/bookmark.sty
(/usr/share/texlive/texmf-dist/tex/latex/bo
Bug#1005833: [DRE-maint] Bug#1005833: src:ruby-redis: fails to migrate to testing for too long: autopkgtest regression
Quoting Paul Gevers (2022-03-21 21:13:29) > Is there any progress on this issue? Is no progress is there another way > to move the problem forward? E.g. revert ruby-redis to the previous > version if redis and fakeredis can agree on the change in behavior? I am preparing an upload of ruby-fakeredis with an upstream PR accomodating the fact that 'exists' returns now an integer, plus some modifications of the test suite. This should fix the issue. Best wishes, Cédric
Bug#1006042: Processed: fixed 1006042 in 0.2.0-1
Dear Sandro Quoting Sandro Tosi (2022-02-23 18:14:41) > are you sure this is correct? rich never had a 0.2.0-1 upload Sorry, I messed up when copying with my big fingers another bug number. Thank you for noticing, and apologies for the noise. Best wishes, Cédric signature.asc Description: signature
Bug#1002115: bug in texlive?
I suspect this is caused by a change in texlive.
Here is the diff for the list of packages used in tests in ci.debian.net
between the last green and the (almost) first red:
--- kramdown-ok 2022-01-26 14:35:12.162946913 +0100
+++ kramdown-nok2022-01-26 14:35:21.802998157 +0100
@@ -1,7 +1,7 @@
fontconfig-config 2.13.1-4.2
fonts-dejavu-core 2.37-2
fonts-lmodern 2.004.5-6.1
-gem2deb-test-runner1.7
+gem2deb-test-runner1.8
kramdown 2.3.1-3
libapache-pom-java 18-1
libbrotli1 1.0.9-2+b3
@@ -11,7 +11,7 @@
libfontbox-java1:1.8.16-2
libfontconfig1 2.13.1-4.2
libfreetype6 2.11.0+dfsg-1
-libglib2.0-0 2.70.1-1
+libglib2.0-0 2.70.2-1
libgraphite2-3 1.3.14-1
libharfbuzz0b 2.7.4-1
libice62:1.0.10-1
@@ -70,13 +70,13 @@
rubygems-integration 1.18
t1utils1.41-4
tex-common 6.17
-texlive-base 2021.20210921-1
+texlive-base 2021.20211127-1
texlive-binaries 2021.20210626.59705-1
-texlive-fonts-recommended 2021.20210921-1
-texlive-latex-base 2021.20210921-1
-texlive-latex-extra2021.20210921-1
-texlive-latex-recommended 2021.20210921-1
-texlive-pictures 2021.20210921-1
+texlive-fonts-recommended 2021.20211127-1
+texlive-latex-base 2021.20211127-1
+texlive-latex-extra2021.20211127-1
+texlive-latex-recommended 2021.20211127-1
+texlive-pictures 2021.20211127-1
tidy 2:5.6.0-11
x11-common 1:7.7+23
xdg-utils 1.1.3-4.1
The test failure comes from the filtering of the latex output. Removing
the 'scan and join' part works around the issue.
diff --git a/test/test_files.rb b/test/test_files.rb
index 7e2ccad..bc5523a 100644
--- a/test/test_files.rb
+++ b/test/test_files.rb
@@ -150,7 +150,7 @@ class TestFiles < Minitest::Test
io.close_write
io.read
end
- assert($?.exitstatus == 0, result.scan(/^!(.*\n.*)/).join("\n"))
+ assert($?.exitstatus == 0, result)
end
end
end
signature.asc
Description: PGP signature
Bug#1004299: ruby-net-ssh: FTBFS in sid
Package: ruby-net-ssh Version: 1:6.1.0-2 Hi, When trying to rebuild ruby-net-ssh in sid, I get test failures related to DSA cryptography. They all have the message: OpenSSL:PKey::DSAError: bad sig size Hopefully, this is the relevant part. Full log attached Finished in 4.013999s, 372.1974 runs/s, 1244.6442 assertions/s. 1) Error: Authentication::TestAgent#test_add_dsa_cert_identity: OpenSSL::PKey::DSAError: bad sig size /<>/lib/net/ssh/transport/openssl.rb:115:in `ssh_do_sign' /<>/lib/net/ssh/authentication/certificate.rb:91:in `sign!' /<>/test/authentication/test_agent.rb:414:in `make_cert' /<>/test/authentication/test_agent.rb:273:in `test_add_dsa_cert_identity' 2) Error: Authentication::TestKeyManager#test_each_identity_should_load_from_implicit_cert_file: OpenSSL::PKey::DSAError: bad sig size /<>/lib/net/ssh/transport/openssl.rb:115:in `ssh_do_sign' /<>/lib/net/ssh/authentication/certificate.rb:91:in `sign!' /<>/test/authentication/test_key_manager.rb:320:in `rsa_cert' /<>/test/authentication/test_key_manager.rb:76:in `test_each_identity_should_load_from_implicit_cert_file' 3) Error: Authentication::TestKeyManager#test_each_identity_should_ignore_explicit_cert_file_unless_matching_key_is_avaiable: OpenSSL::PKey::DSAError: bad sig size /<>/lib/net/ssh/transport/openssl.rb:115:in `ssh_do_sign' /<>/lib/net/ssh/authentication/certificate.rb:91:in `sign!' /<>/test/authentication/test_key_manager.rb:320:in `rsa_cert' /<>/test/authentication/test_key_manager.rb:104:in `test_each_identity_should_ignore_explicit_cert_file_unless_matching_key_is_avaiable' 4) Error: Authentication::TestKeyManager#test_each_identity_should_load_from_explicit_cert_file_given_matching_key_is_loaded: OpenSSL::PKey::DSAError: bad sig size /<>/lib/net/ssh/transport/openssl.rb:115:in `ssh_do_sign' /<>/lib/net/ssh/authentication/certificate.rb:91:in `sign!' /<>/test/authentication/test_key_manager.rb:320:in `rsa_cert' /<>/test/authentication/test_key_manager.rb:88:in `test_each_identity_should_load_from_explicit_cert_file_given_matching_key_is_loaded' 5) Error: Authentication::TestKeyManager#test_each_identity_should_match_explicit_keycert_with_agent_provided_identity: OpenSSL::PKey::DSAError: bad sig size /<>/lib/net/ssh/transport/openssl.rb:115:in `ssh_do_sign' /<>/lib/net/ssh/authentication/certificate.rb:91:in `sign!' /<>/test/authentication/test_key_manager.rb:320:in `rsa_cert' /<>/test/authentication/test_key_manager.rb:141:in `test_each_identity_should_match_explicit_keycert_with_agent_provided_identity' 6) Error: Authentication::TestKeyManager#test_sign_with_agent_originated_key_should_be_signable_through_explicitly_loaded_cert: OpenSSL::PKey::DSAError: bad sig size /<>/lib/net/ssh/transport/openssl.rb:115:in `ssh_do_sign' /<>/lib/net/ssh/authentication/certificate.rb:91:in `sign!' /<>/test/authentication/test_key_manager.rb:320:in `rsa_cert' /<>/test/authentication/test_key_manager.rb:218:in `test_sign_with_agent_originated_key_should_be_signable_through_explicitly_loaded_cert' 1494 runs, 4996 assertions, 0 failures, 6 errors, 0 skips rake aborted! Command failed with status (1): [ruby -w /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/test_all.rb" "test/test_buffer.rb" "test/test_buffered_io.rb" "test/test_config.rb" "test/test_key_factory.rb" "test/test_known_hosts.rb" "test/test_proxy_jump.rb" -v] /usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `' Tasks: TOP => default (See full trace by running task with --trace) ERROR: Test "ruby3.0" failed. Exiting. dh_auto_install: error: dh_ruby --install /<>/debian/ruby-net-ssh returned exit code 1 make: *** [debian/rules:7: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Source: ruby-net-ssh Version: 1:6.1.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled ruby-net-ssh_6.1.0-2_amd64-2022-01-24T13:24:15Z.build.gz Description: application/gzip signature.asc Description: signature
Bug#946683: nokogumbo has been merged into nokogiri
Hi, It seems that since nokogiri 1.12, the functionalities of nokogumbo have been merged into nokogiri. html-proofer does not depend on nokogumbo anymore, and uses nokogiri >=1.12. It seems reasonable to upgrade nokogiri (I am trying to do it), make all packages depending on ruby-nokogumbo to switch to nokogiri if it is not already the case, and then remove nokogumbo. Best wishes, Cédric signature.asc Description: signature
Bug#892058: thanks for the reminder
> This is a courtesy reminder that your Debian key is expiring on 2022-01-20. > [...] > If you like this service, please leave a favorable comment here [2]. Thanks Felix Lechner for the reminder about the expiration of my GPG key approaching. I found it very useful! Best wishes, Cédric signature.asc Description: signature
Bug#996386: other error with mechanize 2.7.7-3
The error in the log comes from ruby-mechanize < 2.7.7-3 not depending
on ruby-webrick.
Now, there are 7 test failures of the following kind:
> 1) ShamRack mounted Rack application can be accessed using open-uri
> Failure/Error: response = open("http://www.greetings.com";)
>
> Errno::ENOENT:
>No such file or directory @ rb_sysopen - http://www.greetings.com
> # ./spec/sham_rack_spec.rb:42:in `initialize'
> # ./spec/sham_rack_spec.rb:42:in `open'
> # ./spec/sham_rack_spec.rb:42:in `block (3 levels) in '
>
> 2) ShamRack.at with a block mounts associated block as an app
> Failure/Error: expect(open("http://simple.xyz";).read).to eq("Easy, huh?")
>
> Errno::ENOENT:
>No such file or directory @ rb_sysopen - http://simple.xyz
> # ./spec/sham_rack_spec.rb:76:in `initialize'
> # ./spec/sham_rack_spec.rb:76:in `open'
> # ./spec/sham_rack_spec.rb:76:in `block (4 levels) in '
log attached.
Cheers,
Cédricsbuild (Debian sbuild) 0.81.2 (31 January 2021) on kashan
+==+
| ruby-sham-rack 1.4.1-2 (amd64) Thu, 18 Nov 2021 00:00:33 + |
+==+
Package: ruby-sham-rack
Version: 1.4.1-2
Source Version: 1.4.1-2
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full
I: NOTICE: Log filtering will replace
'var/run/schroot/mount/unstable-amd64-sbuild-7945e2af-3685-497b-8e1b-182c61bf38b0'
with '<>'
I: NOTICE: Log filtering will replace
'build/ruby-sham-rack-hdLhOr/resolver-A62XUh' with '<>'
+--+
| Update chroot|
+--+
Get:1 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ InRelease
Ign:1 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ InRelease
Get:2 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ Release
[951 B]
Get:2 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ Release
[951 B]
Get:3 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./
Release.gpg
Ign:3 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./
Release.gpg
Get:4 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ Packages
[659 B]
Get:5 http://deb.debian.org/debian unstable InRelease [165 kB]
Err:4 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ Packages
Could not open file
/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive/./Packages - open (13:
Permission denied)
Get:4 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ Packages
[1084 B]
Get:6 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB]
Ign:6 http://deb.debian.org/debian unstable/main Sources.diff/Index
Get:7 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index
[63.6 kB]
Ign:7 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index
Get:8 http://deb.debian.org/debian unstable/main Sources [9378 kB]
Get:9 http://deb.debian.org/debian unstable/main amd64 Packages [8838 kB]
Fetched 18.5 MB in 2s (8057 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages were automatically installed and are no longer required:
fontconfig-config fonts-dejavu-core libbrotli1 libbsd0 libc-devtools
libdeflate0 libexpat1 libfontconfig1 libfreetype6 libgd3 libjbig0
libjpeg62-turbo libmd0 libpng16-16 libtiff5 libwebp6 libx11-6 libx11-data
libxau6 libxcb1 libxdmcp6 libxpm4 manpages manpages-dev sensible-utils ucf
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
libsemanage2 libsepol2
The following packages will be upgraded:
apt bash binutils binutils-common binutils-x86-64-linux-gnu coreutils cpp-10
dash debconf g++-10 gcc-10 gcc-10-base libapt-pkg6.0 libbinutils
libcrypt-dev libcrypt1 libctf-nobfd0 libctf0 libdebconfclient0 libexpat1
libgcc-10-dev libgmp10 libjpeg62-turbo libpcre2-8-0 libselinux1
libsemanage-common libsemanage1 libstdc++-10-dev libsystemd0 libtasn1-6
libtinfo6 libudev1 linux-libc-dev login ncurses-base ncurses-bin passwd
tzdata
38 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 35.1 MB/58.4 MB of archives.
After this operation, 980 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian unstable/main amd64 g++-10 amd64 10.3.0-12
[9433 kB]
Get:2 http://deb.debian.org/debian unstable/main amd64 gcc-10 amd64 10.3.0-12
[17.1 MB]
Get:3 http://deb.debian.org/debian unstable/main amd64 cpp-10 amd64 10.3.0-12
[8571 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 35.1 M
Bug#996125: reassign to ruby-rspec-rails or rails?
The actual part reporting the error seems to be: > An error occurred while loading ./spec/rails/integration/forms_spec.rb. > Failure/Error: require 'rspec/rails' > > ArgumentError: > wrong number of arguments (given 4, expected 3) > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # ./spec/rails/rails_spec_helper.rb:7:in `' > # ./spec/rails/integration/forms_spec.rb:1:in `require' > # ./spec/rails/integration/forms_spec.rb:1:in `' which seems to be a duplicate of #996377. So it probably has to be merged with that one. signature.asc Description: signature
Bug#996477: E1208: -complete used without allowing arguments
Package: vim-tlib Version: 1.27-5 Severity: normal Tags: upstream Dear maintainer, Since a recent upgrade of vim, the tlib plugin is issuing an error when launching vim: Error detected while processing /var/lib/vim/addons/plugin/02tlib.vim: line 77: E1208: -complete used without allowing arguments This error has been reported upstream, and is not present anymore in more recent version of the plugin. Could you please update the package to a more recent version? Thank you in advance! -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vim-tlib depends on: ii vim2:8.2.3455-2 ii vim-addon-manager 0.5.10 ii vim-gtk3 [vim] 2:8.2.3455-2 vim-tlib recommends no packages. vim-tlib suggests no packages. -- no debconf information
Bug#993829: Please ship nokogiri.h header file
Hi Daniel, Le Sun, Sep 19, 2021 at 10:13:59PM +0200, Daniel Leidert a écrit : > Am Sonntag, dem 19.09.2021 um 17:31 +0200 schrieb Cédric Boutillier: > > I have been looking at the bugs on ruby-nokogiri before trying to update > > it to the new upstream version. > > > > Using the gem install layout is not enough to have the > > ext/nokogiri/nokogiri.h installed. As I understand it, gem_installer.rb > > in gem2deb is removing all sources from the ext/ directory. Actually, I pushed a couple of commits today to fix that: I changed the 'gemspec' target of debian/rules slightly to call a Ruby script filtering non-needed dependencies and the ports/* and patches/* parts of the files metadata. Removing the ports/* from the list of files fixed the gem install layout part. Remains the question about where to put the header file (in the gem install layout context). > RUBYHDRDIR (/usr/include/ruby-) > SITEHDRDIR (/usr/include/ruby-/site_ruby) > VENDORHDRDIR (/usr/include/ruby-/vendor_ruby) In the context of an installation under vendor_ruby, I would go for VENDORHDRDIR, although I would have hoped for a path which does not depend on the ruby version. Best wishes, Cédric signature.asc Description: PGP signature
Bug#993829: Please ship nokogiri.h header file
Hi, I have been looking at the bugs on ruby-nokogiri before trying to update it to the new upstream version. Using the gem install layout is not enough to have the ext/nokogiri/nokogiri.h installed. As I understand it, gem_installer.rb in gem2deb is removing all sources from the ext/ directory. So my questions are: - should we modify gem2deb to allow for installation of headers file? (at least maybe the ones added to the WHITELIST) - if so, should we install them, as the gem command does, in the /usr/lib/ruby/gems/x.y.z/gems/package-a.b.c/ext subdirectory? OR - would it make sense for nokogumbo to use instead Built-Using: to use the nokogiri.h present in the source package? what would be the best strategy for this situation? Best wishes, Cédric signature.asc Description: PGP signature
Bug#993739: blends-common: tempfile has to be replaced by mktemp
Hi Andreas,
I have submitted a merge request on salsa
https://salsa.debian.org/blends-team/blends/-/merge_requests/8
applying the patch attached.
Best wishes,
Cédric
>From e555f8405ea4e2cf90a8d50261545665ab49605c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?C=C3=A9dric=20Boutillier?=
Date: Wed, 8 Sep 2021 12:14:02 +0200
Subject: [PATCH] Replace deprecated temfile by mktemp
debianutils 5.x removed the script `tempfile`, which has to be replaced
by `mktemp` from the coreutils package.
---
debian/changelog | 5 +
share/blends/unixgroups/blend-actions | 2 +-
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/debian/changelog b/debian/changelog
index 88c3aa1..d0f823d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,7 +1,12 @@
blends (0.7.4) UNRELEASED; urgency=medium
+ [ Gianfranco Costamagna ]
* Add Ubuntu disco and eoan sources.list files
+ [ Cédric Boutillier ]
+ * Replace deprecated `tempfile` by `mktemp` in blend-actions script (Closes:
+#993739)
+
-- Gianfranco Costamagna Fri, 14 Jun 2019 00:58:11 +0200
blends (0.7.3) experimental; urgency=medium
diff --git a/share/blends/unixgroups/blend-actions b/share/blends/unixgroups/blend-actions
index 2b12a50..9452d54 100644
--- a/share/blends/unixgroups/blend-actions
+++ b/share/blends/unixgroups/blend-actions
@@ -126,7 +126,7 @@ getAllUsers() {
RET=64 # EX_USAGE
else
SIMPLE=$1
- TMPFILE=`tempfile`
+ TMPFILE=`mktemp`
(IFS=":"
while read user pass uid gid name rest ; do
if [ "$uid" != "" ] ; then
--
2.33.0
Bug#993739: blends-common: tempfile has to be replaced by mktemp
Package: blends-common Version: 0.7.2 Followup-For: Bug #993739 Hi I have just experienced this bug today too. According to the NEWS.Debian file in debianutils package, the `tempfile` script was removed from debianutils in the version 5.0. Therefore, its usage in /usr/share/blends/unixgroups/blend-actions should indeed be replaced by mktemp from coreutils. Best wishes, Cédric
Bug#989151: aerc: please package newer upstream version (0.5.2 as of today)
Package: aerc Severity: wishlist Dear Maintainer, Thank you for introducing this software in Debian. Could you please update the package of aerc to a newer upstream version? The current one, 0.5.2 according to the website, has been out for more than 6 months. Thanks a lot! Cédric signature.asc Description: PGP signature
Bug#988084: unblock: ruby-rugged/1.1.0+ds-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package ruby-rugged
Version 1.1.0+ds-3 in testing was trying to access internet during tests
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987650
As indicated in the bug report, Ubuntu had a patch for that issue
https://git.launchpad.net/~usd-import-team/ubuntu/+source/ruby-rugged/tree/debian/patches/ubuntu-skip-network-tests.patch?id=2f18d60418e71d96ef34c5627370752f94933da6
(I just removed the part where they modified test/remote_test.rb which
is run in Debian only for autopkgtest)
[ Reason ]
Migrating this new version would fix an FTBFS bug caused by those test
failures when the building environment has no access to the internet.
(*and* the internet must not be accessed during build!)
[ Impact ]
[ Tests ]
Five tests from the testsuite are thus now skipped during the build.
[ Risks ]
The code of the library itself has not changed. So risks are (close to)
zero.
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
unblock ruby-rugged/1.1.0+ds-4
diff -Nru ruby-rugged-1.1.0+ds/debian/changelog
ruby-rugged-1.1.0+ds/debian/changelog
--- ruby-rugged-1.1.0+ds/debian/changelog 2021-02-03 10:09:43.0
+0100
+++ ruby-rugged-1.1.0+ds/debian/changelog 2021-05-04 15:27:51.0
+0200
@@ -1,3 +1,12 @@
+ruby-rugged (1.1.0+ds-4) unstable; urgency=high
+
+ * Add patch to really prevent network access in tests (Closes: #987650)
+Thanks Olivier Tilloy for the initial
+patch, adapted here.
+ * Remove duplicate build-dependency on gem2deb
+
+ -- Cédric Boutillier Tue, 04 May 2021 15:27:51 +0200
+
ruby-rugged (1.1.0+ds-3) unstable; urgency=medium
* Enable remote tests only for autopkgtest (Closes: #980258)
diff -Nru ruby-rugged-1.1.0+ds/debian/control
ruby-rugged-1.1.0+ds/debian/control
--- ruby-rugged-1.1.0+ds/debian/control 2021-02-03 10:09:43.0 +0100
+++ ruby-rugged-1.1.0+ds/debian/control 2021-05-04 15:27:51.0 +0200
@@ -8,7 +8,6 @@
Build-Depends: debhelper-compat (= 13),
gem2deb (>= 1),
cmake,
- gem2deb (>= 1.0~),
git,
libgit2-dev (>= 1.1~),
libgit2-fixtures,
diff -Nru ruby-rugged-1.1.0+ds/debian/patches/series
ruby-rugged-1.1.0+ds/debian/patches/series
--- ruby-rugged-1.1.0+ds/debian/patches/series 2021-02-03 10:09:43.0
+0100
+++ ruby-rugged-1.1.0+ds/debian/patches/series 2021-05-04 15:27:51.0
+0200
@@ -3,3 +3,4 @@
dont-try-to-build-libgit2.patch
libgit2-fixtures-path.patch
disable-test-global-config.patch
+skip-network-tests.patch
diff -Nru ruby-rugged-1.1.0+ds/debian/patches/skip-network-tests.patch
ruby-rugged-1.1.0+ds/debian/patches/skip-network-tests.patch
--- ruby-rugged-1.1.0+ds/debian/patches/skip-network-tests.patch
1970-01-01 01:00:00.0 +0100
+++ ruby-rugged-1.1.0+ds/debian/patches/skip-network-tests.patch
2021-05-04 15:27:51.0 +0200
@@ -0,0 +1,53 @@
+Description: skip unit tests that require network access,
+ because Launchpad builders and autopkgtests run in a restricted environment.
+ (This is a trimmed version of Ubuntu patch, letting autopkgtests access the
+ Internet)
+Author: Olivier Tilloy
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987650
+Origin:
https://git.launchpad.net/~usd-import-team/ubuntu/+source/ruby-rugged/tree/debian/patches/ubuntu-skip-network-tests.patch?id=2f18d60418e71d96ef34c5627370752f94933da6
+Reviewed-By: Cédric Boutillier
+
+--- a/test/online/ls_test.rb
b/test/online/ls_test.rb
+@@ -7,6 +7,7 @@ class OnlineLsTest < Rugged::OnlineTestC
+
+ if Rugged.features.include?(:https)
+ def test_ls_over_https
++ skip "this test requires network access"
+ remote = @repo.remotes.create("origin",
"https://github.com/libgit2/TestGitRepository.git";)
+
+ assert_equal [
+--- a/test/online/fetch_test.rb
b/test/online/fetch_test.rb
+@@ -15,6 +15,7 @@ class OnlineFetchTest < Rugged::OnlineTe
+
+ if Rugged.features.include?(:https)
+ def test_fetch_over_https
++ skip "this test requires network access"
+ @repo.remotes.create("origin",
"https://github.com/libgit2/TestGitRepository.git";)
+
+ @repo.fetch("origin")
+@@ -30,6 +31,7 @@ class OnlineFetchTest < Rugged::OnlineTe
+ end
+
+ def test_fetch_over_https_with_certificate_callback
++ skip "this test requires network access"
+ @repo.remotes.create("origin",
"https://github.com/libgit2/TestGitRepository.git";)
+
+ args = {}
+@@ -46,6 +48,7 @@ class OnlineFetchTest < Rugged::OnlineTe
+ end
+
+ def test_fetch_over_https_with_certificate_callback_
Bug#972574: libgit2: merge request with a proposition
Source: libgit2 Followup-For: Bug #972574 Dear Maintainer, I've just created a merge request on salsa https://salsa.debian.org/debian/libgit2/-/merge_requests/3 with a proposition. This adds an extra libgit2-fixtures binary package, shipping the examples under tests/resources in /usr/share/doc/libgit2-fixtures/examples. Feel free to suggest another path if you think it is more appropriate. This allows me to run correctly the testsuite of ruby-rugged, once indicating the correct location of libgit2 fixtures directory. Best wishes, Cédric signature.asc Description: PGP signature
Bug#927076: any progress?
Hi, I was wondering if there was any progress in the process of getting xournalpp into Debian. I would be really happy to have it in the official archive. Oh, I see that your work, Barak, has been imported recently into the Debian group on salsa: https://salsa.debian.org/debian/xournalpp although the last commit is 4 months old. Are there any plans to upload it soon? Thanks in advance signature.asc Description: PGP signature
Bug#972574: libgit2: consider providing a binary package with libgit2 fixtures for test purposes
Source: libgit2 Version: 1.0.0+dfsg.1-2 Severity: wishlist Dear Maintainer, I am in the process of preparing ruby-rugged to work with the new libgit2 1.0 in experimental. The new upstream version of this package has new tests relying on the availability of the fixtures provided in the sourcetree of libgit2. I was wondering if you would consider providing a binary package with these fixtures in case other software relying on libgit2 would use them as part of their testsuite. Best regards, Cédric -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: PGP signature
Bug#967999: version 6.x has support for rails 6
The last upstream version 6.3.0 has support for Rails 6. I have imported the package in the Ruby team salsa group (it was missing for some reason), at the place expected from the Vcs fields. I upgraded roughly the package, and noticed (only?) two test failures (and no error), that I could not fix yet. Cheers Cédric
Bug#943617: help welcome
Dear Klaus-Michael, apologies for my late answer. If you are still interested in helping maintaining ruby-cmdparse, you are most welcome to join the ruby team. We are never lacking manpower to update the many packages maintained by the team. Write an email to debian-r...@lists.debian.org and create an account on the salsa.debian.org platform if you don't have one yet. You'll be included in the ruby group and can update the package from there, and have your package sponsored for an upload in the archive. Best wishes, Cédric signature.asc Description: PGP signature
Bug#969738: ruby-asciidoctor-pdf: relax version constraint on ruby-prawn (2.3.0 in experimental)
Source: ruby-asciidoctor-pdf Version: 1.5.3-1 Severity: important Dear Keith, I have just uploaded ruby-prawn 2.3.0-1~exp1 to experimental. The package ruby-asciidoctor-pdf does not accept versions of ruby-prawn higher than 2.2.x in debian control file and in the gemspec. Please relax this constraint and test against the package in experimental. I also saw that there is a comment in the gemspec about the fact that ttfunk 1.6 may cause problems with asciidoctor-pdf. Note that I already uploaded ttfunk 1.6 to unstable. Possible issues were unnoticed because of the lack of explicit dependency. I hope this is fixable, as prawn 2.3 require ttfunk 1.6. Best regards, Cédric
Bug#969736: ruby-asciidoctor-pdf: misleading Maintainer: field
Package: ruby-asciidoctor-pdf Severity: normal Dear Keith, The package ruby-asciidoctor-pdf indicates that the maintainer for this package is the Ruby team. However this package is not maintained in the Ruby group on salsa, but under your personal name space. This can create some confusion, e.g. in case of bug reports. Would you mind changing the maintainer field of the package to reflect that? You are also most welcome to move the repo to the ruby group, and maintain it from there, if you wish. Best regards, Cédric
Bug#966436: files
Here are the promised files Image: spec/fixtures/clipping_path.jpg Format: JPEG (Joint Photographic Experts Group JFIF format) Mime type: image/jpeg Class: DirectClass Geometry: 200x120+0+0 Resolution: 72x72 Print size: 2.8x1.7 Units: PixelsPerInch Colorspace: sRGB Type: Palette Base type: Undefined Endianess: Undefined Depth: 8-bit Channel depth: red: 8-bit green: 8-bit blue: 8-bit Channel statistics: Pixels: 24000 Red: min: 208 (0.815686) max: 208 (0.815686) mean: 208 (0.815686) standard deviation: 0 (0) kurtosis: 4.19021e+54 skewness: 0 entropy: 0 Green: min: 176 (0.690196) max: 176 (0.690196) mean: 176 (0.690196) standard deviation: 0 (0) kurtosis: -1.73261e+54 skewness: 0 entropy: 0 Blue: min: 177 (0.694118) max: 177 (0.694118) mean: 177 (0.694118) standard deviation: 0 (0) kurtosis: 1.47046e+54 skewness: -1.39375e+37 entropy: 0 Image statistics: Overall: min: 176 (0.690196) max: 208 (0.815686) mean: 187 (0.73) standard deviation: 0 (0) kurtosis: -1.50004 skewness: 0.70469 entropy: 0 Colors: 1 Histogram: 24000: (208,176,177) #D0B0B1 srgb(208,176,177) Rendering intent: Perceptual Gamma: 0.454545 Chromaticity: red primary: (0.64,0.33) green primary: (0.3,0.6) blue primary: (0.15,0.06) white point: (0.3127,0.329) Background color: white Border color: srgb(223,223,223) Matte color: grey74 Transparent color: black Interlace: None Intensity: Undefined Compose: Over Page geometry: 200x120+0+0 Dispose: Undefined Iterations: 0 Compression: JPEG Quality: 99 Orientation: TopLeft Properties: date:create: 2018-03-18T06:54:04+01:00 date:modify: 2018-03-18T06:54:04+01:00 exif:ColorSpace: 1 exif:DateTime: 2016:01:20 19:28:30 exif:ExifOffset: 172 exif:Orientation: 1 exif:PixelXDimension: 200 exif:PixelYDimension: 120 exif:ResolutionUnit: 2 exif:Software: Adobe Photoshop CC 2014 (Macintosh) exif:thumbnail:Compression: 6 exif:thumbnail:JPEGInterchangeFormat: 310 exif:thumbnail:JPEGInterchangeFormatLength: 814 exif:thumbnail:ResolutionUnit: 2 exif:thumbnail:XResolution: 72/1 exif:thumbnail:YResolution: 72/1 exif:XResolution: 72/1 exif:YResolution: 72/1 icc:copyright: Copyright (c) 1998 Hewlett-Packard Company icc:description: sRGB IEC61966-2.1 icc:manufacturer: IEC http://www.iec.ch icc:model: IEC 61966-2.1 Default RGB colour space - sRGB jpeg:colorspace: 2 jpeg:sampling-factor: 1x1,1x1,1x1 signature: 44f62c0b59893193d132f211e53e1d4fc8d92b27d5699d1ccdb340c97f9e6d12 Clipping path: http://www.w3.org/2000/svg"; width="200" height="120"> Profiles: Profile-8bim: 3720 bytes Profile-exif: 1130 bytes Profile-icc: 3144 bytes Profile-xmp: 4273 bytes Artifacts: filename: spec/fixtures/clipping_path.jpg verbose: true Tainted: False Filesize: 14616B Number pixels: 24000 Pixels per second: 2.4MB User time: 0.010u Elapsed time: 0:01.009 Version: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org Image: Filename: spec/fixtures/clipping_path.jpg Format: JPEG (Joint Photographic Experts Group JFIF format) Mime type: image/jpeg Class: DirectClass Geometry: 200x120+0+0 Resolution: 72x72 Print size: 2.8x1.7 Units: PixelsPerInch Colorspace: sRGB Type: Palette Base type: Undefined Endianness: Undefined Depth: 8-bit Channel depth: red: 8-bit green: 8-bit blue: 8-bit Channel statistics: Pixels: 24000 Red: min: 208 (0.815686) max: 208 (0.815686) mean: 208 (0.815686) standard deviation: 0 (0) kurtosis: 4.19021e+54 skewness: 0 entropy: 0 Green: min: 176 (0.690196) max: 176 (0.690196) mean: 176 (0.690196) standard deviation: 0 (0) kurtosis: -1.73261e+54 skewness: 0 entropy: 0 Blue: min: 177 (0.694118) max: 177 (0.694118) mean: 177 (0.694118) standard deviation: 0 (0) kurtosis: 1.47046e+54 skewness: -1.39375e+37 entropy: 0 Image statistics: Overall: min: 176 (0.690196) max: 208 (0.815686) mean: 187 (0.73) standard deviation: 0 (0) kurtosis: -1.50004 skewness: 0.70469 entropy: 0 Colors: 1 Histogram: 24000: (208,176,177) #D0B0B1 srgb(208,176,177) Rendering intent: Perceptual Gamma: 0.454545 Chromaticity: red primary: (0.64,0.33) green primary: (0.3,0.6) blue primary: (0.15,0.06) white point: (0.3127,0.329) Background color: white Border color: srgb(223,223,223) Matte color: grey74 Transparent color: black Interlace: None Intensity: Undefined Compose: Over Page geometry: 200x120+0+0 Di
Bug#966436: reassign to imagemagick 8:6.9.11.24+dfsg-1
reassign 966436 src:imagemagick found 966436 8:6.9.11.24+dfsg-1n retitle scrambled property in identify -verbose output affects 966436 ruby-mini-magick thanks ruby-mini-magick relies (too) heavily on a parsing of output of imagemagick tools like identify. The issue discussed here is caused by a change in the output of the `identify -verbose` command from the version in testing (8:6.9.10.23+dfsg-2.1+b2) and unstable (8:6.9.11.24+dfsg-1). Attached are the corresponding outputs of the above command on the file from ruby-mini-magick specs (spec/fixtures/clipping_path.jpg). In the "unstable" version, the field Properties: has first subfield (on line 96) with a strange name, which makes regexp filtering from ruby-mini-magick choke. The content seems to be the same as the "Clipping path:" field. This subfield does not appear in the version of testing. It is mentionned as a warning on newer versions of ruby-mini-magick that the `details` method reading the output of `identify -verbose` in a specific way, has become unreliable for newer versions of ImageMagick. I am therefore disabling the corresping test in that code. However, I believe that the output of identify -verbose should not contain such cryptic field names, therefore, I am reassigning the but to imagemagick package. Thanks, Cédric signature.asc Description: PGP signature
Bug#955429: possiblity of using a different download agent like wget in bad internet connections
Hi, Here is a log attached. The client has private IP 192.168.0.106 behind an ADSL "box" with public IP 82.65.29.121 The package with a missed download was actually this time apt-cacher-ng: E: Impossible de récupérer http://deb.debian.org/debian/pool/main/a/apt-cacher-ng/apt-cacher-ng_3.5-1_amd64.deb Somme de contrôle de hachage incohérente Hashes of expected file: - SHA256:5bf309906ebfb202e2d91abd6bb952f42e38326c6a12fdc9326936dbf0b974b9 - MD5Sum:7407fe84c3f123b76a5daebd9bb71925 [weak] - Filesize:562512 [weak] Hashes of received file: - SHA256:f7284dd1761a74cd592496c8c3451721b14894c03fed22b9fd499924a1ea7dfb - MD5Sum:d1df236d3c207c51d32c26da401a10e5 [weak] - Filesize:562512 [weak] Last modification reported: Mon, 20 Apr 2020 22:42:49 + Thanks for investigating. Cheers, Cédric apt-cacher.err.gz Description: application/gzip signature.asc Description: PGP signature
Bug#956280: shapelib: change in ronn 0.9.0 breaks generation of manpages
On Sat, Apr 11, 2020 at 06:20:13AM +0200, Sebastiaan Couwenberg wrote: > > pycsw required the same changes. Those are also ready in git. Ah... I was wondering why it was not listed by build-rdepends script (without parameters), but it is probably because it is in non-free. > You don't have to wait for me, just bump the severity of this issue to > serious when you move it to unstable. Ok. I went ahead, and uploaded to unstable. Raising bug severity. Cheers, Cédric signature.asc Description: PGP signature
Bug#956280: shapelib: change in ronn 0.9.0 breaks generation of manpages
Dear Sebastiaan, On Thu, Apr 09, 2020 at 12:20:52PM +0200, Sebastiaan Couwenberg wrote: > > Hopefully that (new) behavior will stay, this is not the first time an > update of ruby-ronn required changes. I think (or at least hope too) that it is here to stay. > When do you plan to move it to unstable? Given that shapelib is the only reverse build-dependency failing because of this change, we can move to unstable when shapelib is ready to. What about in 7 days from now? Tell me what suits best for you. Cheers, Cédric signature.asc Description: PGP signature
Bug#955429: possiblity of using a different download agent like wget in bad internet connections
Hi, On Thu, Apr 09, 2020 at 09:43:02PM +0530, Pirate Praveen wrote: > boutil and terceiro also reported same problem yesterday in #debian-ruby irc > (copying them). So I think the issue is not specific to me. > > boutil: hi! do you experience many "Hash Sum mismatch" when doing upgrades > with apt-cache-ng? I indeed experience this often on my laptop (uptodate sid). On wifi, about every second `apt update` fails with such a mismatch, either when updating my system, or building a package with sbuild. Ethernet connection is a bit better, but still it happens. I have a not so fast ADSL line. I just got 5 times in a row this: [...] Err:19 http://ftp.fr.debian.org/debian testing/main DEP-11 64x64 Icons Hash Sum mismatch Hashes of expected file: - Filesize:7050569 [weak] - SHA256:802728a6bcbe5201c8cafa40286b9b10c8942beefe2922725056bfc706f86753 - MD5Sum:570e3cdb335fed69c669af1610093c7b [weak] Hashes of received file: - SHA256:43b59d8c2ef9ac42b56f38108557a5e9b35a793a96a4268d6004a0d5e10865f9 - MD5Sum:46fcee066fb69d7934cbbdf8d941273a [weak] - Filesize:7050569 [weak] Last modification reported: Fri, 10 Apr 2020 08:17:35 + Release file created at: Fri, 10 Apr 2020 15:23:29 + [...] My desktop station at work doesn't seem to show this behavior. It is connected to a fast ethernet cable and fast internet connection. Cheers, Cédric signature.asc Description: PGP signature
Bug#956280: shapelib: change in ronn 0.9.0 breaks generation of manpages
Source: shapelib Version: 1.5.0-1 Severity: important Dear Maintainer, I uploaded ruby-ronn 0.9.0 in experimental. This version contains a change that strips all extensions (not just .ronn) from processed files to produce the name of the man page. It seems that the loop present in debian/rules to rename the man pages from .md.1 to .1 extension fails if there is no debian/man/*.md.1 file. When ruby-ronn 0.9.0 will go in unstable, removing this loop will be enough, but as is, the loop does not behave well if debian/man/*.md.1 is empty. Best regards, Cédric -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: PGP signature
Bug#953198: ronn 0.9.0 uploaded to experimental
Hi! Thank you for your work. I am uploading right now your version with some additional commits to experimental, as some reverse build-dependencies (in particular shapelib) are failing to build with this new version. Looking forward to your next contribution to the Ruby team Best wishes, Cédric signature.asc Description: PGP signature
Bug#943191: nanoc: Python2 removal in sid/bullseye
Hi Sandro, Thanks for the heads-up, and sorry for the delay. I am uploading your fix now, in 4.11.0-5. Cheers, Cédric signature.asc Description: PGP signature
Bug#950901: ruby-fakefs: missing ruby2.7 support
Package: ruby-fakefs Version: 0.20.1-1 Severity: important Tags: upstream Control: forwarded -1 https://github.com/fakefs/fakefs/issues/437 Dear Maintainer, This library still does not support ruby2.7. More investigation is needed.
Bug#949392: RM: ruby-notifier -- ROM; dead upstream, RC buggy, no reverse dependencies
Package: ftp.debian.org Severity: normal Hi, We would like to request the removal of ruby-notifier package, which is has had no activity upstream activity for four years, has a RC bug #896175, low popcon, no reverse (build-) dependencies. THanks in advance. Cédric, for the ruby team
Bug#941618: torus-trooper: fails to start with "undefined symbol" error
Package: torus-trooper Version: 0.22.dfsg1-12 Severity: important Dear Maintainer, I've just installed the game and tried to launch it from the terminal: I got the following error message: torus-trooper: symbol lookup error: torus-trooper: undefined symbol: _D4core4stdc5errno5errnoFNbNdNiNeZ Rebuilding in sbuild fixed the issue for me. Does it mean that the package needs a binNMU? Cheers -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages torus-trooper depends on: ii libbulletml0v5 0.0.6-7 ii libc6 2.29-2 ii libgcc1 1:9.2.1-8 ii libgl1 1.1.0-1+b1 ii libglu1-mesa [libglu1] 9.0.0-2.1+b3 ii libgphobos769.2.1-8 ii libsdl-mixer1.2 1.2.12-16 ii libsdl1.2debian 1.2.15+dfsg2-5 ii torus-trooper-data 0.22.dfsg1-12 torus-trooper recommends no packages. torus-trooper suggests no packages. -- no debconf information
Bug#919877: fixed by 1.7.1-3 upload
Control: fixed -1 ruby-sprite-factory/1.7.1-3 Hi, This failing test is skipped by a patch since 1.7.1-3. The package now builds fine. I am therefore closing this bug. Cheers, Cédric
Bug#939437: ruby-glib2: missing dependency on ruby-pkg-config >=1.3.5
Package: ruby-glib2 Version: 3.3.7-1 Severity: important Dear Maintainer, the glib2 gemspec indicates that it should depend on ruby-pkg-config. However this package does not appear in the dependency list. gem dependency check will thus fail for every package depending on ruby-glib2. Please add the dependency or remove it from gemspec depending on what is the best approach. Best wishes, Cédric -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ruby-glib2 depends on: ii libc6 2.28-10 ii libglib2.0-0 2.60.6-2 ii libruby2.52.5.5-4 ii ruby 1:2.5.1 ruby-glib2 recommends no packages. ruby-glib2 suggests no packages. -- no debconf information
Bug#925397: unblock: nanoc/4.11.0-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package nanoc Version 4.11.0-3 currently in unstable fixes RC bug #924845: the package now does not build-depend on ruby-fog (which has been removed from the archive), but only on ruby-fog-local (and suggests ruby-fog-core). Please find in attachment the debdiff between the source package 4.11.0-2 currently in testing. unblock nanoc/4.11.0-3 -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru nanoc-4.11.0/debian/changelog nanoc-4.11.0/debian/changelog --- nanoc-4.11.0/debian/changelog 2019-01-06 22:10:41.0 +0100 +++ nanoc-4.11.0/debian/changelog 2019-03-23 00:18:11.0 +0100 @@ -1,3 +1,10 @@ +nanoc (4.11.0-3) unstable; urgency=medium + + * Change (build-)dependencies from ruby-fog (removed from the archive) to +ruby-fog-local (Closes: #924845) + + -- Cédric Boutillier Sat, 23 Mar 2019 00:18:11 +0100 + nanoc (4.11.0-2) unstable; urgency=medium * Tighten ruby-hamster and ruby-ref dependency relation from Recommends to diff -Nru nanoc-4.11.0/debian/control nanoc-4.11.0/debian/control --- nanoc-4.11.0/debian/control 2019-01-06 22:10:41.0 +0100 +++ nanoc-4.11.0/debian/control 2019-03-23 00:18:11.0 +0100 @@ -26,7 +26,7 @@ ruby-ddplugin, ruby-erubi, ruby-erubis, - ruby-fog (>= 0.13.0~), + ruby-fog-local, ruby-fuubar, ruby-haml, ruby-hamster, @@ -110,7 +110,7 @@ Suggests: coderay | ruby-pygments.rb | python3-pygments | highlight, git, rsync, - ruby-fog (>= 0.13.0~), + ruby-fog-core (>= 0.13.0~), ruby-rack Description: static site generator written in Ruby Nanoc is a static site generator, fit for building anything from a small signature.asc Description: PGP signature
Bug#919048: fixed in unstable : should postpone autoremoval from testing
Hi, This bug has been fixed with 1.0.0-1. ruby-haml-rails is flagged for autoremoval in 19 hours. Hoping that writing to this bug will postpone the autoremoval to let the package from unstable migrate to testing in time. Cédric
Bug#907438: fixed in 1.0.0-2
Control: fixed -1 ruby-toml-rb/1.0.0-2 Hi, thanks for your report. this bug has been fixed with the 1.0.0-2, when the file init.rb from source was installed in the binary package. I am therefore closing this bug. Cheers, Cédric
Bug#888130: set severity to normal as 2.9.4-2 skips this test
Control: tag -1 -ftbfs Control: severity -1 normal Control: tag -1 experimental Hi, This bug does not affect experimental, as the 3.x branch removed this test (and the corresponding code). The reuse functionality has been reported upstream to cause problems in some situations in the 2.x branch. I am therefore skipping the corresponding test in 2.9.4-2, and decrease the severity to normal for now, since the possible problem does not affect the building process. Cheers, Cédric signature.asc Description: PGP signature
Bug#912249: not ftbfs anymore since 1.2.0-1 (test disable)
Control: tag -1 -ftbfs Control: retitle -1 test_tail_change2(FileTailTest) fails Control: severity -1 normal Hi, This test is now disabled in the test suite (build and autopkgtest). I am therefore downgrading the severity of the bug and removing the ftbfs tag, but leave the bug open, waiting for a true fix. Cheers, Cédric signature.asc Description: PGP signature
Bug#919720: RM: ruby-albino -- ROM; dead upstream, obsolete
Package: ftp.debian.org Severity: normal Dear FTP masters, please remove ruby-albino from the archive. It has problems due to transition of pygmentize to python3, dead upstream for many years and obsolete. No reverse (build)dependencies. Thanks in advance! Cheers, Cédric
Bug#919653: python-pygments: pygmentize and its manpage in different binary packages
Package: python-pygments Version: 2.3.1+dfsg-1 Severity: normal Tags: a11y Dear Maintainer, I've noticed that even though the script pygmentize has been moved to python3-pygments, its manpage is still shipped within the python-pygments binary package (no man page in the python3-pygments). Cheers, Cédric -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python-pygments depends on: ii python 2.7.15-3 Versions of packages python-pygments recommends: ii python-chardet3.0.4-2 ii python-pkg-resources 40.6.2-1 Versions of packages python-pygments suggests: pn python-pygments-doc ii ttf-bitstream-vera 1.10-8 -- no debconf information
Bug#918236: transient bug in ruby-prawn
Control: tag -1 notfound ruby-prawn-svg/0.28.0-2 This was caused during the transition to ruby-prawn 2.2.0 during which a mismatch for version of ruby-ttfunk occurred. This is now solved, and has no root in this package. Closing. Cheers, Cédric signature.asc Description: PGP signature
Bug#918235: transient bug in ruby-prawn
Control: tag -1 notfound ruby-prawn-icon/2.3.0-2 This was caused during the transition to ruby-prawn 2.2.0 during which a mismatch for version of ruby-ttfunk occurred. This is now solved, and has no root in this package. Closing. Cheers, Cédric signature.asc Description: PGP signature
Bug#918605: fixed with 3.8.1-2 upload
Control: tag -1 fixed ryby-rspec-rails/3.8.1-2 Hi, This has been fixed with the upload of ruby-rspec-rails/3.8.1-2 in unstable. Cheers, Cédric signature.asc Description: PGP signature
Bug#918234: ruby-asciidoctor-pdf: FTBFS in sid
Package: ruby-asciidoctor-pdf Followup-For: Bug #918234 The log in the report corresponds to a transient bug during the update of ruby- prawn (earlier version depended on earlier version of ruby-ttfunk). So this part is gone. But the dependency check still fails now because of version mismatch of ruby-treetop: the gemspec file wants version 1.5.3 whereas the archive has 1.6.8 The solution is to patch further the gemspec file to relax strict dependency on this version of treetop. diff --git a/debian/patches/0001-Fix-dependencies-for-debian-build.patch b/debian/patches/0001-Fix-dependencies-for-debian-build.patch index 05748d1..589b7f4 100644 --- a/debian/patches/0001-Fix-dependencies-for-debian-build.patch +++ b/debian/patches/0001-Fix-dependencies-for-debian-build.patch @@ -14,11 +14,9 @@ Signed-off-by: Keith Packard lib/asciidoctor-pdf/prawn-templates_ext.rb | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) -diff --git a/asciidoctor-pdf.gemspec b/asciidoctor-pdf.gemspec -index 940bc9f..59b23c9 100644 --- a/asciidoctor-pdf.gemspec +++ b/asciidoctor-pdf.gemspec -@@ -43,10 +43,10 @@ An extension for Asciidoctor that converts AsciiDoc documents to PDF using the P +@@ -43,13 +43,13 @@ s.add_runtime_dependency 'prawn', '>= 1.3.0', '< 2.3.0' s.add_runtime_dependency 'prawn-table', '0.2.2' # prawn-templates >= 0.0.5 requires prawn >= 2.2.0, so we must cast a wider net to support Ruby 1.9.3 @@ -32,11 +30,13 @@ index 940bc9f..59b23c9 100644 s.add_runtime_dependency 'safe_yaml', '~> 1.0.4' s.add_runtime_dependency 'thread_safe', '~> 0.3.6' s.add_runtime_dependency 'concurrent-ruby', '~> 1.0.5' -diff --git a/lib/asciidoctor-pdf/prawn-templates_ext.rb b/lib/asciidoctor- pdf/prawn-templates_ext.rb -index fca8178..92fe260 100644 + # For our usage, treetop 1.6.2 is slower than 1.5.3 +- s.add_runtime_dependency 'treetop', '1.5.3' ++ s.add_runtime_dependency 'treetop', '>= 1.5.3' + end --- a/lib/asciidoctor-pdf/prawn-templates_ext.rb +++ b/lib/asciidoctor-pdf/prawn-templates_ext.rb -@@ -2,4 +2,4 @@ class Prawn::Document +@@ -2,4 +2,4 @@ # NOTE allows prawn-templates 0.0.4 to be used with prawn >= 2.2.0 const_set :VALID_OPTIONS, (send :remove_const, :VALID_OPTIONS).dup if VALID_OPTIONS.frozen? end -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ruby-asciidoctor-pdf depends on: ii ruby 1:2.5.1 ii ruby-asciidoctor 1.5.8-1 ii ruby-concurrent 1.0.5-2 ii ruby-prawn2.2.0+dfsg-1 ii ruby-prawn-icon 2.3.0-2 ii ruby-prawn-svg0.28.0-2 ii ruby-prawn-table 0.2.2-1 ii ruby-safe-yaml1.0.4-2 ii ruby-thread-safe 0.3.6-1 ii ruby-treetop 1.6.8-1 ruby-asciidoctor-pdf recommends no packages. ruby-asciidoctor-pdf suggests no packages. diff --git a/debian/patches/0001-Fix-dependencies-for-debian-build.patch b/debian/patches/0001-Fix-dependencies-for-debian-build.patch index 05748d1..589b7f4 100644 --- a/debian/patches/0001-Fix-dependencies-for-debian-build.patch +++ b/debian/patches/0001-Fix-dependencies-for-debian-build.patch @@ -14,11 +14,9 @@ Signed-off-by: Keith Packard lib/asciidoctor-pdf/prawn-templates_ext.rb | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) -diff --git a/asciidoctor-pdf.gemspec b/asciidoctor-pdf.gemspec -index 940bc9f..59b23c9 100644 --- a/asciidoctor-pdf.gemspec +++ b/asciidoctor-pdf.gemspec -@@ -43,10 +43,10 @@ An extension for Asciidoctor that converts AsciiDoc documents to PDF using the P +@@ -43,13 +43,13 @@ s.add_runtime_dependency 'prawn', '>= 1.3.0', '< 2.3.0' s.add_runtime_dependency 'prawn-table', '0.2.2' # prawn-templates >= 0.0.5 requires prawn >= 2.2.0, so we must cast a wider net to support Ruby 1.9.3 @@ -32,11 +30,13 @@ index 940bc9f..59b23c9 100644 s.add_runtime_dependency 'safe_yaml', '~> 1.0.4' s.add_runtime_dependency 'thread_safe', '~> 0.3.6' s.add_runtime_dependency 'concurrent-ruby', '~> 1.0.5' -diff --git a/lib/asciidoctor-pdf/prawn-templates_ext.rb b/lib/asciidoctor-pdf/prawn-templates_ext.rb -index fca8178..92fe260 100644 + # For our usage, treetop 1.6.2 is slower than 1.5.3 +- s.add_runtime_dependency 'treetop', '1.5.3' ++ s.add_runtime_dependency 'treetop', '>= 1.5.3' + end --- a/lib/asciidoctor-pdf/prawn-templates_ext.rb +++ b/lib/asciidoctor-pdf/prawn-templates_ext.rb -@@ -2,4 +2,4 @@ class Prawn::Document +@@ -2,4 +2,4 @@ # NOTE allows prawn-templates 0.0.4 to be used with prawn >= 2.2.0 const_set :VALID_OPTIONS, (send :remove_const, :VALID_OPTIONS).dup if VALID_OPTIONS.frozen? end
Bug#914546: failing test skipped in 3.7.1-2; decreasing bug severity
Control: severity -1 normal Control: tag -1 - ftbfs Hi, The bug has been reported upstream, and while waiting for a fix, the failing test is skipped in 3.7.1-2, so that this won't cause a ftbs. The bug is kept open, but severity is lowered to normal. Thanks, Cédric signature.asc Description: PGP signature
Bug#905648: skipping all tests, non-critical
Control: severity -1 normal As per upstream's advice, https://github.com/grosser/parallel/issues/227 tests are now skipped entirely (except naive library loading) since 1.12.1-2. The test failures are still present, but are not critical anymore because they don't lead to build failure. I am therefore lowering the severity Cedric signature.asc Description: PGP signature
Bug#913404: builds but tests fail
Control: forwarded -1 https://github.com/taf2/curb/issues/369 The library builds with the following commit from upstream https://github.com/taf2/curb/commit/aa23bf67b0290882514385ad25659d4511c882d2 however, several test failures appear: https://github.com/taf2/curb/issues/369 signature.asc Description: PGP signature
Bug#908258: ruby-sentry-raven: FTBFS with ruby-rspec 3.8
Source: ruby-sentry-raven Version: 2.7.2-2 Severity: serious Justification: ftbfs Dear Maintainer, The package fails to build from source after the upload of ruby-rspec 3.8 (was fine with 3.7), because of a failing test: Failures: 1) Integration tests hitting quota limit shouldn't swallow exception Failure/Error: expect(@logger).not_to receive(:error).twice RuntimeError: `count` is not supported with negative message expectations # ./spec/raven/integration_spec.rb:38:in `block (2 levels) in ' Finished in 1.01 seconds (files took 0.73133 seconds to load) 256 examples, 1 failure, 2 pending Failed examples: rspec ./spec/raven/integration_spec.rb:34 # Integration tests hitting quota limit shouldn't swallow exception This failure is also experienced upstream, as Jenkins instance reports the same test failure with rspec 3.8 gem from Github repository. Cheers, Cédric -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#895411: (no subject)
This is in fact explicitly stated in the changelog entry for anki/2.1.0+dfsg~b37-2.
Bug#888949: libconfig-model-dpkg-perl: recognize X{S,B}-Ruby-Versions field for packages depending on ruby, not only ruby section
Sure, thanks!
Bug#888949: libconfig-model-dpkg-perl: recognize X{S,B}-Ruby-Versions field for packages depending on ruby, not only ruby section
> How about basing this decision on the Maintainer field ? (which would > probably > be more reliable than basing the decision on the presence of a dependency) The XS-Ruby-Version is used (only?) by dh_ruby provided by the gem2deb package. I think this behaviour would be useful also for packages not maintained by the Ruby team, and they have a higher probability to not be in the ruby section. So I think "build-depend on gem2deb" would be the best criterion. Now a decision based on the Maintainer field would possibly cover more than 95% of the cases already, with (almost?) no false positive. Cheers, Cédric signature.asc Description: PGP signature
Bug#868314: not the same problem
Hi Federico, Thank you for your additional comment on this bug. I don't think it is the same problem as in the original report. The error you see in irb comes from the fact that you run your session in a directory which doesn't contain a Gemfile to describe the dependencies of your project. In particular it is not the same error as the one in the initial bug report, where I suppose that a Gemfile was present with dependencies not corresponding to installed packages/gems. If you want to start jekyll, invoking bundler is not needed. You should be able to start a new site by just typing: $ jekyll new foo in the terminal. Can you confirm that you can start a new site, or can you be more specific in what you were expecting from the Bundler.setup command? Best wishes, Cédric signature.asc Description: PGP signature
Bug#891125: vim-latexsuite: please package new version 1.10
Package: vim-latexsuite Version: 1:1.9.0-1 Severity: wishlist Hi, Could you please package the version 1.10, released earlier this year? I am particularly interested in the new IUNMAP function which helps deactivate selectively some bindings. This could certainly help with #499004. Thanks in advance. Best wishes, Cédric
Bug#890860: stretch-pu: package ruby-redis-store/1.1.6-1
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Hi,
I have prepared a patch for Debian bug #882034 (CVE-2017-1000248) from
by adapting the upstream patch from
https://github.com/redis-store/redis-store/pull/290
(which should be applied after
https://github.com/redis-store/redis-store/commit/bcd1c28cf10ff18b4352cdacbe04113af3fec68d,
not present in the version 1.1.6)
Please find attached the debdiff for the version in Stretch.
It is the same as the change for 1.1.6-2 which went to unstable (without
the additional packaging change).
It was proposed by the security team to fx it with a Stretch update
instead of a security upload.
Thanks
Cédric
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/debian/changelog b/debian/changelog
index d28f11f..83455a6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+ruby-redis-store (1.1.6-1+deb9u1) stretch; urgency=high
+
+ * Team upload
+ * Add upstream patch to fix CVE-2017-1000248, allowing unsafe objects to be
+loaded from redis (Closes: #882034)
+
+ -- Cédric Boutillier Fri, 01 Dec 2017 17:22:29 +0100
+
ruby-redis-store (1.1.6-1) unstable; urgency=medium
* Upstream update
diff --git a/debian/patches/CVE-2017-1000248.patch
b/debian/patches/CVE-2017-1000248.patch
new file mode 100644
index 000..44c91de
--- /dev/null
+++ b/debian/patches/CVE-2017-1000248.patch
@@ -0,0 +1,551 @@
+Description: Replace marshalling with pluggable serializers
+Author: Tom Scott
+Bug: https://github.com/redis-store/redis-store/issues/289
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882034
+Applied-Upstream:
https://github.com/redis-store/redis-store/commit/e0c1398d54a9661c8c70267c3a925ba6b192142e
+Origin: upstream
+Last-Update: Tue, 15 Aug 2017 11:07:07 -0400
+
+This is in response to a vulnerability warning we received on Friday,
+August 11th, 2017. While most users will not be affected by this
+change, we recommend that developers of new applications use a different
+serializer other than `Marshal`. This, along with the removal of the
+`:marshalling` option, will enforce "sane defaults" in terms of securely
+serializing/de-serializing data.
+
+- Add `:serializer` option and deprecate `:marshalling`. Although you
+ will still be able to enable/disable serialization with Marshal using
+ `:marshalling` in the 1.x series, this will be removed by 2.0.
+
+- Rename `Redis::Store::Marshalling` to `Redis::Store::Serialization` to
+ reflect its new purpose.
+
+Fixes #289
+---
+ lib/redis-store.rb | 12 ---
+ lib/redis/store.rb | 28 +--
+ lib/redis/store/factory.rb | 9 -
+ lib/redis/store/namespace.rb | 4 +--
+ .../store/{marshalling.rb => serialization.rb} | 6 ++--
+ test/redis/store/factory_test.rb | 40 --
+ test/redis/store/namespace_test.rb | 4 +--
+ .../{marshalling_test.rb => serialization_test.rb} | 4 +--
+ 8 files changed, 80 insertions(+), 27 deletions(-)
+ rename lib/redis/store/{marshalling.rb => serialization.rb} (90%)
+ rename test/redis/store/{marshalling_test.rb => serialization_test.rb} (98%)
+
+--- a/lib/redis-store.rb
b/lib/redis-store.rb
+@@ -1,12 +1 @@
+-require 'redis'
+ require 'redis/store'
+-require 'redis/store/factory'
+-require 'redis/distributed_store'
+-require 'redis/store/namespace'
+-require 'redis/store/marshalling'
+-require 'redis/store/version'
+-
+-class Redis
+- class Store < self
+- end
+-end
+--- a/lib/redis/store.rb
b/lib/redis/store.rb
+@@ -1,3 +1,9 @@
++require 'redis'
++require 'redis/store/factory'
++require 'redis/distributed_store'
++require 'redis/store/namespace'
++require 'redis/store/serialization'
++require 'redis/store/version'
+ require 'redis/store/ttl'
+ require 'redis/store/interface'
+
+@@ -7,6 +13,24 @@
+
+ def initialize(options = { })
+ super
++
++ unless options[:marshalling].nil?
++puts %(
++ DEPRECATED: You are passing the :marshalling option, which has been
++ replaced with `serializer: Marshal` to support pluggable
serialization
++ backends. To disable serialization (much like disabling
marshalling),
++ pass `serializ
Bug#890257: ruby-grape: FTBFS with ruby2.3 and ruby-rack-test 0.7
Source: ruby-grape Version: 0.16.2-2 Severity: serious Justification: fails to build from source Dear Maintainer, The version 0.16.2-2 fails to build with ruby2.3. According to ci.debian.net, this has been happening since Sept, 7 2018 https://ci.debian.net/data/autopkgtest/unstable/amd64/r/ruby-grape/20170907_031907/log.gz This coincides with the transition to ruby-activesupport 2:4.2.9-3 which itself induced the transition from ruby-rack-test 0.6.3 to 0.7. Using ruby-rack-test 0.6.3 from stretch makes the tests pass with ruby2.3 (they fail with ruby2.5, but it is another problem). Cheers, Cédric -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information
Bug#888949: libconfig-model-dpkg-perl: recognize X{S,B}-Ruby-Versions field for packages depending on ruby, not only ruby section
Package: libconfig-model-dpkg-perl
Version: 2.105
Severity: minor
Dear Maintainer,
For a few years now, cme recognizes the X{S,B}-Ruby-Versions fields in
debian/control for packages of the ruby section.
Thanks a lot for that.
The spectrum of ruby packages in Debian became wider some of the
packages, though they use gem2deb and make use of these variables, are
not in the ruby section of the archive. Such an example is nanoc, a
static website generator (and thus in the web section).
Running cme fix dpkg-control on nanoc results in a no-op since the
variable XS-Ruby-Versions is not recognized.
Could you please widen the criteria for packages for which these fields are
recognized?
(like those depending on ruby or rather build-depending on gem2deb?)
Thank you in advance.
Cédric
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libconfig-model-dpkg-perl depends on:
ii libapt-pkg-perl 0.1.33
ii libarray-intspan-perl2.003-1
ii libconfig-model-perl 2.116-1
ii libexporter-lite-perl0.08-1
ii liblog-log4perl-perl 1.49-1
ii libmouse-perl2.5.1-1
ii libparse-recdescent-perl 1.967015+dfsg-1
ii libsoftware-license-perl 0.103012-1
ii libtext-autoformat-perl 1.74-2
ii libtext-levenshtein-damerau-perl 0.41-1
ii liburi-perl 1.73-1
ii libwww-perl 6.31-1
ii libyaml-perl 1.24-1
ii licensecheck 3.0.31-2
ii lintian 2.5.72
ii perl 5.26.1-4
ii perl-modules-5.26 [libmodule-corelist-perl] 5.26.1-4
Versions of packages libconfig-model-dpkg-perl recommends:
ii libconfig-model-tkui-perl 1.365-1
libconfig-model-dpkg-perl suggests no packages.
-- no debconf information
Bug#868314: [DRE-maint] Bug#868314: jekyll: Could not find public_suffix-2.0.5 in any of the sources
Control: tag -1 moreinfo Hi Lucas, I can't reproduce this issue on my system. As I understand from the code, this could arise if the site you want to build with jekyll contains a Gemfile. Then Bundler is set up, and the error seems to be related to dependency problems of your gems. Is this occuring if you invoke require "bundler" Bundler.setup from an irb session? >From the rubygems website, I think the only reverse dependency on public_suffix is addressable in Debian. https://rubygems.org/gems/public_suffix/reverse_dependencies Otherwise, could you provide a minimal example exhibiting the issue? Thanks Cedric
Bug#882034: ruby-redis-store for jessie and stretch (#882034 CVE-2017-1000248). Proposed patch
Hi, On Fri, Dec 08, 2017 at 09:31:47AM +0100, Salvatore Bonaccorso wrote: > Hi Cédric, > Thanks a lot for fixing this in unstable and experimental, so we have > quarantee that it's fixed in next stable. For stretch: Can you fix the > issue via a point release? Sure. It is too late for the one coming this weekend, but I'll ask inclusion for the next Stretch update. > What do you mean by the version in jessie? AFAICT the package was not > renamed, and ruby-redis-store is not present in jessie, do I miss > something? Oops, sorry. Indeed there is no version of ruby-redis-store. I got confused with another package. Thanks! Cédric signature.asc Description: PGP signature
Bug#882034: ruby-redis-store for jessie and stretch (#882034 CVE-2017-1000248). Proposed patch
Hi,
I have prepared a patch for Debian bug #882034 (CVE-2017-1000248) from
by adapting the upstream patch from
https://github.com/redis-store/redis-store/pull/290
(which should be applied after
https://github.com/redis-store/redis-store/commit/bcd1c28cf10ff18b4352cdacbe04113af3fec68d,
not present in the version 1.1.6)
Please find attached the debdiff for the version in Stretch.
It is the same as the change for 1.1.6-2 which went to unstable (without
the additional packaging change).
As jessie has the same version, the debdiff will look the same except
the one line in the changelog with version number and suite.
Do you ack this patch, and allow me to upload to security.debian.org?
Thanks
Cédric
diff -Nru ruby-redis-store-1.1.6/debian/changelog
ruby-redis-store-1.1.6/debian/changelog
--- ruby-redis-store-1.1.6/debian/changelog 2015-07-28 13:52:12.0
+0200
+++ ruby-redis-store-1.1.6/debian/changelog 2017-12-01 17:22:29.0
+0100
@@ -1,3 +1,11 @@
+ruby-redis-store (1.1.6-1+deb9u1) stretch-security; urgency=high
+
+ * Team upload
+ * Add upstream patch to fix CVE-2017-1000248, allowing unsafe objects to be
+loaded from redis (Closes: #882034)
+
+ -- Cédric Boutillier Fri, 01 Dec 2017 17:22:29 +0100
+
ruby-redis-store (1.1.6-1) unstable; urgency=medium
* Upstream update
diff -Nru ruby-redis-store-1.1.6/debian/patches/CVE-2017-1000248.patch
ruby-redis-store-1.1.6/debian/patches/CVE-2017-1000248.patch
--- ruby-redis-store-1.1.6/debian/patches/CVE-2017-1000248.patch
1970-01-01 01:00:00.0 +0100
+++ ruby-redis-store-1.1.6/debian/patches/CVE-2017-1000248.patch
2017-12-01 17:21:20.0 +0100
@@ -0,0 +1,551 @@
+Description: Replace marshalling with pluggable serializers
+Author: Tom Scott
+Bug: https://github.com/redis-store/redis-store/issues/289
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882034
+Applied-Upstream:
https://github.com/redis-store/redis-store/commit/e0c1398d54a9661c8c70267c3a925ba6b192142e
+Origin: upstream
+Last-Update: Tue, 15 Aug 2017 11:07:07 -0400
+
+This is in response to a vulnerability warning we received on Friday,
+August 11th, 2017. While most users will not be affected by this
+change, we recommend that developers of new applications use a different
+serializer other than `Marshal`. This, along with the removal of the
+`:marshalling` option, will enforce "sane defaults" in terms of securely
+serializing/de-serializing data.
+
+- Add `:serializer` option and deprecate `:marshalling`. Although you
+ will still be able to enable/disable serialization with Marshal using
+ `:marshalling` in the 1.x series, this will be removed by 2.0.
+
+- Rename `Redis::Store::Marshalling` to `Redis::Store::Serialization` to
+ reflect its new purpose.
+
+Fixes #289
+---
+ lib/redis-store.rb | 12 ---
+ lib/redis/store.rb | 28 +--
+ lib/redis/store/factory.rb | 9 -
+ lib/redis/store/namespace.rb | 4 +--
+ .../store/{marshalling.rb => serialization.rb} | 6 ++--
+ test/redis/store/factory_test.rb | 40 --
+ test/redis/store/namespace_test.rb | 4 +--
+ .../{marshalling_test.rb => serialization_test.rb} | 4 +--
+ 8 files changed, 80 insertions(+), 27 deletions(-)
+ rename lib/redis/store/{marshalling.rb => serialization.rb} (90%)
+ rename test/redis/store/{marshalling_test.rb => serialization_test.rb} (98%)
+
+--- a/lib/redis-store.rb
b/lib/redis-store.rb
+@@ -1,12 +1 @@
+-require 'redis'
+ require 'redis/store'
+-require 'redis/store/factory'
+-require 'redis/distributed_store'
+-require 'redis/store/namespace'
+-require 'redis/store/marshalling'
+-require 'redis/store/version'
+-
+-class Redis
+- class Store < self
+- end
+-end
+--- a/lib/redis/store.rb
b/lib/redis/store.rb
+@@ -1,3 +1,9 @@
++require 'redis'
++require 'redis/store/factory'
++require 'redis/distributed_store'
++require 'redis/store/namespace'
++require 'redis/store/serialization'
++require 'redis/store/version'
+ require 'redis/store/ttl'
+ require 'redis/store/interface'
+
+@@ -7,6 +13,24 @@
+
+ def initialize(options = { })
+ super
++
++ unless options[:marshalling].nil?
++puts %(
++ DEPRECATED: You are passing the :marshalling option, which has been
++ replaced with `serializer: Marshal` to support pluggable
serialization
++ backends. To disable serialization (much like disabling
marshalling),
++ pass `serializer: nil` in your configuration.
++
++ The :marshalling option will be removed for redis-store 2.0.
++)
++ end
++
++ @serializer = options.key?(:serializer) ? options[:seri
Bug#864561: mitigated by a fix in ruby2.3 >= 2.3.3-1+deb9u1
Hi, I could not reproduce the attack. The ruby2.3 interpreter in Debian received a patch preventing SMTP command injections https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864860 So this package used in conjunction with the Debian version of the ruby interpreter in stretch or unstable/testing is not vulnerable. Cheers, Cédric signature.asc Description: PGP signature
Bug#882649: stretch-pu: package ruby-httparty/0.13.7-1
On Sat, Nov 25, 2017 at 09:57:45PM +0100, Cédric Boutillier wrote: > On Sat, Nov 25, 2017 at 09:51:52AM +, Adam D. Barratt wrote: > > The metadata for that bug indicates that it also affects the package in > > unstable. Is that correct? > It is correct. I am preparing a newer upstream version for unstable > which also fixes this issue. I uploaded 0.13.7-2 in unstable with the same fix https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864723#12 signature.asc Description: PGP signature
Bug#882802: jessie-pu: package ruby-ox/2.1.1-2+b2
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
Hi,
this update fixes bug #881445 [CVE-2017-15928]
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881445
by cherrypicking a patch from upstream, to crash of the ruby interpreter
on a parse error.
Debdiff attached.
As mentioned in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882724#10
since the debdiffs are identical for jessie and stretch,
except for version numbers and suite, the upload to jessie will follow
shortly this report.
Cheers,
Cédric
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr:en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru ruby-ox-2.1.1/debian/changelog ruby-ox-2.1.1/debian/changelog
--- ruby-ox-2.1.1/debian/changelog 2014-04-04 12:58:15.0 +0200
+++ ruby-ox-2.1.1/debian/changelog 2017-11-26 01:08:40.0 +0100
@@ -1,3 +1,12 @@
+ruby-ox (2.1.1-2+deb8u1) jessie; urgency=medium
+
+ * Team upload
+ * Add fix_parse_obj_segfault.patch picked from upstream
++ fix CVE-2017-15928: segmentation fault in parse_obj
+(Closes: #881445)
+
+ -- Cédric Boutillier Sun, 26 Nov 2017 01:08:40 +0100
+
ruby-ox (2.1.1-2) unstable; urgency=medium
* Team upload.
diff -Nru ruby-ox-2.1.1/debian/gbp.conf ruby-ox-2.1.1/debian/gbp.conf
--- ruby-ox-2.1.1/debian/gbp.conf 1970-01-01 01:00:00.0 +0100
+++ ruby-ox-2.1.1/debian/gbp.conf 2017-11-26 01:08:40.0 +0100
@@ -0,0 +1,3 @@
+[DEFAULT]
+debian-branch=jessie/master
+upstream-branch=jessie/upstream
diff -Nru ruby-ox-2.1.1/debian/patches/fix_parse_obj_segfault.patch
ruby-ox-2.1.1/debian/patches/fix_parse_obj_segfault.patch
--- ruby-ox-2.1.1/debian/patches/fix_parse_obj_segfault.patch 1970-01-01
01:00:00.0 +0100
+++ ruby-ox-2.1.1/debian/patches/fix_parse_obj_segfault.patch 2017-11-26
01:08:40.0 +0100
@@ -0,0 +1,51 @@
+Description: Avoid crash with invalid XML passed to Oj.parse_obj()
+ this fixes CVE-2017-15928
+Author: Peter Ohler
+Origin:
https://github.com/ohler55/ox/commit/e4565dbc167f0d38c3f93243d7a4fcfc391cbfc8.patch
+Bug: https://github.com/ohler55/ox/issues/194
+Debian-Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881445
+Last-Update: 2017-11-25
+
+--- a/ext/ox/obj_load.c
b/ext/ox/obj_load.c
+@@ -791,8 +791,10 @@
+ Helper gh;
+
+ helper_stack_pop(&pi->helpers);
+- gh = helper_stack_peek(&pi->helpers);
+-
++ if (NULL == (gh = helper_stack_peek(&pi->helpers))) {
++ set_error(&pi->err, "Corrupt parse stack, container is
wrong type", pi->str, pi->s);
++ return;
++ }
+ rb_hash_aset(gh->obj, ph->obj, h->obj);
+ }
+ break;
+--- a/ext/ox/err.c
b/ext/ox/err.c
+@@ -42,7 +42,11 @@
+ va_end(ap);
+ }
+
++#if __GNUC__ > 4
++_Noreturn void
++#else
+ void
++#endif
+ ox_err_raise(Err e) {
+ rb_raise(e->clas, "%s", e->msg);
+ }
+--- a/ext/ox/ox.c
b/ext/ox/ox.c
+@@ -990,7 +990,11 @@
+ #endif
+ }
+
++#if __GNUC__ > 4
++_Noreturn void
++#else
+ void
++#endif
+ _ox_raise_error(const char *msg, const char *xml, const char *current, const
char* file, int line) {
+ int xline = 1;
+ int col = 1;
diff -Nru ruby-ox-2.1.1/debian/patches/series
ruby-ox-2.1.1/debian/patches/series
--- ruby-ox-2.1.1/debian/patches/series 2014-03-22 13:16:52.0 +0100
+++ ruby-ox-2.1.1/debian/patches/series 2017-11-26 01:08:40.0 +0100
@@ -1 +1,2 @@
+fix_parse_obj_segfault.patch
000-fix-so-load-path.patch
Bug#880276: caused by the fix of #842432
Control: retitle -1 test using GCM with IV option fails after fix for CVE-2016-7798 Hi, Checking when the package stopped to pass autopkgtests, I could trace the issue to the fix of #842432 in ruby2.3 to avoid IV reuse in GCM mode. The title of the failing test test_ciphertext_encrypted_with_v2_decrypts_with_v2_gcm_iv_option also suggests it is the source of the problem. Cédric
Bug#882724: stretch-pu: package ruby-ox/2.1.1-2+b6
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Hi,
this update fixes bug #881445 [CVE-2017-15928]
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881445
by cherrypicking a patch from upstream, to crash of the ruby interpreter
on a parse error.
Debdiff attached.
As jessie and stretch have the same version of this package, I am
willing to upload the same fix to jessie (same diff except the version
number with deb8 instead of deb9). Should I submit an independent bug
report for the jessie proposed update ?
Thanks in advance.
Cédric
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr:en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru ruby-ox-2.1.1/debian/changelog ruby-ox-2.1.1/debian/changelog
--- ruby-ox-2.1.1/debian/changelog 2014-04-04 12:58:15.0 +0200
+++ ruby-ox-2.1.1/debian/changelog 2017-11-26 01:08:40.0 +0100
@@ -1,3 +1,12 @@
+ruby-ox (2.1.1-2+deb9u1) stretch; urgency=medium
+
+ * Team upload
+ * Add fix_parse_obj_segfault.patch picked from upstream
++ fix CVE-2017-15928: segmentation fault in parse_obj
+(Closes: #881445)
+
+ -- Cédric Boutillier Sun, 26 Nov 2017 01:08:40 +0100
+
ruby-ox (2.1.1-2) unstable; urgency=medium
* Team upload.
diff -Nru ruby-ox-2.1.1/debian/gbp.conf ruby-ox-2.1.1/debian/gbp.conf
--- ruby-ox-2.1.1/debian/gbp.conf 1970-01-01 01:00:00.0 +0100
+++ ruby-ox-2.1.1/debian/gbp.conf 2017-11-26 00:52:18.0 +0100
@@ -0,0 +1,3 @@
+[DEFAULT]
+debian-branch=stretch/master
+upstream-branch=stretch/upstream
diff -Nru ruby-ox-2.1.1/debian/patches/fix_parse_obj_segfault.patch
ruby-ox-2.1.1/debian/patches/fix_parse_obj_segfault.patch
--- ruby-ox-2.1.1/debian/patches/fix_parse_obj_segfault.patch 1970-01-01
01:00:00.0 +0100
+++ ruby-ox-2.1.1/debian/patches/fix_parse_obj_segfault.patch 2017-11-26
01:08:40.0 +0100
@@ -0,0 +1,51 @@
+Description: Avoid crash with invalid XML passed to Oj.parse_obj()
+ this fixes CVE-2017-15928
+Author: Peter Ohler
+Origin:
https://github.com/ohler55/ox/commit/e4565dbc167f0d38c3f93243d7a4fcfc391cbfc8.patch
+Bug: https://github.com/ohler55/ox/issues/194
+Debian-Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881445
+Last-Update: 2017-11-25
+
+--- a/ext/ox/obj_load.c
b/ext/ox/obj_load.c
+@@ -791,8 +791,10 @@
+ Helper gh;
+
+ helper_stack_pop(&pi->helpers);
+- gh = helper_stack_peek(&pi->helpers);
+-
++ if (NULL == (gh = helper_stack_peek(&pi->helpers))) {
++ set_error(&pi->err, "Corrupt parse stack, container is
wrong type", pi->str, pi->s);
++ return;
++ }
+ rb_hash_aset(gh->obj, ph->obj, h->obj);
+ }
+ break;
+--- a/ext/ox/err.c
b/ext/ox/err.c
+@@ -42,7 +42,11 @@
+ va_end(ap);
+ }
+
++#if __GNUC__ > 4
++_Noreturn void
++#else
+ void
++#endif
+ ox_err_raise(Err e) {
+ rb_raise(e->clas, "%s", e->msg);
+ }
+--- a/ext/ox/ox.c
b/ext/ox/ox.c
+@@ -990,7 +990,11 @@
+ #endif
+ }
+
++#if __GNUC__ > 4
++_Noreturn void
++#else
+ void
++#endif
+ _ox_raise_error(const char *msg, const char *xml, const char *current, const
char* file, int line) {
+ int xline = 1;
+ int col = 1;
diff -Nru ruby-ox-2.1.1/debian/patches/series
ruby-ox-2.1.1/debian/patches/series
--- ruby-ox-2.1.1/debian/patches/series 2014-03-22 13:16:52.0 +0100
+++ ruby-ox-2.1.1/debian/patches/series 2017-11-26 01:08:40.0 +0100
@@ -1 +1,2 @@
+fix_parse_obj_segfault.patch
000-fix-so-load-path.patch
Bug#882714: stretch-pu: package ruby-pygments.rb/0.6.3-2
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Hi, the proposed update fixes a reasonable limit to RLIMIT_NOFILE, avoiding closing too many files at a time. This fixes #876768 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876768 and fixes weechat. Best regards, Cédric -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr:en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff -Nru ruby-pygments.rb-0.6.3/debian/changelog ruby-pygments.rb-0.6.3/debian/changelog --- ruby-pygments.rb-0.6.3/debian/changelog 2016-07-08 14:43:00.0 +0200 +++ ruby-pygments.rb-0.6.3/debian/changelog 2017-11-25 21:48:18.0 +0100 @@ -1,3 +1,11 @@ +ruby-pygments.rb (0.6.3-2+deb9u1) stretch; urgency=medium + + * Add Set-reasonable-upper-limit-to-RLIMIT_NOFILE.patch +to avoid closing too many files when mentos starts +(Closes: #876768) + + -- Cédric Boutillier Sat, 25 Nov 2017 21:48:18 +0100 + ruby-pygments.rb (0.6.3-2) unstable; urgency=medium * Team upload diff -Nru ruby-pygments.rb-0.6.3/debian/gbp.conf ruby-pygments.rb-0.6.3/debian/gbp.conf --- ruby-pygments.rb-0.6.3/debian/gbp.conf 1970-01-01 01:00:00.0 +0100 +++ ruby-pygments.rb-0.6.3/debian/gbp.conf 2017-11-25 21:41:16.0 +0100 @@ -0,0 +1,3 @@ +[DEFAULT] +debian-branch = stretch/master +upstream-branch = stretch/upstream diff -Nru ruby-pygments.rb-0.6.3/debian/patches/0011-Set-reasonable-upper-limit-to-RLIMIT_NOFILE.patch ruby-pygments.rb-0.6.3/debian/patches/0011-Set-reasonable-upper-limit-to-RLIMIT_NOFILE.patch --- ruby-pygments.rb-0.6.3/debian/patches/0011-Set-reasonable-upper-limit-to-RLIMIT_NOFILE.patch 1970-01-01 01:00:00.0 +0100 +++ ruby-pygments.rb-0.6.3/debian/patches/0011-Set-reasonable-upper-limit-to-RLIMIT_NOFILE.patch 2017-11-25 21:45:19.0 +0100 @@ -0,0 +1,29 @@ +commit d69d8e9ea11f9cd6652ef4cb066356792182af7e +Author: Cédric Boutillier +Date: Fri Sep 29 22:49:47 2017 +0200 + +Set reasonable upper limit to RLIMIT_NOFILE + +When RLIMIT_NOFILE is too high, the number of files to close +can be too important and the process of closing could take more time +than the timeout set (default to 8s). + +This causes asciidoctor to crash on some architectures + +https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876768 + +Gbp-Pq: Name 0008-Set-reasonable-upper-limit-to-RLIMIT_NOFILE.patch + +diff --git a/lib/pygments/mentos.py b/lib/pygments/mentos.py +index 9c7c650..cf70b7b 100755 +--- a/lib/pygments/mentos.py b/lib/pygments/mentos.py +@@ -334,7 +334,7 @@ def main(): + # close fd's inherited from the ruby parent + import resource + maxfd = resource.getrlimit(resource.RLIMIT_NOFILE)[1] +-if maxfd == resource.RLIM_INFINITY: ++if maxfd >= 65536: + maxfd = 65536 + + for fd in range(3, maxfd): diff -Nru ruby-pygments.rb-0.6.3/debian/patches/series ruby-pygments.rb-0.6.3/debian/patches/series --- ruby-pygments.rb-0.6.3/debian/patches/series2016-07-08 14:43:00.0 +0200 +++ ruby-pygments.rb-0.6.3/debian/patches/series2017-11-25 21:46:08.0 +0100 @@ -8,3 +8,4 @@ 0008-fix_test_pygments.patch 0009-adapt-to-new-pygments.patch 0010-no-relative-path-for-require-in-tests.patch +0011-Set-reasonable-upper-limit-to-RLIMIT_NOFILE.patch
Bug#882649: stretch-pu: package ruby-httparty/0.13.7-1
Control: tags -1 - moreinfo On Sat, Nov 25, 2017 at 09:51:52AM +, Adam D. Barratt wrote: > The metadata for that bug indicates that it also affects the package in > unstable. Is that correct? It is correct. I am preparing a newer upstream version for unstable which also fixes this issue. > [On a side note, and slightly abusing the fact that you're around - > could I persuade you to have a look at https://bugs.debian.org/cgi-bin/ > bugreport.cgi?bug=876768 , please? It's blocking getting a weechat > security issue fixed in stretch.] I am working on it. Expect a bug report for it soon. Best regards, Cédric signature.asc Description: PGP signature
Bug#882649: stretch-pu: package ruby-httparty/0.13.7-1
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Hi, The current package in stretch provides a Ruby library that cannot be loaded properly with Ruby 'gem' tool, because of a too strict versioned dependency on the json Ruby library https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864723 This update adds a patch to relax this dependency in the Gemfile, which fixes the problem. Cédric -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr:en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff -Nru ruby-httparty-0.13.7/debian/changelog ruby-httparty-0.13.7/debian/changelog --- ruby-httparty-0.13.7/debian/changelog 2016-06-07 10:57:47.0 +0200 +++ ruby-httparty-0.13.7/debian/changelog 2017-11-25 00:30:18.0 +0100 @@ -1,3 +1,10 @@ +ruby-httparty (0.13.7-1+deb9u1) stretch; urgency=medium + + * Relax dependency version in gem dependency on json. +This fixes loading httparty with the gem command (Closes: #864723) + + -- Cédric Boutillier Sat, 25 Nov 2017 00:30:18 +0100 + ruby-httparty (0.13.7-1) unstable; urgency=medium * Imported Upstream version 0.13.7 diff -Nru ruby-httparty-0.13.7/debian/gbp.conf ruby-httparty-0.13.7/debian/gbp.conf --- ruby-httparty-0.13.7/debian/gbp.conf1970-01-01 01:00:00.0 +0100 +++ ruby-httparty-0.13.7/debian/gbp.conf2017-11-25 00:15:47.0 +0100 @@ -0,0 +1,3 @@ +[buildpackage] +debian-branch=stretch/master +upstream-branch=stretch/upstream diff -Nru ruby-httparty-0.13.7/debian/patches/relax_version_json.patch ruby-httparty-0.13.7/debian/patches/relax_version_json.patch --- ruby-httparty-0.13.7/debian/patches/relax_version_json.patch 1970-01-01 01:00:00.0 +0100 +++ ruby-httparty-0.13.7/debian/patches/relax_version_json.patch 2017-11-25 00:28:56.0 +0100 @@ -0,0 +1,17 @@ +Author: Cédric Boutillier +Debian-Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864723 +Origin: https://github.com/jnunemaker/httparty/commit/1cbb101feaffcc1f11c77a71009558c6086ebb4b +Forwarded: no +Last-Update: 2017-11-25 + +--- a/httparty.gemspec b/httparty.gemspec +@@ -15,7 +15,7 @@ + + s.required_ruby_version = '>= 1.9.3' + +- s.add_dependency 'json', "~> 1.8" ++ s.add_dependency 'json', ">= 1.8" + s.add_dependency 'multi_xml', ">= 0.5.2" + + # If this line is removed, all hard partying will cease. diff -Nru ruby-httparty-0.13.7/debian/patches/series ruby-httparty-0.13.7/debian/patches/series --- ruby-httparty-0.13.7/debian/patches/series 2016-06-07 10:57:47.0 +0200 +++ ruby-httparty-0.13.7/debian/patches/series 2017-11-25 00:26:34.0 +0100 @@ -1 +1,2 @@ skip_failing_test.patch +relax_version_json.patch
Bug#880963: FTBFS: [kwalify.gemspec] isn't a Gem::Specification (NilClass instead).
Source: kwalify Version: 0.7.2-4 Severity: serious Justification: fails to build from source Coin, When trying to rebuild kwalify, I got the following output: dpkg-buildpackage: info: source package kwalify dpkg-buildpackage: info: source version 0.7.2-3 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Marc Dequènes (Duck) dpkg-buildpackage: info: host architecture amd64 dpkg-source --before-build kwalify dpkg-source: info: using options from kwalify/debian/source/local-options: --unapply-patches fakeroot debian/rules clean dh clean --buildsystem=ruby --with ruby dh: Compatibility levels before 9 are deprecated (level 7 in use) debian/rules override_dh_auto_clean make[1]: Entering directory '/home/boutil/debian/pkg-ruby-extras/kwalify' dh_auto_clean dh_auto_clean: Compatibility levels before 9 are deprecated (level 7 in use) dh_ruby --clean dh_ruby --clean [kwalify.gemspec] isn't a Gem::Specification (NilClass instead). [kwalify.gemspec.gem2deb] isn't a Gem::Specification (NilClass instead). /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:124:in `load_gemspec': E: cannot load gemspec kwalify.gemspec (RuntimeError) from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:34:in `block in initialize' from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:33:in `chdir' from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:33:in `initialize' from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:24:in `new' from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:24:in `initialize' from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:202:in `new' from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:202:in `block in installers' from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:201:in `map' from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:201:in `installers' from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:43:in `clean' from /usr/bin/dh_ruby:96:in `' dh_auto_clean: dh_ruby --clean returned exit code 1 debian/rules:31: recipe for target 'override_dh_auto_clean' failed make[1]: *** [override_dh_auto_clean] Error 1 make[1]: Leaving directory '/home/boutil/debian/pkg-ruby-extras/kwalify' debian/rules:18: recipe for target 'clean' failed make: *** [clean] Error 2 It seems that new versions of gem2deb are unable to parse the gemspec metadata. Cheers, Cédric -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr:en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) signature.asc Description: PGP signature
Bug#862539: RM: ruby-bluecloth -- ROM; dead upstream
Package: ftp.debian.org Severity: normal Hi Please remove ruby-bluecloth from the archive. It is dead upstream and has no more reverse dependencies in unstable. Thanks in advance. Best wishes, Cédric signature.asc Description: PGP signature
Bug#829497: RoM filed
Hi, The corresponding removal bug has been filed. See: bugs.debian.org/862537 Best wishes, Cédric signature.asc Description: PGP signature
Bug#862537: RM: ruby-bdb -- ROM; dead upstream
Package: ftp.debian.org Severity: normal Hi, Please remove ruby-dbd from the archive. It has been dead upstream for a long time. The only reverse dependency, dhelp, has migrated away from Berkeley DB, so there is no reason to keep it any more. Thanks in advance. Cheers, Cédric signature.asc Description: PGP signature
Bug#858972: ftpsync: typo in the maintainers field and description missing
Package: ftpsync Version: 20170204 Severity: normal Dear Maintainer, there is a typo in the Mainer: field in the control file: It should read Debian Mirror Team instead of Debiab. Also could you please add a long description? Thanks in advance! Cheers, Cédric -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) signature.asc Description: PGP signature
Bug#854577: unblock: ruby-hamster/3.0.0-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear release team,
Please unblock package ruby-hamster
Version 3.0.0-1 in testing is affected by a serious bug #853032
because of a timing sensitive test.
Version 3.0.0-2 currently in unstable has this test disabled.
This new version has a patch to disable the test. The VCS-* url are
fixed, and wrap-and-sort was run on the control file.
See the source debdiff against the package in testing attached.
Best regards,
Cédric
unblock ruby-hamster/3.0.0-2
-- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru ruby-hamster-3.0.0/debian/changelog
ruby-hamster-3.0.0/debian/changelog
--- ruby-hamster-3.0.0/debian/changelog 2016-02-26 15:32:31.0 +0100
+++ ruby-hamster-3.0.0/debian/changelog 2017-02-07 23:36:50.0 +0100
@@ -1,3 +1,11 @@
+ruby-hamster (3.0.0-2) unstable; urgency=medium
+
+ * Team upload
+ * Skip timing sensitive test (Closes: #853032)
+ * Fix Vcs-* URLs
+
+ -- Cédric Boutillier Tue, 07 Feb 2017 23:36:50 +0100
+
ruby-hamster (3.0.0-1) unstable; urgency=medium
* update to upstream version 3.0.0.
diff -Nru ruby-hamster-3.0.0/debian/control ruby-hamster-3.0.0/debian/control
--- ruby-hamster-3.0.0/debian/control 2016-02-26 15:32:31.0 +0100
+++ ruby-hamster-3.0.0/debian/control 2017-02-07 23:36:50.0 +0100
@@ -5,13 +5,13 @@
Uploaders: Hanno Zulla
Build-Depends: debhelper (>= 9~),
gem2deb,
+ pry,
rake,
ruby-concurrent (>= 1.0.0),
- ruby-rspec,
- pry
+ ruby-rspec
Standards-Version: 3.9.7
Vcs-Git: https://anonscm.debian.org/git/pkg-ruby-extras/ruby-hamster.git
-Vcs-Browser: https://anonscm.debian.org/git/pkg-ruby-extras/ruby-hamster.git
+Vcs-Browser: https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-hamster.git
Homepage: https://github.com/hamstergem/hamster
Testsuite: autopkgtest-pkg-ruby
XS-Ruby-Versions: all
@@ -27,4 +27,3 @@
Hamster collections are immutable. Whenever you modify a Hamster
collection, the original is preserved and a modified copy is
returned. This makes them inherently thread-safe and sharable.
-
diff -Nru
ruby-hamster-3.0.0/debian/patches/0002-skip-timing-sensitive-test.patch
ruby-hamster-3.0.0/debian/patches/0002-skip-timing-sensitive-test.patch
--- ruby-hamster-3.0.0/debian/patches/0002-skip-timing-sensitive-test.patch
1970-01-01 01:00:00.0 +0100
+++ ruby-hamster-3.0.0/debian/patches/0002-skip-timing-sensitive-test.patch
2017-02-07 23:36:50.0 +0100
@@ -0,0 +1,29 @@
+Subject: skip timing sensitive test
+Author: Cédric Boutillier
+Date: 2017-02-07
+Bug-Debian: https://bugs.debian.org/853032
+
+---
+ spec/lib/hamster/list/multithreading_spec.rb | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/spec/lib/hamster/list/multithreading_spec.rb
b/spec/lib/hamster/list/multithreading_spec.rb
+index bb4359d..1b5e6f7 100644
+--- a/spec/lib/hamster/list/multithreading_spec.rb
b/spec/lib/hamster/list/multithreading_spec.rb
+@@ -30,7 +30,7 @@ describe Hamster::List do
+ threads.each(&:join)
+ end
+
+- it "doesn't give horrendously bad performance if thread realizing the list
sleeps" do
++ xit "doesn't give horrendously bad performance if thread realizing the list
sleeps" do
+ start = Time.now
+ list = (1..100).to_list.map { |x| sleep(0.001); x * 2 }
+
+@@ -45,4 +45,4 @@ describe Hamster::List do
+ elapsed = Time.now - start
+ elapsed.should_not > 0.3
+ end
+-end
+\ No newline at end of file
++end
diff -Nru ruby-hamster-3.0.0/debian/patches/series
ruby-hamster-3.0.0/debian/patches/series
--- ruby-hamster-3.0.0/debian/patches/series2016-02-26 15:32:31.0
+0100
+++ ruby-hamster-3.0.0/debian/patches/series2017-02-07 23:36:50.0
+0100
@@ -1 +1,2 @@
01-remove-code-climate.patch
+0002-skip-timing-sensitive-test.patch
signature.asc
Description: PGP signature
Bug#841583: (no subject)
Thanks for the report. I am investigating this bug. Cheers, Cédric
Bug#845905: (no subject)
Thanks for the report. I am investigating this bug. Cheers, Cédric
Bug#835929: not a bug but a configuration issue on my side
Hi again, This bug was not a bug, but a configuration issue on my machine. See below. I tried to close manually the bug earlier this morning, but because of a typo in the email address, the mail never reached the BTS. I apologize for having you make a new version, to add something that turns out to be an unnecessary dependency (... or I may be wrong again) Cédric Hi, I am closing the bug I opened earlier, as it turns out to not be at all related to liquidprompt, but to the fact that my mercurial configuration file imported from an older machine wanted the git extension, but it wasn't installed. If I was still using mercurial, I would have noticed. Sorry for the noise, and also thanks for taking care of this nice and useful package by the way! Cheers, Cédric
Bug#835929: liquidprompt: sould suggest mercurial-git?
Package: liquidprompt Version: 1.11-1 Severity: minor Dear Maintainer, Opening a terminal in a directory containing a mercurial repository gave me the following message at every prompt: *** failed to import extension hgext.git: No module named git Installing mercurial-git made the message disappear. Should this package suggest installing mercurial-git and/or edit the message to point to the missing package? Thanks! Best wishes, Cédric -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) liquidprompt depends on no packages. liquidprompt recommends no packages. Versions of packages liquidprompt suggests: ii acpi1.7-1 ii lm-sensors 1:3.4.0-3 -- no debconf information
Bug#833788: [DRE-maint] Bug#833788: Bug#833788: Fails to insert tags around code blocks
On Sat, Aug 27, 2016 at 12:09:49PM +0200, Cédric Boutillier wrote: > replace HTML by LegacyHTML on line 30 of This is of course HTMLLegacy... sorry for the typo. Cédric signature.asc Description: PGP signature
Bug#833788: [DRE-maint] Bug#833788: Bug#833788: Fails to insert tags around code blocks
reassign 833788 ruby-kramdown thanks Hi Ryan, I think I found a solution: replace HTML by LegacyHTML on line 30 of /usr/lib/ruby/vendor_ruby/kramdown/converter/syntax_highlighter/rouge.rb. I am reassigning this bug to ruby-kramdown. The next upload will contain this fix. Cédric signature.asc Description: PGP signature
Bug#833788: [DRE-maint] Bug#833788: Bug#833788: Fails to insert tags around code blocks
Hi again, I have been maybe a bit optimistic. 3.2 is still not ready for rouge2, but there is work upstream and maybe it will be integrated in 3.3. The problem you see is related I think to an incompatibility with kramdown, the default markdown renderer, and the version 2 of rouge, the default syntax highlighter. The WIP from upstream members is available in a pull request: https://github.com/jekyll/jekyll/pull/5230 but using this patch fixes some issues (pre missing for fenced code blocks), it doesn't seem to help for indented code blocks... I was able to see again pre tags for your code block by either replacing kramdown by redcarpet, or rouge by coderay or pygments (which was I think the default syntax highlighter in Jekyll 2.x). This might be a workaround for your issue. Cheers, Cédric
Bug#835298: override: jekyll:web/optional
Package: ftp.debian.org Severity: normal Hi, jekyll being written in Ruby, it was put (by default by the helper tool of the Ruby team) in the ruby section. But since it is a static website generator, it is more suitable to put it in the web section, as its control file is saying already. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832227 Thanks Cédric
Bug#833788: [DRE-maint] Bug#833788: Fails to insert tags around code blocks
Hi! Thanks for your report. It seems to be an incompatibility with jekyll 3.1 and ruby-rouge 2.x. Installing an earlier version of ruby-rouge (like 1.9.1) makes pre tags appear again. jekyll 3.2 is supposed to work fully with ruby-rouge 2.x and we are preparing an upload for it, which should then fix this bug. Cheers, Cédric signature.asc Description: PGP signature
Bug#827834: deprecated: use ruby-state-machines instead
Package: ruby-state-machine Followup-For: Bug #827834 This gem is indicated as obsolete, see: https://github.com/pluginaweek/state_machine/issues/343 the only reverse dependency ruby-eye has been patched to use a maintained fork, ruby-state-machines, already in the archive. This bug is not worth fixing. Just remove the package when the new ruby-eye 0.7-4 migrates to testing. Cheers, Cédric
Bug#825281: [DRE-maint] Bug#825281: [package:jekyll] jakyll server --watch fails to execute
Hi, It seems you are running jessie. Can you tell me to which version of the jekyll package it applies? Currently, the version in testing/unstable depends on ruby-jekyll-watch, which installs the ruby-listen and ruby-rb-inotify. Thanks Cédric signature.asc Description: PGP signature
Bug#818472: [DRE-maint] Bug#818472: ruby-diaspora-vines: unsatisfiable Depends: ruby-eventmachine (>= 1.0.8)
Hi! I noticed that this package has no repository on Alioth in the Ruby team. Could you please push the Git repo to the team infrastructure? I could also this weekend start a new one by importing the existing .dsc package. Cheers, Cédric signature.asc Description: PGP signature
Bug#826317: ruby-grape: FTBFS because of failing tests
Package: ruby-grape
Version: 0.5.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
Since the presence of ruby-grape-entity 0.5.1-1 in the archive, ruby-grape
0.5.0-1 has failing tests, resulting in a failing build.
Failures:
1) Grape::API http_codes is used as presenter
Failure/Error: expect(last_response.body).to eql({ code: 408, static:
'some static text' }.to_json)
expected: "{\"code\":408,\"static\":\"some static text\"}"
got: "{:code=>408, :static=>\"some static text\"}"
(compared using eql?)
# ./spec/grape/api_spec.rb:1887:in `block (3 levels) in '
2) Grape::API http_codes presented with
Failure/Error: expect(last_response.body).to eql({ code: 408, static:
'some static text' }.to_json)
expected: "{\"code\":408,\"static\":\"some static text\"}"
got: "{:code=>408, :static=>\"some static text\"}"
(compared using eql?)
# ./spec/grape/api_spec.rb:1898:in `block (3 levels) in '
3) Grape::Middleware::Error with http code presents an error message
Failure/Error: expect(last_response.body).to eq({ code: 200, static:
'static text' }.to_json)
expected: "{\"code\":200,\"static\":\"static text\"}"
got: "{:code=>200, :static=>\"static text\"}"
(compared using ==)
# ./spec/grape/middleware/error_spec.rb:74:in `block (3 levels) in '
Finished in 6.67 seconds (files took 0.77349 seconds to load)
1162 examples, 3 failures
Failed examples:
rspec ./spec/grape/api_spec.rb:1876 # Grape::API http_codes is used as presenter
rspec ./spec/grape/api_spec.rb:1890 # Grape::API http_codes presented with
rspec ./spec/grape/middleware/error_spec.rb:70 # Grape::Middleware::Error with
http code presents an error message
Cheers,
Cédric
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Bug#826316: ruby-grape-entity 0.5.1-1 breaks tests of ruby-grape 0.5.0
Package: ruby-grape-entity Version: 0.5.0-1 Severity: important Dear Maintainer, ruby-grape fails to build because of failing tests. The autopackage tests for ruby-grape started to fail when ruby-grape-entity 0.5.1-1 was introduced. Using version 0.5.0-1 instead to build ruby-grape results in a successful build. Cheers, Cédric -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ruby-grape-entity depends on: ii ruby1:2.3.0+4 ii ruby-activesupport 2:4.2.6-1 ii ruby-multi-json 1.11.2-3 ruby-grape-entity recommends no packages. ruby-grape-entity suggests no packages. -- no debconf information
Bug#824737: caused by a change in pygments not match
Hi, when checking why empty blocks were appearing, I found that pygments are including them on purpose so that empty new lines are not ignored by the HTML parser. See https://bitbucket.org/birkenfeld/pygments-main/src/176329bf17a98677643a935fb6ef5b1d0c88aeb6/pygments/formatters/html.py?at=default&fileviewer=file-view-default#html.py-705 I guess we need to skip/change tests to take care of that. Cheers, Cédric
Bug#825515: [DRE-maint] Bug#825515: lolcat: just hangs
Hi! I have just tested in Konsole and xterm, and for me, it was working as expected. If I run "lolcat file.txt", it displays the content of the file with nice colors, and if I just do "lolcat", then it behaves like cat, and repeats the lines entered in the standard input (only with colors), and ends with ^D. Can you send the exact command you tried to run, and the names of the terminals you tried? Cheers, Cédric
