Here is another example where maintainers need to coordinate more and pay attention. https://admin.fedoraproject.org/updates/F9/FEDORA-2008-10000 (rpcbind-0.1.7-1.fc9) went into Fedora 9 updates testing on 11-22. On the 25th bodhi feedback showed that this requires selinux changes. https://admin.fedoraproject.org/updates/F9/FEDORA-2008-11122 (selinux-policy-3.3.1-115.fc9) went into Fedora 9 updates testing on 12-10. This was the build to fix rpcbind. On 12-10 rpcbind was submitted for stable. On the same day, bodhi feedback requested that this update not go out until the matching selinux-policy went out to stable. On 12-11 rpcbind went into stable. selinux-policy remained in -testing, until 12-15 (today) when it was obsoleted by a newer policy, which is also going into -testing. This means our F9 users on a supposedly stable release will have non-functional rpcbind (and dependent software) until at least sometime late tomorrow (today's push is still going, won't start another one for at least another 15 hours. This could have easily been solved if the maintainers for rpcbind and selinux-policy worked together to ensure that the updates went to the same places at the same time. In the future, please do be aware if your update requires fixes in something else, that everything goes together in lock step. mgrepl, can you request the latest -policy go to stable so that F9 users can get the proper fixes as soon as possible? -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
