Your message dated Sun, 17 Jan 2010 20:00:40 +0100
with message-id <[email protected]>
and subject line This should be fixed now
has caused the Debian Bug report #564162,
regarding gnome-user-share: Both obexd-server and obex-data-server should be 
allowed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
564162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564162
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-user-share
Version: 2.28.2-2
Severity: important

I am trying to install blueman and have found a conflict between
gnome-desktop-environment and blueman that seems to be related to the
recent change. The problem arises from the fact that gnome-user-share
depends on obexd-server, blueman on obex-data-server and obexd-server
conflicts on obex-data-server.

The change that probably made the problem:
gnome-user-share (2.28.2-1) unstable; urgency=low
   [ Josselin Mouette ]
      * Depend on obexd-server, not obex-data-server.

Proposed solution: gnome-user-share should depend on both obexd-server
and obex-data-server (as alternate dependency), so that blueman can be
painlessly installed.


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'squeeze'), (500, 
'testing'), (100, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-user-share depends on:
ii  apache2.2-bin                 2.2.14-4   Apache HTTP Server common binary f
ii  gconf2                        2.28.0-1   GNOME configuration database syste
ii  gnome-bluetooth               2.28.3-2   GNOME Bluetooth tools
ii  libapache2-mod-dnssd          0.6-2      Zeroconf support for Apache 2 via 
ii  libc6                         2.10.2-2   GNU C Library: Shared libraries
ii  libcanberra-gtk0              0.22-1     Gtk+ helper for playing widget eve
ii  libcanberra0                  0.22-1     a simple abstract interface for pl
ii  libdbus-1-3                   1.2.16-2   simple interprocess messaging syst
ii  libdbus-glib-1-2              0.82-2     simple interprocess messaging syst
ii  libgconf2-4                   2.28.0-1   GNOME configuration database syste
ii  libglib2.0-0                  2.22.3-1   The GLib library of C routines
ii  libgtk2.0-0                   2.18.3-1   The GTK+ graphical user interface 
ii  libnotify1 [libnotify1-gtk2.1 0.4.5-1    sends desktop notifications to a n
ii  libselinux1                   2.0.89-4   SELinux runtime shared libraries
ii  libunique-1.0-0               1.1.6-1    Library for writing single instanc
ii  libx11-6                      2:1.3.2-1  X11 client-side library
ii  obexd-server                  0.14-1     D-Bus OBEX server

gnome-user-share recommends no packages.

gnome-user-share suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
I've uploaded today a newer gnome-bluetooth's revision (2.28.6-2) 
which contains the fix for this.

gnome-bluetooth's needs obex-data-server to work properly and 
therefore I've switched back to use it, so now you should be able to 
use both blueman and gnome-bluetooth without any dependency issue.

Note that no GNOME package actually make use of obexd-server at the 
moment. I found this out by talking with a GNOME developer some days 
ago that explained me a bit better how things are going with 
obexd-server and obex-data-server, so luckily this issue is fixed now.

Closing the bug.

Cheers,

-- 

  .''`.
 : :' :   Andrea Veri <[email protected]>,
 `. `'                <[email protected]>,
   `-                 <[email protected]>

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to