Bug#749991: Wrong kernel in debian-installer package

2018-10-01 Thread Wolfgang Schweer
On Thu, Apr 06, 2017 at 09:46:55AM +0200, Cyril Brulebois wrote: > Alexander Sosedkin (2017-04-06): > > That's one way to think about it. Got it, keeping old modules is hard. > > But I wasn't asking about keeping old modules, I see no point in this. > > I was asking about generating and

Bug#749991: Wrong kernel in debian-installer package

2017-04-06 Thread Cyril Brulebois
Alexander Sosedkin (2017-04-06): > That's one way to think about it. Got it, keeping old modules is hard. > But I wasn't asking about keeping old modules, I see no point in this. > I was asking about generating and publishing a matching > dists/testing/main/installer-/current

Bug#749991: Wrong kernel in debian-installer package

2017-04-06 Thread Wouter Verhelst
On Thu, Apr 06, 2017 at 10:01:41AM +0700, Alexander Sosedkin wrote: > On Thu, 6 Apr 2017 00:05:17 +0200 > Cyril Brulebois wrote: > > > That's unfortunate, yes, but there's no easy way to keep old packages > > around in a given repository. > > That's one way to think about it.

Bug#749991: Wrong kernel in debian-installer package

2017-04-05 Thread Alexander Sosedkin
On Thu, 6 Apr 2017 00:05:17 +0200 Cyril Brulebois wrote: > That's unfortunate, yes, but there's no easy way to keep old packages > around in a given repository. That's one way to think about it. Got it, keeping old modules is hard. But I wasn't asking about keeping old modules,

Bug#749991: Wrong kernel in debian-installer package

2017-04-05 Thread Cyril Brulebois
Alexander Sosedkin (2017-04-05): > > Added tag(s) stretch-ignore. > > Whatever it means, it sounds very wrong. > > I see you guys like discussing workarounds, but how about, you know, > actually publishing the correct kernel for netboot in the repo? > Somebody used to do

Bug#749991: Wrong kernel in debian-installer package

2017-04-05 Thread Alexander Sosedkin
> Added tag(s) stretch-ignore. Whatever it means, it sounds very wrong. I see you guys like discussing workarounds, but how about, you know, actually publishing the correct kernel for netboot in the repo? Somebody used to do that, why isn't it the case now?

Bug#749991: Wrong kernel in debian-installer package

2017-03-27 Thread Holger Levsen
On Mon, Mar 27, 2017 at 12:54:18PM +0100, Ian Campbell wrote: > > > One can always use http://snapshot.debian.org/ as one's mirror and > > specify a dated URL that matches the ISO's creation date. > I think (based on the last few paragraphs in the "Usage" section of > that URL) that one would also

Bug#749991: Wrong kernel in debian-installer package

2017-03-27 Thread Ian Campbell
On Mon, 2017-03-27 at 13:32 +0200, Philip Hands wrote: > > Alexander Sosedkin writes: > > > On Mon, 27 Mar 2017 12:43:40 +0200 > > > > Philipp Kern wrote: > > > > > Even if we'd leave the old kernel udebs in testing for a while, you'd  > > > still hit a

Bug#749991: Wrong kernel in debian-installer package

2017-03-27 Thread Alexander Sosedkin
On Mon, 27 Mar 2017 13:32:46 +0200 Philip Hands wrote: > Alexander Sosedkin writes: > > > On Mon, 27 Mar 2017 12:43:40 +0200 > > Philipp Kern wrote: > > > >> Even if we'd leave the old kernel udebs in testing for a while, > >> you'd

Bug#749991: Wrong kernel in debian-installer package

2017-03-27 Thread Philip Hands
Alexander Sosedkin writes: > On Mon, 27 Mar 2017 12:43:40 +0200 > Philipp Kern wrote: > >> Even if we'd leave the old kernel udebs in testing for a while, you'd >> still hit a point where we'd need to drop them and old installers >> would break. > > I can

Bug#749991: Wrong kernel in debian-installer package

2017-03-27 Thread Alexander Sosedkin
On Mon, 27 Mar 2017 12:43:40 +0200 Philipp Kern wrote: > Even if we'd leave the old kernel udebs in testing for a while, you'd > still hit a point where we'd need to drop them and old installers > would break. I can see that it's impossible to support downloading modules for

Bug#749991: Wrong kernel in debian-installer package

2017-03-27 Thread Philipp Kern
On 2017-03-27 11:56, Nye Liu wrote: The reason I ask is because I have custom grub menu configs that I don't want to constantly hand edit or patch on a cron job along with a cron to download the dailies... and then have no idea if the cron will do the right thing, or if the daily even works.

Bug#749991: Wrong kernel in debian-installer package

2017-03-27 Thread Nye Liu
Thanks for your response. On Sun, 26 Mar 2017 18:31:45 +0200 Philipp Kern wrote: > IOW: Is there a way to guarantee that > (dist)/main/installer-amd64/current/images/netboot/netboot.tar.gz does not > contain a kernel that has no modules package IN THAT SAME mirror? > > Or

Bug#749991: Wrong kernel in debian-installer package

2017-03-26 Thread Philipp Kern
On 03/14/2017 10:34 PM, Nye Liu wrote: > On Tue, Mar 14, 2017 at 08:39:31PM +, Ben Hutchings wrote: >> On Tue, 2017-03-14 at 11:36 -0700, Nye Liu wrote: >>> The only apparent solution is to have the kernel maintainers coordinate >>> with the d-i maintainers so that whatever kernel is used in

Bug#749991: Wrong kernel in debian-installer package

2017-03-14 Thread Nye Liu
On Tue, Mar 14, 2017 at 08:39:31PM +, Ben Hutchings wrote: > On Tue, 2017-03-14 at 11:36 -0700, Nye Liu wrote: > > The only apparent solution is to have the kernel maintainers coordinate  > > with the d-i maintainers so that whatever kernel is used in d-i is NOT  > > removed from the package

Bug#749991: Wrong kernel in debian-installer package

2017-03-14 Thread Ben Hutchings
On Tue, 2017-03-14 at 11:36 -0700, Nye Liu wrote: > The only apparent solution is to have the kernel maintainers coordinate  > with the d-i maintainers so that whatever kernel is used in d-i is NOT  > removed from the package repository and its mirrors. The kernel maintainers already coordinate

Bug#749991: Wrong kernel in debian-installer package

2017-03-14 Thread Nye Liu
The only apparent solution is to have the kernel maintainers coordinate with the d-i maintainers so that whatever kernel is used in d-i is NOT removed from the package repository and its mirrors.

Bug#749991: Wrong kernel in debian-installer package

2016-04-21 Thread Nye Liu
This really should be marked grave or serious because it means net install is completely broken.