Pacman: sent interrupt and now thinks its up to date.

Question

Its a little long, so I've pastebin'd it.
http://pastebin.com/m4465efec
So, I understand stuff gets corrupted while downloading.  That's why one always checks the [md5,sha1,sha256]sum of what you are downloading.  But tell me.  Did I hit the interrupt in the wrong place?  I realized this -Syu wasn't going to go well, so I ^C'd out of it.  Did I hose my local database?  How do I get myself out of this one gracefully?
I also thought it strange that it didn't show the progress bar for the extra.db, and also for the latter half of the packages it was downloading.  But according to conky, I was still moving data (albeit, I don't know where from or to.)
Last edited by wriggary (2010-02-15 23:17:22)

Answer 1

Earlier, I had tried that (after I made the pastebin) , and it did the downloading core.db.tar.gz.. without the progress bar, just like -Syu, and also said the local database was up to date.
But I tried it now (about 3 hours since I last tried) And it seemed to properly download the [$repo].db.tar.gz files.  Its offering again to replace klibc, I'll give it a try again.
Is this just some random weirdness while the mirror was syncing?
[edit]
Oh yeah, check line 90 on the pastebin.  I did include an -Syyu.
[/edit]
Last edited by wriggary (2010-02-15 23:10:38)