Hi Abhijith,
On Sun, 12 Jan, 2020, 12:35 PM abhijith sheheer,
wrote:
> Hi,
> ruby-get-process-mem have been updated to latest upstream 0.2.5 and builds
> in clean chroot.
>
When you say "build", you mean sbuild or meta/build?
In any case, could you run meta/build (if not done yet) and check fo
Hi Abhijith,
On Sun, 12 Jan, 2020, 12:36 PM abhijith sheheer,
wrote:
> Thanks Utkarsh.
> Should we update the ruby-team/ruby-pg with my commits?
>
I already have :)
Best,
Utkarsh
>
Hi,
ruby-get-process-mem have been updated to latest upstream 0.2.5 and builds
in clean chroot.
Link: https://salsa.debian.org/abspython-guest/ruby-get-process-mem/
Needs review and sponsorship.
Thanks in advance.
Regards,
Abhijith Sheheer
On 2020, ജനുവരി 12 1:53:56 AM IST, "David Suárez"
wrote:
>Could you try again?. The upload goes now for experimental until
>duplicates packages of v3 of this same gem gets ROM.
>
>I will request ROM for:
>
> - ruby-aws-sdk-s3
> - ruby-aws-sdk-core
> - ruby-aws-sdk-kms
>
>The motive is,
On 11/1/20 21:09, Pirate Praveen wrote:
On ശ, Jan 11, 2020 at 20:46, David Suárez wrote:
Well, if you applies this, I dunno why the upload were blocked until
upstream CI of gitlab. If gitlab is in experimental, I dunno why it
should block any unstable (working and well done packaging) upl
On ശ, Jan 11, 2020 at 20:46, David Suárez
wrote:
Well, if you applies this, I dunno why the upload were blocked until
upstream CI of gitlab. If gitlab is in experimental, I dunno why it
should block any unstable (working and well done packaging) upload.
Because we actually run the upstrea
Hi,
On 11/1/20 20:29, Pirate Praveen wrote:
On ശ, Jan 11, 2020 at 19:53, David Suárez wrote:
Hi,
Any update here?
Utkarsh was looking at the upstream ci and possibility of fixing the
upstream tests. But I have uploaded it now.
So now, we have two broken packages:
- ruby-aws-sdk (exp
On ശ, Jan 11, 2020 at 19:53, David Suárez
wrote:
Hi,
Any update here?
Utkarsh was looking at the upstream ci and possibility of fixing the
upstream tests. But I have uploaded it now.
So now, we have two broken packages:
- ruby-aws-sdk (experimental version): broken to enduser who wa
Hi,
debcheck complains for (probably all) Ruby packages about the fact that ruby-
interpreter cannot be satisfied on any architecture. It seems that jruby used
to provide ruby-interpreter up to version 1.7.26-1 (oldstable). Should this be
dropped from the gem2deb templates and then (via the usual
9 matches
Mail list logo