Dear all,
I found a solution without having to temporarily remove kolab:
I had a look at what aptitude dist-upgrade proposed, and then did
apt-install default-mysql-client default-mysql-server
which was a step in the right direction. Now aptitude dist-upgrade proposed to
remove cyrus-imapd. This made me wonder how this could be, so I checked
***@kolab:~# apt-cache policy cyrus-imapd
cyrus-imapd:
Installed: 2.5.11.41-0~kolab2
Candidate: 2.5.11.41-0~kolab2
Version table:
2.5.11.41-0~kolab2 501
501 http://obs.kolabsys.com/repositories/Kolab:/16/Debian_9.0 ./
Packages
*** 2.5.11.41-0~kolab2 100
100 /var/lib/dpkg/status
2.5.10-3 500
500 http://mirror.hetzner.de/debian/packages stretch/main amd64
Packages
500 http://http.debian.net/debian stretch/main amd64 Packages
which made me suspect that two different versions of this package exist that
have the exact same version string, and in fact there are some subtle
differences e.g. in the Depends (look for libpci3 for example).
***@kolab:~# apt-cache show cyrus-imapd
Package: cyrus-imapd
Version: 2.5.11.41-0~kolab2
Architecture: amd64
Maintainer: Jeroen van Meeuwen (Kolab Systems) <***@kolabsys.com>
Installed-Size: 4591
Depends: postfix | mail-transport-agent, adduser (>= 3.34), dpkg (>> 1.9.0),
netbase (>= 4.07), gawk, libc6 (>= 2.14), libcomerr2 (>= 1.01), libdb5.3,
libjansson4 (>= 2.
0.1), libldap-2.4-2 (>= 2.4.7), libpci3 (>= 1:3.5.2-1), libpcre3, libsasl2-2,
libsensors4 (>= 1:3.0.0), libsnmp30 (>= 5.7.3+dfsg-1.7~dfsg), libssl1.1 (>=
1.1.0), libwrap
0 (>= 7.6-4~), libzephyr4, perl (>= 5.24.1-3+deb9u4), perlapi-5.24.1
Suggests: sasl2-bin, apt-listchanges (>= 2.35)
...
standard mail spool. It stores mail in a separate directory in its
own MH-like format.
Description-md5: 784eb5fed1d37ab067b173ecc415ee36
Package: cyrus-imapd
Status: install ok installed
Priority: extra
Section: mail
Installed-Size: 4371
Maintainer: Jeroen van Meeuwen (Kolab Systems) <***@kolabsys.com>
Architecture: amd64
Version: 2.5.11.41-0~kolab2
Replaces: cyrus-common-2.2, cyrus-common-2.3, cyrus-common-2.4, cyrus-
imapd-2.2, cyrus-imapd-2.3, cyrus-imapd-2.4, cyrus22-common, cyrus22-imapd,
cyrus23-common, cyrus23
-imapd, cyrus24-common, cyrus24-imapd
Provides: cyrus-common-2.2, cyrus-common-2.3, cyrus-common-2.4, cyrus-
imapd-2.2, cyrus-imapd-2.3, cyrus-imapd-2.4, cyrus22-common, cyrus23-common,
cyrus24-common, imap-s
erver, pop3-server
Depends: postfix | mail-transport-agent, adduser (>= 3.34), dpkg (>> 1.9.0),
netbase (>= 4.07), gawk, libasn1-8-heimdal (>= 1.4.0+git20110226), libc6 (>=
2.14), libcomer
r2 (>= 1.01), libdb5.3, libgssapi3-heimdal (>= 1.4.0+git20110226), libjansson4
(>= 2.0.1), libkrb5-26-heimdal (>= 1.4.0+git20110226), libldap-2.4-2 (>=
2.4.7), libpci3 (
= 1:3.2.1-1), libpcre3 (>= 1:8.35), libroken18-heimdal (>=
1.4.0+git20110226), libsasl2-2, libsensors4 (>= 1:3.0.0), libsnmp30 (>=
5.7.2.1+dfsg-1+deb8u1+b1~dfsg), libss
l1.0.0 (>= 1.0.0), libwrap0 (>= 7.6-4~), libzephyr4, perl (>=
5.20.2-3+deb8u11), perlapi-5.20.2
...
standard mail spool. It stores mail in a separate directory in its
own MH-like format.
Description-md5: 784eb5fed1d37ab067b173ecc415ee36
Homepage: http://www.cyrusimap.org/
So I went ahead and did an apt install cyrus-imapd, which (not sure why)
updated to the newer version with the same version name. Then some more
dependency digging told me that I have to downgrade php-sabre-dav-2.1 from
version 2.1.11-1 (not sure where this came from, I think from kolabsys) to
version 2.10-1 from Debian stretch:
apt install php-sabre-dav-2.1/stretch
and voilá - the dist-upgrade succeeded without removing kolab!
Cheers,
Johannes
P.S.: I do think that this could at least partially have been avoided if the
version string in the Debian 9 repo would be always different from the version
string in the Debian 8 repo. For example, for my R backports repositories on
CRAN, I always append ~stretchcran.0 to the version string for backports to
stretch, and ~jessiecran.0 for backports to jessie. Here ~kolab2 was used for
both repositories.
Hi Matthias,
in my experience, Kolab 16 is just as stable on Debian Stretch as it is on
Jessie.
To upgrade, you typically change all APT sources, then run "apt
dist-upgrade". Some manual intervention may be required afterwards: for
instance, you may have to make sure that all PHP 5 packages are upgraded to
their PHP 7 counterparts. That involves a bit of fumbling, but no rocket
science. Should any questions arise in the process, feel free to ask them
here or on IRC.
I will gladly take this opportunity to ask here: I changed my APT sources
(both for debian and for kolab) to stretch / Debian 9.0, took the usual
precautions and started the upgrade. After the minimal upgrade with apt-get
upgrade two times which went fine and upgraded a lot of packages, I get
***@kolab:/etc/apt/apt.conf.d# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... The following packages were automatically installed and
are no longer required:
389-admin 389-admin-console 389-console 389-ds 389-ds-base 389-ds-base-libs
...
sa-compile sane-utils smarty3 socat spamassassin spamc update-inetd wallace
zendframework
Use 'apt-get autoremove' to remove them.
Done
The following packages will be REMOVED:
chwala erlang-webtool irony kolab kolab-webclient libcwidget3 libnss3-1d
libpcrecpp0 libperl5.20 libproxy1 libpython3.4-minimal libpython3.4-stdlib
libreadline6-dev
libsigc++-2.0-0c2a libwxbase3.0-0 libwxgtk3.0-0 mysql-client-5.5 mysql-
server-5.5 mysql-server-core-5.5 perl-modules php-sabre-dav-2.1 python3.4
python3.4-minimal
The following NEW packages will be installed:
ca-certificates-java default-java-plugin default-jre default-jre-headless
...
r-cran-survival r-recommended re2c reportbug
129 upgraded, 94 newly installed, 23 to remove and 0 not upgraded.
Need to get 237 MB/240 MB of archives.
After this operation, 633 MB of additional disk space will be used.
Do you want to continue? [Y/n]
I am not sure I want to remove kolab, kolab-webclient, chwala and irony in the
process, if they get removed it must be for some dependency problem, so I am
not sure I will be able to reinstall them afterwards. Any thoughts on this?
Johannes
For obvious reasons, I recommend creating a full backup before the upgrade.
Best regards,
Christoph
Post by Matthias Buschthis is quite valuable information. many thanks.
how stable is kolab 16 on stretch?
do I just change debian apt/sources to stretch and run dist-upgrade?
I just saw, documentation now has debian9 too...
What process do you recommend to upgrade from kolab 16 on deb8 to deb9?
change only debian or only kolab or both apt sources?
run apt-get upgrade or dist-upgrade between what changes?
(usually, I change all apt sources, run upgrade, then dist-upgrade)
_______________________________________________
users mailing list
https://lists.kolab.org/mailman/listinfo/users
--
PD Dr. Johannes Ranke
Grenzach-Wyhlen