John Covici wrote:
> On Tue, 22 Aug 2017 05:16:55 -0400,
> Neil Bothwick wrote:
>> [1 ]
>> [2 ]
>> RUBY_TARGET Is an expanded use flag so ypu need to run emerge - - update - -
>> newuse @world to apply the change. The depclean should work,
>> Just check for stray ruby settings in /etc/portage.
On Tue, Aug 22, 2017 at 07:57:39AM -0400, John Covici wrote:
> >
> > I deleted RUBYTARGETS from make.conf, ran eselect to make ruby22 the
> > default, but when I ran emerge --depclean I still have packages
> > pulling ruby21 as follows:
> >
> > Calculating dependencies .. . done!
> > dev-l
On Tue, 22 Aug 2017 05:16:55 -0400,
Neil Bothwick wrote:
>
> [1 ]
> [2 ]
> RUBY_TARGET Is an expanded use flag so ypu need to run emerge - - update - -
> newuse @world to apply the change. The depclean should work,
> Just check for stray ruby settings in /etc/portage.
>
> On 22 August 2017 0
RUBY_TARGET Is an expanded use flag so ypu need to run emerge - - update - -
newuse @world to apply the change. The depclean should work,
Just check for stray ruby settings in /etc/portage.
On 22 August 2017 05:21:23 EEST, John Covici wrote:
>On Mon, 21 Aug 2017 21:20:04 -0400,
>Alec Ten Harms
On Tue, 22 Aug 2017 02:58:31 -0400,
Raffaele Belardi wrote:
>
> On Mon, 2017-08-21 at 22:21 -0400, John Covici wrote:
> > On Mon, 21 Aug 2017 21:20:04 -0400,
> > Alec Ten Harmsel wrote:
> > >
> > I deleted RUBYTARGETS from make.conf, ran eselect to make ruby22 the
> > default, but when I ran emer
On Mon, 2017-08-21 at 22:21 -0400, John Covici wrote:
> On Mon, 21 Aug 2017 21:20:04 -0400,
> Alec Ten Harmsel wrote:
> >
> I deleted RUBYTARGETS from make.conf, ran eselect to make ruby22 the
> default, but when I ran emerge --depclean I still have packages
> pulling ruby21 as follows:
>
> Calcu
On Mon, 21 Aug 2017 21:20:04 -0400,
Alec Ten Harmsel wrote:
>
>
> On 08/21/2017 10:13 AM, allan gottlieb wrote:
> >
> > I issued emerge --pretend --verbose --depclean =ruby-2.1.9
> > and the response was
> >
> > dev-lang/ruby
> > selected: 2.1.9
> > protected: none
> > omitted:
On Mon, Aug 21 2017, Alec Ten Harmsel wrote:
> On 08/21/2017 10:13 AM, allan gottlieb wrote:
>>
>> I issued emerge --pretend --verbose --depclean =ruby-2.1.9
>> and the response was
>>
>> dev-lang/ruby
>> selected: 2.1.9
>> protected: none
>> omitted: 2.2.6
>>
>> Am I correct in b
On 08/21/2017 10:13 AM, allan gottlieb wrote:
I issued emerge --pretend --verbose --depclean =ruby-2.1.9
and the response was
dev-lang/ruby
selected: 2.1.9
protected: none
omitted: 2.2.6
Am I correct in believing it is now safe to issue
emerge --depclean =ruby-2.1.9
than
On Mon, Aug 21 2017, Hans de Graaff wrote:
> On Sun, 20 Aug 2017 08:26:49 -0600, Alec Ten Harmsel wrote:
>
>> I don't believe that will be enough. You should update RUBY_TARGETS in
>> /etc/portage/make.conf if you have it set. If you don't have it set and
>> are still getting this error, that's a
On Sun, 20 Aug 2017 08:26:49 -0600, Alec Ten Harmsel wrote:
> I don't believe that will be enough. You should update RUBY_TARGETS in
> /etc/portage/make.conf if you have it set. If you don't have it set and
> are still getting this error, that's a bug and should be filed on b.g.o.
> I have a custo
11 matches
Mail list logo