On Dec 13, 2007 7:30 AM, Alexander Baldeck <kth5@archlinuxppc.org> wrote:
Aaron Griffin wrote:
On Dec 12, 2007 11:22 PM, Jason Chu <jason@archlinux.org> wrote:
Are you sure it's the db file? I would have pointed at the thing that tells updatesync-many that packages are ready to be updated: cvs and tags.
You think someone may have accidentally untagged all of core? I'm not sure what you're trying to say here.
I reconstructed the commands I ran for uploading the package. It turns out I accidentally uploaded the package to ~/staging/core64/add/add/*.pkg.tar.gz. This was probably the cause, sorry for only reporting this now.
Weird. I had a similar issue one time where the dir didn't exist (/add) so when I uploaded it, it was uploaded as a _file_ named 'add'. This is yet-another-craptastic-reason-we-need-new-db-scripts, eh?