FYI
There was a request on IRC to also promote firmware-sof
Moving that here to have an auditable trail why things were changed - also I guess we'd want to have an explicit ack by the kernel team that this is the very same case.
From #ubuntu-release
[11:53] <luis220413> ubuntu-archive: Please move the firmware-sof source package to main to be consistent with linux-firmware. See bug
[11:53] <luis220413> See bug 1738272
@Kernel Team - or most likely @apw - do you agree and want this promoted as maintained by the kernel team?
@Luis:
This isn't listed in https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html so there would need to be a dependency or seed change to hold it in main.
Do you know (if not coordinate with the kernel team please) where this will be done before being promoted? [Without that it would again fall out of main in the next few hours after promotion]
FYI
There was a request on IRC to also promote firmware-sof
Moving that here to have an auditable trail why things were changed - also I guess we'd want to have an explicit ack by the kernel team that this is the very same case.
From #ubuntu-release
[11:53] <luis220413> ubuntu-archive: Please move the firmware-sof source package to main to be consistent with linux-firmware. See bug
[11:53] <luis220413> See bug 1738272
Even if all other special firmware cases apply this still would need an owning team. reqorts. qa.ubuntu. com/reports/ m-r-package- team-mapping. html lists kernel-packages as the owner, so that aspect should be fine indeed.
http://
@Kernel Team - or most likely @apw - do you agree and want this promoted as maintained by the kernel team?
@Luis: /people. canonical. com/~ubuntu- archive/ component- mismatches- proposed. html so there would need to be a dependency or seed change to hold it in main.
This isn't listed in https:/
Do you know (if not coordinate with the kernel team please) where this will be done before being promoted? [Without that it would again fall out of main in the next few hours after promotion]