On Fri, Jun 23, 2023 at 05:20:04PM +, Brandeburg, Jesse wrote:
> If I may, I'd like to revive this long ago [1] thread, and now that RHEL9.1
> is out, can we proceed to build coccinelle for EPEL 9.1?
>
> Is there anything I can do to help?
>
> [1]
>
On Fri, Mar 11, 2022 at 09:36:08AM +, Richard W.M. Jones wrote:
> On Fri, Mar 04, 2022 at 11:14:31AM +, Richard W.M. Jones wrote:
> > On Fri, Mar 04, 2022 at 11:01:20AM +, Richard W.M. Jones wrote:
> > > On Fri, Mar 04, 2022 at 10:51:48AM +, Richard W.M. Jones wrote:
> > > > I'll
On Fri, Mar 11, 2022 at 10:57:29AM +0100, Miro Hrončok wrote:
> On 11. 03. 22 10:36, Richard W.M. Jones wrote:
> >On Fri, Mar 04, 2022 at 11:14:31AM +, Richard W.M. Jones wrote:
> >>On Fri, Mar 04, 2022 at 11:01:20AM +, Richard W.M. Jones wrote:
> >>>On Fri, Mar 04, 2022 at 10:51:48AM
On 11. 03. 22 10:36, Richard W.M. Jones wrote:
On Fri, Mar 04, 2022 at 11:14:31AM +, Richard W.M. Jones wrote:
On Fri, Mar 04, 2022 at 11:01:20AM +, Richard W.M. Jones wrote:
On Fri, Mar 04, 2022 at 10:51:48AM +, Richard W.M. Jones wrote:
I'll see if we can move the OCaml packages
On Fri, Mar 04, 2022 at 11:14:31AM +, Richard W.M. Jones wrote:
> On Fri, Mar 04, 2022 at 11:01:20AM +, Richard W.M. Jones wrote:
> > On Fri, Mar 04, 2022 at 10:51:48AM +, Richard W.M. Jones wrote:
> > > I'll see if we can move the OCaml packages to CRB. It seems to be the
> > >
On Fri, Mar 04, 2022 at 11:01:20AM +, Richard W.M. Jones wrote:
> On Fri, Mar 04, 2022 at 10:51:48AM +, Richard W.M. Jones wrote:
> > I'll see if we can move the OCaml packages to CRB. It seems to be the
> > easiest way to fix the original coccinelle build problem.
>
> This gets odder.
On Fri, Mar 4, 2022 at 6:01 AM Richard W.M. Jones wrote:
>
> On Fri, Mar 04, 2022 at 10:51:48AM +, Richard W.M. Jones wrote:
> > I'll see if we can move the OCaml packages to CRB. It seems to be the
> > easiest way to fix the original coccinelle build problem.
>
> This gets odder. I see
On Fri, Mar 04, 2022 at 10:51:48AM +, Richard W.M. Jones wrote:
> I'll see if we can move the OCaml packages to CRB. It seems to be the
> easiest way to fix the original coccinelle build problem.
This gets odder. I see from our internal spreadsheet and downloads
that some of the ocaml
On Thu, Mar 03, 2022 at 12:42:03PM -0500, Josh Boyer wrote:
> On Thu, Mar 3, 2022 at 12:27 PM Richard W.M. Jones wrote:
> >
> > On Wed, Mar 02, 2022 at 09:04:04AM -0500, Neal Gompa wrote:
> > > So why not have the OCaml toolchain exposed in RHEL CRB? It sounds
> > > like it would be very
On Thu, Mar 3, 2022 at 12:27 PM Richard W.M. Jones wrote:
>
> On Wed, Mar 02, 2022 at 09:04:04AM -0500, Neal Gompa wrote:
> > So why not have the OCaml toolchain exposed in RHEL CRB? It sounds
> > like it would be very beneficial to have it there.
>
> It's a good question. I think we chose not
On Wed, Mar 02, 2022 at 09:04:04AM -0500, Neal Gompa wrote:
> So why not have the OCaml toolchain exposed in RHEL CRB? It sounds
> like it would be very beneficial to have it there.
It's a good question. I think we chose not to do that simply because
we were worried about handling CVEs in a
On Wed, Mar 2, 2022 at 8:52 AM Richard W.M. Jones wrote:
>
> To keep this a bit more specific, we're trying to build coccinelle for
> EPEL 9. This requires ocaml [compiler] and a bunch of ocaml packages.
> They are mainly in RHEL buildroot.
>
> The problem we're going to have (which to be fair
To keep this a bit more specific, we're trying to build coccinelle for
EPEL 9. This requires ocaml [compiler] and a bunch of ocaml packages.
They are mainly in RHEL buildroot.
The problem we're going to have (which to be fair is a problem
somewhat specific to OCaml linking) is that an alternate
On Tue, Mar 1, 2022 at 8:45 AM Stephen John Smoogen wrote:
>
>
>
> On Tue, 1 Mar 2022 at 08:19, Richard W.M. Jones wrote:
>>
>> On Tue, Mar 01, 2022 at 04:21:56AM -0500, Neal Gompa wrote:
>> > On Tue, Mar 1, 2022 at 3:07 AM Richard W.M. Jones
>> > wrote:
>> > >
>> > >
>> > >
On Tue, 1 Mar 2022 at 08:19, Richard W.M. Jones wrote:
> On Tue, Mar 01, 2022 at 04:21:56AM -0500, Neal Gompa wrote:
> > On Tue, Mar 1, 2022 at 3:07 AM Richard W.M. Jones
> wrote:
> > >
> > >
> > > https://bugzilla.redhat.com/show_bug.cgi?id=2058274
> > >
> > > fails to build with:
> > >
> >
On Tue, Mar 1, 2022 at 8:20 AM Richard W.M. Jones wrote:
>
> On Tue, Mar 01, 2022 at 04:21:56AM -0500, Neal Gompa wrote:
> > On Tue, Mar 1, 2022 at 3:07 AM Richard W.M. Jones wrote:
> > >
> > >
> > > https://bugzilla.redhat.com/show_bug.cgi?id=2058274
> > >
> > > fails to build with:
> > >
> >
On Tue, Mar 01, 2022 at 04:21:56AM -0500, Neal Gompa wrote:
> On Tue, Mar 1, 2022 at 3:07 AM Richard W.M. Jones wrote:
> >
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=2058274
> >
> > fails to build with:
> >
> > DEBUG util.py:444: No matching package to install: 'ocaml-dune >= 1.0'
>
On Tue, 1 Mar 2022 at 03:06, Richard W.M. Jones wrote:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2058274
>
> fails to build with:
>
> DEBUG util.py:444: No matching package to install: 'ocaml-dune >= 1.0'
>
> This package is in RHEL 9 buildroot (ocaml-dune-2.8.5-5.el9.x86_64).
>
> I
On Tue, Mar 1, 2022 at 3:07 AM Richard W.M. Jones wrote:
>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2058274
>
> fails to build with:
>
> DEBUG util.py:444: No matching package to install: 'ocaml-dune >= 1.0'
>
> This package is in RHEL 9 buildroot (ocaml-dune-2.8.5-5.el9.x86_64).
>
>
19 matches
Mail list logo
