Ticket #1905 (accepted defect)
packagekit daemon crashing due to interactive pacakge install?
| Reported by: | peepsalot | Owned by: | tick |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | opkg | Version: | Om2008.8 |
| Severity: | normal | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Estimated Completion (week): | ||
| HasPatchForReview: | no | PatchReviewResult: | |
| Reproducible: |
Description
I tried running pkcon update on my my freerunner.
It displayed many lines of installing packages, then suddenly quit when it got to openmoko-community-repository :
...
installing openmoko-common2-0.1.0+svnr3259-r0 [===============] (74%)
installing openmoko-community-repository-1.0-r0.01[ ] (74%)
The daemon crashed mid-transaction!
I did "killall packagekitd" and tried the upgrade again through opkg.
This time when it got to that same package there was a interactive prompt:
Configuration file '/etc/opkg/Multiverse-feed.conf'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions (if diff is installed)
The default action is to keep your current version.
* Multiverse-feed.conf (Y/I/N/O/D) [default=N] ?
If I remember correctly from some short reading I've done about packagekit: interactive installs are not supported, so I'm guessing that's why it crashed.
Change History
comment:2 Changed 5 years ago by tick
Yes, it shall not ask user. I think you are right.
Pondering how to deal with that.
comment:4 Changed 5 years ago by zecke
- Component changed from unknown to Installer
Putting component back. "Installer" is the closest component we have for packagekit as opkg, assassin and packagekit build a unit responsible for installing packages. If the number of bugs for packagekit increase we can consider creating a new component. :)
