All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: linux-integrity@vger.kernel.org,
	"Bruno E. O. Meneguele" <bmeneg@redhat.com>
Subject: Re: [PATCH 1/1] ci: Remove CentOS 8
Date: Wed, 23 Mar 2022 13:55:47 +0100	[thread overview]
Message-ID: <YjsY01DZe0X67rUx@pevik> (raw)
In-Reply-To: <8c8dc78ab91d41c5755b5e1ae13a3054816d8072.camel@linux.ibm.com>

> Hi Petr,

> > > Removing "centos:latest" works, but is there another option?  Perhaps
> > > defining a different repo - "REPO=quay.io/centos/"?
> > This fix would be for Travis, which I'm not able to fix, but not for GitHub
> > Actions :(. I'm not aware how to specify alternative repository for it.

> FYI, "centos:stream9" results in crypto deprecated warnings and results
> in /dev/null errors.  Instead of removing the "centos:latest" entry in
> travis, I'll replace it with "centos:stream8" for now.

> The "centos:stream9" -devel rpm packages are in the CRB repo.  I
> manually set the CRB repo to enabled using sed.  Is there a better way
> of enabling CRB?

> Do you prefer to limit this patch to just removing the "centos:latest"
> entry in ci.yml and reposting it, or should I trim it?
I'll check if centos:stream8 works on GitHub Actions.

Kind regards,
Petr

> thanks,

> Mimi


  reply	other threads:[~2022-03-23 12:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15  7:49 [PATCH 1/1] ci: Remove CentOS 8 Petr Vorel
2022-03-22 18:25 ` Mimi Zohar
2022-03-22 19:30   ` Petr Vorel
2022-03-23 12:14     ` Mimi Zohar
2022-03-23 12:55       ` Petr Vorel [this message]
2022-03-23 13:45       ` Petr Vorel

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=YjsY01DZe0X67rUx@pevik \
    --to=pvorel@suse.cz \
    --cc=bmeneg@redhat.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=zohar@linux.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.