Just to be clear, these are both upstream commits. Is there any work
going on upstream to resolve the issue?
Currently eoan is using a kernel copied forward from disco, but we
should be putting a 5.2 kernel into eoan-proposed within the next couple
of weeks. This is likely to be before we could expect to see them in a
disco-proposed kernel, as the patch deadline for the next kernel SRU
cycle has passed.
I agree that the likelihood of regressions is slim for us, as the
changes were made only to support builds using clang. So I will go ahead
and revert these in our 5.2 tree.
I'm not sure why there's a xenial nomination here for a ftbfs in eoan
though ...
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834315
Title:
Revert x86/vdso linker changes from #1830890 as this causes glibc
2.29-0ubuntu3 FTBFS on eoan
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834315/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
