Hi, In #620322 it is proposed to ship libvncclient library in a separate binary package. In order to do this, the following steps have to be performed: * put libvncclient library into a new libvncclient0 binary package * libvncclient0 binary must break and replace older libvncserver0 binary packages * libvncserver0 binary should depend on the exact version of libvncclient0 binary at least until every rdep has been rebuilt with the new structure * rdeps have to be rebuilt to pick the new dependencies
As long as libvncserver0 depends on the new libvncclient0, this shouldn't be a problem, but I'd like to coordinate this transition with you to avoid problems. Which option would you like the most between the following? 1) leave libvncserver untouched until Wheezy is released 2) perform the switch, keep the libvncserver0 -> libvncclient0 dependency, remove it when every rdep is rebuilt to pick the new structure 3) perform the switch, schedule binNMUs immediately, and drop the libvncserver0 -> libvncclient0 dependency ASAP Cheers, Luca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org