Date: Thu, 07 May 2009 17:47:30 -0500 From: Robert Noland <rnoland@FreeBSD.org> To: Josh Rickmar <joshua_rickmar@eumx.net> Cc: FreeBSD Ports Mailing List <ports@freebsd.org>, Dmitry Marakasov <amdmi3@amdmi3.ru> Subject: Re: xcb-util 0.3.4 breaks awesome Message-ID: <1241736450.1788.18.camel@balrog.2hip.net> In-Reply-To: <alpine.BSF.2.00.0905071831170.17395@FGD135.localdomain> References: <alpine.BSF.2.00.0905062112380.17395@FGD135.localdomain> <20090507220706.GF3811@hades.panopticon> <alpine.BSF.2.00.0905071831170.17395@FGD135.localdomain>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-sl8oT0zom9MYfi/VunrB Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2009-05-07 at 18:39 -0400, Josh Rickmar wrote: > On Fri, 8 May 2009, Dmitry Marakasov wrote: >=20 > > * Josh Rickmar (joshua_rickmar@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. > > > > >=20 > 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: >=20 > # touch /var/db/pkg/xcb-util-0.3.3/+IGNOREME >=20 > Now in portmaster, I get the following message when using -a to update > all my ports: >=20 > =3D=3D=3D>>> Launching child to update xcb-util-0.3.3 to xcb-util-0.3.4 >=20 > =3D=3D=3D>>> xcb-util-0.3.3 has an +IGNOREME file >=20 > =3D=3D=3D>>> Update anyway? [n] --=20 Robert Noland <rnoland@FreeBSD.org> FreeBSD --=-sl8oT0zom9MYfi/VunrB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEABECAAYFAkoDZQIACgkQM4TrQ4qfROMWCwCdHgqUHp25LF1O36ZYibMZbky9 9fcAn3t1ZAaiLCHPuWsbaVq2e41Nb7c4 =uwUr -----END PGP SIGNATURE----- --=-sl8oT0zom9MYfi/VunrB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1241736450.1788.18.camel>