[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#220675: xserver-common: Providing requested info

On Tue, Jun 08, 2004 at 12:04:09AM -0400, Adam Aube wrote:
> $ export DEBIAN_FRONTEND=readline
> $ sudo dpkg-reconfigure xserver-common
> Password:
> xserver-common config note: Linux kernel > 2.5 detected; using 0 as 
> default nice value
> xserver-common config note: setting xserver-common/xwrapper/allowed_users
>    from configuration file
> xserver-common config note: setting xserver-common/xwrapper/nice_value
>    from configuration file
> Configuring xserver-common
> xserver-common postinst note: not updating /etc/X11/Xwrapper.config; no
>    stored checksum available
> The output from the console commands was edited for formatting only; no 
> content was changed. A cat of /etc/X11/Xwrapper.config confirms the file 
> has not been changed.

Right.  The package is working precisely as documented, both in the
Debian X FAQ[1] and the NEWS.Debian[2] file.

No stored checksum was available, so the script deduced that you were
managing the /etc/X11/Xwrapper.config file "manually".

xfree86 (4.2.1-11) unstable; urgency=medium

  * The following configuration files use a new, MD5-checksum-based method of
    - /etc/X11/X
    - /etc/X11/XF86Config-4
    - /etc/X11/Xwrapper.config

    This new method attempts to detect changes to these files, and if they are
    modified by the user, the files will be ignored by the packaging system
    henceforth.  The debconf region markers (e.g. "### BEGIN DEBCONF SECTION")
    formerly used in Xwrapper.config and XF86Config-4 are no longer used, are
    disregarded if present, and will not be newly written.

    The debconf templates in the xserver-common, xserver-xfree86, and
    xserver-xfree86-dbg packages (the latter shares all of its templates with
    xserver-xfree86) having to do with whether or not files on the disk should
    be overwritten have been removed, and are unregistered in the new
    packages' pre-installation scripts.

    In the event that you have customized these configuration files, and have
    neglected both to correct debconf's notion of whether it should manage
    those files, and (in the case of Xwrapper.config and XF86Config-4) have
    not removed the "debconf region markers" before upgrading to xfree86
    4.2.1-10 or later, backups are made and stored in the same directory, with
    the suffix ".dpkg-old".

    See the Debian X FAQ at <http://people.debian.org/~branden/xsf/FAQ> or in
    the file /usr/share/doc/xfree86-common/FAQ.gz after this upgrade is
    complete for more information on the Debian XFree86 packages' new method
    of handling these configuration files.

 -- Branden Robinson <branden@debian.org>  Sun, 24 Aug 2003 15:07:11 -0500

A future version of the XFree86 packages will exit the configuration
script *before* asking any questions if it can determine that it won't
be able to modify any files.  Fundamentally, however, the package is
working as designed.

[1] file:///usr/share/doc/xfree86-common/FAQ.gz
[2] file:///usr/share/doc/xserver-common/NEWS.Debian.gz

G. Branden Robinson                |    No executive devotes much effort to
Debian GNU/Linux                   |    proving himself wrong.
branden@debian.org                 |    -- Laurence J. Peter
http://people.debian.org/~branden/ |

Attachment: signature.asc
Description: Digital signature

Reply to: