1 |
On Sun, Dec 23, 2001 at 05:24:10PM -0700 or thereabouts, Collins Richey wrote: |
2 |
> after emerge rsync, I did an emerge sys-apps/portage, expecting |
3 |
> portage-1.8.0 per the changelog, but got portage-1.9.0_pre1 instead. |
4 |
> |
5 |
> emerge was ok, but when I tried to unmerge the previous portage, I got |
6 |
> the following |
7 |
> |
8 |
> root@g2r61 portage # cd /var/db/pkg/sys-apps/portage-1.7.7/ |
9 |
> root@g2r61 portage-1.7.7 # ebuild portage-1.7.7.ebuild unmerge |
10 |
> Traceback (most recent call last): |
11 |
> File "/usr/sbin/ebuild", line 35, in ? |
12 |
> a=portage.doebuild(pargs[0],x,getroot(),debug=debug) |
13 |
> File "/usr/lib/python2.0/site-packages/portage.py", line 718, in |
14 |
> doebuild a=open(settings["T"]+"/src_uri_new","w") |
15 |
> IOError: [Errno 13] Permission denied: |
16 |
> '/var/tmp/portage/portage-1.7.7/temp/src_uri_new' |
17 |
|
18 |
Try doing ebuild --stayroot portage-1.7.7.ebuild unmerge |
19 |
|
20 |
If you see chousers last email to the list there is a short mention about this new version of portage however he said it was masked, seems that's not the case. |
21 |
|
22 |
Regards, |
23 |
|
24 |
-- |
25 |
Joshua Pierre |
26 |
Developer & Release Technician |
27 |
Themes.Org -- Open Source Interface Enhancement |