On 2020-10-23 15:32:48, Steinar H. Gunderson wrote:
> On Fri, Oct 23, 2020 at 03:27:23PM +0200, Guillem Jover wrote:
> > 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
On Fri, Oct 23, 2020 at 03:27:23PM +0200, Guillem Jover wrote:
> 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
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
> >
Processing control commands:
> forwarded -1 https://github.com/axboe/liburing/issues/228
Bug #972758 [liburing1] ABI breakage without soname bump
Set Bug forwarded-to-address to 'https://github.com/axboe/liburing/issues/228'.
--
972758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972758
On Fri, Oct 23, 2020 at 12:41:36PM +0200, Julien Cristau wrote:
> All that's needed is a 0.8 release I guess.
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
On Fri, Oct 23, 2020 at 12:20:30PM +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
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
On Fri, Oct 23, 2020 at 10:47:57AM +0200, Steinar H. Gunderson wrote:
> On Fri, Oct 23, 2020 at 09:55:36AM +0200, Steinar H. Gunderson wrote:
> > If this were somehow only about newer functionality or critical fixes, it
> > could
> > be fixed by bumping the versioned dependency, but rhis goes
On Fri, Oct 23, 2020 at 09:55:36AM +0200, Steinar H. Gunderson wrote:
> If this were somehow only about newer functionality or critical fixes, it
> could
> be fixed by bumping the versioned dependency, but rhis goes both ways; if you
> build plocate against liburing 0.6-3, and then upgrade
Package: liburing1
Version: 0.7-1
Severity: grave
Tags: upstream
Hi,
I've had a number of reports from people who are having problems with plocate,
that can be traced to differing versions of liburing1. Specifically, plocate
is built in sid against liburing1 0.7-1 (which gets a versioned
10 matches
Mail list logo
