Control: clone -1 -2
Control: retitle -2 update ruby-sexp-processor to 4.17
Control: reassign -2 ruby-sexp-processor
On Sun, 30 Apr 2023 20:35:00 +0530 Praveen Arimbrathodiyil
wrote:
> Package: ruby-ruby-parser
> Version: 3.19.2-1
> Severity: important
>
> Gitlab 15.11.0 needs ruby-ruby-parser
Control: reassign ruby3.1
Control: affects ruby-ruby-parser
On Thu, 4 May 2023 23:12:08 +0530 Praveen Arimbrathodiyil
wrote:
>
>
> On 04/05/23 11:05 pm, Praveen Arimbrathodiyil wrote:
> >
> >
> > On 04/05/23 10:44 pm, Pirate Praveen wrote:
> >> Running the tests like upstream would with ruby 3
On 04/05/23 11:05 pm, Praveen Arimbrathodiyil wrote:
On 04/05/23 10:44 pm, Pirate Praveen wrote:
Running the tests like upstream would with ruby 3.1 installed via rvm,
the same errors are reproduced.
https://github.com/seattlerb/ruby_parser/issues/337#issuecomment-1535023385
on bullseye
On 04/05/23 10:44 pm, Pirate Praveen wrote:
Running the tests like upstream would with ruby 3.1 installed via rvm,
the same errors are reproduced.
https://github.com/seattlerb/ruby_parser/issues/337#issuecomment-1535023385
on bullseye with rvm installed ruby 3.0, all tests pass. Though on
On Sun, 30 Apr 2023 20:35:00 +0530 Praveen Arimbrathodiyil
wrote:
> Package: ruby-ruby-parser
> Version: 3.19.2-1
> Severity: important
>
> Gitlab 15.11.0 needs ruby-ruby-parser 3.20 and while trying to update
> it, the build fails with
>
> 13) Failure:
> TestRubyParserV32#test_unless_pre_not_
5 matches
Mail list logo