Re: Release Notes should document possible issues with X transition
Hi, * Frans Pop ([EMAIL PROTECTED]) [060416 18:28]: > The most important issue is that /usr/X11R6/bin has been dropped and only > remains as a symlink to /usr/bin. This means it has to be empty at the > time of the upgrade. > The new packages conflict with most packages that used /usr/X11R6/bin, but > maybe not all have been caught. The RN should document how users can > prepare for the upgrade and how they can work their way out of trouble if > a conflict should arise. I added documentation for that into the release notes. > A potential other issue is that paths for fonts and modules have changed > and thus changes in the X configuration file may be needed. Whether this > really is an issue depends on how well conversion of old X11 config files > is supported at the time of the release. Is that still the case? If so, some text from the X-team would be welcome. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Release Notes should document possible issues with X transition
* Andreas Barth ([EMAIL PROTECTED]) [061114 14:35]: > > A potential other issue is that paths for fonts and modules have changed > > and thus changes in the X configuration file may be needed. Whether this > > really is an issue depends on how well conversion of old X11 config files > > is supported at the time of the release. > > Is that still the case? If so, some text from the X-team would be > welcome. 17:17 < aba> jcristau: #362996 17:22 < jcristau> I think the xserver-xorg maintainer script take care of updating the paths when transitioning old XF86Config to xorg.conf 17:24 < aba> ok, so we just consider that irrelevant (except to have an hint to the wiki entry about the transition, which we have anyways) 17:30 < jcristau> I think so, yes So, this is done as well. Thanks. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Release Notes should document possible issues with X transition
On Monday 17 April 2006 09:57, Daniel Stone wrote:
> On Mon, Apr 17, 2006 at 02:28:19AM +0200, Frans Pop wrote:
> > A potential other issue is that paths for fonts and modules have
> > changed and thus changes in the X configuration file may be needed.
> > Whether this really is an issue depends on how well conversion of old
> > X11 config files is supported at the time of the release.
>
> Mangling config files is always a last-resort option: much easier to
> provide the two old font paths (/usr/{X11R6/,}lib/X11/fonts) as
> symlinks to the new.
Note that this bug report is more a reminder that probably something will
need to be documented in the Release Notes than a proposed text. I hope
the XSF will provide a proposed text for the real issues that need
documenting.
I'd suggest to first finish the transition, then thoroughly test the
upgrade path from Sarge and after that come up with a proposed text for
the release notes.
P.S. The bug number is #362996.
pgpoaZiMmy9II.pgp
Description: PGP signature
Re: Release Notes should document possible issues with X transition
On Mon, Apr 17, 2006 at 02:28:19AM +0200, Frans Pop wrote:
> A potential other issue is that paths for fonts and modules have changed
> and thus changes in the X configuration file may be needed. Whether this
> really is an issue depends on how well conversion of old X11 config files
> is supported at the time of the release.
Mangling config files is always a last-resort option: much easier to
provide the two old font paths (/usr/{X11R6/,}lib/X11/fonts) as symlinks
to the new.
signature.asc
Description: Digital signature
Release Notes should document possible issues with X transition
Package: release-notes Severity: important With the release of modular Xorg 7.0 packages, some structural changes have been made that may hit users during upgrade and thus should be documented in the Release Notes. The most important issue is that /usr/X11R6/bin has been dropped and only remains as a symlink to /usr/bin. This means it has to be empty at the time of the upgrade. The new packages conflict with most packages that used /usr/X11R6/bin, but maybe not all have been caught. The RN should document how users can prepare for the upgrade and how they can work their way out of trouble if a conflict should arise. A potential other issue is that paths for fonts and modules have changed and thus changes in the X configuration file may be needed. Whether this really is an issue depends on how well conversion of old X11 config files is supported at the time of the release. pgpuw7b486x3P.pgp Description: PGP signature
