Issue #335 has been updated by lukeshu.
Target version set to don't break and confuse parabolers % Done changed from 0 to 100 TL;DR: Wait until I push 20120522 later today, and run `librechroot clean-repo` to fix your chroot, or delete it and recreate it. I've just fixed it in git. I'll push 20120522 by the end of the day (more bugs to squash!). I was about to explain why this was confusing because the fix is to run `pacman -Sy` after adding [repo], but before running pacman again, but that it does this! It turns out that `pacman -Sy` was failing because /repo/repo.db didn't exist yet. I've added creating an empty repo.db to the create action. `librechroot clean-repo` will also "fix" a chroot because it rm's the file and re-creates it. I've just added `mkdir /repo` to it for the case that the directory doesn't exist. ---------------------------------------- Bug #335: pacman can't find [repo] database file https://labs.parabola.nu/issues/335 Author: alfplayer Status: open Priority: bug Assignee: Category: Target version: don't break and confuse parabolers After librechroot make, libremakepkg forces enabling [repo] in pacman.conf, and pacman fails because it can't find the database file for [repo]. libretools version: libre-testing/libretools 20130514-1 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://labs.parabola.nu/my/account _______________________________________________ Dev mailing list [email protected] https://lists.parabolagnulinux.org/mailman/listinfo/dev
