Merge lp:~ubuntu-branches/ubuntu/precise/bluez/precise-201203072011 into lp:ubuntu/precise/bluez

Proposed by Ubuntu Package Importer
Status: Merged
Merge reported by: Evan Broder
Merged at revision: not available
Proposed branch: lp:~ubuntu-branches/ubuntu/precise/bluez/precise-201203072011
Merge into: lp:ubuntu/precise/bluez
Diff against target: 200 lines (+112/-29) (has conflicts)
7 files modified
debian/bluez.bluetooth.default (+0/-20)
debian/bluez.bluetooth.upstart (+1/-9)
debian/bluez.maintscript (+1/-0)
debian/bluez.postrm (+49/-0)
debian/bluez.preinst (+45/-0)
debian/changelog (+15/-0)
debian/control (+1/-0)
Text conflict in debian/changelog
To merge this branch: bzr merge lp:~ubuntu-branches/ubuntu/precise/bluez/precise-201203072011
Reviewer Review Type Date Requested Status
Evan Broder (community) Disapprove
Ubuntu branches Pending
Review via email: mp+96445@code.launchpad.net

Description of the change

The package importer has detected a possible inconsistency between the package history in the archive and the history in bzr. As the archive is authoritative the importer has made lp:ubuntu/precise/bluez reflect what is in the archive and the old bzr branch has been pushed to lp:~ubuntu-branches/ubuntu/precise/bluez/precise-201203072011. This merge proposal was created so that an Ubuntu developer can review the situations and perform a merge/upload if necessary. There are three typical cases where this can happen.
  1. Where someone pushes a change to bzr and someone else uploads the package without that change. This is the reason that this check is done by the importer. If this appears to be the case then a merge/upload should be done if the changes that were in bzr are still desirable.
  2. The importer incorrectly detected the above situation when someone made a change in bzr and then uploaded it.
  3. The importer incorrectly detected the above situation when someone just uploaded a package and didn't touch bzr.

If this case doesn't appear to be the first situation then set the status of the merge proposal to "Rejected" and help avoid the problem in future by filing a bug at https://bugs.launchpad.net/udd linking to this merge proposal.

(this is an automatically generated message)

To post a comment you must log in.
Revision history for this message
Evan Broder (broder) wrote :

Eh, I did the merge/rebase/whatever you want to call it by hand.

review: Disapprove

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== removed file 'debian/bluez.bluetooth.default'
2--- debian/bluez.bluetooth.default 2009-06-30 20:05:13 +0000
3+++ debian/bluez.bluetooth.default 1970-01-01 00:00:00 +0000
4@@ -1,20 +0,0 @@
5-# Defaults for bluez
6-
7-# start bluetooth on boot?
8-# compatibility note: if this variable is _not_ found bluetooth will start
9-BLUETOOTH_ENABLED=1
10-
11-# This setting used to switch HID devices (e.g mouse/keyboad) to HCI mode, that
12-# is you will have bluetooth functionality from your dongle instead of only
13-# HID. This is accomplished for supported devices by udev in
14-# /lib/udev/rules.d/62-bluez-hid2hci.rules by invoking hid2hci with correct
15-# parameters.
16-# See /usr/share/doc/bluez/NEWS.Debian.gz for further information.
17-
18-# Older daemons like pand dund and hidd can be found in bluez-compat package as
19-# they are deprecated and provided for backward compatibility only.
20-
21-# Note that not every bluetooth dongle is capable of switching back to HID mode,
22-# see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355497
23-HID2HCI_ENABLED=0
24-HID2HCI_UNDO=0
25
26=== modified file 'debian/bluez.bluetooth.upstart'
27--- debian/bluez.bluetooth.upstart 2012-01-24 11:31:04 +0000
28+++ debian/bluez.bluetooth.upstart 2012-03-07 20:15:22 +0000
29@@ -9,18 +9,10 @@
30 env RFCOMM_CONF=/etc/bluetooth/rfcomm.conf
31
32 expect fork
33+respawn
34
35 exec /usr/sbin/bluetoothd
36
37-pre-start script
38- test -f /etc/default/bluetooth && . /etc/default/bluetooth || :
39-
40- if [ "$BLUETOOTH_ENABLED" = "0" ];
41- then
42- exit 1
43- fi
44-end script
45-
46 post-start script
47 [ "$VERBOSE" = no ] && redirect='>/dev/null 2>&1' || redirect=
48
49
50=== added file 'debian/bluez.maintscript'
51--- debian/bluez.maintscript 1970-01-01 00:00:00 +0000
52+++ debian/bluez.maintscript 2012-03-07 20:15:22 +0000
53@@ -0,0 +1,1 @@
54+rm_conffile /etc/default/bluetooth 4.98-2ubuntu1
55
56=== added file 'debian/bluez.postrm'
57--- debian/bluez.postrm 1970-01-01 00:00:00 +0000
58+++ debian/bluez.postrm 2012-03-07 20:15:22 +0000
59@@ -0,0 +1,49 @@
60+#!/bin/sh
61+# postrm script for bluez
62+#
63+# see: dh_installdeb(1)
64+
65+set -e
66+
67+# summary of how this script can be called:
68+# * <postrm> `remove'
69+# * <postrm> `purge'
70+# * <old-postrm> `upgrade' <new-version>
71+# * <new-postrm> `failed-upgrade' <old-version>
72+# * <new-postrm> `abort-install'
73+# * <new-postrm> `abort-install' <old-version>
74+# * <new-postrm> `abort-upgrade' <old-version>
75+# * <disappearer's-postrm> `disappear' <overwriter>
76+# <overwriter-version>
77+# for details, see http://www.debian.org/doc/debian-policy/ or
78+# the debian-policy package
79+
80+
81+case "$1" in
82+ remove|upgrade|failed-upgrade|disappear)
83+ ;;
84+
85+ purge)
86+ if [ "$(cat /etc/init/bluetooth.override)" = "$(printf "# Inserted by bluez\nmanual\n")" ]; then
87+ rm -f /etc/init/bluetooth.override
88+ fi
89+ ;;
90+
91+ abort-install|abort-upgrade)
92+ if dpkg --compare-versions "$2" le-nl 4.98-2ubuntu1; then
93+ perl -i -0pe 's/# Inserted by bluez\nmanual\n//' /etc/init/bluetooth.override
94+ fi
95+ ;;
96+
97+ *)
98+ echo "postrm called with unknown argument \`$1'" >&2
99+ exit 1
100+ ;;
101+esac
102+
103+# dh_installdeb will replace this with shell code automatically
104+# generated by other debhelper scripts.
105+
106+#DEBHELPER#
107+
108+exit 0
109
110=== added file 'debian/bluez.preinst'
111--- debian/bluez.preinst 1970-01-01 00:00:00 +0000
112+++ debian/bluez.preinst 2012-03-07 20:15:22 +0000
113@@ -0,0 +1,45 @@
114+#!/bin/sh
115+# preinst script for bluez
116+#
117+# see: dh_installdeb(1)
118+
119+set -e
120+
121+# summary of how this script can be called:
122+# * <new-preinst> `install'
123+# * <new-preinst> `install' <old-version>
124+# * <new-preinst> `upgrade' <old-version>
125+# * <old-preinst> `abort-upgrade' <new-version>
126+# for details, see http://www.debian.org/doc/debian-policy/ or
127+# the debian-policy package
128+
129+
130+case "$1" in
131+ install|upgrade)
132+ if dpkg --compare-versions "$2" le-nl 4.98-2ubuntu1; then
133+ (
134+ test -f /etc/default/bluetooth && . /etc/default/bluetooth
135+ if [ "$BLUETOOTH_ENABLED" = 0 ] &&
136+ (! [ -f /etc/init/bluetooth.override ] ||
137+ ! grep -q -e "start on" -e "manual" /etc/init/bluetooth.override); then
138+ printf "# Inserted by bluez\nmanual\n" >> /etc/init/bluetooth.override
139+ fi
140+ )
141+ fi
142+ ;;
143+
144+ abort-upgrade)
145+ ;;
146+
147+ *)
148+ echo "preinst called with unknown argument \`$1'" >&2
149+ exit 1
150+ ;;
151+esac
152+
153+# dh_installdeb will replace this with shell code automatically
154+# generated by other debhelper scripts.
155+
156+#DEBHELPER#
157+
158+exit 0
159
160=== modified file 'debian/changelog'
161--- debian/changelog 2012-03-07 14:36:24 +0000
162+++ debian/changelog 2012-03-07 20:15:22 +0000
163@@ -1,3 +1,4 @@
164+<<<<<<< TREE
165 bluez (4.98-2ubuntu3) precise; urgency=low
166
167 * debian/patches/enable_audio_profiles.patch: properly enable the Source
168@@ -6,6 +7,20 @@
169
170 -- Mathieu Trudel-Lapierre <mathieu-tl@ubuntu.com> Wed, 07 Mar 2012 14:36:24 -0500
171
172+=======
173+bluez (4.98-2ubuntu3) precise; urgency=low
174+
175+ [ Pali Rohár ]
176+ * Respawn bluetooth daemon if crashed.
177+
178+ [ Evan Broder ]
179+ * Eliminate the /etc/default/bluetooth conffile as it's not the Upstart
180+ way. Transition the BLUETOOTH_ENABLED variable to an Upstart override
181+ variable if it's been changed.
182+
183+ -- Evan Broder <evan@ebroder.net> Wed, 07 Mar 2012 11:33:02 -0800
184+
185+>>>>>>> MERGE-SOURCE
186 bluez (4.98-2ubuntu2) precise; urgency=low
187
188 * debian/patches/enable_audio_profiles.patch: enable the Gateway and Source
189
190=== modified file 'debian/control'
191--- debian/control 2012-02-22 10:51:07 +0000
192+++ debian/control 2012-03-07 20:15:22 +0000
193@@ -72,6 +72,7 @@
194
195 Package: bluez
196 Architecture: amd64 armel i386 ia64 mips mipsel powerpc s390 s390x sparc alpha armhf avr32 hppa m68k powerpcspe sh4 sparc64 ppc64
197+Pre-Depends: ${misc:Pre-Depends}
198 Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, module-init-tools, udev (>= 170-1), lsb-base, dbus, python-gobject, python-dbus
199 Replaces: bluez-input, bluez-network, bluez-serial, bluez-utils (<= 3.36-3), bluez-audio (<= 3.36-3), udev (<< 170-1)
200 Conflicts: bluez-utils (<= 3.36-3), bluez-audio (<= 3.36-3)

Subscribers

People subscribed via source and target branches

to all changes: