[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1115930: marked as done (transition: bobcat)

Your message dated Thu, 25 Sep 2025 10:29:16 +0200
with message-id <1a49213e-8f0b-4e08-8857-214589637610@debian.org>
and subject line Re: Bug#1115930: transition: bobcat
has caused the Debian Bug report #1115930,
regarding transition: bobcat
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.)


-- 
1115930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115930
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: bobcat@packages.debian.org
Control: affects -1 + src:bobcat
User: release.debian.org@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.

Any suggestions are welcome,

Thank you,
tony

Here is the proposed ben file:

title = "bobcat";
is_affected = .depends ~ "libbobcat6";
is_good = .depends ~ "libbobcat6" & >= "6.09.00";
is_bad = .depends ~ "libbobcat6" & << "6.09.00;

--- End Message ---
--- Begin Message --- 
On 24/09/2025 20:23, tony mancill wrote:

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: bobcat@packages.debian.org
Control: affects -1 + src:bobcat
User: release.debian.org@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.


Hi Emilio,

The upstream developer confirmed via private mail that this is an API
break only, so no rebuilds are needed.

As I understand it, it is still considered transition because of the
API breakage, but let me know if I have that wrong.
There's no transition in this specific case. The best course of action is to file bugs at severity important, giving a target deadline for the bobcat upload (leaving some time for those packages to have an opportunity to get fixed), and then upload it to unstable, raising the severity of those bugs to serious. You can help those packages by attaching patches etc.
I'm closing the bug as I don't think there's anything for us to do, but feel free to reply if you have further questions or need anything. 

Cheers,
Emilio

--- End Message ---
Reply to: