dvd+rw-tools doesn't update in dapper

[Francisco Javier Cuadrado]

Binary package hint: dvd+rw-tools

Today, I have an update for dvd+rw-tools, but this doesn't work.

dvd+rw-tools update depends on genisoimage packet, but genisoimage doesn't exist in dapper backports repositories, so dvd+rw-tools doesn't update.

Packet information

Name: dvd+rw-tools
Mantainer: Daniel Baumann <email address hidden>

Installed version: 5.21.4.10.8-4ubuntu1

Last version: 7.0.6-dapper1

[Sebastian Rasmussen (sebras)]

It may be worth noting that cdrskin, one of the suggested packages for dvd+rw-tools, is missing as well.

[Roderick Drew (r-c-drew)]

I encountered exactly the same problem today. Adept Manager reports that installation would break other packages.

[psl (slansky)]

I can confirm this problem too.
Ubuntu 6.06.1, i686.

oem@scenic:~$ sudo apt-get install dvd+rw-tools
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  dvd+rw-tools: Depends: genisoimage but it is not installable
E: Broken packages

$ apt-cache search genisoimage
dvd+rw-tools - DVD+-RW/R tools

[Lothar (lothar-tradescape)]

can conform it for Dapper 64bit, too

The following packages have unmet dependencies:
  dvd+rw-tools: Depends: genisoimage but it is not installable
E: Broken packages

[William Grant (wgrant)]

Backporters, please look into this.

[kko (kko)]

William Grant:

Just so I understand, can you please explain this. You assigned this bug to backporters, but why did you also mark this as rejected, as it is/was a valid issue?

[John Dong (jdong)]

It is a valid issue for dapper-backports, but not a valid issue for the central Ubuntu repositories.

It's just a semantic of handling which bugs go to whom.

This issue was resolved as fast as I could, and by now you should be able to access updatable dvd+rw-tools packages.

[kko (kko)]

John Dong:

Thank you for your explanation, this - somehow - helps clarify why a bug reported against "dvd+rw-tools" (main) wouldn't actually be valid in this case.

(Launchpad terminology: Apparently "dapper-backports" are a completely separate "product" in the Launchpad, so it seems that a conceivably less confusing solution - simply changing the "package" this bug affects to point to "dapper-backports" - wouldn't have been possible in Launchpad. At least not with Launchpad's current implementation. (Please correct me if I'm wrong.) Marking this as a duplicate also nicely re-resolved this. :-)

Thanks also for your work on the backport, and, indeed, for resolving this issue very swiftly.

[John Dong (jdong)]

Right, the current conventions are:

* When you file a bug against a Ubuntu package, it's for one of the central repositories {dapper, edgy, feisty, etc} (assumed latest unless you say otherwise).
* When such a bug is "nominated" for a release, it's referring to the -updates repository (via the StableReleaseUpdates process)
* Backports are done as separate Launchpad products for now.