Hi Utkarsh,
On Sun, Dec 15, 2019 at 11:34 AM Utkarsh Gupta
wrote:
> You could've avoided that trouble (at least some part of it) by using
> the meta/build[1] script.
The rebuild of the rdeps is really neat. I didn't know about this
repo. Thanks a lot! :)
Joseph
Hi guys,
I updated ruby-tilt yesterday and I see a few packages broken after that:
* ruby-hamlit but it's an old version and testing with tilt 2.0.10 on
the latest version works so if you're ok with it I'll update the
package later today
* ruby-slim: for this one it seems that the upstream tests
Hi guys,
FYI I'm moving the default branches of the following packages I've
worked on recently from master to debian/master and updating gbp.conf
there after dropping the master branch, so please make sure to update
your local branches if you plan to work on them:
* asciidoctor
* ruby-asciidoctor
On Mon, Aug 26, 2019 at 5:32 AM Antonio Terceiro wrote:
> It's probably a good idea, and will avoid having to do the same
> workaround on every package that has a similar issue.
Awesome, thanks for your reply. I created
https://salsa.debian.org/ruby-team/gem2deb/merge_requests/6
Joseph
Hi Antonio,
Thanks for that awesome walk-though and findings!
Where would you stand on having gem2deb-test-runner moving out the
Gemfile.lock like it does with lib for autopkgtest mode?
I don't see a lot of value in keeping the Gemfile.lock in an
environment where the gems are system-packaged. (Ha
So I spent some time trying to debug the issue but came up empty.
The load path are really similar:
During the build:
- LOAD_PATH -
/<>/spec
/<>/spec
/<>/lib
/<>/debian/ruby-arbre/usr/lib/ruby/vendor_ruby
.
/usr/share/rubygems-integration/all/gems/did_you_mean-1.2.1/lib
/usr/local/lib/sit
Hi Utkarsh,
Looking at ruby arbre right now I'm able to reproduce your issue using
gbp buildpackage --run-autopkgtest (with a fresh sbuild chroot for
unstable).
> Now, the packages using bundler and ruby-combustion, their autopkgtest
> fails (build is perfectly fine!) saying:
> "File does not exi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi guys,
I'm preparing the lastest version of asciidoctor and am facing some issues.
Upstream removed the test suite from the gem in
https://github.com/asciidoctor/asciidoctor/pull/3048 to reduce the
size
of the gem.
So I switched the watch file to
Hi Cédric,
On Wed, Nov 28, 2018 at 1:53 AM Cédric Boutillier wrote:
> Uploaded, and tagged/pushed to salsa.
Awesome, thanks a lot! :)
> I meant use debhelper-compat in the debian/control boilerplate created
> by gem2deb instead of the debian/compat file. And/or also update the
> "debhelper-comp
Hi Cédric,
Sorry for the late reply, I've been having crazy days lately.
On Tue, Nov 27, 2018 at 3:47 PM Cédric Boutillier wrote:
> I don't have time and energy tonight to wait for all reverse
> build/dependency to build. But if you agree we my proposition (or make a
> new one), I am willing to
Hi guys,
I've updated the asciidoctor package with the latest 1.5.8 version of
asciidoctor.
It fixes 2 bugs: #913892 which is a CVE and #909105 which currently
blocks some packages like ndctl from being available on ia64 (see the
last comments at the end of #909105).
It is available in https://sa
Could it be due to the fact that you have sha1 certs?
https://salsa.debian.org/ruby-team/ruby-redis/blob/master/test/support/ssl/trusted-cert.crt
Not sure if it's still accepted with openssl 1.1.
On Thu, Oct 11, 2018 at 10:28 AM Pirate Praveen
wrote:
>
> Hi,
>
> Can someone help with ruby-redis te
On Tue, May 15, 2018 at 2:59 PM, Cédric Boutillier wrote:
> Uploaded. Thanks!
Awesome, thanks Cedric! :)
Hi guys,
I've updated the asciidoctor package with the latest 1.5.7.1 version
of asciidoctor.
It is available in https://salsa.debian.org/ruby-team/asciidoctor
Could you have a look when you have a moment to review the changes please?
Thanks for your help,
Joseph
On Sat, May 12, 2018 at 11:41 PM, Guillaume Grossetie
wrote:
> Just so you know, a new bug fix release release is available 1.5.7.1:
> https://github.com/asciidoctor/asciidoctor/releases/tag/v1.5.7.1
Good catch, thanks Guillaume.
Packaging the new version right now.
Joseph
Awesome, thanks Antonio! :)
I updated another patch to be able to push it upstream. The repo is
now up-to-date. If you pulled the repo in the interval, could you pull
again before reviewing please?
Thanks for your help,
Joseph
On Sat, May 5, 2018 at 11:43 PM, Joseph Herlant wrote:
> Hi guys,
>
> I'
Hi guys,
I've updated the asciidoctor package with the latest 1.5.7 release
from 3 days ago.
It is available in https://salsa.debian.org/ruby-team/asciidoctor
Could you have a look when you have a moment to review the changes please?
Thanks for your help,
Joseph
Hi,
I've done a modification to fix the FTBS in asciidoctor.
Could someone have a look at it please?
https://salsa.debian.org/ruby-team/asciidoctor
Thanks for your help
Joseph
Hi Lucas,
Thanks a lot for your review
> After had a look in ruby-tilt a saw that upstream changed the years of
> the copyright, you should update it in debian/copyright file.
Updated in the repo.
> Another minor issue: you could check dependencies during build in
> debian/rules, you just need
Hi guys,
I package ruby-tilt's latest version (mostly to fix some annoying
warning I had on other applications that have been removed upstream
about a year ago).
Also fixed a few lintian complains and enabled the autopkgtests
The new version is available in
https://salsa.debian.org/ruby-team/ruby-
Hi,
I'd like to help maintaining the asciidoctor package so I've requested
the access to the ruby-team on Salsa (sending this mail to give
context to the request).
Thanks for your help,
Joseph
22 matches
Mail list logo
