Mailinglist Archive: opensuse-buildservice (74 mails)

< Previous Next >
Re: [opensuse-buildservice] Re: Package installation after build fails, requirements NOT installed
Am 24.05.19 um 13:33 schrieb Ralf Becker:
Hi Andreas,

thanks for your answer :)

Am 24.05.19 um 11:57 schrieb Andreas Schwab:
Try asking in opensuse-packaging@. Looks like your install script is
trying to use a service and fails if that isn't started.

It tries to start the service, if it's not running:

[ 46s] Created symlink
/etc/systemd/system/ ->
[ 46s] Failed to connect to bus: No such file or directory

But it fails, because of the build environment.

I understand that it is though for the package install check to
successful start something like the docker daemon, in all types of

Ugly hack from our in-house OBS instance, that my cow-orkers have found:

chkconfig FOOBAR on || true

# in kiwi environment:
### ZYPP_CONF=/var/cache/kiwi/zypper/zypp.conf.25480
# in obs environment:
### YAST_IS_RUNNING=instsys
if [ -n "$BUILD_ROOT" ] && [ "$YAST_IS_RUNNING" = instsys ] && [ "$PNAME" =
"%{name}" ]; then
echo "INFO: not restarting FOOBAR in build service environment"
elif [ "$PBL_SKIP_BOOT_TEST" = 1 ] && echo "$ZYPP_CONF" | grep -q '/kiwi/'; then
echo "INFO: not restarting FOOBAR in kiwi environment"
# restart. stop does not hurt if it is not running
%if 0%{?rhel} >= 7 || 0%{?suse_version} > 1200
systemctl stop FOOBAR
systemctl start FOOBAR
/etc/init.d/FOOBAR stop
/etc/init.d/FOOBAR start

As you can see, it is doing things you should not do in a %post script (always
starting the service...), but the part
mentioned in the comments could help you.

Have fun,
Stefan Seyfried

"For a successful technology, reality must take precedence over
public relations, for nature cannot be fooled." -- Richard Feynman
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >