mstflint_access kernel module licensing is inconsistent
Bug #2061186 reported by
dann frazier
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mstflint (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Committed
|
Undecided
|
dann frazier | ||
Mantic |
Fix Committed
|
Undecided
|
dann frazier |
Bug Description
[Impact]
The mstflint_access kernel module provided by the mstflint-dkms package has inconsistent licensing in the source. While the SPDX-License-
Since I'm backporting changes before/after this correction, I felt it made sense to backport the licensing clarification as well.
[Test Case]
Confirm that the licensing in the source is now consistent.
[Where Things Could Go Wrong]
This is self-described as a licensing correct - updating comments only.
Changed in mstflint (Ubuntu): | |
status: | New → Fix Released |
summary: |
- mstflint licensing is unclear + mstflint_access kernel module licensing is unclear |
summary: |
- mstflint_access kernel module licensing is unclear + mstflint_access kernel module licensing is inconsistent |
Changed in mstflint (Ubuntu Jammy): | |
status: | New → In Progress |
Changed in mstflint (Ubuntu Mantic): | |
status: | New → In Progress |
Changed in mstflint (Ubuntu Jammy): | |
assignee: | nobody → dann frazier (dannf) |
Changed in mstflint (Ubuntu Mantic): | |
assignee: | nobody → dann frazier (dannf) |
To post a comment you must log in.
Hello dann, or anyone else affected,
Accepted mstflint into mantic-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ mstflint/ 4.21.0+ 1-1ubuntu0. 1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification- needed- mantic to verification- done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- mantic. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance for helping!
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.