[opensuse-buildservice] yum update before building?
My OBS is repo contains broken Fedora 27/28 builds because OBS Fedora repo seems to contain older versions of some critical dependencies. In particular, OBS seems to have R-core-3.4.4 whereas Fedora currently ships R-core-3.5.0. Because these versions are binary incompatible, the OBS build of my application does not work on the user machine. Log file: https://build.opensuse.org/build/home:jeroenooms:opencpu-2.0/Fedora_28/x86_6... Is there some way to "yum update" before starting the build? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi Jeroen, Maybe this helps: In advanced --> meta, change the order so the updates repo is used first: <repository name="Fedora_28"> <path project="Fedora:28" repository="update"/> <path project="Fedora:28" repository="standard"/> <arch>x86_64</arch> <arch>aarch64</arch> </repository> with kind regards, / met vriendelijke groet, Stefan van der Eijk with kind regards, / met vriendelijke groet, Stefan van der Eijk On Tue, Aug 21, 2018 at 11:15 PM Jeroen Ooms <jeroenooms@gmail.com> wrote:
My OBS is repo contains broken Fedora 27/28 builds because OBS Fedora repo seems to contain older versions of some critical dependencies.
In particular, OBS seems to have R-core-3.4.4 whereas Fedora currently ships R-core-3.5.0. Because these versions are binary incompatible, the OBS build of my application does not work on the user machine. Log file: https://build.opensuse.org/build/home:jeroenooms:opencpu-2.0/Fedora_28/x86_6...
Is there some way to "yum update" before starting the build?
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Dienstag, 21. August 2018, 23:26:29 CEST wrote Stefan van der Eijk:
Hi Jeroen,
Maybe this helps: In advanced --> meta, change the order so the updates repo is used first:
<repository name="Fedora_28"> <path project="Fedora:28" repository="update"/> <path project="Fedora:28" repository="standard"/>
the standard path is actually not needed here, since the last entry always gets expanded (and "update" has already "standard" as path in Fedora:28) JFYI ;)
<arch>x86_64</arch> <arch>aarch64</arch></repository>
with kind regards, / met vriendelijke groet,
Stefan van der Eijk with kind regards, / met vriendelijke groet,
Stefan van der Eijk
On Tue, Aug 21, 2018 at 11:15 PM Jeroen Ooms <jeroenooms@gmail.com> wrote:
My OBS is repo contains broken Fedora 27/28 builds because OBS Fedora repo seems to contain older versions of some critical dependencies.
In particular, OBS seems to have R-core-3.4.4 whereas Fedora currently ships R-core-3.5.0. Because these versions are binary incompatible, the OBS build of my application does not work on the user machine. Log file: https://build.opensuse.org/build/home:jeroenooms:opencpu-2.0/Fedora_28/x86_6...
Is there some way to "yum update" before starting the build?
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
-- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Wed, Aug 22, 2018 at 8:16 AM, Adrian Schröter <adrian@suse.de> wrote:
On Dienstag, 21. August 2018, 23:26:29 CEST wrote Stefan van der Eijk:
Hi Jeroen,
Maybe this helps: In advanced --> meta, change the order so the updates repo is used first:
<repository name="Fedora_28"> <path project="Fedora:28" repository="update"/> <path project="Fedora:28" repository="standard"/>
the standard path is actually not needed here, since the last entry always gets expanded (and "update" has already "standard" as path in Fedora:28)
Thanks both, this worked! Indeed, merely replacing "standard" with "update" in the meta file did the job. I don't understand why "update" is not the default as it is on a standard Fedora installation, but at least I have working binaries now :-) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mittwoch, 22. August 2018, 10:28:15 CEST wrote Jeroen Ooms:
On Wed, Aug 22, 2018 at 8:16 AM, Adrian Schröter <adrian@suse.de> wrote:
On Dienstag, 21. August 2018, 23:26:29 CEST wrote Stefan van der Eijk:
Hi Jeroen,
Maybe this helps: In advanced --> meta, change the order so the updates repo is used first:
<repository name="Fedora_28"> <path project="Fedora:28" repository="update"/> <path project="Fedora:28" repository="standard"/>
the standard path is actually not needed here, since the last entry always gets expanded (and "update" has already "standard" as path in Fedora:28)
Thanks both, this worked! Indeed, merely replacing "standard" with "update" in the meta file did the job. I don't understand why "update" is not the default as it is on a standard Fedora installation, but at least I have working binaries now :-)
update is not the default because your build might not work on a plain installation without updates. And builds rarely needing updates. And we save rebuilds ;) -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- 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 -
Jeroen Ooms -
Stefan van der Eijk