On Tue, Mar 14, 2017 at 08:39:31PM +0000, 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 repository and its mirrors.
> 
> The kernel maintainers already coordinate with the d-i maintainers,
> thanks.  We don't remove any packages; that happens automatically.

Is there a mechanism to insure that when packages are removed from a repo
are reflected in netboot.tar.gz?

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 maybe even an automated way to update netboot.tar.gz every time a
dists linux-image-(arch).deb is updated, a new netboot.tar.gz can be
created from (dist)/main/installer-amd64/current/images/netboot/netboot.tar.gz?

Reply via email to