severity 28 important
severity 443918 important
merge 28 443918
thanks
Here's a snippet from IRC that carrying an explanation from GNOME Team.
Though still present, the problem is already solved by binNMUs, so lower
the severity.
manphiz any one had a look at #28? It seems libwnck1 is not in sid
anymore, so it wouldn't be a problem.
manphiz and the problem is already taken care of by binNMUs
lool manphiz: The actual problem is that you can't install libwnck1
with libwnck$next if the dependencies on libwnck-commno are too strict
in both packages
Np237 we could relax those dependencies, after all these are only
translations
lool manphiz: The dependencies have been relaxed somewhat, but still
do not permit mixing libwnck from an older GNOME with the new one
lool manphiz: Basically the same thing happened to libvte
manphiz lool, I see. but maybe they are meant not to be installable at
the same time?
lool manphiz: There were other alternatives which were heavier in
terms of maintenance, so the conclusion of the discusions I started on
debian-gtk-gnome@ were to unversion the dependency between libvte$n and
-common
lool manphiz: the spirit of the Debian Policy is to permit shared libs
to be parallel installable
lool Even if libwnckn and n+1 have no direct file conflict, they
conflict de facto
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
