[Pkg-giraffe-discuss] python3

[Carsten Schoenert]

Hello Mark,

Am 18.05.2018 um 09:52 schrieb Mark Dufour:
> hi all,
> 
> I've been using python3 as my default for quite some time now, and am
> not aware of any real problems.. do you guys see any reason not to
> make it the default for the debian packages (meaning, search and such
> run with python3 always?)?

no not really and the current status of kopanocore in Debian, "only"
available in testing/unstable and no packages in a stable release, makes
it easy to think about to make Python3 the default for Kopano.

As you may have noticed we had recently a discussion on debian-devel
about abandoning Python2 based packages in favor for Python3 related to
the EOL of Python in 2020. I remember that there was in the end no
reason to cut of Python2 packages out of the next Debian release. OTOH
it makes not really sense to me to now introduce new Pyhton2 packages if
there are no hard revers dependencies that would require such Python2
based packages.

In short, yes I'd prefer if we make the switch right now to move over to
Python3 based packages. I tried in the past week to get close to this.

> well, I guess a dual configure/build would
> still be needed to support python2 scripts which is a bit annoying..
> for our own packages, we currently only support python3 via
> python3-kopano and python3-mapi, and the rest still runs with python2
> by default, but that may change before long.. (need to check our
> supported distro plan to see when all have a suitable python3
> version/python3 dependencies).
As you have written in a earlier email it's mostly a build
configuration, build call or the correct call of variables within the
build to get Python3 packages so it's not a dedicated and special setup
within the Debian (and Ubuntu) packaging.
The changes over the past months to kopanocore are incredible and still
there are a lot of changes. I wasn't able to follow that in detail and
not only the Pyhton3 related changes will take some time.

I collected all my previous changes I'd made after the upload of 8.6.1-1
yesterday and made a upload of a version -2 which contains the new
binary package kopano-spamd which needs again a review of the FTP
masters. The dropping of python-mapi etc. for a new package python3-mapi
will again require again uploads to NEW, so it would make sense to get
those new packages all together and do a upload to NEW only one time.
This will need to take some time on our side.

We still need to solve a autopkgtest failure [1] of kopanocore which
still exists since a few uploads do probably changed behavior of
kopanocore itself.
After a little bit of talking about the test failure with Guido it looks
like the dbconfig-common stuff seems to interact correctly with the
config file /etc/kopano/server.cfg for what ever reason.

The main reason for the CI failure is that kopanocore can not connect to
the SQL server with the (correct) credentials in
/etc/kopano/debian-db.cfg which are included by '!include debian-db.cfg'
within the file server.cfg

I can hopefully invest some more time to solve this problem in the next
weeks.

[1] https://ci.debian.net/packages/k/kopanocore/

-- 
Regards
Carsten Schoenert