| Summary: | Update Request: nvidia340 GPL fix | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Thomas Backlund <tmb> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | andrewsfarm, sysadmin-bugs, tarazed25 |
| Version: | 5 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | has_procedure advisory mga5-64-ok | ||
| Source RPM: | nvidia340 | CVE: | |
| Status comment: | |||
| Bug Depends on: | |||
| Bug Blocks: | 18031, 18374, 18375 | ||
|
Description
Thomas Backlund
2016-05-24 10:49:17 CEST
Thomas Backlund
2016-05-24 13:47:03 CEST
Blocks:
(none) =>
18031
Thomas Backlund
2016-05-24 13:59:09 CEST
Blocks:
(none) =>
18374
Thomas Backlund
2016-05-24 13:59:14 CEST
Blocks:
(none) =>
18375 Testing mga5 64
tl;dr; Adding an OK. I already have dkms packages installed, so it doesn't appear to do alot but notably doesn't attempt to pull in a prebuilt kmod. Requires seem OK.
The only danger I see in this is if people have manually installed and are using kernels without using the *-latest meta-packages but even then it will only conceivably fail if they are using an older kernel, without keeping up with kernel updates. If this is what they've done however, then that scenario is quite likely due to kernel versioning.
# rpm -qa *kernel*
nvidia340-kernel-desktop-latest-340.96-6.mga5.nonfree
kernel-userspace-headers-4.1.15-2.mga5
kernel-desktop-devel-4.1.15-2.mga5-1-1.mga5
kernel-desktop-latest-4.1.15-2.mga5
kernel-desktop-4.1.15-2.mga5-1-1.mga5
kernel-desktop-devel-latest-4.1.15-2.mga5
nvidia340-kernel-4.1.15-desktop-2.mga5-340.96-1.mga5.nonfree
kernel-firmware-20150722-1.mga5
kernel-firmware-nonfree-20151018-1.mga5.nonfree
# rpm -qa *nvidia*
dkms-nvidia340-340.96-1.mga5.nonfree
nvidia340-doc-html-340.96-1.mga5.nonfree
nvidia340-kernel-desktop-latest-340.96-1.mga5.nonfree
nvidia340-kernel-4.1.15-desktop-2.mga5-340.96-1.mga5.nonfree
x11-driver-video-nvidia340-340.96-1.mga5.nonfree
# urpmq --list-media active
Core Release
Core Updates
Core Updates Testing
Nonfree Release
Nonfree Updates
Nonfree Updates Testing
Tainted Release
Tainted Updates
Core 32bit Release
Core 32bit Updates
Nonfree 32bit Release
Nonfree 32bit Updates
Tainted 32bit Release
Tainted 32bit Updates
# urpmi nvidia340-kernel-desktop-latest
Marking nvidia340-kernel-desktop-latest as manually installed, it won't be auto-orphaned
writing /var/lib/rpm/installed-through-deps.list
installing nvidia340-kernel-desktop-latest-340.96-6.mga5.nonfree.x86_64.rpm from /var/cache/urpmi/rpms
Preparing... ######################################
1/1: nvidia340-kernel-desktop-latest
######################################
1/1: removing nvidia340-kernel-desktop-latest-340.96-1.mga5.nonfree.x86_64
######################################
Checking requires (irrelevant output omitted)..
# urpmq --media Testing --requires nvidia340-kernel-desktop-latest
dkms-nvidia340[>= 340.96-1.mga5.nonfree]
kernel-desktop-devel-latest
# dkms status -m nvidia340
nvidia340, 340.96-1.mga5.nonfree, 4.1.15-desktop-2.mga5, x86_64: installed
nvidia340, 340.96-1.mga5.nonfree, 4.1.15-desktop-2.mga5, x86_64: installed-binary from 4.1.15-desktop-2.mga5Whiteboard:
(none) =>
has_procedure mga5-64-ok I'll test this builds with the new kernel before validating.
Len Lawrence
2016-06-05 21:13:05 CEST
CC:
(none) =>
tarazed25 I had updated to the 4.4.11 kernel in both 64 and 32 bit before seeing that this was separate. Booted into kernel 4.1.18.2 and tried to update this package, but it didn't appear as an update for me on either system. Yes, I DID make sure to activate nonfree testing. Everything is working, in both kernels, so I can only assume that the package was installed and did what it was supposed to do. I leave it to you whether this is enough for an OK in the whiteboard. CC:
(none) =>
andrewsfarm Validating. CC:
(none) =>
sysadmin-bugs Advisory uploaded. Whiteboard:
has_procedure mga5-64-ok =>
has_procedure advisory mga5-64-ok An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGAA-2016-0091.html Status:
NEW =>
RESOLVED |