Bug#1115379: marked as done (transition: poco)
Your message dated Tue, 30 Sep 2025 10:19:19 +0200
with message-id <fc4538b4-8942-4574-9011-b4eb57a1348d@debian.org>
and subject line Re: Bug#1115379: transition: poco
has caused the Debian Bug report #1115379,
regarding transition: poco
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.)
--
1115379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115379
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: poco@packages.debian.org
Control: affects -1 + src:poco
User: release.debian.org@packages.debian.org
Usertags: transition
Hi release team,
Please assign a transition slot for poco. The reverse deps that do not
already FTBFS (#1114216, #1114430) build with the experimental version.
Thanks,
Bastian
Ben file:
title = "poco";
is_affected = .depends ~ "libpocoactiverecord100" | .depends ~ "libpococrypto100" | .depends ~ "libpocodata100" | .depends ~ "libpocodatamysql100" | .depends ~ "libpocodataodbc100" | .depends ~ "libpocodatapostgresql100" | .depends ~ "libpocodatasqlite100" | .depends ~ "libpocoencodings100" | .depends ~ "libpocofoundation100" | .depends ~ "libpocojson100" | .depends ~ "libpocojwt100" | .depends ~ "libpocomongodb100" | .depends ~ "libpoconet100" | .depends ~ "libpoconetssl100" | .depends ~ "libpocoprometheus100" | .depends ~ "libpocoredis100" | .depends ~ "libpocoutil100" | .depends ~ "libpocoxml100" | .depends ~ "libpocozip100" | .depends ~ "libpocoactiverecord112" | .depends ~ "libpococrypto112" | .depends ~ "libpocodata112" | .depends ~ "libpocodatamysql112" | .depends ~ "libpocodataodbc112" | .depends ~ "libpocodatapostgresql112" | .depends ~ "libpocodatasqlite112" | .depends ~ "libpocoencodings112" | .depends ~ "libpocofoundation112" | .depends ~ "libpocojson112" | .depends ~ "libpocojwt112" | .depends ~ "libpocomongodb112" | .depends ~ "libpoconet112" | .depends ~ "libpoconetssl112" | .depends ~ "libpocoprometheus112" | .depends ~ "libpocoredis112" | .depends ~ "libpocoutil112" | .depends ~ "libpocoxml112" | .depends ~ "libpocozip112";
is_good = .depends ~ "libpocoactiverecord112" | .depends ~ "libpococrypto112" | .depends ~ "libpocodata112" | .depends ~ "libpocodatamysql112" | .depends ~ "libpocodataodbc112" | .depends ~ "libpocodatapostgresql112" | .depends ~ "libpocodatasqlite112" | .depends ~ "libpocoencodings112" | .depends ~ "libpocofoundation112" | .depends ~ "libpocojson112" | .depends ~ "libpocojwt112" | .depends ~ "libpocomongodb112" | .depends ~ "libpoconet112" | .depends ~ "libpoconetssl112" | .depends ~ "libpocoprometheus112" | .depends ~ "libpocoredis112" | .depends ~ "libpocoutil112" | .depends ~ "libpocoxml112" | .depends ~ "libpocozip112";
is_bad = .depends ~ "libpocoactiverecord100" | .depends ~ "libpococrypto100" | .depends ~ "libpocodata100" | .depends ~ "libpocodatamysql100" | .depends ~ "libpocodataodbc100" | .depends ~ "libpocodatapostgresql100" | .depends ~ "libpocodatasqlite100" | .depends ~ "libpocoencodings100" | .depends ~ "libpocofoundation100" | .depends ~ "libpocojson100" | .depends ~ "libpocojwt100" | .depends ~ "libpocomongodb100" | .depends ~ "libpoconet100" | .depends ~ "libpoconetssl100" | .depends ~ "libpocoprometheus100" | .depends ~ "libpocoredis100" | .depends ~ "libpocoutil100" | .depends ~ "libpocoxml100" | .depends ~ "libpocozip100";
--- End Message ---
--- Begin Message ---
On 17/09/2025 09:30, Emilio Pozuelo Monfort wrote:
Control: tags -1 confirmed
On 16/09/2025 21:58, Bastian Germann wrote:
I have fixed the mumble bug and it is also building with experimental
poco.
Go ahead.
And it migrated a few days ago. Closing.
Emilio
--- End Message ---
Reply to: