Hi all,
we recently encountered a compatibility issue with older version of
Clamp that we use on ruby 2.0 installations. Latest Clamp releases
require ruby 2.1+. See [1] for some more details.
The easiest solution seems to be dropping ruby 2.0 support, which was
eol 2016-02-24 anyway. We use scl with ruby 2.2 on rpm based distros,
so we should be safe there.
The question is how big deal it would be for Debian based distros. I
checked ruby versions on what we currently support:
Support for Trusty has been dropped in 1.16 and 1.17 will drop Jessie.
Focussing on 2.1+ or 2.2+ should be no problem.
···
On Tue, Oct 10, 2017 at 01:21:36PM +0200, Tomas Strachota wrote:
>Hi all,
>we recently encountered a compatibility issue with older version of
>Clamp that we use on ruby 2.0 installations. Latest Clamp releases
>require ruby 2.1+. See [1] for some more details.
>
>The easiest solution seems to be dropping ruby 2.0 support, which was
>eol 2016-02-24 anyway. We use scl with ruby 2.2 on rpm based distros,
>so we should be safe there.
>
>The question is how big deal it would be for Debian based distros. I
>checked ruby versions on what we currently support:
>- Debian Jessie - ruby 2.1 (https://packages.debian.org/jessie/ruby)
>- Debian Stretch - ruby 2.3 (https://packages.debian.org/stretch/ruby)
>- Ubuntu Trusty - ruby 1.9 (https://packages.ubuntu.com/trusty/ruby)
>but we depend on a package ruby2.0
>- Ubuntu Xenial - ruby 2.3 (https://packages.ubuntu.com/xenial/ruby)
>
>So the only issue seems to be with Trusty, where we could bump the
>dependency to ruby2.3.
>
>What do you think, are there any objections against dropping it?
···
On Tue, Oct 10, 2017 at 01:45:42PM +0200, Ewoud Kohl van Wijngaarden wrote:
> On Tue, Oct 10, 2017 at 01:21:36PM +0200, Tomas Strachota wrote:
> >we recently encountered a compatibility issue with older version of
> >Clamp that we use on ruby 2.0 installations. Latest Clamp releases
> >require ruby 2.1+. See [1] for some more details.
> >
> >The easiest solution seems to be dropping ruby 2.0 support, which was
> >eol 2016-02-24 anyway. We use scl with ruby 2.2 on rpm based distros,
> >so we should be safe there.
> Support for Trusty has been dropped in 1.16 and 1.17 will drop Jessie.
> Focussing on 2.1+ or 2.2+ should be no problem.
···
On Tue, Oct 10, 2017 at 8:00 AM, Michael Moll wrote:
On Tue, Oct 10, 2017 at 01:45:42PM +0200, Ewoud Kohl van Wijngaarden wrote:
On Tue, Oct 10, 2017 at 01:21:36PM +0200, Tomas Strachota wrote:
we recently encountered a compatibility issue with older version of
Clamp that we use on ruby 2.0 installations. Latest Clamp releases
require ruby 2.1+. See [1] for some more details.
The easiest solution seems to be dropping ruby 2.0 support, which was
eol 2016-02-24 anyway. We use scl with ruby 2.2 on rpm based distros,
so we should be safe there.
Support for Trusty has been dropped in 1.16 and 1.17 will drop Jessie.
Focussing on 2.1+ or 2.2+ should be no problem.
Thanks,
I removed ruby 2.0.0 from configuration matrix of the jenkins jobs
relavant to hammer. And created two redmine issues for removing the
old compatibility code:
···
On Tue, Oct 10, 2017 at 2:44 PM, Andrew Kofink wrote:
> +1 out with the old
>
> On Tue, Oct 10, 2017 at 8:00 AM, Michael Moll wrote:
>>
>> On Tue, Oct 10, 2017 at 01:45:42PM +0200, Ewoud Kohl van Wijngaarden >> wrote:
>> > On Tue, Oct 10, 2017 at 01:21:36PM +0200, Tomas Strachota wrote:
>> > >we recently encountered a compatibility issue with older version of
>> > >Clamp that we use on ruby 2.0 installations. Latest Clamp releases
>> > >require ruby 2.1+. See [1] for some more details.
>> > >
>> > >The easiest solution seems to be dropping ruby 2.0 support, which was
>> > >eol 2016-02-24 anyway. We use scl with ruby 2.2 on rpm based distros,
>> > >so we should be safe there.
>> > Support for Trusty has been dropped in 1.16 and 1.17 will drop Jessie.
>> > Focussing on 2.1+ or 2.2+ should be no problem.
>>
>> exactly.
>> --
>> Michael Moll
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "foreman-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to foreman-dev+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> Andrew Kofink
> akofink@redhat.com
> IRC: akofink
> Associate Software Engineer
> Red Hat Satellite
>
> --
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.