W dniu sob, 16.12.2017 o godzinie 16∶48 +1300, użytkownik Kent Fredric
napisał:
> On Fri, 15 Dec 2017 21:09:15 +0100
> Michał Górny wrote:
>
> > Sounds like you've put some awful self-symlink into this directory.
> > The script incorrectly follows top-level symlinks when
On Fri, 15 Dec 2017 21:09:15 +0100
Michał Górny wrote:
> Sounds like you've put some awful self-symlink into this directory.
> The script incorrectly follows top-level symlinks when removing, I'll
> fix that.
If it helps, this is on a no-multilib install, and the tree if I
W dniu pią, 15.12.2017 o godzinie 22∶24 +1300, użytkownik Kent Fredric
napisał:
> On Sat, 09 Dec 2017 11:26:36 +0100
> Michał Górny wrote:
>
> I ran this on a chroot.
>
> > 5. Run 'unsymlink-lib --migrate'.
> >
> > 6. Reboot your system and see if it still boots, possibly
On Sat, 09 Dec 2017 11:26:36 +0100
Michał Górny wrote:
I ran this on a chroot.
> 5. Run 'unsymlink-lib --migrate'.
>
> 6. Reboot your system and see if it still boots, possibly test if
> important programs work. Also check if emerge starts but don't install
> anything. If
Le 09 décembre à 11:26 Michał Górny a écrit
> Hi, everyone.
>
> I've pushed a commented out set of 17.1 profiles for amd64 that feature
> the long-overdue SYMLINK_LIB=no setup. I'd really appreciate some real
> testing.
>
> Warning: there is a slight risk of breaking your system, in particular
>
Dnia 11 grudnia 2017 14:21:30 CET, Xavier Miller
napisał(a):
>Le 2017-12-11 08:25, Xavier Miller a écrit :
>> Le 2017-12-10 23:24, Michał Górny a écrit :
>>> I suspect you mean python-exec scripts, because Python modules still
>>> land in /usr/lib64. In which case,
Le 2017-12-11 08:25, Xavier Miller a écrit :
Le 2017-12-10 23:24, Michał Górny a écrit :
I suspect you mean python-exec scripts, because Python modules still
land in /usr/lib64. In which case, everything's fine.
Could be.
Glad to hear the migration is OK.
My systems are migrated, and
OK thanks.
Have a nice day,
Xavier.
Le 2017-12-11 08:59, Michał Górny a écrit :
Dnia 11 grudnia 2017 08:25:22 CET, Xavier Miller
napisał(a):
Le 2017-12-10 23:24, Michał Górny a écrit :
I suspect you mean python-exec scripts, because Python modules still
land in
Dnia 11 grudnia 2017 08:25:22 CET, Xavier Miller
napisał(a):
>Le 2017-12-10 23:24, Michał Górny a écrit :
>> I suspect you mean python-exec scripts, because Python modules still
>> land in /usr/lib64. In which case, everything's fine.
>
>Could be.
>
>Glad to hear the
Le 2017-12-10 23:24, Michał Górny a écrit :
I suspect you mean python-exec scripts, because Python modules still
land in /usr/lib64. In which case, everything's fine.
Could be.
Glad to hear the migration is OK.
My systems are migrated, and stable.
Just a last dummy question : why is lib64
W dniu nie, 10.12.2017 o godzinie 22∶30 +0100, użytkownik Xavier Miller
napisał:
>
> Le 10/12/17 à 22:26, Xavier Miller a écrit :
> > Hi,
> >
> > Le 10/12/17 à 22:13, Mike Gilbert a écrit :
> > > On Sun, Dec 10, 2017 at 3:33 PM, Michał Górny
> > > wrote:
> > > > > And the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Le 10/12/17 à 22:26, Xavier Miller a écrit :
> Hi,
>
> Le 10/12/17 à 22:13, Mike Gilbert a écrit :
>> On Sun, Dec 10, 2017 at 3:33 PM, Michał Górny
>> wrote:
And the list of other ebuilds (cd /var/db/pkg ; grep -l
Hi,
Le 10/12/17 à 22:13, Mike Gilbert a écrit :
> On Sun, Dec 10, 2017 at 3:33 PM, Michał Górny wrote:
>>> And the list of other ebuilds (cd /var/db/pkg ; grep -l '/lib/'
>>> */*/CONTENTS)
...
...
>>
>> I would need more specific details (some example files at least) but
>>
On Sun, Dec 10, 2017 at 3:33 PM, Michał Górny wrote:
> W dniu nie, 10.12.2017 o godzinie 14∶56 +0100, użytkownik Xavier Miller
> napisał:
>> Hi,
>>
>> I did emerge -e @world on a no-multilib chroot, and I have a lot of
>> ebuilds that install libs on /{,usr/}/lib/ in place of
W dniu nie, 10.12.2017 o godzinie 14∶56 +0100, użytkownik Xavier Miller
napisał:
> Hi,
>
> I did emerge -e @world on a no-multilib chroot, and I have a lot of
> ebuilds that install libs on /{,usr/}/lib/ in place of lib64
>
> First are kernel-related ebuilds:
> - kernel's make install
> -
Hi,
I did emerge -e @world on a no-multilib chroot, and I have a lot of
ebuilds that install libs on /{,usr/}/lib/ in place of lib64
First are kernel-related ebuilds:
- kernel's make install
- linux-firmware
And the list of other ebuilds (cd /var/db/pkg ; grep -l '/lib/'
*/*/CONTENTS)
On 10/12/2017 11:45, Michał Górny wrote:
> Indeed it seems to dislike lib32 symlink. I'll try to fix that.
> In the meantime, you can skip baselayout for now and return to it once
> all multilib packages are rebuilt (and lib32 is gone).
>
The rest worked fine. At the end also baselayout behave
W dniu nie, 10.12.2017 o godzinie 10∶59 +, użytkownik Justin Lecher
napisał:
> Hi
>
> Is the baselayout ready for this? I get following error
>
> * You need to merge /lib32 into /lib
> * ERROR: sys-apps/baselayout-2.4.1-r2::gentoo failed (setup phase):
> * non-empty dir found where
Hi
Is the baselayout ready for this? I get following error
* You need to merge /lib32 into /lib
* ERROR: sys-apps/baselayout-2.4.1-r2::gentoo failed (setup phase):
* non-empty dir found where there should be none: /lib32
Which hints that the baselayout might not be happy with this setup?
Le 09/12/17 à 22:00, Michał Górny a écrit :
> W dniu sob, 09.12.2017 o godzinie 21∶47 +0100, użytkownik Xavier Miller
> napisał:
>>
>> Tool doesn't work with no-multilib profiles:
>
> Are you using the old version? Version 2 was fixed to support no-
> multilib, and you certainly should update
On 12/09/2017 04:00 PM, Michał Górny wrote:
>
> rm -r /lib.{old,new} /usr/lib.{old,new}
>
It probably won't hurt anything, but that should be run in BASH.
W dniu sob, 09.12.2017 o godzinie 21∶47 +0100, użytkownik Xavier Miller
napisał:
>
> Le 09/12/17 à 11:26, Michał Górny a écrit :
> > Hi, everyone.
> >
> > I've pushed a commented out set of 17.1 profiles for amd64 that feature
> > the long-overdue SYMLINK_LIB=no setup. I'd really appreciate some
Le 09/12/17 à 11:26, Michał Górny a écrit :
> Hi, everyone.
>
> I've pushed a commented out set of 17.1 profiles for amd64 that feature
> the long-overdue SYMLINK_LIB=no setup. I'd really appreciate some real
> testing.
>
> Warning: there is a slight risk of breaking your system, in particular
Hi, everyone.
I've pushed a commented out set of 17.1 profiles for amd64 that feature
the long-overdue SYMLINK_LIB=no setup. I'd really appreciate some real
testing.
Warning: there is a slight risk of breaking your system, in particular
multilib libraries and/or programs.
To switch to the new
24 matches
Mail list logo