On Tue, Aug 23, 2022 at 08:51:12AM -0400, Stefan Hajnoczi wrote:
> On Tue, Aug 23, 2022 at 11:24:10AM +0100, Richard W.M. Jones wrote:
> > On Tue, Aug 23, 2022 at 11:38:26AM +0200, Dominik 'Rathann' Mierzejewski 
> > wrote:
> > > I'd suggest doing a mock, copr or scratch build and running abipkgdiff
> > > comparing current rawhide and the updated binary packages. It'll tell
> > > you if there are any subtle ABI differences.
> > 
> > Here's a scratch build:
> > 
> >   https://koji.fedoraproject.org/koji/taskinfo?taskID=91169327
> > 
> > The differences are:
> > 
> > $ abipkgdiff liburing-2.0-4.fc37.x86_64.rpm liburing-2.2-1.fc38.x86_64.rpm 
> > --devel-pkg1 liburing-devel-2.0-4.fc37.x86_64.rpm --devel-pkg2 
> > liburing-devel-2.2-1.fc38.x86_64.rpm --debug-info-pkg1 
> > liburing-debuginfo-2.0-4.fc37.x86_64.rpm --debug-info-pkg2 
> > liburing-debuginfo-2.2-1.fc38.x86_64.rpm
> 
> The changes look good to me. Thanks for posting this information!

It's building now:

  https://koji.fedoraproject.org/koji/taskinfo?taskID=91172512

Note that I had to add the following to the spec file:

  BuildRequires: gcc-c++

Also (we were discussing in a different thread) liburing really needs
a ./run script like we have in libvirt, libnbd etc. because
configuring another project to use upstream liburing from source is a
pain.

Rich.


-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
nbdkit - Flexible, fast NBD server with plugins
https://gitlab.com/nbdkit/nbdkit
_______________________________________________
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to