[gentoo-dev] pkg_postinst errors portage 1.5.3

[gentoo-dev] pkg_postinst errors portage 1.5.3

[Gontran]

Dear luvahs,

Upgrading portage to 1.5.3 from generic rc5 install, received some error
messages during pkg_postinst:

+ pkg_postinst
+ '[' '!' -e //etc/make.profile ']'
+ local x
+ '[' -e //usr/lib/python2.0/portage.py ']'
+ //usr/lib/python2.0/portage.py //usr/lib/python2.0/portage.py.bak
/usr/sbin/ebuild.sh: //usr/lib/python2.0/portage.py: Permission denied
+ rm -f //usr/lib/python2.0/portage.pyc
+ '[' -e //usr/lib/python2.0/xpak.py ']'
+ //usr/lib/python2.0/xpak.py //usr/lib/python2.0/xpak.py.bak
/usr/sbin/ebuild.sh: //usr/lib/python2.0/xpak.py: Permission denied
+ rm -f //usr/lib/python2.0/xpak.pyc
+ set +x
>>> Regenerating /etc/ld.so.cache...
>>> sys-apps/portage-1.5.3 merged.

I remember something about the '+' lines are just reminders to developers,
but I'm concerned about the 'Permission denied' messages.

I'm wondering if it's safe to use emerge to update some packages per ChadH's
info fixes.

Rgds,
Gontran

Re: [gentoo-dev] pkg_postinst errors portage 1.5.3

[Daniel Robbins]

On Sun, Aug 05, 2001 at 11:27:45AM -0700, Gontran wrote:

> Upgrading portage to 1.5.3 from generic rc5 install, received some error
> messages during pkg_postinst:
> 
> + pkg_postinst
> + '[' '!' -e //etc/make.profile ']'
> + local x
> + '[' -e //usr/lib/python2.0/portage.py ']'
> + //usr/lib/python2.0/portage.py //usr/lib/python2.0/portage.py.bak
> /usr/sbin/ebuild.sh: //usr/lib/python2.0/portage.py: Permission denied
> + rm -f //usr/lib/python2.0/portage.pyc
> + '[' -e //usr/lib/python2.0/xpak.py ']'
> + //usr/lib/python2.0/xpak.py //usr/lib/python2.0/xpak.py.bak
> /usr/sbin/ebuild.sh: //usr/lib/python2.0/xpak.py: Permission denied
> + rm -f //usr/lib/python2.0/xpak.pyc
> + set +x
> >>> Regenerating /etc/ld.so.cache...
> >>> sys-apps/portage-1.5.3 merged.
> 
> I remember something about the '+' lines are just reminders to developers,
> but I'm concerned about the 'Permission denied' messages.

The permission denied message is a problem related to those files being
busy.  

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] pkg_postinst errors portage 1.5.3

[Daniel Robbins]

On Sun, Aug 05, 2001 at 01:00:07PM -0600, Daniel Robbins wrote:

> The permission denied message is a problem related to those files being
> busy.  

Um; this is now fixed on CVS.  Everyone should remerge the new portage-1.5.3;
if for some reason Portage doesn't run, then make sure you have portage.py and
xpak.py in /usr/lib/python2.0/site-packages.  If so, then zap the portage.py(c)
and xpak.py(c) files in /usr/lib/python2.0/, which is the old location.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] pkg_postinst errors portage 1.5.3

[Gontran]

* Daniel Robbins (drobbins@gentoo.org) wrote:
> On Sun, Aug 05, 2001 at 01:00:07PM -0600, Daniel Robbins wrote:
> 
> > The permission denied message is a problem related to those files being
> > busy.  
> 
> Um; this is now fixed on CVS.  Everyone should remerge the new portage-1.5.3;
> if for some reason Portage doesn't run, then make sure you have portage.py and
> xpak.py in /usr/lib/python2.0/site-packages.  If so, then zap the portage.py(c)
> and xpak.py(c) files in /usr/lib/python2.0/, which is the old location.
> 

I got the new portage from 12:08 MST with 

> emerge rsync 

but ...

> cd /usr/portage/sys-apps/portage
> emerge portage-1.5.3.ebuild
Calculating dependencies.Traceback (most recent call last):
  File "/usr/sbin/emerge", line 436, in ?
    mydepgraph.create(mytype+" "+portage.root+" "+mykey)
  File "/usr/sbin/emerge", line 55, in create
    edepend=portage.doebuild(myebuild,"depend",1,edebug)
TypeError: too many arguments; expected 3, got 4


Rgds,
Gontran

Re: [gentoo-dev] pkg_postinst errors portage 1.5.3

[Daniel Robbins]

On Sun, Aug 05, 2001 at 12:27:40PM -0700, Gontran wrote:
> * Daniel Robbins (drobbins@gentoo.org) wrote:
> > On Sun, Aug 05, 2001 at 01:00:07PM -0600, Daniel Robbins wrote:
> > 
> > > The permission denied message is a problem related to those files being
> > > busy.  
> > 
> > Um; this is now fixed on CVS.  Everyone should remerge the new portage-1.5.3;
> > if for some reason Portage doesn't run, then make sure you have portage.py and
> > xpak.py in /usr/lib/python2.0/site-packages.  If so, then zap the portage.py(c)
> > and xpak.py(c) files in /usr/lib/python2.0/, which is the old location.
> > 
> 
> I got the new portage from 12:08 MST with 
> 
> > emerge rsync 
> 
> but ...
> 
> > cd /usr/portage/sys-apps/portage
> > emerge portage-1.5.3.ebuild
> Calculating dependencies.Traceback (most recent call last):
>   File "/usr/sbin/emerge", line 436, in ?
>     mydepgraph.create(mytype+" "+portage.root+" "+mykey)
>   File "/usr/sbin/emerge", line 55, in create
>     edepend=portage.doebuild(myebuild,"depend",1,edebug)
> TypeError: too many arguments; expected 3, got 4

Yes; as I explained, you need to delete the old portage.py and xpak.py in
/usr/lib/python2.0 for Portage to work again.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] pkg_postinst errors portage 1.5.3

[Gontran]

* Daniel Robbins (drobbins@gentoo.org) wrote:
> On Sun, Aug 05, 2001 at 12:27:40PM -0700, Gontran wrote:
> > * Daniel Robbins (drobbins@gentoo.org) wrote:
> > > On Sun, Aug 05, 2001 at 01:00:07PM -0600, Daniel Robbins wrote:
> > > 
> > > > The permission denied message is a problem related to those files being
> > > > busy.  
> > > 
> > > Um; this is now fixed on CVS.  Everyone should remerge the new portage-1.5.3;
> > > if for some reason Portage doesn't run, then make sure you have portage.py and
> > > xpak.py in /usr/lib/python2.0/site-packages.  If so, then zap the portage.py(c)
> > > and xpak.py(c) files in /usr/lib/python2.0/, which is the old location.
> > > 
> > 
> > I got the new portage from 12:08 MST with 
> > 
> > > emerge rsync 
> > 
> > but ...
> > 
> > > cd /usr/portage/sys-apps/portage
> > > emerge portage-1.5.3.ebuild
> > Calculating dependencies.Traceback (most recent call last):
> >   File "/usr/sbin/emerge", line 436, in ?
> >     mydepgraph.create(mytype+" "+portage.root+" "+mykey)
> >   File "/usr/sbin/emerge", line 55, in create
> >     edepend=portage.doebuild(myebuild,"depend",1,edebug)
> > TypeError: too many arguments; expected 3, got 4
> 
> Yes; as I explained, you need to delete the old portage.py and xpak.py in
> /usr/lib/python2.0 for Portage to work again.

Right there.  I can't seem to follow directions at times, and hadn't yet
removed those two files from /usr/lib/python2.0, so I did the following:

gogo portage > rm /usr/lib/python2.0/portage.py
gogo portage > rm /usr/lib/python2.0/xpak.py   
gogo portage > emerge portage-1.5.3.ebuild 
Calculating dependencies.Traceback (most recent call last):
  File "/usr/sbin/emerge", line 436, in ?
    mydepgraph.create(mytype+" "+portage.root+" "+mykey)
  File "/usr/sbin/emerge", line 55, in create
    edepend=portage.doebuild(myebuild,"depend",1,edebug)
TypeError: too many arguments; expected 3, got 4
gogo portage > ls /usr/lib/python2.0/site-packages/
README  portage.py  portage.pyc  portage.pyo  xpak.py  xpak.pyc  xpak.pyo
gogo portage > 


Sorry for the hassle.

At your service,
Gontran

Re: [gentoo-dev] pkg_postinst errors portage 1.5.3

[Collins Richey]

On Sun, 5 Aug 2001 14:18:01 -0600 Daniel Robbins <drobbins@gentoo.org>
wrote:

> On Sun, Aug 05, 2001 at 12:27:40PM -0700, Gontran wrote:
> > * Daniel Robbins (drobbins@gentoo.org) wrote:
> > > On Sun, Aug 05, 2001 at 01:00:07PM -0600, Daniel Robbins wrote:
> > > 
> > > > The permission denied message is a problem related to those files
> being
> > > > busy.  
> > > 
> > > Um; this is now fixed on CVS.  Everyone should remerge the new
> portage-1.5.3;
> > > if for some reason Portage doesn't run, then make sure you have
> portage.py and
> > > xpak.py in /usr/lib/python2.0/site-packages.  If so, then zap the
> portage.py(c)
> > > and xpak.py(c) files in /usr/lib/python2.0/, which is the old
> location.
> > > 
> > 
> > I got the new portage from 12:08 MST with 
> > 
> > > emerge rsync 
> > 
> > but ...
> > 
> > > cd /usr/portage/sys-apps/portage
> > > emerge portage-1.5.3.ebuild
> > Calculating dependencies.Traceback (most recent call last):
> >   File "/usr/sbin/emerge", line 436, in ?
> >     mydepgraph.create(mytype+" "+portage.root+" "+mykey)
> >   File "/usr/sbin/emerge", line 55, in create
> >     edepend=portage.doebuild(myebuild,"depend",1,edebug)
> > TypeError: too many arguments; expected 3, got 4
> 
> Yes; as I explained, you need to delete the old portage.py and xpak.py
> in
> /usr/lib/python2.0 for Portage to work again.
> 
> Best Regards,
> 

Is that "delete them" before or after merging portage 1.5.3?


-- 
Collins Richey
Denver Area
Gentoo_rc5 XFCE

Re: [gentoo-dev] pkg_postinst errors portage 1.5.3

[Daniel Robbins]

On Sun, Aug 05, 2001 at 02:50:13PM +0000, Collins Richey wrote:

> Is that "delete them" before or after merging portage 1.5.3?

After.  If you've already merge Portage 1.5.3 and messed up Portage, rm them
before.

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.