2.1 beta 3 to 2.1 beta 4 upgrade issue
johannes_graumann at web.de
Mon Jan 29 17:11:56 CET 2007
obmtool will usually automatically determine which packages need to be
built. If you have made changes to the configuration files in
/kolab/etc/kolab/templates/ and/or the release includes a change in the
format of configuration files, the installation procedure will put the
default/new files in place, but will backup the old ones as *.rpmsave. If
not attended to, kolab will complain about these at start-up and refuse to
start the service(s) involved. After making sure that all modifications you
made to the original have been transferred to the new file (e.g. by
using 'diff'), you can safely remove the files tagged *.rpmsafe. Kolab
should now start up just fine.
That would have given me the needed information ...
Thomas Arendsen Hein wrote:
> * Johannes Graumann <johannes_graumann at web.de> [20070123 09:48]:
>> used last night to download beta 4 and do a "./obmtool kolab" seemed to
>> run through fine, but upon "/etc/init.d/kolab restart" I got the
>> following message:
>> openpkg:rc:WARNING: package "clamav" has unresolved configuration file
>> openpkg:rc:WARNING: indicated by "*.rpm(new|orig|save)" files in or below
>> openpkg:rc:WARNING: directory "/kolab/etc/clamav". Please resolve first!
>> So I went to investigate and found
>> indeed "/kolab/etc/clamav/clamd.conf.rpmsave"
>> and "/kolab/etc/clamav/freshclam.conf.rpmsave". Diffing them against
>> there non-"rpmsave" counterparts yielded no differences in not-commented
>> lines, so I moved the two files away or now and things seem to work.
>> Is this an appropriate procedure or did I overlook something?
> Yes, this is appropriate.
> It is mentioned in the README in a misleading way:
> | obmtool will usually automatically determine which packages need to be
> | built. If you have made changes to the configuration files in
> | /kolab/etc/kolab/templates/ and the new release has a new kolabd package
> | you may need to transfer your changes from the backups created by rpm
> | (the *.rpmsave) files to the new template files.
> There should be a paragraph saying that files generated from these
> templates usually cause *.rpmsave files to be created, too, and that
> these (only these!) rpmsave files can be moved back to the original
> name (and with the exception of slapd.conf even removed without
> looking at them)
> The clamav security advisory states this more explicit:
> Maybe you can prepare such a paragraph for the README?
More information about the users