On Wed, 16 Mar 2011 16:31:07 -0400, Eric Bélanger wrote:
On Wed, Mar 16, 2011 at 2:46 PM, Dan McGee <dpmcgee@gmail.com> wrote:
Multiple signoffs per architecture would be great, as well as any observations dealing with the upgrade process. Release notes: http://projects.archlinux.org/pacman.git/tree/NEWS
@Everyone for FYI, Allan for suggestions:
13:39 < bash`> error: failed to commit transaction (conflicting files) 13:39 < bash`> pacman: /usr/bin/pactree exists in filesystem 13:39 < bash`> for example :P 13:39 < bash`> pacman-contrib conflicts 13:39 < toofishes> yeah 13:39 < toofishes> just rm that file for now and continue...good catch
Anything we can do here to make this suck less? Unless on -S vs -U it gets pulled into the transaction so things won't conflict, but we'd have to rebuild it at the same time and get it in [community-testing], right?
-Dan
I just noticed that the new CheckSpace option has some issues in chroot when I update the chroot with "mkarchroot -u". If I explicitely chroot in the chroot and run pacman -Syu there it works. The error message is below (ignore the missing repo warnings). I also suppose the warning messages should be on seperate lines.
Isn't CheckSpace disabled by default? -- Pierre Schmitz, https://users.archlinux.de/~pierre