As the email thread +1 to unpushing them.

+! to unpushing them

+1, yeah.

+1 from me

+1 from me as well.
This passed the voting on this weeks EPEL meeting.
I will begin cleaning up these old Bodhi updates, starting with the oldest year.(2011) Since it only has 8 updates, it will be a good testbed to make sure I have my procedures correct.

I have settled on the following process for removing these packages from bodhi update.
1 - Give a -1 karma, with the following comment "Due to the age of this package, it should not be added to EPEL. If you feel this package should still be in EPEL, please rebuilt it and submit another update request."
2 - unpush the update (This removes any packages from the epel-testing repository) (Some packages had already been unpushed)
3 - obsolete the update (This removes it from any bodhi testing and/or pending settings)

I have done all the 2011 and 2012 packages.
I will wait until next week before doing more. See if people notice and/or have issues before moving on to the years with much more old packages.

Sounds good. We should email the lists and I will put up a blog this weekend. I would like to help out on the next set so I know how this is done and can spread the load.

It is all scripted, so there isn't really much load. The hardest part was getting the list in the first place. I was doing some work on bodhi 4.0 code (not released yet), and made a script that lists all the updates open updates. But it seems that my script isn't compatible with bodhi 3.x.

Anyway, with the lists it was just a matter of

cat epel-old-bodhi-updates-2011 | while read line
do
echo "=============================================="
bodhi updates query --alias $line
bodhi updates comment --karma -1 $line "Due to the age of this package, it should not be added to EPEL. If you feel this package should still be in EPEL, please rebuilt it and submit another update request."
bodhi updates request $line unpush
bodhi updates request $line obsolete
echo "=============================================="
done

And I just watched the output to make sure nothing strange happened.

Didn't hear any complaints over the weekend, so I moved forward with the next few years.

I have now cleaned up all the 2013, 2014, and 2015 old bodhi updates for EPEL6 and 7.

When bodhi switched to automatically pushing 2 week old epel updates to stable (several months ago) this was automatically cleaned up for all those updates I hadn't finished.
Closing this issue.