Re: libical 4.0 for rawhide (when?)

On Tue, 2026-07-07 at 18:56 +0200, Milan Crha wrote:
> I will check the other packages and update this thread once I'm done
> with it, with the information about my findings.

	Hi,
this is what I found, some of them have proposed patches, some are
already covered.

Generic build failures, unrelated to libical 4.x. I cannot tell for
sure whether they will need any libical changes or not:

   kdepimlibs - already fails to build in rawhide (due to too old CMake rules)

   kmymoney - contains libical 4.x fixes, but fails with:
        In file included from /usr/include/python3.15/Python.h:68,
        from /builddir/build/BUILD/kmymoney-5.2.2-build/kmymoney-5.2.2/kmymoney/plugins/woob/interface/woobinterface.cpp:16:
        /usr/include/python3.15/pyport.h:494:9: error: ‘__STDC_VERSION__’ is not defined, evaluates to ‘0’ [-Werror=undef]

   redwax-tool - fails due to OpenSSL changes (in the redwax_openssl.c)

Those with available patches, either committed or proposed upstream,
where applicable:

   cairo-dock-plug-ins - https://github.com/Cairo-Dock/cairo-dock-plug-ins/pull/132
   claws-mail - https://www.claws-mail.org/bugzilla/show_bug.cgi?id=4942
   gnokii - custom patch at https://download.copr.fedorainfracloud.org/results/mcrha/libical-4.x/srpm-builds/10695986/gnokii-0.6.31-47.0.fc45.src.rpm
   gnome-calendar - https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/763
   orage - https://gitlab.xfce.org/apps/orage/-/merge_requests/94 , which is different from the stable version series, see the COPR source package at https://download.copr.fedorainfracloud.org/results/mcrha/libical-4.x/srpm-builds/10698061/orage-4.20.3-4.fc45.src.rpm
   osmo - https://sourceforge.net/p/osmo-pim/osmo/merge-requests/5/
   syncevolution - https://gitlab.freedesktop.org/SyncEvolution/syncevolution/-/merge_requests/8

Ported upstream for the development version only:

   cyrus-imapd - requires libical 4.0.0 since 3.13.4, see https://github.com/cyrusimap/cyrus-imapd/blob/b8fc9fd5997b6572e84f79a4ac7372d49ff6ba80/docsrc/download/release-notes/3.13/x/3.13.4.rst#L58

I do not know what to do with:

   kf5-kcalendarcore - there are some upstream fixes like
      https://invent.kde.org/frameworks/kcalendarcore/-/merge_requests/199
      https://invent.kde.org/frameworks/kcalendarcore/-/merge_requests/203
      https://invent.kde.org/frameworks/kcalendarcore/-/merge_requests/213
      , but they do not apply cleanly

Simple builds (which are either unaffected or fixed/prepared in the
versions available in Fedora):

   asterisk
   bluez
   cyrus-timezone
   evolution-data-server
   evolution
   evolution-ews
   GoldenCheetah
   kf6-kcalendarcore

Then there are the packages with "indirect dependency" on the libical,
which all build fine:

   akonadi-calendar
   akonadi-search
   calendarsupport
   eventviews
   folks
   incidenceeditor
   kcalutils
   kf5-akonadi-calendar
   kf5-akonadi-search
   kf5-calendarsupport
   kf5-eventviews
   kf5-incidenceeditor
   kf5-kblog
   kf5-kcalendarutils
   kf5-ktnef
   kf5-libkgapi
   kitinerary
   ktnef
   libkgapi


The COPR repository
https://copr.fedorainfracloud.org/coprs/mcrha/libical-4.x/builds/
contains all the builds, failed and succeeded, for easier checking of
the logs. It's two pages of the builds, those interesting on the second
page.

I do not know the release schedule for the `cyrus-imap`, when the
3.13.x will become a stable series (or whether/when it'll get to
Fedora). Then there's that `kf5-kcalendarcore`, with `kdepimlibs`,
`kmymoney` and `redwax-tool`, though these last three can be probably
ignored.

What do the respective maintainers think, please?

I do not want to hurry too much, but it also looks like the Fedora
packages are mostly ready for the switch to the libical 4.x series.
Once the problematic packages are figure out, I will fill a Change
proposal.

	Bye,
	Milan

P.S.: the `gnokii` seems to be a very old project, its web pages show
samba content. No idea whether it's possible to propose any changes for
it to the upstream, or even where it would be.

-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new