bluez-passkey-gnome should be removed from the archive and bluez-gnome should replace bluez-passkey-gnome

Bug #73383 reported by Baptiste Mille-Mathias
18
Affects Status Importance Assigned to Milestone
bluez-gnome (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

bluez-passkey-gnome was a packaging mistake.

Both bluez-gnome and bluez-passkey-gnome contain the same files, but bluez-passkey-gnome is no longer generated by the build,so it should be removed from the archive - but something seems to be holding it in place.

Separately, the bluez-gnome package needs to replace bluez-passkey-gnome

Revision history for this message
Laurent Bigonville (bigon) wrote : Re: bluez-passkey-gnome should be removed from the archive

bluez-passkey-gnome should be removed from the archive in feisty. This has been renamed to bluez-gnome by debian.

Changed in bluez-gnome:
status: Unconfirmed → Confirmed
Revision history for this message
Marcel Holtmann (holtmann) wrote :

The bluez-passkey-gnome package was a packing mistake and should be fully removed. The package that contains all GNOME related applications is bluez-gnome. This is the name of the source package and should also be the name of the binary package. It is now fixed in Debian.

Revision history for this message
Daniel Holbach (dholbach) wrote :

It will be automatically removed soon. It's just the binary package, not the source package.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Once ubuntu-meta has been updated, this should have happened.

Revision history for this message
Robert Collins (lifeless) wrote :

bluez-gnome is still faulty: It needs to have a 'replaces: bluez-passkey-gnome' control entry, otherwise upgrades on machines with bluez-passkey-gnome installed will fail.

Possibly having a conflicts line as well would be a good idea, or even 'upgrades' though I think that that is not honoured well by the UI level tool chain so theres not much point.

Having conflicts will force bluez-passkey-gnome to be uninstalled, but that may require user intervention depending on the packaging toolchain being used by the user, so I suggest just a replaces: clause for now.

Changed in bluez-gnome:
importance: Undecided → Low
description: updated
Revision history for this message
Steve Kowalik (stevenk) wrote :

This has been fixed in the 0.7-1ubuntu1 upload of bluez-gnome.

Changed in bluez-gnome:
status: Confirmed → Fix Committed
Steve Kowalik (stevenk)
Changed in bluez-gnome:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.