Every time cups is updated I have to check mime.convs and mime.types to ensure that references to handling raw file types are uncommented otherwise we notice that one of our printers stops working because the files are overwritten by the updates. Should config files not be left untouched?
We do have 'print command = lpr -r -oraw -P %p %s' in smb.conf but this on its own didn't make the printer work.
Do I just need to keep checking or is there a better way
Oh, Centos 3.4, by the way!
Thanks
Nigel Kendrick
On Wed, 2005-04-27 at 11:27 +0100, Nigel Kendrick wrote:
Every time cups is updated I have to check mime.convs and mime.types to ensure that references to handling raw file types are uncommented otherwise we notice that one of our printers stops working because the files are overwritten by the updates. Should config files not be left untouched?
We do have 'print command = lpr -r -oraw -P %p %s' in smb.conf but this on its own didn't make the printer work.
Do I just need to keep checking or is there a better way
Oh, Centos 3.4, by the way!
Thanks
Nigel Kendrick
That package is not one that is modified by the CentOS team (any package (except kernel) that is modified will have .centos in the name of the package). In the spec file, one has to specifically call out which files have noreplace status ... and those must not be configured that way.
If this is a problem, and those files should not be replaced, please post a bug at RedHat so that they can correct it in future versions.
Thanks,
Nigel Kendrick wrote:
Every time cups is updated I have to check mime.convs and mime.types to ensure that references to handling raw file types are uncommented otherwise we notice that one of our printers stops working because the files are overwritten by the updates. Should config files not be left untouched?
We do have 'print command = lpr -r -oraw -P %p %s' in smb.conf but this on its own didn't make the printer work.
Do I just need to keep checking or is there a better way
They are overwritten by system-config-printer, which is probably called from postinstall part of cups package. You either configure cups by hand (and remove system-config-printer and system-config-printer-gui), or you don't touch any files in /etc/cups and let system-config-printer take care of them.
Same goes for all other packages from system-config-* category. You either remove the package and configure things by hand. Or you install the package and do not touch generated configuration files. It's all or nothing.
If you don't have system-config-printer packages installed, then you should report bug against cups RPM package (those two files should be marked as noreplace).
-
Aleksandar Milivojevic -
Johnny Hughes -
Nigel Kendrick