Ben Hines wrote:
[]
> Martin you posted this a month ago (below). :) The fix (supposedly?) is 
> to update "gnome-vfs-ssl" first. or, "gnome-vfs" if you have that one.
> 
> "fink update gnome-vfs-ssl"

Yes, but after Sarah's reply to that, I had to write (and this worked)

> I see. Seems to be one of those situations where fink needs 
> some help for being able to update. The next thing to try would 
> be to remove the old gnome-vfs manually first:
> 
>  sudo dpkg --remove --force-depends gnome-vfs
> 
> Then fink update gnome-vfs.

The problem is that gnome-vfs[-ssl]-1.0.5 depends on gnome-vfs-shlibs 
which depends on gnome-mime-data. So any fink update will first try to 
install gnome-mime-data. But gnome-mime-data conflicts with the 
pre-1.0.5 version of gnome-vfs that is installed. So there is really no 
way out of this situation without using force.

In the case of control-center, there was the possibility to put a 
BuildDepends on gnome-vfs-dev (>= 1.0.5-5) instead of the Conflicts 
line. Here for gnome-mime-data this would lead to a circular dependency 
and probably to the dreaded "node already exists" error.

> This really should be fixed in the package if possible. Or we need to 
> fix fink to update packages in the correct order somehow.

There have been other situations like this (gnuplot/aquaterm comes to 
mind, some kdebindings thing recently, an earlier tetex-texmf update and 
some others I remember vaguely) where dpkg --remove --force-depends (or 
else uninstalling half of the fink distribution) was the only way out.

I don't know how to handle these situations gracefully. It seems that 
apt-get is better in some of these cases, because it looks at the whole 
picture first and then decides what to do. Fink is a little too eager to 
install dependencies immediately without considering the consequences. 
Ideally, there should be a way to say: Install this dependency later, 
after the update, something like Depends-but-does-not-BuildDepend :-)

Otherwise, the gnome packages would have to be modified, but I have no 
idea how important the dependency of gnome-vfs-shlibs on gnome-mime-data 
is or what it would take to avoid the conflict of gnome-mime-data with 
the older gnome-vfs.

> Will this problem affect *everyone* when this stuff is moved to stable 
> and with the next bindist?

It seems so. Although with the bindist I am not sure. Apt-get might do 
the right thing, but I don't know about dselect's intelligence.

-- 
Martin






-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to