qapt-deb-installer's Status and Details misleading and confusing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QApt |
New
|
Medium
|
|||
qapt (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Here is how to reproduce this bug:
* Download http://
This is a small archive that contains a set of test, empty, Debian package files along with their source.
(run ./build to rebuild them)
* Assuming you have a 64-bit system, run the following command
but ***** DO NOT START THE INSTALL! *****
(if you have a 32-bit system, exchange i386 and amd64 everywhere)
qapt-
The testrd-python-any package has a single 'python:any' dependency which should already be satisfied given that the system already has 'python:amd64' installed. Still qapt-deb-installer displays the following Status line:
Status: Requires the installation of 173 additional packages
What this does not say is that it also wants to remove dozens of packages among which critical ones such as python, unity, ubuntu-desktop, gconf2, gnome-terminal, gksu, gdebi-core, gnome-packagekit, software-center, etc.
The Details button will show a list of the impacted packages but that list is not sorted alphabetically which makes it hard to figure out if a given package is going to be removed.
This issue can be reproduced with the python-gtk2 test packages.
So to summarize:
* The Status should warn about package removal.
* The Details list should sort the package names alphabetically.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: qapt-deb-installer 2.0.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Wed Jul 24 15:55:39 2013
InstallationDate: Installed on 2013-04-29 (86 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
SourcePackage: qapt
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in qapt: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Hi there!
Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https:/ /bugs.kde. org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.
Thanks!