[arch-releng] pacman.conf.{i686,x86_64} ignored by archiso?

Gerardo Exequiel Pozzi vmlinuz386 at yahoo.com.ar
Fri Apr 6 11:41:35 EDT 2012

On 04/06/2012 12:12 PM, Dieter Plaetinck wrote:
> On Fri, 06 Apr 2012 11:48:27 -0300
> Gerardo Exequiel Pozzi<vmlinuz386 at yahoo.com.ar>  wrote:
>> On 04/06/2012 11:24 AM, Dieter Plaetinck wrote:
>>> in the releng env
>>> (http://projects.archlinux.org/users/dieter/releng.git/tree/) it seems the
>>> pacman.conf.{i686,x86_64} files are now being ignored. (i enabled testing in there but it's not used)
>>> Frankly I don't even know/remember how this ever worked, I can't find a reference to these files anywhere.
>>> How does one control which pacman.conf archiso must use during building of the arch environment it puts on the isos?
>>> Dieter
>> I do not know about how these scripts works, the only thing that I can
>> say is about archiso:
>> build.sh (wrapper to mkarchiso) does not have a parameter to set a
>> pacman.conf, so mkarchiso by default will use /etc/pacman.conf.
> has this always been like this?
Yes, never used neither in the age of Makefile instead of build.sh. At 
some point we used a local copy of pacman.conf in overlay (unmodified 
from pacman package when mkarchroot does not support NOCOPY)
>> Can you point me where is supposed to be used these files in
>> releng-scripts? I can not found any references in the tree.
> exactly, that's what I said.  I don't know where these files are ever used. They should be used when building the iso's.
Weird. sure?

But think that these files are never used, because:

They are out-of-date (compared to newer pacman.conf) -> There are no 
"SigLevel" -> Default "SigLevel" is used, that is "Optional TrustedOnly" 
by pacman-4 -> without manual interaction pacman will not work. -> no ISOs.

But we have ISOs all times :) Or I am missing something?

Gerardo Exequiel Pozzi
\cos^2\alpha + \sin^2\alpha = 1

More information about the arch-releng mailing list