[arch-dev-public] [signoff] pacman 3.5.0-1
snowmaniscool at gmail.com
Wed Mar 16 17:06:12 EDT 2011
On Wed, Mar 16, 2011 at 5:01 PM, Allan McRae <allan at archlinux.org> wrote:
> On 17/03/11 06:42, Pierre Schmitz wrote:
>> 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 at gmail.com> wrote:
>>>> Multiple signoffs per architecture would be great, as well as any
>>>> observations dealing with the upgrade process. Release notes:
>>>> @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],
>>> 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.
> CheckSpace will not work in choots. Run "df" in there to see why. I never
> got around to documenting that...
Now that you mention it, I recall the numerous disscussions in the
pacman ML. I'll just disable it.
> The warning message is fixed in m git branch. It was too late for a string
> change once I discovered it.
OK. I'll continue to use/test it in the next few days.
>> Isn't CheckSpace disabled by default?
> Yes it is.
More information about the arch-dev-public