Dear all,
I understood that there is now, or it was since log time, but it is enforced in the last months, a procedure of retireing obsoleted, unmaintained packages. Nothing against it, just that the way it is applied creates problems. Most probably it is because maintainers are not having a look at the e-mails with the subject "Orphaned packages in epelX".
We have now a situation like this:
- one of our packages uses "python-daemon"-
https://admin.fedoraproject.org/pkgdb/package/python-daemon/. As you see it is supported on all OSes, in particular it is supported on EPEL5
- python-daemon depends on "python-lockfile" -
https://admin.fedoraproject.org/pkgdb/package/python-lockfile/and
"2015-01-23: Retired orphaned package, because it was orphaned for more than six weeks.
Reference:
https://fedorahosted.org/epel/ticket/7"
And from here you arrive to our problem - we are not able to install our middleware because:
--> Running transaction check
--> Processing Dependency: python-daemon for package: apel-ssm
--> Running transaction check
---> Package python-daemon.noarch 0:1.5.2-3.el5 set to be updated
--> Processing Dependency: python-lockfile for package: python-daemon
--> Finished Dependency Resolution
python-daemon-1.5.2-3.el5.noarch from epel has depsolving problems
--> Missing Dependency: python-lockfile is needed by package python-daemon-1.5.2-3.el5.noarch (epel)
Our packages were not changed or build latelly, and even if they were we couldn't see the issue as the dependecy is on python-daemon and it is only at runtime.