From owner-freebsd-stable@FreeBSD.ORG Fri Jan 30 19:53:15 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EDD8106566C; Fri, 30 Jan 2009 19:53:15 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail13.syd.optusnet.com.au (mail13.syd.optusnet.com.au [211.29.132.194]) by mx1.freebsd.org (Postfix) with ESMTP id 2F2128FC12; Fri, 30 Jan 2009 19:53:14 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-216-167.belrs3.nsw.optusnet.com.au [122.106.216.167]) by mail13.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n0UJrC8X027415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 31 Jan 2009 06:53:13 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id n0UJrBpS079121; Sat, 31 Jan 2009 06:53:11 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id n0UJrBob079120; Sat, 31 Jan 2009 06:53:11 +1100 (EST) (envelope-from peter) Date: Sat, 31 Jan 2009 06:53:11 +1100 From: Peter Jeremy To: Robert Noland Message-ID: <20090130195311.GK1755@server.vk2pj.dyndns.org> References: <6B7ABE80-35AB-4C44-B5A4-200E10DCC3AC@airwired.net> <49819BD5.5040709@FreeBSD.org> <1233236412.1779.40.camel@wombat.2hip.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+1TulI7fc0PCHNy3" Content-Disposition: inline In-Reply-To: <1233236412.1779.40.camel@wombat.2hip.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Unhappy Xorg upgrade X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2009 19:53:16 -0000 --+1TulI7fc0PCHNy3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable As a general note, this is the second time in a row that an X.org upgrade broke X for a significant number of people. IMO, this suggests that our approach to X.org upgrades needs significant changes (see below). X11 is a critical component for anyone who is using FreeBSD as a desktop and having upgrades fail or come with significant POLA violations and regressions for significant numbers of people is not acceptable. On 2009-Jan-29 08:40:11 -0500, Robert Noland wrote: >I've had patches available for probably a couple of months now posted to >freebsd-x11@. For the few people who tested it, I had no real issues >reported. I didn't recall seeing any reference to patches so I went looking. All I could find is a couple of references to a patchset existing buried inside threads discussing specific problems with X. The majority of people who didn't have those specific problems probably skipped the thread and never saw that a patchset was available. When the X.org 7.0 upgrade was planned, a heads-up went out on a number of mailing lists, together with a pointer to the patchset and upgrade instructions and the upgrade did not proceed until both a reasonable number of people reported success and reported problems had been ironed out. Given the ongoing problems with code provided by X.org, I suggest that this approach needs to be followed for every future release of X.org until (if) the X.org Project demonstrates that they can provide release-quality code. > This update also brings in support for a >lot of people who are running newer hardware. And breaks support for lots of people who used to have functional X servers. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --+1TulI7fc0PCHNy3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmDWqcACgkQ/opHv/APuIdisQCgogeNZ8aXPDJ3gcZ/23Gyp/CV bmsAn0efyI9cS6TWGFkofoYh6oFmtc5l =i2p0 -----END PGP SIGNATURE----- --+1TulI7fc0PCHNy3--