*** This bug is a duplicate of bug 1932163 ***
    https://bugs.launchpad.net/bugs/1932163

All autopkgtests for the newly accepted evdi (1.9.1-1ubuntu3~20.04.1) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

evdi/1.9.1-1ubuntu3~20.04.1 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#evdi

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1923638

Title:
  [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11

Status in evdi package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in evdi source package in Focal:
  Fix Committed

Bug description:
  evdi-dkms in hirsute cannot be used with the 5.11 kernel in hirsute as
  it will fail to build. Upstream updates for 5.11 proved problematic,
  and a working set of updates became available in the upstream project
  only recently. Unfortunately these updates are difficult to backport
  due to upstream changes, and if they are backported the kernel team
  has no access to hardware to confirm that the backports function as
  intended. Therefore the safest course of action seems to be to move
  forward to the latest upstream evdi release plus they fixes for 5.11
  from git, which has been tested by a number of evdi users already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to