Re: [Cooker] Dependancy LOOP: eel, libeel0 and nautilus-mozilla, nautilus
Arnd Bergmann <[EMAIL PROTECTED]> writes: > On Tue, 19 Jun 2001, R.I.P. Deaddog wrote: > >> On 19 Jun 2001, Warly wrote: >> >> > >> > libfoo0 must not require foo, or it is an error >> >> Currently libGConf1 requires GConf1 and it's intentional. >> > No, libGConf1 requires GConf, which is not nice but acceptable. > Any libfoo0 can require foo (libesound0 requires esound) or > even foo >= 1.2.3, but never foo0, foo=1.2.3 or foo=1.2.3-4mdk. > This problem currently exists in eel, fribidi, libtabe, kdelibs > (implicitly) and xmorph. yes (should remember to add it to the policy...) -- Warly
Re: [Cooker] Dependancy LOOP: eel, libeel0 and nautilus-mozilla,nautilus
On Tue, 19 Jun 2001, R.I.P. Deaddog wrote: > On 19 Jun 2001, Warly wrote: > > > > > libfoo0 must not require foo, or it is an error > > Currently libGConf1 requires GConf1 and it's intentional. > No, libGConf1 requires GConf, which is not nice but acceptable. Any libfoo0 can require foo (libesound0 requires esound) or even foo >= 1.2.3, but never foo0, foo=1.2.3 or foo=1.2.3-4mdk. This problem currently exists in eel, fribidi, libtabe, kdelibs (implicitly) and xmorph. Arnd <><
Re: [Cooker] Dependancy LOOP: eel, libeel0 and nautilus-mozilla,nautilus
On 19 Jun 2001, Warly wrote: > > In the old days, most of these packages only had a foo and a foo-devel > > package. Now there usually is foo, libfoo0 and libfoo0-devel with > > "foo requires libfoo0 = 1.2.3", "libfoo0-devel requires libfoo0 = 1.2.3" > > and possibly some "bar-2.3.4 requires libfoo0". When you get foo-2.0.0, > > you can install libfoo2 and upgrade foo and libfoo-devel without having > > to rebuild or even port bar. > > However, it can be assumed that foo-2.0.0 and foo-1.2.3 can not be installed > > at the same time, so if libfoo0 requires foo-1.2.3, you cannot have > > foo-2.0.0 and bar-2.3.4 at the same time, which is bad. > > libfoo0 must not require foo, or it is an error Currently libGConf1 requires GConf1 and it's intentional. Abel
Re: [Cooker] Dependancy LOOP: eel, libeel0 and nautilus-mozilla, nautilus
Arnd Bergmann <[EMAIL PROTECTED]> writes: > On Mon, 18 Jun 2001, Andrej Borsenkow wrote: > >> > >> > There are actually over 20 of these and most are probably hard to avoid >> > (see below). The cases with 'libfoo0-1.2.3 requires foo-1.2.3' are >> > however broken, imho. >> >> Why? It simply means that both versions must match. If this requirements is >> correct is another question; but there is nothing broken in dependency >> itself. >> > In the old days, most of these packages only had a foo and a foo-devel > package. Now there usually is foo, libfoo0 and libfoo0-devel with > "foo requires libfoo0 = 1.2.3", "libfoo0-devel requires libfoo0 = 1.2.3" > and possibly some "bar-2.3.4 requires libfoo0". When you get foo-2.0.0, > you can install libfoo2 and upgrade foo and libfoo-devel without having > to rebuild or even port bar. > However, it can be assumed that foo-2.0.0 and foo-1.2.3 can not be installed > at the same time, so if libfoo0 requires foo-1.2.3, you cannot have > foo-2.0.0 and bar-2.3.4 at the same time, which is bad. libfoo0 must not require foo, or it is an error > To put it more simply, if you cannot install A without B nor B without A > and they both come from the same source, they can just as well be in the > same RPM. > > Arnd <>< -- Warly
Re: [Cooker] Dependancy LOOP: eel, libeel0 and nautilus-mozilla,nautilus
Hy, I just wanted to add my two cents. On 18th Jun 2001 14:59:06 +0200 Arnd Bergmann collected these lines: > warning: LOOP: > warning: Aurora-Monitor-NewStyle-Categorizing-WsLib-8.2-7mdk PreReq: Aurora = >8.2-7mdk > warning: Aurora-8.2-7mdk Requires: Aurora-Monitor This makes sense actually, since it is possible to use different Aurora Monitor packages with Aurora. > warning: LOOP: > warning: bash-2.05-5mdk Requires: ld-linux.so.2 > warning: glibc-2.2.3-2mdk PreReq: /bin/sh Wouldn't it be better to create a real stand alone shell and make glibc depend on this? > warning: LOOP: > warning: libesound0-0.2.22-4mdk Requires: esound > warning: esound-0.2.22-4mdk Requires: libesd.so.0 This just doesn't make any sense. > warning: LOOP: > warning: chkconfig-1.2.22-1mdkRequires: msec >= 0.10 > warning: msec-0.15-16mdk Requires: chkconfig >= 0.9-6 chkconfig shouldn't depend on msec but use it if available. > warning: LOOP: > warning: mandrake_desk-8.0-12mdk Requires: libcapplet.so.0 > warning: control-center-1.4.0.1-2mdk Requires: mandrake_desk >= >7.2-8mdk same here. control-center shouldn't require mandrake_desk > warning: LOOP: > warning: e2fsprogs-1.20-1mdk Requires: libext2fs2 > warning: libext2fs2-1.20-1mdk Requires: e2fsprogs > warning: LOOP: > warning: libeel0-1.0-2mdk Requires: eel = 1.0 > warning: eel-1.0-2mdk Requires: libeel0 > warning: LOOP: > warning: libfribidi0-0.1.15-2mdk Requires: fribidi = 0.1.15 > warning: fribidi-0.1.15-2mdk Requires: libfribidi0 = 0.1.15 > warning: LOOP: > warning: libGConf1-1.0.1-3mdk Requires: GConf >= 1.0.1 > warning: GConf-1.0.1-3mdk PreReq: libGConf1 > warning: LOOP: > warning: libtabe-0.2.1-3mdk Requires: libtabe0 = 0.2.1-3mdk > warning: libtabe0-0.2.1-3mdk Requires: libtabe = 0.2.1 same as esound. Just unnecessary to splitt these packages. Alexander Werth
Re: [Cooker] Dependancy LOOP: eel, libeel0 and nautilus-mozilla, nautilus
I have to agree. While putting all of the reusable routines in a library is nice, it seems with a lot of packages that we're creating library packages for their own sake. This is making things almost as messy as Windows as far as figuring out what's missing and why something doesn't work. Just my $0.02 worth. V. Andrej Borsenkow wrote: > > > > > To put it more simply, if you cannot install A without B nor B without A > > and they both come from the same source, they can just as well be in the > > same RPM. > > > > Thinking ... umm ... you are right. Really :-) > > -andrej
RE: [Cooker] Dependancy LOOP: eel, libeel0 and nautilus-mozilla, nautilus
> > To put it more simply, if you cannot install A without B nor B without A > and they both come from the same source, they can just as well be in the > same RPM. > Thinking ... umm ... you are right. Really :-) -andrej
RE: [Cooker] Dependancy LOOP: eel, libeel0 and nautilus-mozilla,nautilus
On Mon, 18 Jun 2001, Andrej Borsenkow wrote: > > > > There are actually over 20 of these and most are probably hard to avoid > > (see below). The cases with 'libfoo0-1.2.3 requires foo-1.2.3' are > > however broken, imho. > > Why? It simply means that both versions must match. If this requirements is > correct is another question; but there is nothing broken in dependency > itself. > In the old days, most of these packages only had a foo and a foo-devel package. Now there usually is foo, libfoo0 and libfoo0-devel with "foo requires libfoo0 = 1.2.3", "libfoo0-devel requires libfoo0 = 1.2.3" and possibly some "bar-2.3.4 requires libfoo0". When you get foo-2.0.0, you can install libfoo2 and upgrade foo and libfoo-devel without having to rebuild or even port bar. However, it can be assumed that foo-2.0.0 and foo-1.2.3 can not be installed at the same time, so if libfoo0 requires foo-1.2.3, you cannot have foo-2.0.0 and bar-2.3.4 at the same time, which is bad. To put it more simply, if you cannot install A without B nor B without A and they both come from the same source, they can just as well be in the same RPM. Arnd <><
RE: [Cooker] Dependancy LOOP: eel, libeel0 and nautilus-mozilla, nautilus
> > There are actually over 20 of these and most are probably hard to avoid > (see below). The cases with 'libfoo0-1.2.3 requires foo-1.2.3' are > however broken, imho. Why? It simply means that both versions must match. If this requirements is correct is another question; but there is nothing broken in dependency itself. -andrej
Re: [Cooker] Dependancy LOOP: eel, libeel0 and nautilus-mozilla,nautilus
On Mon, 18 Jun 2001, Stefan van der Eijk wrote: > warning: LOOP: > warning: removing eel-1.0-2mdk "Requires: libeel0" from tsort relations. > warning: eel-1.0-2mdk Requires: libeel0 > warning: removing libeel0-1.0-2mdk "Requires: eel = 1.0" from tsort > relations. > warning: libeel0-1.0-2mdk Requires: eel = 1.0 > warning: LOOP: > warning: removing nautilus-mozilla-1.0.3-4mdk "Requires: nautilus = > 1.0.3" from tsort relations. > warning: nautilus-mozilla-1.0.3-4mdk Requires: nautilus > = 1.0.3warning: removing nautilus-1.0.3-4mdk "Requires: nautilus-mozilla > = 1.0.3-4mdk" from tsort relations. > warning: nautilus-1.0.3-4mdk Requires: There are actually over 20 of these and most are probably hard to avoid (see below). The cases with 'libfoo0-1.2.3 requires foo-1.2.3' are however broken, imho. Since you will not bee able to install foo-2.0.0 and libfoo0-1.2.3 at the same time, libfoo0 might just as well be inside the foo package or it has to be 'libfoo0-1.2.3 requires foo >= 1.2.3'. Arts still has to be fixed to not depend on kdelibs. Arnd <>< warning: LOOP: warning: bash-2.05-5mdk Requires: libhistory.so.4.2 warning: readline-4.2-2mdkRequires: ld-linux.so.2 warning: glibc-2.2.3-2mdk PreReq: /bin/sh warning: LOOP: warning: aspell-br-0.2.1-2mdk Requires: aspell warning: aspell-0.33.6-5mdk Requires: aspell-dictionary warning: LOOP: warning: Aurora-Monitor-NewStyle-Categorizing-WsLib-8.2-7mdk PreReq: Aurora = 8.2-7mdk warning: Aurora-8.2-7mdk Requires: Aurora-Monitor warning: LOOP: warning: bash-2.05-5mdk Requires: libtermcap.so.2 warning: libtermcap2-2.0.8-29mdk Requires: ld-linux.so.2 warning: glibc-2.2.3-2mdk PreReq: /bin/sh warning: LOOP: warning: bash-2.05-5mdk Requires: ld-linux.so.2 warning: glibc-2.2.3-2mdk PreReq: /bin/sh warning: LOOP: warning: libesound0-0.2.22-4mdk Requires: esound warning: esound-0.2.22-4mdk Requires: libesd.so.0 warning: LOOP: warning: chkconfig-1.2.22-1mdkRequires: msec >= 0.10 warning: msec-0.15-16mdk Requires: chkconfig >= 0.9-6 warning: LOOP: warning: XFree86-libs-4.1.0-4mdk Requires(auto): libGL.so.1 warning: Mesa-3.4.2-1mdk Requires: Mesa-common warning: Mesa-common-3.4.2-1mdk Requires: libICE.so.6 warning: LOOP: warning: libncurses5-5.2-12mdkRequires: ncurses warning: ncurses-5.2-12mdkRequires: libgpm.so.1 warning: libgpm1-1.19.3-8mdk Requires: libncurses.so.5 warning: LOOP: warning: libsasl7-1.5.24-4mdk Requires(auto): liblber.so.2 warning: libldap2-2.0.11-3mdk Requires: libsasl.so.7 warning: LOOP: warning: Bastille-Curses-module-1.2.0.rc3-0.1mdk Requires: Bastille warning: Bastille-1.2.0.rc3-0.1mdkRequires: Bastille-perl-UI-module warning: LOOP: warning: mandrake_desk-8.0-12mdk Requires: libcapplet.so.0 warning: control-center-1.4.0.1-2mdk Requires: mandrake_desk >= 7.2-8mdk warning: LOOP: warning: e2fsprogs-1.20-1mdk Requires: libext2fs2 warning: libext2fs2-1.20-1mdk Requires: e2fsprogs warning: LOOP: warning: libeel0-1.0-2mdk Requires: eel = 1.0 warning: eel-1.0-2mdk Requires: libeel0 warning: LOOP: warning: libfribidi0-0.1.15-2mdk Requires: fribidi = 0.1.15 warning: fribidi-0.1.15-2mdk Requires: libfribidi0 = 0.1.15 warning: LOOP: warning: libGConf1-1.0.1-3mdk Requires: GConf >= 1.0.1 warning: GConf-1.0.1-3mdk PreReq: libGConf1 warning: LOOP: warning: libtabe-0.2.1-3mdk Requires: libtabe0 = 0.2.1-3mdk warning: libtabe0-0.2.1-3mdk Requires: libtabe = 0.2.1 warning: LOOP: warning: XFree86-4.1.0-4mdk Requires: xinitrc >= 2.4.4-10mdk warning: xinitrc-2.4.4-45mdk Requires: XFree86 >= 3.3.5-12mdk warning: LOOP: warning: libarts2-2.2-0.alpha2.5mdk Requires: libDCOP.so.1 warning: kdelibs-2.2-0.alpha2.5mdkRequires: libartsflow.so.0 warning: LOOP: warning: xmorph-20010220-2mdk Requires: libmorph0 warning: libmorph0-20010220-2mdk Requires: xmorph = 20010220 warning: LOOP: warning: nautilus-mozilla-1.0.3-4mdk Re
[Cooker] Dependancy LOOP: eel, libeel0 and nautilus-mozilla, nautilus
[root@taz root]# urpmi gnome-core One of the following packages is needed: 1- nautilus-1.0.3-4mdk 2- mc-4.5.54-2mdk What is your choice? (1-2) 1 To satisfy dependencies, the following packages are going to be installed (28 MB): libmedusa0-0.5.1-1mdk nautilus-1.0.3-4mdk nautilus-mozilla-1.0.3-4mdk rep-gtk-0.15-2mdk fam-2.6.4-2mdk qiv-1.6-4mdk sawfish-0.38-3mdk libeel0-1.0-2mdk rep-gtk-gnome-0.15-2mdk eel-1.0-2mdk medusa-0.5.1-1mdk gnome-core-1.4.0.4-2mdk Is it ok? (Y/n) y installing /mirrors/i586/Mandrake/RPMS/libeel0-1.0-2mdk.i586.rpm /mirrors/i586/Mandrake/RPMS/eel-1.0-2mdk.i586.rpm /mirrors/i586/Mandrake/RPMS/libmedusa0-0.5.1-1mdk.i586.rpm /mirrors/i586/Mandrake/RPMS/rep-gtk-0.15-2mdk.i586.rpm /mirrors/i586/Mandrake/RPMS/fam-2.6.4-2mdk.i586.rpm /mirrors/i586/Mandrake/RPMS/medusa-0.5.1-1mdk.i586.rpm /mirrors/i586/Mandrake/RPMS/nautilus-1.0.3-4mdk.i586.rpm /mirrors/i586/Mandrake/RPMS/nautilus-mozilla-1.0.3-4mdk.i586.rpm /mirrors/i586/Mandrake/RPMS/qiv-1.6-4mdk.i586.rpm /mirrors/i586/Mandrake/RPMS/rep-gtk-gnome-0.15-2mdk.i586.rpm /mirrors/i586/Mandrake/RPMS/sawfish-0.38-3mdk.i586.rpm /mirrors/i586/Mandrake/RPMS/gnome-core-1.4.0.4-2mdk.i586.rpm warning: LOOP: warning: removing eel-1.0-2mdk "Requires: libeel0" from tsort relations. warning: eel-1.0-2mdk Requires: libeel0 warning: removing libeel0-1.0-2mdk "Requires: eel = 1.0" from tsort relations. warning: libeel0-1.0-2mdk Requires: eel = 1.0 warning: LOOP: warning: removing nautilus-mozilla-1.0.3-4mdk "Requires: nautilus = 1.0.3" from tsort relations. warning: nautilus-mozilla-1.0.3-4mdk Requires: nautilus = 1.0.3warning: removing nautilus-1.0.3-4mdk "Requires: nautilus-mozilla = 1.0.3-4mdk" from tsort relations. warning: nautilus-1.0.3-4mdk Requires: nautilus-mozilla = 1.0.3-4mdk Preparing... ### [100%] ### [ 8%] ### [ 16%] ### [ 25%] ### [ 33%] ### [ 41%] ### [ 50%] ### [ 58%] ### [ 66%] ### [ 75%] ### [ 83%] ### [ 91%] ### [100%] [root@taz root]#
