No longer works in Yakkety

Thanks for reporting this and spotting the applicable commit! Since wily is EOL, your proposal isn't so visible, so I converted it into two debdiffs (for zesty and yakkety) and subscribed ubuntu-sponsors.

 Sorry to ask but how do i apply this patch? If this is the issue where the mobile broadband dongle no longer shows up in the list of available connections, I have this issue since upgrading to 16.10 from 16.04 as well). thx.

@zak wylde: If you can't wait, you can install from Debian; please see <http://askubuntu.com/a/851296>.

@Gunnar - thanks, that seemed to work. At least I can get online now :)

Uploaded to yakkety's unapproved queue. A member of the Stable Release team will need to manually approve it before it can be published as a proposed update for Ubuntu 16.10.

I'm unsubscribing ~ubuntu-sponsors now. Feel free to resubscribe if there's something else that needs to be sponsored.

This bug was fixed in the package usb-modeswitch - 2.4.0+repack0-1ubuntu1

---------------
usb-modeswitch (2.4.0+repack0-1ubuntu1) zesty; urgency=medium

  * Sync with Debian (LP: #1639607, #1639379). Remaining changes:
    - Replace libjim/jimsh build-depends with libpipeline-dev, libudev-dev.
    - dispatcher-c-rewrite.patch: Rewrite dispatcher in C to avoid TCL deps.
    - redirect_dispatcher_output.patch: redirect all dispatcher output when
      called from udev to /dev/null.
    - systemd_service_name.patch: fix instance name for systemd;
      make sure we don't try to start usb-modeswitch with an invalid instance
      name.
  * Refresh patches

usb-modeswitch (2.4.0+repack0-1) unstable; urgency=medium

  * New 2.4.0 upstream release
  * Refresh patches
  * Bump S-V to 3.9.8 without changes needed
  * Set hardening=+all in DEB_BUILD_MAINT_OPTIONS
  * Use the https alternative in VCS-Browser
  * Add patch to fix official{,l}y typo

usb-modeswitch (2.3.0+repack0-1) unstable; urgency=medium

  * New 2.3.0 upstream release
    - Fixed bug which prevented early logging
  * Remove patch to use udev-specific code to wait on /usr mount
    (Closes: #810104)
  * Update gbp.conf

usb-modeswitch (2.2.6+repack0-1) unstable; urgency=medium

  * New 2.2.6 upstream release

usb-modeswitch (2.2.5+repack0-1) unstable; urgency=medium

  * New 2.2.5 upstream release
  * Refresh patches

 -- Jeremy Bicha <email address hidden> Sun, 11 Dec 2016 22:39:28 -0500

Reading this changelog as an SRU team member I find it really unhelpful if not confusing.

+ * Cherry-pick commit 10a62408 from Debian unstable to resolve
+ incompatibility with systemd (>= 230-1~) (LP: #1639607).

Using the words "cherry-pick" and then dropping a patch:

+++ usb-modeswitch-2.2.5+repack0/debian/patches/series 2016-11-06 18:19:05.000000000 +0000
@@ -1,4 +1,3 @@
-03_use_udev_specifics.patch

is what I find confusing. I think using the upstream changelog entry and or commit comment would have been more informative in this case.

Hello Carlos, or anyone else affected,

Accepted usb-modeswitch into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/usb-modeswitch/2.2.5+repack0-1ubuntu1.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 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, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

I installed usb-modeswitch 2.2.5+repack0-1ubuntu1.1 from yakkety-proposed and confirmed the test case.

@Brian: Not sure I understand your remark on the changelog entry. Dropping that patch was part of the upstream commit.

Gunnar, I think he's recommending that an SRU changelog be more specific about what's being done to the package.

As an example, Ubuntu security fix changelogs tend to be extremely specific [1], listing not only the patch name but even the specific source file changed and what the change was. I don't think regular SRUs need to be as specific as that, but I think Brian wanted us to mention in the changelog that we did drop a patch.

[1] https://launchpad.net/ubuntu/+source/game-music-emu/0.6.0-3ubuntu0.16.04.1

I enabled proposed on Yakkety and updated, and now works for me with usb-modeswitch 2.2.5+repack0-1ubuntu1.1.

Yes, something like "Cherry pick .. from Debian unstable" which drops patch 1234 because it was incorrect would have been more informative. Generally speaking seeing patches removed in an SRU is quite suspicious.

This bug was fixed in the package usb-modeswitch - 2.2.5+repack0-1ubuntu1.1

---------------
usb-modeswitch (2.2.5+repack0-1ubuntu1.1) yakkety; urgency=medium

  * Cherry-pick commit 10a62408 from Debian unstable to resolve
    incompatibility with systemd (>= 230-1~) (LP: #1639607).

 -- Carlos Maddela <email address hidden> Mon, 07 Nov 2016 05:19:05 +1100

The verification of the Stable Release Update for usb-modeswitch has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.