1 |
Joshua Pierre wrote: [Sun Dec 23 2001, 7:26:22PM EST] |
2 |
> If you see chousers last email to the list there is a short mention |
3 |
> about this new version of portage however he said it was masked, seems |
4 |
> that's not the case. |
5 |
|
6 |
Right-o. I forgot to commit. Sorry all, should be fixed in cvs now, in |
7 |
rsync soon. Thanks for the catch. |
8 |
|
9 |
> On Sun, Dec 23, 2001 at 05:24:10PM -0700 or thereabouts, Collins Richey wrote: |
10 |
> > after emerge rsync, I did an emerge sys-apps/portage, expecting |
11 |
> > portage-1.8.0 per the changelog, but got portage-1.9.0_pre1 instead. |
12 |
> > |
13 |
> > emerge was ok, but when I tried to unmerge the previous portage, I got |
14 |
> > the following |
15 |
> > |
16 |
> > root@g2r61 portage # cd /var/db/pkg/sys-apps/portage-1.7.7/ |
17 |
> > root@g2r61 portage-1.7.7 # ebuild portage-1.7.7.ebuild unmerge |
18 |
> > Traceback (most recent call last): |
19 |
> > File "/usr/sbin/ebuild", line 35, in ? |
20 |
> > a=portage.doebuild(pargs[0],x,getroot(),debug=debug) |
21 |
> > File "/usr/lib/python2.0/site-packages/portage.py", line 718, in |
22 |
> > doebuild a=open(settings["T"]+"/src_uri_new","w") |
23 |
> > IOError: [Errno 13] Permission denied: |
24 |
> > '/var/tmp/portage/portage-1.7.7/temp/src_uri_new' |
25 |
> |
26 |
> Try doing ebuild --stayroot portage-1.7.7.ebuild unmerge |
27 |
|
28 |
That should work, but chowning all of /var/tmp/portage to be read/writable |
29 |
by normal users would be the 'preferred' solution. |
30 |
|
31 |
--Chouser |