Re: OpenPKG procedure: test-drive OpenPKG 4 from scratch
Thanks for you answer Jeff. But I also don't know RPM macros and Lua well enough to debug this issue. But anyway, am I the only one to have this kind of problems while bootstrapping all my servers? Olivier __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: OpenPKG procedure: test-drive OpenPKG 4 from scratch
Hi all, actually, I could reproduce exactly the same error while bootstrapping OpenPKG-4 under Solaris 10 (amd64). So I decided to investigate a bit more, and here are my results: at the end of the compilation, just before the RPM files are created, I can see a lot of errors related to Lua. So my question: is it a bug or am I missing something on all my systems? If you need the complete bootstrap logs (for Debian and Solaris), feel free to ask. Thanks a lot in advance for your help, Olivier = Executing(%install): env -i OPENPKG_BOOT=1 /tmp/openpkg-4.0.1-20100104-buildroot/openpkg/lib/openpkg/bash --norc --noprofile --posix -e /tmp/rpm-tmp.23037 Processing files: openpkg-4.0.1-20100104 error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via realpath(3): No such file or directory 4 (empty) 3 (empty) error: Macro %_rpmdir failed to expand error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via realpath(3): No such file or directory 5 (empty) 4 (empty) error: Macro %_rpmdir failed to expand error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via realpath(3): No such file or directory 6 (empty) 5 (empty) error: Macro %_rpmdir failed to expand error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via realpath(3): No such file or directory 7 (empty) 6 (empty) error: Macro %_rpmdir failed to expand error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via realpath(3): No such file or directory 8 (empty) 7 (empty) error: Macro %_rpmdir failed to expand error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via realpath(3): No such file or directory 9 (empty) 8 (empty) error: Macro %_rpmdir failed to expand error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via realpath(3): No such file or directory 10 (empty) 9 (empty) error: Macro %_rpmdir failed to expand error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via realpath(3): No such file or directory 11 (empty) 10 (empty) error: Macro %_rpmdir failed to expand error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via realpath(3): No such file or directory 12 (empty) 11 (empty) error: Macro %_rpmdir failed to expand error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via realpath(3): No such file or directory 13 (empty) 12 (empty) error: Macro %_rpmdir failed to expand error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via realpath(3): No such file or directory 14 (empty) 13 (empty) error: Macro %_rpmdir failed to expand error: Lua script failed: /tmp/rpm.6:34: failed to resolve path via realpath(3): No such file or directory 15 (empty) 14 (empty) error: Macro %_rpmdir failed to expand error: Recursion depth(17) greater than max(16) 15 (empty) 14 error: Macro %_rpmdir has unterminated body 14 (empty) error: Recursion depth(17) greater than max(16) 15 (empty) error: Macro %_rpmdir has unterminated body 15 (empty) error: Recursion depth(17) greater than max(16) error: Recursion depth(17) greater than max(16) error: Recursion depth(17) greater than max(16) 15 (empty) 14 (empty) 13 (empty) 12 (empty) 11 (empty) 10 (empty) 9 (empty) 8 (empty) 7 (empty) 6 (empty) 5 (empty) 4 (empty) 3 (empty) 2 (empty) 1 (empty) 0 (empty) error: Could not open : No such file or directory = __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: OpenPKG procedure: test-drive OpenPKG 4 from scratch
On Jan 26, 2010, at 6:59 AM, Olivier Fournier wrote: error: Macro %_rpmdir failed to expand error: Recursion depth(17) greater than max(16) 15 (empty) 14 error: Macro %_rpmdir has unterminated body 14 (empty) error: Recursion depth(17) greater than max(16) 15 (empty) error: Macro %_rpmdir has unterminated body 15 (empty) error: Recursion depth(17) greater than max(16) error: Recursion depth(17) greater than max(16) error: Recursion depth(17) greater than max(16) 15 (empty) 14 (empty) 13 (empty) 12 (empty) 11 (empty) 10 (empty) 9 (empty) 8 (empty) 7 (empty) 6 (empty) 5 (empty) 4 (empty) 3 (empty) 2 (empty) 1 (empty) 0 (empty) error: Could not open : No such file or directory I don't know OpenPKG macros sufficiently well to tell what the actual flaw is. But the recursion depth failure is usually from a loop that tries to expand a macro that is also expanded within the definition. hth 73 de Jeff__ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: OpenPKG procedure: test-drive OpenPKG 4 from scratch
Ralf S. Engelschall wrote: I've done an installation under Debian 5.0 myself recently without problems. Interesting that it caused problems for you. My tests were done on two fresh-installed Debian 5.0.3 on the following architectures: * Linux debian-test 2.6.26-2-amd64 #1 SMP Thu Nov 5 02:23:12 UTC 2009 x86_64 GNU/Linux * Linux debian-test 2.6.26-2-openvz-amd64 #1 SMP Thu Nov 5 03:06:00 UTC 2009 i686 GNU/Linux And the results were exactly the same = permissions problems. It should not. The warnings result because of the wrong ownerships on the files. Why the ownerships are wrong I don't know. Have you specified some strange --user or --group options during bootstrapping? Here is my bootstraping command: sh openpkg-4.0.1-20100104.src.sh \ --prefix=/openpkg --tag=openpkg \ --user=openpkg --group=openpkg so no strange user or group option. Also this is incorrect. There ownerships were not correctly set for you as it seems. I've to check this myself under Debian 5.0 again... Would be great if you could test again with an up to date Debian version. Thanks a lot in advance. Olivier __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: OpenPKG procedure: test-drive OpenPKG 4 from scratch
On Mon, Jan 18, 2010, Olivier Fournier wrote: here are my results of the test-driving procedure on a fresh installed Debian Lenny. I've done an installation under Debian 5.0 myself recently without problems. Interesting that it caused problems for you. Can someone explain me the following things: - Why does OpenPKG need to be bootstrapped twice in order to get it to work without warnings? It should not. The warnings result because of the wrong ownerships on the files. Why the ownerships are wrong I don't know. Have you specified some strange --user or --group options during bootstrapping? - Why do the permissions of the license file have to be manually adjusted in order to activate a license? It should not require any permission adjustments. There something is broken for you. - Why do so many files belong to root after a fresh installation? Also this is incorrect. There ownerships were not correctly set for you as it seems. I've to check this myself under Debian 5.0 again... Ralf S. Engelschall r...@engelschall.com www.engelschall.com __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: OpenPKG procedure: test-drive OpenPKG 4 from scratch
Hi everyone, here are my results of the test-driving procedure on a fresh installed Debian Lenny. Can someone explain me the following things: - Why does OpenPKG need to be bootstrapped twice in order to get it to work without warnings? - Why do the permissions of the license file have to be manually adjusted in order to activate a license? - Why do so many files belong to root after a fresh installation? Thanks and Regards, Olivier - # system information r...@lab:/var/tmp# uname -a Linux lab.test 2.6.26-2-openvz-amd64 #1 SMP Thu Nov 5 03:06:00 UTC 2009 i686 GNU/Linux r...@lab:/var/tmp# cat /etc/debian_version 5.0.3 # download latest OpenPKG framework bootstrap sources r...@lab:/var/tmp# curl -LO http://openpkg.org/go/download/openpkg.src.sh % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 2 43.6M2 949k0 0 262k 0 0:02:50 0:00:03 0:02:47 314k # bootstrap OpenPKG instance r...@lab:/var/tmp# sh openpkg.src.sh --prefix=/openpkg --tag=openpkg --user=openpkg --group=openpkg OpenPKG CURRENT Source Bootstrap Package, version 20100104 Building for prefix /openpkg on current platform ++ extracting OpenPKG source distribution ++ building OpenPKG binary distribution OpenPKG Bootstrap Procedure ++ bootstrap version: 4.0.1-20100104 ... # install newly produced package r...@lab:/var/tmp# sh openpkg-*-openpkg.sh OpenPKG CURRENT Binary Bootstrap Package, version package openpkg is not installed Built for prefix /openpkg on target platform ix86-debian5.0 ++ hooking OpenPKG instance into system environment ++ creating OpenPKG instance root directory /openpkg ++ extracting OpenPKG binary distribution ++ installing OpenPKG binary distribution ++ fixating OpenPKG instance filesystem hierarchy ++ post-processing OpenPKG bootstrap installation ... # switch to openpkg user = why these warnings? r...@lab:/var/tmp# su - openpkg openpkg:WARNING: invalid owner user id 0 (expected 1001) on configuration file /openpkg/etc/openpkg/managers -- ignoring file openpkg:WARNING: invalid owner user id 0 (expected 1001) on configuration file /openpkg/etc/openpkg/managers -- ignoring file open...@lab$ # rebuild openpkg = why is it needed? Don't I have already the latest version? r...@lab:/var/tmp# /openpkg/bin/openpkg build openpkg | sh openpkg:WARNING: invalid owner user id 0 (expected 1001) on configuration file /openpkg/etc/openpkg/managers -- ignoring file openpkg:WARNING: invalid owner user id 0 (expected 1001) on configuration file /openpkg/etc/openpkg/managers -- ignoring file openpkg:WARNING: invalid owner user id 0 (expected 1001) on configuration file /openpkg/etc/openpkg/managers -- ignoring file openpkg:WARNING: invalid owner user id 0 (expected 1001) on configuration file /openpkg/etc/openpkg/managers -- ignoring file openpkg:WARNING: invalid owner user id 0 (expected 1001) on configuration file /openpkg/etc/openpkg/managers -- ignoring file openpkg:WARNING: invalid owner user id 0 (expected 1001) on configuration file /openpkg/etc/openpkg/managers -- ignoring file openpkg:WARNING: invalid owner user id 0 (expected 1001) on configuration file /openpkg/etc/openpkg/managers -- ignoring file openpkg:WARNING: invalid owner user id 0 (expected 1001) on configuration file /openpkg/etc/openpkg/managers -- ignoring file openpkg:WARNING: invalid owner user id 0 (expected 1001) on configuration file /openpkg/etc/openpkg/managers -- ignoring file openpkg:WARNING: invalid owner user id 0 (expected 1001) on configuration file /openpkg/etc/openpkg/managers -- ignoring file http://download.openpkg.org/framework/release/source/openpkg-4.0.1-20100104.src.rpm openpkg:WARNING: invalid owner user id 0 (expected 1001) on configuration file /openpkg/etc/openpkg/managers -- ignoring file ## 3.7% ... # switch to openpkg user = OK, no more warning r...@lab:/var/tmp# su - openpkg open...@lab$ # activate community license = permission denied open...@lab$ openpkg license activate COMMUNITY /openpkg/libexec/openpkg/license: line 167: /openpkg/etc/openpkg/license: Permission denied openpkg:license:ERROR: failed to activate license under id COMMUNITY # change ownership of license file r...@lab:/var/tmp# chown -R openpkg:openpkg /openpkg/etc/openpkg/license # activate community license = OK open...@lab$ openpkg license activate COMMUNITY # files belonging to root. Is it normal? r...@lab:/var/tmp# find /openpkg/ -user root /openpkg/.bash_login /openpkg/etc/rc.conf /openpkg/etc/openpkg/register.tran /openpkg/etc/openpkg/managers.rpmorig /openpkg/etc/openpkg/rpmlua.rpmorig /openpkg/etc/openpkg/rpmpopt.rpmorig /openpkg/etc/openpkg/register.prep /openpkg/etc/openpkg/platform.rpmorig /openpkg/etc/openpkg/register.util
