Learn more about these different git repos.
Other Git URLs
I built caddy-1.0.5-1.el7 for epel7 and submitted it in bodhi. I planned to test it once it was in the testing repo, but forgot and it was pushed to stable. Unfortunately the update is broken and the command core dumps immediately.
ASAP to minimize the number of users that apply this broken update.
I'm working through the options to resolve this long term. I'll be sending a summary of these to the epel-devel list soon. One of the options will be to retire caddy from epel7 outright. If I take that action, untagging this build will no longer be necessary, but I don't have a date for that or even know for sure that is the outcome. It would be best to untag this build in the interim.
EL7 users installing or updating to a broken caddy package.
Metadata Update from @jnsamyak: - Issue tagged with: low-gain, low-trouble, ops
Don't like doing this, but I understand this is a exceptional case. ;(
Anyhow, untagged it, the next time an epel7 update goes out it will disappear from the repo and the caddy-1.0.3-1.el7 version will be there.
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Metadata Update from @kevin: - Issue assigned to kevin
After consulting with upstream, I decided that retirement is the least bad choice.
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/JZRLEWOCX5QX3XZ7INLUZIB7LPAMDUZC/
Login to comment on this ticket.