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:

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,

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.

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

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

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:

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

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,

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

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

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;) > >

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) > # >

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

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. > > >

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.

Bug#993739: blends-common: tempfile has to be replaced by mktemp

oan 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/sh

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

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

Bug#988084: unblock: ruby-rugged/1.1.0+ds-4

(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

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

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

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

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

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

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

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.

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:

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

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

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

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

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

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

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,

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

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

Bug#925397: unblock: nanoc/4.11.0-3

+ + * 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

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.

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

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).

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

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:

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

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

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

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

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

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

Bug#890860: stretch-pu: package ruby-redis-store/1.1.6-1

: #882034) + + -- Cédric Boutillier <bou...@debian.org> 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 0

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

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

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

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

Bug#882034: ruby-redis-store for jessie and stretch (#882034 CVE-2017-1000248). Proposed patch

) + + -- Cédric Boutillier <bou...@debian.org> 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

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

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 preparin

Bug#882802: jessie-pu: package ruby-ox/2.1.1-2+b2

/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

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

Bug#882724: stretch-pu: package ruby-ox/2.1.1-2+b6

+(Closes: #881445) + + -- Cédric Boutillier <bou...@debian.org> 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.000

Bug#882714: stretch-pu: package ruby-pygments.rb/0.6.3-2

closing too many files when mentos starts +(Closes: #876768) + + -- Cédric Boutillier <bou...@debian.org> 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/gb

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.

Bug#882649: stretch-pu: package ruby-httparty/0.13.7-1

) stretch; urgency=medium + + * Relax dependency version in gem dependency on json. +This fixes loading httparty with the gem command (Closes: #864723) + + -- Cédric Boutillier <bou...@debian.org> Sat, 25 Nov 2017 00:30:18 +0100 + ruby-httparty (0.13.7-1) unstable; urgency=medium * Im

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

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

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

Bug#854577: unblock: ruby-hamster/3.0.0-2

) unstable; urgency=medium + + * Team upload + * Skip timing sensitive test (Closes: #853032) + * Fix Vcs-* URLs + + -- Cédric Boutillier <bou...@debian.org> 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 -Nr

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

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

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

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

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

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

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

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:

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

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

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

Bug#816863: RFP: ruby-ffi-bit-masks -- FFI plugin which adds support for bitmasked types

Package: wnpp Severity: wishlist * Package name: ruby-ffi-bit-masks Version : 0.1.0 Upstream Author : Hal Brodigan * URL : https://github.com/postmodern/ffi-bit_masks * License : Expat Programming Lang: Ruby Description : FFI

  1   2   3   4   5   6   >