Hello all,
ok, my point is that dependencies on external data/files are
potentially dangerous. if the maintainer of the upstream site makes
changes (as has been done in the past with foo2zjs), then the package
no longer works as intended. if someone replaces the upstream files
with
Hi
I understand your sentiment, and it is indeed a grey area situation. If I
take policy literary, I think this package is fine in main, but it is not
as simple...
In order to get this bug rolling (and lenny released ;-) ), can you all
live with me splitting up the package in two packages:
Hi
Sorry for the confusing statement here.
I understand your sentiment, and it is indeed a grey area situation.
If I take policy literary, I think this package is fine in main, but it
is not as simple...
In order to get this bug rolling (and lenny released ;-) ), can you all
On Sunday 26 October 2008 08:03:46 Steffen Joeris wrote:
Hi
I understand your sentiment, and it is indeed a grey area situation. If
I take policy literary, I think this package is fine in main, but it is
not as simple...
In order to get this bug rolling (and lenny released ;-) ), can
Hi there!
On Sun, 26 Oct 2008 08:03:46 +0100, Steffen Joeris wrote:
On Sun, 26 Oct 2008 07:38:51 +0100. Joost Yervante Damad wrote:
I understand your sentiment, and it is indeed a grey area situation. If I
take policy literary, I think this package is fine in main, but it is not
as simple...
On Sun, 26 Oct 2008 10:12:49 pm Luca Capello wrote:
Hi there!
On Sun, 26 Oct 2008 08:03:46 +0100, Steffen Joeris wrote:
On Sun, 26 Oct 2008 07:38:51 +0100. Joost Yervante Damad wrote:
I understand your sentiment, and it is indeed a grey area situation.
If I take policy literary, I think
Hi Luca,
[3] not that I checked with such printers, I'm only in touch with one
that needs a non-free firmware
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466758#15
So you don't think that your usage of the package is more contrib
then main?
Personally I find it a rather grey
severity 449497 important
thanks
On Sun, 26 Oct 2008 11:40:34 pm Joost Yervante Damad wrote:
Hi Luca,
[3] not that I checked with such printers, I'm only in touch with one
that needs a non-free firmware
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466758#15
So you don't
Hi there!
BTW, Joost, it seems that for the BugSprint [1] you got quite a nasty
bug, sorry :-D
On Sun, 26 Oct 2008 14:08:03 +0100, Steffen Joeris wrote:
severity 449497 important
Thanks to Steffen for the downgrade. To everyone else: please don't
change the severity anymore: while it can
severity 449497 serious
thank you
i don't see how this bug can be considered anything less than serious.
as i explained in my last message, there are two potential grave
problems: security and breakage. and even if neither of these
problems exist now, they certainly could arise during the
Hello,
README.Debian of foo2zjs provides the following text:
cut
foo2zjs for Debian
---
Please understand that I had to delete some files which the author is
still providing, because I got no source code for them.
This is necessary to get the package into Debian main.
If you really
severity 449497 serious
tag 449497 -wishlist
thank you
ok, my point is that dependencies on external data/files are
potentially dangerous. if the maintainer of the upstream site makes
changes (as has been done in the past with foo2zjs), then the package
no longer works as intended. if someone
the problem with external dependencies is that functionality can be
broken due to circumstances outside of your control. vis a vis, the
getweb stuff is currently broken (in unstable as well as stable!)
because the upstream author randomly decided to modify his directory
naming scheme. this is
Package: foo2zjs
Version: 20070718dfsg-6
Severity: serious
Justification: Policy 2.2.1
foo2zjs relies heavily upon non-free firmware that is hosted at the
upstream site. this behavior, i believe, does not adhere to the spirit of
the debian policy for software in main (packages should not
severity 449497 wishlist
tags 449497 wontfix
thanks
Hi Michael
To the best of my knowledge, not all printers need this firmware. Thus, the
package is operational without additional firmware. Unfortunately, some
printers need firmware, that is right. Please feel free to ask hp or the
other
the appropriate solution should be to split the package into separate
foo2zjs and foo2zjs-contrib packages, where the contrib package
contains only the getweb firmware fetching stuff.
has debian-legal reviewed the package? its really up to them to
determine whether this is a policy violation or
On Tue, 6 Nov 2007 04:16:50 pm you wrote:
i believe that the proper solution is to split the package into
foo2zjs and foo2zjs-contrib -- where the contrib package will have
only the non-free getweb stuff.
Nah, a package split with only this script in it would be overkill.
The script is offered
17 matches
Mail list logo
