Control: severity -1 important
On Fri, 30 Nov 2018 10:50:54 +0530 Pirate Praveen
wrote:
> On Thu, 29 Nov 2018 18:08:13 +0100 Dominik George
> wrote:
> > Hi,
> >
> > >> It is not a regression in unstable, so it need not block the testing
> > >migration.
> >
> > ...but it needs get gitlab autor
On Thu, 29 Nov 2018 18:08:13 +0100 Dominik George
wrote:
> Hi,
>
> >> It is not a regression in unstable, so it need not block the testing
> >migration.
>
> ...but it needs get gitlab autoremoved from testing if not fixed :).
Yes, we need to find the root cause or reduce severity if there is a
Hi,
>> It is not a regression in unstable, so it need not block the testing
>migration.
...but it needs get gitlab autoremoved from testing if not fixed :).
>I was not able to reproduce it when downgrading to ruby-grape 1.0.3
>manually.
This is correct. I hope you don't expect users to dig a pa
On Thu, 29 Nov 2018 19:58:24 +0530 Pirate Praveen
wrote:
> It is not a regression in unstable, so it need not block the testing
> migration. I will dig deeper to find the root cause. At least the gitlab's
> main Gemfile.lock is supposed to be regenerated every time a ruby package is
> updated v
Control: found -1 10.8.7+dfsg-1
It is not a regression in unstable, so it need not block the testing migration.
I will dig deeper to find the root cause. At least the gitlab's main
Gemfile.lock is supposed to be regenerated every time a ruby package is updated
via dpkg triggers.
--
Sent from
5 matches
Mail list logo