Poldek robi BUM
Przy install -F * powitał mnie taki kwiatek: kdelibs-devel-3.5.5-4.x86_64 zaznaczył kdelibs-libs-3.5.5-4.x86_64 (wł. kdelibs-libs 9:3.5.5-2) Something wrong, something not quite right. Assertion 'pkg_is_marked(ictx-ts-pms, pkg) == 0' failed, mark.c:101 Please report this bug to [EMAIL PROTECTED]. Przerwane Całość loga załączniku. [EMAIL PROTECTED] ~]$ rpm -qa | grep poldek poldek-0.20.1-0.20060823.21.6.x86_64 poldek-libs-0.20.1-0.20060823.21.6.x86_64 Zdrawiam [EMAIL PROTECTED] Installing set #32 Przetwarzanie zale¿no¶ci... kdelibs-3.5.5-2.x86_64 zostanie zast±piony przez kdelibs-3.5.5-4.x86_64 kdelibs-devel-3.5.5-2.x86_64 zostanie zast±piony przez kdelibs-devel-3.5.5-4.x86_64 kdelibs-devel-3.5.5-4.x86_64 zaznaczy³ xorg-lib-libICE-devel-1.0.3-1.x86_64 (w³. libtool(/usr/lib64/libICE.la)) xorg-lib-libICE-devel-1.0.2-1.x86_64 zostanie zast±piony przez xorg-lib-libICE-devel-1.0.3-1.x86_64 xorg-lib-libICE-devel-1.0.3-1.x86_64 zaznaczy³ xorg-lib-libICE-1.0.3-1.x86_64 (w³. xorg-lib-libICE = 1.0.3-1) xorg-lib-libICE-1.0.2-1.x86_64 zostanie zast±piony przez xorg-lib-libICE-1.0.3-1.x86_64 xorg-lib-libICE-1.0.2-3.athlon zostanie zast±piony przez xorg-lib-libICE-1.0.3-1.x86_64 b³±d: libICE.so.6 jest wymagany przez wine-0.9.16-1.athlon b³±d: libICE.so.6 jest wymagany przez wine-dll-d3d-0.9.16-1.athlon b³±d: libICE.so.6 jest wymagany przez wine-dll-gl-0.9.16-1.athlon b³±d: libICE.so.6 jest wymagany przez opera-9.02-2.athlon kdelibs-devel-3.5.5-4.x86_64 zaznaczy³ xorg-lib-libSM-devel-1.0.2-4.x86_64 (w³. libtool(/usr/lib64/libSM.la)) xorg-lib-libSM-devel-1.0.2-1.x86_64 zostanie zast±piony przez xorg-lib-libSM-devel-1.0.2-4.x86_64 xorg-lib-libSM-devel-1.0.2-4.x86_64 zaznaczy³ xorg-lib-libSM-1.0.2-4.x86_64 (w³. xorg-lib-libSM = 1.0.2-4) xorg-lib-libSM-1.0.2-1.x86_64 zostanie zast±piony przez xorg-lib-libSM-1.0.2-4.x86_64 xorg-lib-libSM-1.0.2-3.athlon zostanie zast±piony przez xorg-lib-libSM-1.0.2-4.x86_64 b³±d: xorg-lib-libSM-1.0.2-3.athlon (w³. libSM.so.6) jest wymagany przez opera-9.02-2.athlon b³±d: xorg-lib-libSM-1.0.2-3.athlon (w³. libSM.so.6) jest wymagany przez wine-0.9.16-1.athlon b³±d: xorg-lib-libSM-1.0.2-3.athlon (w³. libSM.so.6) jest wymagany przez wine-dll-d3d-0.9.16-1.athlon b³±d: xorg-lib-libSM-1.0.2-3.athlon (w³. libSM.so.6) jest wymagany przez wine-dll-gl-0.9.16-1.athlon kdelibs-devel-3.5.5-4.x86_64 zaznaczy³ xorg-lib-libX11-devel-1.1.1-1.x86_64 (w³. libtool(/usr/lib64/libX11.la)) xorg-lib-libX11-devel-1.0.99.1-1.x86_64 zostanie zast±piony przez xorg-lib-libX11-devel-1.1.1-1.x86_64 xorg-lib-libX11-devel-1.1.1-1.x86_64 zaznaczy³ xorg-lib-libXau-devel-1.0.3-1.x86_64 (w³. libtool(/usr/lib64/libXau.la)) xorg-lib-libXau-devel-1.0.2-1.x86_64 zostanie zast±piony przez xorg-lib-libXau-devel-1.0.3-1.x86_64 xorg-lib-libXau-devel-1.0.3-1.x86_64 zaznaczy³ xorg-lib-libXau-1.0.3-1.x86_64 (w³. xorg-lib-libXau = 1.0.3-1) xorg-lib-libXau-1.0.2-1.x86_64 zostanie zast±piony przez xorg-lib-libXau-1.0.3-1.x86_64 xorg-lib-libXau-1.0.2-3.athlon zostanie zast±piony przez xorg-lib-libXau-1.0.3-1.x86_64 xorg-lib-libX11-devel-1.1.1-1.x86_64 zaznaczy³ xorg-lib-libXdmcp-devel-1.0.2-4.x86_64 (w³. libtool(/usr/lib64/libXdmcp.la)) xorg-lib-libXdmcp-devel-1.0.2-1.x86_64 zostanie zast±piony przez xorg-lib-libXdmcp-devel-1.0.2-4.x86_64 xorg-lib-libXdmcp-devel-1.0.2-4.x86_64 zaznaczy³ xorg-lib-libXdmcp-1.0.2-4.x86_64 (w³. xorg-lib-libXdmcp = 1.0.2-4) xorg-lib-libXdmcp-1.0.2-1.x86_64 zostanie zast±piony przez xorg-lib-libXdmcp-1.0.2-4.x86_64 xorg-lib-libXdmcp-1.0.2-3.athlon zostanie zast±piony przez xorg-lib-libXdmcp-1.0.2-4.x86_64 xorg-lib-libX11-devel-1.1.1-1.x86_64 zaznaczy³ libxcb-devel-1.0-4.x86_64 (w³. libtool(/usr/lib64/libxcb-xlib.la)) libxcb-devel-1.0-4.x86_64 zaznaczy³ libpthread-stubs-0.1-1.x86_64 (w³. libpthread-stubs) libxcb-devel-1.0-4.x86_64 zaznaczy³ libxcb-1.0-4.x86_64 (w³. libxcb = 1.0-4) xorg-lib-libX11-devel-1.1.1-1.x86_64 zaznaczy³ xorg-lib-libX11-1.1.1-1.x86_64 (w³. xorg-lib-libX11 = 1.1.1-1) xorg-lib-libX11-1.0.99.1-1.x86_64 zostanie zast±piony przez xorg-lib-libX11-1.1.1-1.x86_64 xorg-lib-libX11-1.0.99.2-3.athlon zostanie zast±piony przez xorg-lib-libX11-1.1.1-1.x86_64 b³±d: xorg-lib-libX11-1.0.99.2-3.athlon (w³. libX11.so.6) jest wymagany przez opera-9.02-2.athlon b³±d: xorg-lib-libX11-1.0.99.2-3.athlon (w³. libX11.so.6) jest wymagany przez wine-0.9.16-1.athlon b³±d: xorg-lib-libX11-1.0.99.2-3.athlon (w³. libX11.so.6) jest wymagany przez wine-dll-d3d-0.9.16-1.athlon b³±d: xorg-lib-libX11-1.0.99.2-3.athlon (w³. libX11.so.6) jest wymagany przez wine-dll-gl-0.9.16-1.athlon zach³anna aktualizacja Mesa-libGL-6.5-1.20060911.1.athlon do 6.5.2-2 (niespe³nione libX11.so.6) b³±d: Mesa-libGL-6.5.2-2.x86_64: equal version installed, give up b³±d: libX11.so.6 jest wymagany przez Mesa-libGL-6.5-1.20060911.1.athlon kdelibs-devel-3.5.5-4.x86_64 zaznaczy³ xorg-lib-libXcursor-devel-1.1.8-3.x86_64 (w³. libtool(/usr/lib64/libXcursor.la))
Re: Poldek robi BUM
Dnia 02-01-2007, wto o godzinie 10:21 +0100, Cezary Krzyzanowski napisał(a): Przy install -F * powitał mnie taki kwiatek: Ekhmsorry - Evo gave me en before pl and I didn't see that. Nevertheless the problem stays. [EMAIL PROTECTED] ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
gcc-java vs java-sun-tools
There is a problem with gcc-java vs java-sun-tools. These packages are conflicting on each other but tons of java specs require one or another. This means that manual uninstalling/installing on builders is required. I guess that the only one conflicting file is /usr/bin/jar - I'm thinking about adding gcc-java-tools package with jar binary only but... it seems that such subpackage was already there and was removed: Revision 1.298 2005/05/11 21:20:15 pluto - gcc-java-tools mreged into gcc-java. this package isn't common for every java implementation now. The other solution would be putting Obsoletes without Conflicts in each package so there would be no problems on builders (installation deps based would work) ... Any ideas how other distros deal with this problem? -- Arkadiusz MiśkiewiczPLD/Linux Team arekm / maven.plhttp://ftp.pld-linux.org/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: gcc-java vs java-sun-tools
On Tuesday 02 January 2007 17:39, Szymon Siwek wrote: On Tue, Jan 02, 2007 at 03:49:43PM +0100, Arkadiusz Miskiewicz wrote: There is a problem with gcc-java vs java-sun-tools. These packages are conflicting on each other but tons of java specs require one or another. This means that manual uninstalling/installing on builders is required. /usr/bin/jar is symlink to jar-binary. The problem is that fresh rpm detects conflict about symlinks. Problem? It looks like a ,,fix''. The other solution would be putting Obsoletes without Conflicts in each package so there would be no problems on builders (installation deps based would work) ... It would be evil gentoo has script as javac, javadoc etc that runs proper binaries depending on user setting or global settings. -- Arkadiusz MiśkiewiczPLD/Linux Team arekm / maven.plhttp://ftp.pld-linux.org/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: gcc-java vs java-sun-tools
On Tuesday 02 January 2007 15:49, Arkadiusz Miskiewicz wrote: There is a problem with gcc-java vs java-sun-tools. there was a thread about it on devel-pl: http://lists.pld-linux.org/mailman/pipermail/pld-devel-pl/2006-July/135330.html ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
