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

Bug#504025: marked as done (apt: Informative messages should display after configuration of all packages)

Your message dated Fri, 31 Oct 2008 06:59:30 +0100
with message-id <20081031055930.GM4145@mykerinos.kheops.frmug.org>
and subject line Re: Bug#504025: apt: Informative messages should display after configuration of all packages
has caused the Debian Bug report #504025,
regarding apt: Informative messages should display after configuration of all packages
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
504025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504025
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 0.7.14+b1
Severity: wishlist

When updating a lot of packages or when doing a dist-upgrade, a user may 
not sit in front of the screen for the hole time. 
When configuring packages, apt should ask for all information needed for 
package configuration prior to the actual configuration right at the 
beginning of the configuration process and postpone all informative 
messages to the very end of the configuration process.
So questions like "which locale should i set for keyboard?" or "shall 
libc6 restart following services..."  together at 
the beginning and all messages like "you have to restart gdm for changes 
to take effect" at the very end.

-- Package-specific info:

-- (no /etc/apt/preferences present) --


-- (/etc/apt/sources.list present, but not submitted) --


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages apt depends on:
ii  debian-archive-keyring   2008.04.16+nmu1 GnuPG archive keys of the Debian a
ii  libc6                    2.7-14          GNU C Library: Shared libraries
ii  libgcc1                  1:4.3.2-1       GCC support library
ii  libstdc++6               4.3.2-1         The GNU Standard C++ Library v3

apt recommends no packages.

Versions of packages apt suggests:
pn  apt-doc                <none>            (no description available)
ii  aptitude               0.4.11.10-1lenny1 terminal-based package manager
ii  bzip2                  1.0.5-1           high-quality block-sorting file co
ii  dpkg-dev               1.14.22           Debian package development tools
ii  lzma                   4.43-14           Compression method of 7z format in
ii  synaptic               0.62.1            Graphical package manager

-- no debconf information

--- End Message ---
--- Begin Message --- 
Quoting Daniel Gasser (gasser@websource.ch):
> Package: apt
> Version: 0.7.14+b1
> Severity: wishlist
> 
> When updating a lot of packages or when doing a dist-upgrade, a user may 
> not sit in front of the screen for the hole time. 
> When configuring packages, apt should ask for all information needed for 
> package configuration prior to the actual configuration right at the 
> beginning of the configuration process and postpone all informative 
> messages to the very end of the configuration process.
> So questions like "which locale should i set for keyboard?" or "shall 
> libc6 restart following services..."  together at 
> the beginning and all messages like "you have to restart gdm for changes 
> to take effect" at the very end.


This has IMHO nothing to do with apt.

*If packages use debconf properly*, they should use the "high"
priority for important-enough user prompting.....and only do prompting
in their *config* script.

If this is respected:
- very few prompting should occur in the configure step
- this should happen fairly early in the installation process

"grouping" questions is a non-sense. The debconf promprint is part of
the logic of each package configuration scripts. For instance, most
often, the debconf questions get their default values from the
package's configuration files, through code that has been inserted by
the package maintainer in the package config script.


For all these reasons, I think this request is mostly useless and
impossible.

If some packages prompt at wrong places (for instance in their
postinst script) at with inappropriate priority (for instance, an
informational note displayed at critical priority), please file bugs
against these packages. Do not blame apt...:)

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: