On Mon, 7 Dec 2020 18:40:24 +, antlists wrote:
> > I don't think the --oneshot is doing anything here. It just prevents
> > adding an atom to the world file when emerging. Besides, in this
> > case, you do want it removed (if it was there) because, as you say,
> > it will just get pulled
On Mon, 7 Dec 2020 18:32:45 - (UTC), Grant Edwards wrote:
> > I agree with this one. I often find emerge fails, telling me the
> > reason, and then once I've fixed that (usually adding a different
> > package or changing some use flags) it fails in exactly the same way
> > for a
On 07/12/2020 18:21, Jack wrote:
I do an emerge -C --oneshot to uninstall those packages. That way,
when emerge finally starts to update world, it pulls them all back (at
least, the ones that are needed) itself without me needing to worry
about it.
I don't think the --oneshot is doing
On 2020-12-07, Jack wrote:
> I agree with this one. I often find emerge fails, telling me the
> reason, and then once I've fixed that (usually adding a different
> package or changing some use flags) it fails in exactly the same way
> for a different package.
Oh yes, on a bad day you can
On 2020.12.07 13:14, antlists wrote:
On 07/12/2020 14:30, Grant Edwards wrote:
I ended up uninstalling packages mentioned in those 150 lines 2-3 at
a
time and until emerge was willing to update world.
After that I guess I start trying to re-install what was removed.
I do an emerge -C
On 07/12/2020 14:30, Grant Edwards wrote:
I ended up uninstalling packages mentioned in those 150 lines 2-3 at a
time and until emerge was willing to update world.
After that I guess I start trying to re-install what was removed.
I do an emerge -C --oneshot to uninstall those packages. That
On 2020-12-06, Grant Edwards wrote:
> On 2020-12-06, Arve Barsnes wrote:
>
>> If you have not completed the world update yet, all those are probably
>> still installed as 3.7 packages. You could try updating all those to
>> 3.8 only first, if you have not done the world update yet.
>
> I can't
On 2020.12.06 15:50, Grant Edwards wrote:
On 2020-12-06, Arve Barsnes wrote:
> On Sun, 6 Dec 2020 at 21:25, Grant Edwards
wrote:
>> > emerge -cpv python:3.7 will show you what is keeping 3.7
>>
>> Something's wrong.
>>
>> That lists 43 packages. I checked the first few, and none of them
On 2020-12-06, Arve Barsnes wrote:
> On Sun, 6 Dec 2020 at 21:25, Grant Edwards wrote:
>> > emerge -cpv python:3.7 will show you what is keeping 3.7
>>
>> Something's wrong.
>>
>> That lists 43 packages. I checked the first few, and none of them require
>> python 3.7.
>
> If you have not
On 12/6/20 3:25 PM, Grant Edwards wrote:
On 2020-12-06, Neil Bothwick wrote:
On Sun, 6 Dec 2020 20:01:27 - (UTC), Grant Edwards wrote:
I updated one of my systems a day or two ago, and Python 3.7 went away
as expected. Today, I'm updating another system and it is rebuilding
tons of stuff
On Sun, 6 Dec 2020 at 21:25, Grant Edwards wrote:
> > emerge -cpv python:3.7 will show you what is keeping 3.7
>
> Something's wrong.
>
> That lists 43 packages. I checked the first few, and none of them require
> python 3.7.
If you have not completed the world update yet, all those are
On 2020-12-06, Neil Bothwick wrote:
> On Sun, 6 Dec 2020 20:01:27 - (UTC), Grant Edwards wrote:
>
>> I updated one of my systems a day or two ago, and Python 3.7 went away
>> as expected. Today, I'm updating another system and it is rebuilding
>> tons of stuff to target python 3.8 instead of
12 matches
Mail list logo
