[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#999504: marked as done (transition: liburing)

Your message dated Sun, 5 Dec 2021 11:27:09 +0100
with message-id <YayT/VkMdmrff1Qc@ramacher.at>
and subject line Re: Bug#999504: transition: liburing
has caused the Debian Bug report #999504,
regarding transition: liburing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
999504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999504
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

Hi!

The liburing source bumped its SONAME from liburing1 to liburing2, but
it should be API compatible. The new upstream has been uploaded to
experimental, and I did a rebuild of all reverse build-depends with the
2.0 release, no FTBFS were found due to the new release. So binNMUs
should be enough for this.

Ben file:

title = "liburing";
is_affected = .depends ~ "liburing1" | .depends ~ "liburing2";
is_good = .depends ~ "liburing2";
is_bad = .depends ~ "liburing1";

Thanks,
Guillem

--- End Message ---
--- Begin Message --- 
On 2021-11-13 02:20:14, Guillem Jover wrote:
> Hi!
> 
> On Fri, 2021-11-12 at 18:50:36 +0100, Sebastian Ramacher wrote:
> > Control: tags -1 confirmed
> > Control: forwarded -1 https://release.debian.org/transitions/html/auto-liburing.html
> > 
> > On 2021-11-12 04:18:57 +0100, Guillem Jover wrote:
> > > Package: release.debian.org
> > > Severity: normal
> > > User: release.debian.org@packages.debian.org
> > > Usertags: transition
> 
> > > The liburing source bumped its SONAME from liburing1 to liburing2, but
> > > it should be API compatible. The new upstream has been uploaded to
> > > experimental, and I did a rebuild of all reverse build-depends with the
> > > 2.0 release, no FTBFS were found due to the new release. So binNMUs
> > > should be enough for this.
> > 
> > Please go ahead.
> 
> Thanks! I've just uploaded it to unstable.

liburing1 got removed from testing.

Cheers
-- 
Sebastian Ramacher

--- End Message ---
Reply to: