Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: transition X-Debbugs-Cc: omniorb-d...@packages.debian.org, 1042...@bugs.debian.org Control: affects -1 + src:omniorb-dfsg
Dear release team, Could you please schedule a transition for omniorb-dfsg 4.3.0. There has been an ABI bump since 4.2.0. There are four reverse dependencies listed: omnievents, tango, pytango and logservice. logservice has been remove from unstable and testing. It is only available in buster. I have checked how omnievent, tango and pytango: * tango (don't pay attention the "omniorb-dfsg" in the URL. those pipelines are run as child pipelines inside omniorb-dfsg: amd64: https://salsa.debian.org/santiago/omniorb-dfsg/-/jobs/4671324 i386: https://salsa.debian.org/santiago/omniorb-dfsg/-/jobs/4671325 autopkgtest: https://salsa.debian.org/santiago/omniorb-dfsg/-/jobs/4671332 * pytango: amd64: https://salsa.debian.org/santiago/pytango/-/jobs/4671408 i386: https://salsa.debian.org/santiago/pytango/-/jobs/4671409 (setup autopkgtest in Salsa CI for it is not straightforward yet (WiP!)) * omnievents (orphaned package): amd64: https://salsa.debian.org/santiago/omniorb-dfsg/-/jobs/4649320 i386: https://salsa.debian.org/santiago/omniorb-dfsg/-/jobs/4649322 it doesn't include autopkgtest binNMU will be required for them. Ben file: title = "omniorb-dfsg"; is_affected = .depends ~ ""/libcos4-2|libomniorb4-2/"" | .depends ~ ""/libcos4-3|libomniorb4-3/""; is_good = .depends ~ ""/libcos4-3|libomniorb4-3/""; is_bad = .depends ~ ""/libcos4-2|libomniorb4-2/""; Thanks, -- Santiago
signature.asc
Description: PGP signature
