[gentoo-dev] Latest portage

[gentoo-dev] Latest portage

[Collins Richey]

after emerge rsync, I did an emerge sys-apps/portage, expecting
portage-1.8.0 per the changelog, but got  portage-1.9.0_pre1 instead.

emerge was ok, but when I tried to unmerge the previous portage, I got
the following

root@g2r61 portage # cd /var/db/pkg/sys-apps/portage-1.7.7/
root@g2r61 portage-1.7.7 # ebuild portage-1.7.7.ebuild unmerge
Traceback (most recent call last):
  File "/usr/sbin/ebuild", line 35, in ?
    a=portage.doebuild(pargs[0],x,getroot(),debug=debug)
  File "/usr/lib/python2.0/site-packages/portage.py", line 718, in
doebuild    a=open(settings["T"]+"/src_uri_new","w")
IOError: [Errno 13] Permission denied:
'/var/tmp/portage/portage-1.7.7/temp/src_uri_new'


-- 
Collins Richey
Denver Area - 22DEC2001 - WWTLRD?
gentoo_rc6 k2.4.17+ext3+xfce+sylpheed+galeon

Re: [gentoo-dev] Latest portage

[Joshua Pierre]

On Sun, Dec 23, 2001 at 05:24:10PM -0700 or thereabouts, Collins Richey wrote:
> after emerge rsync, I did an emerge sys-apps/portage, expecting
> portage-1.8.0 per the changelog, but got  portage-1.9.0_pre1 instead.
> 
> emerge was ok, but when I tried to unmerge the previous portage, I got
> the following
> 
> root@g2r61 portage # cd /var/db/pkg/sys-apps/portage-1.7.7/
> root@g2r61 portage-1.7.7 # ebuild portage-1.7.7.ebuild unmerge
> Traceback (most recent call last):
>   File "/usr/sbin/ebuild", line 35, in ?
>     a=portage.doebuild(pargs[0],x,getroot(),debug=debug)
>   File "/usr/lib/python2.0/site-packages/portage.py", line 718, in
> doebuild    a=open(settings["T"]+"/src_uri_new","w")
> IOError: [Errno 13] Permission denied:
> '/var/tmp/portage/portage-1.7.7/temp/src_uri_new'

Try doing ebuild --stayroot  portage-1.7.7.ebuild unmerge

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.

Regards,

-- 
Joshua Pierre
Developer & Release Technician
Themes.Org -- Open Source Interface Enhancement

Re: [gentoo-dev] Latest portage

[Chris Houser]

Joshua Pierre wrote:                  [Sun Dec 23 2001,  7:26:22PM EST]         
> 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.

Right-o.  I forgot to commit.  Sorry all, should be fixed in cvs now, in
rsync soon.  Thanks for the catch.

> On Sun, Dec 23, 2001 at 05:24:10PM -0700 or thereabouts, Collins Richey wrote:
> > after emerge rsync, I did an emerge sys-apps/portage, expecting
> > portage-1.8.0 per the changelog, but got  portage-1.9.0_pre1 instead.
> > 
> > emerge was ok, but when I tried to unmerge the previous portage, I got
> > the following
> > 
> > root@g2r61 portage # cd /var/db/pkg/sys-apps/portage-1.7.7/
> > root@g2r61 portage-1.7.7 # ebuild portage-1.7.7.ebuild unmerge
> > Traceback (most recent call last):
> >   File "/usr/sbin/ebuild", line 35, in ?
> >     a=portage.doebuild(pargs[0],x,getroot(),debug=debug)
> >   File "/usr/lib/python2.0/site-packages/portage.py", line 718, in
> > doebuild    a=open(settings["T"]+"/src_uri_new","w")
> > IOError: [Errno 13] Permission denied:
> > '/var/tmp/portage/portage-1.7.7/temp/src_uri_new'
> 
> Try doing ebuild --stayroot  portage-1.7.7.ebuild unmerge

That should work, but chowning all of /var/tmp/portage to be read/writable
by normal users would be the 'preferred' solution.

--Chouser