[gentoo-dev] Portage-2.0.47-r1 testing

[gentoo-dev] Portage-2.0.47-r1 testing

[Nick Jones]

Ok. Portage-2.0.47-r1 is ready for testing. It's got a lot of new
stuff in it along with a good deal of fixes. Should be 'wicked-fast'
as it has a lot of updates to caching code and the like. It is masked
in package.mask. I need testers AND feedback. Gimme a holler with
bugs and good/bad comments. Here or on bugs.gentoo.org is fine.

Docs have yet to be updated, but I'm sure you can figure it out
from this:

The short list:
emerge --resume [--pretend]
 * Resume from the last package in action. The one that failed.
emerge --pretend --columns <package>
 * Column output of package, new version, old version
emerge [--verbose] info
 * Display _all_ variables that would be exported to ebuild.sh
 - Excludes variables determined inside of ebuild.sh
emerge [--nospinner] [--noconfmem] <action>
 * Disable the spinner in all circumstances.
 * Do not 'remember' that a file in a CONFIG_PROTECT dir has been
   merged before. This allows you to force the file to reappear after
   you have deleted it.
FEATURES=noclean (changed, remove -a,--autoclean)
 * --autoclean is gone. This functionality is only via FEATURES=noclean
   now. Cleaning actually occurs now in the .47 series.
FEATURES=userpriv,usersandbox
 * userpriv -- Allow portage to drop root and become portage:portage.
   This will be an alternative to sandboxing for users. The $HOME of
   the portage user is set to BUILD_PREFIX/homedir and is deleted for
   every run.
 * usersandbox -- Enable the sandbox along side userpriv. Recommended as
   it shows invalid writes occuring in packages.
RSYNC_TIMEOUT
 * Set in make.conf, allows users to specify a timeout. Some users were
   having problems with this being set too low and it is now configurable.


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Relevant portions of changelog: (2.0.46-r12 and 2.0.47-r1)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
# ChangeLog for Portage; the Gentoo Linux ports system 
# Copyright 2000-2003 Gentoo Technologies, Inc.; Distributed under the GPL v2
# $Header: /home/cvsroot/gentoo-src/portage/ChangeLog,v 1.419 2003/02/16 14:27:57 carpaski Exp $

*portage-2.0.47-r1 (16 Feb 2003): Wicked Fast + UserPriv

  16 Feb 2003; Nicholas Jones <carpaski@gentoo.org> portage.py: Changed a
  few os.system calls to spawn calls. Added userpriv in features check to
  spawn. HOME is now placed in BUILD_PREFIX/homedir when userpriv is enabled.
  Valid command for doebuild() moved to the top of the function. Reorganized
  the directory creation code in doebuild(). HOME is cleaned for every merge
  if in userpriv. LOG_COUNTER fix for the per-ebuild logs -- Only one value
  is used per $PF now.

  16 Feb 2003; Nicholas Jones <carpaski@gentoo.org> emerge: Adjusted options
  to remove --autoclean and make it on-by-default unless killed in FEATURES
  with 'noclean'. Removed debug for --resume. Added RSYNC_TIMEOUT as some
  dialup and other users are experiencing problems with rsync never finishing
  a connection. Added check at the end of an rsync to notify the user when
  a new version of portage is available. Added --pretend capability/fix to
  the --resume code. No resume data and a --resume is no longer a failure.

  16 Feb 2003; Nicholas Jones <carpaski@gentoo.org> ebuild.sh: Updates to
  logic of ${T}/successful handling to allow proper cleaning. dyn_clean()
  will do a recursive dir removal after cleaning specific files. Recursive
  chown removed. CCACHE_DIR handled in portage.py now. Removed a few comments
  and unnecessary checks.

  16 Feb 2003; Nicholas Jones <carpaski@gentoo.org> cnf/*: added comments
  on FEATURES=noclean,noauto,userpriv,usersandbox

  15 Feb 2003; Nicholas Jones <carpaski@gentoo.org> emerge: Alain changed
  the .config() call in the search class to a .settings[] -- Speedup.

  14 Feb 2003; Nicholas Jones <carpaski@gentoo.org> portage.py: Added
  resume to mtimedbkeys.
	
  14 Feb 2003; Nicholas Jones <carpaski@gentoo.org> emerge: --columns
  flag to support column output in --pretend. --resume support added
  to restart portage with the package list with which it stopped -- data
  is stored in mtimedb. Added '--verbose' to 'emerge info' to display
  all variables in settings.

  13 Feb 2003; Nicholas Jones <carpaski@gentoo.org> ebuild.sh: Fix to
  distcc and ccache to prevent them from calling themselves if they
  catch themselves in the path -- double path problem.

  13 Feb 2003; Nicholas Jones <carpaski@gentoo.org> portage.py: Fixes to
  the aux_get() code for metacache updates to eclass deps. Debug output
  removal.

  13 Feb 2003; Nicholas Jones <carpaski@gentoo.org> emerge: More fixes
  to the calls to aux_get() for metacache code. Rearranged the option and
  action arrays. Added --nospinner flag.

  13 Feb 2003; Nicholas Jones <carpaski@gentoo.org> emerge: Reorg of flags.
  Addition of --noconfmem to prevent portage from yanking already-merged
  config files. Extra message in --version about missing gcc and sourcing
  /etc/profile to get it. Yanked the majority of the rsync cachedb update
  code -- Moved it to aux_get.
	
  13 Feb 2003; Nicholas Jones <carpaski@gentoo.org> portage.py: Typo fixes.
  aux_get() now has a metacachedb param for using metadata cache over the
  initial call to doebuild() -- Should speed up rsync users regen time.
  Added support for --noconfmem via settings["NOCONFMEM"] in treewalk().
  Added sys.exit(1) on failure to move files during merge. Comment
  realignment.
	
  11 Feb 2003; Nicholas Jones <carpaski@gentoo.org> portage.py: Fix the
  depcache code by adding in a missing stat call after regeneration.
  Call portageexit() in exithandler() so that mtimedb gets written out
  on cancelled runs. Add in --quiet option. Currently only kills the
  processing messages on emerge regen.
	
  11 Feb 2003; Nicholas Jones <carpaski@gentoo.org> ebuild.sh: Fix the
  eclass code to remove the double inherits cause by eclasses managing
  that on their own.

*portage-2.0.46-r12 (07 Feb 2003): Fixups

  07 Feb 2003; Nicholas Jones <carpaski@gentoo.org> portage.py: Move
  logdir check/generation code so that it's created before 'clean'. Fix
  the usemask/archkeys bug and a related bug with the var enabled. Fix
  to movefile() code to ensure symlinks are handled properly.

  07 Feb 2003; Nicholas Jones <carpaski@gentoo.org> ebuild.sh: Make per-
  ebuild logs use the counter to get a chronological list instead of a
  timestamp based one.
	
  07 Feb 2003; Nicholas Jones <carpaski@gentoo.org> emerge: If a package
  is requested to be updated but is not merged, still add it to world.
	
  07 Feb 2003; Nicholas Jones <carpaski@gentoo.org> *: Update to help.
  Mostly comments on --verbose. Clarification on make.conf* mirrorselect.

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r1 testing

[Rainer Groesslinger]

On Sun, 16 Feb 2003 09:46:14 -0600
Nick Jones <carpaski@twobit.net> wrote:

> Ok. Portage-2.0.47-r1 is ready for testing. It's got a lot of new
> stuff in it along with a good deal of fixes. Should be 'wicked-fast'
> as it has a lot of updates to caching code and the like. It is masked
> in package.mask. I need testers AND feedback. Gimme a holler with
> bugs and good/bad comments. Here or on bugs.gentoo.org is fine.


I just merged it and it seems to be doing fine...
--columns and emerge info is nice and the rsync timeout setting was necessary since the problem happened to many people.

Can't say anything else, only did a sync and some random pretend things with it yet :)


Rainer

--
gentoo-dev@gentoo.org mailing list

[gentoo-dev] Portage-2.0.47-r2 Out For Testing

[Nick Jones]

Ok. I've just pushed out portage-2.0.47-r2. Has a couple fixes, one which
caused the mergelist to dwindle if you weren't doing a --resume.

DepCache had an issue with regeneration (wasn't setting mtimes) and is
now fixed.

emerge --resume will now allow general flags to be modified.
emerge --resume can have --buildpkg and other flags applied to it.

PREROOTPATH is prepended to PATH in ebuild.sh. $S is generated prior
to sourcing the ebuild now, and consequently is available outside of
the functions now.

emerge-webrsync is now part of portage.

--NJ

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 Out For Testing

[Pat Double]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It seems this version doesn't support the "distcc" feature. I have included 
"distcc" in FEATURES and it worked before the 2.0.47 version, but now gcc/g++ 
is not prepended with "distcc".

Is anyone else experiencing this?

On Monday 17 February 2003 06:25 am, Nick Jones wrote:
> Ok. I've just pushed out portage-2.0.47-r2. Has a couple fixes, one which
> caused the mergelist to dwindle if you weren't doing a --resume.

- -- 
Pat Double, double@inebraska.com
"In the beginning God created the heaven and the earth."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+USM9dOmLNuoWoKgRAtccAJ4jzIfnorvo1J5b/52EKOeXU96PAACg0+AE
O6XgGeFcqI/AKgC30y0dEm4=
=VHfq
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r1 testing

[Alexander Futasz]

On Sun, 16 Feb 2003 09:46:14 -0600, Nick Jones wrote:
> Ok. Portage-2.0.47-r1 is ready for testing. It's got a lot of new
> stuff in it along with a good deal of fixes. Should be 'wicked-fast'
> as it has a lot of updates to caching code and the like. It is masked
> in package.mask. I need testers AND feedback. Gimme a holler with
> bugs and good/bad comments. Here or on bugs.gentoo.org is fine.

Sounds nice. Any plans on merging the following patch?

http://bugs.gentoo.org/show_bug.cgi?id=4709

This adds autoupdating of configfiles that havn't been touched and thus
makes a emerge baselayout much less painfull.

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 Out For Testing

[Thomas de Grenier de Latour]

On Mon, 17 Feb 2003 06:25:38 -0600
Nick Jones <carpaski@twobit.net> wrote:

> Ok. I've just pushed out portage-2.0.47-r2.

When I search for some packages as a simple user, I have some strange
errors:

<example>

thomas@gromit thomas $ emerge -s mplayer
Searching...  -
 
aux_get(): (2) couldn't open cache entry for media-video/kmplayer-0.6
               Check for syntax error or corruption in the ebuild.
   
[ Results for search key : mplayer ]
[ Applications found : 4 ]
  
 
 
aux_get(): (2) couldn't open cache entry for media-video/kmplayer-0.6
               Check for syntax error or corruption in the ebuild.
 
 
aux_get(): (2) couldn't open cache entry for media-video/kmplayer-0.7
               Check for syntax error or corruption in the ebuild.
emerge: search: aux_get() failed, skipping
*  media-video/mplayer
      Latest version available: 0.90_rc4
      Latest version installed: 0.90_rc4
      Size of downloaded files: 3,990 kB
      Homepage:    http://www.mplayerhq.hu/
      Description: Media Player for Linux
 
*  net-www/mplayerplug-in
      Latest version available: 0.40
      Latest version installed: 0.40
      Size of downloaded files: 38 kB
      Homepage:    http://mplayerplug-in.sourceforge.net/
      Description: mplayerplug-in video player for mozilla, konq, etc...
 
*  x11-themes/mplayer-skins
      Latest version available: 0.1
      Latest version installed: 0.1
      Size of downloaded files: 4,965 kB
      Homepage:    http://www.mplayerhq.hu/
      Description: Collection of mplayer themes
 
</example>

What do they means ?

-- 
Thomas.

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 Out For Testing

[Brandon Low]

> PREROOTPATH is prepended to PATH in ebuild.sh. $S is generated prior
> to sourcing the ebuild now, and consequently is available outside of
> the functions now.

Someone else posted that distcc doesn't seem to be working, could that relate to this?  What the heck is PREROOTPATH??

--B

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r1 testing

[Matt Tucker]

-- Alexander Futasz <acid.punk@gmx.net> spake thusly:

> Sounds nice. Any plans on merging the following patch?
> 
> http://bugs.gentoo.org/show_bug.cgi?id=4709
> 
> This adds autoupdating of configfiles that havn't been touched and
> thus makes a emerge baselayout much less painfull.

It not only makes it less painful, I completely missed getting bit by
the recent 1.8.6.2 bug, even though I happened to go through it both
ways (1.8.5.8 -> 1.8.6.2 -> 1.8.5.8) on two different machines with
reboots in between.


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 Out For Testing

[Paul de Vrieze]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1027 bytes --]

On Monday 17 February 2003 13:25, Nick Jones wrote:
> Ok. I've just pushed out portage-2.0.47-r2. Has a couple fixes, one which
> caused the mergelist to dwindle if you weren't doing a --resume.
>
> DepCache had an issue with regeneration (wasn't setting mtimes) and is
> now fixed.
>
> emerge --resume will now allow general flags to be modified.
> emerge --resume can have --buildpkg and other flags applied to it.
>
> PREROOTPATH is prepended to PATH in ebuild.sh. $S is generated prior
> to sourcing the ebuild now, and consequently is available outside of
> the functions now.
>
> emerge-webrsync is now part of portage.
>

There are many packages (such as oops and ksymoops) that suddenly stop working 
complaining:
aux_get(): (2) couldn't open cache entry for sys-kernel/ksymoops-2.4.5
               Check for syntax error or corruption in the ebuild.

So for now I'm back with 2.0.46-r12

Paul

-- 
Paul de Vrieze
Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.cs.kun.nl/~pauldv

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Portage-2.0.47-r2 Out For Testing

[Yannick Koehler]

On February 17, 2003 01:28 pm, Thomas de Grenier de Latour wrote:
> On Mon, 17 Feb 2003 06:25:38 -0600
>
> Nick Jones <carpaski@twobit.net> wrote:
> > Ok. I've just pushed out portage-2.0.47-r2.
>
> aux_get(): (2) couldn't open cache entry for media-video/kmplayer-0.6
>                Check for syntax error or corruption in the ebuild.
>
> What do they means ?

My finding on this (it did occurred to me in < 2.0.47-r2 portage as well) is 
that the /var/cache/edb/dep/<ebuild-related file> is of size 0 or less than 
what portage expect.

The solution I got from the IRC was

mv /var/cache/edb/dep <somewhere else>
emerge regen
rm -rf <somewhere else>

I hope I'm not incorrectely giving the dir name has the consequence could be 
desastrous so try at your own risk ;-)

-- 

Yannick Koehler

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 Out For Testing

[Thomas de Grenier de Latour]

On Tue, 18 Feb 2003 10:42:32 -0500
Yannick Koehler <yannick.koehler@colubris.com> wrote:

> I hope I'm not incorrectely giving the dir name has the consequence
> could be desastrous so try at your own risk ;-)

Thanks, it was the right dirname ;-) 
Now everything is okay, even when for non-root users.

-- 
Thomas.

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 Out For Testing

[Jeff Ames]

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

On Tue, Feb 18, 2003 at 10:42:32AM -0500, Yannick Koehler wrote:
> On February 17, 2003 01:28 pm, Thomas de Grenier de Latour wrote:
> >
> > aux_get(): (2) couldn't open cache entry for media-video/kmplayer-0.6
> >                Check for syntax error or corruption in the ebuild.
> 
> My finding on this (it did occurred to me in < 2.0.47-r2 portage as well) is 
> that the /var/cache/edb/dep/<ebuild-related file> is of size 0 or less than 
> what portage expect.
> 
> The solution I got from the IRC was
> 
> mv /var/cache/edb/dep <somewhere else>
> emerge regen
> rm -rf <somewhere else>

I got this problem as well, and the 'emerge regen' solution fixed it.  
However, I also got this error:

portage: 'portage' user or group missing. Please update baselayout
         and merge portage user(250) and group(250) into your passwd
         and group files. Non-root compilation is disabled until then.

re-emerging baselayout didn't fix it -- I had to add a portage user by
hand.  I don't know whether there also has to be an entry in shadow or
not, but I added one anyways.

Is this a new feature, or would emerging portage have deleted portage 
from /etc/passwd?  portage was in /etc/group after this emerge, so I 
didn't have to change anything there.

Jeff

-- 
Jeff Ames                               http://vorlon.cwru.edu/~ames/
GnuPG fingerprint: AE3F 617A 28B1 7D73 C91C  244A 19BD DF1A B9B5 9D8C
GnuPG key ID: 0xB9B59D8C (http://pgp.mit.edu)

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Portage-2.0.47-r2 Out For Testing

[Paul de Vrieze]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 419 bytes --]

On Tuesday 18 February 2003 21:52, Jeff Ames wrote:
> Is this a new feature, or would emerging portage have deleted portage
> from /etc/passwd?  portage was in /etc/group after this emerge, so I
> didn't have to change anything there.
>

Yes, this is a new feature, older portages could not run as a user

Paul

-- 
Paul de Vrieze
Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.cs.kun.nl/~pauldv

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Portage-2.0.47-r2 testing

[MAL]

Nick Jones wrote:
> Ok. Portage-2.0.47-r1 is ready for testing. It's got a lot of new
> stuff in it along with a good deal of fixes. Should be 'wicked-fast'
> as it has a lot of updates to caching code and the like. It is masked
> in package.mask. I need testers AND feedback. Gimme a holler with
> bugs and good/bad comments. Here or on bugs.gentoo.org is fine.

Ok, very odd problems..

Just tried to emerge xpm, and I get:

 >>> Unpacking source...
 >>> Unpacking xpm-3.4k.tar.gz to /var/tmp/portage/xpm-3.4k-r1/work
 >>> Source unpacked.
imake -DUseInstalled -I/usr/X11R6/lib/X11/config
/usr/bin/cpp: line 1: /usr/sbin/gcc-config: No such file or directory
/usr/bin/cpp: line 1: /usr/sbin/gcc-config: No such file or directory
/usr/bin/cpp: line 1: /usr/sbin/gcc-config: No such file or directory
etc... for several thousand lines, until ...
/usr/bin/cpp: cannot make pipe for command substitution: Too many open 
files in system

and then it fails.

So I look for the elusive /usr/sbin/gcc-config, and lo and behold it's 
missing?!  I ran it a few days ago!

So, promptly onto emerge gcc-config, which appears to emerge 
successfully, but produces the following messages:

  * Adding compat symlinks...
/usr/lib/portage/bin/newbin: line 13: dobin: command not found
/usr/lib/portage/bin/prepall: line 6: prepallman: command not found
/usr/lib/portage/bin/prepall: line 7: prepallinfo: command not found
/usr/lib/portage/bin/prepall: line 8: prepallstrip: command not found
 >>> Completed installing into /var/tmp/portage/gcc-config-1.3.1/image/

The build continues and completes... but.. gcc-config is not on the 
system?!  in either /usr/bin/gcc-config or /usr/sbin/gcc-config.
It looks like the build hasn't written any files out.

Originally I tried userpriv and usersandbox, but assuming these were 
causing this problem, I change my features line to just be the default, 
(nothing).  Same thing.

I just unmerged and remerged gcc-config, and the ebuild doesn't seem to 
be adding /usr/bin/gcc-config to the system.

This _could_ all be unrelated to portage, in which case it's 
coincidental with installing 2.0.47-r2.

Help :)
Cheers,
MAL


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 testing

[Benjamin Podszun]

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

Uhm.. Are you sure you didn't mess up something like rm -rf /usr ? ;)
Seriously: That gcc-config "disappears" is quite strange, but that
portage misses binaries is - evil. ;)

I installed 2.0.47-r2 as well on this laptop and I still have the
portage-binaries (dobin etc.) and gcc-config. I'd guess it's - uhm -
portage-unrelated.

Ben

On Wed, 2003-02-19 at 11:42, MAL wrote:
> Nick Jones wrote:
> > Ok. Portage-2.0.47-r1 is ready for testing. It's got a lot of new
> > stuff in it along with a good deal of fixes. Should be 'wicked-fast'
> > as it has a lot of updates to caching code and the like. It is masked
> > in package.mask. I need testers AND feedback. Gimme a holler with
> > bugs and good/bad comments. Here or on bugs.gentoo.org is fine.
> 
> Ok, very odd problems..
> 
> Just tried to emerge xpm, and I get:
> 
>  >>> Unpacking source...
>  >>> Unpacking xpm-3.4k.tar.gz to /var/tmp/portage/xpm-3.4k-r1/work
>  >>> Source unpacked.
> imake -DUseInstalled -I/usr/X11R6/lib/X11/config
> /usr/bin/cpp: line 1: /usr/sbin/gcc-config: No such file or directory
> /usr/bin/cpp: line 1: /usr/sbin/gcc-config: No such file or directory
> /usr/bin/cpp: line 1: /usr/sbin/gcc-config: No such file or directory
> etc... for several thousand lines, until ...
> /usr/bin/cpp: cannot make pipe for command substitution: Too many open 
> files in system
> 
> and then it fails.
> 
> So I look for the elusive /usr/sbin/gcc-config, and lo and behold it's 
> missing?!  I ran it a few days ago!
> 
> So, promptly onto emerge gcc-config, which appears to emerge 
> successfully, but produces the following messages:
> 
>   * Adding compat symlinks...
> /usr/lib/portage/bin/newbin: line 13: dobin: command not found
> /usr/lib/portage/bin/prepall: line 6: prepallman: command not found
> /usr/lib/portage/bin/prepall: line 7: prepallinfo: command not found
> /usr/lib/portage/bin/prepall: line 8: prepallstrip: command not found
>  >>> Completed installing into /var/tmp/portage/gcc-config-1.3.1/image/
> 
> The build continues and completes... but.. gcc-config is not on the 
> system?!  in either /usr/bin/gcc-config or /usr/sbin/gcc-config.
> It looks like the build hasn't written any files out.
> 
> Originally I tried userpriv and usersandbox, but assuming these were 
> causing this problem, I change my features line to just be the default, 
> (nothing).  Same thing.
> 
> I just unmerged and remerged gcc-config, and the ebuild doesn't seem to 
> be adding /usr/bin/gcc-config to the system.
> 
> This _could_ all be unrelated to portage, in which case it's 
> coincidental with installing 2.0.47-r2.
> 
> Help :)
> Cheers,
> MAL
> 
> 
> --
> gentoo-dev@gentoo.org mailing list
> 

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

Re: [gentoo-dev] Portage-2.0.47-r2 testing

[MAL]

Benjamin Podszun wrote:
> Uhm.. Are you sure you didn't mess up something like rm -rf /usr ? ;)
> Seriously: That gcc-config "disappears" is quite strange, but that
> portage misses binaries is - evil. ;)
> 
> I installed 2.0.47-r2 as well on this laptop and I still have the
> portage-binaries (dobin etc.) and gcc-config. I'd guess it's - uhm -
> portage-unrelated.
> 
> Ben

Nope, it's still intact, the system functions flawlessly otherwise... 
/usr isn't even a separate partition, (and no i'm not out of disk space ;)

/usr/lib/portage/bin/dobin etc _are_ there ! all of them, that's what's 
weirder.

I think the gcc-config ebuild is screwing up elsewhere internally.  By 
the looks of it, 1.3.1 creates a g++/gcc etc in /usr/bin.  I guess these 
are wrappers, or pointers to whatever current gcc is selected with 
gcc-config?
Can someone verify this?  I thought gcc was only meant to be selected 
via PATH.

MAL


--
gentoo-dev@gentoo.org mailing list

[gentoo-dev] telnet package in system

[Gustavo Felisberto]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The telnet package in the system profile is net-misc/netkit-telnetd . This 
package lacks ipv6 support. Maybe a good idea was to change it for 
net-misc/telnet-bsd . Bot packages have the same BSD license so no problem 
there.

Gustavo Felisberto
(aka HumpBack)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+U9oADysutLny1SoRAqBkAJ92pWCjFADKY0r29G9oqM1XLtVO0wCgrEp8
YRN5CdPnGGj008gZcs3xsLg=
=W2Dx
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 testing

[Terje Kvernes]

MAL <mal@komcept.com> writes:

  [ ... ]

> So I look for the elusive /usr/sbin/gcc-config, and lo and behold it's
> missing?!  I ran it a few days ago!
> 
> So, promptly onto emerge gcc-config, which appears to emerge
> successfully, but produces the following messages:
> 
>   * Adding compat symlinks...
> /usr/lib/portage/bin/newbin: line 13: dobin: command not found
> /usr/lib/portage/bin/prepall: line 6: prepallman: command not found
> /usr/lib/portage/bin/prepall: line 7: prepallinfo: command not found
> /usr/lib/portage/bin/prepall: line 8: prepallstrip: command not found
>  >>> Completed installing into /var/tmp/portage/gcc-config-1.3.1/image/
> 
> The build continues and completes... but.. gcc-config is not on the
> system?!  in either /usr/bin/gcc-config or /usr/sbin/gcc-config.
> It looks like the build hasn't written any files out.

  the same thing happens here.  reverting to portage 2.0.46-whatever
  fixed the problem.  this also made forkbombs on my box, since even
  restarting X uses the GCC preprocessor, which didn't quite do it's
  thing.  this is, for the record, a 1.2-based system.  I'll submit to
  bugzilla eventually, when it's not 4am.  :-)

  and yes, I've included MAL explicitly in the To:-header.

-- 
Terje

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 testing

[Eric Andresen]

On Wed, 2003-02-19 at 19:56, Terje Kvernes wrote:
> MAL <mal@komcept.com> writes:
> 
>   [ ... ]
> 
> > So I look for the elusive /usr/sbin/gcc-config, and lo and behold it's
> > missing?!  I ran it a few days ago!
> > 
> > So, promptly onto emerge gcc-config, which appears to emerge
> > successfully, but produces the following messages:
> > 
> >   * Adding compat symlinks...
> > /usr/lib/portage/bin/newbin: line 13: dobin: command not found
> > /usr/lib/portage/bin/prepall: line 6: prepallman: command not found
> > /usr/lib/portage/bin/prepall: line 7: prepallinfo: command not found
> > /usr/lib/portage/bin/prepall: line 8: prepallstrip: command not found
> >  >>> Completed installing into /var/tmp/portage/gcc-config-1.3.1/image/
> > 
> > The build continues and completes... but.. gcc-config is not on the
> > system?!  in either /usr/bin/gcc-config or /usr/sbin/gcc-config.
> > It looks like the build hasn't written any files out.
> 
>   the same thing happens here.  reverting to portage 2.0.46-whatever
>   fixed the problem.  this also made forkbombs on my box, since even
>   restarting X uses the GCC preprocessor, which didn't quite do it's
>   thing.  this is, for the record, a 1.2-based system.  I'll submit to
>   bugzilla eventually, when it's not 4am.  :-)
> 
>   and yes, I've included MAL explicitly in the To:-header.

I'm willing to bet that the problem is caused by that particular
ebuild's changing of the PATH. Just a thought. ;)

-- 
--Eric Andresen
  ndiin@asu.edu


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r1 testing

[Martin Larsen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nick Jones wrote:
> FEATURES=userpriv,usersandbox
>  * userpriv -- Allow portage to drop root and become portage:portage.
>    This will be an alternative to sandboxing for users. The $HOME of
>    the portage user is set to BUILD_PREFIX/homedir and is deleted for
>    every run.
>  * usersandbox -- Enable the sandbox along side userpriv. Recommended as
>    it shows invalid writes occuring in packages.

Have I missed something or does this break ccache in default install? AFAIK 
ccache stores the cache in ~/.ccache but with $HOME set to 
BUILD_PREFIX/homedir and delete for every run the point of using ccache kind 
of goes away. :-)

Martin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+VIahDQBX9e7xQ8cRAg2bAJ9GIHu0gap+6ChqF2Tn/QP5xiJ2ZACg0Qp+
HZLe4thvmM8ZO0l4HxCUKpI=
=MH8n
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 testing

[MAL]

Terje Kvernes wrote:
>   the same thing happens here.  reverting to portage 2.0.46-whatever
>   fixed the problem.  this also made forkbombs on my box, since even
>   restarting X uses the GCC preprocessor, which didn't quite do it's
>   thing.  this is, for the record, a 1.2-based system.  I'll submit to
>   bugzilla eventually, when it's not 4am.  :-)

For the record, i'm on a was-1.2 system that I upgraded to 1.4 with the 
update scripts and info here:
http://www.gentoo.org/doc/en/upgrade-to-gentoo-1.4.xml

A good chunk of my system is probably still linked against the old 
libraries, as I emerged the compat libs instead of doing an emerge -e world.

>   and yes, I've included MAL explicitly in the To:-header.

I'm touched.


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 testing

[MAL]

Eric Andresen wrote:
> On Wed, 2003-02-19 at 19:56, Terje Kvernes wrote:
> I'm willing to bet that the problem is caused by that particular
> ebuild's changing of the PATH. Just a thought. ;)

I don't see how.. I have a few (>3) 1.4 systems that went through the 
upgrade fine, and looking at them, I can't see any difference in the 
PATH settings, between them and my updated-1.2 system.

MAL


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 testing

[MAL]

MAL wrote:
> Terje Kvernes wrote:
> 
>>   the same thing happens here.  reverting to portage 2.0.46-whatever
>>   fixed the problem.  this also made forkbombs on my box, since even
>>   restarting X uses the GCC preprocessor, which didn't quite do it's
>>   thing.  this is, for the record, a 1.2-based system.  I'll submit to
>>   bugzilla eventually, when it's not 4am.  :-)
> 
> For the record, i'm on a was-1.2 system that I upgraded to 1.4 with the 
> update scripts and info here:
> http://www.gentoo.org/doc/en/upgrade-to-gentoo-1.4.xml
> 
> A good chunk of my system is probably still linked against the old 
> libraries, as I emerged the compat libs instead of doing an emerge -e 
> world.

Sorry about replying to my own post, but for the record, downgrading 
portage to 2.0.46-r12 allowed me to emerge gcc-config successfully and 
then emerge xpm fine.

Please could someone explain why this happened?  Don't want to be stuck 
on a version of portage forever :/

Cheers,
MAL


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 testing

[Terje Kvernes]

MAL <mal@komcept.com> writes:

  [ ... ]

> Sorry about replying to my own post, but for the record, downgrading
> portage to 2.0.46-r12 allowed me to emerge gcc-config successfully
> and then emerge xpm fine.

  gaaah.  my apologies, I reported the bug and the same "fix" but
  forgot to include that information.  I'll blame the time of night.

  <url: http://bugs.gentoo.org/show_bug.cgi?id=16047 >
 
> Please could someone explain why this happened?  Don't want to be
> stuck on a version of portage forever :/

  I think upgrading to a newer portage will be "safe", but emerging
  gcc-config with the new portage won't be safe.  or something like
  that.  I'll test things once I eventually get a frigging
  RAID-cabinet working at work and eventually catch some sleep.

-- 
Terje

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 testing

[Terje Kvernes]

MAL <mal@komcept.com> writes:

> Terje Kvernes wrote:
>
> > and yes, I've included MAL explicitly in the To:-header.
> 
> I'm touched.

  well, I wasn't sure you were on the list, and I wanted to make sure
  you knew you weren't alone.  sorry.  :-/

-- 
Terje

--
gentoo-dev@gentoo.org mailing list

RE: [gentoo-dev] Portage-2.0.47-r2 testing

[Martin, Stephen]

Is 2.0.47-r2 *supposed* to be in stable?  I did an emerge -u world today and
it upgraded portage to 47.  I too am now having all kinds of problems with
gcc-config.


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 testing

[MAL]

Martin, Stephen wrote:
> Is 2.0.47-r2 *supposed* to be in stable?  I did an emerge -u world today and
> it upgraded portage to 47.  I too am now having all kinds of problems with
> gcc-config.
> 

Supposedly yes :/

I'm sticking with 2.0.46 until someone states what the cause is.

Is, or was, your system, gentoo 1.2 ?

MAL


--
gentoo-dev@gentoo.org mailing list

RE: [gentoo-dev] Portage-2.0.47-r2 testing

[Martin, Stephen]

I believe the system was 1.4_rc1.



-----Original Message-----
From: MAL [mailto:mal@komcept.com] 
Sent: Thursday, February 20, 2003 9:36 AM
To: Martin, Stephen
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Portage-2.0.47-r2 testing

Martin, Stephen wrote:
> Is 2.0.47-r2 *supposed* to be in stable?  I did an emerge -u world today
and
> it upgraded portage to 47.  I too am now having all kinds of problems with
> gcc-config.
> 

Supposedly yes :/

I'm sticking with 2.0.46 until someone states what the cause is.

Is, or was, your system, gentoo 1.2 ?

MAL


--
gentoo-dev@gentoo.org mailing list

--
gentoo-dev@gentoo.org mailing list

RE: [gentoo-dev] Portage-2.0.47-r2 testing

[Martin, Stephen]

OK, my bad.  It doesn't necessarily seem to be a portage problem on my end.
I downgraded to 2.0.46 and I'm still having problems.  I think it might be a
problem with the specific packages I'm trying to emerge.  When trying to
emerge php-4.3.1 I get a message saying that fork() isn't supported on my
platform.


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 testing

[Eric Andresen]

I was refering to lines 22 through 31 of gcc-config-1.3.1.ebuild (and
similar for other gcc-config ebuilds). My guess is the changing of the
way that portage handled things made this method no longer work.

On Thu, 2003-02-20 at 03:20, MAL wrote:
> Eric Andresen wrote:
> > On Wed, 2003-02-19 at 19:56, Terje Kvernes wrote:
> > I'm willing to bet that the problem is caused by that particular
> > ebuild's changing of the PATH. Just a thought. ;)
> 
> I don't see how.. I have a few (>3) 1.4 systems that went through the 
> upgrade fine, and looking at them, I can't see any difference in the 
> PATH settings, between them and my updated-1.2 system.
> 
> MAL
-- 
--Eric Andresen
  ndiin@asu.edu


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 testing

[Paul de Vrieze]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 537 bytes --]

On Thursday 20 February 2003 18:06, Martin, Stephen wrote:
> OK, my bad.  It doesn't necessarily seem to be a portage problem on my end.
> I downgraded to 2.0.46 and I'm still having problems.  I think it might be
> a problem with the specific packages I'm trying to emerge.  When trying to
> emerge php-4.3.1 I get a message saying that fork() isn't supported on my
> platform.
>

php aparently doesn't like jdk's before 1.4

Paul

-- 
Paul de Vrieze
Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Portage-2.0.47-r2 'gcc-config' issues

[Nick Jones]

>>> I'm willing to bet that the problem is caused by that particular
>>> ebuild's changing of the PATH. Just a thought. ;)

>> I don't see how.. I have a few (>3) 1.4 systems that went through the 
>> upgrade fine, and looking at them, I can't see any difference in the 
>> PATH settings, between them and my updated-1.2 system.

Close, but not quite. I believe we've nailed this problem down.
The only causes I see and have fixed are non-root sudo's or non
'su -' actions invoking emerge. The user's bashrc is imported into
the scripts running within portage and consequently overwriting the
settings within ebuild.sh.

System that actually become root via 'su -' or simply login as root
will not experience these problems, and that is the reason no one
noticed the 'problem' until now.

I've masked 2.0.47-r2 as of ~12 hours ago, and will keep it that way
until I get the handling for not-quite-root nailed down and verified.

On a related note... I'm _still_ interested in more testers.
Portage-2.0.47-r3 should be out within the next 24 hours.

--NJ

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 'gcc-config' issues

[Terje Kvernes]

Nick Jones <carpaski@twobit.net> writes:

  [ ... ]

> System that actually become root via 'su -' or simply login as root
> will not experience these problems, and that is the reason no one
> noticed the 'problem' until now.

  I got hit by this bug after doing "ssh root@hostname".  that should
  have worked, right?
 
  [ ... ]

-- 
Terje

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 'gcc-config' issues

[MAL]

Nick Jones wrote:
> System that actually become root via 'su -' or simply login as root
> will not experience these problems, and that is the reason no one
> noticed the 'problem' until now.

I was SSH'd in and it still happened.

MAL


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Portage-2.0.47-r2 'gcc-config' issues

[Nick Jones]

Ok... Can I get you both to test some patches then? Or anyone/everyone
that has this problem via ssh. First patch is against portage.py.

http://gentoo.twobit.net/portage/portage.py-2.0.47_r2-missing_bins.diff
cd /usr/lib/python2.2/site-packages/
patch < ~/portage.py-2.0.47_r2-missing_bins.diff

Then test it to see how it goes... If it works... Let me know... if it
fails... Can you do the following patch and get me the outputs:

http://gentoo.twobit.net/portage/ebuild.sh-2.0.47_r2-env_test.diff
cd /usr/lib/portage/bin/
patch < ~/ebuild.sh-2.0.47_r2-env_test.diff

FEATURES=keeptemp emerge gcc-config
(Once it breaks, you can control-C)
cd /var/tmp/portage/gcc-config-1.3.1/temp
tar jcvf env-reg-yourname.tar.bz2 env.*
anon ftp that to ftp.twobit.net into /incoming, or post it for me.

su -
FEATURES=keeptemp emerge gcc-config
(Once it breaks, you can control-C)
cd /var/tmp/portage/gcc-config-1.3.1/temp
tar jcvf env-root-yourname.tar.bz2 env.*
anon ftp that to ftp.twobit.net into /incoming, or post it for me.


--
gentoo-dev@gentoo.org mailing list