Hi Frank, Can you answer Emilio's question below?
On Mon, Sep 22, 2025 at 02:22:47PM +0200, Emilio Pozuelo Monfort wrote: > On 22/09/2025 02:42, tony mancill wrote: > > Package: release.debian.org > > Severity: normal > > X-Debbugs-Cc: bob...@packages.debian.org > > Control: affects -1 + src:bobcat > > User: release.debian....@packages.debian.org > > Usertags: transition > > > > > > > > Dear Release Team, > > > > The bobcat source package 6.09.00 introduces an API change that will > > require sourceful uploads of a subset of packages that have build > > dependencies on libbobcat-dev. The following packages will FTBFS once > > bobcat >= 6.09.00 (currently in experimental) enters unstable: > > > > bisonc++ > > c++-annotations > > multispeech > > ssh-cron > > > > Once/if the transition is approved, I will file bugs against all of the > > affected build r-deps and mark those packages as affected by the > > transition bug. At that point, I will prepare patches and uploads for > > the affected r-deps, and *then* we should be ready for the upload and > > transition. Note that (3) of these will be trivial, as the upstream > > author of bobcat is also the upstream author of bisonc++, > > c++-annotations, and ssh-cron and has already prepared fixes as new > > upstream versions. > > Looks like the SONAME stayed the same. Is this an API break only, with no ABI > break? If so, we shouldn't need to schedule rebuilds. Frank, can you confirm that there is no ABI change? That is, packages compiled against 6.07.x will cotinue to work with 6.09.00? Or do we need an SONAME bump here? Thank you, tony
