[PALUDIS] Support thread (current v. 0.26.*) - Part 4

[TheNewOsiris]

I upgraded to GCC 4.2.2 and got the following error (seems it can't find GLIBCXX_3.4.9):

Code: Select all

creating accerso
creating man-accerso
./man-accerso > accerso.1
/var/tmp/paludis/sys-apps/paludis-0.26.0_alpha4/work/paludis-0.26.0_alpha4/src/clients/accerso/.libs/lt-man-accerso: /usr/lib/gcc/i586-pc-linux-gnu/4.1.1/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /var/tmp/paludis/sys-apps/paludis-0.26.0_alpha4/work/paludis-0.26.0_alpha4/src/clients/accerso/.libs/lt-man-accerso)
/var/tmp/paludis/sys-apps/paludis-0.26.0_alpha4/work/paludis-0.26.0_alpha4/src/clients/accerso/.libs/lt-man-accerso: /usr/lib/gcc/i586-pc-linux-gnu/4.1.1/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /var/tmp/paludis/sys-apps/paludis-0.26.0_alpha4/work/paludis-0.26.0_alpha4/paludis/args/.libs/libpaludisargs.so.26)
/var/tmp/paludis/sys-apps/paludis-0.26.0_alpha4/work/paludis-0.26.0_alpha4/src/clients/accerso/.libs/lt-man-accerso: /usr/lib/gcc/i586-pc-linux-gnu/4.1.1/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /var/tmp/paludis/sys-apps/paludis-0.26.0_alpha4/work/paludis-0.26.0_alpha4/paludis/.libs/libpaludis.so.26)
/var/tmp/paludis/sys-apps/paludis-0.26.0_alpha4/work/paludis-0.26.0_alpha4/src/clients/accerso/.libs/lt-man-accerso: /usr/lib/gcc/i586-pc-linux-gnu/4.1.1/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /var/tmp/paludis/sys-apps/paludis-0.26.0_alpha4/work/paludis-0.26.0_alpha4/paludis/selinux/.libs/libpaludisselinux.so.26)
/var/tmp/paludis/sys-apps/paludis-0.26.0_alpha4/work/paludis-0.26.0_alpha4/src/clients/accerso/.libs/lt-man-accerso: /usr/lib/gcc/i586-pc-linux-gnu/4.1.1/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /var/tmp/paludis/sys-apps/paludis-0.26.0_alpha4/work/paludis-0.26.0_alpha4/paludis/util/.libs/libpaludisutil.so.26)
make[5]: *** [accerso.1] Error 1
make[5]: Leaving directory `/var/tmp/paludis/sys-apps/paludis-0.26.0_alpha4/work/paludis-0.26.0_alpha4/src/clients/accerso'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/var/tmp/paludis/sys-apps/paludis-0.26.0_alpha4/work/paludis-0.26.0_alpha4/src/clients/accerso'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/paludis/sys-apps/paludis-0.26.0_alpha4/work/paludis-0.26.0_alpha4/src/clients'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/paludis/sys-apps/paludis-0.26.0_alpha4/work/paludis-0.26.0_alpha4/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/paludis/sys-apps/paludis-0.26.0_alpha4/work/paludis-0.26.0_alpha4'
make: *** [all] Error 2

!!! ERROR in sys-apps/paludis-0.26.0_alpha4:
!!! In src_compile at line 3394
!!! emake failed

!!! Call stack:
!!!    * src_compile (/var/tmp/paludis/sys-apps/paludis-0.26.0_alpha4/temp/loadsaveenv:3394)
!!!    * ebuild_f_compile (/usr/libexec/paludis/src_compile.bash:51)
!!!    * ebuild_main (/usr/libexec/paludis/ebuild.bash:363)
!!!    * main (/usr/libexec/paludis/ebuild.bash:381)

die trap: exiting with error.

There is no package called GLIBCXX in portage. Wtf?

EDIT:
I also have one directory that's located at: /usr/lib/gcc/i586-pc-linux-gnu.
and one directory that's located at: /usr/lib/gcc/i686-pc-linux-gnu.

Paludis seems to be loading libstdc++.so.6 from the first (i586) directory. I don't know if this is normal.
I tried to re-install libstdc++ and it is installed in the same place.

Here is my paludis --info:

Code: Select all

CXX:         g++ 4.1.1 (Gentoo 4.1.1-r1)
CXXFLAGS:    -march=prescott -O2 -pipe -fomit-frame-pointer
LDFLAGS:
DATADIR:     /usr/share
LIBDIR:      /usr/lib
LIBEXECDIR:  /usr/libexec
SYSCONFDIR:  /etc
stdlib:      GNU libstdc++ 20060524
libebt:      1.3.0
libwrapiter: 1.0.0
sandbox:     enabled

and gcc -v:

Code: Select all

Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: /var/tmp/paludis/sys-devel/gcc-4.2.2/work/gcc-4.2.2/configure --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/4.2.2 --includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.2.2/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.2.2 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.2.2/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.2.2/info --with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.2.2/include/g++-v4 --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --enable-secureplt --disable-libunwind-exceptions --disable-multilib --enable-libmudflap --disable-libssp --enable-java-awt=gtk --with-arch=i686 --enable-languages=c,c++,java,treelang,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
Thread model: posix
gcc version 4.2.2 (Gentoo 4.2.2 p1.0)

[slycordinator]

You've got too many things going on at once; you've upgraded gcc AND changed your CHOST at the same time. Just the latter can screw things up royally but with the former that makes for a doozy.

[R. Bosch]

Hi, all!

I try to build a git-based package (compiz) on an off-line system. I found that git_fetch is the culprit as fetching goes, but even if I try to set

Code: Select all

export SKIP_FUNCTIONS=git_fetch

to /etc/paludis/bashrc , paludis dies
I could swear I read somewhere how to avoid this fetch, but can't find it at all on the net.
Could be I'm too strict on searching on git_fetch or scm packages?

Which reminds me that I can do a weekly or even daily update of the scm packages (see --dl-reinstall-scm in the man page) but don't see any option on preventing the git-src tree being updated for off-line systems

Thanks in advance!

[TheNewOsiris]

I fixed it. I just removed gcc 4.1.1 and recompiled libstdc++. Paludis finished compiling. Now it's time to re-merge system/world.

[R. Bosch]

Hello again,

I stumbled on "forgotten" updates. I get a list of updates to be done that are missed when I run paludis -ip world.
I got the list with

Code: Select all

paludis -i openoffice xfce4 gimp inkscape --dl-reinstall always -p | grep "^\*" | grep -v R
* x11-proto/glproto [U 1.4.8 -> 1.4.9]
* dev-python/setuptools [U 0.6_rc6 -> 0.6_rc7-r1]
* x11-themes/gtk-engines-xfce [U 2.4.1-r1 -> 2.4.2]
* xfce-base/xfce-mcs-plugins [U 4.4.1-r1 -> 4.4.2]
* xfce-extra/exo [U 0.3.2 -> 0.3.4]
* xfce-base/thunar [U 0.8.0-r3 -> 0.9.0-r1]
* xfce-base/xfce4-panel [U 4.4.1-r1 -> 4.4.2]
* xfce-base/xfwm4 [U 4.4.1-r1 -> 4.4.2]
* xfce-base/xfce-utils [U 4.4.1-r1 -> 4.4.2-r1]
* xfce-base/xfdesktop [U 4.4.1-r1 -> 4.4.2]
* xfce-base/xfce4-session [U 4.4.1 -> 4.4.2]
* xfce-extra/xfce4-icon-theme [U 4.4.1 -> 4.4.2]
* xfce-extra/xfce4-mixer [U 4.4.1 -> 4.4.2]
* xfce-base/xfprint [U 4.4.1 -> 4.4.2]
* xfce-extra/mousepad [U 0.2.12 -> 0.2.13]
* xfce-extra/xfwm4-themes [U 4.4.1 -> 4.4.2]
* x11-libs/vte [U 0.16.9 -> 0.16.10]
* xfce-extra/terminal [U 0.2.6_p25931 -> 0.2.8]
* xfce-extra/xfce4-appfinder [U 4.4.1 -> 4.4.2]
* x11-apps/xwininfo [U 1.0.2 -> 1.0.3]
* xfce-base/xfce4 [U 4.4.1 -> 4.4.2] <target>

I have PALUDIS_OPTIONS="--log-level silent --show-reasons none --show-use-descriptions none --dl-reinstall if-use-changed"
Are there prerequests that a package has to comply with to get updated through paludis -ip world?

[slycordinator]

paludis defaults to only updating RDEPS of packages.

Lets say you installed a program that has a build-time dependency of ">=dev-python/epydoc-2.0" and so when you installed that program it installed epydoc-2.0.

Then later they put epydoc-2.1 in the tree and later your program got an update but the build dependency stayed the same. So when you go to install the new version of your favorite program paludis says to itself that the installed epydoc-2.0 meets the dependency so there's no need to install this newer version.

So to get everything updated you can add

Code: Select all

--dl-deps-default pre-or-post

to your default setting.

[R. Bosch]

paludis defaults to only updating RDEPS of packages.
So to get everything updated you can add

Code: Select all

--dl-deps-default pre-or-post

to your default setting.

So added. Thanks!

[jorges]

Can someone point me to documentation/info about the "categories" file under profiles? I thought that only the categories, e.g. "sys-apps", included in that file were picked by paludis, but with the latest paludis, even after commenting some categories it keeps trying to install packages belonging to them. Has this changed or am I doing something wrong?

jorges

[kernelOfTruth]

does paludis still need a symbolic to /var/lib/portage/world ?in its own directory ?

[slycordinator]

does paludis still need a symbolic to /var/lib/portage/world ?in its own directory ?

If you use the portage2paludis.bash script then it makes /var/db/pkg/world a symlink to /var/lib/portage/world

Though if you set up paludis manually that symlink likely won't exist.

[ikshaar]

What is/should be /var/db/pkg/.cache/provides ??

Building target list... paludis@1197921886: [WARNING] Provides cache at '/var/db/pkg/.cache/provides' is not a regular file.

I found the "explanation" on the getting started page but it is lacking details. Should I create the file ? what is in it ? or how to generate it ?

[krisse]

Trying to install 0.26.0_alpha5, but install fails at applying paludis-0.26.0_alpha5-env.patch.

I'm not sure if the following helps you or not, but:

Code: Select all

***** paludis-0.26.0_alpha5-env.patch *****

===========================================

PATCH COMMAND:   patch -p0 -g0 -E --no-backup-if-mismatch < /mnt/portage/portage/sys-apps/paludis/fil
es/paludis-0.26.0_alpha5-env.patch

===========================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: trunk/paludis/repositories/e/ebuild/ebuild.bash
|===================================================================
|--- trunk/paludis/repositories/e/ebuild/ebuild.bash (revision 4127)
|+++ trunk/paludis/repositories/e/ebuild/ebuild.bash (revision 4168)
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
===========================================

PATCH COMMAND:   patch -p1 -g0 -E --no-backup-if-mismatch < /mnt/portage/portage/sys-apps/paludis/fil
es/paludis-0.26.0_alpha5-env.patch

===========================================
patching file paludis/repositories/e/ebuild/ebuild.bash
Hunk #1 FAILED at 256.
1 out of 1 hunk FAILED -- saving rejects to file paludis/repositories/e/ebuild/ebuild.bash.rej
===========================================

PATCH COMMAND:   patch -p2 -g0 -E --no-backup-if-mismatch < /mnt/portage/portage/sys-apps/paludis/files/paludis-0.26.0_alpha5-env.patch

===========================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: trunk/paludis/repositories/e/ebuild/ebuild.bash
|===================================================================
|--- trunk/paludis/repositories/e/ebuild/ebuild.bash (revision 4127)
|+++ trunk/paludis/repositories/e/ebuild/ebuild.bash (revision 4168)
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
===========================================

PATCH COMMAND:   patch -p3 -g0 -E --no-backup-if-mismatch < /mnt/portage/portage/sys-apps/paludis/files/paludis-0.26.0_alpha5-env.patch

===========================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: trunk/paludis/repositories/e/ebuild/ebuild.bash
|===================================================================
|--- trunk/paludis/repositories/e/ebuild/ebuild.bash (revision 4127)
|+++ trunk/paludis/repositories/e/ebuild/ebuild.bash (revision 4168)
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
===========================================

PATCH COMMAND:   patch -p4 -g0 -E --no-backup-if-mismatch < /mnt/portage/portage/sys-apps/paludis/files/paludis-0.26.0_alpha5-env.patch

===========================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: trunk/paludis/repositories/e/ebuild/ebuild.bash
|===================================================================
|--- trunk/paludis/repositories/e/ebuild/ebuild.bash (revision 4127)
|+++ trunk/paludis/repositories/e/ebuild/ebuild.bash (revision 4168)
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored

Am I missing some files or what?

[aidy]

Having the same problem I think:

Code: Select all

orchestron adriaan # emerge paludis
Calculating dependencies... done!
>>> Verifying ebuild Manifests...

>>> Emerging (1 of 1) sys-apps/paludis-0.26.0_alpha5-r1 to /
 * paludis-0.26.0_alpha5.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                                                                                         [ ok ]
 * checking ebuild checksums ;-) ...                                                                                                                     [ ok ]
 * checking auxfile checksums ;-) ...                                                                                                                    [ ok ]
 * checking miscfile checksums ;-) ...                                                                                                                   [ ok ]
 * checking paludis-0.26.0_alpha5.tar.bz2 ;-) ...                                                                                                        [ ok ]
>>> Unpacking source...
>>> Unpacking paludis-0.26.0_alpha5.tar.bz2 to /var/tmp/portage/sys-apps/paludis-0.26.0_alpha5-r1/work
 * Applying paludis-0.26.0_alpha5-env.patch ...

 * Failed Patch: paludis-0.26.0_alpha5-env.patch !
 *  ( /usr/portage/sys-apps/paludis/files/paludis-0.26.0_alpha5-env.patch )
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/sys-apps/paludis-0.26.0_alpha5-r1/temp/paludis-0.26.0_alpha5-env.patch-31335.out

 * 
 * ERROR: sys-apps/paludis-0.26.0_alpha5-r1 failed.
 * Call stack:
 *                         ebuild.sh, line 1701:  Called dyn_unpack
 *                         ebuild.sh, line  817:  Called qa_call 'src_unpack'
 *                         ebuild.sh, line   44:  Called src_unpack
 *   paludis-0.26.0_alpha5-r1.ebuild, line   74:  Called epatch '/usr/portage/sys-apps/paludis/files/paludis-0.26.0_alpha5-env.patch'
 *                     eutils.eclass, line  304:  Called die
 * The specific snippet of code:
 *                              die "Failed Patch: ${patchname}!"
 *  The die message:
 *   Failed Patch: paludis-0.26.0_alpha5-env.patch!
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/sys-apps/paludis-0.26.0_alpha5-r1/temp/build.log'.
 * 

 * Messages for package sys-apps/paludis-0.26.0_alpha5-r1:

 * Failed Patch: paludis-0.26.0_alpha5-env.patch !
 *  ( /usr/portage/sys-apps/paludis/files/paludis-0.26.0_alpha5-env.patch )
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/sys-apps/paludis-0.26.0_alpha5-r1/temp/paludis-0.26.0_alpha5-env.patch-31335.out
 * 
 * ERROR: sys-apps/paludis-0.26.0_alpha5-r1 failed.
 * Call stack:
 *                         ebuild.sh, line 1701:  Called dyn_unpack
 *                         ebuild.sh, line  817:  Called qa_call 'src_unpack'
 *                         ebuild.sh, line   44:  Called src_unpack
 *   paludis-0.26.0_alpha5-r1.ebuild, line   74:  Called epatch '/usr/portage/sys-apps/paludis/files/paludis-0.26.0_alpha5-env.patch'
 *                     eutils.eclass, line  304:  Called die
 * The specific snippet of code:
 *                              die "Failed Patch: ${patchname}!"
 *  The die message:
 *   Failed Patch: paludis-0.26.0_alpha5-env.patch!
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/sys-apps/paludis-0.26.0_alpha5-r1/temp/build.log'.
 * 

[Bones]

I'm having this same problem with paludis-0.26.0_alpha5:

Code: Select all

***** paludis-0.26.0_alpha5-env.patch *****

===========================================

PATCH COMMAND:   patch -p0 -g0 -E --no-backup-if-mismatch < /usr/portage/sys-apps/paludis/files/paludis-0.26.0_alpha5-env.patch

===========================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: trunk/paludis/repositories/e/ebuild/ebuild.bash
|===================================================================
|--- trunk/paludis/repositories/e/ebuild/ebuild.bash (revision 4127)
|+++ trunk/paludis/repositories/e/ebuild/ebuild.bash (revision 4168)
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
===========================================

PATCH COMMAND:   patch -p1 -g0 -E --no-backup-if-mismatch < /usr/portage/sys-apps/paludis/files/paludis-0.26.0_alpha5-env.patch

===========================================
patching file paludis/repositories/e/ebuild/ebuild.bash
Hunk #1 FAILED at 256.
1 out of 1 hunk FAILED -- saving rejects to file paludis/repositories/e/ebuild/ebuild.bash.rej
===========================================

PATCH COMMAND:   patch -p2 -g0 -E --no-backup-if-mismatch < /usr/portage/sys-apps/paludis/files/paludis-0.26.0_alpha5-env.patch

===========================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: trunk/paludis/repositories/e/ebuild/ebuild.bash
|===================================================================
|--- trunk/paludis/repositories/e/ebuild/ebuild.bash (revision 4127)
|+++ trunk/paludis/repositories/e/ebuild/ebuild.bash (revision 4168)
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
===========================================

PATCH COMMAND:   patch -p3 -g0 -E --no-backup-if-mismatch < /usr/portage/sys-apps/paludis/files/paludis-0.26.0_alpha5-env.patch

===========================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: trunk/paludis/repositories/e/ebuild/ebuild.bash
|===================================================================
|--- trunk/paludis/repositories/e/ebuild/ebuild.bash (revision 4127)
|+++ trunk/paludis/repositories/e/ebuild/ebuild.bash (revision 4168)
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
===========================================

PATCH COMMAND:   patch -p4 -g0 -E --no-backup-if-mismatch < /usr/portage/sys-apps/paludis/files/paludis-0.26.0_alpha5-env.patch

===========================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: trunk/paludis/repositories/e/ebuild/ebuild.bash
|===================================================================
|--- trunk/paludis/repositories/e/ebuild/ebuild.bash (revision 4127)
|+++ trunk/paludis/repositories/e/ebuild/ebuild.bash (revision 4168)
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored

[aidy]

the bug's fixed, you just have to wait till it hits the mirrors

[krisse]

the bug's fixed, you just have to wait till it hits the mirrors

... Which it now has. 0.26.0_alpha5 is being paluded as we speak.

[areian]

Paludis dies at "Starting builtin_loadenv" no matter what package I try to install/update.

Code: Select all

Checking 'readline-5.2.tar.gz'... ok
Checking 'readline52-001'... ok
Checking 'readline52-002'... ok
Checking 'readline52-003'... ok
Checking 'readline52-004'... ok
Checking 'readline52-005'... ok
Checking 'readline52-006'... ok
Checking 'readline52-007'... ok
Checking 'readline52-008'... ok
Checking 'readline52-009'... ok
Checking 'readline52-010'... ok
Checking 'readline52-011'... ok
Checking 'readline52-012'... ok
>>> Running ebuild phase prepare as root:root...
>>> Starting builtin_prepare
>>> Done builtin_prepare
>>> Completed ebuild phase prepare
>>> Running ebuild phases init saveenv as paludisbuild:paludisbuild...
>>> Starting builtin_init
>>> Done builtin_init
>>> Starting builtin_saveenv
>>> Done builtin_saveenv
>>> Completed ebuild phases init saveenv
>>> Running ebuild phases loadenv setup saveenv as root:root...
>>> Starting builtin_loadenv

Install error:
  * In program paludis -i1 paludis:
  * When performing install action from command line:
  * When executing install task:
  * When installing 'sys-libs/readline-5.2_p12-r1:0::gentoo':
  * Install error: Install failed for 'sys-libs/readline-5.2_p12-r1:0::gentoo'

I have no idea why it has started doing this, so a nudge in (almost) any direction would be much appreciated.

[ttuegel]

There is an upstream issue with bash that makes certain versions incompatible with Paludis. Try a line like this in your /etc/paludis/package_mask.conf file:

>=app-shells/bash-3.2_p25

This issue has apparently been cropping up as the main gentoo repository removed the repository mask on this version.

[andi456]

Unfortunately I have already installed the new bash version (bash-3.2_p33). It seems that I cannot reinstall the old one (bash-3.2_p17) because the install phase dies at "Starting builtin_loadenv". So what can I do now?

[krisse]

Unfortunately I have already installed the new bash version (bash-3.2_p33). It seems that I cannot reinstall the old one (bash-3.2_p17) because the install phase dies at "Starting builtin_loadenv". So what can I do now?

Probably sacrilegious to suggest the following in a thread like this, but emerge the old bash? I mean, emerge emerge it. If you've still got portage lying around in your system that is.

[ttuegel]

Unfortunately I have already installed the new bash version (bash-3.2_p33). It seems that I cannot reinstall the old one (bash-3.2_p17) because the install phase dies at "Starting builtin_loadenv". So what can I do now?

Probably sacrilegious to suggest the following in a thread like this, but emerge the old bash? I mean, emerge emerge it. If you've still got portage lying around in your system that is.

Heh, I knew I was forgetting a step in my post. That's what I get for posting at 2am

I noticed that paludis wasn't even able to uninstall my old bash due to the builtin_loadenv bug, so I just used portage to uninstall the new one, then masked it, and I was good to go. If you've managed to uninstall it, you'll probably have to resort to portage. Admittedly, when your system is not working is not the time to be getting religious about package managers. Whatever works, right?

[areian]

I solved it by booting from the minimal install cd, and use its bash to compile the downgraded version, then manually merge it, and lastly installing it correctly through paludis. A bit tricky, but it worked
Never thougt about using emerge, but that definitely sounds like the easiest method by far

[zlin]

Unfortunately I have already installed the new bash version (bash-3.2_p33). It seems that I cannot reinstall the old one (bash-3.2_p17) because the install phase dies at "Starting builtin_loadenv". So what can I do now?

>=app-shells/bash-3.2_p20 is now blocking <sys-apps/paludis-0.26_alpha5. This blocker was inserted an hour after those bash versions got removed from package.mask (since the bash maintainer clearly didn't care to tell us). Anybody unfortunate enough to have upgraded bash before the blocker was inserted can use this patch from r4044 in the paludis trunk to fix paludis (apply it to /usr/libexec/paludis/builtin_saveenv.bash).

[krisse]

Apache 2.2.6-r7 wants to have APACHE2_MODULES set. The portage way to do it, is to set it in make.conf. Where would paludis like it? Tried in /etc/paludis/bashrc, but that got me the following error:

Code: Select all

!!! ERROR in www-servers/apache-2.2.6-r7:
!!! In ? at line 220
!!! /etc/paludis/bashrc attempted to set $APACHE2_MODULES, which must not be set in bashrc.

(Got it built by using

Code: Select all

APACHE2_MODULES="blah blah" paludis -i apache

, but...)

[super-lupo]

krisse:

The paludis way would be in /etc/paludis/use.conf
Add a line like following:

*/* APACHE2_MODULES: -* actions alias auth_basic auth_digest authn_anon authn_dbd authn_dbm authn_default ...