Re: Making rpm5 work with dnf

> On Dec 28, 2016, at 4:59 PM, Mark Hatle wrote: > > > AFAIK, only openssl 1.0.x supports the FIPS module. There are a few folks > looking at private implementations of the older module with OpenSSL 1.1.x, but > definitely not official. > Yes, only 1.0.x atm. The

Re: Making rpm5 work with dnf

On 12/28/16 8:25 AM, Jeffrey Johnson wrote: > >> On Dec 28, 2016, at 7:02 AM, Alexander Kanavin >> wrote: >> >> On 12/27/2016 08:00 PM, Jeffrey Johnson wrote: >> >>> FYI: most of the openssl-1.1.0 port in rpm is now done. >>> >>> I’ve done “Do no harm

Re: Making rpm5 work with dnf

> On Dec 13, 2016, at 11:09 AM, Jeffrey Johnson wrote: > >> >> On Dec 13, 2016, at 8:34 AM, Alexander Kanavin >> > > wrote: >> >> On 12/09/2016 06:11 PM, Jeffrey Johnson wrote: >>> Good: you appear

Re: Making rpm5 work with dnf

> On Dec 13, 2016, at 8:34 AM, Alexander Kanavin > wrote: > > On 12/09/2016 06:11 PM, Jeffrey Johnson wrote: >> Good: you appear to have +beecrypt (for digests) and +libtomcrypt >> (recommended >> because of ECDSA and stable) and +openssl (what Yocto wants

Re: Making rpm5 work with dnf

On 12/09/2016 06:11 PM, Jeffrey Johnson wrote: Good: you appear to have +beecrypt (for digests) and +libtomcrypt (recommended because of ECDSA and stable) and +openssl (what Yocto wants last I heard). Speaking of openssl, it was actually quietly being disabled, because I didn't have the -dev

Re: Making rpm5 work with dnf

> On Dec 9, 2016, at 10:23 AM, Alexander Kanavin > wrote: > > … Good. >> There may be some issues with bison/flex in rpmdb (its WIP, the targets >> aren’t critical), >> and perl-URPM likely should be nuked (rm -rf perl-URPM). > > This is the latest

Re: Making rpm5 work with dnf

On 12/08/2016 07:53 PM, Jeffrey Johnson wrote: 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) and building

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

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 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 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 Dec 7, 2016, at 11:28 AM, Alexander Kanavin > wrote: > > On 12/07/2016 06:22 PM, Alexander Kanavin wrote: > >> checking whether to build with Perl ExtUtils::Embed library... no >> ++ executing failure action >> ++ searching location: /usr/lib64 >>

Re: Making rpm5 work with dnf

On 12/07/2016 06:22 PM, Alexander Kanavin wrote: checking whether to build with Perl ExtUtils::Embed library... no ++ executing failure action ++ searching location: /usr/lib64 configure: error: Unknown location specification /usr/lib64 I'm on Debian Testing, which does not have /usr/lib64 - I

Re: Making rpm5 work with dnf

On 12/02/2016 07:01 PM, Jeffrey Johnson wrote: Building RPM from CVS — once you have decided options and installed pre-requisites) — is mostly this cd rpm ./devtool checkout ./devtool somestanza Choosing options and installing pre-requisites is far from easy however.

Re: Making rpm5 work with dnf

> On Dec 5, 2016, at 9:09 AM, Alexander Kanavin > wrote: > > On 12/02/2016 07:01 PM, Jeffrey Johnson wrote: >> What I need is to be able to see what cmake options you are using in order >> to be able to build dnf pre-requisites without having to checkout (or

Re: Making rpm5 work with dnf

On 12/02/2016 07:01 PM, Jeffrey Johnson wrote: What I need is to be able to see what cmake options you are using in order to be able to build dnf pre-requisites without having to checkout (or install) OpenEmbedded, Sure, yes, but I guess you don't need them right now? OK. This is either

Re: Making rpm5 work with dnf

On 12/01/2016 08:35 PM, Jeffrey Johnson wrote: There is the additional porting issue that libhif has pre-requisites, including (at least) rpm rpm-python libsolv librepo that will need to be shared for a successful porting collaboration. FWIW, I've built and

Re: Making rpm5 work with dnf

> On Nov 30, 2016, at 7:30 AM, Alexander Kanavin > wrote: > > On 11/29/2016 06:02 PM, Jeffrey Johnson wrote: > >> Apologies, I’m new to project/repository management thru github. >> >> Should be fixed. >> >> We may have to iterate thru ssh key exchange etc

Re: Making rpm5 work with dnf

> On Nov 30, 2016, at 7:42 AM, Alexander Kanavin > wrote: > >> >> (aside) >> For starters, RPM5 uses keyutils(8), which has some hope of refactoring >> _ALL__ pubkey >> management out of _ALL_ RPM tool chains by writing a helper that is invoked >> by the

Re: Making rpm5 work with dnf

> On Nov 30, 2016, at 7:42 AM, Alexander Kanavin > wrote: > > On 11/29/2016 06:31 PM, Jeffrey Johnson wrote: >> The fundamental issue is that can only provide compile time >> API compatibility. >> >> That’s fine for apparently simple projects that only

Re: Making rpm5 work with dnf

On 11/29/2016 06:02 PM, Jeffrey Johnson wrote: Apologies, I’m new to project/repository management thru github. Should be fixed. We may have to iterate thru ssh key exchange etc etc soon too, depending on what is needed. Thanks, I've rearranged the branches a little bit: - your OS X build

Re: Making rpm5 work with dnf

> On Nov 29, 2016, at 9:49 AM, Alexander Kanavin > wrote: > > On 11/28/2016 06:35 PM, Jeffrey Johnson wrote: >> 2) There are several repetitive cosmetic (but annoying) API differences. >> These problems could (almost) be handled with some #defines >>

Re: Making rpm5 work with dnf

> On Nov 29, 2016, at 10:10 AM, Alexander Kanavin > wrote: > > On 11/28/2016 06:35 PM, Jeffrey Johnson wrote: > >> Make yourself happy with libhif: all of my work was largely exploratory >> assessing what issues need to be solved. Feel free to clobber

Re: Making rpm5 work with dnf

On 11/28/2016 06:35 PM, Jeffrey Johnson wrote: Make yourself happy with libhif: all of my work was largely exploratory assessing what issues need to be solved. Feel free to clobber anything I checked in to start getting an easily updated master branch. I’ll create a “macports” branch for my

Re: Making rpm5 work with dnf

On 11/28/2016 06:35 PM, Jeffrey Johnson wrote: 2) There are several repetitive cosmetic (but annoying) API differences. These problems could (almost) be handled with some #defines * the “match iterator” rpmmi* interface for rpmdb retrieval * the “problem

Re: Making rpm5 work with dnf

> On Nov 28, 2016, at 11:35 AM, Jeffrey Johnson wrote: > > > Yes, there were quite a few checkins since I created the forks. I updated all > the > repositories that did not need merging this weekend (but that wasn’t libhif). > rpm5/libhif:master is no sync’ed with “upstream”.

Re: Making rpm5 work with dnf

> On Nov 28, 2016, at 9:28 AM, Alexander Kanavin > wrote: > > On 11/26/2016 01:07 AM, Jeffrey Johnson wrote: >> FWIW, your invitation expired or is otherwise unusable (but at least >> I can read your code, todo++). > > Yeah, I pressed the button on github