Re: ruby-premailer build failure in salsa ci

Am Mittwoch, den 14.08.2019, 21:45 +0200 schrieb Daniel Leidert: > Am Mittwoch, den 14.08.2019, 22:21 +0500 schrieb Pirate Praveen: > > It fails with error, > > > > Encoding::InvalidByteSequenceError: "\xE2" on US-ASCII > > > > full log

RFS: ruby-cucumber-expressions

Hello, This package is ready to be uploaded. It has a new upstream release. Salsa CI shows passed with no errors. Could someone please sponsor the upload? Regards, James signature.asc Description: OpenPGP digital signature

Re: ruby-premailer build failure in salsa ci

On Wed, Aug 14, 2019 at 10:21:51PM +0500, Pirate Praveen wrote: > It fails with error, > > Encoding::InvalidByteSequenceError: "\xE2" on US-ASCII > > full log > > Though it built fine in sbuild. I think salsa ci should use sbuild

Re: ruby-premailer build failure in salsa ci

Am Mittwoch, den 14.08.2019, 22:21 +0500 schrieb Pirate Praveen: > It fails with error, > > Encoding::InvalidByteSequenceError: "\xE2" on US-ASCII > > full log https://salsa.debian.org/ruby-team/ruby-premailer/-/jobs/276596 > > Though it built fine in sbuild. I think salsa ci should use sbuild

Re: [Pkg-javascript-devel] Suggestions on ruby-task-list and node-deckar01-task-list

Quoting Pirate Praveen (2019-08-14 19:08:47) > Hi ruby and js teams, > > task_list project [1] provides both ruby and nodejs code from the same > repo. Currently only ruby-task-list binary package is created. I added > a new binary package node-deckar01-task-list for the nodejs code, but > it

ruby-premailer build failure in salsa ci

It fails with error, Encoding::InvalidByteSequenceError: "\xE2" on US-ASCII full log Though it built fine in sbuild. I think salsa ci should use sbuild or same settings as sbuild.

Suggestions on ruby-task-list and node-deckar01-task-list

Hi ruby and js teams, task_list project [1] provides both ruby and nodejs code from the same repo. Currently only ruby-task-list binary package is created. I added a new binary package node-deckar01-task-list for the nodejs code, but it was rejected by ftp masters [2]. They think we should

autopkgtest passing, although gem2deb fails

Hi, can you please help me to examine, why this autopkgtest log shows "pass" instead of "fail"? gem2deb checking the dependencies actually fails missing jekyll. So why is this not reported as an autopkgtest failure? Any idea? Neither autopkgtest nor gem2deb have changed recently. Is this related

Re: team repo configuration on salsa

Am Mittwoch, den 14.08.2019, 03:44 +0530 schrieb Utkarsh Gupta: > On 12/08/19 3:18 pm, Cédric Boutillier wrote: > > > > > > (note that I didn't create the corresponding debian/salsa-ci.yml files > > in the repos). > > The whole world knows by now, but still.. > I have initialized

Re: team repo configuration on salsa

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 of things in gem2deb > as well (if no one does by then). I

Re: Ruby team sprint(s)

Hi Cédric, 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