| 1 |
On Tue, Jan 02, 2018 at 11:14:24AM -0700, thelma@×××××××××××.com wrote: |
| 2 |
> On 01/02/2018 11:01 AM, Mick wrote: |
| 3 |
> > |
| 4 |
> > This is a coincidence. Something *else* must have happened because untarring |
| 5 |
> > the brother archives did not interfere in any way with your @system packages. |
| 6 |
> > |
| 7 |
> > Did you move to the 17.1 amd64 profile as per portage news item '2017-12-26- |
| 8 |
> > experimental-amd64-17-1-profiles' and partly messed up the removal of the |
| 9 |
> > symlink to /lib64? |
| 10 |
> |
| 11 |
> No, I did not touch any of that staff |
| 12 |
> |
| 13 |
> There should be al lot of packages in: /usr/lib |
| 14 |
> but my dir is almost empty only one file left: |
| 15 |
> |
| 16 |
> -rwxr-xr-x 1 root root 53606 Sep 18 2008 libbrcomplpr2.so |
| 17 |
> |
| 18 |
> I think I have to bootstrap the system and start by unzipping untar the |
| 19 |
> stage-3 file. |
| 20 |
> How to untar it so to only replace missing files. |
| 21 |
> |
| 22 |
> -- |
| 23 |
> Joseph |
| 24 |
|
| 25 |
Had the same happen to me when i created a kernel `make tar-pkg` and then |
| 26 |
untarred it with `tar -C`. What happens is ./lib or ./usr/lib in the |
| 27 |
tarball are directories, but on a normal gentoo amd64 system (not 17.1) |
| 28 |
they are symlinks to lib64 and usr/lib64. The symlink gets removed, an |
| 29 |
empty directory created and filled with the tarball contents and that's |
| 30 |
what you have. |
| 31 |
|
| 32 |
Do |
| 33 |
|
| 34 |
# mv /usr/lib/* /usr/lib64/ |
| 35 |
# rm -rf /usr/lib/ |
| 36 |
# ln -s lib64 /usr/lib |
| 37 |
|
| 38 |
and your system should be back. |
| 39 |
|
| 40 |
Also, once you figure out what the problem is/was (empty /usr/lib), naturally |
| 41 |
you'll google for 'tar don't overwrite symlinks' or something of the sort. |
| 42 |
I'll save you the time: you want 'tar -h' when extracting. |
Archives