Hello @all, I'm seeing several cases in my home project where builds on anything < Tumbleweed (i.e. 15.2, 15.3) fail, always with the same error: [ 56s] + %set_build_flags [ 56s] /var/tmp/rpm-tmp.qudRi2: line 33: fg: no job control [ 56s] error: Bad exit status from /var/tmp/rpm-tmp.qudRi2 (%build) [ 56s] Here's the fun bits: - the source and spec file havent changed in weeks, sometimes months - there is no "%set_build_flags" anywhere IN the spec file the broken bit seems to be in what in the spec file reads as: %prep %autosetup -p1 so ... how do I fix this? Cheers MH -- Mathias Homann Mathias.Homann@openSUSE.org OBS: lemmy04 Jabber (XMPP): lemmy@tuxonline.tech IRC: [Lemmy] on freenode and ircnet (bouncer active) telegram: https://telegram.me/lemmy98 keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
On Thursday 2021-02-04 14:10, Mathias Homann wrote:
Hello @all,
I'm seeing several cases in my home project where builds on anything < Tumbleweed (i.e. 15.2, 15.3) fail, always with the same error:
[ 56s] + %set_build_flags [ 56s] /var/tmp/rpm-tmp.qudRi2: line 33: fg: no job control [ 56s] error: Bad exit status from /var/tmp/rpm-tmp.qudRi2 (%build) [ 56s]
It's a bug in the macros that the meson package provides. It requires rpm-4.16, which it does not encode in its specfile, and something which Leap 15.3 also does not have.
On Thu, 2021-02-04 at 14:16 +0100, Jan Engelhardt wrote:
It's a bug in the macros that the meson package provides. It requires rpm-4.16, which it does not encode in its specfile, and something which Leap 15.3 also does not have.
Actually, it should be RPM 4.15 IIRC; and I already have a local branch that declares a Conflicts: rpm < 4.15 for this. So far, not submitted though, Cheers, Dominique
Am Donnerstag, 4. Februar 2021, 14:16:49 CET schrieb Jan Engelhardt:
On Thursday 2021-02-04 14:10, Mathias Homann wrote:
Hello @all,
I'm seeing several cases in my home project where builds on anything < Tumbleweed (i.e. 15.2, 15.3) fail, always with the same error:
[ 56s] + %set_build_flags [ 56s] /var/tmp/rpm-tmp.qudRi2: line 33: fg: no job control [ 56s] error: Bad exit status from /var/tmp/rpm-tmp.qudRi2 (%build) [ 56s]
It's a bug in the macros that the meson package provides. It requires rpm-4.16, which it does not encode in its specfile, and something which Leap 15.3 also does not have.
So, in theory, I could link rpm from Base:System into my home project, and mark it as "use for build" but no publishing, and all should be well? Or would the resulting packages be incompatible with older rpm versions? Cheers MH -- Mathias Homann Mathias.Homann@openSUSE.org OBS: lemmy04 Jabber (XMPP): lemmy@tuxonline.tech IRC: [Lemmy] on freenode and ircnet (bouncer active) telegram: https://telegram.me/lemmy98 keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
On Thu, 2021-02-04 at 14:35 +0100, Mathias Homann wrote:
It's a bug in the macros that the meson package provides. It requires rpm-4.16, which it does not encode in its specfile, and something which Leap 15.3 also does not have.
So, in theory, I could link rpm from Base:System into my home project, and mark it as "use for build" but no publishing, and all should be well? Or would the resulting packages be incompatible with older rpm versions?
I would rather stick to the meson version from the distro. Cheers, Dominique
participants (3)
-
Dominique Leuenberger / DimStar -
Jan Engelhardt -
Mathias Homann