Re: elinks rc bug

2005-05-23 Thread Andrew Donnellan
It is a *serious policy violation*. I've been talking with the ftpparse lists and it turns out that there is a replacement in the program ftpcopy (search google). I haven't verified it though. Here's my analysis of the problems: * Commercial use requires contacting author (no specific DFSG violatio

Re: elinks rc bug

2005-05-21 Thread Frank Lichtenheld
On Sun, May 22, 2005 at 09:23:11AM +1000, Andrew Donnellan wrote: > The latest sarge elinks still has the code Which is exactly what I have said... > On 5/21/05, Frank Lichtenheld <[EMAIL PROTECTED]> wrote: > > Shouldn't this have been fixed by 0.10.4-1? This would leave the issue > > open for s

Re: elinks rc bug

2005-05-21 Thread Andrew Donnellan
The latest sarge elinks still has the code Andrew On 5/21/05, Frank Lichtenheld <[EMAIL PROTECTED]> wrote: > On Sat, May 21, 2005 at 06:13:01PM +1000, Andrew Donnellan wrote: > > I have just submitted a serious bug against the elinks package. > > (310035) It is to do with the fact that there is n

Re: elinks rc bug

2005-05-21 Thread Frank Lichtenheld
On Sat, May 21, 2005 at 06:13:01PM +1000, Andrew Donnellan wrote: > I have just submitted a serious bug against the elinks package. > (310035) It is to do with the fact that there is nonfree code in it, > the same code that was in prozilla. I'd like to know if any of the > release team can send DJ

elinks rc bug

2005-05-21 Thread Andrew Donnellan
I have just submitted a serious bug against the elinks package. (310035) It is to do with the fact that there is nonfree code in it, the same code that was in prozilla. I'd like to know if any of the release team can send DJ Bernstein (the code's author; author of qmail) an official Debian team res