On Tuesday, August 25, 2020 2:23:57 A.M. AEST Grant Edwards wrote:
> On 2020-08-24, Franz Fellner wrote:
> > On Mo 24 Aug 2020 11:21:10 +0200, Hogren wrote:
> >> Maybe try to :
> >>
> >> - Unmerge all python and python-setuptools versions
> >
> > No, don't do that!!!
> > Unmerging all python ve
On 2020-08-24, Thomas Mueller wrote:
>> >> - Unmerge all python and python-setuptools versions
>
>> > No, don't do that!!!
>> > Unmerging all python version will leave you with a non-working portage.
>
>> Indeed -- I've done that. It's not fun. You certainly won't do it a
>> second time.
On 2020-08-24 17:24, Thomas Mueller wrote:
>
> How did you recover? You couldn't even use setup.py at that stage.
>
> Did you have to download the python distfile if you didn't have it
> already, and build using configure and make directly?
You can find someone you trust with the same architect
On Mon, Aug 24, 2020 at 9:48 AM Michael wrote:
>
> On Monday, 24 August 2020 13:02:56 BST Rich Freeman wrote:
> I may give virt-manager a spin, because the users will require a GUI manager
> to launch VMs, but then if I start emerging packages at large I could emerge
> VBox from source instead. O
> >> - Unmerge all python and python-setuptools versions
> > No, don't do that!!!
> > Unmerging all python version will leave you with a non-working portage.
> Indeed -- I've done that. It's not fun. You certainly won't do it a
> second time.
> Grant
How did you recover? You c
On 2020-08-24, Franz Fellner wrote:
> On Mo 24 Aug 2020 11:21:10 +0200, Hogren wrote:
>> Maybe try to :
>>
>> - Unmerge all python and python-setuptools versions
>
> No, don't do that!!!
> Unmerging all python version will leave you with a non-working portage.
Indeed -- I've done that. It's no
Thank you all for your responses.
On Monday, 24 August 2020 13:02:56 BST Rich Freeman wrote:
> On Mon, Aug 24, 2020 at 6:57 AM Neil Bothwick wrote:
> > On Mon, 24 Aug 2020 11:50:42 +0100, Michael wrote:
> > > I have a number of VBox VM systems, some with active software licenses
> > > running on
On Mon, 24 Aug 2020 12:24:26 +0100, Michael wrote:
> > > I have a number of VBox VM systems, some with active software
> > > licenses running on them and the VBox-bin is a low-maintenance and
> > > convenient way to run them. I'd prefer to avoid emerging a non-bin
> > > VBox. Is there some way I
On Sat, Aug 22, 2020 at 09:17:56PM +0100, Ashley Dixon wrote:
> On Sat, Aug 22, 2020 at 04:15:38AM +, Caveman Al Toraboran wrote:
> > just to double check i got you right. due to
> > flushing the buffer to disk, this would mean that
> > mail's throughput is limited by disk i/o?
[...]
> When an
On Mon, Aug 24, 2020 at 6:57 AM Neil Bothwick wrote:
>
> On Mon, 24 Aug 2020 11:50:42 +0100, Michael wrote:
>
> > !!! The following installed packages are masked:
> > - app-emulation/virtualbox-bin-5.2.40.137108::gentoo (masked by:
> > package.mask) /usr/portage/profiles/package.mask:
> > # Michał
On Mon 24 Aug 2020 12:24:26 GMT, Michael wrote:
> Thanks Neil, will this keep all requisite build and run time dependencies, or
> will they have to be added to package.unmask too?
You will have to do the same for all the packages you want to keep (no
matter if it’s a dep or a manually emerged on
On Monday, 24 August 2020 11:57:02 BST Neil Bothwick wrote:
> On Mon, 24 Aug 2020 11:50:42 +0100, Michael wrote:
> > !!! The following installed packages are masked:
> > - app-emulation/virtualbox-bin-5.2.40.137108::gentoo (masked by:
> > package.mask) /usr/portage/profiles/package.mask:
> > # Mich
On Mon, 24 Aug 2020 11:50:42 +0100, Michael wrote:
> !!! The following installed packages are masked:
> - app-emulation/virtualbox-bin-5.2.40.137108::gentoo (masked by:
> package.mask) /usr/portage/profiles/package.mask:
> # Michał Górny (2020-08-22)
> # These packages (or package versions) still
As python-2.7 was EOL'ed I find some packages are being retired and have/will
fall off the tree; e.g. app-office/taskcoach. I keep a version of taskcoach
running in a VM in the hope the devs/maintainer will come up with a version
updated to run on later python releases. Then I see this:
=
Sorry sorry sorry…
Franz is right...
Do not uninstall all python versions !
Hogren
On 24/08/2020 11:39, Franz Fellner wrote:
On Mo 24 Aug 2020 11:21:10 +0200, Hogren wrote:
Maybe try to :
- Unmerge all python and python-setuptools versions
No, don't do that!!!
Unmerging all python versio
On Mo 24 Aug 2020 11:21:10 +0200, Hogren wrote:
> Maybe try to :
>
> - Unmerge all python and python-setuptools versions
No, don't do that!!!
Unmerging all python version will leave you with a non-working portage.
portage is written in python.
You can fix that but it requires some manual interve
Hi,
In your logs, I saw that python 3.7 is executed.
And you wrote that python 3.6 is selected.
I had many problem with the python transition too. I have no simple
solution. I uninstalled many things for reinstall after.
Maybe try to :
- Unmerge all python and python-setuptools versions
-
17 matches
Mail list logo
