On 2020, മേയ് 9 10:15:36 AM IST, Pirate Praveen <prav...@onenetbeyond.org>
wrote:
>
>
>On 2020, മേയ് 9 3:09:54 AM IST, Georg Faerber <ge...@debian.org> wrote:
>>Hi,
>>
>>On 20-05-09 00:02:06, Utkarsh Gupta wrote:
>>> [...]
>>>
>>> Please help us in getting Rails 6 to Sid & Bullseye, too :)
>>>
>>> If you have any questions, please don't hesitate to ask them here or
>>> on IRC.
>>
>>I'm wondering how the help should look like, in detail.. that is: as far
>>as I'm not mistaken, rails 6 is already in experimental. What about
>>reducing manual labor involved in this, and leveraging ci.debian.net to
>>run tests against all of the involved packages. Of course, this only
>>makes sense for packages which ship autopkgtests, and so far I didn't
>>check how many of the involved do so, but I would assume lots of them
>>do.
>>
>>Afterwards the results could be "looked on" programmatically, assuming
>>packages with passing autopkgtests good to go, leaving only packages
>>with failing autopkgtest to look at. And packages without tests,
>>additionally.
>>
>>Thoughts?
>
>Since it is a major rails version, I don't think many gems will have a >=
>constraint allowing it to accept rails 6, those who do are marked as such in
>the list. So almost all of them are going to fail (check dependencies test)
>even if we just need to relax dependencies.
After looking at the list again, I see there is a benefit to automated tests.
For packages listed under,
Ready in unstable (need confirmation, dependency is not strict) (many packages
have no tests)
>>Cheers,
>>Georg
>>
>
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
