RPM Community Forums

Mailing List Message of <rpm-users>

Re: Making rpm5 work with dnf

From: Jeffrey Johnson <n3npq@me.com>
Date: Tue 22 Nov 2016 - 17:10:16 CET
Message-id: <1C515DBF-83EF-48F7-AEEC-D455D2662258@me.com>

> On Nov 22, 2016, at 10:39 AM, Alexander Kanavin <alexander.kanavin@linux.intel.com> wrote:
> On 11/22/2016 05:16 PM, Alexander Kanavin wrote:
>> AttributeError: 'module' object has no attribute 'RPMTRANS_FLAG_NOCONTEXTS'
> There's a similar issue with RPMTRANS_FLAG_NOFILEDIGEST. If I patch these out from dnf, then dnf is at least able to start - I haven't run any of its unit tests yet.

Both NOFILEDIGEST and NOCONTEXTS are disablers unnecessary to dnf execution,
with alternative means to enable/disable other than through python bindings.

Note that the RPM5 SELinux implementation does not include or permit loadable modules.
A SELinux port is much more than exposing a NOCONTEXTS bit. NOFILEDIGEST also has
a slightly different  effect between rpm.org and rpm5.org.

Disabling SELinux is still common functionality however: setting NOCONTEXTS/NOFILEDIGEST to 0
is one way to achieve.

The fundamental porting problem (in both python modules) is how symbols are exposed.

The better way going forward is to set global values in __init__.py as needed.

Again: I cannot do much more than suggest porting approaches unless I can attempt reproducers.
Please try to expose your git repositories somehow, either publicly or privately.

73 de Jeff
> Alex
> ______________________________________________________________________
> RPM Package Manager                                    http://rpm5.org
> User Communication List                             rpm-users@rpm5.org
Received on Tue Nov 22 17:10:21 2016
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.