Your message dated Fri, 28 Jan 2011 16:46:39 -0000
with message-id
<[email protected]>
and subject line Re: Bug#611055: unblock: binutils/2.20.1-16
has caused the Debian Bug report #611055,
regarding unblock: binutils/2.20.1-16
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.)
--
611055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611055
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: freeze-exception
binutils (2.20.1-16) unstable; urgency=low
* Add arm-linux-gnueabi to the multiarch targets, remove the old
arm*-linux-gnu targets. Addresses #610745.
This is a no-change upload for the binary binutils package, and only touches
binutils-multiarch.
--- End Message ---
--- Begin Message ---
On Tue, January 25, 2011 13:54, Adam D. Barratt wrote:
> On Tue, January 25, 2011 06:29, Matthias Klose wrote:
>> binutils (2.20.1-16) unstable; urgency=low
>>
>> * Add arm-linux-gnueabi to the multiarch targets, remove the old
>> arm*-linux-gnu targets. Addresses #610745.
>>
>> This is a no-change upload for the binary binutils package, and only
>> touches binutils-multiarch.
>
> Unfortunately it also FTBFS on powerpc (I realise not as a consequence of
> the change in -16, but it still needs resolving before we can consider an
> unblock).
Seems to have built now. This doesn't really meet the criteria for an
unblock at this point but, after some arguing with myself, unblocked.
Regards,
Adam
--- End Message ---
