Kolab 3.0beta: How to deal correctly with updates?
ITSEF Admin <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kolab |
|---|---|
| Organization | brightsight |
| Message-ID | <201212041232.49619.itsef-admin__10473.7914786257$1354621493$gmane$org@brightsight.com> |
Hi all,
quick question: Are there any actions/commands that typically need to be
performed after some Kolab-specific packages got updated? Reason I'm asking:
The other day, I noticed that there was an update for pykolab (0.5.8-4 ->
0.5.8-6) on my Debian Wheezy system. According to the changelog, this fixes
e.g. issue1398, which seems to refer to a /etc/postfix/sasl/smtpd.conf file.
However, even after the update of the Debian package (normal apt-get
upgrade), this file does not exist.
Also, the update was supposed to fix issue1397 (certificate paths for
postfix) - but main.cf still points to non-existing PEM-files.
Once again, I get the feeling that I'm missing something, so any hint would be
appreciated... :-)
Regards,
Thomas
--
------------------------------------------------------------------------------
Thomas Ribbrock, IT-Team brightsight