[opensuse-buildservice] failed to build sysvinit
My sysvinit package in home:pley fails to build. The RPMs are created but the status afther finishing is "failed". The last lines from build log: [...] Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/sysvinit-2.86-build Wrote: /usr/src/packages/SRPMS/sysvinit-2.86-102.1.src.rpm Wrote: /usr/src/packages/RPMS/i586/sysvinit-2.86-102.1.i586.rpm Wrote: /usr/src/packages/RPMS/i586/sysvinit-debuginfo-2.86-102.1.i586.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.49527 + umask 022 + cd /usr/src/packages/BUILD + cd sysvinit-2.86 + rm -rf /var/tmp/sysvinit-2.86-build + exit 0 mount: can't find / in /etc/fstab or /etc/mtab /bin/bash: halt: command not found Kernel panic - not syncing: Attempted to kill init! Local build with lbuild works without any problem. Any ideas? Kind regards Martin Pley --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi Martin, by the way if your RPMs are created why are you talking about "failed" ? AFAIK this is normal behaviour. I see this on my package builds, too ? Regards Christian Martin Pley schrieb:
My sysvinit package in home:pley fails to build. The RPMs are created but the status afther finishing is "failed". The last lines from build log:
[...] Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/sysvinit-2.86-build Wrote: /usr/src/packages/SRPMS/sysvinit-2.86-102.1.src.rpm Wrote: /usr/src/packages/RPMS/i586/sysvinit-2.86-102.1.i586.rpm Wrote: /usr/src/packages/RPMS/i586/sysvinit-debuginfo-2.86-102.1.i586.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.49527 + umask 022 + cd /usr/src/packages/BUILD + cd sysvinit-2.86 + rm -rf /var/tmp/sysvinit-2.86-build + exit 0 mount: can't find / in /etc/fstab or /etc/mtab /bin/bash: halt: command not found Kernel panic - not syncing: Attempted to kill init!
Local build with lbuild works without any problem. Any ideas?
Kind regards Martin Pley --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Martin Pley wrote:
My sysvinit package in home:pley fails to build. The RPMs are created but the status afther finishing is "failed". The last lines from build log:
[...] /bin/bash: halt: command not found Kernel panic - not syncing: Attempted to kill init!
The buildservice normally doesn't install packages into the chroot if it's going to build the same package from source. E.g. libtool is always installed, except when building libtool itself. But certain packages need to be installed anyway, for instance 'make' or 'rpm' are always present. It turns out that sysvinit is also one of these, because the virtual machine doesn't shutdown otherwise. => adrian/darix/mls: sysvinit needs to be added to the Keep: set in the distro configs. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 02 January 2008 13:50:34 wrote Michal Marek:
Martin Pley wrote:
My sysvinit package in home:pley fails to build. The RPMs are created but the status afther finishing is "failed". The last lines from build log:
[...] /bin/bash: halt: command not found Kernel panic - not syncing: Attempted to kill init!
The buildservice normally doesn't install packages into the chroot if it's going to build the same package from source. E.g. libtool is always installed, except when building libtool itself. But certain packages need to be installed anyway, for instance 'make' or 'rpm' are always present. It turns out that sysvinit is also one of these, because the virtual machine doesn't shutdown otherwise.
=> adrian/darix/mls: sysvinit needs to be added to the Keep: set in the distro configs.
We can build sysvinfo also in openSUSE:Factory without that, so this seems not to be the reason. these both error messages can be ignored (but we should fix them anyway to avoid confusion), there is another line regarding / in /etc/fstab, I dunno yet, if this is the reason .... Need to look more deeply into this. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Mittwoch, 2. Januar 2008 14:51:57 schrieb Adrian Schröter:
On Wednesday 02 January 2008 13:50:34 wrote Michal Marek:
Martin Pley wrote:
My sysvinit package in home:pley fails to build. The RPMs are created but the status afther finishing is "failed". The last lines from build log:
[...] /bin/bash: halt: command not found Kernel panic - not syncing: Attempted to kill init!
The buildservice normally doesn't install packages into the chroot if it's going to build the same package from source. E.g. libtool is always installed, except when building libtool itself. But certain packages need to be installed anyway, for instance 'make' or 'rpm' are always present. It turns out that sysvinit is also one of these, because the virtual machine doesn't shutdown otherwise.
=> adrian/darix/mls: sysvinit needs to be added to the Keep: set in the distro configs.
We can build sysvinfo also in openSUSE:Factory without that, so this seems not to be the reason.
these both error messages can be ignored (but we should fix them anyway to avoid confusion), there is another line regarding / in /etc/fstab, I dunno yet, if this is the reason ....
I'd like to ignore them, but the RPMs are not copied out of the chroot enviroment. Thus they are deleted right after creation. If sysvinit is really not installed, as Michal told, then maybe the fstab-error-message is there because "/bin/mountpoint" is missing. However, I cannot believe that the build-chroot-env works without sysvinit. Kind regards Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (4)
-
Adrian Schröter -
Christian -
Martin Pley -
Michal Marek