bin/build-packages -l pcsxr.922f9c6f11ae9cb2b42ff805fb6362c6163b4739.work-tree.multilib
Btw, I was wrong regarding "HEAD": It is a valid git qualifier, but you can't use it as a revision for the upstream package-repository, because the given qualifier is used to determine if the package is from community or packages.
Unfortunately I don't see how to determine this by other means, because some packages are in community and packages (e.g. cmucl, ddd, fbida, nedit).
I'll have a little hack in my fork testing the HEAD idea too in build-package..
]]>I will think a little about the HEAD-idea before actually starting to implement it.
]]>So I can build and test packages with build-packages:
./build-packages -l which.fe6d45dd22ee25e70164dd3bb84541968ba6813e.4120aefd67048ed2e5bce7caf43e83d88a8165f1.core
I still have trouble with PGP keys everywhere like:
gpg: skipped "0x15eebadc0de": Invalid user ID
gpg: signing failed: Invalid user ID
but I have to sort aout my local PGP mess..
Maybe a './build-packages which.HEAD.HEAD.core' would also be usefull using the current git versions of packages/community resp. packages32?
HEAD would do a 'git rev-parse HEAD' or 'git stash create' to get the current revision. The git stash has the benefit that you
don't have to check in the packages32 directory while still working on the package.
git_revision=$(cd ${repo_path}; git rev-parse HEAD)
mod_git_revision=$(cd ${repo_paths__archlinux32}; git stash create)
if [ -z $mod_git_revision ]; then
mod_git_revision=$(cd ${repo_paths__archlinux32}; git rev-parse HEAD)
fi
Btw: I noticed the gpg-key issue, too (If I understand you correctly, this is the reason why you run "makepkg -S" before running staging-i686-build). But it always went away after some while, so I was unable to debug it :-/ The best choice should be to remove this issue and simply run "staging-i686-build" on a hand-crafted PKGBUILD, I think.
]]>No problem for doing a little bit of packaging.
I'm still trying to understand the builder, so the test-build-package script is pure copy-paste code.
Sure I can make a pull request after cleaning up a little bit.
I'll test again the architeture issue, I have a clue that one of the first makepkg invocations
happens on the host and not in the 32-bit chroot..
..and sed is never aesthetical, in my point of view. :-)
Greetings
Andreas
]]>first let me thank you for the contributions you made :-)
second: Sry, I can't reproduce your error: your regex works fine and also your script looks ok - besides the sed-hack (from an aesthetical point). Also complaint about x86_64 seems wrong - are you sure you're building in a 32-bit environment? Maybe it's from the first makepkg invocation?
third: What do you think of the idea to include your test-build-package script into the builder repository, so everyone can use it?
Cheers,
deep42thought
I patched 'append_architectures' in the following way, not to add the architecture
for 'any' packages:
# append_architectures $PKGBUILD
# mangle $arch in PKBUILDs to contain i486, i586, i686
append_architectures() {
local PKGBUILD="$1"
sed -i '/^arch=.*any/!{/^arch=(/s/(/(i686 /}' "${PKGBUILD}"
}
Comments? :-)
]]>