I am looking now at the number of changes that are included between the versions to determine if this is indeed SRUable. Out of curiosity though - even though I also originally was thinking about backporting 1.6.8, would using 1.6.4 from zesty instead be also feasible? If we go the SRU- way, I now think using 1.6.4 might be easier, as otherwise we'd have to think about updating zesty to 1.4.8 as well (as after upgrading from xenial to zesty a user would get and older package, which is not acceptable).
Another question: did you also by any chance consider using the backports pocket for this purpose? This might be much easier to do than SRUing such a big delta. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: In Progress Bug description: We would like to upgrade xenial to 1.6 series so it supports the same modems as the modem-manager snap, specifically some new Sierra modems (HL8548 and others from HL series, popular in IoT devices). These are the packages that would need to be updated: libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap libqmi: 1.12.6-1 in xenial, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
