Am 04.04.2012 11:22, schrieb Ian Campbell:
> On Mon, 2012-04-02 at 17:59 +0200, Dirk Heinrichs wrote:
>> Hi,
>>
>> my Guruplug is still running kernel 3.1.0, but the current kernel
>> package is 3.2.0. This means that the plug wont be able to reboot w/o
>> manual intervention until the fixed uboot is released.
>
> The new version has been uploaded but has not yet transitioned from sid
> to wheezy.
>
> According to
> http://release.debian.org/migration/testing.pl?package=u-boot
> this is due to a build failure on ia64:
> https://buildd.debian.org/status/fetch.php?pkg=u-boot&arch=ia64&ver=2011.12-3&stamp=1331486439
>
> I've no idea what's going on there though, the failure looks pretty
> wierd to me (a cat from /dev/null appears to have produced something
> other than an empty file!). Might be something to do with #630386?
Although it's nice to know that my poor little guruplug survived another
month w/o reboot, I'd really like to have that fixed u-boot released.
There are lots of other packages which are not available on every
platform, so I wonder why a build failure on ia64 (What's that anyway
:)? ) can block an ARM package for such a long time? Or is there
anything relevant to ia64 in this package?
Bye...
Dirk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
