> What is the rationale behind requesting a fix for trusty? How do you expect > it to get onto > an .iso? A customized iso?
Customers use the initrd provided in our archive, not just isos, e.g.: http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/installer- amd64/current/images/netboot/ubuntu-installer/amd64/initrd.gz And updated isos can be produced by debian-installer, e.g.: http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/installer- amd64/current/images/netboot/mini.iso So are you going to SRU this or should I? ** Changed in: debian-installer-utils (Ubuntu Trusty) Status: Won't Fix => In Progress ** Changed in: debian-installer (Ubuntu Trusty) Status: Won't Fix => In Progress ** Changed in: debian-installer (Ubuntu Zesty) Status: Won't Fix => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714505 Title: systemd kmod builtin uses out of date kmod context To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1714505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
