Thanks for pointing that out, Sebastian -- I had the two states muddled.
With help from Michael, I've now corrected the specification. "Some
software is not installed correctly, and may not run properly. You need
to authenticate to repair the installation." Is that reasonable?

** Description changed:

- Binary package hint: software-center
- 
  Ubuntu Software Center 2.1.18, Ubuntu Maverick
+ Ubuntu Software Center 3.0.5, Ubuntu 10.10
  
  Based on test case sc-017 <https://wiki.ubuntu.com/SoftwareCenter
  #broken-catalog>:
  
  1. sudo apt-get install 4g8 && sudo dpkg --force-depends -r libnet1
  2. Launch Ubuntu Software Center.
  
- What happens: An alert appears, "Items cannot be installed or removed
- until the package catalog is repaired. Do you want to repair it now?"
- "Once Update Manager has finished the repairs, you can close it and
- return to the store."
+ (When finished testing, reset if necessary with "sudo apt-get remove 4g8
+ libnet1".)
+ 
+ What happens:
+ 2. An alert appears, "Items cannot be installed or removed until the package 
catalog is repaired. Do you want to repair it now?" "Once Update Manager has 
finished the repairs, you can close it and return to the store."
  
  Ubuntu Software Center now triggers the repair itself, so this message
  is out of date.
  
- What should happen: An alert should appear with the message "The
- software catalog needs rebuilding. Once you authenticate, it will
- rebuild automatically."
+ What should happen:
+ 2. USC should launch as normal, but there should be a /!\ icon next to 
“Installed Software”. Clicking the icon should produce a PolicyKit alert: "Some 
software is not installed correctly, and may not run properly. You need to 
authenticate to repair the installation."
  
- This could be a separate alert from the authentication alert, but that
- would result in two alerts in a row, which is unpleasant.
+ That text could be in a separate alert from the authentication alert,
+ but that would result in two alerts in a row, which is unpleasant.
  
  So, unless there is a good reason that you would *not* want to fix the
  apt cache (and therefore a reason we shouldn't take advantage of cached
- PolicyKit privileges to do it), the alert that presents this message
+ PolicyKit privileges to do it), the alert that presents that message
  should be the actual PolicyKit alert. That way we get one alert rather
  than two.
  
  That in turn means that there would need to be a specific aptdaemon
  PolicyKit privilege for this task.
+ 
+ <https://wiki.ubuntu.com/SoftwareCenter#broken-cache>

** Changed in: aptdaemon
       Status: Opinion => New

** Description changed:

  Ubuntu Software Center 2.1.18, Ubuntu Maverick
  Ubuntu Software Center 3.0.5, Ubuntu 10.10
  
  Based on test case sc-017 <https://wiki.ubuntu.com/SoftwareCenter
- #broken-catalog>:
+ #broken-cache>:
  
  1. sudo apt-get install 4g8 && sudo dpkg --force-depends -r libnet1
  2. Launch Ubuntu Software Center.
  
  (When finished testing, reset if necessary with "sudo apt-get remove 4g8
  libnet1".)
  
  What happens:
  2. An alert appears, "Items cannot be installed or removed until the package 
catalog is repaired. Do you want to repair it now?" "Once Update Manager has 
finished the repairs, you can close it and return to the store."
  
  Ubuntu Software Center now triggers the repair itself, so this message
  is out of date.
  
  What should happen:
  2. USC should launch as normal, but there should be a /!\ icon next to 
“Installed Software”. Clicking the icon should produce a PolicyKit alert: "Some 
software is not installed correctly, and may not run properly. You need to 
authenticate to repair the installation."
  
  That text could be in a separate alert from the authentication alert,
  but that would result in two alerts in a row, which is unpleasant.
  
  So, unless there is a good reason that you would *not* want to fix the
  apt cache (and therefore a reason we shouldn't take advantage of cached
  PolicyKit privileges to do it), the alert that presents that message
  should be the actual PolicyKit alert. That way we get one alert rather
  than two.
  
  That in turn means that there would need to be a specific aptdaemon
  PolicyKit privilege for this task.
  
  <https://wiki.ubuntu.com/SoftwareCenter#broken-cache>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/635101

Title:
  Broken apt cache error message is out of date

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to