[Pkg-cups-devel] Current bugs we need to squash

[Kenshi Muto]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello CUPS folks,

As you know, CUPS 1.2 upload makes a bunch of bugs and direct mails.
Although I don't want to apologize myself, it's true I've felt blue
by some disrespect mails.

OK, so let's summarize current bugs...
I'd like to ask everyone how we can manage these issues.

1. CUPS 1.2 won't support usb:/dev/foo style.
   This is the design by upstream,
   "The USB backend no longer supports the usb:/dev/foo
    format on systems that support device ID queries.".
   But it's a very very critical problem for us.
   I don't have a good idea to migrate this automatically.
   (how to solve this on Ubuntu, mpitt?)

2. Permission problem. I set system-user: lp, system-group: lp,
   admin-group: lpadmin for cupsd, but it may not work on some
   environments. (I haven't finished checking all bug reports relate
   with this issue)
   Furthermore we can't edit cupsd.conf via Web. It can be solved by
   "chown lp /etc/cups/cupsd.conf". But unfortunately if user chooses
   "use default configuration file", CUPS removes "Include" directives.
   Although upstream knows this (http://www.cups.org/str.php?L1749),
   this isn't fixed so soon.

3. CUPS 1.2 denies to use * in IP address at this time.
   I reported this to upstream and am awaiting the fix.
   http://www.cups.org/str.php?L1769

4. Long name vs Samba. Although CUPS generates printer share name
   automatically, Samba (or old Windows) limits the name to under 12
   characters. Upstream's answer is
   "the long names are only an issue for Win9x/WinME clients and not
    for supported versions of Windows... We may be updating the "Add
    This Printer" functionality to allow users to change the name
    before adding it - in that case, we can display a similar warning
    message next to the printer name field..."
   http://www.cups.org/str.php?L1355
   Samba still hasn't an name mangling, CUPS upstream won't do
   more for this. Hmm.

Other problems, needs more investigation:
#372637: cupsys: installation breaks

  I wonder why this happened even I defined Depends: libcupsys (>=1.2.1).

#373124: cupsys: Cupsys hangs when trying to creates the certs

  Well, that's a bit strange.

Thanks,
- -- 
Kenshi Muto
kmuto at debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iEYEARECAAYFAkSQBKAACgkQQKW+7XLQPLGWlwCfa1UAeK9njsrsMHqPyAiBrtB2
zOIAoI9noOA4GQlRwNuSNv82osLrVno/
=bMGi
-----END PGP SIGNATURE-----