On Tue, 13 Apr 2010, Michael Schroeder wrote:
On Tue, Apr 13, 2010 at 09:51:12AM +0300, Panu Matilainen wrote:
OTOH: are there cases where self-obsoletes, or conflicts for that matter,
that actually match the package itself ever make any sense at all? At
least I can't think of any.
The
On Tue, 13 Apr 2010, Michael Schroeder wrote:
On Tue, Apr 13, 2010 at 09:51:12AM +0300, Panu Matilainen wrote:
Regarding commit fafd80901c129659d4d0c1945f5922858f410ef7, please
test if a refresh of a package which obsoletes itself works.
Well, the commit doesn't change any behavior, it just
On Tue, Apr 13, 2010 at 09:51:12AM +0300, Panu Matilainen wrote:
OTOH: are there cases where self-obsoletes, or conflicts for that matter,
that actually match the package itself ever make any sense at all? At
least I can't think of any.
The debian folks often use a self conflict to make sure
On Tue, Apr 13, 2010 at 09:51:12AM +0300, Panu Matilainen wrote:
Regarding commit fafd80901c129659d4d0c1945f5922858f410ef7, please
test if a refresh of a package which obsoletes itself works.
Well, the commit doesn't change any behavior, it just removes dead code
which hasn't been active in
