On Mon, 2009-08-03 at 07:12 +0000, Duncan wrote: > Frank Peters <frank.pet...@comcast.net> posted > 20090803022804.b9e5a8a0.frank.pet...@comcast.net, excerpted below, on > Mon, 03 Aug 2009 02:28:04 -0400: > > > On Mon, 03 Aug 2009 01:21:40 -0500 > > Lance Lassetter <lancelasset...@gmail.com> wrote: > > > > > > > >> # bash --version > >> GNU bash, version 3.2.39(1)-release (x86_64-pc-linux-gnu) Copyright (C) > >> 2007 Free Software Foundation, Inc. > >> > >> > >> > > Thanks again. I thought so. My bash version is 4.0.28(2) and there > > obviously have been some changes. Version 3.2 goes back a long way. > > Another program where I have experienced problems is eselect, which is > > another bash script. Again there was a syntax fault. > > > > I will have to look into this a little better in the morning and maybe > > file a bug report. > > FWIW, here (and see below for the Gentoo versions): > > GNU bash, version 4.0.28(2)-release (x86_64-pc-linux-gnu) > > That's current ~amd64 as of yesterday's sync. > > I haven't run python-updater in some time but it ran fine when I ran it > last. I do need to run it again since python-3.1 was just in yesterday's > updates, tho, and see what happens. > > Meanwhile, I've had exactly zero problems with eselect, but I don't use > that many modules of it as I manage a lot of what it does, like the > kernel symlink, the make.profile symlink, etc, manually. > > Here's my bash, python and python-updater versions: > > $equery l bash python > * Searching for bash ... > [IP-] [ ~] app-shells/bash-4.0_p28 (0) > > * Searching for python ... > [IP-] [ ~] dev-lang/python-2.6.2-r1 (2.6) > [IP-] [ ~] dev-lang/python-3.1 (3.1) > > * Searching for python-updater ... > [IP-] [ ~] app-admin/python-updater-0.7 (0) > $ > > Are you full ~amd64, or did you package.keyword bash? If you're running > a mixed ~arch/stable system, it's possible that's the problem, tho it > doesn't look like it should be python-updater itself, since 0.7 is the > highest available for both stable and ~arch. > > Here's a depth-2 depends graph for the 4.0 p28 bash version: > > $equery g --depth=2 bash-4.0_p28 > * Searching for bash ... > * dependency graph for app-shells/bash-4.0_p28: > `-- app-shells/bash-4.0_p28 > `-- sys-libs/ncurses-5.7-r1 > `-- sys-libs/gpm-1.20.6 [gpm] > `-- sec-policy/selinux-gpm (unable to resolve: package masked or > removed) > `-- virtual/libintl-0 (virtual/libintl) [nls] > `-- sys-devel/gettext-0.17 [elibc_FreeBSD] > [ app-shells/bash-4.0_p28 stats: packages (5), max depth (2) ] > $ > > python-updater itself doesn't seem to have any significant dependencies, > just a package manager (portage, pkgcore or paludis), at the first level. >
it's mixed. only select few packages installed ~x86 and their required deps. i would, personally, never go full blown ~x86 due to core packages needing to be stable.
