Bug#1042871: marked as done (transition: simdjson)
Your message dated Mon, 21 Aug 2023 16:13:13 +0000
with message-id <CAM8zJQtSJOPe2y0KjG9bgGw4uL9a0z_WhKUrOy-9Bs+rqYT8TQ@mail.gmail.com>
and subject line Re: Bug#1042871: transition: simdjson
has caused the Debian Bug report #1042871,
regarding transition: simdjson
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.)
--
1042871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042871
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
X-Debbugs-Cc: simdjson@packages.debian.org
Control: affects -1 + src:simdjson
Hi release team,
The simdjson upstream has bumped the ABI version along with their
new release. Thus the transition request.
It has only two reverse dependencies in testing. src:vast is not
in testing. All reverse dependencies compiles against the new version.
Reverse-Build-Depends
=====================
* pcm [ok]
* vast [skipped. not in testing]
Reverse-Build-Depends-Arch
==========================
* cloudflare-ddns [ok]
The automatic transition tracker is correct.
Thank you!
Ben file:
title = "simdjson";
is_affected = .depends ~ "libsimdjson14" | .depends ~ "libsimdjson16";
is_good = .depends ~ "libsimdjson16";
is_bad = .depends ~ "libsimdjson14";
Thank you for using reportbug
--- End Message ---
--- Begin Message ---
On Sun, 6 Aug 2023 at 18:27, M. Zhou <lumin@debian.org> wrote:
> Anyway, it has been uploaded to unstable, and successfully built for
> all release architectures.
libsimdjson14 is gone from testing, closing.
--- End Message ---
Reply to: