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

Bug#1120992: marked as done (transition: libcifpp)



Your message dated Sun, 30 Nov 2025 22:37:46 +0100
with message-id <aSy5Kjm2neBCKts0@ramacher.at>
and subject line Re: Bug#1120992: marked as done (transition: libcifpp)
has caused the Debian Bug report #1120992,
regarding transition: libcifpp
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.)


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

Dear release team,

I would like to request a transition slot for libcifpp. Current ben tracker is OK, reverse dependencies build fine.

Best regards,
Maarten L. Hekkelman


Ben file:

title = "libcifpp";
is_affected = .depends ~ "libcifpp7" | .depends ~ "libcifpp9";
is_good = .depends ~ "libcifpp9";
is_bad = .depends ~ "libcifpp7";

--- End Message ---
--- Begin Message ---
On 2025-11-19 11:58:52 +0100, Emilio Pozuelo Monfort wrote:
> Control: reopen -1
> 
> On 19/11/2025 11:51, Debian Bug Tracking System wrote:
> >   libcifpp (9.0.1-2) unstable; urgency=medium
> >   .
> >     * Transition, Closes: #1120992
> 
> Please don't close transition bugs with uploads. The transition starts with
> the upload, it doesn't end. See [1].

The package migrated and the old binaries got removed from testing.
Closing.

Cheers
-- 
Sebastian Ramacher

--- End Message ---

Reply to: