1 |
Frank Peters <frank.peters@×××××××.net> posted |
2 |
20090803022804.b9e5a8a0.frank.peters@×××××××.net, excerpted below, on |
3 |
Mon, 03 Aug 2009 02:28:04 -0400: |
4 |
|
5 |
> On Mon, 03 Aug 2009 01:21:40 -0500 |
6 |
> Lance Lassetter <lancelassetter@×××××.com> wrote: |
7 |
> |
8 |
> |
9 |
> |
10 |
>> # bash --version |
11 |
>> GNU bash, version 3.2.39(1)-release (x86_64-pc-linux-gnu) Copyright (C) |
12 |
>> 2007 Free Software Foundation, Inc. |
13 |
>> |
14 |
>> |
15 |
>> |
16 |
> Thanks again. I thought so. My bash version is 4.0.28(2) and there |
17 |
> obviously have been some changes. Version 3.2 goes back a long way. |
18 |
> Another program where I have experienced problems is eselect, which is |
19 |
> another bash script. Again there was a syntax fault. |
20 |
> |
21 |
> I will have to look into this a little better in the morning and maybe |
22 |
> file a bug report. |
23 |
|
24 |
FWIW, here (and see below for the Gentoo versions): |
25 |
|
26 |
GNU bash, version 4.0.28(2)-release (x86_64-pc-linux-gnu) |
27 |
|
28 |
That's current ~amd64 as of yesterday's sync. |
29 |
|
30 |
I haven't run python-updater in some time but it ran fine when I ran it |
31 |
last. I do need to run it again since python-3.1 was just in yesterday's |
32 |
updates, tho, and see what happens. |
33 |
|
34 |
Meanwhile, I've had exactly zero problems with eselect, but I don't use |
35 |
that many modules of it as I manage a lot of what it does, like the |
36 |
kernel symlink, the make.profile symlink, etc, manually. |
37 |
|
38 |
Here's my bash, python and python-updater versions: |
39 |
|
40 |
$equery l bash python |
41 |
* Searching for bash ... |
42 |
[IP-] [ ~] app-shells/bash-4.0_p28 (0) |
43 |
|
44 |
* Searching for python ... |
45 |
[IP-] [ ~] dev-lang/python-2.6.2-r1 (2.6) |
46 |
[IP-] [ ~] dev-lang/python-3.1 (3.1) |
47 |
|
48 |
* Searching for python-updater ... |
49 |
[IP-] [ ~] app-admin/python-updater-0.7 (0) |
50 |
$ |
51 |
|
52 |
Are you full ~amd64, or did you package.keyword bash? If you're running |
53 |
a mixed ~arch/stable system, it's possible that's the problem, tho it |
54 |
doesn't look like it should be python-updater itself, since 0.7 is the |
55 |
highest available for both stable and ~arch. |
56 |
|
57 |
Here's a depth-2 depends graph for the 4.0 p28 bash version: |
58 |
|
59 |
$equery g --depth=2 bash-4.0_p28 |
60 |
* Searching for bash ... |
61 |
* dependency graph for app-shells/bash-4.0_p28: |
62 |
`-- app-shells/bash-4.0_p28 |
63 |
`-- sys-libs/ncurses-5.7-r1 |
64 |
`-- sys-libs/gpm-1.20.6 [gpm] |
65 |
`-- sec-policy/selinux-gpm (unable to resolve: package masked or |
66 |
removed) |
67 |
`-- virtual/libintl-0 (virtual/libintl) [nls] |
68 |
`-- sys-devel/gettext-0.17 [elibc_FreeBSD] |
69 |
[ app-shells/bash-4.0_p28 stats: packages (5), max depth (2) ] |
70 |
$ |
71 |
|
72 |
python-updater itself doesn't seem to have any significant dependencies, |
73 |
just a package manager (portage, pkgcore or paludis), at the first level. |
74 |
|
75 |
-- |
76 |
Duncan - List replies preferred. No HTML msgs. |
77 |
"Every nonfree program has a lord, a master -- |
78 |
and if you use the program, he is your master." Richard Stallman |