Your message dated Mon, 09 Dec 2013 20:44:12 +0100
with message-id <52a61d8c.60...@thykier.net>
and subject line Re: Bug#728294: gtk+3.0: FTBFS on sparc but built there in the 
past
has caused the Debian Bug report #728294,
regarding gtk+3.0: FTBFS on sparc but built there in the past
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 ow...@bugs.debian.org
immediately.)


-- 
728294: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gtk+3.0
Version: 3.8.6-1
Severity: serious

Hi,

Your package appears to FTBFS on sparc, but was built there in the
past.  This (among other things) blocks testing migration.

~Niels

--- End Message ---
--- Begin Message ---
On 2013-10-30 12:12, Emilio Pozuelo Monfort wrote:
> On 30/10/13 11:46, YunQiang Su wrote:
>> On Wed, Oct 30, 2013 at 6:39 PM, Niels Thykier <ni...@thykier.net> wrote:
>>> Package: gtk+3.0
>>> Version: 3.8.6-1
>>> Severity: serious
>>>
>>> Hi,
>>>
>>> Your package appears to FTBFS on sparc, but was built there in the
>>> past.  This (among other things) blocks testing migration.
> 
> Indeed. I had missed that.
> 
> It fails with:
> 
> ERROR:/build/gtk+3.0-W7h_KC/gtk+3.0-3.8.6/./gtk/tests/testing.c:261:test_spin_button_arrows:
> assertion failed: (newval < oldval)
>   /ui-tests/spin-button-arrows:                                        FAIL
> 
>> It was failed on mips64el port, while successful when manually build or
>> rebuild with sbuild.
>> It is nearly the same situation as sparc.
> 
> Is it failing on the same test? Have you investigated it already?
> 
> Emilio
> 

Looks like someone made it build now, so I'll close this one.

~Niels

--- End Message ---

Reply via email to