Re: gdbm reabase question
On Wed, Jun 20, 2018 at 8:27 AM Tom Hughes <tom(a)compton.nu> 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 version was built simultaneously
in f28 and rawhide and the rawhide build failed and was never fixed
so it still has the f26 one.
I was able to get a successful clisp build in Rawhide after updating
to the latest upstream sources, so it is now built against the current
gdbm.
--
Jerry James
http://www.jamezone.org/