Re: Bug#689230: virtuoso 7.1 to Debian proper [Was: Bug#689230: new version is needed!]
Hi all! Just a little nudge here again! Ubuntu 16.04 (which is a Long Term Support release) has a Debian Import Freeze on the February 18th, and for Virtuoso 7.2 to make it in, it should have an update in Debian well before that. I'm neither an Ubuntu or Virtuoso user, but I think it is important for both that it goes in there. :-) Cheers, Kjetil
Re: Bug#689230: virtuoso 7.1 to Debian proper [Was: Bug#689230: new version is needed!]
On Tuesday 03 February 2015 17:22:11 Tim Haynes wrote: [snip] It seems this would be a fortuitous moment to ask: if I'm wanted to be regarded as the VOS maintainer in Debian, how do I go about officially signing on? First you need to wait until us the current maintainers orphan the package. That will happen as soon as KDE doesn't needs virtuoso anymore. Then you need to adopt the package, do whatever you need to get it ready for the archive and find a sponsor [0] to upload it. Take a look at [1] for more info on this last part of the process. [0] https://wiki.debian.org/Glossary#sponsor [1] http://mentors.debian.net/ -- May the source be with you. Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Re: Bug#689230: virtuoso 7.1 to Debian proper [Was: Bug#689230: new version is needed!]
On Friday 13 June 2014 09:37:48 Yaroslav Halchenko wrote: Hi Tim, We are looking to get virtuoso updated in Debian. I was referred to http://wiki.lod2.eu/display/LOD2DOC/Installation+of+a+local+LOD2+stack as an alternative source and I see that you have done some work to update package (from Ubuntu) for the 7.1 release. Since you had some experience with it, would you be interested to jump on board with maintaining virtuoso in Debian? (there is seems to be some work still needed to finalize the package you have created so it could be accepted to stock Debian) Remember that if you introduce a new version it doesn't has to create problem in the current one. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Re: Bug#689230: virtuoso 7.1 to Debian proper [Was: Bug#689230: new version is needed!]
On Mon, 16 Jun 2014, Lisandro Damián Nicanor Pérez Meyer wrote: Hi Tim, We are looking to get virtuoso updated in Debian. I was referred to http://wiki.lod2.eu/display/LOD2DOC/Installation+of+a+local+LOD2+stack as an alternative source and I see that you have done some work to update package (from Ubuntu) for the 7.1 release. Since you had some experience with it, would you be interested to jump on board with maintaining virtuoso in Debian? (there is seems to be some work still needed to finalize the package you have created so it could be accepted to stock Debian) Remember that if you introduce a new version it doesn't has to create problem in the current one. 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? -- 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/20140616155139.ga19...@onerussian.com
Re: Bug#689230: virtuoso 7.1 to Debian proper [Was: Bug#689230: new version is needed!]
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
