Site Navigation:
Welcome to bodhi v0.9.15

Latest Updates

UpdateReleaseStatusTypeRequestKarmaSubmitterAge
python-pbr-0.10.8-1.fc21Fedora 21pendingapevec3 minutes
python-pbr-0.10.8-1.fc22Fedora 22pendingapevec3 minutes
python-pbr-0.10.8-1.el7Fedora EPEL 7pendingapevec4 minutes
rubygem-domain_name-0.5.24-1.fc20Fedora 20pendingmtasaka3 hours
yakuake-2.9.9-8.fc21Fedora 21pendings4504kr3 hours
rubygem-domain_name-0.5.24-1.fc21Fedora 21pendingmtasaka3 hours
rubygem-domain_name-0.5.24-1.fc22Fedora 22pendingmtasaka3 hours
yakuake-2.9.9-8.fc22Fedora 22pendings4504kr3 hours
prosody-0.9.8-1.el6Fedora EPEL 6pendingrobert5 hours
coin-or-Ipopt-3.12.3-1.fc21Fedora 21pendingsagitter5 hours

Latest Comments [more]

UpdateCommentFromKarma
libspf2-1.2.10-5.20150405gitd57d79fd.fc21stevej
libspf2-1.2.10-5.20150405gitd57d79fd.fc20stevej
libspf2-1.2.10-5.20150405gitd57d79fd.el7stevej
libspf2-1.2.10-5.20150405gitd57d79fd.el6stevej
libspf2-1.2.10-5.20150405gitd57d79fd.el5stevej
libspf2-1.2.10-5.20150405gitd57d79fd.fc22stevej
selinux-policy-3.13.1-122.fc22jbastian
libinput-0.13.0-6.fc22jbastian
firefox-37.0.1-1.fc20Why on Earth does a critical path security update potentially have to stay in testing for 14 days? Shouldn't this policy be revised? The currently available version of Firefox in Fedora 20 has a CRITICAL vulnerability which allows a man-in-the-middle attacker to impersonate ANY HTTPS website. In this context, shouldn't security concerns win out over the worry that there MIGHT be some regression? We already know there's a serious problem in the current package, so why do we have to wait 14 days just because there MIGHT be some problem in the new package?Anonymous Tester
virt-manager-1.1.0-6.git310f6527.fc21Cannot create a new VM: Error: 'vmmCreate' object has no attribute 'capsinfo'nerijus