FFe: Please merge blueman 2.0-1 (universe) from Debian stretch (main)

Blueman 2.0 needs to have in archive merged obexd. Unfortunately, it's not easy to do. See bug #1263260.

I'm subscribing Micah, as he has interest in this case.

Setting status as incomplete for now.

This is actually blocked by Bug #1162781 as obexd has been merged into bluez, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772094

Thanks, unsure if that's the summary which is confusing or if the info is missing, but could you explain why it's ok to drop the ubuntu changes there?

If that question from comment #3 is directed at me, then the summary was autogenerated by requestsync, I haven't changed what requestsync generated with regard to dropping patches.

That said I have directed upstream at the patches Ubuntu has been carrying to see what are still relevant and can be upstreamed.

" - debian/patches/01_dont_autostart_lxde.patch:
      + Don't autostart the applet in LXDE."

that change looks like it's a least still relevant, somebody should do a merge rather than a sync then

the new version also supports still both bluez4&5 so it can be uploaded directly to wily, no need to use the transition ppa for that one

When you say someone should do a merge, to whom are you referring?

It looks like 03_filemanager_fix.patch can be dropped since it's no longer applicable (file manager paths are not hard-coded). I agree that 01_dont_autostart_lxde.patch is still relevant.

I've put together a merge in my PPA here: https://launchpad.net/~bluesabre/+archive/ubuntu/bluez5

blueman (2.0-1ubuntu1) wily; urgency=low

  * Merge from Debian unstable. Remaining changes:
    - debian/patches/03_filemanage_fix.patch:
      + Dropped, no longer needed.
    - debian/patches/dhcpclient_priority
    - debian/patches/01_dont_autostart_lxde.patch
      + Refreshed patches

 -- Sean Davis <email address hidden> Thu, 20 Aug 2015 22:53:28 -0400

blueman (2.0-1) unstable; urgency=low

  * New upstream release

 -- Christopher Schramm <email address hidden> Sun, 24 May 2015 10:08:00 +0200

blueman (2.0~rc1-1) unstable; urgency=low

  * New upstream release (Closes: #757633)

 -- Christopher Schramm <email address hidden> Wed, 13 May 2015 17:08:00 +0200

blueman (1.99~alpha2-1) unstable; urgency=low

  * New upstream release (Closes: #779613, #764635, #762526, #762527, #549274,
                          #652005, #761284, #761286)

 -- Christopher Schramm <email address hidden> Fri, 06 Mar 2015 10:12:00 +0200

debdiff: Ubuntu to Ubuntu

debdiff: Debian to Ubuntu

I assume you've tested it (for future FFes please clarify that)

Go ahead.

Yes, already tested. Works well with my bluetooth headphones and mouse, no issues with normal usage.

Will add the clarification for future FFes. Thanks!

This bug was fixed in the package blueman - 2.0-1ubuntu1

---------------
blueman (2.0-1ubuntu1) wily; urgency=low

  * Merge from Debian unstable (LP: #1482626). Remaining changes:
    - debian/patches/03_filemanage_fix.patch:
      + Dropped, no longer needed.
    - debian/patches/dhcpclient_priority
    - debian/patches/01_dont_autostart_lxde.patch
      + Refreshed patches

blueman (2.0-1) unstable; urgency=low

  * New upstream release

blueman (2.0~rc1-1) unstable; urgency=low

  * New upstream release (Closes: #757633)

blueman (1.99~alpha2-1) unstable; urgency=low

  * New upstream release (Closes: #779613, #764635, #762526, #762527, #549274,
                          #652005, #761284, #761286)

 -- Sean Davis <email address hidden> Mon, 07 Sep 2015 12:48:18 -0400