[DRE-maint] Bug#895186: asciidoctor: url-related issues are fixed upstream

2018-04-14 Thread Joseph Herlant
Control: tag -1 + fixed-upstream Hi, The issue has been fixed upstream and will be released as part of 1.5.7 whose timeline is being discussed in https://github.com/asciidoctor/asciidoctor/issues/2663 Thanks, Joseph ___ Pkg-ruby-extras-maintainers

[DRE-maint] Bug#895187: asciidoctor: url-related issues are fixed upstream

2018-04-14 Thread Joseph Herlant
Control: tag -1 + fixed-upstream Hi, The issue has been fixed upstream and will be released as part of 1.5.7 whose timeline is being discussed in https://github.com/asciidoctor/asciidoctor/issues/2663 Thanks, Joseph ___ Pkg-ruby-extras-maintainers

[DRE-maint] Bug#909105: consider switching asciidoctor to Architecture: all

2018-09-18 Thread Joseph Herlant
Hi Helmut, Thanks for your report. I think you can find the explanations to those questions in #893467 which is the origin of th split of the asciidoc package. Let me know if there are still more questions about it after reading #893467. Regarding the dependency version, that's a good point

[DRE-maint] Bug#909105: consider switching asciidoctor to Architecture: all

2018-09-18 Thread Joseph Herlant
> I reported that bug. Indeed, that's why I was confused! :D > After reading my report three times, I see how you > might have interpreted it that way. I wrote that there is a problem, > "because asciidoctor is Architecture: all and implicitly Multi-Arch: > no". The problem results from the

[DRE-maint] Bug#899307: ruby-sequel-pg: All SELECT ::Dataset methods fails with FrozenError

2019-06-12 Thread Joseph Herlant
Control: tags -1 + moreinfo Hi Andrey, I'm trying to reproduce your issue but I can't seem to be able to. I get an error the 1st time I try to establish the connection but I believe that's linked to something else. Here's what I see (I use docker run --rm --name pg-docker -e

[DRE-maint] Bug#934998: asciidoctor: new upstream version

2019-08-18 Thread Joseph Herlant
Control: owner -1 ! Hi Brian, Thanks for your report. I was working on that upgrade a few wweeks ago but hit some roadblock as you can see in https://lists.debian.org/debian-ruby/2019/06/msg3.html I'll try to see if I can package the new version today. Joseph -BEGIN PGP SIGNATURE-

[DRE-maint] Bug#934530: ruby-sequel-pg - new version available

2019-08-11 Thread Joseph Herlant
Package: ruby-sequel-pg Version: 1.6.16-1+b2 Severity: wishlist Dear Maintainer, I can see that ruby-sequel-pg has a new version available and has a RC bug (#899307 which is not happening anymore, I checked). Do you mind if I prepare the new version and upload it as a team upload? Thanks for

[DRE-maint] Bug#935196: asciidoctor: Source highlighting does not work any more

2019-08-20 Thread Joseph Herlant
Control: forwarded -1 https://github.com/asciidoctor/asciidoctor/issues/3394 Control: owner -1 ! Hi Sebastien, Thanks for your report. I'm working on a patch with upstream. Thanks, Joseph ___ Pkg-ruby-extras-maintainers mailing list

[DRE-maint] Bug#946805: ruby-hamlit: Please upgrade to latest upstream

2019-12-15 Thread Joseph Herlant
Package: ruby-hamlit Version: 2.9.2-2 Severity: wishlist Dear Maintainer, Since the upgrade of ruby-tilt to 2.0.10 yesterday the tests for ruby-hamlit fail. See: https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby- hamlit/3668609/log.gz It seems that this has been fixed in the latest