Control: forwarded -1 https://github.com/axboe/liburing/issues/228
Hi! On Fri, 2020-10-23 at 12:20:30 +0200, Steinar H. Gunderson wrote: > On Fri, Oct 23, 2020 at 11:33:41AM +0200, Julien Cristau wrote: > > https://github.com/axboe/liburing/commit/25bbcbef3e0a8bfba8044be55d08d5116c51dccd > > seems to have bumped SONAME upstream. > > That would fix it, yes, but it seems to have missed the kflags change > (the commit says all added padding is at the end). > > The kflags change was made a month or so before 0.7 release: > > > https://github.com/axboe/liburing/commit/0f0517331307605e576b3492c93dc4988e06fdc0 Ouch, right, missed that one. :/ Thanks for the report and analysis. On Fri, 2020-10-23 at 12:47:00 +0200, Steinar H. Gunderson wrote: > On Fri, Oct 23, 2020 at 12:41:36PM +0200, Julien Cristau wrote: > > All that's needed is a 0.8 release I guess. Reported and requested this upstream. > Yes, that would fix it. Optionally, one would require something like > a Breaks: liburing (<< 0.7-2) added on all packages compiled against > liburing, plus versioned Breaks on liburing1 on all packages in the > archive ever built against pre-0.7. :-/ If we want to support the interim versions that have never been in a stable release, then I think the only way is to bump the minmum version in liburing shlibs and symbols files to 0.7, then rebuild the couple of packages built with 0.6 against 0.7, and then add Breaks in liburing against the old dependent package versions using the previous liburing releases. Otherwise I'll just package the new upstream release and request a rebuild of reverse dependencies, and we could just ignore 0.7 as if it never existed. :) Thanks, Guillem
