Whilst we can upload fixes for zesty and trusty; neither of those will
have a point release anymore to include a fix for this.
What is the rationale behind requesting a fix for trusty? How do you
expect it to get onto an .iso? A customized iso?
** Changed in: debian-installer-utils (Ubuntu Zesty)
Status: New => In Progress
** Changed in: debian-installer-utils (Ubuntu Xenial)
Status: New => In Progress
** Changed in: debian-installer-utils (Ubuntu Trusty)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: debian-installer-utils (Ubuntu Xenial)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: debian-installer-utils (Ubuntu Zesty)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: debian-installer-utils (Ubuntu Trusty)
Status: New => Won't Fix
** Changed in: debian-installer (Ubuntu Trusty)
Status: New => Won't Fix
** Changed in: debian-installer (Ubuntu Artful)
Status: New => Fix Released
** Changed in: debian-installer (Ubuntu Zesty)
Status: New => Won't Fix
** No longer affects: debian-installer (Ubuntu Bionic)
** Changed in: debian-installer (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: debian-installer (Ubuntu)
Milestone: ubuntu-17.10 => None
** Changed in: debian-installer (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** No longer affects: debian-installer-utils (Ubuntu Bionic)
** No longer affects: systemd (Ubuntu)
** No longer affects: systemd (Ubuntu Artful)
** No longer affects: systemd (Ubuntu Bionic)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in 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
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
