On Wed, Jun 20, 2018 at 8:27 AM Tom Hughes wrote:
> I guess because 2.49-22.20170224hg.fc26 is the version currently
> in rawhide, which is indeed older than the version in F28 which
> suggests that it wasn't built in rawhide first as is supposed
> to happen.
>
> As you say it looks like the new v
On 20/06/18 15:17, Jerry James wrote:
There was a successful clisp build for f28, which depends on gdbm
rather than compat-gdbm, so I don't know why the F26 build should
matter. Clisp is again failing to build in Rawhide, though. I've got
it on my list of Fedora Things To Do. I will try updat
On Wed, Jun 20, 2018 at 3:50 AM wrote:
> clisp-0:2.49-22.20170224hg.fc26.i686
> clisp-0:2.49-22.20170224hg.fc26.x86_64
There was a successful clisp build for f28, which depends on gdbm
rather than compat-gdbm, so I don't know why the F26 build should
matter. Clisp is again failing to build in Ra
On Wed, Jun 20, 2018 at 11:49:38AM +0200, mskal...@redhat.com wrote:
> Hi,
> a new version of gdbm is out. So I would like to update gdbm in
> Rawhide.
> (Important note to my question is that gdbm is in minimal buildroot.)
>
> I've planned to do following (please correct me if I'm wrong it would
Hi,
a new version of gdbm is out. So I would like to update gdbm in
Rawhide.
(Important note to my question is that gdbm is in minimal buildroot.)
I've planned to do following (please correct me if I'm wrong it would
result in disaster):
1. build compat-gdbm package with current content of gdbm pa
