Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Unsupported Software
  • Search

[PALUDIS] Support thread (current v. 0.22.2) - Part 2

This forum covers all Gentoo-related software not officially supported by Gentoo. Ebuilds/software posted here might harm the health and stability of your system(s), and are not supported by Gentoo developers. Bugs/errors caused by ebuilds from overlays.gentoo.org are covered by this forum, too.
Locked
Advanced search
494 posts
  • Page 13 of 20
    • Jump to page:
  • Previous
  • 1
  • …
  • 11
  • 12
  • 13
  • 14
  • 15
  • …
  • 20
  • Next
Author
Message
nikaya
Veteran
Veteran
User avatar
Posts: 1471
Joined: Sat May 13, 2006 9:43 am
Location: Germany

Post by nikaya » Sat Mar 03, 2007 6:42 pm

zxy wrote:you can of course try

Code: Select all

export SANDBOX_PREDICT=/
paludis -i paludis
That didn't work:

Code: Select all

john.doe # export SANDBOX_PREDICT=/ 
john.doe # paludis -i paludis
[...]
compiling works well
[...]

Cleaning stale versions after installing sys-apps/paludis-0.20.1::gentoo

* sys-apps/paludis-0.20.0::installed

(1 of 1) Cleaning sys-apps/paludis-0.20.0::installed

>>> Running ebuild phases prerm saveenv...
bunzip2 < /var/db/pkg/sys-apps/paludis-0.20.0/environment.bz2 > /var/tmp/paludis/environment-sys-apps-paludis-0.20.0-22480
ebuild_scrub_environment /var/tmp/paludis/environment-sys-apps-paludis-0.20.0-22480
source /var/tmp/paludis/environment-sys-apps-paludis-0.20.0-22480
/var/tmp/paludis/environment-sys-apps-paludis-0.20.0-22480: line 4302: SANDBOX_ACTIVE: readonly variable
rm /var/tmp/paludis/environment-sys-apps-paludis-0.20.0-22480
source /var/tmp/paludis/environment-sys-apps-paludis-0.20.0
>>> Starting pkg_prerm
>>> Done pkg_prerm
>>> Starting builtin_saveenv
/usr/libexec/paludis/builtin_saveenv.bash: line 24: /var/db/pkg/sys-apps/paludis-0.20.0/loadsaveenv: Keine Berechtigung
>>> Done builtin_saveenv
>>> Completed ebuild phases prerm saveenv
--- [!time] /usr/bin/adjutrix
--- [!time] /usr/bin/inquisitio
--- [!time] /usr/bin/paludis
--- [!time] /usr/include/paludis/about.hh
--- [!time] /usr/include/paludis/args/args.hh
--- [!time] /usr/include/paludis/args/args_dumper.hh
--- [!time] /usr/include/paludis/args/args_error.hh
--- [!time] /usr/include/paludis/args/args_group.hh
--- [!time] /usr/include/paludis/args/args_handler.hh
--- [!time] /usr/include/paludis/args/args_option.hh

[...]

>>> Running ebuild phases loadenv postrm...
bunzip2 < /var/db/pkg/sys-apps/paludis-0.20.0/environment.bz2 > /var/tmp/paludis/environment-sys-apps-paludis-0.20.0-22524
ebuild_scrub_environment /var/tmp/paludis/environment-sys-apps-paludis-0.20.0-22524
source /var/tmp/paludis/environment-sys-apps-paludis-0.20.0-22524
/var/tmp/paludis/environment-sys-apps-paludis-0.20.0-22524: line 4302: SANDBOX_ACTIVE: readonly variable
rm /var/tmp/paludis/environment-sys-apps-paludis-0.20.0-22524
source /var/tmp/paludis/environment-sys-apps-paludis-0.20.0
>>> Starting builtin_loadenv

!!! ERROR in sys-apps/paludis-0.20.0:
!!! In builtin_loadenv at line 24
!!! /var/db/pkg/sys-apps/paludis-0.20.0/loadsaveenv not a file

!!! Call stack:
!!!    * builtin_loadenv (/usr/libexec/paludis/builtin_loadenv.bash:24)
!!!    * ebuild_f_loadenv (/var/tmp/paludis/environment-sys-apps-paludis-0.20.0-22524:1240)
!!!    * ebuild_main (/usr/libexec/paludis/ebuild.bash:346)
!!!    * main (/usr/libexec/paludis/ebuild.bash:364)

die trap: exiting with error.

Unhandled exception:
  * In program paludis -i paludis:
  * When performing install action from command line:
  * When executing install task:
  * When uninstalling 'sys-apps/paludis-0.20.0' from 'installed':
  * Uninstall error: Uninstall failed for 'sys-apps/paludis-0.20.0::installed' (paludis::PackageUninstallActionError)
Maybe a bug. :?

BTW:

Code: Select all

 * You have 1 unread news items
How can I read the news?
Notes on Dhamma
How to waste your time: look for an explanation of consciousness, ask to know what feeling is. (Nanavira Thera)
Top
zxy
Veteran
Veteran
User avatar
Posts: 1160
Joined: Fri Jan 06, 2006 8:07 am
Location: in bed in front of the computer
Contact:
Contact zxy
Website

Post by zxy » Sat Mar 03, 2007 6:52 pm

@john.doe
spb wrote:
Jeremy_Z wrote:You mean it is a bug, fixed in SVN, so we have to wait for next release ?
Yes. The next release in this case being 0.20.1, whose difference from 0.20.0 is exactly that fix.
zxy wrote:i did

Code: Select all

rm -r /var/db/pkg/sys-apps/paludis-0.20.0   
paludis-i paludis
That works.
john.doe wrote:How can I read the news?

Code: Select all

eselect news
This will show you what you can do with news.
Nature does not hurry, yet everything is accomplished.
Lao Tzu
Top
dayul
Apprentice
Apprentice
User avatar
Posts: 180
Joined: Wed Jun 02, 2004 10:16 am
Location: Blackpool, England

Post by dayul » Sat Mar 03, 2007 7:06 pm

@john.doe

i saw a similar error to you, i managed to get round it by:

Code: Select all

export SANDBOX_PREDICT=/ 
paludis -i =sys-apps/paludis-0.20.0
paludis -i =sys-apps/paludis-0.20.1
Maybe overkill, but it worked for me. The first install (i.e 0.20.0) gave me the same error, but i ignored that and tried to install 0.20.1, and it installed without error.
Mailtc- system tray mail checker.
Top
fldc2
Tux's lil' helper
Tux's lil' helper
User avatar
Posts: 112
Joined: Wed Jun 14, 2006 7:32 pm
Location: Motala, Sweden

Post by fldc2 » Sun Mar 04, 2007 7:28 am

ll4e wrote:By not using xeffects..

From the FAQ:
Repository Blacklists

Paludis will sometimes blacklist certain repositories. When using a blacklisted repository, you will receive a warning when Paludis starts up. This is not a fatal error, but you should realise that use of the repository in question will likely lead to breakages.

Repositories are only blacklisted under extreme circumstances, such as:

* When they are known to be very broken.
* When they are known to rely heavily upon quirks in Portage's behaviour that Paludis will not emulate.
* When they are known to be a security threat.
I am aware of this and i don't care, this is my choice and this was not my question, can i disable this warning?
Top
zxy
Veteran
Veteran
User avatar
Posts: 1160
Joined: Fri Jan 06, 2006 8:07 am
Location: in bed in front of the computer
Contact:
Contact zxy
Website

Post by zxy » Sun Mar 04, 2007 8:40 am

I think you can edit (remove entries in) the /usr/share/paludis/repository_blacklist.txt
Nature does not hurry, yet everything is accomplished.
Lao Tzu
Top
nikaya
Veteran
Veteran
User avatar
Posts: 1471
Joined: Sat May 13, 2006 9:43 am
Location: Germany

Post by nikaya » Sun Mar 04, 2007 9:43 am

zxy wrote:@john.doe
zxy wrote:i did

Code: Select all

rm -r /var/db/pkg/sys-apps/paludis-0.20.0   
paludis-i paludis
That works.
ok,ok.Done it.With a little bad conscience. :?
zxy wrote:
john.doe wrote:How can I read the news?

Code: Select all

eselect news
This will show you what you can do with news.
Thanks.Found it before by manual reading /usr/local/overlays/paludis-extras/metadata/news/,but that did not letting disappeared the message.
Notes on Dhamma
How to waste your time: look for an explanation of consciousness, ask to know what feeling is. (Nanavira Thera)
Top
fldc2
Tux's lil' helper
Tux's lil' helper
User avatar
Posts: 112
Joined: Wed Jun 14, 2006 7:32 pm
Location: Motala, Sweden

Post by fldc2 » Sun Mar 04, 2007 10:19 am

zxy wrote:I think you can edit (remove entries in) the /usr/share/paludis/repository_blacklist.txt
Thanks, missed that file :D
Top
revenger
n00b
n00b
User avatar
Posts: 23
Joined: Fri Sep 23, 2005 10:10 pm
Location: The Netherlands

Post by revenger » Sun Mar 04, 2007 7:32 pm

when uninstalling mozilla-firefox-2.0.0.1-r4 with paludis 0.20.1 i get:

Code: Select all

# paludis -u =www-client/mozilla-firefox-2.0.0.1-r4::installed
Building unmerge list... done

These packages will be uninstalled:

* www-client/mozilla-firefox-2.0.0.1-r4::installed


Total: 1 package

Updating world file



(1 of 1) Uninstalling www-client/mozilla-firefox-2.0.0.1-r4::installed

>>> Running ebuild phases prerm saveenv...
bunzip2 < /var/db/pkg/www-client/mozilla-firefox-2.0.0.1-r4/environment.bz2 > /var/tmp/paludis/environment-www-client-mozilla-firefox-2.0.0.1-r4-22420
ebuild_scrub_environment /var/tmp/paludis/environment-www-client-mozilla-firefox-2.0.0.1-r4-22420
source /var/tmp/paludis/environment-www-client-mozilla-firefox-2.0.0.1-r4-22420
/var/tmp/paludis/environment-www-client-mozilla-firefox-2.0.0.1-r4-22420: line 5172: SANDBOX_ACTIVE: readonly variable
rm /var/tmp/paludis/environment-www-client-mozilla-firefox-2.0.0.1-r4-22420
source /var/tmp/paludis/environment-www-client-mozilla-firefox-2.0.0.1-r4
/var/tmp/paludis/environment-www-client-mozilla-firefox-2.0.0.1-r4: line 5104: unexpected EOF while looking for matching `"'
/var/tmp/paludis/environment-www-client-mozilla-firefox-2.0.0.1-r4: line 5105: syntax error: unexpected end of file

!!! ERROR in www-client/mozilla-firefox-2.0.0.1-r4:
!!! In ebuild_load_ebuild at line 1767
!!! Can't load saved environment

!!! Call stack:
!!!    * ebuild_load_ebuild (/var/tmp/paludis/environment-www-client-mozilla-firefox-2.0.0.1-r4-22420:1767)
!!!    * ebuild_main (/usr/libexec/paludis/ebuild.bash:341)
!!!    * main (/usr/libexec/paludis/ebuild.bash:364)

die trap: exiting with error.

Uninstall error:
  * In program paludis -u =www-client/mozilla-firefox-2.0.0.1-r4::installed:
  * When performing uninstall action from command line:
  * When executing uninstall task:
  * When uninstalling 'www-client/mozilla-firefox-2.0.0.1-r4' from 'installed':
  * Uninstall error: Uninstall failed for 'www-client/mozilla-firefox-2.0.0.1-r4::installed'
the last couple of lines of /var/tmp/paludis/environment-www-client-mozilla-firefox-2.0.0.1-r4:

Code: Select all

# tail -n 10 /var/tmp/paludis/environment-www-client-mozilla-firefox-2.0.0.1-r4 
declare -x save_var_KERNEL="linux"
declare -x save_var_LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text"
declare -x save_var_LINGUAS=""
declare -x save_var_LIRC_DEVICES=""
declare -x save_var_MISDN_CARDS=""
declare -x save_var_USE="gnome ipv6 java mozbranding mozdevelop amd64 alsa_cards_ice1712 elibc_glibc userland_GNU alsa_pcm_plugins_adpcm alsa_pcm_plugins_alaw alsa_pcm_plugins_asym alsa_pcm_plugins_copy alsa_pcm_plugins_dmix alsa_pcm_plugins_dshare alsa_pcm_plugins_dsnoop alsa_pcm_plugins_empty alsa_pcm_plugins_extplug alsa_pcm_plugins_file alsa_pcm_plugins_hooks alsa_pcm_plugins_iec958 alsa_pcm_plugins_ioplug alsa_pcm_plugins_ladspa alsa_pcm_plugins_lfloat alsa_pcm_plugins_linear alsa_pcm_plugins_meter alsa_pcm_plugins_mulaw alsa_pcm_plugins_multi alsa_pcm_plugins_null alsa_pcm_plugins_plug alsa_pcm_plugins_rate alsa_pcm_plugins_route alsa_pcm_plugins_share alsa_pcm_plugins_shm alsa_pcm_plugins_softvol lcd_devices_bayrad lcd_devices_cfontz lcd_devices_cfontz633 lcd_devices_glk lcd_devices_hd44780 lcd_devices_lb216 lcd_devices_lcdm001 lcd_devices_mtxorb lcd_devices_ncurses lcd_devices_text input_devices_evdev input_devices_keyboard input_devices_mouse kernel_linux video_cards_nv video_cards_nvidia video_cards_vesa "
declare -x save_var_USERLAND="GNU"
declare -x save_var_USE_EXPAND="DVB_CARDS ALSA_CARDS ELIBC USERLAND LIRC_DEVICES ALSA_PCM_PLUGINS FOO2ZJS_DEVICES FCDSL_CARDS LINGUAS CAMERAS CROSSCOMPILE_OPTS LCD_DEVICES INPUT_DEVICES KERNEL VIDEO_CARDS FRITZCAPI_CARDS MISDN_CARDS"
declare -x save_var_USE_EXPAND_HIDDEN=""
declare -x save_var_VIDEO_CARDS="nv nvidia vesa"
Top
revenger
n00b
n00b
User avatar
Posts: 23
Joined: Fri Sep 23, 2005 10:10 pm
Location: The Netherlands

Post by revenger » Sun Mar 04, 2007 7:50 pm

revenger wrote:...
also getting similar errors when uninstalling app-emulation/emul-linux-x86-qtlibs-10.0 and mail-filter/spamassassin-3.1.8

edit: as well as app-doc/xorg-docs-1.3 and media-sound/rhythmbox-0.9.7-r3
Last edited by revenger on Sun Mar 04, 2007 11:07 pm, edited 1 time in total.
Top
revenger
n00b
n00b
User avatar
Posts: 23
Joined: Fri Sep 23, 2005 10:10 pm
Location: The Netherlands

Post by revenger » Sun Mar 04, 2007 11:02 pm

also sandbox access violation when installing pdflib-6.0.3-r1, again with paludis 0.20.1:

Code: Select all

libtool: install: warning: remember to run `libtool --finish /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux'
../../../config/install-sh -c -m 644 pdflib_pl.pm /var/tmp/paludis/media-libs/pdflib-6.0.3-r1/image///usr/lib64/perl5/site_perl/5.8.8/x86_64-linux
gmake[3]: Leaving directory `/var/tmp/paludis/media-libs/pdflib-6.0.3-r1/work/PDFlib-Lite-6.0.3/bind/pdflib/perl'
gmake[3]: Entering directory `/var/tmp/paludis/media-libs/pdflib-6.0.3-r1/work/PDFlib-Lite-6.0.3/bind/pdflib/python'
libtool: install: warning: remember to run `libtool --finish /usr/lib64/python2.4/lib-dynload'
gmake[3]: Leaving directory `/var/tmp/paludis/media-libs/pdflib-6.0.3-r1/work/PDFlib-Lite-6.0.3/bind/pdflib/python'
gmake[2]: Leaving directory `/var/tmp/paludis/media-libs/pdflib-6.0.3-r1/work/PDFlib-Lite-6.0.3/bind/pdflib'
gmake[1]: Leaving directory `/var/tmp/paludis/media-libs/pdflib-6.0.3-r1/work/PDFlib-Lite-6.0.3/bind'
gmake[1]: Entering directory `/var/tmp/paludis/media-libs/pdflib-6.0.3-r1/work/PDFlib-Lite-6.0.3/progs'
gmake[2]: Entering directory `/var/tmp/paludis/media-libs/pdflib-6.0.3-r1/work/PDFlib-Lite-6.0.3/progs/pdflib'
mkdir -p /var/tmp/paludis/media-libs/pdflib-6.0.3-r1/image//usr/bin
../../config/install-sh -c pdfimage text2pdf /var/tmp/paludis/media-libs/pdflib-6.0.3-r1/image//usr/bin
gmake[2]: Leaving directory `/var/tmp/paludis/media-libs/pdflib-6.0.3-r1/work/PDFlib-Lite-6.0.3/progs/pdflib'
gmake[1]: Leaving directory `/var/tmp/paludis/media-libs/pdflib-6.0.3-r1/work/PDFlib-Lite-6.0.3/progs'
mkdir -p /var/tmp/paludis/media-libs/pdflib-6.0.3-r1/image//usr/bin
./config/install-sh -c pdflib-config /var/tmp/paludis/media-libs/pdflib-6.0.3-r1/image//usr/bin
install: omitting directory `doc/pdflib'
gzip: /var/tmp/paludis/media-libs/pdflib-6.0.3-r1/image/usr/share/doc/pdflib-6.0.3-r1//pdflib: No such file or directory
>>> Done src_install
>>> Starting builtin_saveenv
>>> Done builtin_saveenv
>>> Completed ebuild phases init setup unpack compile test install saveenv
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/var/log/sandbox/sandbox-13229.log"

unlink:    /usr/lib/portage/pym/portage_dep.pyc (symlink to /usr/lib64/portage/pym/portage_dep.pyc)
open_wr:   /usr/lib/portage/pym/portage_dep.pyc (symlink to /usr/lib64/portage/pym/portage_dep.pyc)
unlink:    /usr/lib/portage/pym/portage_exception.pyc (symlink to /usr/lib64/portage/pym/portage_exception.pyc)
open_wr:   /usr/lib/portage/pym/portage_exception.pyc (symlink to /usr/lib64/portage/pym/portage_exception.pyc)
unlink:    /usr/lib/portage/pym/portage_versions.pyc (symlink to /usr/lib64/portage/pym/portage_versions.pyc)
open_wr:   /usr/lib/portage/pym/portage_versions.pyc (symlink to /usr/lib64/portage/pym/portage_versions.pyc)
unlink:    /usr/lib/portage/pym/portage.pyc (symlink to /usr/lib64/portage/pym/portage.pyc)
open_wr:   /usr/lib/portage/pym/portage.pyc (symlink to /usr/lib64/portage/pym/portage.pyc)
unlink:    /usr/lib/portage/pym/cache/__init__.pyc (symlink to /usr/lib64/portage/pym/cache/__init__.pyc)
open_wr:   /usr/lib/portage/pym/cache/__init__.pyc (symlink to /usr/lib64/portage/pym/cache/__init__.pyc)
unlink:    /usr/lib/portage/pym/cache/cache_errors.pyc (symlink to /usr/lib64/portage/pym/cache/cache_errors.pyc)
open_wr:   /usr/lib/portage/pym/cache/cache_errors.pyc (symlink to /usr/lib64/portage/pym/cache/cache_errors.pyc)
unlink:    /usr/lib/portage/pym/cvstree.pyc (symlink to /usr/lib64/portage/pym/cvstree.pyc)
open_wr:   /usr/lib/portage/pym/cvstree.pyc (symlink to /usr/lib64/portage/pym/cvstree.pyc)
unlink:    /usr/lib/portage/pym/xpak.pyc (symlink to /usr/lib64/portage/pym/xpak.pyc)
open_wr:   /usr/lib/portage/pym/xpak.pyc (symlink to /usr/lib64/portage/pym/xpak.pyc)
unlink:    /usr/lib/portage/pym/getbinpkg.pyc (symlink to /usr/lib64/portage/pym/getbinpkg.pyc)
open_wr:   /usr/lib/portage/pym/getbinpkg.pyc (symlink to /usr/lib64/portage/pym/getbinpkg.pyc)
unlink:    /usr/lib/portage/pym/output.pyc (symlink to /usr/lib64/portage/pym/output.pyc)
open_wr:   /usr/lib/portage/pym/output.pyc (symlink to /usr/lib64/portage/pym/output.pyc)
unlink:    /usr/lib/portage/pym/portage_const.pyc (symlink to /usr/lib64/portage/pym/portage_const.pyc)
open_wr:   /usr/lib/portage/pym/portage_const.pyc (symlink to /usr/lib64/portage/pym/portage_const.pyc)
unlink:    /usr/lib/portage/pym/portage_util.pyc (symlink to /usr/lib64/portage/pym/portage_util.pyc)
open_wr:   /usr/lib/portage/pym/portage_util.pyc (symlink to /usr/lib64/portage/pym/portage_util.pyc)
unlink:    /usr/lib/portage/pym/portage_data.pyc (symlink to /usr/lib64/portage/pym/portage_data.pyc)
open_wr:   /usr/lib/portage/pym/portage_data.pyc (symlink to /usr/lib64/portage/pym/portage_data.pyc)
unlink:    /usr/lib/portage/pym/portage_manifest.pyc (symlink to /usr/lib64/portage/pym/portage_manifest.pyc)
open_wr:   /usr/lib/portage/pym/portage_manifest.pyc (symlink to /usr/lib64/portage/pym/portage_manifest.pyc)
unlink:    /usr/lib/portage/pym/portage_checksum.pyc (symlink to /usr/lib64/portage/pym/portage_checksum.pyc)
open_wr:   /usr/lib/portage/pym/portage_checksum.pyc (symlink to /usr/lib64/portage/pym/portage_checksum.pyc)
unlink:    /usr/lib/portage/pym/portage_exec.pyc (symlink to /usr/lib64/portage/pym/portage_exec.pyc)
open_wr:   /usr/lib/portage/pym/portage_exec.pyc (symlink to /usr/lib64/portage/pym/portage_exec.pyc)
unlink:    /usr/lib/portage/pym/portage_locks.pyc (symlink to /usr/lib64/portage/pym/portage_locks.pyc)
open_wr:   /usr/lib/portage/pym/portage_locks.pyc (symlink to /usr/lib64/portage/pym/portage_locks.pyc)
unlink:    /usr/lib/portage/pym/portage_localization.pyc (symlink to /usr/lib64/portage/pym/portage_localization.pyc)
open_wr:   /usr/lib/portage/pym/portage_localization.pyc (symlink to /usr/lib64/portage/pym/portage_localization.pyc)
unlink:    /usr/lib/portage/pym/portage_gpg.pyc (symlink to /usr/lib64/portage/pym/portage_gpg.pyc)
open_wr:   /usr/lib/portage/pym/portage_gpg.pyc (symlink to /usr/lib64/portage/pym/portage_gpg.pyc)
unlink:    /usr/lib/portage/pym/eclass_cache.pyc (symlink to /usr/lib64/portage/pym/eclass_cache.pyc)
open_wr:   /usr/lib/portage/pym/eclass_cache.pyc (symlink to /usr/lib64/portage/pym/eclass_cache.pyc)
unlink:    /usr/lib/portage/pym/portage_update.pyc (symlink to /usr/lib64/portage/pym/portage_update.pyc)
open_wr:   /usr/lib/portage/pym/portage_update.pyc (symlink to /usr/lib64/portage/pym/portage_update.pyc)
unlink:    /usr/lib/portage/pym/portage_selinux.pyc (symlink to /usr/lib64/portage/pym/portage_selinux.pyc)
open_wr:   /usr/lib/portage/pym/portage_selinux.pyc (symlink to /usr/lib64/portage/pym/portage_selinux.pyc)
unlink:    /usr/lib/portage/pym/cache/metadata.pyc (symlink to /usr/lib64/portage/pym/cache/metadata.pyc)
open_wr:   /usr/lib/portage/pym/cache/metadata.pyc (symlink to /usr/lib64/portage/pym/cache/metadata.pyc)
unlink:    /usr/lib/portage/pym/cache/flat_hash.pyc (symlink to /usr/lib64/portage/pym/cache/flat_hash.pyc)
open_wr:   /usr/lib/portage/pym/cache/flat_hash.pyc (symlink to /usr/lib64/portage/pym/cache/flat_hash.pyc)
unlink:    /usr/lib/portage/pym/cache/fs_template.pyc (symlink to /usr/lib64/portage/pym/cache/fs_template.pyc)
open_wr:   /usr/lib/portage/pym/cache/fs_template.pyc (symlink to /usr/lib64/portage/pym/cache/fs_template.pyc)
unlink:    /usr/lib/portage/pym/cache/template.pyc (symlink to /usr/lib64/portage/pym/cache/template.pyc)
open_wr:   /usr/lib/portage/pym/cache/template.pyc (symlink to /usr/lib64/portage/pym/cache/template.pyc)
unlink:    /usr/lib/portage/pym/cache/mappings.pyc (symlink to /usr/lib64/portage/pym/cache/mappings.pyc)
open_wr:   /usr/lib/portage/pym/cache/mappings.pyc (symlink to /usr/lib64/portage/pym/cache/mappings.pyc)
unlink:    /usr/lib/portage/pym/portage_dep.pyc (symlink to /usr/lib64/portage/pym/portage_dep.pyc)
open_wr:   /usr/lib/portage/pym/portage_dep.pyc (symlink to /usr/lib64/portage/pym/portage_dep.pyc)
unlink:    /usr/lib/portage/pym/portage_exception.pyc (symlink to /usr/lib64/portage/pym/portage_exception.pyc)
open_wr:   /usr/lib/portage/pym/portage_exception.pyc (symlink to /usr/lib64/portage/pym/portage_exception.pyc)
unlink:    /usr/lib/portage/pym/portage_versions.pyc (symlink to /usr/lib64/portage/pym/portage_versions.pyc)
open_wr:   /usr/lib/portage/pym/portage_versions.pyc (symlink to /usr/lib64/portage/pym/portage_versions.pyc)
unlink:    /usr/lib/portage/pym/portage.pyc (symlink to /usr/lib64/portage/pym/portage.pyc)
open_wr:   /usr/lib/portage/pym/portage.pyc (symlink to /usr/lib64/portage/pym/portage.pyc)
unlink:    /usr/lib/portage/pym/cache/__init__.pyc (symlink to /usr/lib64/portage/pym/cache/__init__.pyc)
open_wr:   /usr/lib/portage/pym/cache/__init__.pyc (symlink to /usr/lib64/portage/pym/cache/__init__.pyc)
unlink:    /usr/lib/portage/pym/cache/cache_errors.pyc (symlink to /usr/lib64/portage/pym/cache/cache_errors.pyc)
open_wr:   /usr/lib/portage/pym/cache/cache_errors.pyc (symlink to /usr/lib64/portage/pym/cache/cache_errors.pyc)
unlink:    /usr/lib/portage/pym/cvstree.pyc (symlink to /usr/lib64/portage/pym/cvstree.pyc)
open_wr:   /usr/lib/portage/pym/cvstree.pyc (symlink to /usr/lib64/portage/pym/cvstree.pyc)
unlink:    /usr/lib/portage/pym/xpak.pyc (symlink to /usr/lib64/portage/pym/xpak.pyc)
open_wr:   /usr/lib/portage/pym/xpak.pyc (symlink to /usr/lib64/portage/pym/xpak.pyc)
unlink:    /usr/lib/portage/pym/getbinpkg.pyc (symlink to /usr/lib64/portage/pym/getbinpkg.pyc)
open_wr:   /usr/lib/portage/pym/getbinpkg.pyc (symlink to /usr/lib64/portage/pym/getbinpkg.pyc)
unlink:    /usr/lib/portage/pym/output.pyc (symlink to /usr/lib64/portage/pym/output.pyc)
open_wr:   /usr/lib/portage/pym/output.pyc (symlink to /usr/lib64/portage/pym/output.pyc)
unlink:    /usr/lib/portage/pym/portage_const.pyc (symlink to /usr/lib64/portage/pym/portage_const.pyc)
open_wr:   /usr/lib/portage/pym/portage_const.pyc (symlink to /usr/lib64/portage/pym/portage_const.pyc)
unlink:    /usr/lib/portage/pym/portage_util.pyc (symlink to /usr/lib64/portage/pym/portage_util.pyc)
open_wr:   /usr/lib/portage/pym/portage_util.pyc (symlink to /usr/lib64/portage/pym/portage_util.pyc)
unlink:    /usr/lib/portage/pym/portage_data.pyc (symlink to /usr/lib64/portage/pym/portage_data.pyc)
open_wr:   /usr/lib/portage/pym/portage_data.pyc (symlink to /usr/lib64/portage/pym/portage_data.pyc)
unlink:    /usr/lib/portage/pym/portage_manifest.pyc (symlink to /usr/lib64/portage/pym/portage_manifest.pyc)
open_wr:   /usr/lib/portage/pym/portage_manifest.pyc (symlink to /usr/lib64/portage/pym/portage_manifest.pyc)
unlink:    /usr/lib/portage/pym/portage_checksum.pyc (symlink to /usr/lib64/portage/pym/portage_checksum.pyc)
open_wr:   /usr/lib/portage/pym/portage_checksum.pyc (symlink to /usr/lib64/portage/pym/portage_checksum.pyc)
unlink:    /usr/lib/portage/pym/portage_exec.pyc (symlink to /usr/lib64/portage/pym/portage_exec.pyc)
open_wr:   /usr/lib/portage/pym/portage_exec.pyc (symlink to /usr/lib64/portage/pym/portage_exec.pyc)
unlink:    /usr/lib/portage/pym/portage_locks.pyc (symlink to /usr/lib64/portage/pym/portage_locks.pyc)
open_wr:   /usr/lib/portage/pym/portage_locks.pyc (symlink to /usr/lib64/portage/pym/portage_locks.pyc)
unlink:    /usr/lib/portage/pym/portage_localization.pyc (symlink to /usr/lib64/portage/pym/portage_localization.pyc)
open_wr:   /usr/lib/portage/pym/portage_localization.pyc (symlink to /usr/lib64/portage/pym/portage_localization.pyc)
unlink:    /usr/lib/portage/pym/portage_gpg.pyc (symlink to /usr/lib64/portage/pym/portage_gpg.pyc)
open_wr:   /usr/lib/portage/pym/portage_gpg.pyc (symlink to /usr/lib64/portage/pym/portage_gpg.pyc)
unlink:    /usr/lib/portage/pym/eclass_cache.pyc (symlink to /usr/lib64/portage/pym/eclass_cache.pyc)
open_wr:   /usr/lib/portage/pym/eclass_cache.pyc (symlink to /usr/lib64/portage/pym/eclass_cache.pyc)
unlink:    /usr/lib/portage/pym/portage_update.pyc (symlink to /usr/lib64/portage/pym/portage_update.pyc)
open_wr:   /usr/lib/portage/pym/portage_update.pyc (symlink to /usr/lib64/portage/pym/portage_update.pyc)
unlink:    /usr/lib/portage/pym/portage_selinux.pyc (symlink to /usr/lib64/portage/pym/portage_selinux.pyc)
open_wr:   /usr/lib/portage/pym/portage_selinux.pyc (symlink to /usr/lib64/portage/pym/portage_selinux.pyc)
unlink:    /usr/lib/portage/pym/cache/metadata.pyc (symlink to /usr/lib64/portage/pym/cache/metadata.pyc)
open_wr:   /usr/lib/portage/pym/cache/metadata.pyc (symlink to /usr/lib64/portage/pym/cache/metadata.pyc)
unlink:    /usr/lib/portage/pym/cache/flat_hash.pyc (symlink to /usr/lib64/portage/pym/cache/flat_hash.pyc)
open_wr:   /usr/lib/portage/pym/cache/flat_hash.pyc (symlink to /usr/lib64/portage/pym/cache/flat_hash.pyc)
unlink:    /usr/lib/portage/pym/cache/fs_template.pyc (symlink to /usr/lib64/portage/pym/cache/fs_template.pyc)
open_wr:   /usr/lib/portage/pym/cache/fs_template.pyc (symlink to /usr/lib64/portage/pym/cache/fs_template.pyc)
unlink:    /usr/lib/portage/pym/cache/template.pyc (symlink to /usr/lib64/portage/pym/cache/template.pyc)
open_wr:   /usr/lib/portage/pym/cache/template.pyc (symlink to /usr/lib64/portage/pym/cache/template.pyc)
unlink:    /usr/lib/portage/pym/cache/mappings.pyc (symlink to /usr/lib64/portage/pym/cache/mappings.pyc)
open_wr:   /usr/lib/portage/pym/cache/mappings.pyc (symlink to /usr/lib64/portage/pym/cache/mappings.pyc)
--------------------------------------------------------------------------------

Install error:
  * In program paludis -i --dl-reinstall if-use-changed world:
  * When performing install action from command line:
  * When executing install task:
  * Install error: Install failed for 'media-libs/pdflib-6.0.3-r1::gentoo'
Top
govi
n00b
n00b
Posts: 2
Joined: Sun Jan 21, 2007 4:13 pm

Post by govi » Sun Mar 04, 2007 11:14 pm

Code: Select all

paludis@1173050235: [WARNING] The names_cache key is not set in '/etc/paludis/repositories/paludis-overlay.conf'. You should read http://paludis.pioto.org/cachefiles.html and select an appropriate value.
Building target list...
Building dependency list...
Unhandled exception:
  * In program paludis -pi world:
  * When performing install action from command line:
  * When executing install task:
  * When adding PackageDepSpec 'virtual/baselayout':
  * When fetching metadata for 'sys-apps/baselayout-1.12.6':
  * When loading VDBRepository entry for 'sys-apps/baselayout-1.12.6' from '/var/db/pkg':
  * When validating use flag name 'bzip2%':
  * Name 'bzip2%' is not a valid use flag name (paludis::UseFlagNameError)
I've just install paludis. What I ned to do to it work?
I've done of course what was writen in migration guide( manual method).
Top
truc
Advocate
Advocate
User avatar
Posts: 3199
Joined: Mon Jul 25, 2005 9:24 am

Post by truc » Mon Mar 05, 2007 7:41 am

a good start would be to read those paludis WARNINGS you've just pasted here... You can at the very least suppress one of them
The End of the Internet!
Top
nikaya
Veteran
Veteran
User avatar
Posts: 1471
Joined: Sat May 13, 2006 9:43 am
Location: Germany

Post by nikaya » Mon Mar 05, 2007 9:00 am

govi wrote: I've just install paludis. What I ned to do to it work?
I've done of course what was writen in migration guide( manual method).
As long as you are not experienced and familiar with paludis I recommend using the portage2paludis.bash script.
Notes on Dhamma
How to waste your time: look for an explanation of consciousness, ask to know what feeling is. (Nanavira Thera)
Top
spb
Retired Dev
Retired Dev
User avatar
Posts: 2135
Joined: Fri Jan 02, 2004 1:18 pm
Location: Cambridge, UK

Post by spb » Mon Mar 05, 2007 3:51 pm

govi wrote:

Code: Select all

paludis@1173050235: [WARNING] The names_cache key is not set in '/etc/paludis/repositories/paludis-overlay.conf'. You should read http://paludis.pioto.org/cachefiles.html and select an appropriate value.
Building target list...
Building dependency list...
Unhandled exception:
  * In program paludis -pi world:
  * When performing install action from command line:
  * When executing install task:
  * When adding PackageDepSpec 'virtual/baselayout':
  * When fetching metadata for 'sys-apps/baselayout-1.12.6':
  * When loading VDBRepository entry for 'sys-apps/baselayout-1.12.6' from '/var/db/pkg':
  * When validating use flag name 'bzip2%':
  * Name 'bzip2%' is not a valid use flag name (paludis::UseFlagNameError)
It looks like your vdb entry for baselayout is broken. Look in /var/db/pkg/sys-apps/baselayout-1.12.6/USE and remove any % signs you may see. If there aren't any, look for the string 'bzip2%' in any other files in that directory and remove what appears to be the culprit.
14:20:19 <mark_alec> i fail
..shortly afterwards...
14:32:09 <spb> so it's "do what i want or i ban you"
14:32:13 <mark_alec> yes
Top
govi
n00b
n00b
Posts: 2
Joined: Sun Jan 21, 2007 4:13 pm

Post by govi » Mon Mar 05, 2007 9:43 pm

OK, now it's working.
Top
BlueZeniX
n00b
n00b
Posts: 52
Joined: Sat Jun 28, 2003 4:43 pm
Location: The Netherlands
Contact:
Contact BlueZeniX
Website

Install stage acting weird

Post by BlueZeniX » Wed Mar 07, 2007 1:31 pm

Hi everyone,

I've been using paludis for a while now and its definately much faster. The lack of --skipfirst and having to copy paste the resume command everytime something fails is one thing I dislike, but overall its really great.

Now I have a weird issue with a custom ebuild for neko (www.nekovm.org) which I need for haXe (www.haxe.org).
Compiling and all goes well, install stage finishes. But its not installing the correct files.

When I press CTRL-Z and go to /var/tmp/paludis/dev-lang/neko-1.5.3/work/neko-1.5.3/bin/, there are a few files:

Code: Select all

-rwxr-xr-x 1 root root  124816 mrt  7 14:26 libneko.so
-rwxr-xr-x 1 root root 1467617 mrt  7 14:27 mysql.ndll
-rwxr-xr-x 1 root root    9572 mrt  7 14:26 neko
-rwxr-xr-x 1 root root  173671 mrt  7 14:27 nekoc
-rwxr-xr-x 1 root root  273097 mrt  7 14:27 nekoml
-rwxr-xr-x 1 root root   69951 mrt  7 14:27 nekotools
-rwxr-xr-x 1 root root   13757 mrt  7 14:27 regexp.ndll
-rwxr-xr-x 1 root root   14300 mrt  7 14:27 sqlite.ndll
-rwxr-xr-x 1 root root   92000 mrt  7 14:26 std.ndll
-rw-r--r-- 1 root root     175 mrt  7 14:27 test.n
-rwxr-xr-x 1 root root   13951 mrt  7 14:27 zlib.ndll
All the neko* files need to be installed in /usr/bin according to the ebuild:

Code: Select all

src_install() {
    exeinto /usr/bin

    doexe bin/neko
    doexe bin/nekoc
    doexe bin/nekoml
    doexe bin/nekotools

    dolib.so bin/libneko.so

    insinto /usr/neko/lib
    doins bin/std.ndll
    doins bin/regexp.ndll
    doins bin/mysql.ndll
    doins bin/zlib.ndll

    if use apache2 ; then
        uses_apache2
        insinto ${APACHE2_MODULESDIR}
        doins bin/mod_neko2.ndll
        insinto ${APACHE2_MODULES_CONFDIR}
        doins ${FILESDIR}/50_mod_neko.conf
    fi

    insinto /usr/include/neko
    doins vm/neko.h

    doenvd ${FILESDIR}/50neko
}
...So after installation all works out well I go to

Code: Select all

zenix bin # cd /usr/bin/
zenix bin # ls -Al neko*
-rwxr-xr-x 1 root root 9572 mrt  7 14:29 neko
-rwxr-xr-x 1 root root 9572 mrt  7 14:29 nekoc
-rwxr-xr-x 1 root root 9572 mrt  7 14:29 nekoml
-rwxr-xr-x 1 root root 9572 mrt  7 14:29 nekotools
nekoc, nekoml and nekotools are all the same file as "neko"!!

So my question here:

Why?!?! 8O
Oi!
Top
dhave
Apprentice
Apprentice
User avatar
Posts: 298
Joined: Fri Oct 28, 2005 4:03 pm
Location: Still outside the Matrix ...

Post by dhave » Wed Mar 07, 2007 5:11 pm

Could I make another appeal that this thread be closed and that future Paludis posts be in separate threads by exact topic with [PALUDIS] in the subject?

Just now I did a forum search on "stale cache", and this thread came up among the results. Since this thread is currently 13 pages long with 315 replies, I would have had to open every page and do a page search. Instead, I had to just skip this thread altogether.

See my point? For support threads to be useful, they have to be searchable, and an open-ended mega-thread like this one is not searchable. Especially since Paludis is in heavy development with a lot of people testing, we need a decent support format.

Thanks.
Last edited by dhave on Wed Mar 07, 2007 5:19 pm, edited 1 time in total.
This space available!
Top
zxy
Veteran
Veteran
User avatar
Posts: 1160
Joined: Fri Jan 06, 2006 8:07 am
Location: in bed in front of the computer
Contact:
Contact zxy
Website

Post by zxy » Wed Mar 07, 2007 5:15 pm

dhave you can serch the topic only and you get a list of posts. Quite easy.
You don't need to see all the topics on all the pages.
Last edited by zxy on Wed Mar 07, 2007 5:20 pm, edited 1 time in total.
Nature does not hurry, yet everything is accomplished.
Lao Tzu
Top
dhave
Apprentice
Apprentice
User avatar
Posts: 298
Joined: Fri Oct 28, 2005 4:03 pm
Location: Still outside the Matrix ...

Post by dhave » Wed Mar 07, 2007 5:19 pm

zxy wrote:dhave you can serch the topic only and you get a list of posts. Quite easy.
I don't see that in the search options. Please instruct me! Thanks.
This space available!
Top
dhave
Apprentice
Apprentice
User avatar
Posts: 298
Joined: Fri Oct 28, 2005 4:03 pm
Location: Still outside the Matrix ...

Post by dhave » Wed Mar 07, 2007 5:21 pm

dhave wrote:
zxy wrote:dhave you can serch the topic only and you get a list of posts. Quite easy.
I don't see that in the search options. Please instruct me! Thanks.
Just found it. I seldom use Quick Search, and that's where the option was.

Thanks! I wonder how much longer I would have gone without knowing about that useful feature.
This space available!
Top
alligator421
Apprentice
Apprentice
Posts: 191
Joined: Wed Jul 30, 2003 10:36 pm

Post by alligator421 » Sat Mar 10, 2007 12:18 am

Upgrading hdparm package replaced my /etc/init.d/hdparm. same with acpid. Why /etc/init.d directory is not config protected ? All /etc should be protected imho. bug ? feature ?
Top
Jeremy_Z
l33t
l33t
User avatar
Posts: 671
Joined: Mon Apr 05, 2004 3:21 pm
Location: Shanghai

Post by Jeremy_Z » Sat Mar 10, 2007 10:51 am

init.d should not contain any configuration, conf.d have.

But when i have packages upgrading /etc/init.d/ i have to make a dispatch-conf, it is not automatic.
"Because two groups of consumers drive the absolute high end of home computing: the gamers and the porn surfers." /.
My gentoo projects, Kelogviewer and a QT4 gui for etc-proposals
Top
alligator421
Apprentice
Apprentice
Posts: 191
Joined: Wed Jul 30, 2003 10:36 pm

Post by alligator421 » Sun Mar 11, 2007 7:14 am

alligator421 wrote:Upgrading hdparm package replaced my /etc/init.d/hdparm. same with acpid. Why /etc/init.d directory is not config protected ? All /etc should be protected imho. bug ? feature ?
Ok. I found out.
It seems paludis overwrite or "touch" /etc/init.d/hdparm, thus changing date stamp, if file is all the same as before.
If there is any difference it will put an ._cfg000_hdparm which is right.
Top
zxy
Veteran
Veteran
User avatar
Posts: 1160
Joined: Fri Jan 06, 2006 8:07 am
Location: in bed in front of the computer
Contact:
Contact zxy
Website

Post by zxy » Tue Mar 13, 2007 10:40 am

The Paludis 'Killer Feature'?

It's been put together nicely. :D
Nature does not hurry, yet everything is accomplished.
Lao Tzu
Top
yoshi314
l33t
l33t
User avatar
Posts: 852
Joined: Thu Dec 30, 2004 9:33 pm
Location: PL
Contact:
Contact yoshi314
Website

Post by yoshi314 » Tue Mar 13, 2007 3:59 pm

a quick question - i have setup rsync to produce verbose output when doing sync, just like it was a couple of months ago by default in gentoo.

the thing that bothers me now is that when paludis synchronizes (synces? synchs?) main gentoo repository it redownloads everything from scratch.

plain emerge --sync does not do that, because rsync says that timestamps are identical on rsync server and on my pc. if i launch paludis directly after that emerge --sync paludis still wants to redownload everything, as if it did not notice my portage tree (but it installs packages just fine).

/etc/paludis/repositories/gentoo.conf

Code: Select all

location = /usr/portage
sync = rsync://rsync.europe.gentoo.org/gentoo-portage
profiles = /usr/portage/profiles/default-linux/x86/2006.1/desktop
distdir = /home/gentoo/distfiles
format = ebuild
names_cache = ${location}/.cache/names
write_cache = /var/cache/paludis/metadata
what is wrong with my setup? i created initial configs with migration script.
~amd64
Top
Locked
494 posts
  • Page 13 of 20
    • Jump to page:
  • Previous
  • 1
  • …
  • 11
  • 12
  • 13
  • 14
  • 15
  • …
  • 20
  • Next

Return to “Unsupported Software”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy

 

 

magic