Bug#914989: Adjust found versions
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 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. signature.asc Description: OpenPGP digital signature
Bug#914989: Adjust found versions
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 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. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#914989: Adjust found versions
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 package out of snapshots.debian.org. The issue is with the ruby-grape version currently in testing. >and also >confirm >if restarting gitlab-sidekiq service will solve the issue. If a restart >will solve the issue, we may need to automate that. After downgrading to 1.0.3 restart works. It does not do so with 1.1.0. -nik
Bug#914989: Adjust found versions
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 via dpkg triggers. I was not able to reproduce it when downgrading to ruby-grape 1.0.3 manually. Can you mention the exact steps to reproduce? and also confirm if restarting gitlab-sidekiq service will solve the issue. If a restart will solve the issue, we may need to automate that. signature.asc Description: OpenPGP digital signature
Bug#914989: Adjust found versions
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 my Android device with K-9 Mail. Please excuse my brevity.
