| 1 |
On Wed, 10 Aug 2016 17:26:02 -0400, covici@××××××××××.com wrote: |
| 2 |
|
| 3 |
> I would like to know the correct way to emerge a tbz2 file where I |
| 4 |
> wanted to go back to a version which worked and I had used a .9999 |
| 5 |
> package, so I could not do it in .git (let me know if there is a way to |
| 6 |
> go back to a commit). What I did was to go to / and extract the |
| 7 |
> archive, but that totally hosed my system, because the /usr/lib which is |
| 8 |
> normally a link to /usr/lib64 was replace with a directory and so I was |
| 9 |
> getting lots of libraries which could not be found although they were |
| 10 |
> there. After discovering this and rebooting, etc. I solved the problem |
| 11 |
> by extracting to a temp directory and making sure bad things didn't |
| 12 |
> happen. Now I can watch, but is there a correct way to do this? |
| 13 |
|
| 14 |
I had exactly the same problem with /lib being overwritten when I |
| 15 |
unpacked a tbz into /, it took a while to work out what was wrong. |
| 16 |
|
| 17 |
Although it gives warnings, emerge -1a /path/to/pkg.tbz usually works. |
| 18 |
|
| 19 |
|
| 20 |
-- |
| 21 |
Neil Bothwick |
| 22 |
|
| 23 |
I get enough exercise just pushing my luck. |
Archives