On Thu, 2009-05-07 at 18:39 -0400, Josh Rickmar wrote: > On Fri, 8 May 2009, Dmitry Marakasov wrote: > > > * Josh Rickmar (joshua_rick...@eumx.net) wrote: > > > > That's quite complicated problem actually - xcb-util update has > > broken awesome; we could update awesome to 3.3-rc1, but it requires > > startup-notification 0.10 (which likely requires new xcb-util as > > well). > > > > Thus we'll likely have to wait for s-n 0.10 and consider awesome > > broken for now. Meanwhile, awesome users are recommended to not > > upgrade from/downgrade to xcb-util 0.3.3. > > > > This is really our fault as there should've been more testing and > > coordination with this update. > > > > > > OK. I've known about this break for quite some time now as there have > been many Linux users who had this same problem. In case of something > like this in the future, should I send a message to the maintainer > telling him/her about the potential break?
Sending a HEADS UP message to the maintainer if you are aware of an issue would be a good courtesy and hopefully minimize any breakage. A short delay for a maintainer to address the issue is reasonable, but that is a slippery slope. I say give a reasonable amount of time for the breakage to be addressed (where the definition of reasonable is open to interpretation). If it isn't addressed, please move forward and commit. robert. > Also, to anyone who hasn't updated their xcb-util port yet, here's what > I did to prevent tools like portmaster from installing the newer > version: > > # touch /var/db/pkg/xcb-util-0.3.3/+IGNOREME > > Now in portmaster, I get the following message when using -a to update > all my ports: > > ===>>> Launching child to update xcb-util-0.3.3 to xcb-util-0.3.4 > > ===>>> xcb-util-0.3.3 has an +IGNOREME file > > ===>>> Update anyway? [n] -- Robert Noland <rnol...@freebsd.org> FreeBSD
signature.asc
Description: This is a digitally signed message part