On Thu, 29 Nov 2018 19:58:24 +0530 Pirate Praveen
<prav...@onenetbeyond.org> 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.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to