| 1 |
On Fri, 2009-08-28 at 11:18 +0200, Fabian Groffen wrote: |
| 2 |
> On 28-08-2009 10:08:11 +0100, Alan Hourihane wrote: |
| 3 |
> > > I guess the problem is more why it wants to remove that /usr. Maybe |
| 4 |
> > > because of the same problem we once had during install, where paths |
| 5 |
> > > "below" the offset prefix shouldn't be taken into account at all, |
| 6 |
> > > because you should not do anything there, and may not even be able to do |
| 7 |
> > > so. |
| 8 |
> > |
| 9 |
> > All you need to do is look at the CONTENTS file which as something like |
| 10 |
> > this... |
| 11 |
> > |
| 12 |
> > dir /usr |
| 13 |
> > dir /usr/bin |
| 14 |
> > obj /usr/bin/comm 4e28628520359733270907c62c738b3f 1250795126 |
| 15 |
> > obj /usr/bin/arch 59d8b1d83cfbc020751c8febc4706901 1250795126 |
| 16 |
> > obj /usr/bin/factor a68ac36164e0ac5c1245e358e688942e 1250795126 |
| 17 |
> > |
| 18 |
> > Look at the first line.... Enough said... |
| 19 |
> |
| 20 |
> right, but your prefix is '/', so that makes sense. |
| 21 |
|
| 22 |
Right, normally the "rmdir" would fail because there are files still in |
| 23 |
existance in those directories. But with a symlink that doesn't hold |
| 24 |
true. |
| 25 |
|
| 26 |
> the "fix" is most probably that portage shouldn't remove a symlink if it |
| 27 |
> expects a dir. Put differently, portage should ensure that it only |
| 28 |
> unmerges what it expects. Would that theory work? |
| 29 |
|
| 30 |
I'm worried about something like this.... |
| 31 |
|
| 32 |
dir /usr/share/mypackage |
| 33 |
dir /usr/share/mypackage/test |
| 34 |
dir /usr/share/mypackage/symlink-to-test |
| 35 |
|
| 36 |
Where "symlink-to-test" points to "test" and should be removed. Then |
| 37 |
removal of "mypackage" might fail because the symlink would still exist. |
| 38 |
|
| 39 |
Alan. |
Archives