Hi Reinhard,
X2go formerly used binary packages of names nxcomp, nxcompshad and
nxcompext. These are now called libxcomp3, libxcompshad3, libxcompext3.
I have added conflicts stanzas to the new packages, but on install
they do not enforce the uninstallation of the nxcomp* binary packages.
What is needed to force uninstallation of the old nx packages formerly
shipped with X2go?
Thanks for any input, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Thu, Jul 14, 2011 at 14:41:48 (CEST), Mike Gabriel wrote:
Hi Reinhard,
X2go formerly used binary packages of names nxcomp, nxcompshad and nxcompext. These are now called libxcomp3, libxcompshad3, libxcompext3.
Yes, this is in accordance to the library packaging guidelines: http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html
I have added conflicts stanzas to the new packages, but on install they do not enforce the uninstallation of the nxcomp* binary packages. What is needed to force uninstallation of the old nx packages formerly shipped with X2go?
See debian policy section 7.6: http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
-- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4
-
Mike Gabriel -
Reinhard Tartler