[ CCing to the bug report ] On Tue, Jan 06, 2009 at 01:41:07PM +0100, Michal Čihař wrote:
> Hi > > Dne Tue, 6 Jan 2009 13:28:27 +0100 > Cristian Greco <[email protected]> napsal(a): > > > I did test my changes and they seems to work fine for me. > > > > It is not necessary to create a dummy package also for d-t-common (which > > is not related at all with deluge-core) nor to add the Provides: field. > > On the contrary, this is an error because Provides: is only necessary to > > keep the old rev-deps, and this is not what we want. > > > > Upgrading d-t from 0.5.9 to 1.0.7 will cause the installation of deluge, > > which depends on deluge-core, which conflicts with d-t-common (<< 1.0.7). > > So finally you get installed: > > deluge-core > > deluge-common > > deluge > > deluge-torrent > > and can safely remove the last one. > > But deluge should Provides/Replaces/Conflicts deluge-torrent to ensure > that deluge-torrent is automatically removed on upgrades. And I think > that deluge-core should at least Replaces deluge-torrent-common again > to make it automatically remove by apt on upgrades (and you will > probably need the dummy package for this to work anyway). Have you > tested to upgrade using apt or you did manual installation using dpkg? > > The wiki page referenced in a bug report exists for good reason - it is > really not obvious how to make it properly. I test the package upgrade using apt with a local repository created with pbuilder. It seems to work fine for me both with my patch and the proposed patch. Using my patch the sole Conflicts:/Replaces: relationship is between d-t-common and the new d-core, which are the base packages for both the old and the new sets. There is no need to use Provides: because it should only be used if we want to keep rev-deps. deluge-torrent-common --> deluge-torrent * | conflicts/replaces * deluge-core -> deluge-common -> deluge -> deluge-torrent Could you please point me to the possible problems generated by using my patch othern than the provided one (this is just for the sake of completeness, because I'm not really able to catch any significative difference)? Thanks, -- Cristian Greco GPG key ID: 0x0C095825
diff -u deluge-1.0.7.dfsg/debian/control deluge-1.0.7.dfsg/debian/control
--- deluge-1.0.7.dfsg/debian/control
+++ deluge-1.0.7.dfsg/debian/control
@@ -17,8 +17,8 @@
python-xdg,
python-gobject,
python-pkg-resources
-Conflicts: deluge-torrent-common
-Replaces: deluge-torrent-common
+Conflicts: deluge-torrent-common (<< 1.0.7.dfsg-1)
+Replaces: deluge-torrent-common (<< 1.0.7.dfsg-1)
Description: bittorrent client written in Python/PyGTK (daemon)
Deluge is a bittorrent client that utilizes a daemon/client model.
.
@@ -99,0 +100,10 @@
+
+Package: deluge-torrent
+Architecture: all
+Depends: ${misc:Depends}, deluge
+Description: bittorrent client written in Python/PyGTK (transitional package)
+ Deluge is a bittorrent client that utilizes a daemon/client model.
+ .
+ This is a transitional dummy package to ensure clean upgrades from old
+ releases (the package deluge-torrent is replaced by deluge). If nothing
+ depends on it, this package can be safely removed after upgrade.
signature.asc
Description: Digital signature
