Opened 14 months ago
Last modified 9 months ago
#18600 new bug
Failed full-sync/update leaves behind duplicated "transaction-n" folders/content — at Initial Version
Reported by: | bipolar | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Servers/package_daemon | Version: | R1/beta4 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
Situation:
Ran pkgman full
. Had to Ctrl-C due to stalled downloads. administrative/transaction-3
ended up with 66 packages (150 MB).
Ran pkgman full
again, it downloaded all needed packages under administrative/transaction-4
dir,
but failed to apply changes due to, this time, #15068.
Ran pkgman full
again. Got the same failure, but now I have administrative/transaction-5
with the same 163 packages (around 316 MB total) that are present under transaction-1
As in... all the content was duplicated on the new folder.
Can repeat the last two steps ad-nauseum or until I get disk full, whichever comes first :-D
Of note, got an activated-packages.tmp
with the same datetime as transaction-5 there too.
transaction-1
and transaction-2
where empty dirs (I've just removed them after the fact).
---
I've seen similar in the past, but couldn't reproduce it before nuking the administrative folder, and rebooting, in order to be able to use pkgman normally again.
This time, I've kept copies of:
- syslog
- activated_packages / activated_packages.tmp
- output of
ls -l1
for/system/packages/
and thetransaction-n
folders.
Before nuking things back to order. Hope that's enough. Let me know if I should attach the 100 KB .zip of all of them, or just specific files.