Your message dated Sat, 28 Jul 2007 07:21:59 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closing bugs dinstall didn't.\
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: aptitude
Version: 0.4.4-4
Severity: normal

Hi,

I seem to remember that previously when some packages were left in a
broken state in an upgrade those packages were shown as
broken/installable (or something) in the aptitude ui. Nowadays even
when the installation leaves packages broken, after I get back to the
UI pressing 'g' simply says "No packages are scheduled to be
installed, removed, or upgraded".

For example, this is what the installation process reported:

------------------------------------------------------------
[...]
Errors were encountered while processing:
 python
 python-dev
 python-gmenu
 gnome-menus
 pykdeextensions
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up python (2.4.4-5) ...
dpkg: error processing python (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of pykdeextensions:
 pykdeextensions depends on python (<< 2.5); however:
  Package python is not configured yet.
 pykdeextensions depends on python (>= 2.4); however:
  Package python is not configured yet.
dpkg: error processing pykdeextensions (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python-dev:
 python-dev depends on python (= 2.4.4-5); however:
  Package python is not configured yet.
dpkg: error processing python-dev (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python-gmenu:
 python-gmenu depends on python (<< 2.6); however:
  Package python is not configured yet.
 python-gmenu depends on python (>= 2.4); however:
  Package python is not configured yet.
dpkg: error processing python-gmenu (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of gnome-menus:
 gnome-menus depends on python (>= 2.3); however:
  Package python is not configured yet.
 gnome-menus depends on python-gmenu (= 2.18.0-2); however:
  Package python-gmenu is not configured yet.
dpkg: error processing gnome-menus (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 python
 pykdeextensions
 python-dev
 python-gmenu
 gnome-menus
------------------------------------------------------------

When I look in the UI, this is what the packages look like:

------------------------------------------------------------
C     python                             2.4.4-5     2.4.4-5
u A   pykdeextensions                    0.4.0-4     0.4.0-4
u     python-dev                         2.4.4-5     2.4.4-5
u A   python-gmenu                       2.18.0-2    2.18.0-2
u A   gnome-menus                        2.18.0-2    2.18.0-2
------------------------------------------------------------

However they are all listed among correctly installed packages and
nothing except the C or u state shows that they haven't been installed
correctly. Also as I said, pressing 'g' just reports nothing to do.

I think the former behavior was definitely more intuitive and correct.

        Sami


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.20.4-grsec-sli
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages aptitude depends on:
ii  apt [libapt-pkg-libc6.3-6-3 0.6.46.4-0.1 Advanced front-end for dpkg
ii  libc6                       2.5-7        GNU C Library: Shared libraries
ii  libgcc1                     1:4.1.2-7    GCC support library
ii  libncursesw5                5.5-5        Shared libraries for terminal hand
ii  libsigc++-2.0-0c2a          2.0.17-2     type-safe Signal Framework for C++
ii  libstdc++6                  4.1.2-7      The GNU Standard C++ Library v3

Versions of packages aptitude recommends:
ii  aptitude-doc-en [aptitude-doc 0.4.4-4    English manual for aptitude, a ter
ii  libparse-debianchangelog-perl 1.0-1      parse Debian changelogs and output

-- no debconf information

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
Version: 0.4.5.1-1

  Apparently dinstall neglected to send a closing message for these
bugs when 0.4.5.1-1 was uploaded.


aptitude (0.4.5.1-1) experimental; urgency=low

  * New upstream version.

  * This version merges in the code I wrote in 2005 to support the
    patch against apt to add removal of automatic patches.  aptitude
    should merge its list of "automatic" packages into the global apt
    list when it's run.

  * aptitude will now let you go ahead when there isn't anything to
    change, but some packages need to be configured. (Closes: #424709)

  * Translation updates:

    - French (Closes: #428585, #428826)
    - Portuguese (Closes: #425779)
    - Vietnamese (Closes: #426976)

  * Use debian/compat instead of DH_COMPAT; switch to debhelper
    compatibility level 5.

 -- Daniel Burrows <[EMAIL PROTECTED]>  Fri, 15 Jun 2007 08:53:06 -0700


  Daniel

--- End Message ---

Reply via email to