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

Re: Next d-i alpha release: late June



On 2016-06-25, Cyril Brulebois <kibi@debian.org> wrote:
> Karsten Merker <merker@debian.org> (2016-06-25):
>> on armhf we currently face some u-boot-related problems. U-Boot
>> 2016.03 (in unstable and testing) causes kernel hangs under certain
>> conditions on a number of sunxi platforms.  These issues are fixed in
>> u-boot v2016.05 (latest official release), but v2016.05 has brought
>> new regressions on the am57xx_evm and firefly-rk3288 platforms, so it
>> cannot go into the archive as is.  For details, please refer to
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825214.
>
> Thanks for bringing this up.
>
>> I would be good to have the u-boot issues fixed before we publish the
>> next d-i release.  A possible option would be to backport commit
>> affa020559bca31d6531e19cb1f009c22705a73d from u-boot 2016.05 to
>> u-boot 2016.03 and to urgent the result into testing before doing the
>> d-i release (CCing Vagrant Cascadian, the u-boot maintainer).
>> 
>> Kibi, Vagrant: what's your opinion on the topic?
>
> If the fixes are identified and can be applied on top of the current
> packages in unstable, pushing them (upload & urgent) looks like a good
> plan to me. :)

I can prepare and upload of 2016.03 with patches, but I'm not able to do
as much testing as usual, as i wouldn't be able to recover if the board
tests fail (due to debconf)... but if the patches are limited in scope,
it should be fairly safe to upload.

FWIW, Once u-boot 2016.07 is released in July, I'd like to upload to
unstable. It at least fixes the issues with am57xx. Haven't made any
progress with firefly and it's prone to failing in hard-to-recover ways,
so maybe should just get removed.


live well,
  vagrant

Attachment: pgpx1wZ3lFLuX.pgp
Description: PGP signature


Reply to: