Paludis support thread (current v. 0.14.3) - Part 1

[ciaranm]

I was installing kdebase-kioslaves and test failed because it couldnt connect to X server.
OK, I started fluxbox (loged in as user, and startx). Still the same. Anybody came past this?

(I know I can disable test in bashrc, but I would like to pass as many tests as possible)

Packages that need an X server need to use Xvfb. There's an eclass (virtual-x?) for helping out.

[zxy]

I tried to use --regenerate-installable-cache while installing all world packages. The need for this function became obvious when I couldn't paste the resume command from one terminal to another. It was too big. But tests fail from time to time.

The thing I'm interersted in is how to use the function. I tried a few variants but none of them worked.

[ciaranm]

I tried to use --regenerate-installable-cache while installing all world packages. The need for this function became obvious when I couldn't paste the resume command from one terminal to another. It was too big. But tests fail from time to time.

Did you mean --resume-command-template? If so, it's a mkstemp mask.

You don't need to regenerate the cache if a package fails in the compile or test phase. It's only necessary if Paludis starts updating the VDB and then dies before it reaches the install_post or uninstall_post hook.

[zxy]

I tried to use --regenerate-installable-cache while installing all world packages. The need for this function became obvious when I couldn't paste the resume command from one terminal to another. It was too big. But tests fail from time to time.

Did you mean --resume-command-template? If so, it's a mkstemp mask.

You don't need to regenerate the cache if a package fails in the compile or test phase. It's only necessary if Paludis starts updating the VDB and then dies before it reaches the install_post or uninstall_post hook.

Stupid me!!! Yes I ment --resume-command-template.

[Lepaca Kliffoth]

Did anyone manage to make the xeffects overlay work with paludis? I always get something like "Can't install blah since SRC_URI references unknown mirror:// 'kde'". Or 'gnome'. This happens with the kdelibs and gtk+ ebuilds.

edit: also, beryl-core fails with "failed running aclocal"

[Conan]

Did anyone manage to make the xeffects overlay work with paludis? I always get something like "Can't install blah since SRC_URI references unknown mirror:// 'kde'". Or 'gnome'. This happens with the kdelibs and gtk+ ebuilds.

edit: also, beryl-core fails with "failed running aclocal"

Already answered in the thread.

Each repository needs its own mirrors file.

[Lepaca Kliffoth]

Already answered in the thread.

Each repository needs its own mirrors file.

In the xeffects thread? I'll go check it out. JWith only the info you're giving me here, I don't have any idea how to fix the problem so I hope I can find more info there.

[BlackEdder]

Not sure in what thread it was answered, but basically each repository needs a thirdpartymirrors file under profile/, so copy this file from the main tree to your xeffects overlay.

[Lepaca Kliffoth]

Sorry, I'm dumb. It was on the first page, back when I was struggling with a borked system and didn't read anything else. Sorry and thanks.

[dleverton]

1) What's the preferred way of adding things to CONFIG_PROTECT with Paludis? With Portage I had it in /etc/make.conf; does it work in bashrc, or is there somewhere else it needs to go?

2) Is there an equivalent of FEATURES="collision-protect"?

[ciaranm]

1) What's the preferred way of adding things to CONFIG_PROTECT with Paludis? With Portage I had it in /etc/make.conf; does it work in bashrc, or is there somewhere else it needs to go?

bashrc is fine.

2) Is there an equivalent of FEATURES="collision-protect"?

No. That feature is an osx thing.

[zxy]

About --resume-command-template
I just did

Code: Select all

paludis -i1 lcms --resume-command-template pal-XXXXXX.bash

and the output is

Code: Select all

Resume command saved to file: pal-XXXXXX.bash

But the file is not present.

If I do just

Code: Select all

paludis -i1 lcms --resume-command-template pal-XXXXXX

I get

Code: Select all

Resume command saved to file: pal-6dbJMn

And now the file is there.

Is it possible to use a file with .bash on the end. How?

[ciaranm]

Is it possible to use a file with .bash on the end. How?

Consult the mkstemp(3) man page:

The last six characters of template must be XXXXXX and these
are replaced with a string that makes the filename unique.

[dleverton]

1) What's the preferred way of adding things to CONFIG_PROTECT with Paludis? With Portage I had it in /etc/make.conf; does it work in bashrc, or is there somewhere else it needs to go?

bashrc is fine.

Hmm, I did some experimenting with this. First, to clarify, I meant /etc/paludis/bashrc - that may have been obvious from the context, but since there are various bashrc files floating about, I thought I'd better be sure. Anyway, putting it in /etc/paludis/bashrc works for the merge itself¹, but the message at the end that reports files that need updating only seems to consider /etc. I then tried adding it to a file in /etc/env.d, but even after env-update and . /etc/profile, Paludis ignores this completely, same for CONFIG_PROTECT entries added by packages. Could you clarify the proper behaviour here, please (or am I just doing something silly)?

[1] (warning for anyone else out there who cares, looks like you need to explicitly include the default value:

Code: Select all

export CONFIG_PROTECT="/foo/bar ${CONFIG_PROTECT}"

- fortunately I realised it probably worked this way before I actually tried installing anything with config files)

2) Is there an equivalent of FEATURES="collision-protect"?

No. That feature is an osx thing.

OK, but I like not having to worry about my packages trying to kill each other, at least in this particular way. If you're not interested in including it in Paludis itself, I might have a go at writing a hook for it, does that sound reasonably sane? I haven't looked into the hook mechanism much yet, but on a quick glance it looks like ebuild_merge_pre would be the proper place, right?

[ciaranm]

1) What's the preferred way of adding things to CONFIG_PROTECT with Paludis? With Portage I had it in /etc/make.conf; does it work in bashrc, or is there somewhere else it needs to go?

bashrc is fine.

Hmm, I did some experimenting with this. First, to clarify, I meant /etc/paludis/bashrc - that may have been obvious from the context, but since there are various bashrc files floating about, I thought I'd better be sure. Anyway, putting it in /etc/paludis/bashrc works for the merge itself¹, but the message at the end that reports files that need updating only seems to consider /etc. I then tried adding it to a file in /etc/env.d, but even after env-update and . /etc/profile, Paludis ignores this completely, same for CONFIG_PROTECT entries added by packages. Could you clarify the proper behaviour here, please (or am I just doing something silly)?

CONFIG_PROTECT may well be being overridden by something else in your environment.

2) Is there an equivalent of FEATURES="collision-protect"?

No. That feature is an osx thing.

OK, but I like not having to worry about my packages trying to kill each other, at least in this particular way. If you're not interested in including it in Paludis itself, I might have a go at writing a hook for it, does that sound reasonably sane? I haven't looked into the hook mechanism much yet, but on a quick glance it looks like ebuild_merge_pre would be the proper place, right?

You could do it as an ebuild_merge_pre hook, yes.

[Lepaca Kliffoth]

Paludis is ignoring my VIDEO_CARDS setting. It's not the end of the world and I don't care that much, but:

* VIDEO_CARDS: fbdev nvidia vesa

Results in:
* x11-base/xorg-server-1.1.1-r3::gentoo [U 1.1.1-r2] (-3dfx) -aiglx -debug -dmx dri -ipv6 -kdrive -minimal nptl sdl xorg -xprint input_devices: -acecad -aiptek -calcomp -citron -digitaledge -dmc -dynapro -elo2300 -elographics evdev -fpit -hyperpen -jamstudio joystick keyboard -magellan -microtouch mouse -mutouch -palmax -penmount -spaceorb -summa -synaptics -tek4957 -ur98 -vmmouse -void -wacom video_cards: apm ark chips cirrus cyrix dummy -epson fbdev -fglrx glint i128 (-i740) i810 (-impact) (-imstt) -mach64 mga neomagic (-newport) (-nsc) nv nvidia -r128 -radeon rendition s3 s3virge savage siliconmotion sis sisusb (-sunbw2) (-suncg14) (-suncg3) (-suncg6) (-sunffb) (-sunleo) (-suntcx) tdfx tga trident tseng v4l vesa vga via vmware voodoo

For clarity, here is the list of enabled flags:

video_cards: apm ark chips cirrus cyrix dummy fbdev glint i128 i810 mga neomagic nv nvidia rendition s3 s3virge savage siliconmotion sis sisusb tdfx tga trident tseng v4l vesa vga via vmware voodoo

WTF??

[zxy]

in my /etc/paludis/use.conf

Code: Select all

* VIDEO_CARDS: -* nvidia nv vesa

don't forget -* to exclude all, but the ones you set.

[Lepaca Kliffoth]

Thanks!

[boniek]

I want to set my own colors for paludis output (both schemes look horrible on a grey terminal ). Is this possible? How can I do that?

[jordan83]

Hi,

today I tried to install the package media-plugins/kipi-plugins, ~x86 version.

One of the dependancy is media-libs/lcms and paludis tried to upgrade it from version 1.14-r1 to ~1.15.

When the process arrived to "unmerge old package" stage, I got this error:

Code: Select all

...
--- [!empt] /usr/lib/python2.4/site-packages
--- [!empt] /usr/lib/python2.4
--- [!empt] /usr/lib/pkgconfig
--- [!empt] /usr/lib
--- [!empt] /usr/bin
--- [!empt] /usr

!!! ERROR in media-libs/lcms-1.14-r1:
!!! In builtin_unmerge at line 77
!!! unmerge failed

!!! Call stack:
!!!    * builtin_unmerge (/usr/libexec/paludis/builtin_unmerge.bash:77)
!!!    * ebuild_f_unmerge (/usr/libexec/paludis/builtin_unmerge.bash:100)
!!!    * ebuild_main (/usr/libexec/paludis/ebuild.bash:296)
!!!    * main (/usr/libexec/paludis/ebuild.bash:308)

die trap: exiting with error.

Unhandled exception:
  * In program paludis -i media-plugins/kipi-plugins:
  * When performing install action from command line:
  * When executing install task:
  * When uninstalling 'media-libs/lcms-1.14-r1' from 'installed':
  * Uninstall error: Uninstall failed for 'media-libs/lcms-1.14-r1::installed' (N7paludis27PackageUninstallActionErrorE)

Now I have two versions of lcms installed and I cannot unmerge any of them:

Code: Select all

# paludis -q lcms
* media-libs/lcms
    gentoo:                1.14-r1 1.15 {:0}
    installed:             1.14-r1 1.15* {:0}
    Homepage:              http://www.littlecms.com/
    Description:           A lightweight, speed optimized color management engine
    License:               ( LGPL-2.1 )
    Source origin:         media-libs/lcms-1.15::gentoo
    Installed time:        Sun Dec 10 09:03:51 2006
    Use flags:              (jpeg) (python) (tiff) (zlib)

paludis -u =media-libs/lcms-1.15

Code: Select all

# paludis -u =media-libs/lcms-1.15
Building unmerge list... done

These packages will be uninstalled:

* media-libs/lcms-1.15::installed


Total: 1 package

Updating world file



Uninstalling media-libs/lcms-1.15::installed

>>> Starting pkg_prerm
>>> Done pkg_prerm
>>> Starting builtin_unmerge
--- [!type] /usr/bin/icc2ps
--- [!type] /usr/bin/icclink
--- [!type] /usr/bin/icctrans
--- [!type] /usr/bin/jpegicc
--- [!type] /usr/bin/tiffdiff
--- [!type] /usr/bin/tifficc
--- [!type] /usr/bin/wtpt
--- [!type] /usr/include/icc34.h
--- [!type] /usr/include/lcms.h
--- [!type] /usr/lib/liblcms.a
--- [!type] /usr/lib/liblcms.la
--- [!type] /usr/lib/liblcms.so
--- [!type] /usr/lib/liblcms.so.1
--- [!type] /usr/lib/liblcms.so.1.0.15
--- [!type] /usr/lib/pkgconfig/lcms.pc
--- [!type] /usr/lib/python2.4/site-packages/_lcms.a
--- [!type] /usr/lib/python2.4/site-packages/_lcms.la
--- [!type] /usr/lib/python2.4/site-packages/_lcms.so
--- [!type] /usr/lib/python2.4/site-packages/lcms.py
--- [!type] /usr/share/doc/lcms-1.15/AUTHORS.gz
--- [!type] /usr/share/doc/lcms-1.15/INSTALL.gz
--- [!type] /usr/share/doc/lcms-1.15/LCMSAPI.TXT.gz
--- [!type] /usr/share/doc/lcms-1.15/NEWS.gz
--- [!type] /usr/share/doc/lcms-1.15/README.1ST.gz
--- [!type] /usr/share/doc/lcms-1.15/TUTORIAL.TXT.gz
unmerge@1165738494: [WARNING] Malformed VDB entry 'obj /usr/share/lcms/profiles/sRGB Color Space Profile.icm 1d3fda2edb4a89ab60a23c5f7c7d81dd 1165737830'
--- [!type] /usr/share/lcms/profiles/sRGBSpac.icm
--- [!type] /usr/share/man/man1/icc2ps.1
--- [!type] /usr/share/man/man1/icclink.1
--- [!type] /usr/share/man/man1/jpegicc.1
--- [!type] /usr/share/man/man1/tifficc.1
--- [!type] /usr/share/man/man1/wtpt.1
--- [!empt] /usr/share/man/man1
--- [!empt] /usr/share/man
--- [!empt] /usr/share/lcms/profiles
--- [!empt] /usr/share/lcms
--- [!type] /usr/share/doc/lcms-1.15
--- [!empt] /usr/share/doc
--- [!empt] /usr/share
--- [!empt] /usr/lib/python2.4/site-packages
--- [!empt] /usr/lib/python2.4
--- [!empt] /usr/lib/pkgconfig
--- [!empt] /usr/lib
--- [!empt] /usr/include
--- [!empt] /usr/bin
--- [!empt] //usr

!!! ERROR in media-libs/lcms-1.15:
!!! In builtin_unmerge at line 77
!!! unmerge failed

!!! Call stack:
!!!    * builtin_unmerge (/usr/libexec/paludis/builtin_unmerge.bash:77)
!!!    * ebuild_f_unmerge (/usr/libexec/paludis/builtin_unmerge.bash:100)
!!!    * ebuild_main (/usr/libexec/paludis/ebuild.bash:296)
!!!    * main (/usr/libexec/paludis/ebuild.bash:308)


!!! This package failed inside the test phase. You should read
!!!    http://paludis.berlios.de/KnownIssues.html
!!! for more information on packages with test phase failures.


/usr/libexec/paludis/ebuild.bash: line 73: kill: (4474) - No such process

Uninstall error:
  * In program paludis -u =media-libs/lcms-1.15:
  * When performing uninstall action from command line:
  * When executing uninstall task:
  * When uninstalling 'media-libs/lcms-1.15' from 'installed':
  * Uninstall error: Uninstall failed for 'media-libs/lcms-1.15::installed'

paludis -u =media-libs/lcms-1.14-r1

Code: Select all

Building unmerge list... done

These packages will be uninstalled:

* media-libs/lcms-1.14-r1::installed


Total: 1 package

Updating world file



Uninstalling media-libs/lcms-1.14-r1::installed

>>> Starting pkg_prerm
>>> Done pkg_prerm
>>> Starting builtin_unmerge
--- [!type] /usr/bin/wtpt
--- [!type] /usr/bin/jpegicc
--- [!type] /usr/bin/icctrans
--- [!type] /usr/bin/tifficc
--- [!type] /usr/bin/icc2ps
--- [!type] /usr/bin/icclink
--- [!type] /usr/lib/liblcms.a
--- [!type] /usr/lib/pkgconfig/lcms.pc
--- [!type] /usr/lib/liblcms.so.1
--- [!type] /usr/lib/liblcms.so.1.0.14
--- [!type] /usr/lib/python2.4/site-packages/lcms.py
--- [!type] /usr/lib/python2.4/site-packages/_lcms.a
--- [!type] /usr/lib/python2.4/site-packages/_lcms.la
--- [!type] /usr/lib/python2.4/site-packages/_lcms.so
--- [!type] /usr/lib/liblcms.la
--- [!type] /usr/lib/liblcms.so
--- [!type] /usr/share/doc/lcms-1.14-r1/LCMSAPI.TXT.gz
--- [!type] /usr/share/doc/lcms-1.14-r1/README.1ST.gz
--- [!type] /usr/share/doc/lcms-1.14-r1/NEWS.gz
--- [!type] /usr/share/doc/lcms-1.14-r1/INSTALL.gz
--- [!type] /usr/share/doc/lcms-1.14-r1/AUTHORS.gz
--- [!type] /usr/share/doc/lcms-1.14-r1/TUTORIAL.TXT.gz
--- [!type] /usr/share/man/man1/jpegicc.1.gz
--- [!type] /usr/share/man/man1/wtpt.1.gz
--- [!type] /usr/share/man/man1/tifficc.1.gz
--- [!type] /usr/share/man/man1/icc2ps.1.gz
--- [!type] /usr/share/man/man1/icclink.1.gz
--- [!type] /usr/share/lcms/profiles/sRGBSpac.icm
unmerge@1165738578: [WARNING] Malformed VDB entry 'obj /usr/share/lcms/profiles/sRGB Color Space Profile.icm 1d3fda2edb4a89ab60a23c5f7c7d81dd 1157305483'
--- [!type] /usr/include/lcms.h
--- [!type] /usr/include/icc34.h
--- [!empt] /usr/include
--- [!empt] /usr/share/lcms/profiles
--- [!empt] /usr/share/lcms
--- [!empt] /usr/share/man/man1
--- [!empt] /usr/share/man
--- [!type] /usr/share/doc/lcms-1.14-r1
--- [!empt] /usr/share/doc
--- [!empt] /usr/share
--- [!empt] /usr/lib/python2.4/site-packages
--- [!empt] /usr/lib/python2.4
--- [!empt] /usr/lib/pkgconfig
--- [!empt] /usr/lib
--- [!empt] /usr/bin
--- [!empt] /usr

!!! ERROR in media-libs/lcms-1.14-r1:
!!! In builtin_unmerge at line 77
!!! unmerge failed

!!! Call stack:
!!!    * builtin_unmerge (/usr/libexec/paludis/builtin_unmerge.bash:77)
!!!    * ebuild_f_unmerge (/usr/libexec/paludis/builtin_unmerge.bash:100)
!!!    * ebuild_main (/usr/libexec/paludis/ebuild.bash:296)
!!!    * main (/usr/libexec/paludis/ebuild.bash:308)

die trap: exiting with error.

Uninstall error:
  * In program paludis -u =media-libs/lcms-1.14-r1:
  * When performing uninstall action from command line:
  * When executing uninstall task:
  * When uninstalling 'media-libs/lcms-1.14-r1' from 'installed':
  * Uninstall error: Uninstall failed for 'media-libs/lcms-1.14-r1::installed'

I think this message might be useful to understand the problem:

unmerge@1165738494: [WARNING] Malformed VDB entry 'obj /usr/share/lcms/profiles/sRGB Color Space Profile.icm 1d3fda2edb4a89ab60a23c5f7c7d81dd 1165737830'

How do I proceed now?
Is this either a Paludis bug or a buggy ebuild bug?

You might answer that it is a test bug because of the message:

!! This package failed inside the test phase. You should read
!!! http://paludis.berlios.de/KnownIssues.html
!!! for more information on packages with test phase failures.

but it is not, since in my bashrc file I have:

Code: Select all

SKIP_FUNCTIONS="test"

Another thing to notice is that Paludis does not detect this inconsistency of VDB database.
If I simply ignore the problem and try again
paludis -i media-plugins/kipi-plugins I get:

Code: Select all

# paludis -i media-plugins/kipi-plugins
Building target list...
Building dependency list... done

These packages will be installed:

* media-libs/libkexif-0.2.2 [N] arts -debug -xinerama
* media-plugins/kipi-plugins-0.1.2 [N] arts -debug gphoto2 opengl -xinerama

Total: 2 packages (2 new)


Installing media-libs/libkexif-0.2.2::gentoo

>>> Starting builtin_fetch
>>> Need to fetch libkexif-0.2.2.tar.bz2
wget -T 30 -t 1 -O /var/paludis/repositories/gentoo/distfiles/libkexif-0.2.2.tar.bz2 http://distfiles.gentoo.org/distfiles/libkexif-0.2.2.tar.bz2
--09:35:50--  http://distfiles.gentoo.org/distfiles/libkexif-0.2.2.tar.bz2
           => `/var/paludis/repositories/gentoo/distfiles/libkexif-0.2.2.tar.bz2'
Resolving distfiles.gentoo.org... 216.165.129.135, 156.56.247.195, 64.50.236.52, ...
Connecting to distfiles.gentoo.org|216.165.129.135|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 442,833 (432K) [application/x-tar]

100%[============================================================ \
=============================================================>] 442,833       42.47K/s    ETA 00:00

09:36:01 (41.64 KB/s) - `/var/paludis/repositories/gentoo/distfiles/libkexif-0.2.2.tar.bz2' saved [442833/442833]

 * Checking MD5 for libkexif-0.2.2.tar.bz2 ...                           [ ok ]
 * Checking RMD160 for libkexif-0.2.2.tar.bz2 ...                        [ ok ]
 * Checking SHA256 for libkexif-0.2.2.tar.bz2 ...                        [ ok ]
>>> Done builtin_fetch
>>> Starting builtin_init
>>> Done builtin_init
>>> Starting pkg_setup
>>> Done pkg_setup
>>> Starting src_unpack
>>> Unpacking libkexif-0.2.2.tar.bz2 to /var/tmp/paludis/media-libs/libkexif-0.2.2/work
tar jxf /var/paludis/repositories/gentoo/distfiles/libkexif-0.2.2.tar.bz2 --no-same-owner
>>> Done src_unpack
>>> Starting src_compile
 * Running elibtoolize in: libkexif-0.2.2/admin
 *   Applying portage-1.5.10.patch ...

As you can see Paludis proceeds with the installation considering lcms as successfully installed
I think that this is a dangerous misbehavior, since in my opinion the installation of the package shouldn't be considered completed in this case and Paludis should print out an error until the problem is somehow fixed.

Thanks in advance.

mod edit: inserted line break for page formatting --Earthwings

[zxy]

Maybe

Code: Select all

paludis --regenerate-installable-cache
paludis --regenerate-installed-cache

could do the trick.

[jordan83]

Unluckily I had to solve the problem using the "bad and dirty" approach, deleting the two entry /var/db/pkg/media-libs/lcms-1.15/ and /var/db/pkg/media-libs/lcms-1.14-r1 since after a reboot X.org stopped to work and I had no other choice (having only this laptop... ).

Paludis should definitely detect this kind of dangerous situations.
A lot of users don't know what is /var/db/pkg/ and they probably would corrupt the database without knowing what really happened.

In the forum you can read a lot of topics about people complaining about trivial errors that they could have solved in one minute just reading the output
If the error is hidden as in the situation I've reported, they would just run one more time the original command (in my case paludis -i media-plugins/kipi-plugins) to try again the installation and they would corrupt the installed repository without realizing it.

How will they find the source of error, the next time they reboot and they have something going wrong?

Maybe

Code: Select all

paludis --regenerate-installable-cache
paludis --regenerate-installed-cache

could do the trick.

I don't know, since I read this message only now that I've already solved the problem.

However, in my opinion in cases like this regenerating the cache is not really useful.
Cache is something built starting from the database, therefore if you have a corrupted database regenerating the cache will only give you corrupted cache...

[floffe]

I think the problem here is that the VDB format does not allow spaces in filenames. I seem to remember ciaranm ranting about portage handling it in some ugly way. It should work if you just deleted the offending files (with spaces) and then uninstalled the rest regularly.

[jordan83]

I think the problem here is that the VDB format does not allow spaces in filenames. I seem to remember ciaranm ranting about portage handling it in some ugly way. It should work if you just deleted the offending files (with spaces) and then uninstalled the rest regularly.

You're perfectly right

I edited /var/db/pkg/media-libs/media-libs/lcms-1.15/CONTENTS and I removed the entry
/usr/share/lcms/profiles/sRGB Color Space Profile.icm 1d3fda2edb4a89ab60a23c5f7c7d81dd 1157305483.

After that Paludis uninstalled properly the package.

However the problem remains

[zxy]

I know that ciaranm said, that cache has to be rebuilt ater an ebuild fails (I think probably in most cases). So the corrupt cache could make problems.

I would really like to hear from ciraranm about this.