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

Bug#1083240: marked as done (transition: jimtcl)

Your message dated Sat, 12 Oct 2024 12:57:47 +0200
with message-id <ZwpWK_zO3ZDH8CkE@ramacher.at>
and subject line Re: Bug#1083240: transition: jimtcl
has caused the Debian Bug report #1083240,
regarding transition: jimtcl
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.)


-- 
1083240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083240
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
X-Debbugs-Cc: jimtcl@packages.debian.org
Control: affects -1 + src:jimtcl

Hello,

I would like to request a transition slot for jimtcl 0.83
(experimental -> unstable) due to soname bump. Current ben tracker [1]
is OK. It has two rdeps. One(openocd) has ftbfs issue but have fixed
now[2] and usb-modeswitch is build fine.


So please let me know if any issues.

Ben file:

title = "jimtcl";
is_affected = .depends ~ "libjim0.82t64" | .depends ~ "libjim0.83";
is_good = .depends ~ "libjim0.83";
is_bad = .depends ~ "libjim0.82t64";


[1]: https://release.debian.org/transitions/html/auto-jimtcl.html
[2]: https://bugs.debian.org/1082908

-- 
Regards,
--
  Bo YU

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On 2024-10-11 06:14:48 +0800, Bo YU wrote:
> Hi,
> 
> On Sat, Oct 5, 2024 at 5:59 AM Sebastian Ramacher <sramacher@debian.org> wrote:
> >
> ..
> >
> > Please go ahead.
> 
> The transitions should have been completed from my view. so could we
> close this?:)

Indeed, closing.

Cheers
-- 
Sebastian Ramacher

--- End Message ---
Reply to: