[Since] Gnumed [client generally] is to be installed in a TESTING
machine via apt-get, what you CAN do is put all the dependencies of
GNUmed in the Preferences with a pin number [greater than] stable:
Exactly like you did with the gnumed-client package
Explanation: get gnumed-client debs from testing
Package: gnumed-client
Pin: release a=testing
Pin-Priority: 601
Explanation: get gnumed dependencies from testing
Package: gnumed-common
Pin: release a=testing
Pin-Priority: 601
Explanation: [also needs python-support] debs from testing
Package: python-support
Pin: release a=testing
Pin-Priority: 601
AND ETC ...
Rogerio
apt-get update
When I try to apt-get install gnumed-client I get
The following packages have unmet dependencies:
gnumed-client: Depends: python-support (>= 0.90.0) but 0.8.4 is to
be installed
Depends: gnumed-common (= 0.4.5-1) but 0.3.10-1 is
to be installed
E: Broken packages
Similarly (for GUI users) the GNOME Update Manager panel advises
that my Debian virtual system is up to date except that it displays
gnumed-common in a grayed-out (non-selectable) manner listing
From version 0.3.10-1 to 0.4.5-1
My /etc/apt/preferences is as follows and sources.list is below that.
Does a putative cause exist for the breakage or ought I regard it
something that "just happens" on user machines?
Do I need to
apt-get install gnumed-client -o DPkg::options::="--force-
overwrite"
or
apt-get install gnumed-common -o DPkg::options::="--force-
overwrite"
================================
Explanation: apt preference will not accept release name
lenny is release 5.x and was stable at January 2009
Package: *
Pin: release v=5.*
Pin-Priority: 501
Explanation: make testing available, but at a lower priority
Package: *
Pin: release a=testing
Pin-Priority: 200
Explanation: make unstable available, but at an even lower priority
Package: *
Pin: release a=unstable
Pin-Priority: 100
Explanation: make experimental available, at the lowest priority
Package: *
Pin: release a=experimental
Pin-Priority: 50
Explanation: get gnumed-client debs from testing
Package: gnumed-client
Pin: release a=testing
Pin-Priority: 601
===============================
debian:/etc/apt# cat sources.list
#
# deb cdrom:[Debian GNU/Linux 5.0.0 _Lenny_ - Official i386 NETINST
Binary-1 20090214-16:03]/ lenny main
#deb cdrom:[Debian GNU/Linux 5.0.0 _Lenny_ - Official i386 NETINST
Binary-1 20090214-16:03]/ lenny main
deb http://ftp3.nrc.ca/debian/ lenny main
deb-src http://ftp3.nrc.ca/debian/ lenny main
deb http://security.debian.org/ lenny/updates main
deb-src http://security.debian.org/ lenny/updates main
deb http://volatile.debian.org/debian-volatile lenny/volatile main
deb-src http://volatile.debian.org/debian-volatile lenny/volatile main
deb http://ftp.de.debian.org/debian experimental main
deb http://ftp.de.debian.org/debian testing main
deb http://ftp.de.debian.org/debian unstable main
Explanation: gnumed-common must usually be sourced like the client
Package: gnumed-common
Pin: release a=testing
Pin-Priority: 601
Explanation: gnumed-doc must usually be sourced like the client
Package: gnumed-doc
Pin: release a=testing
Pin-Priority: 601
_______________________________________________
Gnumed-devel mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/gnumed-devel