On Thu, 14 Feb 2019 21:26:34 +0530 Pirate Praveen <prav...@onenetbeyond.org> wrote: > On Thu, 14 Feb 2019 16:35:22 +0100 Paul Gevers <elb...@debian.org> wrote: > > Hi > > > > On 14-02-2019 14:36, Utkarsh Gupta wrote: > > > The autopkgtest regression in testing was due to ruby-capybara[2], which > > > was not in testing, which was blocked by an RC bug in puma[3]. > > ^^^^^^^^^^^^^^^^^^^^^ > > which is bug #900156 which was filed on 26 May 2018 and didn't see a fix > > until 2 days before the soft freeze. > > > > rails 5 transition took longer than we expected. Without rails 5 in testing, > we did not have any chance to get diaspora or redmine to buster. Once we got > rails 5 to buster, we focused on the dependencies and noticed puma was > blocking ruby-capybara. >
Also ruby-capybara started depending on puma only from 3.12.0, which was uploaded on 2019-01-07 only (because rails recommends ruby-capybara >= 2.15). At this point only I started caring about puma and realized its original uploader was no longer in the uploaders list. So I added myself as an uploader for puma and fixed the bug with a patch from upstream. Then there was a new rc bug appearing only on single CPU machines, which was fixed the very next day. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
