Created attachment 700677 [details]
Updated srpm

Don't know if there's any interest, but here's an updated version. Perhaps someone googling for  a more recent Fedora package finds it :)

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Apparently, supybot-gribble obsoletes supybot, but fails at doing it correctly, because supybot has been bumped and rebuilt a few times meanwhile. What's the status with regard to that? Should it have been retired? It seems so.

https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life


    supybot <= 0:0.83.4.1-7.fc20  obsoleted by  supybot-gribble-0:0.83.4.1-15.fc20.noarch  from  supybot-gribble


    supybot-0:0.83.4.1-11.fc20.noarch  isn't obsoleted  (supybot-0.83.4.1-11.fc20.src.rpm)
    supybot-0:0.83.4.1-10.fc19.noarch  isn't obsoleted  (supybot-0.83.4.1-10.fc19.src.rpm)
    supybot-0:0.83.4.1-9.fc18.noarch  isn't obsoleted  (supybot-0.83.4.1-9.fc18.src.rpm)
    supybot-0:0.83.4.1-8.fc17.noarch  isn't obsoleted  (supybot-0.83.4.1-8.fc17.src.rpm)
    supybot-0:0.83.4.1-7.fc16.noarch  is oldest

I have a bad feeling about this. In fact, supybot is still developed and I would rather say that gribble is a separate project. Even if it stays more or less compatible with supybot the plugin set is different.

Another side of this is that supybot seems to have abandoned the "make a release" trail and rather just commits.

Isn't the proper solution here to package gribble separately, and make a git post-release of supybot?

Dunno.

  # repoquery --whatconflicts supybot-gribble
  supybot-0:0.83.4.1-11.fc20.noarch

  # repoquery --whatobsoletes supybot
  supybot-gribble-0:0.83.4.1-15.fc20.noarch

If it Conflicts, it shouldn't set an insufficient Obsoletes tag, too. The spec file doesn't tell whether the FPC has approved that conflict.

Situation is unchanged. I'm giving up here, since there is no response.

To sum up, the current Obsoletes tag is too low, because supybot has been rebuilt a few times since then without adding any changes. At some point, it seems, supybot-gribble was supposed to replace/obsolete supybot, but supybot has escaped from that during several mass-rebuilds.

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.