Re: Upgrading Kolab 16 from Jessie to Stretch (was: Status of GUAM and TLS>1.1 ?)

Hi Christoph,

Am Mittwoch, 5. September 2018, 13:08:22 CEST schrieb Christoph Erhardt:
> Hi Johannes,
> 
> glad you got it to work! Now that you mentioned it, I remember these two
> additional pitfalls as well. I upgraded my system back in May and
> regretfully failed to take notes. ;-)
> 
> Did the upgrade from PHP 5 to 7, including all PHP packages, work without
> any manual intervention? I definitely had to hand-pick the php-* packages
> when I migrated my system to Stretch.

well, I just hadn't noticed that iRony wasn't working... I did have to replace 
the packages listed by dpkg --get-selections | grep php5 by their php7 
counterparts, and install the php7 apache module. In the process, my apache 
php module got disabled, so I had to a2enmod php7.0 and now the kolab modules 
are loaded when apache2 starts. For reference, the error message I got in /
var/log/iRony/errors was 

[13-Sep-2018 11:50:03 Europe/Berlin] PHP Fatal error:  Call to undefined 
function dl() in /usr/share/php/kolabformat.php on line 22

which was triggered because the php kolab modules were not loaded.

Also, /usr/lib/php5/sessionclean had spammed my root@kolab-box mail account 
whith error messages about '/usr/lib/php5/20131226/kolabformat.so' and others 
which could not be loaded.

I think everything works now...

Cheers,

Johannes

> 
> I agree that some kind of distribution suffix would be helpful in the case
> of the cyrus-imapd package. Unfortunately, I believe it's not trivial to do
> that because all .deb packages are built from the exact same sources:
> https://obs.kolabsys.com/package/show/Kolab:16/cyrus-imapd
> 
> That said, allow me to argue that upgrading the underlying distro is neither
> officially documented nor officially supported - it's a best-effort thing.
> We try our best not to actively break things, but the faint-hearted are
> probably better off with the "back up -> install cleanly -> restore"
> routine. :-)
> 
> Best regards,
> Christoph
> 
> On Wednesday, 5 September 2018 12:36:40 CEST Johannes Ranke wrote:
> > 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
> > 
> > root@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).
> > 
> > root@kolab:~# apt-cache show cyrus-imapd
> > Package: cyrus-imapd
> > Version: 2.5.11.41-0~kolab2
> > Architecture: amd64
> > Maintainer: Jeroen van Meeuwen (Kolab Systems) <[email protected]>
> > 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) <[email protected]>
> > 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.


-- 
PD Dr. Johannes Ranke
Grenzach-Wyhlen

_______________________________________________
users mailing list
[email protected]
https://lists.kolab.org/mailman/listinfo/users