Your message dated Tue, 8 Jan 2013 23:31:05 +0100
with message-id <[email protected]>
and subject line Re: Bug#333546: aptitude: ignores user request to upgrade a 
package without explanation
has caused the Debian Bug report #333546,
regarding aptitude: ignores user request to upgrade a package without 
explanation
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 [email protected]
immediately.)


-- 
333546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=333546
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.2.15.9-6
Severity: normal

aptitude ignores my install request without giving a reason (which would be
that it needs to uninstall argouml)

# aptitude install libi18n-java
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
The following packages have been kept back:
  libi18n-java libnspr4 libnss3 mozilla mozilla-browser
  mozilla-dom-inspector mozilla-mailnews mozilla-psm
0 packages upgraded, 0 newly installed, 0 to remove and 8 not
upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Writing extended state information... Done
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
# apt-get install libi18n-java
Reading package lists... Done
Building dependency tree... Done
The following packages will be REMOVED:
  argouml
The following packages will be upgraded:
  libi18n-java
1 upgraded, 0 newly installed, 1 to remove and 7 not upgraded.
Need to get 110kB of archives.
After unpacking 2634kB disk space will be freed.
Do you want to continue [Y/n]?
#

Aptitude should behave like apt-get does in this situation.

libi18n-java:
  Installed: 0.1.2.0.1-1
  Candidate: 0.1.3a-1
  Version table:
     0.1.3a-1 0
        500 http://ftp.de.debian.org unstable/main Packages
 *** 0.1.2.0.1-1 0
        100 /var/lib/dpkg/status
argouml:
  Installed: 0.14-7
  Candidate: 0.14-7
  Version table:
 *** 0.14-7 0
        500 http://ftp.de.debian.org unstable/contrib Packages
        100 /var/lib/dpkg/status
(which has a dependency on libi18n-java (<< 0.1.3) )

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.13-rc4
Locale: LANG=de_DE.UTF-8@euro, LC_CTYPE=de_DE.UTF-8@euro (charmap=UTF-8)

Versions of packages aptitude depends on:
ii  apt [libapt-pkg-libc6.3-6-3.1 0.6.41     Advanced front-end for dpkg
ii  libc6                         2.3.5-6    GNU C Library: Shared libraries an
ii  libgcc1                       1:4.0.2-2  GCC support library
ii  libncurses5                   5.4-9      Shared libraries for terminal hand
ii  libsigc++-1.2-5c2             1.2.5-5    type-safe Signal Framework for C++
ii  libstdc++6                    4.0.2-2    The GNU Standard C++ Library v3

Versions of packages aptitude recommends:
pn  aptitude-doc-en | aptitude-do <none>     (no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 0.6.8.2-1

Hi Erich,

Erich Schubert wrote:
> Hello Daniel,
> >   Could you check whether 0.3.4 does the same thing?  At least one bug
> > like this has been fixed in that branch.
> 
> 0.3.4 does basically the same thing - except that it gives a reason. ;-)
> So this is a lot better; in fact the behaviour makes more sense than
> that of apt-get now: argouml is the only reason why libi18n-java is
> actually installed; so if it would upgrade libi18n-java by uninstalling
> argouml, it would become unused and thus uninstalled, too... ;-)
> 
> [...]
> The following packages are BROKEN:
>   argouml
> The following packages are unused and will be REMOVED:
>   libi18n-java
> 0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> Need to get 0B of archives. After unpacking 81.9kB will be freed.
> The following packages have unmet dependencies:
>   argouml: Depends: libi18n-java (< 0.1.3) but it is not installable
> Resolving dependencies...
> The following actions will resolve these dependencies:
> 
> Keep the following packages at their current version:
> libi18n-java [0.1.2.0.1-1 (now)]
> 
> Score is 61
> 
> Accept this solution? [Y/n/q/?]
> The following packages have been kept back:
>   libi18n-java
> 0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
> Need to get 0B of archives. After unpacking 0B will be used.
> Do you want to continue? [Y/n/?]
> [...]
> 
> The last [Y/n/?] question doesn't make sense, though:
> basically it's a "I'm going to do nothing [Y/n/?]"

That dialog nowadays looks like this:

| The following actions will resolve these dependencies:
| 
|      Keep the following packages at their current version:
| 1)     python-dnspython [Not Installed]                   

So I think that point is solved, too.

> Also I would suggest the wording "would be BROKEN" at the beginning.

This looks like this nowadays:

| The following NEW packages will be installed:
|   python-dnspython 
| 0 packages upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
| Need to get 119 kB of archives. After unpacking 597 kB will be used.
| The following packages have unmet dependencies:
|  linkchecker : Conflicts: python-dnspython but 1.10.0-1 is to be installed.
| The following actions will resolve these dependencies:
|
|      Remove the following packages:
| 1)     linkchecker                 

I think it's clear enough that the package is not yet broken that way.

> Also a more human-readable reasoning would be nice, but I guess you
> can't do that...

Not sure if that's more human-readable nowadays, but as all the
remaining issues seem to be solved in the meanwhile, I'm closing this
bug report as fixed with the current version of aptitude in testing
and unstable.

The initially reported issue was already solved by Daniel Burrows with
0.3.4.

                Regards, Axel
-- 
 ,''`.  |  Axel Beckert <[email protected]>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-    |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5

--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel

Reply via email to