Re: RFC: dropping Ruby-Versions fields

2022-08-28 Thread Antonio Terceiro
On Sat, Aug 20, 2022 at 01:45:38PM -0300, Antonio Terceiro wrote: > Hello, > > Today, we have XS-Ruby-Versions and XB-Ruby-Versions: fields in our > source packages. There are two fields: > > - XS-Ruby-Versions is required by gem2deb to even build the package, and > is supposed to indicate whic

Re: RFC: dropping Ruby-Versions fields

2022-08-22 Thread Abraham Raji
Hey, On 8/20/22 10:15 PM, Antonio Terceiro wrote: Given that 1) we don't really support packages not working with all available Ruby versions, 2) multiple ruby versions are only present simultaneously during transitions, and 3) we only release with a single version, I propose that we drop these

Re: RFC: dropping Ruby-Versions fields

2022-08-22 Thread Lucas Nussbaum
Hi, On 20/08/22 at 13:45 -0300, Antonio Terceiro wrote: > Hello, > > Today, we have XS-Ruby-Versions and XB-Ruby-Versions: fields in our > source packages. There are two fields: > > - XS-Ruby-Versions is required by gem2deb to even build the package, and > is supposed to indicate which Ruby ve

Re: RFC: dropping Ruby-Versions fields

2022-08-22 Thread Lucas Kanashiro
HI, Em 20/08/2022 13:45, Antonio Terceiro escreveu: > Hello, > > Today, we have XS-Ruby-Versions and XB-Ruby-Versions: fields in our > source packages. There are two fields: > > - XS-Ruby-Versions is required by gem2deb to even build the package, and > is supposed to indicate which Ruby versions

Re: RFC: dropping Ruby-Versions fields

2022-08-22 Thread Cédric Boutillier
Hi! > On Sat, Aug 20, 2022 at 10:16 PM Antonio Terceiro wrote: > > Given that 1) we don't really support packages not working with all > > available Ruby versions, 2) multiple ruby versions are only present > > simultaneously during transitions, and 3) we only release with a single > > version, I

Re: RFC: dropping Ruby-Versions fields

2022-08-21 Thread Utkarsh Gupta
Hey, On Sat, Aug 20, 2022 at 10:16 PM Antonio Terceiro wrote: > Given that 1) we don't really support packages not working with all > available Ruby versions, 2) multiple ruby versions are only present > simultaneously during transitions, and 3) we only release with a single > version, I propose