Re: Making rpm5 work with dnf

On 12/08/2016 10:54 AM, Jeff Johnson wrote: Jeff, can you commit the changes to cvs? I can’t check in code blindly, nor will I check in code that cannot be tested, nor do I have the time to generate diff’s and examine your port. There is no way to test (even de facto, by running some other

Re: Making rpm5 work with dnf

On 12/07/2016 07:21 PM, Jeffrey Johnson wrote: Your next stopping point is going to be Berkeley DB as a pre-requisite. I didn't get there yet; I hit a couple different issues, and these do look like bugs. The relevant configure options are --with-libgit2 \ --enable-build-pic \

Re: Making rpm5 work with dnf

> On Dec 8, 2016, at 10:16 AM, Alexander Kanavin > wrote: > > On 12/07/2016 07:21 PM, Jeffrey Johnson wrote: >> Your next stopping point is going to be Berkeley DB as a pre-requisite. > > I didn't get there yet; I hit a couple different issues, and these do

Re: Making rpm5 work with dnf

> On Dec 8, 2016, at 8:49 AM, Alexander Kanavin > wrote: > > On 12/08/2016 10:54 AM, Jeff Johnson wrote: >>> Jeff, can you commit the changes to cvs? >>> >> >> I can’t check in code blindly, nor will I check in code that cannot be >> tested, >> nor do I

createrepo_c python test failures

If you try building createrepo_c (my build is in doit.sh), you will see … RPM5 builds against libgit2 tip and libgit2 “breaks” every other month. The fixes are usually rather easy, but the code is entirely proof-of-concept. I recommend rm -rf libgit2 (which is likely enuf to disable)