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

Bug#804055: marked as done (transition: graphicsmagick)



Your message dated Fri, 18 Dec 2015 18:32:59 +0100
with message-id <5674434B.1040102@debian.org>
and subject line Re: Bug#804055: transition: graphicsmagick
has caused the Debian Bug report #804055,
regarding transition: graphicsmagick
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.)


-- 
804055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804055
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

Hi,

I've uploaded a new graphicsmagick version to Sid (sorry) that changes
the libGraphicsMagick++-Q16 soname from 11 to 12 . It builds fine on
all architectures.

The Ben file:
title = "graphicsmagick";
is_affected = .depends ~ /\b(libgraphicsmagick++-q16-11)\b/ | .depends
~ /\b(libgraphicsmagick++-q16-12)\b/;
is_good = .depends ~ /\b(libgraphicsmagick++-q16-12)\b/;
is_bad = .depends ~ /\b(libgraphicsmagick++-q16-11)\b/;

Please schedule the needed binNMUs.

Thanks,
Laszlo/GCS

--- End Message ---
--- Begin Message ---
On 16/11/15 10:11, Emilio Pozuelo Monfort wrote:
> On 14/11/15 17:35, László Böszörményi (GCS) wrote:
>> On Mon, Nov 9, 2015 at 10:23 AM, Emilio Pozuelo Monfort
>> <pochu@debian.org> wrote:
>>> On 09/11/15 09:59, László Böszörményi (GCS) wrote:
>>>>  OK, 0.5.12 was uploaded and built on all supported architectures, but
>>>> fails on mips64el due to an ICE. Otherwise the transition is all green
>>>> now.
>>>
>>> You can ignore mips64el for now. It's not in testing so that won't block the
>>> transition.
>>  As noted, it went fine and the transition is over. This bug can be
>> closed if you agree.
> 
> Not yet, the old library hasn't been removed yet because octave doesn't want to
> migrate. That's because octave has old cruft, britney is trying to migrate, but
> it is not installable.
> 
> I'll be taking a look at this at some point. It's all done from your side so no
> worries about this.

And octave just went in, so this is over.

Cheers,
Emilio

--- End Message ---

Reply to: