gdebi ignores Replaces directive in case of Conflict
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-apt (Ubuntu) |
Triaged
|
Medium
|
Michael Vogt |
Bug Description
Binary package hint: gdebi
I have encountered this problem with the CrossOver Office (http://
I have reproduced the situation with dummy packages so you have all the details. You can get them there:
* source (1.4KB)
http://
* basic package (1.2KB)
http://
* sophisticated package (1.2KB)
http://
Here is how to reproduce the problem:
$ sudo gdebi foo_1.0.
Reading package lists: Done
Reading state information: Done
Reading state information: Done
Reading state information: Done
Package for testing gdebi's Replaces support
This is the package to be replaced by the more 'sophisticated' version.
Do you want to install the software package? [y/N]:y
Selecting previously deselected package foo.
(Reading database ... 151236 files and directories currently installed.)
Unpacking foo (from foo_1.0.
Setting up foo (1.0.0-1) ...
$ sudo gdebi foo-pro_
Reading package lists: Done
Reading state information: Done
Reading state information: Done
Reading state information: Done
This package is uninstallable
Conflicts with the installed package 'foo'
So gdebi does not want to replace the foo package with foo-pro. I think it should maybe warn the user but still allow him to proceed. With dpkg there is no issue:
$ dpkg -i foo-pro_
Selecting previously deselected package foo-pro.
dpkg: considering removing foo in favour of foo-pro ...
dpkg: yes, will remove foo in favour of foo-pro.
(Reading database ... 151239 files and directories currently installed.)
Unpacking foo-pro (from foo-pro_
Setting up foo-pro (1.0.0-1) ...
Changed in gdebi (Ubuntu): | |
status: | New → Triaged |
Changed in gdebi (Ubuntu): | |
milestone: | later → none |
affects: | gdebi (Ubuntu) → python-apt (Ubuntu) |
tags: | added: apt.debfile |
description: | updated |
Thanks for your bugreport and your very good test case. This will not make it into gutsy unfortunately but I tagged it "later" so that it gets looked at right after the release.
Thanks,
Michael