Hi there!
Can you please keep the foo2zjs-maintainer mailing list cc:ed? If you
do so, no need to cc: me, I read the list. TIA.
I'm sorry for the long mail: I performed more tests with the only
foo2zjs printer I have [1] and I found some interesting stuff, please
read below. I tried to be as more detailed as I could, at least to give
a better overview of the foo2zjs driver status.
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466758#15
On Sat, 01 Nov 2008 09:47:21 +0100, Anthony Towns wrote:
> On Fri, Oct 31, 2008 at 03:52:31PM +0100, Andreas Barth wrote:
>> 2. As per constitution, we (the tech ctte) only makes decision as last
>> resort. So currently, the next step would be for anyone who disagrees
>> with this bug not being release critical to ask the release team to
>> review the decision and maybe overrule it.
>
> I'm not sure I'd want the release team to be able to stop the tech-ctte
> from being involved simply by not making a decision, so I'm not sure I
> agree with this precisely. But in the general case, yes, I'd rather see
> the release team making the call on this.
FYI, the Release Team was asked for an advice on Sun, 26 October [2].
However, I know we (the Debian foo2zjs maintainers) decided to go to the
tech-ctte just two days later...
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=yes&bug=503814#125
>> tech ctte members, any opinion from you on that?
>
> Basically, +1.
>
> On a technical level, it seems to me there's two aspects:
>
> (1) can a package in main include a script that gets stuff from some
> random website really be considered DFSG-free/policy-compliant?
NB, in this case it is not "from some random website", but it is from
*upstream* website, which means that these data are not included in the
upstream sources for other reasons.
Anyway, if the script is moved to /u/s/d/$PKG/examples I would say it is
OK for the package to be in main. And, again, I think the main point is
if printers can work without those data, read below.
> (2) should we make sure that the stuff on the random website is also
> available from somewhere in Debian, in case the random website gets
> shut down, etc?
If there are licensing issues, I see no advantages for Debian in
distributing them. Here what the getweb script from the last tested
upstream version [1] would download:
- not strictly required files (not fully sure, but read below for my
experience with the HP Color LaserJet 1500L)
$ ./getweb 2600n # Get HP Color LaserJet 2600n .ICM files
$ ./getweb 1600 # Get HP Color LaserJet 1600 .ICM files
$ ./getweb 1500 # Get HP Color LaserJet 1500 .ICM files
$ ./getweb 1215 # Get HP Color LaserJet CP1215 .ICM files
$ ./getweb 2530 # Get Konica Minolta 2530 DL .ICM files
$ ./getweb 2490 # Get Konica Minolta 2490 MF .ICM files
$ ./getweb 2480 # Get Konica Minolta 2480 MF .ICM files
$ ./getweb 6115 # Get Xerox Phaser 6115MFP .ICM files
$ ./getweb 2430 # Get Konica Minolta 2430 DL .ICM files
$ ./getweb 2300 # Get Minolta 2300 DL .ICM files
$ ./getweb 2200 # Get Minolta 2200 DL .ICM files
$ ./getweb cpwl # Get Minolta Color PageWorks/Pro L .ICM files
$ ./getweb 300 # Get Samsung CLP-300 .ICM files
$ ./getweb 315 # Get Samsung CLP-315 .ICM files
$ ./getweb 600 # Get Samsung CLP-600 .ICM files
$ ./getweb 610 # Get Samsung CLP-610 .ICM files
$ ./getweb 2160 # Get Samsung CLX-2160 .ICM files
$ ./getweb 3160 # Get Samsung CLX-3160 .ICM files
$ ./getweb 6110 # Get Xerox Phaser 6110 and 6110MFP .ICM files
$ ./getweb 500 # Get Lexmark C500 .ICM files
$ ./getweb 3200 # Get Oki C3200 .ICM files
$ ./getweb 3300 # Get Oki C3300 .ICM files
$ ./getweb 3400 # Get Oki C3400 .ICM files
$ ./getweb 3530 # Get Oki C3530 MFP .ICM files
$ ./getweb 5100 # Get Oki C5100 .ICM files
$ ./getweb 5200 # Get Oki C5200 .ICM files
$ ./getweb 5500 # Get Oki C5500 .ICM files
$ ./getweb 5600 # Get Oki C5600 .ICM files
$ ./getweb 5800 # Get Oki C5800 .ICM files
- firmwares needed for the print to work (the problem with these files
should be the same about "kernel" firmwares)
$ ./getweb 1020 # Get HP LJ 1020 firmware file
$ ./getweb 1018 # Get HP LJ 1005 firmware file
$ ./getweb 1005 # Get HP LJ 1005 firmware file
$ ./getweb 1000 # Get HP LJ 1000 firmware file
$ ./getweb p1505 # Get HP LJ P1505 firmware file
$ ./getweb p1008 # Get HP LJ P1008 firmware file
$ ./getweb p1007 # Get HP LJ P1007 firmware file
$ ./getweb p1006 # Get HP LJ P1006 firmware file
$ ./getweb p1005 # Get HP LJ P1005 firmware file
$ ./getweb 2300dl_fw # Get Minolta 2300DL v2.55 firmware (experts only)
> (1) seems to be resolved as per Andi's comments, but I kind-of think
> (2) is actually the more important issue, and that the stuff getting
> downloaded should probably be packaged for non-free and possibly
> volatile, in order to remove the external dependency.
I would stop using the term "dependency" because in most of the cases
above there is no dependency (as in dpkg) involved at all here, but
mostly an "enhance".
> The package in main would then get a "Suggests:
> foo2zjs-nonfree-drivers", and if the script gets moved to contrib,
> that could then become "Suggests: foo2zjs-nf-d |
> foo2zj-nf-d-getter-script". That assumes someones willing to do the
> legwork of packaging the drivers, of course, which might require
> negotiating permission to redistribute them from whoever owns them.
I have no problem in packaging the ICM/firmware files [3] and I have
already thought about contacting upstream providers of the ICM profiles,
but I have not did it yet because I would prefer this issue solved
first. However, read below for interesting information about some ICM
profiles and their license.
[3] as I showed you before, there are no drivers involved here at all
I spent the whole Sunday and today printing test pages on the HP Color
LaserJet 1500L and an updated lenny-i386, with the not-yet-uploaded new
upstream version [1]. There were two tests: one image, the default
GNOME/Debian splash on lenny [4] with two lines (one green and one
yellow); a PDF produced by Inkscape, with "this is a test" as text and 4
squares in different colors (blue, yellow, green and red).
[4] /usr/share/pixmaps/splash/gnome-debian-splash.png
1) without any external files and any manual intervention (i.e. the
printer was plugged in and GNOME recognized it), the printer actually
prints, and in color, too. This means that my claim that the HP
Color LaserJet 1500L printer needs external data to work [5] is
false (maybe I thought it was not working because of older versions
of the driver).
FWIW, while GNOME chose the correct driver (the foo2oak one), I
cannot choose any specific ICM Color Profile, only testing.icm and
user*.icm.
[5] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449497#103
2) if I configure the printer through the GNOME "Printer configuration"
utility, there are two changes:
- I can now choose a specific ICM Color Profile (hpclj2600n-1.icm)
- the overall quality is degraded, see bug #504415 [6]
[6] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504415
3) if I install the external data thanks to the getweb script, nothing
changes WRT the color quality nor the blurry output described at [6].
To be sure the settings were the default ones, I configured a new
CUPS printer.
Now, what the getweb script downloads for the HP Color LaserJet 1500L:
a) hpclj2600n.tar.gz [7], it contains 2 files:
- hpclj2600n-0.icm is the "hp color LaserJet 3700 ICC color profiles
sRGB" available from the HP website [8]. FWIW in case this file
will be included in a non-free package, I would expect to include
the CMYK version [9], too
- hpclj2600n-1.icm, which is Copyright by LOGO GmbH, Steinfurt
[7] http://foo2hp.rkkda.com/icm/hpclj2600n.tar.gz
[8] file: clj3700rgbwin.exe (2003/12/01)
MD5 checksum: cb536de644eed0136b108c957a918f02
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp? \
lang=en&cc=us&prodTypeId=18972&prodSeriesId=315849&prodNameId=315851& \
swEnvOID=228&swLang=8&mode=2&taskId=135&swItem=lj-16769-1
[9] file: clj3700cmykwin.exe (2003/12/01)
MD5 checksum: 6ce6fbe3f25d96061726e28b7da269e3
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp? \
lang=en&cc=us&prodTypeId=18972&prodSeriesId=315849&prodNameId=315851& \
swEnvOID=228&swLang=8&mode=2&taskId=135&swItem=lj-16768-1
b) km2430.tar.gz [10], it contains 3 files (km2430_*.icm), which are
available from the Minolta website in the GDI Linux driver [11].
This driver seems to be under GPL-2, but the 3 .icm files are
available only as binaries
[10] http://foo2zjs.rkkda.com/icm/km2430.tar.gz
[11] file: 2430DL_lin64bit_1_6_1.zip
MD5 checksum: 4fd111a57a7c10d6196968a3dba6d386
http://onyxftp.mykonicaminolta.com/download/SearchResults.aspx? \
productid=962&filetypeid=0&osid=16
If needed, I can go through every file the getweb script would download
to check their license and where they come from. And again, I can (try
to) contact the owner of these files to negotiate redistribution.
Thx, bye,
Gismo / Luca
Attachment:
pgp1Cg76P43Zv.pgp
Description: PGP signature