DPDK CI discussions
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Aaron Conole <aconole@redhat.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: [dpdk-ci] OBS project configuration
Date: Wed, 22 Jul 2020 14:18:45 +0000	[thread overview]
Message-ID: <17a484531bae4754aae5e78e5324b780@pantheon.tech> (raw)

[-- Attachment #1: Type: text/plain, Size: 1770 bytes --]

Hi Aaron,

I've tinkered a bit with the initial repository/architecture configuration. Here's what I looked at: https://build.opensuse.org/repositories/home:jlinkes - a bunch of RedHat/Debian systems on all supported architectures.

First a general note: the rpm .spec file defines the make build instead of meson build. This currently leads to failures in rpm builds, so we need to change it to meson build (I don't think using MAKE_PAUSE=n is the way to go, since make build is going to be deprecated).

You can look at the results here: https://build.opensuse.org/package/show/home:jlinkes/upstream_master. I think we can enable the passing repositories right away. Some notes about .deb failures:

*        Debian_9.0 doesn't even start because it doesn't have the proper packages: nothing provides debhelper >= 10.3~, (got version 10.2.5) etc. I think we can leave Debian 9 out since there's still Debian 10 that works fine.

*        xUbuntu_18.04 errors because of ERROR: Meson version is 0.45.1 but project requires >= 0.47.1. This is basically the same as Debian 9. However, Ubuntu 18.04 is a popular distribution, so we might want to think of a workaround. Maybe we disable it now a enable later if we find one.

I did a run with older code in https://build.opensuse.org/package/show/home:jlinkes/series_10567, but that still uses make build, so it's not very useful. There are build errors, but those could go away with meson build and maybe the systems won't even have the proper version of meson.

For now, what makes sense to me is to enable the Debian repositories except Debian 9 and Ubuntu 18.04, then changing rpms to build with meson and testing it and then we can enable Red Hat repositories based on how that goes.

Regards,
Juraj

[-- Attachment #2: Type: text/html, Size: 7809 bytes --]

             reply	other threads:[~2020-07-22 14:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22 14:18 Juraj Linkeš [this message]
2020-07-22 14:44 ` Aaron Conole
2020-07-23  5:04   ` Juraj Linkeš

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17a484531bae4754aae5e78e5324b780@pantheon.tech \
    --to=juraj.linkes@pantheon.tech \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).