Dear FESCo members
My co-maintainer built http://koji.fedoraproject.org/koji/buildinfo?buildID=156184 for F13. This package breaks the DR17 EFL chain. The reason i asked rel-eng https://fedorahosted.org/rel-eng/ticket/3508 very late (sorry) is i wasn't aware that i could have had it untaged with rel-eng. I was also waiting for the final DR17 and EFL 1.0 release from upstream to get into F13. Sadly upstream still has not released so time is running out slowly for F13. Right now DR17, EFL is broken in F13. I cant update the complete chain to the version embryo has, because two old packages (old maintainer didn't changed it to the replacements) are broken with the .063 release. Upstream wont fix it and i can't do it.
My options are to use epoch or get it untaged with rel-eng. Almost everybody wants me to prevent the use of epoch, so i ask here for help to let rel-eng untag it.
I will be at the next FESCo IRC meeting.
Best regards
I think an Epoch is pretty much the only good solution here, sorry.
Added to 2010-03-16 meeting agenda.
FWIW this is not a packaging problem but a social one. Simon and Thomas are co-maintaining each other's e17 packages and Simon pushed an update of embryo. On the other hand Thomas asked rel-eng and FeSCo for intervention without noticing Simon first. IMO the problems could easily be solved without introducing an epoch if both maintainers just worked together. I don't think this is a FeSCo thing, at least not from a technical POV.
According to Rudolf Kastl it's just a "trivial update" and no new packages are needed. Rudolf has everything running on rawhide and repeatedly offered Thomas his help, but Thomas never provided him any details like build.logs. Instead he just informed me and Simon that he is orphaning all his DR17.
I suggest that Simon and Rudolf work on fixing the broken dependencies instead of introducing an epoch and reverting to a release that is more than 2 years old. If they don't manage to get the update done within the next week (beta freeze), we can decide for an epoch in the next meeting.
Fesco will allow rel-eng to untag this package in this rare case.
Please fix things up.
Login to comment on this ticket.