| View previous topic :: View next topic |
| Author |
Message |
ciaranm
Retired Dev
Joined: 19 Jul 2003
Posts: 1719
Location: In Hiding
|
 Posted: Mon Dec 04, 2006 1:05 pm Post subject: |
 |
|
| zxy wrote: | 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. |
|
| Back to top |
|
 |
zxy
Veteran
Joined: 06 Jan 2006
Posts: 1160
Location: in bed in front of the computer
|
| Posted: Mon Dec 04, 2006 1:48 pm Post subject: |
|
|
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.
_________________
Nature does not hurry, yet everything is accomplished.
Lao Tzu |
|
| Back to top |
|
|
ciaranm
Retired Dev
Joined: 19 Jul 2003
Posts: 1719
Location: In Hiding
|
| Posted: Mon Dec 04, 2006 2:29 pm Post subject: |
|
|
| zxy wrote: | | 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. |
|
| Back to top |
|
|
zxy
Veteran
Joined: 06 Jan 2006
Posts: 1160
Location: in bed in front of the computer
|
| Posted: Mon Dec 04, 2006 4:28 pm Post subject: |
|
|
| ciaranm wrote: | | zxy wrote: | | 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. 
_________________
Nature does not hurry, yet everything is accomplished.
Lao Tzu |
|
| Back to top |
|
|
Lepaca Kliffoth
l33t
Joined: 28 Apr 2004
Posts: 737
Location: Florence, Italy
|
| Posted: Mon Dec 04, 2006 5:25 pm Post subject: |
|
|
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"
_________________
It isn't enough to win - everyone else must lose, and you also have to rub it in their face (maybe chop off an arm too for good measure).
Animebox! |
|
| Back to top |
|
|
Conan
Guru
Joined: 02 Nov 2004
Posts: 360
|
| Posted: Mon Dec 04, 2006 5:51 pm Post subject: |
|
|
| Lepaca Kliffoth wrote: | 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. |
|
| Back to top |
|
|
Lepaca Kliffoth
l33t
Joined: 28 Apr 2004
Posts: 737
Location: Florence, Italy
|
| Posted: Mon Dec 04, 2006 5:56 pm Post subject: |
|
|
| Conan wrote: |
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.
_________________
It isn't enough to win - everyone else must lose, and you also have to rub it in their face (maybe chop off an arm too for good measure).
Animebox! |
|
| Back to top |
|
|
BlackEdder
Advocate
Joined: 26 Apr 2004
Posts: 2588
Location: Dutch enclave in Egham, UK
|
| Posted: Mon Dec 04, 2006 6:43 pm Post subject: |
|
|
| 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. |
|
| Back to top |
|
|
Lepaca Kliffoth
l33t
Joined: 28 Apr 2004
Posts: 737
Location: Florence, Italy
|
| Posted: Mon Dec 04, 2006 7:10 pm Post subject: |
|
|
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.
_________________
It isn't enough to win - everyone else must lose, and you also have to rub it in their face (maybe chop off an arm too for good measure).
Animebox! |
|
| Back to top |
|
|
dleverton
Guru
Joined: 28 Aug 2006
Posts: 517
|
| Posted: Mon Dec 04, 2006 9:07 pm Post subject: |
|
|
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"? |
|
| Back to top |
|
|
ciaranm
Retired Dev
Joined: 19 Jul 2003
Posts: 1719
Location: In Hiding
|
| Posted: Mon Dec 04, 2006 9:13 pm Post subject: |
|
|
| dleverton wrote: | | 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.
| Quote: | | 2) Is there an equivalent of FEATURES="collision-protect"? |
No. That feature is an osx thing. |
|
| Back to top |
|
|
zxy
Veteran
Joined: 06 Jan 2006
Posts: 1160
Location: in bed in front of the computer
|
| Posted: Tue Dec 05, 2006 3:24 pm Post subject: |
|
|
About --resume-command-template
I just did | Code: | | paludis -i1 lcms --resume-command-template pal-XXXXXX.bash |
and the output is | Code: | | Resume command saved to file: pal-XXXXXX.bash |
But the file is not present.
If I do just
| Code: | | paludis -i1 lcms --resume-command-template pal-XXXXXX |
I get | Code: | | 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?
_________________
Nature does not hurry, yet everything is accomplished.
Lao Tzu |
|
| Back to top |
|
|
ciaranm
Retired Dev
Joined: 19 Jul 2003
Posts: 1719
Location: In Hiding
|
| Posted: Tue Dec 05, 2006 3:27 pm Post subject: |
|
|
| zxy wrote: | | Is it possible to use a file with .bash on the end. How? |
Consult the mkstemp(3) man page:
| Quote: |
The last six characters of template must be XXXXXX and these
are replaced with a string that makes the filename unique.
|
|
|
| Back to top |
|
|
dleverton
Guru
Joined: 28 Aug 2006
Posts: 517
|
| Posted: Tue Dec 05, 2006 5:52 pm Post subject: |
|
|
| ciaranm wrote: | | dleverton wrote: | | 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: | | export CONFIG_PROTECT="/foo/bar ${CONFIG_PROTECT}" |
- fortunately I realised it probably worked this way before I actually tried installing anything with config files)
| Quote: | | Quote: | | 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? |
|
| Back to top |
|
|
ciaranm
Retired Dev
Joined: 19 Jul 2003
Posts: 1719
Location: In Hiding
|
| Posted: Wed Dec 06, 2006 12:13 am Post subject: |
|
|
| dleverton wrote: | | ciaranm wrote: | | dleverton wrote: | | 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.
| Quote: | | Quote: | | Quote: | | 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. |
|
| Back to top |
|
|
Lepaca Kliffoth
l33t
Joined: 28 Apr 2004
Posts: 737
Location: Florence, Italy
|
| Posted: Fri Dec 08, 2006 9:02 am Post subject: |
|
|
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??
_________________
It isn't enough to win - everyone else must lose, and you also have to rub it in their face (maybe chop off an arm too for good measure).
Animebox! |
|
| Back to top |
|
|
zxy
Veteran
Joined: 06 Jan 2006
Posts: 1160
Location: in bed in front of the computer
|
| Posted: Fri Dec 08, 2006 9:05 am Post subject: |
|
|
in my /etc/paludis/use.conf
| Code: | | * VIDEO_CARDS: -* nvidia nv vesa |
don't forget -* to exclude all, but the ones you set.
_________________
Nature does not hurry, yet everything is accomplished.
Lao Tzu |
|
| Back to top |
|
|
Lepaca Kliffoth
l33t
Joined: 28 Apr 2004
Posts: 737
Location: Florence, Italy
|
| Posted: Fri Dec 08, 2006 9:26 am Post subject: |
|
|
Thanks!
_________________
It isn't enough to win - everyone else must lose, and you also have to rub it in their face (maybe chop off an arm too for good measure).
Animebox! |
|
| Back to top |
|
|
boniek
Guru
Joined: 26 Mar 2005
Posts: 373
|
|
| Back to top |
|
|
jordan83
Apprentice
Joined: 17 Apr 2006
Posts: 222
Location: check your closet...
|
| Posted: Sun Dec 10, 2006 8:23 am Post subject: |
|
|
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: | ...
--- [!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: | # 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: | # 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: | 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:
| Quote: | | 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:
but it is not, since in my bashrc file I have:
| Code: | | 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: | # 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
_________________
Time is a great teacher, but unfortunately it kills all its pupils.
Louis-Hector Berlioz
--
When the Boogeyman goes to sleep every night, he checks his closet for Chuck Norris.
chucknorrisfacts.com |
|
| Back to top |
|
|
zxy
Veteran
Joined: 06 Jan 2006
Posts: 1160
Location: in bed in front of the computer
|
| Posted: Sun Dec 10, 2006 9:07 am Post subject: |
|
|
Maybe | Code: | paludis --regenerate-installable-cache
paludis --regenerate-installed-cache |
could do the trick.
_________________
Nature does not hurry, yet everything is accomplished.
Lao Tzu |
|
| Back to top |
|
|
jordan83
Apprentice
Joined: 17 Apr 2006
Posts: 222
Location: check your closet...
|
| Posted: Sun Dec 10, 2006 10:47 am Post subject: |
|
|
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? 
| zxy wrote: | Maybe | Code: | 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...
_________________
Time is a great teacher, but unfortunately it kills all its pupils.
Louis-Hector Berlioz
--
When the Boogeyman goes to sleep every night, he checks his closet for Chuck Norris.
chucknorrisfacts.com |
|
| Back to top |
|
|
floffe
Guru
Joined: 24 Nov 2003
Posts: 414
Location: Linköping, Sweden
|
| Posted: Sun Dec 10, 2006 11:34 am Post subject: |
|
|
| 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. |
|
| Back to top |
|
|
jordan83
Apprentice
Joined: 17 Apr 2006
Posts: 222
Location: check your closet...
|
| Posted: Sun Dec 10, 2006 11:52 am Post subject: |
|
|
| floffe wrote: | | 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
_________________
Time is a great teacher, but unfortunately it kills all its pupils.
Louis-Hector Berlioz
--
When the Boogeyman goes to sleep every night, he checks his closet for Chuck Norris.
chucknorrisfacts.com |
|
| Back to top |
|
|
zxy
Veteran
Joined: 06 Jan 2006
Posts: 1160
Location: in bed in front of the computer
|
| Posted: Sun Dec 10, 2006 12:10 pm Post subject: |
|
|
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.
_________________
Nature does not hurry, yet everything is accomplished.
Lao Tzu |
|
| Back to top |
|
|
|
Unsupported Software
