Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #63515
| From | Cyril Brulebois <kibi@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.boot, linux.debian.ports.arm, linux.debian.devel.release, linux.debian.kernel |
| Subject | Re: Fixing stretch debian-installer on armhf |
| Date | 2019-03-07 14:40 +0100 |
| Message-ID | <xz1pD-2hT-5@gated-at.bofh.it> (permalink) |
| References | <xyQud-3K5-1@gated-at.bofh.it> |
| Organization | Debian |
Cross-posted to 4 groups.
[Multipart message — attachments visible in raw view] - view raw
Hi, Vagrant Cascadian <vagrant@debian.org> (2019-03-06): > Even rebuilding the debian-installer images, while pulling in a > working kernel that would boot, debian-installer would load .udeb > modules from stretch, not stretch-updates. This might be ok for > hd-media targets or targets that do not load module .udeb files from > the network, but netboot targets are not likely to work at all. To clarify, from an earlier IRC conversations (#-boot yesterday, #-kernel a couple of days ago): we're mostly considering rebuilding src:debian-installer, not respinning ISO images (those don't seem to be in widespread use in the arm* world). > So some of the options at the moment appear to be: > > * Wait for another point release, rebuild debian-installer, leaving > debian-installer on armhf broken until then. How long till the next > point release? This wasn't confirmed yet but April 27 seems to be the front runner at this stage. > * Rebuild the debian-installer images, pulling in updates from > stretch-updates, leaving only armhf netboot targets broken. Expanding a bit: rebuilding src:debian-installer from the stretch branch, which has s-p-u enabled, would fetch the fixed kernel and a couple of its udebs, at build time; the resulting netboot images wouldn't know about s-p-u though at run time, and would try to load udebs from stretch. Even if we were to have some kind of support for loading udebs from stretch and from s-p-u (backports support patches could help), that would only be an option until a new linux is accepted into s-p-u. Finally, for completeness, there's no specific suppport regarding stretch-updates; we pull stuff from a given suite and optionally from $suite-p-u; of course, we could still switch from s-p-u to s-u for one particular upload… > * Another point release with the kernel update sooner than planned, > and rebuild debian-installer images. This was brought up on #-kernel and it didn't spark joy (lots of teams need to be around for a point release)… Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Fixing stretch debian-installer on armhf Vagrant Cascadian <vagrant@debian.org> - 2019-03-07 03:00 +0100
Re: Fixing stretch debian-installer on armhf Cyril Brulebois <kibi@debian.org> - 2019-03-07 14:40 +0100
Re: Fixing stretch debian-installer on armhf Ben Hutchings <ben@decadent.org.uk> - 2019-03-07 23:10 +0100
Re: Fixing stretch debian-installer on armhf Vagrant Cascadian <vagrant@debian.org> - 2019-03-07 23:40 +0100
Re: Fixing stretch debian-installer on armhf Cyril Brulebois <kibi@debian.org> - 2019-03-08 00:00 +0100
Re: Fixing stretch debian-installer on armhf Cyril Brulebois <kibi@debian.org> - 2019-03-08 00:00 +0100
Re: Fixing stretch debian-installer on armhf "Adam D. Barratt" <adam@adam-barratt.org.uk> - 2019-03-09 12:10 +0100
Re: Fixing stretch debian-installer on armhf Vagrant Cascadian <vagrant@debian.org> - 2019-03-26 21:50 +0100
csiph-web