It wasn't me who fixed it. :-) The text needs to be updated, but that's
bug 635101 (and bug 635138).
--
Can't fix broken packages from within USC
https://bugs.launchpad.net/bugs/442262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hi, Thanks, MPT. I had a broken dependency today in my Maverick install
and discovered that you had implemented this. Now the USC helpfully
gives a dialog to the user asking if it should repair or not.
I'm marking as fix released. Thank you!
** Changed in: software-center (Ubuntu)
Status:
** Changed in: aptdaemon
Status: New => Opinion
--
Can't fix broken packages from within USC
https://bugs.launchpad.net/bugs/442262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
Thanks for your answers. I'll get to this in a few weeks.
--
Can't fix broken packages from within USC
https://bugs.launchpad.net/bugs/442262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
(Sorry for the overlapping previous comments today, but I process my bug
mail sequentially, mpt :)
1. In the past this error message covered to different errors:
Unfinished previous installations and a broken dependency tree.
The first one will be the result of a faiulre in a post installation
sc
1) It can be either the user's fault or accidental. A power outage
during installation of software can lead to improper configuration and
will bring down the entire apt system. The remedy for that situation can
usually be resoved via 'sudo apt-get -f install' or 'sudo dpkg
reconfigure'. Synaptic al
The next step is for me to design how to present the repair option, so I
have a few questions.
1. When this happens, whose fault is it? Can a power cut during installation
cause a broken package, for example? Can a badly-coded package cause it? What
other causes are there?
1a. If a badly-coded p
** Also affects: aptdaemon
Importance: Undecided
Status: New
--
Can't fix broken packages from within USC
https://bugs.launchpad.net/bugs/442262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
** Summary changed:
- Software Center needs to be able to fix Broken Packages
+ Can't fix broken packages from within USC
** Description changed:
- ***PLEASE NOTE THE BELOW PARAGRAPH***
+ *** DO NOT USE THIS BUG REPORT AS A SUPPORT FORUM. ***
+ Please use http://ubuntuforums.org/ for any problem
