[DRE-maint] Bug#914989: Adjust found versions

Pirate Praveen praveen at onenetbeyond.org
Sat Dec 8 14:11:02 GMT 2018


Control: severity -1 important

On Fri, 30 Nov 2018 10:50:54 +0530 Pirate Praveen
<praveen at onenetbeyond.org> wrote:
> On Thu, 29 Nov 2018 18:08:13 +0100 Dominik George <natureshadow at debian.org> 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 an easy work around like restarting the service.
> 
> > >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 package out of snapshots.debian.org. The issue is with the ruby-grape version currently in testing.
> 
> Well, this is for confirming the bug. If it was expecting an exact version, any version change will trigger the bug.
> 
> > After downgrading to 1.0.3 restart works. It does not do so with 1.1.0.
> 
> I will try to update to 1.1.0 and confirm soon.


I was not able to reproduce the issue. I did a clean install of gitlab
11.3.11, then downgraded ruby-grape to 1.0.3 from snapshots, then
upgraded ruby grape to 1.1. May be because there was no jobs being
processed by sidekiq. If we really want to fix this, probably we should
restart sidekiq service every time a ruby library is updated.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20181208/2df1d9df/attachment.sig>


More information about the Pkg-ruby-extras-maintainers mailing list