[arch-general] devtools

Baho Utot baho-utot at columbus.rr.com
Mon Mar 23 16:07:33 EDT 2009


Aaron Griffin wrote:
> On Sat, Mar 21, 2009 at 4:12 PM, Baho Utot <baho-utot at columbus.rr.com> wrote:
>   
>> Aaron Griffin wrote:
>>     
>>> On Sat, Mar 21, 2009 at 8:06 AM, Baho Utot <baho-utot at columbus.rr.com>
>>> wrote:
>>>
>>>       
>>>> I am testing using the devtools scripts
>>>>
>>>> I created the chroot according to the developer
>>>> wiki:Building_in_a-Clean_Chroot
>>>>
>>>> modified the pacman.conf as follows:
>>>>
>>>> [CORE]
>>>> Server = file:///home/CORE
>>>>
>>>> [EXTRA]
>>>> Server = file:///home/EXTRA
>>>>
>>>> these point inside the chroot
>>>>
>>>> I built bcm43xx-fwcutter as a test and which succeeded
>>>> I placed the package into /home/CORE in the chroot
>>>> and ran repo -add CORE.db.tar.gz *.pkg.* to create the repo db file
>>>>
>>>> then trying to build the broadcomm firmware which requires
>>>> bcm43xx-fwcutter
>>>> I get
>>>>
>>>> sudo makechrootpkg -c -r /home/Build.Chroot/
>>>> building union chroot
>>>> moving build files to chroot
>>>> Setting PKGDEST in makepkg.conf
>>>> Setting SRCDEST in makepkg.conf
>>>> allowing 'nobody' sudo rights in the chroot
>>>> mounting sysfs : /sys
>>>> mounting procfs : /proc
>>>> binding device nodes : /dev
>>>> binding pacman cache : /var/cache/pacman
>>>> copying mtab : /etc/mtab
>>>> copying resolv.conf : /etc/resolv.conf
>>>> starting chroot (/chrootbuild)
>>>> ==> Making package: b43-firmware 4.150.10.5-1 any (Sat Mar 21 12:54:45
>>>> UTC
>>>> 2009)
>>>> ==> Checking Runtime Dependencies...
>>>> ==> Checking Buildtime Dependencies...
>>>> ==> Installing missing dependencies...
>>>> b43-fwcutter package not found, searching for group...
>>>> error: 'b43-fwcutter': not found in sync db
>>>> ==> ERROR: Pacman failed to install missing dependencies.
>>>> cleaning up mounts
>>>> Moving completed package file to
>>>> /home/SVN/repos/Projects/Desktop/extra/broadcom.firmware
>>>> mv: cannot stat
>>>>
>>>> `/home/Build.Chroot/union/pkgdest/b43-firmware-4.150.10.5-1-*.pkg.tar.gz':
>>>> No such file or directory
>>>> Build failed, check $CHROOT_DIR/rw/build
>>>> cleaning up unioned mounts
>>>>
>>>> shouldn't pacman have found b43-fwcutter packages in the chroot?
>>>>
>>>> Or am I missing something?
>>>>
>>>>         
>>> Where did you create the CORE db? The chroot tools use 3 directories
>>> to manage chroots under unionfs. The 'root' directory is intended to
>>> remain clean, with all changes to the chroot done in the 'rw'
>>> directory. Which dir did you create this repo in? If you did it in
>>> 'root', does the rw directory contain similar files? If so, I believe
>>> unionfs will give those files precedence.
>>>
>>>
>>>       
>> I created the repo in /home/Build.Chroot/root/home
>>
>>     
>>> I would recommend creating the repo at:
>>> /home/Build.Chroot/rw/home/CORE, using your scheme above. This way,
>>> the actual chroot itself remains clean and you can always clean it up
>>> by doing a rm -rf /home/Build.Chroot/rw
>>>
>>>       
>> Ok I will move it to the /home/Build.Chroot/rw directory,
>> the wiki states that the "local repo " should be under <chrootdir>/root/repo
>> If your suggestion doesn't work I'll move it to <chrootdir>/root/repo and
>> try again
>>     
>
> Well, the local repo can be anywhere and in either dir. Personally, I
> would use the rw directory as it keeps the original chroot as clean as
> possible
>   
Ok I'll put it in the rw


More information about the arch-general mailing list