Your message dated Fri, 2 Jan 2026 10:46:10 +0100
with message-id <[email protected]>
and subject line Re: Bug#1114871: transition: libmng
has caused the Debian Bug report #1114871,
regarding transition: libmng
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 [email protected]
immediately.)


-- 
1114871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1114871
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected], [email protected]
Control: affects -1 + src:libmng
User: [email protected]
Usertags: transition

I would like to transition from libmng1 to libmng2. Ubuntu already using 
libmng2,
so that should be easy, I guess.

libmng2 is already in experiemental as well.

Following are packages that depends on libmng1.

mplayer
qt5-image-formats-plugins
libmng-dev
libxine2-misc-plugins
libsynfig0t64
qt5-image-formats-plugins
qt6-image-formats-plugins
mplayer-gui
mencoder

Ben file:

title = "libmng";
is_affected = .depends ~ "libmng1" | .depends ~ "libmng2";
is_good = .depends ~ "libmng2";
is_bad = .depends ~ "libmng1";

--- End Message ---
--- Begin Message ---
On 2025-12-03 16:12:46 +0100, Emilio Pozuelo Monfort wrote:
> On 03/12/2025 15:14, Kartik Mistry wrote:
> > On Wed, 3 Dec 2025 at 19:25, Kartik Mistry <[email protected]> wrote:
> > > 2025/12/03 19:05:28 Building package 1 of 7: synfig
> > > 2025/12/03 19:07:34 building synfig failed: exit status 2
> > > 2025/12/03 19:21:31 FAILED: synfig (see buildlogs/synfig_1.5.1+dfsg-4)
> > > 
> > > Re-running synfig, and if it fails, will file a bug against the package.
> > 
> > It seems to be hit by "#1079335  synfig FTBFS with autoconf 2.72". Not
> > a fault of libmng2 for sure.
> > 
> > Should I go ahead with the upload in this case?
> 
> Yes, go ahead.

libmng migrated and the old binaries got removed from testing. Closing

Cheers
-- 
Sebastian Ramacher

--- End Message ---

Reply via email to