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
debdiff: Ubuntu to Ubuntu
** Patch added: "debdiff: Ubuntu to Ubuntu"
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1482626/+attachment/4449975/+files/blueman_1.99%7Ealpha1-1ubuntu1-2.0-1ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
debdiff: Debian to Ubuntu
** Patch added: "debdiff: Debian to Ubuntu"
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1482626/+attachment/4449977/+files/blueman_2.0-1-2.0-1ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
When you say someone should do a merge, to whom are you referring?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1482626
Title:
Sync blueman 2.0-1 (universe) from Debian stretch (main)
To manage no
"- 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
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
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?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1482
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
** Bug watch added: Debian Bug tracker #772094
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772094
--
You received this bug notification because you a
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.
** Changed in: blueman (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: blueman (Ubu
