Packaging issue: what to do about debuginfo after arch->noarch change?

Tom Callaway tcallawa at
Mon May 14 14:44:34 UTC 2012

On 05/14/2012 10:34 AM, Tom Lane wrote:
> I recently converted mysql-connector-java from arch to noarch (it used
> to use GCJ to build, now it doesn't).  Martin Cermak pointed out to me
> that if you had the debuginfo subpackage installed, and you upgrade,
> the old debuginfo will still be there even though it's now irrelevant.
> Is this a bug, and if so what should I do about it?
> It seems to me that it's not a bug, because AFAICS there has never been
> any attempt to enforce that only relevant debuginfo packages are
> installed.  For instance, there isn't any Requires: at all from a
> debuginfo package to its base package, let alone an exact-version-match
> Requires:.
> It was suggested that I could add an Obsoletes: line to the specfile
> to get rid of the old debuginfo package, but this seems a bit weird
> to me, and inconsistent with the fact that there aren't Requires:
> linkages.
> I don't see anything in the packaging guidelines that addresses the
> point.  Given that we're converting most Java packages to noarch,
> perhaps the issue comes up often enough to justify having a policy?

Hmm. I'm inclined to say that we ought to resolve this either in
anaconda or preupgrade by running some sort of "cleanup" script that
looks for orphan debuginfo and flushes them down the drain, as opposed
to carrying Obsoletes.


Fedora Project

More information about the devel mailing list