On 19-08-28 10:07:34, Utkarsh Gupta wrote:
> I did complete fixing the pending test failures (as an attempt to
> enable tests in all the packages), thus requesting you to review and
> upload the same (since they are NEW).
>
> ruby-benchmark-memory
> ruby-ammeter
> ruby-arbre (thanks to terceiro :D
On 19-08-28 10:13:53, Utkarsh Gupta wrote:
> Perfecto.
> I just did add a metadata file to include d/upstream/metadata (as we
> discussed in the BoF); rest in on you :D
:)
> Also, if possible, I'd love to see gem2deb using the correct upstream
> tarballs in d/watch *somehow* instead of what it fe
Hey Georg,
On 14/08/19 3:43 pm, Georg Faerber wrote:
> Hi Utkarsh, all,
>
> On 19-08-14 03:44:02, Utkarsh Gupta wrote:
>> But FWIW, we have CI enabled for every package under the Ruby team now.
> That's really great, thanks to everyone involved!
>
>> Over the next few days, I'll integrate a couple
Hey,
I did complete fixing the pending test failures (as an attempt to enable
tests in all the packages), thus requesting you to review and upload the
same (since they are NEW).
ruby-benchmark-memory
ruby-ammeter
ruby-arbre (thanks to terceiro :D)
More to come..
Best,
Utkarsh
signature.asc
Hey,
Since a couple of gems were needing rails 5.2.3 (and we were (at least I
was :P) patching it out to use 5.2.2 that is available in the archive),
I hit multiple obstacles where certain gems won't work with 5.2.2.
So to save the pain of patching, I uploaded 5.2.3 to the archive.
If you were pa
Hey,
On 27/08/19 2:17 pm, Georg Faerber wrote:
> Dear team, all,
>
> On 19-08-11 17:27:16, Cédric Boutillier wrote:
>> I maintain my proposition to hold a Ruby sprint in Paris.
>> Do we plan to have a 5-day sprint as the last two times? I think it was
>> a good format to have a lot of things done.
Hey,
On 27/08/19 2:25 pm, Georg Faerber wrote:
> On 19-08-27 08:44:47, Georg Faerber wrote:
>> Also, Antonio, I think consensus is reached regarding your initial
>> proposal, minus squashing the commits, so I think you're good to go
>> ahead.
> If possible, I would like to not receive build notifi
Hey,
On 27/08/19 7:04 pm, Georg Faerber wrote:
> On 19-08-27 08:44:47, Georg Faerber wrote:
>> Also, Antonio, I think consensus is reached regarding your initial
>> proposal, minus squashing the commits, so I think you're good to go
>> ahead.
> As per discussion on IRC, this is now live: KGB notif
Hi,I've updated the Debian package of the Ruby gem premailer-rails.
The package was tested on sbuild, meta and was successfully built.
Also, all the test are passed successfully. I've pushed the package to
the salsa repo which may be found at
https://salsa.debian.org/ruby-team/ruby-premailer-rails
On 19-08-27 08:44:47, Georg Faerber wrote:
> Also, Antonio, I think consensus is reached regarding your initial
> proposal, minus squashing the commits, so I think you're good to go
> ahead.
As per discussion on IRC, this is now live: KGB notifications for
commits and CI pipeline stati are now sen
On 19-08-27 08:44:47, Georg Faerber wrote:
> Also, Antonio, I think consensus is reached regarding your initial
> proposal, minus squashing the commits, so I think you're good to go
> ahead.
If possible, I would like to not receive build notifications for tags,
but just for commits. In the huge ma
Dear team, all,
On 19-08-11 17:27:16, Cédric Boutillier wrote:
> I maintain my proposition to hold a Ruby sprint in Paris.
> Do we plan to have a 5-day sprint as the last two times? I think it was
> a good format to have a lot of things done.
>
> If we aim for December or January, I can propose t
Hi all,
On 19-08-17 13:02:44, Antonio Terceiro wrote:
> fair enough. I noticed that the python team has two channels:
> #debian-python for humans, and #debian-python-changes for
> notifications. maybe we could do something similar?
This seems like the way to go given all the mails in response, s
13 matches
Mail list logo
