Bug 153684 - Installation always reports "could not commit changes - Adept Manager"
Summary: Installation always reports "could not commit changes - Adept Manager"
Status: RESOLVED FIXED
Alias: None
Product: adept
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Peter Rockai
URL:
Keywords:
: 156433 157703 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-12-08 16:50 UTC by Martin Schoch
Modified: 2008-03-09 14:56 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Schoch 2007-12-08 16:50:59 UTC
Version:           2.1 Cruiser (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages
Compiler:          gcc 4.1 
OS:                Linux

On installation of new packages, there is always an error message.

Title:  "could not commit changes - Adept Manager". 

Body: "There was an error commiting (sic!) changes. Possibly there was a problem downloading some packages or the commit would break packages." 

But usually, the packages are shown as installed afterwards and appear to work. 

How to reproduce: Install any package that was not installed before.
Expected behaviour: 
a) Only display error message if installation failed
b) When success/failure of installation cannot be determined with certainty, display a message that describes the problem with more detail.
c) (least importantly) fix the typo in "committing" ;-)
Comment 1 Andreas Troschka 2008-03-05 17:32:02 UTC
This happens in situations where the installation process couldn't be terminated for different reasons (interactivity req. from installer scripts, server not reacheable, preexistent files with wrong access permissions, etc.).

> sudo dpkg --configure -a
> sudo apt-get -update

will mostly solve the problem.

Comment 2 Peter Rockai 2008-03-09 14:40:12 UTC
These issues are now handled much better in 3.0 alpha codebase, which means that the reported issues should disappear in next release. The fix mostly consists of addressing a) and b) and removing the offending dialog altogether wrt. c). The error messages have been redone, hopefully with fewer typos of this kind :-).
Comment 3 Peter Rockai 2008-03-09 14:53:28 UTC
*** Bug 156433 has been marked as a duplicate of this bug. ***
Comment 4 Peter Rockai 2008-03-09 14:56:33 UTC
*** Bug 157703 has been marked as a duplicate of this bug. ***