On Sun, Nov 3, 2013 at 11:01 AM, Anthony G. Basile <bluen...@gentoo.org> wrote: > Getting back to my original post: I want to make the python team aware of > the needs of releng and exercise care in the future when making a commit > where "alarm bells" go off. An email to releng@ or gentoo-dev@ asking "will > this mess up your stuff" would have been sufficient as we then could have > tested. I don't know if any deeper lesson can be learned. I don't expect > anyone to have super cow powers and forsee every eventuality. Don't be > afraid to use the community. >
I think we were rushing to come up with a solution for a problem that really only affected ~arch, and in the process we caused some problems for a few stable or mixed-arch users. It was rushed because we started getting bugs and IRC pings with words like "QA violation" about the original /var/db/pkg sed hack we had employed. I think a little patience by all parties would have helped. As you say, if we had taken the time to ping some people to test it, the situation may have been avoided.
