Package: aptitude
Version: 0.4.10-1
Severity: critical
Justification: breaks unrelated software


The "markauto" and "unmarkauto" commands work in reverse as specified in
the manual, and in reverse as common sense would say they should.

I have a manually installed package, libdirectfb-1.0-0:

$ aptitude show libdirectfb-1.0-0 | egrep '^(Automatically|State)'
State: installed
Automatically installed: no

I want this package to be marked as "automatically installed".  So I do
a "markauto":

$ sudo aptitude markauto libdirectfb-1.0-0 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Reading extended state information       
Initializing package states... Done
Reading task descriptions... Done  
Building tag database... Done    
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 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       
Reading state information... Done
Reading extended state information      
Initializing package states... Done
Reading task descriptions... Done  
Building tag database... Done    

OK.  It didn't tell me it actually carried out any useful work (even
though it emitted a lot of noise), so let's assume it worked.  Now I
query the package state again:

$ aptitude show libdirectfb-1.0-0 | egrep '^(Automatically|State)'
State: installed
Automatically installed: no

Wow.  Humm.  Maybe it didn't work after all.  Let's try the other
command:

$ sudo aptitude unmarkauto libdirectfb-1.0-0 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Reading extended state information       
Initializing package states... Done
Reading task descriptions... Done  
Building tag database... Done    
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 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       
Reading state information... Done
Reading extended state information      
Initializing package states... Done
Reading task descriptions... Done  
Building tag database... Done    

Ok, it still doesn't say it did anything (Boy, it is really noisy.)
Let's check the state anyway:

$ aptitude show libdirectfb-1.0-0 | egrep '^(Automatically|State)'
State: installed
Automatically installed: yes

WOW!  Now that's broken!  Let's try to put it in manual mode again, with
the "markauto" command:

$ sudo aptitude markauto libdirectfb-1.0-0 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Reading extended state information       
Initializing package states... Done
Reading task descriptions... Done  
Building tag database... Done    
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 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       
Reading state information... Done
Reading extended state information      
Initializing package states... Done
Reading task descriptions... Done  
Building tag database... Done    

OK, I got more useless noise, now does it continue to fail?

$ aptitude show libdirectfb-1.0-0 | egrep '^(Automatically|State)'
State: installed
Automatically installed: no

Why, yes, it failed to do the thing I told it to do, but it correctly
did exactly the opposite!

Guys.  Come on.  Does anyone actually _test_ this stuff?

I'm guessing this bug is a "duplicate" of #330131 and #372184.  It is
_still_ broken in 0.4.10 though.  I'm marking the bug as critical
because of the reports in those other bugs.

Thanks for your work on aptitude.  It is awesome.  I only wish that devs
would put more attention to simple things such as this one.


-- Package-specific info:
Terminal: xterm
$DISPLAY is set.

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

Kernel: Linux 2.6.21-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages aptitude depends on:
ii  apt [libapt-pkg-libc6.6 0.7.9            Advanced front-end for dpkg
ii  libc6                   2.7-6            GNU C Library: Shared libraries
ii  libcwidget1             0.5.6.1-3        high-level terminal interface libr
ii  libgcc1                 1:4.3-20080116-1 GCC support library
ii  libncursesw5            5.6+20080119-1   Shared libraries for terminal hand
ii  libsigc++-2.0-0c2a      2.0.17-2         type-safe Signal Framework for C++
ii  libstdc++6              4.3-20080116-1   The GNU Standard C++ Library v3

Versions of packages aptitude recommends:
pn  aptitude-doc-en | aptitude-do <none>     (no description available)
ii  libparse-debianchangelog-perl 1.1.1-2    parse Debian changelogs and output

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to