Yeah.  There's a couple tickets that could probably be subsumed by a new
one.  I'll have a look.

On Thu, Jun 16, 2022 at 8:04 PM Gilles Sadowski <gillese...@gmail.com>
wrote:

> Hello.
>
> Le jeu. 16 juin 2022 à 19:36, Alex Remily <alex.rem...@gmail.com> a écrit
> :
> >
> > Do you think we could simply use CRYPTO-120
> > <https://issues.apache.org/jira/browse/CRYPTO-120>?
>
> Maybe.
> Or open a new one with an up-to-date description,
> and signal that it replaces old/obsolete reports...
>
> Gilles
>
> > On Thu, Jun 16, 2022 at 1:31 PM Gilles Sadowski <gillese...@gmail.com>
> > wrote:
> >
> > > Hello.
> > >
> > > Since there is an issue to be solved, could you file a report on JIRA?
> > > [And post there patches or new files, and instructions.]
> > >
> > > Thanks,
> > > Gilles
> > >
> > > Le jeu. 16 juin 2022 à 19:18, Alex Remily <alex.rem...@gmail.com> a
> écrit
> > > :
> > > >
> > > > I just ran [2], and whatever it does, it doesn't appear to do a
> build of
> > > > commons-crypto.  I'd appreciate it if any developers who have the
> time
> > > > would take a look at the dockerfile here:
> > > >
> > > > https://github.com/aremily/commons-crypto
> > > >
> > > > If you're copying the dockerfile into your own fork, you'll need the
> > > > makefile.common file as well.
> > > >
> > > > Alex
> > > >
> > > > On Thu, Jun 16, 2022 at 1:07 PM Jochen Wiedmann <
> > > jochen.wiedm...@gmail.com>
> > > > wrote:
> > > >
> > > > > On Thu, Jun 16, 2022 at 7:00 PM sebb <seb...@gmail.com> wrote:
> > > > >
> > > > > > [1] src/docker/Dockerfile
> > > > > > [2] src/conf/Docker/Dockerfile-luw
> > > > >
> > > > > Have to admit, that I wasn't aware of [2], when I created [1].
> Mine is
> > > > > incomplete, and can easily be removed. Was basically just an
> attempt
> > > > > to reproduce the build instructions in the hope, that others would
> > > > > verify, and fix my errors.
> > > > >
> > > > > Jochen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Reply via email to