search

knubknub / opkg

Automatically exported from code.google.com/p/opkg
0 stars 0 forks source link

Replaced package not removed during upgrade #136

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Taken from a comment on issue 89. This needs its own separate issue number.

#2 radolin

I can confirm the bug in a similar situation. I created a package A, and 
package B. In newer versions of package B it integrates the function of A, so A 
is no longer needed and B now has the  'replace A' property.

Steps

1. Install A. Install B
2. Upgrade B to new version, which 'replaces: A'

Expected result:

A is removed during B upgrade

Actual Result:

Both A and new version of B are installed.

Original issue reported on code.google.com by paul.betafive on 3 Jul 2014 at 3:01

GoogleCodeExporter commented 8 years ago 
Ok, this isn't a bug. As per the Debian Policy Manual [1], a package isn't 
actually replaced unless it's listed in both 'Replaces' and 'Conflicts'.

We do need to better document our handling of package control fields, but 
that's another issue.

[1]: http://www.debian.org/doc/debian-policy/ch-relationships.html

Original comment by paul.betafive on 19 Jul 2014 at 12:42