Bug#1091963: transition: capnproto

[tony mancill]

Package: release.debian.org
Severity: normal
X-Debbugs-Cc: ***@packages.debian.org
Control: affects -1 + src:capnproto
User: ***@packages.debian.org
Usertags: transition

Dear Release Team,

I am requesting a transition slot for capnproto 1.1.0 to get the Debian
package current for Trixie. The package has been accepted in
experimental [1] and appears in the auto-transition page [2]. I am able
to build all of the reverse-build-dependencies against 1.1.0 in a sid
chroot, so I expect this to go smoothly, but there's no urgency for this
transition, and so it can wait for the abseil, grpc, and protobuf
transitions to complete.

Thank you,
tony

[1] https://tracker.debian.org/news/1600399/accepted-capnproto-110-1-source-amd64-into-experimental/
[2] https://release.debian.org/transitions/html/auto-capnproto.html


Ben file:

title = "capnproto";
is_affected = .depends ~ "libcapnp-1.0.1" | .depends ~ "libcapnp-1.1.0";
is_good = .depends ~ "libcapnp-1.1.0";
is_bad = .depends ~ "libcapnp-1.0.1";

[Debian Bug Tracking System]

Post by tony mancill
affects -1 + src:capnproto

Bug #1091963 [release.debian.org] transition: capnproto
Added indication that 1091963 affects src:capnproto

[Debian Bug Tracking System]

tags -1 confirmed

Bug #1091963 [release.debian.org] transition: capnproto
Added tag(s) confirmed.

[Debian Bug Tracking System]

Your message dated Sat, 1 Mar 2025 13:20:57 +0100
with message-id <***@ramacher.at>
and subject line Re: Bug#1091963: transition: capnproto
has caused the Debian Bug report #1091963,
regarding transition: capnproto
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 ***@bugs.debian.org
immediately.)