On Mon, 16 Jun 2014, Lisandro Damián Nicanor Pérez Meyer wrote: > > do you see obvious warning points to keep in mind? there seems to be > > not that many dependents on virtuoso's components, or am I > > misunderstanding?
> I don't remember virtuoso's internals, but for example the binaries can not > have the same name. "upgrade" would consist of upgrading all those binaries (bin/*) as well to the most recent version. Thus they would be coming from 8.1, we would need to assure that any dependent package is compatible to the "new binaries". Do you see any dependent packages present in Debian which require those binaries and would not be compatible somehow with 8.1? meanwhile imho we should proceed with preparing updated package, and then, whenever ready, check all the dependent projects to assure a smooth transition. > That being said, remember that I'm still writing as particular and not team- > wide, so maybe you still don't have the permission from the maintainers to do > so. That is why we are following up on the existing issue (#689230) which maintainers (I hope) monitor. Meanwhile I will BCC (to avoid future duplication of emails) the Debian Krap team (and other uploaders) explicitly to possibly bring their direct attention/feedback. -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140616162024.gg19...@onerussian.com