Mailing List Archive: Stabilizing CUPS 1.3

Stabilizing CUPS 1.3

Apr 25, 2008, 4:56 PM

Post #1 of 3 (145 views)

Hello fellow developers,

CUPS 1.3 has been in the tree for quite some time now and has matured
to a degree where it should be ready to go stable. We've no open CUPS
bugs for 1.3 anymore. Also maintaining CUPS 1.2 will be even harder as
time goes by since there's nearly no month passing without a new CVE
affecting CUPS and we have to plug the holes with patches.

KDE 3.5.9 will go stable any time soon and I'd like to have CUPS
stabilised along with it since an upgrade from CUPS 1.2 to 1.3 would
mean an additional rebuild of kdelibs. An ewarn message has already
been added to the ebuild to notify our users to run etc-update and
revdep-rebuild after upgrading from CUPS 1.2 since this is very
important.

If there's anything I might oversee please speak up.

Upstream feature changelog for CUPS 1.3 can be found here:
http://www.cups.org/documentation.php/whatsnew.html

Our current cups-1.3.7-r1 ebuild:
http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-print/cups/cups-1.3.7-r1.ebuild?view=markup

Regards
Timo Gurr
--
gentoo-dev@lists.gentoo.org mailing list

Re: Re: Stabilizing CUPS 1.3 [ In reply to ]

tgurr at gentoo

Apr 26, 2008, 10:34 AM

Post #2 of 3 (137 views)

Permalink

Hello Holger,

2008/4/26 Holger Hoffstaette <holger@wizards.de>:
> Do you happen to know if this is solved in recent versions?

UTF-8 and US-ASCII are the only supported charsets since CUPS 1.3.3.
There's some info about this in the Upstream bug:
http://www.cups.org/str.php?L2537

Comment #17 of the Samba bug you posted seems to mention it'll get
fixed over there for Samba 3.2.0/3.2.1:
https://bugzilla.samba.org/show_bug.cgi?id=5080#c17

> My understanding is that changing samba's "unix charset" to something
> else would fix this, but that is not feasible for me at this point.
> If there is any other way I'd love to hear about it. :)

I'd consider this rather a Samba problem since it probably won't get
fixed or worked around on the CUPS side. But out of interest, any
reason to not convert all your files with convmv to UTF-8 and set in
smb.conf for example:

[global]
dos charset = 850
unix charset = UTF-8

which should get rid of this issue as well (according to the Samba bug
comments) and displays the files correctly for Microsoft Windows
clients, too.

Regards
Timo Gurr
--
gentoo-dev@lists.gentoo.org mailing list

Re: Stabilizing CUPS 1.3 [ In reply to ]

holger at wizards

Jun 17, 2008, 1:29 AM

Post #3 of 3 (139 views)

Permalink

Hi Timo

On Sat, 26 Apr 2008 01:56:17 +0200, Timo Gurr wrote:

> Hello fellow developers,
>
> CUPS 1.3 has been in the tree for quite some time now and has matured to a
> degree where it should be ready to go stable. [...]
>
> If there's anything I might oversee please speak up.

I'm not a dev but my last attempt at using 1.3.x was not successful because
of a change in (more strict AFAIU) input handling. Other distros were
bitten by this as well:
https://bugzilla.samba.org/show_bug.cgi?id=5080
https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/203944

(find many more by googling for "cups Unsupported character set").

Do you happen to know if this is solved in recent versions? My
understanding is that changing samba's "unix charset" to something else
would fix this, but that is not feasible for me at this point.
If there is any other way I'd love to hear about it. :)

thank you
Holger

--
gentoo-dev@lists.gentoo.org mailing list