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