If ant-jmf is going away, something should probably obsolete it. Filing against
ant as I have no clue what the proper thing to do the obsoleting is.
Since I nominally own the "ant" package, I'd like to understand the
failure mode a little better. Gary removed the "jmf" subpackage of
"ant" on July 18 (cvs diff -c -r1.53 -r1.54 devel/ant.spec). As you
point out, nothing currently obsoletes it. Under what specific
circumstances does this lack of "Obsoletes" lead to problems? Is this
related to bug 164389?
ant-jmf depends on an explicit version of ant which no longer exists. So trying
to do an update will fail as that package is then left with broken dependencies.
If it's just going away, it probably makes sense to just have the main ant
package obsolete it (since that's where the requires is)
And it's only vaguely related to the ant-bsf case -- that's much clearer in that
ant-apache-bsf provides the same functionality that used to be in the ant-bsf
package and thus, it should obsolete (and possibly also provide for old packages
which depended on the old package name) ant-bsf.
I'm marking this as a duplicate of bug 164389. The initial report for
164389 is a little confusing, but upon careful reading it turns out to
be the same bug.
*** This bug has been marked as a duplicate of 164389 ***