Bug#634015: Proposition to team-maintain m2crypto.
Dear all, after clearing out possible copyright issues in some files of the m2crypto source package, I am ready to upload an updated package. I would like to manage its sources in a VCS. I originally thought about the Debian Python Modules Team, but it only uses Subversion. Here are the three possibilities I see: - In python-modules, with Subversion, or - in collab-maint, with Git. Dima or anybody else interested in participating, please let me know your preferences. Otherwise I think I will go for collab-maint with Git. Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634015: Proposition to team-maintain m2crypto.
Package: python-m2crypto Severity: serious That may take a little more time, as I noted that demo/x509/proxylib.py is not free: # Matt Rodriguez, LBNL #Copyright (c) 2003, The Regents of the University of California, #through Lawrence Berkeley National Laboratory #(subject to receipt of any required approvals from the U.S. Dept. of Energy). #All rights reserved. Of course, this file is not used at build time and is not distributed in our binary packages, but if I understand well our procedures, I can not knowingly upload a package that contains this file. Hence the question to the other developers: is it necessary to correct m2crypto source package in Stable ? Not that I am interested to do it – you know my position on these files is that they should be documented but ignored otherwise (see http://lists.debian.org/20100124144741.gd13...@kunpuu.plessy.org ). So if the answer is yes, can somebody volunteer to do the work ? Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan It's certainly necessary for us to not distribute stuff which is not distributable. I'm therefore BCCing sub...@bugs.debian.org, as this should be a separate bug from the wishlist bug this is currently attached to. stew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634015: Proposition to team-maintain m2crypto.
Le Mon, Aug 08, 2011 at 11:37:22PM +0900, Charles Plessy a écrit : Le Sun, Aug 07, 2011 at 11:58:48PM +0100, Dima Barsky a écrit : Sorry for the delay, I was away for a while. I have to admit, I have not paid much attention to m2crypto lately, so if you or anybody else wants to pick it up I would not mind at all. If there are no volunteers I'll have a look at the bug reports and upload a new version in the next week or two. Hi Dima, thanks for the answer ! I will go ahead with the upload soon. That may take a little more time, as I noted that demo/x509/proxylib.py is not free: # Matt Rodriguez, LBNL #Copyright (c) 2003, The Regents of the University of California, #through Lawrence Berkeley National Laboratory #(subject to receipt of any required approvals from the U.S. Dept. of Energy). #All rights reserved. Of course, this file is not used at build time and is not distributed in our binary packages, but if I understand well our procedures, I can not knowingly upload a package that contains this file. Hence the question to the other developers: is it necessary to correct m2crypto source package in Stable ? Not that I am interested to do it – you know my position on these files is that they should be documented but ignored otherwise (see http://lists.debian.org/20100124144741.gd13...@kunpuu.plessy.org ). So if the answer is yes, can somebody volunteer to do the work ? Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634015: Proposition to team-maintain m2crypto.
Le Sun, Aug 07, 2011 at 11:58:48PM +0100, Dima Barsky a écrit : Sorry for the delay, I was away for a while. I have to admit, I have not paid much attention to m2crypto lately, so if you or anybody else wants to pick it up I would not mind at all. If there are no volunteers I'll have a look at the bug reports and upload a new version in the next week or two. Hi Dima, thanks for the answer ! I will go ahead with the upload soon. But do not hesitate to look at the bug reports, especially if you had contacts earlier with Upstream. Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634015: Proposition to team-maintain m2crypto.
Hi Charles, Sorry for the delay, I was away for a while. I have to admit, I have not paid much attention to m2crypto lately, so if you or anybody else wants to pick it up I would not mind at all. If there are no volunteers I'll have a look at the bug reports and upload a new version in the next week or two. Regards, Dima. On Sat, Aug 06, 2011 at 03:08:15PM +0900, Charles Plessy wrote: Dear Dima, and everybody, in order to update the package euca2ools, that is used to operate virtual machines on cloud systems such as the Amazon EC2, Eucalyptus, or OpenStack, I would need an update of the m2crypto package. Dima, I hope that everything is going well for you, as I have not had any answer from you for three weeks, and as the m2crypto package is not actively maintained (unanswered bug reports, unacknowledged NMU,…). I would like to ask you and the developer community about the possiblity to transfer m2crypto in a packaging team, such as the Debian Python Modules Team, where it would be easier to join forces to keep the package up to date. euca2ools frequently makes use of the latest functions of m2crypto, so it is not the first time that we need to wait for an update of m2crypto in Debian in order to move forward for euca2ools. I am currently using a locally updated m2crypto package, and could take the opportunity of an update to upload a package with an extended maintainer list. Would you agree, and would there be other developers interested in maintaining m2crypto ? Have a nice week-end, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634015: Proposition to team-maintain m2crypto.
Dear Dima, and everybody, in order to update the package euca2ools, that is used to operate virtual machines on cloud systems such as the Amazon EC2, Eucalyptus, or OpenStack, I would need an update of the m2crypto package. Dima, I hope that everything is going well for you, as I have not had any answer from you for three weeks, and as the m2crypto package is not actively maintained (unanswered bug reports, unacknowledged NMU,…). I would like to ask you and the developer community about the possiblity to transfer m2crypto in a packaging team, such as the Debian Python Modules Team, where it would be easier to join forces to keep the package up to date. euca2ools frequently makes use of the latest functions of m2crypto, so it is not the first time that we need to wait for an update of m2crypto in Debian in order to move forward for euca2ools. I am currently using a locally updated m2crypto package, and could take the opportunity of an update to upload a package with an extended maintainer list. Would you agree, and would there be other developers interested in maintaining m2crypto ? Have a nice week-end, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
