Re: [gentoo-user] CFLAGS
I feel like the Pentium D is march=prescott though, again, native should work fine as well. Chris Reffett On 11/02/2010 06:40 AM, Yohan Pereira wrote: On Tuesday 02 November 2010 2:13:41 pm Coert Waagmeester wrote: I have installed a 64 bit gentoo on my intel Pentium D machine. also as far as i know, core2 is for core 2 duo quad etc cpus ... not for pentium D. -O2 -march=core2 -pipe use native as Alan suggested. or refer to http://www.gentoo-wiki.info/Safe_Cflags
Re: [gentoo-user] NetworkManager SIGSEGV
It was probably the wpa_supplicant update, see bug 320097 on bugs.gentoo.org. Just had this problem myself this morning, you can fix it by using the ebuild provided in the bug or by downgrading wpa_supplicant (which had 0.7.2 hardmasked today). Hope this helps! Chris Reffett On 05/18/2010 09:57 PM, Iain Buchanan wrote: After a recent upgrade, the NetworkManager daemon crashes (for me!). Thanks in advance to to those who are about to suggest that I use something else, but NM has features I use that nothing else provides :) The backtrace is HUGE, so there's obviously some loop going on somewhere, but according to my earlier problems with massive amounts of logging, I don't think this is the cause of the current seg fault. Can someone tell me what needs to be recompiled / downgraded to fix it? I've had no luck figuring it out so far! the innermost 10 frames are: #0 0xb794 in _IO_vfprintf_internal (s=0xbf80042c, format=0x80b38e4 WARN %s(): Trying to remove a non-existant call id.\n, ap=0xbf8009fc \\9\v\b\023좷ä\n\200¿¿\n\200¿\001) at vfprintf.c:197 #1 0xb79f12e2 in *__GI___vasprintf_chk (result_ptr=0xbf80053c, flags=1, format=0x80b38e4 WARN %s(): Trying to remove a non-existant call id.\n, args=0xbf8009fc \\9\v\b\023좷ä\n\200¿¿\n\200¿\001) at vasprintf_chk.c:68 #2 0xb7aebb4f in vasprintf (string=0xbf80053c, format=0x80b38e4 WARN %s(): Trying to remove a non-existant call id.\n, args=0xbf8009fc \\9\v\b\023좷ä\n\200¿¿\n\200¿\001) at /usr/include/bits/stdio2.h:199 #3 IA__g_vasprintf (string=0xbf80053c, format=0x80b38e4 WARN %s(): Trying to remove a non-existant call id.\n, args=0xbf8009fc \\9\v\b\023좷ä\n\200¿¿\n\200¿\001) at gprintf.c:315 #4 0xb7ad7a16 in IA__g_strdup_vprintf (format=0x80b38e4 WARN %s(): Trying to remove a non-existant call id.\n, args=0xbf8009fc \\9\v\b\023좷ä\n\200¿¿\n\200¿\001) at gstrfuncs.c:244 #5 0xb7abf3e0 in IA__g_logv (log_domain=value optimized out, log_level=G_LOG_LEVEL_WARNING, format=0x80b38e4 WARN %s(): Trying to remove a non-existant call id.\n, args1=0xbf8009fc \\9\v\b\023좷ä\n\200¿¿\n\200¿\001) at gmessages.c:516 #6 0xb7abf846 in IA__g_log (log_domain=0x0, log_level=G_LOG_LEVEL_WARNING, format=0x80b38e4 WARN %s(): Trying to remove a non-existant call id.\n) at gmessages.c:569 #7 0x0805e72c in nm_call_store_remove (store=0x80f8320, object=0x80f92e0, call_id=0x1) at nm-call-store.c:71 #8 0x0809f34a in nm_supplicant_info_destroy (user_data=0x80e3760) at nm-supplicant-interface.c:179 #9 0xb7c682f9 in d_pending_call_free (data=0x80d8388) at /var/tmp/portage/dev-libs/dbus-glib-0.86/work/dbus-glib-0.86/dbus/dbus-gproxy.c:1780 and most of this will repeat a few thousand times. and the outermost 10 frames are: #174513 0xb7bc6d76 in IA__g_signal_emit (instance=0x80d70b8, signal_id=8, detail=81) at gsignal.c:3037 #174514 0xb7c6d52d in dbus_g_proxy_emit_remote_signal (connection=0x80d5418, message=0x80d56d8, user_data=0x80d4878) at /var/tmp/portage/dev-libs/dbus-glib-0.86/work/dbus-glib-0.86/dbus/dbus-gproxy.c:1734 #174515 dbus_g_proxy_manager_filter (connection=0x80d5418, message=0x80d56d8, user_data=0x80d4878) at /var/tmp/portage/dev-libs/dbus-glib-0.86/work/dbus-glib-0.86/dbus/dbus-gproxy.c:1301 #174516 0xb7c31ecb in dbus_connection_dispatch (connection=0x80d5418) at dbus-connection.c:4451 #174517 0xb7c6360d in message_queue_dispatch (source=0x80d6d80, callback=0, user_data=0x0) at /var/tmp/portage/dev-libs/dbus-glib-0.86/work/dbus-glib-0.86/dbus/dbus-gmain.c:101 #174518 0xb7ab57b8 in g_main_dispatch (context=0x80d2e08) at gmain.c:1960 #174519 IA__g_main_context_dispatch (context=0x80d2e08) at gmain.c:2513 #174520 0xb7ab9050 in g_main_context_iterate (context=0x80d2e08, block=value optimized out, dispatch=1, self=0x80cc170) at gmain.c:2591 #174521 0xb7ab94bf in IA__g_main_loop_run (loop=0x80d2e98) at gmain.c:2799 #174522 0x0807f1ac in main (argc=1, argv=0xbfffee84) at NetworkManager.c:648 I've recompiled dbus, dbus-glib, networkmanager and a bunch of stuff, but to no avail. The last updates before it broke were: dev-libs/nspr-4.8.4-r1 dev-libs/libsigc++-2.2.7 dev-lang/swig-1.3.40-r1 dev-lang/orc-0.4.4 sci-libs/proj-4.7.0 media-libs/tiff-4.0.0_beta5 x11-libs/pixman-0.18.2 dev-perl/libwww-perl-5.836 sci-libs/libgeotiff-1.3.0_rc2-r1 net-dns/bind-tools-9.7.0_p1 sci-libs/gdal-1.7.1-r1 x11-proto/xproto-7.0.17 net-wireless/wpa_supplicant-0.7.2 sys-power/pm-utils-1.3.0-r3 media-fonts/urwvn-fonts-3.05 sys-auth/nss-mdns-0.10 dev-libs/totem-pl-parser-2.28.3 sys-fs/cryptsetup-1.1.1_rc2 sys-fs/udev-154 sci-geosciences/googleearth-5.1.3535.3218 gnome-base/librsvg-2.26.3 media-gfx/gtkam-0.1.17 x11-base/xorg-server-1.8.1 app-emulation/wine-1.1.44 sci-libs/libgeotiff-1.3.0_rc2-r1 sci-libs/gdal-1.7.1-r1 any ideas? thanks,
Re: [gentoo-user] Re: libpng12 is missing
On 05/09/2010 09:32 AM, walt wrote: On 05/09/2010 05:10 AM, Xi Shen wrote: hi, my system is gentoo amd64, kde 4.3. i just updated my portage, and updated the world. then i ran revdep-rebuild, and i got a error when building notification-daemon-0.4.0-r1. the error found in the build log is: cannot find -lpng12 i have both libpng-1.2.43-r1 and libpng-1.4.2 installed, but i do not have libpng12.a in my /usr/lib64 directory. and 'pkg-config libpng --libs' only show '-lpng14'. Are you sure you still have version 1.2.43 installed? I'm going thru the same thing now on x86 and libpng-1.2 was deleted during the update. I now have only 1.4.2 remaining. Revdep-rebuild has been enumerating broken files for twenty minutes and is still going. I've never seen breakage this bad before. This machine is going to be useless for the next 24 hours or so until all the packages are rebuilt. It looks like preserved-libs didn't catch this one either. I just ran revdep-rebuild overnight, and now notification-daemon and pygtk won't build. But emerge @preserved-rebuild came up with nothing before the revdep-rebuild. Chris Reffett
Re: [gentoo-user] stop eth0 from starting at boot
The easiest way to rectify this, I've found, is to just delete /etc/init.d/net.eth0. Alternately, if you do want to keep the init script around, but don't want to wait for it to time out before continuing the boot process, what I did was add dhcpcd_eth0=-b to fork it into the background. As for what is trying to start net.eth0, I think there's an option in either /etc/rc.conf or /etc/conf.d/rc that determines what counts as net for init scripts that need net: no net required, loopback only, one non-loopback, or all of the net.* scripts. Try looking into that. Chris Reffett On 03/09/2010 09:47 PM, Tony Miller wrote: /etc/init.d/net.eth0 is not in any runlevels: o_0 tony # rc-update show bootmisc | boot checkfs | boot checkroot | boot clock | boot consolefont | boot hald | default hostname | boot keymaps | boot local | default nonetwork localmount | boot modules | boot net.lo | boot net.wlan0 | default netmount | default ntp-client | default rmnologin | boot sshd | default udev-postmount | default urandom | boot vixie-cron | default xdm | default Yet it still insists on trying to start at boot! This isn't What I Want, since this computer is a laptop and I generally use the wifi. Could it be related to udev or hotplug? Thanks, -Tony
Re: [gentoo-user] What's happening to six-0.5.3?
Six depends on kde 3.5, which has been hardmasked for removal from the portage tree. I believe you can use the kde-sunset overlay to keep it around if you really need it. Or maybe there's a version in the works for KDE 4? Chris Reffett On 01/02/2010 11:12 AM, Kevin O'Gorman wrote: I've been playing with this game (hex) using six through many revisions. It now appears that the latest version has been hard masked. I wonder why. I don't see anything wrong in its function, even under KDE 4, although it does not show up in my menus without help. It has not undergone an upgrade in a few years, but it was still entered in the Computer Olympiad in 2009. It didn't win, but made a fair showing. -- Kevin O'Gorman, PhD
Re: [gentoo-user] Re: fsck date problem during boot
Dale wrote: Harry Putnam wrote: Stroller strol...@stellar.eclipse.co.uk writes: On 4 Nov 2009, at 15:45, Harry Putnam wrote: ... Somehow the date of last fsck on /boot is seen as `in the future' so fsck fails on /dev/had1 (/boot). The first thing I would want to check is the motherboard battery. Is the time correct if you reboot and immediately enter BIOS? That was a pretty good help but apparently not all the story. When I checked bios, the clock was exactly 1 hr fast (didn't pick up the end of daylight saving time I guess). Reset the clock and tested with 2 more reboots, each time mounting /boot and fiddling around with files. Each time the same failure occurs. I check bios time again. Its right. Here is the (edited) output form fsck Superblock last mount time (Wed Nov 4 18:05:13 2009, now = Wed Nov 4 12:11:49 2009) is in the future. Fixy? yes [...] ---- ---=--- - Superblock last mount time (Wed Nov 4 18:14:54 2009, now = Wed Nov 4 12:18:01 2009) is in the future. Fixy? yes [...] so still somehow, those last mount dates are way wrong. I hope I'm checking the right thing in bios. Its under cmos and shows the time ticking away. You can adjust all columns. with +/-. I can't recall exactly how I did this but there is a command to tell the OS to set the clock on the mobo to the system time when shutting down. That way everything should sync up when you reboot, except for that tiny little bit if you shutdown completely for a few days or something. The command is hwclock. I can't recall where I put the thing because I am logged into KDE 4 and I can't find nothing in here yet. It's pretty but it is different so I'm lost. I *think* I put it in the rc file or something. I remember the file is run during shutdown tho. That may help if you know which file that is. Hope that helps. Dale :-) :-) It's in /etc/conf.d/clock (or /etc/conf.d/hwclock for baselayout 2/openrc), and it's called CLOCK_SYSTOHC. Set it to yes to write the system time to hardware on shutdown.
Re: [gentoo-user] Re: license mask
Nikos Chantziaras wrote: On 10/19/2009 03:33 AM, Crístian Viana wrote: hi! when I try to update virtualbox-ose-additions, portage says: !!! All ebuilds that could satisfy ~app-emulation/virtualbox-ose-additions-3.0.8 have been masked. !!! One of the following masked packages is required to complete your request: - app-emulation/virtualbox-ose-additions-3.0.8 (masked by: PUEL license(s)) A copy of the 'PUEL' license is located at '/usr/portage/licenses/PUEL'. it suggests me to read the Gentoo Handbook, but it isn't updated. what should I do to unmask this package? I've never seen this kind of masking. In make.conf: ACCEPT_LICENSE=* to unmask all licenses. Or else name the licenses you wish unmasked one by one. Yeah, they added this in a recent portage-2.2 rc. It masks end user license agreements by default (-...@eula is the syntax, if I recall correctly)
Re: [gentoo-user] Re: license mask
Dale wrote: Chris Reffett wrote: Nikos Chantziaras wrote: On 10/19/2009 03:33 AM, Crístian Viana wrote: hi! when I try to update virtualbox-ose-additions, portage says: !!! All ebuilds that could satisfy ~app-emulation/virtualbox-ose-additions-3.0.8 have been masked. !!! One of the following masked packages is required to complete your request: - app-emulation/virtualbox-ose-additions-3.0.8 (masked by: PUEL license(s)) A copy of the 'PUEL' license is located at '/usr/portage/licenses/PUEL'. it suggests me to read the Gentoo Handbook, but it isn't updated. what should I do to unmask this package? I've never seen this kind of masking. In make.conf: ACCEPT_LICENSE=* to unmask all licenses. Or else name the licenses you wish unmasked one by one. Yeah, they added this in a recent portage-2.2 rc. It masks end user license agreements by default (-...@eula is the syntax, if I recall correctly) I checked make.conf.example and this is not documented yet. I'm on portage-2.2_rc46. Is it in a later version or did I miss something? The file I checked is here: /usr/share/portage/config/make.conf.example Just curious. Dale :-) You've got a recent enough version, I think it came in around rc44 or so. Look in 'man make.conf' for the info on it...I guess they haven't changed make.conf.example yet.
Re: [gentoo-user] Re: Syntax for masking kde:4?
Couldn't you just grab the kde 4.3 package.keyword list and append that to package.mask, since it uses the same slot format? Nikos Chantziaras wrote: On 10/11/2009 02:30 PM, Peter Humphrey wrote: Hello list, In the last few days some parts of KDE v4 seem to have been moved into the stable tree, but on some of my boxes I want to exclude kde:4 (but not qt:4). What is the syntax for a single entry in package.mask to exclude the whole of kde:4? I did start masking each package separately, but that's far too much work - I'd finish up with an entry for every kde package that has a version 4. Also, kde:4, which seems like the right thing to specify, is an invalid package atom according to eix. I can't see anything relevant in man pages or the gentoo kde configuration guide. Google hasn't helped me either. Portage unfortunately doesn't allow wildcards in the package name of atoms. But you can install KDE4 on one machine and then use: qlist -ISLC kde-base/*:4.3 to generate a list to put in package.mask in the machines you don't want KDE4. On my machine, the above command results in the following (it should at least cut down on the rest of the packages you need to mask): kde-base/ark:4.3 kde-base/dolphin:4.3 kde-base/drkonqi:4.3 kde-base/gwenview:4.3 kde-base/kamera:4.3 kde-base/kappfinder:4.3 kde-base/kapptemplate:4.3 kde-base/kate:4.3 kde-base/kcalc:4.3 kde-base/kcheckpass:4.3 kde-base/kcminit:4.3 kde-base/kcmshell:4.3 kde-base/kcolorchooser:4.3 kde-base/kcontrol:4.3 kde-base/kde-env:4.3 kde-base/kdeartwork-colorschemes:4.3 kde-base/kdeartwork-desktopthemes:4.3 kde-base/kdeartwork-emoticons:4.3 kde-base/kdeartwork-iconthemes:4.3 kde-base/kdeartwork-kscreensaver:4.3 kde-base/kdeartwork-meta:4.3 kde-base/kdeartwork-sounds:4.3 kde-base/kdeartwork-styles:4.3 kde-base/kdeartwork-wallpapers:4.3 kde-base/kdeartwork-weatherwallpapers:4.3 kde-base/kdebase-cursors:4.3 kde-base/kdebase-data:4.3 kde-base/kdebase-desktoptheme:4.3 kde-base/kdebase-kioslaves:4.3 kde-base/kdebase-menu:4.3 kde-base/kdebase-menu-icons:4.3 kde-base/kdebase-meta:4.3 kde-base/kdebase-startkde:4.3 kde-base/kdebase-wallpapers:4.3 kde-base/kdebugdialog:4.3 kde-base/kdegraphics-meta:4.3 kde-base/kdegraphics-strigi-analyzer:4.3 kde-base/kdelibs:4.3 kde-base/kdepasswd:4.3 kde-base/kdepimlibs:4.3 kde-base/kdeplasma-addons:4.3 kde-base/kdesu:4.3 kde-base/kdialog:4.3 kde-base/kdm:4.3 kde-base/kdnssd:4.3 kde-base/keditbookmarks:4.3 kde-base/keditfiletype:4.3 kde-base/kephal:4.3 kde-base/kfile:4.3 kde-base/kfind:4.3 kde-base/kfmclient:4.3 kde-base/kgamma:4.3 kde-base/kget:4.3 kde-base/kglobalaccel:4.3 kde-base/khelpcenter:4.3 kde-base/khotkeys:4.3 kde-base/kiconfinder:4.3 kde-base/kinfocenter:4.3 kde-base/kioclient:4.3 kde-base/klipper:4.3 kde-base/kmenuedit:4.3 kde-base/kmimetypefinder:4.3 kde-base/knetattach:4.3 kde-base/knewstuff:4.3 kde-base/knotify:4.3 kde-base/kolourpaint:4.3 kde-base/konqueror:4.3 kde-base/konsole:4.3 kde-base/kpasswdserver:4.3 kde-base/kquitapp:4.3 kde-base/krdc:4.3 kde-base/kreadconfig:4.3 kde-base/krosspython:4.3 kde-base/kruler:4.3 kde-base/krunner:4.3 kde-base/ksaneplugin:4.3 kde-base/kscreensaver:4.3 kde-base/ksmserver:4.3 kde-base/ksnapshot:4.3 kde-base/ksplash:4.3 kde-base/kstart:4.3 kde-base/kstartupconfig:4.3 kde-base/kstyles:4.3 kde-base/ksysguard:4.3 kde-base/ksystraycmd:4.3 kde-base/ktimezoned:4.3 kde-base/ktraderclient:4.3 kde-base/kuiserver:4.3 kde-base/kurifilter-plugins:4.3 kde-base/kwalletd:4.3 kde-base/kwin:4.3 kde-base/kwrite:4.3 kde-base/kwrited:4.3 kde-base/libkcddb:4.3 kde-base/libkdcraw:4.3 kde-base/libkexiv2:4.3 kde-base/libkipi:4.3 kde-base/libknotificationitem:4.3 kde-base/libkonq:4.3 kde-base/libksane:4.3 kde-base/libkworkspace:4.3 kde-base/libplasmaclock:4.3 kde-base/libtaskmanager:4.3 kde-base/nsplugins:4.3 kde-base/okular:4.3 kde-base/oxygen-icons:4.3 kde-base/phonon-kde:4.3 kde-base/plasma-apps:4.3 kde-base/plasma-runtime:4.3 kde-base/plasma-workspace:4.3 kde-base/powerdevil:4.3 kde-base/renamedlg-plugins:4.3 kde-base/solid:4.3 kde-base/solid-hardware:4.3 kde-base/solidautoeject:4.3 kde-base/soliduiserver:4.3 kde-base/svgpart:4.3 kde-base/systemsettings:4.3 kde-base/thumbnailers:4.3
Re: [gentoo-user] Re: Syntax for masking kde:4?
It could be manually downloaded from http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob_plain;f=Documentation/package.keywords/kde-4.3.keywords;hb=master Nikos Chantziaras wrote: From where? On 10/11/2009 10:58 PM, Chris Reffett wrote: Couldn't you just grab the kde 4.3 package.keyword list and append that to package.mask, since it uses the same slot format? Nikos Chantziaras wrote: On 10/11/2009 02:30 PM, Peter Humphrey wrote: Hello list, In the last few days some parts of KDE v4 seem to have been moved into the stable tree, but on some of my boxes I want to exclude kde:4 (but not qt:4). What is the syntax for a single entry in package.mask to exclude the whole of kde:4? I did start masking each package separately, but that's far too much work - I'd finish up with an entry for every kde package that has a version 4. Also, kde:4, which seems like the right thing to specify, is an invalid package atom according to eix. I can't see anything relevant in man pages or the gentoo kde configuration guide. Google hasn't helped me either. Portage unfortunately doesn't allow wildcards in the package name of atoms. But you can install KDE4 on one machine and then use: qlist -ISLC kde-base/*:4.3 to generate a list to put in package.mask in the machines you don't want KDE4. On my machine, the above command results in the following (it should at least cut down on the rest of the packages you need to mask): kde-base/ark:4.3 kde-base/dolphin:4.3 kde-base/drkonqi:4.3 kde-base/gwenview:4.3 kde-base/kamera:4.3 kde-base/kappfinder:4.3 kde-base/kapptemplate:4.3 kde-base/kate:4.3 kde-base/kcalc:4.3 kde-base/kcheckpass:4.3 kde-base/kcminit:4.3 kde-base/kcmshell:4.3 kde-base/kcolorchooser:4.3 kde-base/kcontrol:4.3 kde-base/kde-env:4.3 kde-base/kdeartwork-colorschemes:4.3 kde-base/kdeartwork-desktopthemes:4.3 kde-base/kdeartwork-emoticons:4.3 kde-base/kdeartwork-iconthemes:4.3 kde-base/kdeartwork-kscreensaver:4.3 kde-base/kdeartwork-meta:4.3 kde-base/kdeartwork-sounds:4.3 kde-base/kdeartwork-styles:4.3 kde-base/kdeartwork-wallpapers:4.3 kde-base/kdeartwork-weatherwallpapers:4.3 kde-base/kdebase-cursors:4.3 kde-base/kdebase-data:4.3 kde-base/kdebase-desktoptheme:4.3 kde-base/kdebase-kioslaves:4.3 kde-base/kdebase-menu:4.3 kde-base/kdebase-menu-icons:4.3 kde-base/kdebase-meta:4.3 kde-base/kdebase-startkde:4.3 kde-base/kdebase-wallpapers:4.3 kde-base/kdebugdialog:4.3 kde-base/kdegraphics-meta:4.3 kde-base/kdegraphics-strigi-analyzer:4.3 kde-base/kdelibs:4.3 kde-base/kdepasswd:4.3 kde-base/kdepimlibs:4.3 kde-base/kdeplasma-addons:4.3 kde-base/kdesu:4.3 kde-base/kdialog:4.3 kde-base/kdm:4.3 kde-base/kdnssd:4.3 kde-base/keditbookmarks:4.3 kde-base/keditfiletype:4.3 kde-base/kephal:4.3 kde-base/kfile:4.3 kde-base/kfind:4.3 kde-base/kfmclient:4.3 kde-base/kgamma:4.3 kde-base/kget:4.3 kde-base/kglobalaccel:4.3 kde-base/khelpcenter:4.3 kde-base/khotkeys:4.3 kde-base/kiconfinder:4.3 kde-base/kinfocenter:4.3 kde-base/kioclient:4.3 kde-base/klipper:4.3 kde-base/kmenuedit:4.3 kde-base/kmimetypefinder:4.3 kde-base/knetattach:4.3 kde-base/knewstuff:4.3 kde-base/knotify:4.3 kde-base/kolourpaint:4.3 kde-base/konqueror:4.3 kde-base/konsole:4.3 kde-base/kpasswdserver:4.3 kde-base/kquitapp:4.3 kde-base/krdc:4.3 kde-base/kreadconfig:4.3 kde-base/krosspython:4.3 kde-base/kruler:4.3 kde-base/krunner:4.3 kde-base/ksaneplugin:4.3 kde-base/kscreensaver:4.3 kde-base/ksmserver:4.3 kde-base/ksnapshot:4.3 kde-base/ksplash:4.3 kde-base/kstart:4.3 kde-base/kstartupconfig:4.3 kde-base/kstyles:4.3 kde-base/ksysguard:4.3 kde-base/ksystraycmd:4.3 kde-base/ktimezoned:4.3 kde-base/ktraderclient:4.3 kde-base/kuiserver:4.3 kde-base/kurifilter-plugins:4.3 kde-base/kwalletd:4.3 kde-base/kwin:4.3 kde-base/kwrite:4.3 kde-base/kwrited:4.3 kde-base/libkcddb:4.3 kde-base/libkdcraw:4.3 kde-base/libkexiv2:4.3 kde-base/libkipi:4.3 kde-base/libknotificationitem:4.3 kde-base/libkonq:4.3 kde-base/libksane:4.3 kde-base/libkworkspace:4.3 kde-base/libplasmaclock:4.3 kde-base/libtaskmanager:4.3 kde-base/nsplugins:4.3 kde-base/okular:4.3 kde-base/oxygen-icons:4.3 kde-base/phonon-kde:4.3 kde-base/plasma-apps:4.3 kde-base/plasma-runtime:4.3 kde-base/plasma-workspace:4.3 kde-base/powerdevil:4.3 kde-base/renamedlg-plugins:4.3 kde-base/solid:4.3 kde-base/solid-hardware:4.3 kde-base/solidautoeject:4.3 kde-base/soliduiserver:4.3 kde-base/svgpart:4.3 kde-base/systemsettings:4.3 kde-base/thumbnailers:4.3
Re: [gentoo-user] Re: Masked package needs itsself ?
meino.cra...@gmx.de wrote: Sorry, I'm not following what you're trying to say :P jpeg-7 is masked, Without it any update process stops with this failure. jpeg-7 needs itsself to update jpeg-7 (according the output I posted). If I install it, many packaged needs to rebuild, for which I have not the time. When I want to prevent that, I am urged to install another masked package. Why needs a non masked system a masked packed and build against it (incorporate its masked character) OR needs a compatibility package which also is masked to not to build (directly) against the other masked package? Or in more peotic words: To live on, take this poison. If you dont want to get poisoned take the other poison. Sorry, english is not my native code page... Actually, according to the output you posted, something depends on jpeg-7. The output you posted didn't actually indicate that jpeg-7 depends on itself. There should have been a list below that output of what actually does depend on =media-libs/jpeg-7, if that helps at all. Chris Reffett
