Hi all,
I'm posting to -buildservice as I think from a packaging PoV, the .spec should be fine.
The package Virtualization:VMware/open-vm-tools fails to build for openSUSE_13.2 and openSUSE_Factory repositories.
If I check this package out and do locally osc build, then the build works just fine, either in a chroot env (default for me) or in a kvm sessioon using --vm-type=kvm. Both cases give successful builds.
Which special trick did I miss to get the same result in OBS as I get locally?
Cheers, Dominique
Dimstar / Dominique Leuenberger dimstar@opensuse.org writes:
If I check this package out and do locally osc build, then the build works just fine, either in a chroot env (default for me) or in a kvm sessioon using --vm-type=kvm. Both cases give successful builds.
Did you run the pesign-repackage stage?
Andreas.
On Thu, 2014-11-13 at 11:30 +0100, Andreas Schwab wrote:
Dimstar / Dominique Leuenberger dimstar@opensuse.org writes:
If I check this package out and do locally osc build, then the build works just fine, either in a chroot env (default for me) or in a kvm sessioon using --vm-type=kvm. Both cases give successful builds.
Did you run the pesign-repackage stage?
I don't understand the question - or rather: I have no idea how to do that. Something that happens on OBS in plus which does not happen on osc build?
(said differently: no - I haven't)
Dominique
Dimstar / Dominique Leuenberger dimstar@opensuse.org writes:
On Thu, 2014-11-13 at 11:30 +0100, Andreas Schwab wrote:
Dimstar / Dominique Leuenberger dimstar@opensuse.org writes:
If I check this package out and do locally osc build, then the build works just fine, either in a chroot env (default for me) or in a kvm sessioon using --vm-type=kvm. Both cases give successful builds.
Did you run the pesign-repackage stage?
I don't understand the question - or rather: I have no idea how to do that. Something that happens on OBS in plus which does not happen on osc build?
$ osc rbl Virtualization:VMware/open-vm-tools openSUSE_13.2 i586 | grep pesign-repackage.spec [ 576s] OTHER/pesign-repackage.spec [ 583s] OTHER/pesign-repackage.spec [ 1s] cloud138 started "build pesign-repackage.spec" at Thu Nov 13 09:39:16 UTC 2014. [ 1s] processing recipe /var/cache/obs/worker/root_2/.build-srcdir/pesign-repackage.spec ... [ 1s] running changelog2spec --target rpm --file /var/cache/obs/worker/root_2/.build-srcdir/pesign-repackage.spec [ 1s] init_buildsystem --configdir /var/run/obs/worker/2/build/configs --cachedir /var/cache/build --prepare --clean --rpmlist /var/cache/obs/worker/root_2/.build.rpmlist /var/cache/obs/worker/root_2/.build-srcdir/pesign-repackage.spec build rpmlint-Factory ... [ 36s] processing recipe /.build-srcdir/pesign-repackage.spec ... [ 36s] init_buildsystem --configdir /.build/configs --cachedir /var/cache/build /.build-srcdir/pesign-repackage.spec build rpmlint-Factory ... [ 125s] I have the following modifications for pesign-repackage.spec: [ 125s] ----- building pesign-repackage.spec (user abuild) [ 125s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --define 'disturl obs://build.opensuse.org/Virtualization:VMware/openSUSE_13.2/ca5286273410c74606fd18219f8eea93-open-vm-tools' /home/abuild/rpmbuild/SOURCES/pesign-repackage.spec
Andreas.
On Thu, 2014-11-13 at 12:59 +0100, Andreas Schwab wrote:
Dimstar / Dominique Leuenberger dimstar@opensuse.org writes:
On Thu, 2014-11-13 at 11:30 +0100, Andreas Schwab wrote:
Dimstar / Dominique Leuenberger dimstar@opensuse.org writes:
If I check this package out and do locally osc build, then the build works just fine, either in a chroot env (default for me) or in a kvm sessioon using --vm-type=kvm. Both cases give successful builds.
Did you run the pesign-repackage stage?
I don't understand the question - or rather: I have no idea how to do that. Something that happens on OBS in plus which does not happen on osc build?
$ osc rbl Virtualization:VMware/open-vm-tools openSUSE_13.2 i586 | grep pesign-repackage.spec [ 576s] OTHER/pesign-repackage.spec [ 583s] OTHER/pesign-repackage.spec [ 1s] cloud138 started "build pesign-repackage.spec" at Thu Nov 13 09:39:16 UTC 2014. [ 1s] processing recipe /var/cache/obs/worker/root_2/.build-srcdir/pesign-repackage.spec ... [ 1s] running changelog2spec --target rpm --file /var/cache/obs/worker/root_2/.build-srcdir/pesign-repackage.spec [ 1s] init_buildsystem --configdir /var/run/obs/worker/2/build/configs --cachedir /var/cache/build --prepare --clean --rpmlist /var/cache/obs/worker/root_2/.build.rpmlist /var/cache/obs/worker/root_2/.build-srcdir/pesign-repackage.spec build rpmlint-Factory ... [ 36s] processing recipe /.build-srcdir/pesign-repackage.spec ... [ 36s] init_buildsystem --configdir /.build/configs --cachedir /var/cache/build /.build-srcdir/pesign-repackage.spec build rpmlint-Factory ... [ 125s] I have the following modifications for pesign-repackage.spec: [ 125s] ----- building pesign-repackage.spec (user abuild) [ 125s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --define 'disturl obs://build.opensuse.org/Virtualization:VMware/openSUSE_13.2/ca5286273410c74606fd18219f8eea93-open-vm-tools' /home/abuild/rpmbuild/SOURCES/pesign-repackage.spec
Eh, thanks for that! So, after 'my' build is actually done, there is a 2nd .spec being started to sign the KMPs. But it seems that pesign is messing up the scriptlets in the other packages.
I vote for a bug in pesign! :) It should probably not even touch packages that don't have kernel modules.
Anyway, the hunt has an end - the guilty one identified.. now to the right fix...
Cheers, Dominique
On 13.11.2014 13:46, Dimstar / Dominique Leuenberger wrote:
I vote for a bug in pesign! :) It should probably not even touch packages that don't have kernel modules.
Not buildrequiring kernel-syms will be a clear signal that you have no kernel modules :)
Greetings, Stephan
On Thu, 2014-11-13 at 15:05 +0100, Stephan Kulow wrote:
On 13.11.2014 13:46, Dimstar / Dominique Leuenberger wrote:
I vote for a bug in pesign! :) It should probably not even touch packages that don't have kernel modules.
Not buildrequiring kernel-syms will be a clear signal that you have no kernel modules :)
Greetings, Stephan
But the fact is I DO have kernel modules in this package... but not the one that has the suid binary that is being touched...
buildservice@lists.opensuse.org
-
Andreas Schwab -
Dimstar / Dominique Leuenberger -
Stephan Kulow