Red Hat Bugzilla – Bug 474769
templates and translated templates should be marked as configuration files
Last modified: 2009-09-02 07:25:48 EDT
Apologies if this request does not belong here...
I've heard from RedHat support representatives and my local (in Israel) RedHat support that a re-base of CUPS on version 1.3.x is planned.
I would like to request that the language translation be placed in separate packages, e.g.: `cups-he' for Hebrew, `cups-fr' for French ...
The Hebrew language translation files we (the company I work for) use is maintained as a `rpm' and is different than what I submitted upstream. We have extended its functionality in ways upstream declined: http://www.cups.org/str.php?L2155
Separate language packages will allow us to avoid file ownership conflicts when using rpm.
We won't be splitting out languages into separate sub-packages. However, a more appropriate solution would be to mark the templates and translated templates as configuration files, as in bug #441719.
Unfortunately it is too late to make this change for RHEL-5.3, but it may appear in a future update.
I've looked at bug #441719 and it reminds me of a very pertinent issue I've
filed with RedHat support.
CUPS is re-based on 1.3.7 as I saw. Our CUPS server is RHEL 5.2 and most (if
not all) clients are RHEL 4.4+ .
The clients print Hebrew iso-8859-9 encoded and compressed (gzipped) text files
by way similar to this:
LANG=he_IL lp -h pserver -p printer1 iso-8859-8.txt.gz
This will fail with CUPS 1.3.7, and to have this:
lp -h pserver -p printer1 -ocomression=gzip
work the patch for STR #2997 needs to be applied.
(my original patch, as upstream later agreed:
Opher: please file a separate bug report for that, as it is a different issue. This bug does appear to be present in our package currently going through evaluation. As there is a work-around for it and the issue was not discovered until very recently it is unlikely (though not impossible) the fix will appear in Red Hat Enterprise Linux 5.3. Filing a separate bug report will help as it will be possible to track it for a future update.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.