As per the policy for nonresponsive package maintainers , this is a ticket to contact Douglas E. Warner (FAS account: silfreed).
pytrainer has had broken runtime dependencies since Fedora 16. The last installable package was for F15. The broken deps reports have also been sent out daily with each rawhide report. This issue is tracked in bug #754669.
Furthermore, since F14, the pytrainer package hasn't worked. According to bug #668853, pytrainer immediately exits at start up without any error message.
Neither of the bug reports had received any comments from the maintainer.
Douglas, please respond.
Douglas E. Warner, could you respond to the ticket, please?
Sorry; I've definitely been AWOL for awhile w.r.t. package building for Fedora. Do you have a co-maintainer lined up for this package that is interested in maintaining this package as well? If not I can post to the devel list and see if anyone is interested. Failing that the package should probably be orphaned/removed from Fedora due to the FTBFS.
No, I don't have anyone specific in mind. If you could post to the devel list, I think that would be a great way forward.
Note that technically pytrainer isn't FTBFS: it builds fine, but has broken runtime dependencies. This is also the reason why it hasn't been already removed from Fedora with the FTBFS cleanup process.
Thanks, and glad to hear you are still around, even if you don't currently have time to work on the packages.
Could you send the email to the devel list, please?
Could you please post to the devel list, or perhaps just orphan the package(s) you don't have time for in pkgdb?
The pkgdb link for pytrainer is https://admin.fedoraproject.org/pkgdb/acls/name/pytrainer
I have posted a follow up mail to the devel list: http://lists.fedoraproject.org/pipermail/devel/2012-September/171355.html
I've acked acls for bsjones, who wants to try and fix this package up.
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:
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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
Thank you for reporting this bug and we are sorry it could not be fixed.