Re: What is needed to mock build for rhel+epel on Fedora?

2023-03-14 Thread Barry
On 14 Mar 2023, at 20:28, murph nj wrote:On Mon, Mar 13, 2023 at 12:00 PM Barry Scott wrote:What do I need to setup to allow mock to build for rhel+epel on Fedora? I'm getting this error: $ mock -r rhel+epel-8-x86_64 --print-root ERROR: /etc/pki/entitlement is not a dir

Re: What is needed to mock build for rhel+epel on Fedora?

2023-03-14 Thread Todd Zullinger
Barry Scott wrote: >> On 13 Mar 2023, at 20:15, Richard Shaw wrote: >> Does it have to be RHEL? I've used Alma and Rocky with success. > > Good question. > > If I build for Alma or Rocky will it install on RHEL, > Centos, Oracle Linux etc? > > I picked RHEL as all the others aim to be ABI compa

Re: What is needed to mock build for rhel+epel on Fedora?

2023-03-14 Thread murph nj
> On Mon, Mar 13, 2023 at 12:00 PM Barry Scott > wrote: > >> What do I need to setup to allow mock to build for rhel+epel on Fedora? >> >> I'm getting this error: >> >> $ mock -r rhel+epel-8-x86_64 --print-root >> ERROR: /etc/pki/entitlement is not a directory is subscription-manager >> installed?

Re: What is needed to mock build for rhel+epel on Fedora?

2023-03-14 Thread Barry Scott
> On 13 Mar 2023, at 20:15, Richard Shaw wrote: > > On Mon, Mar 13, 2023 at 12:00 PM Barry Scott > wrote: >> What do I need to setup to allow mock to build for rhel+epel on Fedora? >> >> I'm getting this error: >> >> $ mock -r rhel+epel-8-x86_64 --print-root >>

Re: is cockpit able to handle btrfs mirror's ?

2023-03-14 Thread old sixpack13
> On Fri, Mar 10, 2023, at 1:57 PM, old sixpack13 wrote: > > This is expected behavior right now (certainly not expected by a reasonable > user) from a ... Thanks ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to

Re: is cockpit able to handle btrfs mirror's ?

2023-03-14 Thread Chris Murphy
On Fri, Mar 10, 2023, at 1:57 PM, old sixpack13 wrote: > more to read: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/thread/MNAGV2XFQOLXQAXGP2CBHOQRGVYDXD2O/ This is expected behavior right now (certainly not expected by a reasonable user) from a development pers