Re: Policy on Binary Firmware Fetching in Main (e.g. foo2zjs)

2007-11-16 Thread Tristan Seligmann
* Michael Gilbert [EMAIL PROTECTED] [2007-11-14 23:54:08 -0500]: you missed my email with the logical proof that there is a dependency: does getweb function correctly if the external files are unable to be downloaded? if the answer is no, then the script must be considered to depend on

Re: Policy on Binary Firmware Fetching in Main (e.g. foo2zjs)

2007-11-15 Thread John Halton
On 15/11/2007, Michael Gilbert [EMAIL PROTECTED] wrote: i don't see a difference. if any part of the package requires access to non-free data to function correctly, then the entire package should be considered to depend on non-free. this is different from the compiz situation where the

Re: Policy on Binary Firmware Fetching in Main (e.g. foo2zjs)

2007-11-15 Thread Frank Küster
Michael Gilbert michael.s.gilbert at gmail.com writes: Stephen Gran wrote: That being said, packages that exist solely to download external non-free content have traditionally been considered contrib material. If this is just a helper script that nothing else in the package uses, it

Re: Policy on Binary Firmware Fetching in Main (e.g. foo2zjs)

2007-11-14 Thread Michael Gilbert
To use a rough analogy, compiz doesn't work on certain graphics cards unless one uses the proprietary driver for that card, but that doesn't in itself make compiz non-free. right, but this situation is different. so lets assume that foo2zjs is analogous to compiz and the printer firmware is

Re: Policy on Binary Firmware Fetching in Main (e.g. foo2zjs)

2007-11-14 Thread Michael Gilbert
Stephen Gran wrote: does getweb function correctly if the external files are unable to be downloaded? That's not a very useful question - does a web browser function 'correctly' when it gets a 404? It depends entirely on what you mean by correctly, and that starts to feel like there's no

Re: Policy on Binary Firmware Fetching in Main (e.g. foo2zjs)

2007-11-14 Thread Michael Gilbert
You are missing the point: some printers may or may not work, but the program itself still has the same capabilities and is not influenced by what getweb does. that's why it is ok for most of the program to be in main. its just getweb that depends on non-free data. No, it does not. you

Re: Re: Policy on Binary Firmware Fetching in Main (e.g. foo2zjs)

2007-11-13 Thread Stephen Gran
This one time, at band camp, Michael Gilbert said: and since getweb depends on non-free software and is a part of the package, foo2zjs as a whole is considered to depend on non-free software. No. getweb *downloads* and copies some non-free software, it does not depend on it. does getweb

Re: Policy on Binary Firmware Fetching in Main (e.g. foo2zjs)

2007-11-13 Thread Marco d'Itri
[EMAIL PROTECTED] wrote: You are missing the point: some printers may or may not work, but the program itself still has the same capabilities and is not influenced by what getweb does. that's why it is ok for most of the program to be in main. its just getweb that depends on non-free data.

Re: Policy on Binary Firmware Fetching in Main (e.g. foo2zjs)

2007-11-12 Thread Marco d'Itri
[EMAIL PROTECTED] wrote: No, it's a very different case since here we have a large free self-contained free software program which works without any non-free dependencies, whose package also contains an additional little script which downloads and copies to an external device some file.

Re: Re: Policy on Binary Firmware Fetching in Main (e.g. foo2zjs)

2007-11-12 Thread John Halton
On Mon, Nov 12, 2007 at 08:20:53PM -0500, Michael Gilbert wrote: does getweb function correctly if the external files are unable to be downloaded? if the answer is no, then the script must be considered to depend on those files. and since those external files contain non-free data, then the

Re: Policy on Binary Firmware Fetching in Main (e.g. foo2zjs)

2007-11-11 Thread Marco d'Itri
[EMAIL PROTECTED] wrote: Paragraph 2.2.2 probably resolves any ambiguity here: No, it's about a different situation. Examples of packages which would be included in contrib are [...] free packages which require contrib, non-free packages or *packages which are not in our archive at all* for

Re: Bug#449497: Policy on Binary Firmware Fetching in Main (e.g. foo2zjs)

2007-11-11 Thread Marco d'Itri
On Nov 10, Michael Gilbert [EMAIL PROTECTED] wrote: the maintainer does not believe this to be an issue [1] because the firmware fetching stuff is a small part of the total package. i The maintainer is correct. suggested that he could split out the firmware fetching stuff into a contrib

Re: Policy on Binary Firmware Fetching in Main (e.g. foo2zjs)

2007-11-11 Thread Michael Gilbert
Marco d'Itri wrote: No, it's a very different case since here we have a large free self-contained free software program which works without any non-free dependencies, whose package also contains an additional little script which downloads and copies to an external device some file. There is

Re: Policy on Binary Firmware Fetching in Main (e.g. foo2zjs)

2007-11-11 Thread Michael Gilbert
i received the following message from the upstream author of foo2zjs. it is his belief that much of the package should be non-free. see below. Rick Richardson wrote: It is not the firmware only. It is also ICC/ICM Color Correction files. And PATENTS. Patents by IBM and ATT in the USA and

Re: Policy on Binary Firmware Fetching in Main (e.g. foo2zjs)

2007-11-10 Thread John Halton
On Sat, Nov 10, 2007 at 12:32:08AM -0500, Michael Gilbert wrote: the first is that packages in main should not have any dependencies on non-free software. however, debian policy is not entirely clear on the issue. section 2.2.1 says ... the packages in main must not require a package outside

Policy on Binary Firmware Fetching in Main (e.g. foo2zjs)

2007-11-09 Thread Michael Gilbert
i recently submitted a serious bug against foo2zjs because the package provides a non-free firmware fetching script (called getweb) in main. i believe this to be a serious bug for two reasons: the first is that packages in main should not have any dependencies on non-free software. however,