** Description changed: + [ Impact ] + The linux-image-generic package depends on linux-firmware which is over half a gigabyte in size installed. I will assume that quite many people do not have netronome hardware which weighs in at almost 150MB of that. I kindly suggest to put such large firmware for less common hardware into its own linux-firmware-extra package which would be recommended by linux-firmare. Comments? I'm willing to help with the packaging provided that the changes have a chance to land. + + juergh: The main driver for this is that a firmware package update + brings down the archive due to its size. It's been decided to backport + the split to Noble. + + [ Test case ] + + 1. Install currently released linux-firmware monolith from -updates pocket. + 2. Gather list of installed firmware files. + 3. Update linux-firmware from -proposed pocket which pulls in all the split packages. + 4. Gather list of installed firmware file. + 5. Verify lists from #2 and #4 are identical. + 6. dist-upgrade to Resolute. + 7. Verify all firmware packages are correctly upgraded. + + [ Where Problems Could Occur ] + + Potential issues during package installation and upgrades, due to + conflicting package contents. Given that the package build process is + completely different it's possible that some firmware files are missing, + resulting in non-functional HW. + + [ Notes ] + + The first release of the split packages provides the same firmwares as + the currently released linux-firmware monolith. An upgrade from the + monolith to the split packages should be completely transparent and not + introduce any regressions (famous last words :-/).
** Description changed: [ Impact ] The linux-image-generic package depends on linux-firmware which is over half a gigabyte in size installed. I will assume that quite many people do not have netronome hardware which weighs in at almost 150MB of that. I kindly suggest to put such large firmware for less common hardware into its own linux-firmware-extra package which would be recommended by linux-firmare. Comments? I'm willing to help with the packaging provided that the changes have a chance to land. juergh: The main driver for this is that a firmware package update - brings down the archive due to its size. It's been decided to backport - the split to Noble. + brings down the archive due to the package size. It's been decided to + backport the split to Noble. [ Test case ] 1. Install currently released linux-firmware monolith from -updates pocket. 2. Gather list of installed firmware files. 3. Update linux-firmware from -proposed pocket which pulls in all the split packages. 4. Gather list of installed firmware file. 5. Verify lists from #2 and #4 are identical. 6. dist-upgrade to Resolute. 7. Verify all firmware packages are correctly upgraded. [ Where Problems Could Occur ] Potential issues during package installation and upgrades, due to conflicting package contents. Given that the package build process is completely different it's possible that some firmware files are missing, resulting in non-functional HW. [ Notes ] The first release of the split packages provides the same firmwares as the currently released linux-firmware monolith. An upgrade from the monolith to the split packages should be completely transparent and not introduce any regressions (famous last words :-/). ** Description changed: [ Impact ] The linux-image-generic package depends on linux-firmware which is over half a gigabyte in size installed. I will assume that quite many people do not have netronome hardware which weighs in at almost 150MB of that. I kindly suggest to put such large firmware for less common hardware into its own linux-firmware-extra package which would be recommended by linux-firmare. Comments? I'm willing to help with the packaging provided that the changes have a chance to land. juergh: The main driver for this is that a firmware package update brings down the archive due to the package size. It's been decided to backport the split to Noble. [ Test case ] 1. Install currently released linux-firmware monolith from -updates pocket. 2. Gather list of installed firmware files. 3. Update linux-firmware from -proposed pocket which pulls in all the split packages. - 4. Gather list of installed firmware file. + 4. Gather list of installed firmware files. 5. Verify lists from #2 and #4 are identical. 6. dist-upgrade to Resolute. 7. Verify all firmware packages are correctly upgraded. [ Where Problems Could Occur ] Potential issues during package installation and upgrades, due to conflicting package contents. Given that the package build process is completely different it's possible that some firmware files are missing, resulting in non-functional HW. [ Notes ] The first release of the split packages provides the same firmwares as the currently released linux-firmware monolith. An upgrade from the monolith to the split packages should be completely transparent and not introduce any regressions (famous last words :-/). ** Description changed: [ Impact ] The linux-image-generic package depends on linux-firmware which is over half a gigabyte in size installed. I will assume that quite many people do not have netronome hardware which weighs in at almost 150MB of that. I kindly suggest to put such large firmware for less common hardware into its own linux-firmware-extra package which would be recommended by linux-firmare. Comments? I'm willing to help with the packaging provided that the changes have a chance to land. juergh: The main driver for this is that a firmware package update brings down the archive due to the package size. It's been decided to backport the split to Noble. [ Test case ] 1. Install currently released linux-firmware monolith from -updates pocket. 2. Gather list of installed firmware files. 3. Update linux-firmware from -proposed pocket which pulls in all the split packages. 4. Gather list of installed firmware files. 5. Verify lists from #2 and #4 are identical. - 6. dist-upgrade to Resolute. + 6. Upgrade to Resolute. 7. Verify all firmware packages are correctly upgraded. [ Where Problems Could Occur ] Potential issues during package installation and upgrades, due to conflicting package contents. Given that the package build process is completely different it's possible that some firmware files are missing, resulting in non-functional HW. [ Notes ] The first release of the split packages provides the same firmwares as the currently released linux-firmware monolith. An upgrade from the monolith to the split packages should be completely transparent and not introduce any regressions (famous last words :-/). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958518 Title: Split linux-firmware into multiple packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958518/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
