On Wed, Jul 20, 2022 at 10:42 AM Kalev Lember <kalevlem...@gmail.com> wrote:
>
> Hi all,
>
> evolution-data-server 3.45.1 has bumped sonames of all its libraries.
> This is in part due to switching from libsoup 2 to libsoup 3 to make
> sure that all of the consumers link to only libsoup 3.
>
> This has already been pushed to rawhide as part of GNOME 43.alpha and
> Milan and I did rebuilds of everything that wasn't FTBFS.
>
> There are still a bunch of packages needing rebuilding and it would be
> great if individual maintainers could take a look at fixing those. New
> evolution-data-server is already in rawhide so the affected packages are
> going to fail the rawhide mass rebuild that is scheduled to start today.

(snip)

> Still needing rebuild (currently FTBFS):
>
> chatty-0.6.7-1.fc37.src.rpm
> elementary-calendar-6.1.1-1.fc37.src.rpm
> elementary-mail-6.4.0-1.fc36.src.rpm
> elementary-planner-3.0.7-1.fc37.src.rpm
> elementary-tasks-6.3.0-1.fc37.src.rpm
> evolution-rss-0.3.96-9.fc36.src.rpm
> switchboard-plug-onlineaccounts-6.5.0-1.fc37.src.rpm

I've looked into my packages on this list, and three are FTBFS because
of too many packagers cooking soup:

- elementary-calendar
- elementary-mail
- elementary-tasks

Only switchboard-plug-onlineaccounts failure seems to be caused by
e-d-s directly:

"error: The name `soup_uri' does not exist in the context of
`E.SourceWebdav' (libedataserver-1.2)"
Is this an expected API change, and if so, do I need to poke upstream
to help me port it to the latest e-d-s version?

Fabio
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to