[opensuse-buildservice] build.opensuse.org down?
https://build.opensuse.org/ is returning 503 "Down for Maintenance" and hence my local OBS install is also down. Did I miss an announcement on this list? Magnus Lewis-Smith -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Mittwoch, 23. Mai 2012, 09:57:37 schrieb Magnus Lewis-Smith:
https://build.opensuse.org/ is returning 503 "Down for Maintenance" and hence my local OBS install is also down.
Did I miss an announcement on this list?
No, sorry, we are down due to problems with our storage (again) :/ We do work on it right now. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi, I just did OBS upgrade on my private installation from OBS2.1 to OBS2.3. Back in OBS2.1, I could successfully build armv7el on x86_64 hosts. After upgrade to OBS2.1, all cross builds become failure with messages: ---------------------------------------------- running bzip2-x86-arm postinstall script chroot: failed to run command `sh': No such file or directory running tar-x86-arm postinstall script chroot: failed to run command `sh': No such file or directory running coreutils-x86-arm postinstall script chroot: failed to run command `sh': No such file or directory ......... ----------------------------------------------- I compared the old successful log with the failed one, and found that OBS2.3 missed the step of "copying qemu": -------------------------------------------------------- processing specfile /local/ramdrive/obs/worker/root_2/.build-srcdir/autoconf.spec ... running changelog2spec --target rpm --file /local/ramdrive/obs/worker/root_2/.build-srcdir/autoconf.spec init_buildsystem --cachedir /var/cache/build --clean --rpmlist /local/ramdrive/obs/worker/root_2/.build.rpmlist /local/ramdrive/obs/worker/root_2/.build-srcdir/autoconf.spec build rpmlint-Factory ... copying qemu /usr/bin/qemu-arm /usr/bin/qemu-arm-binfmt /usr/bin/qemu-armeb /usr/bin/qemu-armeb-binfmt /usr/bin/qemu-mips /usr/bin/qemu-mips-binfmt /usr/bin/qemu-mipsel /usr/bin/qemu-mipsel-binfmt /usr/bin/qemu-mipsn32 /usr/bin/qemu-mipsn32-binfmt /usr/bin/qemu-mipsn32el /usr/bin/qemu-mipsn32el-binfmt /usr/bin/qemu-ppc /usr/bin/qemu-ppc-binfmt /usr/bin/qemu-ppc64 /usr/bin/qemu-ppc64-binfmt /usr/bin/qemu-ppc64abi32 /usr/bin/qemu-ppc64abi32-binfmt /usr/bin/qemu-sh4 /usr/bin/qemu-sh4-binfmt /usr/bin/qemu-sh4eb /usr/bin/qemu-sh4eb-binfmt /usr/bin/qemu-sparc /usr/bin/qemu-sparc-binfmt /usr/bin/qemu-sparc32plus /usr/bin/qemu-sparc32plus-binfmt /usr/bin/qemu-sparc64 /usr/bin/qemu-sparc64-binfmt /usr/sbin/qemu-binfmt-conf.sh -------------------------------------------------------- How can I add this step back in OBS2.3? OBS Server OS: OpenSUSE 11.4, OBS2.3 OBS Worker OS: OpenSUSE 12.1, obs-worker-2.3.0-1.8, qemu-1.0.1-99.1 Thanks, Rick -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Mittwoch, 23. Mai 2012, 21:41:08 schrieb Rick Liu:
Hi,
I just did OBS upgrade on my private installation from OBS2.1 to OBS2.3. Back in OBS2.1, I could successfully build armv7el on x86_64 hosts. After upgrade to OBS2.1, all cross builds become failure with messages:
you could install an older build package, but it is actually recommended that you install your qemu package in Preinstall section instead. The reason behind this is that qemu has influence to the build result. That means all workers would have the same qemu package, you would need to update all workers at the same time and it would not be possible to maintain an old stable qemu for old projects and a newer one for new projects. The release notes contain some comments about this IIRC. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Mittwoch, 23. Mai 2012, 21:41:08 schrieb Rick Liu:
Hi,
I just did OBS upgrade on my private installation from OBS2.1 to OBS2.3. Back in OBS2.1, I could successfully build armv7el on x86_64 hosts. After upgrade to OBS2.1, all cross builds become failure with messages:
you could install an older build package, but it is actually recommended that you install your qemu package in Preinstall section instead.
[Rick Liu] I just found out that if I modify "/usr/lib/obs/server/build/build" file and enable USE_SYSTEM_QEMU (USE_SYSTEM_QEMU="--use-system-qemu"), I can add back "copying qemu" step. Is there a config file I can set (instead of hacking build script directly)? Is there any bad consequence of modify this line in "/usr/lib/obs/server/build/build" file? Rick -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Mittwoch, 23. Mai 2012, 22:55:07 schrieb Rick Liu:
Am Mittwoch, 23. Mai 2012, 21:41:08 schrieb Rick Liu:
Hi,
I just did OBS upgrade on my private installation from OBS2.1 to OBS2.3. Back in OBS2.1, I could successfully build armv7el on x86_64 hosts. After upgrade to OBS2.1, all cross builds become failure with messages:
you could install an older build package, but it is actually recommended that you install your qemu package in Preinstall section instead.
[Rick Liu] I just found out that if I modify "/usr/lib/obs/server/build/build" file and enable USE_SYSTEM_QEMU (USE_SYSTEM_QEMU="--use-system-qemu"), I can add back "copying qemu" step.
Is there a config file I can set (instead of hacking build script directly)?
No, there is not such a thing in bs_worker yet. We could add it though. But it is really highly recommended that you change your setup instead, because of the other problems.
Is there any bad consequence of modify this line in "/usr/lib/obs/server/build/build" file?
No, except that the old problems are back: * You can only have a single qemu version for your entire OBS instance. * You need to update all your workers manually. * All people doing local builds need to follow this special qemu * You will never be able to have a stable and maintainable branch Seriously, this should never ever been used on any production system. It was a gross hack. If you say you need it in any case, I will add an option to BSConfig.pm for the workers, because we became incompatible. But IMHO you should really change your setup instead. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (3)
-
Adrian Schröter -
Magnus Lewis-Smith -
Rick Liu