[gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

[gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

[Alan Mackenzie]

Hi, Gentoo.

In my attempt to 'emerge --update --deep xfce4-meta', one sole package
is refusing to build, namely pygtk.

Its log file displays many (perhaps 100) error lines like:

    Could not write method AtkObject.get_attributes: No ArgType for AtkAttributeSet*

.  The command that caused all these errors was:

libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I/usr/include/python2.6 -I/usr/include/python2.6 -pthread -I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I./gtk -I/usr/lib64/python2.6/site-packages/numpy/core/include -pthread -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -O2 -pipe -march=athlon64 -Wall -fno-strict-aliasing -std=c9x -MT pango_la-pangomodule.lo -MD -MP -MF .deps/pango_la-pangomodule.Tpo -c pangomodule.c  -fPIC -DPIC -o .libs/pango_la-pangomodule.o

.  If anybody knows how to fix this, or a more appropriate place to ask
for help, please tell me.

Thanks in advance!

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

[Dale]

Alan Mackenzie wrote:
> Hi, Gentoo.
>
> In my attempt to 'emerge --update --deep xfce4-meta', one sole package
> is refusing to build, namely pygtk.
>
> Its log file displays many (perhaps 100) error lines like:
>
>      Could not write method AtkObject.get_attributes: No ArgType for AtkAttributeSet*
>
> .  The command that caused all these errors was:
>
> libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I/usr/include/python2.6 -I/usr/include/python2.6 -pthread -I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I./gtk -I/usr/lib64/python2.6/site-packages/numpy/core/include -pthread -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -O2 -pipe -march=athlon64 -Wall -fno-strict-aliasing -std=c9x -MT pango_la-pangomodule.lo -MD -MP -MF .deps/pango_la-pangomodule.Tpo -c pangomodule.c  -fPIC -DPIC -o .libs/pango_la-pangomodule.o
>
> .  If anybody knows how to fix this, or a more appropriate place to ask
> for help, please tell me.
>
> Thanks in advance!
>
>    

I did a bit of googling and found some things to try.  Running 
etc-update was one and python-updater was another.  I also saw a mention 
of running fixlibtool but I'm not sure that helped any.

Maybe one of those will help.  Maybe worth trying at least.

Dale

:-)  :-)

Re: [gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

[Alan McKinnon]

Apparently, though unproven, at 20:05 on Friday 22 April 2011, Alan Mackenzie 
did opine thusly:

> Hi, Gentoo.
> 
> In my attempt to 'emerge --update --deep xfce4-meta', one sole package
> is refusing to build, namely pygtk.
> 
> Its log file displays many (perhaps 100) error lines like:
> 
>     Could not write method AtkObject.get_attributes: No ArgType for
> AtkAttributeSet*
> 
> .  The command that caused all these errors was:
> 
> libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I.
> -I/usr/include/python2.6 -I/usr/include/python2.6 -pthread
> -I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -I./gtk
> -I/usr/lib64/python2.6/site-packages/numpy/core/include -pthread
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -O2 -pipe -march=athlon64 -Wall
> -fno-strict-aliasing -std=c9x -MT pango_la-pangomodule.lo -MD -MP -MF
> .deps/pango_la-pangomodule.Tpo -c pangomodule.c  -fPIC -DPIC -o
> .libs/pango_la-pangomodule.o
> 
> .  If anybody knows how to fix this, or a more appropriate place to ask
> for help, please tell me.
> 
> Thanks in advance!

This one might be tricky. Here's a tip: include version numbers of packages 
that are giving trouble, and whether you run stable, testing or (god forbid!) 
a mixture - this can be rather important in guiding one to what to do next (a 
process mostly defined by instinct rather than by say reason)

The error looks like an API break between pygtk and whatever provides 
AtkObject. That is part of the gtk accessibility toolkit, and the relevant 
files come out of a package called atk.

My first guess is that pygtk and atk are now out of sync on your machine. Try 
this:

emerge -av1 atk
emerge -av1 pygtk

Post back if that doesn't work.

Another tip: search bugs.gentoo.org first before posting - oftentimes 
theproblem is already known and reported on. In this specific case however, I 
didn't find anything.


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

[Alan Mackenzie]

Hi, Alan.

On Sat, Apr 23, 2011 at 12:43:45AM +0200, Alan McKinnon wrote:
> Apparently, though unproven, at 20:05 on Friday 22 April 2011, Alan Mackenzie 
> did opine thusly:

> > Hi, Gentoo.

> > In my attempt to 'emerge --update --deep xfce4-meta', one sole
> > package is refusing to build, namely pygtk.

> > Its log file displays many (perhaps 100) error lines like:

> >     Could not write method AtkObject.get_attributes: No ArgType for
> > AtkAttributeSet*

> > .  The command that caused all these errors was:

> > libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I.
> > -I/usr/include/python2.6 -I/usr/include/python2.6 -pthread
> > -I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0
> > -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
> > -I/usr/lib64/glib-2.0/include -I./gtk
> > -I/usr/lib64/python2.6/site-packages/numpy/core/include -pthread
> > -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
> > -I/usr/lib64/glib-2.0/include -O2 -pipe -march=athlon64 -Wall
> > -fno-strict-aliasing -std=c9x -MT pango_la-pangomodule.lo -MD -MP -MF
> > .deps/pango_la-pangomodule.Tpo -c pangomodule.c  -fPIC -DPIC -o
> > .libs/pango_la-pangomodule.o

> > .  If anybody knows how to fix this, or a more appropriate place to
> > ask for help, please tell me.

> > Thanks in advance!

> This one might be tricky. Here's a tip: include version numbers of
> packages that are giving trouble, and whether you run stable, testing
> or (god forbid!) a mixture - this can be rather important in guiding
> one to what to do next (a process mostly defined by instinct rather
> than by say reason)

OK.  As a relative newbie, I only run "stable".  My system is giving me
enough headaches as it is.

> The error looks like an API break between pygtk and whatever provides 
> AtkObject. That is part of the gtk accessibility toolkit, and the relevant 
> files come out of a package called atk.

> My first guess is that pygtk and atk are now out of sync on your machine. Try 
> this:

> emerge -av1 atk
> emerge -av1 pygtk

> Post back if that doesn't work.

Sadly, it didn't work.

> Another tip: search bugs.gentoo.org first before posting - oftentimes 
> the problem is already known and reported on. In this specific case
> however, I didn't find anything.

OK.  I managed to get the problem fixed, basically by trying everything,
though I don't really understand what I did.  This was my recipe:

    emerge --sync
    emerge --update --deep --newuse xfce4-meta

, which updated libglade-2.6.4 and pygtk-2.22.0-r1 successfully.  So
thanks!

> -- 
> alan dot mckinnon at gmail dot com

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2942 bytes --]

On Saturday 23 April 2011 17:35:44 Alan Mackenzie wrote:
> Hi, Alan.
> 
> On Sat, Apr 23, 2011 at 12:43:45AM +0200, Alan McKinnon wrote:
> > Apparently, though unproven, at 20:05 on Friday 22 April 2011, Alan
> > Mackenzie
> > 
> > did opine thusly:
> > > Hi, Gentoo.
> > > 
> > > In my attempt to 'emerge --update --deep xfce4-meta', one sole
> > > package is refusing to build, namely pygtk.
> > > 
> > > Its log file displays many (perhaps 100) error lines like:
> > >     Could not write method AtkObject.get_attributes: No ArgType for
> > > 
> > > AtkAttributeSet*
> > > 
> > > .  The command that caused all these errors was:
> > > 
> > > libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I.
> > > -I/usr/include/python2.6 -I/usr/include/python2.6 -pthread
> > > -I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0
> > > -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
> > > -I/usr/lib64/glib-2.0/include -I./gtk
> > > -I/usr/lib64/python2.6/site-packages/numpy/core/include -pthread
> > > -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
> > > -I/usr/lib64/glib-2.0/include -O2 -pipe -march=athlon64 -Wall
> > > -fno-strict-aliasing -std=c9x -MT pango_la-pangomodule.lo -MD -MP -MF
> > > .deps/pango_la-pangomodule.Tpo -c pangomodule.c  -fPIC -DPIC -o
> > > .libs/pango_la-pangomodule.o
> > > 
> > > .  If anybody knows how to fix this, or a more appropriate place to
> > > ask for help, please tell me.
> > > 
> > > Thanks in advance!
> > 
> > This one might be tricky. Here's a tip: include version numbers of
> > packages that are giving trouble, and whether you run stable, testing
> > or (god forbid!) a mixture - this can be rather important in guiding
> > one to what to do next (a process mostly defined by instinct rather
> > than by say reason)
> 
> OK.  As a relative newbie, I only run "stable".  My system is giving me
> enough headaches as it is.
> 
> > The error looks like an API break between pygtk and whatever provides
> > AtkObject. That is part of the gtk accessibility toolkit, and the
> > relevant files come out of a package called atk.
> > 
> > My first guess is that pygtk and atk are now out of sync on your machine.
> > Try this:
> > 
> > emerge -av1 atk
> > emerge -av1 pygtk
> > 
> > Post back if that doesn't work.
> 
> Sadly, it didn't work.
> 
> > Another tip: search bugs.gentoo.org first before posting - oftentimes
> > the problem is already known and reported on. In this specific case
> > however, I didn't find anything.
> 
> OK.  I managed to get the problem fixed, basically by trying everything,
> though I don't really understand what I did.  This was my recipe:
> 
>     emerge --sync
>     emerge --update --deep --newuse xfce4-meta
> 
> , which updated libglade-2.6.4 and pygtk-2.22.0-r1 successfully.  So
> thanks!

What do you get when you run:

# eselect python list
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

[Alan Mackenzie]

Hi, Mick.

On Sat, Apr 23, 2011 at 08:46:30PM +0100, Mick wrote:
> On Saturday 23 April 2011 17:35:44 Alan Mackenzie wrote:
> > Hi, Alan.

> > On Sat, Apr 23, 2011 at 12:43:45AM +0200, Alan McKinnon wrote:
> > > Apparently, though unproven, at 20:05 on Friday 22 April 2011, Alan
> > > Mackenzie

> > > did opine thusly:
> > > > Hi, Gentoo.

> > > > In my attempt to 'emerge --update --deep xfce4-meta', one sole
> > > > package is refusing to build, namely pygtk.

> > > > Its log file displays many (perhaps 100) error lines like:
> > > >     Could not write method AtkObject.get_attributes: No ArgType for

> > > > AtkAttributeSet*

> > > > .  The command that caused all these errors was:

> > > > libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I.
> > > > -I/usr/include/python2.6 -I/usr/include/python2.6 -pthread
> > > > -I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0
> > > > -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
> > > > -I/usr/lib64/glib-2.0/include -I./gtk
> > > > -I/usr/lib64/python2.6/site-packages/numpy/core/include -pthread
> > > > -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
> > > > -I/usr/lib64/glib-2.0/include -O2 -pipe -march=athlon64 -Wall
> > > > -fno-strict-aliasing -std=c9x -MT pango_la-pangomodule.lo -MD -MP -MF
> > > > .deps/pango_la-pangomodule.Tpo -c pangomodule.c  -fPIC -DPIC -o
> > > > .libs/pango_la-pangomodule.o

> > > > .  If anybody knows how to fix this, or a more appropriate place
> > > > to ask for help, please tell me.

> > > > Thanks in advance!

> > > This one might be tricky. Here's a tip: include version numbers of
> > > packages that are giving trouble, and whether you run stable,
> > > testing or (god forbid!) a mixture - this can be rather important
> > > in guiding one to what to do next (a process mostly defined by
> > > instinct rather than by say reason)

> > OK.  As a relative newbie, I only run "stable".  My system is giving
> > me enough headaches as it is.

> > > The error looks like an API break between pygtk and whatever
> > > provides AtkObject. That is part of the gtk accessibility toolkit,
> > > and the relevant files come out of a package called atk.

> > > My first guess is that pygtk and atk are now out of sync on your
> > > machine.  Try this:

> > > emerge -av1 atk
> > > emerge -av1 pygtk

> > > Post back if that doesn't work.

> > Sadly, it didn't work.

> > > Another tip: search bugs.gentoo.org first before posting -
> > > oftentimes the problem is already known and reported on. In this
> > > specific case however, I didn't find anything.

> > OK.  I managed to get the problem fixed, basically by trying
> > everything, though I don't really understand what I did.  This was my
> > recipe:

> >     emerge --sync
> >     emerge --update --deep --newuse xfce4-meta

> > , which updated libglade-2.6.4 and pygtk-2.22.0-r1 successfully.  So
> > thanks!

> What do you get when you run:

> # eselect python list

Available Python interpreters:
  [1]   python2.6 *
  [2]   python2.7
  [3]   python3.1

> -- 
> Regards,
> Mick

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 770 bytes --]

On Saturday 23 April 2011 21:06:25 Alan Mackenzie wrote:
> On Sat, Apr 23, 2011 at 08:46:30PM +0100, Mick wrote:

> > What do you get when you run:
> > 
> > # eselect python list
> 
> Available Python interpreters:
>   [1]   python2.6 *
>   [2]   python2.7
>   [3]   python3.1

OK, the next stage would be to change your python to the latest stable:

eselect python set 2

and then remerge those packages that were linked against the old python:

python-updater -v -p

to get a list of these.

When you finish all this you can run:

emerge --depclean -v -p

It should now ask you to remove the old python, but check carefully the 
remaining packages in case something important is in the list and breaks your 
system.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Alan Mackenzie]

Hi, Mick.

On Sun, Apr 24, 2011 at 09:17:45AM +0100, Mick wrote:
> On Saturday 23 April 2011 21:06:25 Alan Mackenzie wrote:
> > On Sat, Apr 23, 2011 at 08:46:30PM +0100, Mick wrote:

> > > What do you get when you run:

> > > # eselect python list

> > Available Python interpreters:
> >   [1]   python2.6 *
> >   [2]   python2.7
> >   [3]   python3.1

> OK, the next stage would be to change your python to the latest stable:

> eselect python set 2

DONE.

> and then remerge those packages that were linked against the old
> python:

> python-updater -v -p

> to get a list of these.

That gives me a list of 24 packages.  Am I meant to actually run
python-updater without the -p, here?

> When you finish all this you can run:

> emerge --depclean -v -p

> It should now ask you to remove the old python, but check carefully the
> remaining packages in case something important is in the list and
> breaks your system.

I do emerge --depclean -v -p.  It says I should run emerge -uDN @world
first.  I'm a bit apprehensive about this, since the world update says it
would reemerge 138 packages (I'm not sure whether this is top-level
(whatever that means) packages or the real total).  In that list are 3
blockages I don't know wha do do with.  My experience suggests this will
not work smoothly, and I'll likely be left with a non-working (or even a
non-bootable) system.

How come?  Well, I started my installation in February 2010, and with one
thing and another, didn't get it finished, so it went into cold storage
until a month ago.  I've had so much trouble trying to get updated, that
it might be better to start again from scratch with a new stage3 (or even
a new installation CD).  This would surely leave my home directory and
suchlike untouched.  What do you think?

> -- 
> Regards,
> Mick

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2626 bytes --]

On Sunday 24 April 2011 14:25:58 Alan Mackenzie wrote:
> Hi, Mick.
> 
> On Sun, Apr 24, 2011 at 09:17:45AM +0100, Mick wrote:
> > On Saturday 23 April 2011 21:06:25 Alan Mackenzie wrote:
> > > On Sat, Apr 23, 2011 at 08:46:30PM +0100, Mick wrote:
> > > > What do you get when you run:
> > > > 
> > > > # eselect python list
> > > 
> > > Available Python interpreters:
> > >   [1]   python2.6 *
> > >   [2]   python2.7
> > >   [3]   python3.1
> > 
> > OK, the next stage would be to change your python to the latest stable:
> > 
> > eselect python set 2
> 
> DONE.
> 
> > and then remerge those packages that were linked against the old
> > python:
> > 
> > python-updater -v -p
> > 
> > to get a list of these.
> 
> That gives me a list of 24 packages.  Am I meant to actually run
> python-updater without the -p, here?

That's correct.  As the man emerge say -p stands for --pretend.  Just to give 
a chance to see what it wants to do and think about it before you run it again 
without it for execution.

You need to do this next.


> > When you finish all this you can run:
> > 
> > emerge --depclean -v -p
> > 
> > It should now ask you to remove the old python, but check carefully the
> > remaining packages in case something important is in the list and
> > breaks your system.
> 
> I do emerge --depclean -v -p.  It says I should run emerge -uDN @world
> first.  I'm a bit apprehensive about this, since the world update says it
> would reemerge 138 packages (I'm not sure whether this is top-level
> (whatever that means) packages or the real total).  In that list are 3
> blockages I don't know wha do do with.  My experience suggests this will
> not work smoothly, and I'll likely be left with a non-working (or even a
> non-bootable) system.

At this stage you should only run:

python-updater -v

Nothing else.

Once it completes you can run --depclean which will ask you to remove the 
older 2.6 python package.


> How come?  Well, I started my installation in February 2010, and with one
> thing and another, didn't get it finished, so it went into cold storage
> until a month ago.  I've had so much trouble trying to get updated, that
> it might be better to start again from scratch with a new stage3 (or even
> a new installation CD).  This would surely leave my home directory and
> suchlike untouched.  What do you think?

Adding the -N flag will remerge any packages that are affected by changes to 
USE flags that you have made since they were first installed.  So the list 
will be longer than without it.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2884 bytes --]

On Sunday 24 April 2011 16:44:05 Mick wrote:
> On Sunday 24 April 2011 14:25:58 Alan Mackenzie wrote:
> > Hi, Mick.
> > 
> > On Sun, Apr 24, 2011 at 09:17:45AM +0100, Mick wrote:
> > > On Saturday 23 April 2011 21:06:25 Alan Mackenzie wrote:
> > > > On Sat, Apr 23, 2011 at 08:46:30PM +0100, Mick wrote:
> > > > > What do you get when you run:
> > > > > 
> > > > > # eselect python list
> > > > 
> > > > Available Python interpreters:
> > > >   [1]   python2.6 *
> > > >   [2]   python2.7
> > > >   [3]   python3.1
> > > 
> > > OK, the next stage would be to change your python to the latest stable:
> > > 
> > > eselect python set 2
> > 
> > DONE.
> > 
> > > and then remerge those packages that were linked against the old
> > > python:
> > > 
> > > python-updater -v -p
> > > 
> > > to get a list of these.
> > 
> > That gives me a list of 24 packages.  Am I meant to actually run
> > python-updater without the -p, here?
> 
> That's correct.  As the man emerge say -p stands for --pretend.  Just to
> give a chance to see what it wants to do and think about it before you run
> it again without it for execution.
> 
> You need to do this next.
> 
> > > When you finish all this you can run:
> > > 
> > > emerge --depclean -v -p
> > > 
> > > It should now ask you to remove the old python, but check carefully the
> > > remaining packages in case something important is in the list and
> > > breaks your system.
> > 
> > I do emerge --depclean -v -p.  It says I should run emerge -uDN @world
> > first.  I'm a bit apprehensive about this, since the world update says it
> > would reemerge 138 packages (I'm not sure whether this is top-level
> > (whatever that means) packages or the real total).  In that list are 3
> > blockages I don't know wha do do with.  My experience suggests this will
> > not work smoothly, and I'll likely be left with a non-working (or even a
> > non-bootable) system.
> 
> At this stage you should only run:
> 
> python-updater -v
> 
> Nothing else.
> 
> Once it completes you can run --depclean which will ask you to remove the
> older 2.6 python package.
> 
> > How come?  Well, I started my installation in February 2010, and with one
> > thing and another, didn't get it finished, so it went into cold storage
> > until a month ago.  I've had so much trouble trying to get updated, that
> > it might be better to start again from scratch with a new stage3 (or even
> > a new installation CD).  This would surely leave my home directory and
> > suchlike untouched.  What do you think?
> 
> Adding the -N flag will remerge any packages that are affected by changes
> to USE flags that you have made since they were first installed.  So the
> list will be longer than without it.

Post any blockers shown if you don't know what you need to do about them.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Stroller]

On 24/4/2011, at 4:44pm, Mick wrote:
> ...
> At this stage you should only run:
> 
> python-updater -v
> 
> Nothing else.


Doing this today I've had a couple of packages that needed to be emerged with USE=-doc when they failed.

Stroller.


 

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Alan Mackenzie]

Hi, Mick.

On Sun, Apr 24, 2011 at 04:44:05PM +0100, Mick wrote:
> On Sunday 24 April 2011 14:25:58 Alan Mackenzie wrote:
> > Hi, Mick.

> > On Sun, Apr 24, 2011 at 09:17:45AM +0100, Mick wrote:
> > > On Saturday 23 April 2011 21:06:25 Alan Mackenzie wrote:
> > > > On Sat, Apr 23, 2011 at 08:46:30PM +0100, Mick wrote:

> > > python-updater -v -p

> > > to get a list of these.

> > That gives me a list of 24 packages.  Am I meant to actually run
> > python-updater without the -p, here?

> That's correct.  As the man emerge say -p stands for --pretend.  Just
> to give a chance to see what it wants to do and think about it before
> you run it again without it for execution.

> You need to do this next.

DONE.

> > > When you finish all this you can run:

> > > emerge --depclean -v -p

> > > It should now ask you to remove the old python, but check carefully
> > > the remaining packages in case something important is in the list
> > > and breaks your system.

> > I do emerge --depclean -v -p.  It says I should run emerge -uDN
> > @world first.  I'm a bit apprehensive about this, since the world
> > update says it would reemerge 138 packages (I'm not sure whether this
> > is top-level (whatever that means) packages or the real total).  In
> > that list are 3 blockages I don't know wha do do with.  My experience
> > suggests this will not work smoothly, and I'll likely be left with a
> > non-working (or even a non-bootable) system.

> At this stage you should only run:

> python-updater -v

> Nothing else.

> Once it completes you can run --depclean which will ask you to remove
> the older 2.6 python package.

I had to (or, at least, did) run emerge -uND @world.  Funnily enough, it
ran to completion without manual intervention.  :-)  I'd like to run
--depclean, but it's threatening to remove my 2.6.31-r6 kernel sources,
which correspond to my working kernel.  What's the easiest way to protect
these from --depclean?

> -- 
> Regards,
> Mick

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2991 bytes --]

On Monday 25 April 2011 13:11:53 Alan Mackenzie wrote:
> Hi, Mick.
> 
> On Sun, Apr 24, 2011 at 04:44:05PM +0100, Mick wrote:
> > On Sunday 24 April 2011 14:25:58 Alan Mackenzie wrote:
> > > Hi, Mick.
> > > 
> > > On Sun, Apr 24, 2011 at 09:17:45AM +0100, Mick wrote:
> > > > On Saturday 23 April 2011 21:06:25 Alan Mackenzie wrote:
> > > > > On Sat, Apr 23, 2011 at 08:46:30PM +0100, Mick wrote:
> > > > python-updater -v -p
> > > > 
> > > > to get a list of these.
> > > 
> > > That gives me a list of 24 packages.  Am I meant to actually run
> > > python-updater without the -p, here?
> > 
> > That's correct.  As the man emerge say -p stands for --pretend.  Just
> > to give a chance to see what it wants to do and think about it before
> > you run it again without it for execution.
> > 
> > You need to do this next.
> 
> DONE.
> 
> > > > When you finish all this you can run:
> > > > 
> > > > emerge --depclean -v -p
> > > > 
> > > > It should now ask you to remove the old python, but check carefully
> > > > the remaining packages in case something important is in the list
> > > > and breaks your system.
> > > 
> > > I do emerge --depclean -v -p.  It says I should run emerge -uDN
> > > @world first.  I'm a bit apprehensive about this, since the world
> > > update says it would reemerge 138 packages (I'm not sure whether this
> > > is top-level (whatever that means) packages or the real total).  In
> > > that list are 3 blockages I don't know wha do do with.  My experience
> > > suggests this will not work smoothly, and I'll likely be left with a
> > > non-working (or even a non-bootable) system.
> > 
> > At this stage you should only run:
> > 
> > python-updater -v
> > 
> > Nothing else.
> > 
> > Once it completes you can run --depclean which will ask you to remove
> > the older 2.6 python package.
> 
> I had to (or, at least, did) run emerge -uND @world.  Funnily enough, it
> ran to completion without manual intervention.  :-)  I'd like to run
> --depclean, but it's threatening to remove my 2.6.31-r6 kernel sources,
> which correspond to my working kernel.  What's the easiest way to protect
> these from --depclean?

Aha! That's why I said first look at what it wants to remove - you don't want 
to cripple your system.  In this case of course it won't cripple anything, 
because it won't remove the kernel image from /boot/

If you look in /usr/src/linux/ you will see a number of kernel sources listed 
in there.  If you've run update world there should be a more up-to-date kernel 
awaiting for you to configure and compile it.  Do that first; copy the 
necessary files into /boot; configure grub.conf to boot with you latest 
kernel; and after you boot into it and check that all is good you can allow --
depclean to remove older kernel source files.

PS.  You may need to manually remove older source files left in 
/usr/src/linux/ when depclean completes its job.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Alan Mackenzie]

Hi, Mick.

On Mon, Apr 25, 2011 at 03:12:15PM +0100, Mick wrote:
> On Monday 25 April 2011 13:11:53 Alan Mackenzie wrote:

> > > Once it completes you can run --depclean which will ask you to
> > > remove the older 2.6 python package.

> > I had to (or, at least, did) run emerge -uND @world.  Funnily enough,
> > it ran to completion without manual intervention.  :-)  I'd like to
> > run --depclean, but it's threatening to remove my 2.6.31-r6 kernel
> > sources, which correspond to my working kernel.  What's the easiest
> > way to protect these from --depclean?

> Aha! That's why I said first look at what it wants to remove - you
> don't want to cripple your system.  In this case of course it won't
> cripple anything, because it won't remove the kernel image from /boot/

> If you look in /usr/src/linux/ you will see a number of kernel sources
> listed in there.  If you've run update world there should be a more
> up-to-date kernel awaiting for you to configure and compile it.  Do
> that first; copy the necessary files into /boot; configure grub.conf to
> boot with you latest kernel; and after you boot into it and check that
> all is good you can allow -- depclean to remove older kernel source
> files.

Yes, I've got new kernel sources, and yesterday and today I've spent
about 5 hours head-banging to get a working kernel.  (I've managed it,
thankfully.)  But the new kernel's X-windows isn't filling my 1920x1080
shiny new monitor like the old kernel did.  I've still got some fiddling
to do.

Call me a clinging cry-baby if you like, but until I'm confident about my
new kernel, I'd like to hang on to the old one, including its sources.
It'd also be nice to run --depclean in the meantime.  Do I have to do
recursive copying or directory renaming to achiev this?

As a matter of interest, do you know how to configure a framebuffer
console to fill up a wide screen (say, to a width of 170 characters) as
contrasted with the 128 characters which were optimum on an old fashioned
CRT?

> PS.  You may need to manually remove older source files left in 
> /usr/src/linux/ when depclean completes its job.

OK.  I can manage that.

> -- 
> Regards,
> Mick

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Mark Knecht]

On Mon, Apr 25, 2011 at 8:03 AM, Alan Mackenzie <acm@muc.de> wrote:
<SNIP>
> Call me a clinging cry-baby if you like, but until I'm confident about my
> new kernel, I'd like to hang on to the old one, including its sources.
> It'd also be nice to run --depclean in the meantime.  Do I have to do
> recursive copying or directory renaming to achiev this?
>

Run something like

emerge --noreplace =gentoo-sources-2.6.38-r1

to add the kernel you want to keep to your world file, or just add the
kernel with it's specific revision to the world file manually. At that
point emerge won't delete it and you won't get any messages until
portage maintainers remove it from portage.

HTH,
Mark

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Alan Mackenzie]

Hi, Mark.

On Mon, Apr 25, 2011 at 08:29:47AM -0700, Mark Knecht wrote:
> On Mon, Apr 25, 2011 at 8:03 AM, Alan Mackenzie <acm@muc.de> wrote:

> Run something like

> emerge --noreplace =gentoo-sources-2.6.38-r1

That's just the job.  Thanks.

> HTH,
> Mark

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2829 bytes --]

On Monday 25 April 2011 16:03:21 Alan Mackenzie wrote:
> Hi, Mick.
> 
> On Mon, Apr 25, 2011 at 03:12:15PM +0100, Mick wrote:
> > On Monday 25 April 2011 13:11:53 Alan Mackenzie wrote:
> > > > Once it completes you can run --depclean which will ask you to
> > > > remove the older 2.6 python package.
> > > 
> > > I had to (or, at least, did) run emerge -uND @world.  Funnily enough,
> > > it ran to completion without manual intervention.  :-)  I'd like to
> > > run --depclean, but it's threatening to remove my 2.6.31-r6 kernel
> > > sources, which correspond to my working kernel.  What's the easiest
> > > way to protect these from --depclean?
> > 
> > Aha! That's why I said first look at what it wants to remove - you
> > don't want to cripple your system.  In this case of course it won't
> > cripple anything, because it won't remove the kernel image from /boot/
> > 
> > If you look in /usr/src/linux/ you will see a number of kernel sources
> > listed in there.  If you've run update world there should be a more
> > up-to-date kernel awaiting for you to configure and compile it.  Do
> > that first; copy the necessary files into /boot; configure grub.conf to
> > boot with you latest kernel; and after you boot into it and check that
> > all is good you can allow -- depclean to remove older kernel source
> > files.
> 
> Yes, I've got new kernel sources, and yesterday and today I've spent
> about 5 hours head-banging to get a working kernel.  (I've managed it,
> thankfully.)  But the new kernel's X-windows isn't filling my 1920x1080
> shiny new monitor like the old kernel did.  I've still got some fiddling
> to do.
> 
> Call me a clinging cry-baby if you like, but until I'm confident about my
> new kernel, I'd like to hang on to the old one, including its sources.
> It'd also be nice to run --depclean in the meantime.  Do I have to do
> recursive copying or directory renaming to achiev this?
> 
> As a matter of interest, do you know how to configure a framebuffer
> console to fill up a wide screen (say, to a width of 170 characters) as
> contrasted with the 128 characters which were optimum on an old fashioned
> CRT?

I think that things have moved on since the first time you installed Gentoo.  
Latest kernels have the ability to load firmware for your video card that 
takes account of the native resolution of the monitor - without any additional 
framebuffer drivers (like vesa, uvesa, radeonfb, etc.)  As a matter of fact 
you'll get a blank screen if you try to boot the latest kernels with KMS 
configured using any additional framebuffer driver.

To save me describing each step, you would do better reading through this page 
which details everything you need to do:

http://www.gentoo.org/doc/en/xorg-config.xml

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Alan Mackenzie]

Hi, Nick.

On Mon, Apr 25, 2011 at 05:00:49PM +0100, Mick wrote:
> On Monday 25 April 2011 16:03:21 Alan Mackenzie wrote:

> > As a matter of interest, do you know how to configure a framebuffer
> > console to fill up a wide screen (say, to a width of 170 characters)
> > as contrasted with the 128 characters which were optimum on an old
> > fashioned CRT?

> I think that things have moved on since the first time you installed
> Gentoo.  Latest kernels have the ability to load firmware for your
> video card that takes account of the native resolution of the monitor -
> without any additional framebuffer drivers (like vesa, uvesa, radeonfb,
> etc.)  As a matter of fact you'll get a blank screen if you try to boot
> the latest kernels with KMS configured using any additional framebuffer
> driver.

Indeed.  :-(

> To save me describing each step, you would do better reading through
> this page which details everything you need to do:

> http://www.gentoo.org/doc/en/xorg-config.xml

A fascinating document.  Thanks!

> -- 
> Regards,
> Mick

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

[Alan McKinnon]

Apparently, though unproven, at 18:35 on Saturday 23 April 2011, Alan 
Mackenzie did opine thusly:

> OK.  I managed to get the problem fixed, basically by trying everything,
> though I don't really understand what I did.  This was my recipe:
> 
>     emerge --sync
>     emerge --update --deep --newuse xfce4-meta
> 
> , which updated libglade-2.6.4 and pygtk-2.22.0-r1 successfully.  So
> thanks!

In that case, you either had an incomplete portage tree and syncing gave you 
all the bits you needed. Or the pygtk ebuild was faulty and the dev fixed it 
without bumping the version number.


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

[Volker Armin Hemmann]

On Saturday 23 April 2011 22:21:28 Alan McKinnon wrote:
> Apparently, though unproven, at 18:35 on Saturday 23 April 2011, Alan
> 
> Mackenzie did opine thusly:
> > OK.  I managed to get the problem fixed, basically by trying everything,
> > 
> > though I don't really understand what I did.  This was my recipe:
> >     emerge --sync
> >     emerge --update --deep --newuse xfce4-meta
> > 
> > , which updated libglade-2.6.4 and pygtk-2.22.0-r1 successfully.  So
> > thanks!
> 
> In that case, you either had an incomplete portage tree and syncing gave you
> all the bits you needed. Or the pygtk ebuild was faulty and the dev fixed
> it without bumping the version number.

which happens everytime a version is so bugged it does not install.

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[David W Noon]

[-- Attachment #1: Type: text/plain, Size: 749 bytes --]

On Sun, 24 Apr 2011 21:40:02 +0200, Stroller wrote about Re:
[gentoo-user] Reinstall Gentoo?  [Was: Building pygtk-2.22.0-r1 fails.
Help, please!]:

>On 24/4/2011, at 4:44pm, Mick wrote:
>> ...
>> At this stage you should only run:
>> 
>> python-updater -v
>> 
>> Nothing else.
>
>
>Doing this today I've had a couple of packages that needed to be
>emerged with USE=-doc when they failed.

Those would be jinja and sphinx.  They are notorious for their circular
dependency, which requires USE='-doc' to bypass.
-- 
Regards,

Dave  [RLU #314465]
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
dwnoon@ntlworld.com (David W Noon)
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 534 bytes --]

On Sun, 24 Apr 2011 21:17:23 +0100, David W Noon wrote:

> >Doing this today I've had a couple of packages that needed to be
> >emerged with USE=-doc when they failed.  
> 
> Those would be jinja and sphinx.  They are notorious for their circular
> dependency, which requires USE='-doc' to bypass.

It's rarely desirable to enable doc globally. It is best to enable only
for those packages where you need extended documentation.


-- 
Neil Bothwick

A bit of tolerance is worth a megabyte of flaming. -- Henry Spencer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 770 bytes --]

On Sunday 24 April 2011 21:30:33 Neil Bothwick wrote:
> On Sun, 24 Apr 2011 21:17:23 +0100, David W Noon wrote:
> > >Doing this today I've had a couple of packages that needed to be
> > >emerged with USE=-doc when they failed.
> > 
> > Those would be jinja and sphinx.  They are notorious for their circular
> > dependency, which requires USE='-doc' to bypass.
> 
> It's rarely desirable to enable doc globally. It is best to enable only
> for those packages where you need extended documentation.

@Alan Mackenzie:

What Neil is saying can be achieved by setting package specific USE flags in 
the file /etc/portage/package.use; e.g. use an entry like:

dev-python/jinja -doc i18n

to exclude USE flag "doc", but include "i18n".
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 793 bytes --]

On Sun, 24 Apr 2011 23:16:39 +0100, Mick wrote:

> > It's rarely desirable to enable doc globally. It is best to enable
> > only for those packages where you need extended documentation.  
> 
> @Alan Mackenzie:
> 
> What Neil is saying can be achieved by setting package specific USE
> flags in the file /etc/portage/package.use; e.g. use an entry like:

What I'm saying is that you should have -doc in /etc/make.conf and enable
it on a per-package basis. The doc flag builds extra documentation that
general users don't need, man/info/html pages are included by default (at
least, that's how it is supposed to work, the odd package, like ffmpeg,
won't even include a man page without the doc flag). 


-- 
Neil Bothwick

This is as bad as it can get-but don't bet on it.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1056 bytes --]

On Monday 25 April 2011 08:30:58 Neil Bothwick wrote:
> On Sun, 24 Apr 2011 23:16:39 +0100, Mick wrote:
> > > It's rarely desirable to enable doc globally. It is best to enable
> > > only for those packages where you need extended documentation.
> > 
> > @Alan Mackenzie:
> > 
> > What Neil is saying can be achieved by setting package specific USE
> 
> > flags in the file /etc/portage/package.use; e.g. use an entry like:
> What I'm saying is that you should have -doc in /etc/make.conf and enable
> it on a per-package basis. The doc flag builds extra documentation that
> general users don't need, man/info/html pages are included by default (at
> least, that's how it is supposed to work, the odd package, like ffmpeg,
> won't even include a man page without the doc flag).

The doc USE flag is disabled by default on my make.profile 
(amd64/10.0/desktop), so although it won't need to be set as -doc in 
/etc/make.conf, it will need to be set as doc in the packages that need it in 
/etc/portage/package.use.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 927 bytes --]

On Mon, 25 Apr 2011 08:49:35 +0100, Mick wrote:

> > What I'm saying is that you should have -doc in /etc/make.conf and
> > enable it on a per-package basis. The doc flag builds extra
> > documentation that general users don't need, man/info/html pages are
> > included by default (at least, that's how it is supposed to work, the
> > odd package, like ffmpeg, won't even include a man page without the
> > doc flag).  
> 
> The doc USE flag is disabled by default on my make.profile 
> (amd64/10.0/desktop), so although it won't need to be set as -doc in 
> /etc/make.conf, it will need to be set as doc in the packages that need
> it in /etc/portage/package.use.

I know it's disabled by default, but it seems like the OP has enabled it
globally.


-- 
Neil Bothwick

"When you play a Microsoft CD backwards you can hear demonic Voices...
that's nothing - when you play it forward it installs Windows"

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Alan Mackenzie]

Hi, Neil.

A happy Easter to everybody who celebrates it, and a very good day to
everybody else!

On Mon, Apr 25, 2011 at 11:07:15AM +0100, Neil Bothwick wrote:
> On Mon, 25 Apr 2011 08:49:35 +0100, Mick wrote:

> > The doc USE flag is disabled by default on my make.profile
> > (amd64/10.0/desktop), so although it won't need to be set as -doc in
> > /etc/make.conf, it will need to be set as doc in the packages that
> > need it in /etc/portage/package.use.

> I know it's disabled by default, but it seems like the OP has enabled it
> globally.

Not me!  The handbook strongly recommended against doing this.

> -- 
> Neil Bothwick

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Stroller]

On 25/4/2011, at 11:07am, Neil Bothwick wrote:
>> ...
>> The doc USE flag is disabled by default on my make.profile 
>> (amd64/10.0/desktop), so although it won't need to be set as -doc in 
>> /etc/make.conf, it will need to be set as doc in the packages that need
>> it in /etc/portage/package.use.
> 
> I know it's disabled by default, but it seems like the OP has enabled it
> globally.

In case you're mistaking me for the OP: I have it enabled globally, I just mentioned the necessity of disabling it for some packages in case the OP came across the same problem.

Maybe I should disable doc, but it seems "wrong" to me, to miss out on all this potentially useful information (which admittedly I never use).

Stroller.

Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 390 bytes --]

On Mon, 25 Apr 2011 13:18:22 +0100, Stroller wrote:

> Maybe I should disable doc, but it seems "wrong" to me, to miss out on
> all this potentially useful information (which admittedly I never use).

The potentially useful information is installed anyway. USE=doc enables
the potentially useless information ;-)


-- 
Neil Bothwick

Happiness is merely the remission of pain.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]