FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Development

 
 
LinkBack Thread Tools
 
Old 08-07-2011, 10:58 PM
Dima Barsky
 
Default 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-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110807225848.GA25719@ac93.org">http://lists.debian.org/20110807225848.GA25719@ac93.org
 
Old 08-08-2011, 02:37 PM
Charles Plessy
 
Default 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-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110808143722.GB21660@merveille.plessy.net">http://lists.debian.org/20110808143722.GB21660@merveille.plessy.net
 
Old 08-10-2011, 12:00 AM
Charles Plessy
 
Default 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.GD13468@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-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110810000031.GB8658@merveille.plessy.net">http://lists.debian.org/20110810000031.GB8658@merveille.plessy.net
 
Old 08-10-2011, 12:17 PM
Philipp Kern
 
Default Bug#634015: Proposition to team-maintain m2crypto.

On 2011-08-10, Charles Plessy <plessy@debian.org> wrote:
> ################################################## ##########################
> # 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.GD13468@kunpuu.plessy.org ). So
> if the answer is yes, can somebody volunteer to do the work ?

All I can say is "wtf". You knowingly accept that Debian distributes
undistributable files? It's not that it's a non-free license that still allows
distribution, it's "All Rights Reserved".

Kind regards
Philipp Kern


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: slrnj44tlv.7pm.trash@kelgar.0x539.de">http://lists.debian.org/slrnj44tlv.7pm.trash@kelgar.0x539.de
 
Old 08-10-2011, 12:41 PM
Mike O'Connor
 
Default 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.GD13468@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 submit@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-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87ei0tigm9.fsf@tang.vireo.org">http://lists.debian.org/87ei0tigm9.fsf@tang.vireo.org
 
Old 08-11-2011, 11:44 PM
Charles Plessy
 
Default Bug#634015: Proposition to team-maintain m2crypto.

Le Wed, Aug 10, 2011 at 12:17:04PM +0000, Philipp Kern a écrit :
> On 2011-08-10, Charles Plessy <plessy@debian.org> wrote:
> > ################################################## ##########################
> > # 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.GD13468@kunpuu.plessy.org ). So
> > if the answer is yes, can somebody volunteer to do the work ?
>
> All I can say is "wtf". You knowingly accept that Debian distributes
> undistributable files? It's not that it's a non-free license that still allows
> distribution, it's "All Rights Reserved".

In summary:

- Somebody, not me, accepted the m2crypto package with this file in our archive.

- I found this file and reported it. I admit I did not realise immediately
it was not redistributable at all.

- You said ‘wtf’.

- I contacted the file's author (whose new address was not easy to find), who
confirmed it is intended to be resistributed under the same terms as the whole
m2crypto package.

- Problem solved.

I appologise for ranting about non-free files with the wrong example. This was
inapproppriate, and I understand I lose credit for this. But I do not think that
saying ‘wtf’ contributed at all to solve the real problem.

Cheers,

--
Charles


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110811234424.GD25991@merveille.plessy.net">http://lists.debian.org/20110811234424.GD25991@merveille.plessy.net
 
Old 08-12-2011, 12:29 AM
Charles Plessy
 
Default 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-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110812002914.GA26537@merveille.plessy.net">http://lists.debian.org/20110812002914.GA26537@merveille.plessy.net
 

Thread Tools




All times are GMT. The time now is 06:14 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org