19.20-812932 release for Ubuntu In amdgpu-core package there is a preinst script which checks a distribution version. If it is not Ubuntu, it allows installation with warning. But if it detects it is another version of Ubuntu, it declines installation. Why not just let users to install and just warn them that they are using unsupported version? Anyway, users may modify a package with my script, that I attached to this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=110795 Also installation denial of this single package causes a big trouble for those who tried to use installer script. You can see in that bug report that another user was in situation with a lot of broken packages. I also was in such situation and did not know how to recover from that state. Later I have prepared a script to remove everything from amdgpu-pro (also attached there). But really, if you still want to stop ubuntu users, then why do not edit installer, so it goes to install only amdgpu-core first (without its dependencies), and only after that it goes to install all other packages that are returned by build_package_list? Or just make distribution check in installer script rather than in package scriptlet.
Ubuntu packaging issue; this needs to be reported to Ubuntu instead.
TIL AMD does its support via our bugzilla...
This is not a Ubuntu issue, we do this purposely. Let me discuss internally and I can try to get a better solution.
I pushed a fix to move the check to the postinstall script of the pin file, should be easy to comment out installing that package in the script (not really required for install). I'm not sure when the driver will be updated externally with this fix.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/34.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.