On April 14, 2004 07:31 am, Örn Hansen wrote:
onsdag 14 april 2004 04:23 skrev Sergei Klink:
No offense, but this is quite a non-informative example, if example at all... As far as I can tell, that's your inappropriate config, not apt's fault, and you're apparently trying to install something like glibc :)
Sorry, the offending package was:
z600cups
Which is created for RedHat and depends on cups >= 1:1.1.15 but I have 1.1.19 installed. YaST figures this out easily, but apt doesn't ...
I'm not even sure whether this is the way YaST should behave. I'm not very familiar with packaging, but just ignoring epoch numbers does not sound like a good thing. I suspect that this is the wanted behavior of apt(it compares 0:1.1.19 and 1:1.1.15, and obviously chooses the higher epoch number as higher version). If you'd be really wishing to use apt, pinning is IMHO the best workaround here(check your mail archives for the links, please ;-), but this is the sign that you're probably using packages that you shouldn't be ;) Out of curiosity, did the drivers work?.. So I'm pretty sure this doesn't qualify as an example.
Another problem with apt, is the new x86_64 library packages. It complained about a few of the libraries not being there, when they were and YaST had no problem with those dependancies.
Example? Sounds like you're saying that the apt repository doesn't contain all the packages you need, at most(though I haven't yet seen any missing libraries in x86_64 that some packages would be dependent upon). It seems to me almost every(if not all) package included with SuSE is available in some repository on gwdg.de, if there's something missing, and a dependency still points to it, it's a bug you should probably report, but it has nothing to do with apt(or YaST) (remember also that there could be two libraries of the same name, still seen as different provides) Btw, just FYI, the installation will also "break" if you have unsigned packages... P.S. To put this all together, if you have to go to /var/cache/apt/archives to run rpm -Uvh *.rpm manually, and it works, then really, apt has pretty much done its job already :) After downloading/checking signatures(which is where it often stops due to the lack of such with the default config), the only thing left for apt to do is to pass the packages to rpm to install...