#49172 test_schema_comparewithfiles failing on Nonetype
Closed: wontfix Opened by firstyear.

Issue Description

This issue has two points. First, is that we were not handling conditions where schema was empty, so we got a none type back.

Second, schema handling moves in 1.3.6, to the join systemschema dir and schemadir. We should be reflective of this in our test, which requires and update to the defaults.inf to list the path.


Metadata Update from @firstyear:
- Custom field reviewstatus adjusted to new
- Custom field type adjusted to defect

Metadata Update from @firstyear:
- Custom field reviewstatus adjusted to review (was: new)

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to ack (was: review)

commit f78663990f821627db181834baf708ce492cf0d2
To ssh://git@pagure.io/389-ds-base.git
1d0ff1d..f786639 master -> master
commit decfdbd8900a3f44fc65b9232d0424bb54d96626
To ssh://git@pagure.io/lib389.git
de0ae7c..decfdbd master -> master

Metadata Update from @firstyear:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

Can't create any instance with latest master:

>       from lib389.schema import Schema
E         File "/mnt/tests/rhds/tests/upstream/src/lib389/lib389/schema.py", line 41
E           if ds_is_newer(1.3.6.0):
E                              ^
E       SyntaxError: invalid syntax

Metadata Update from @vashirov:
- Issue status updated to: Open (was: Closed)

Reviewed by William.
To ssh://pagure.io/lib389.git
decfdbd..93393a9 master -> master

Metadata Update from @vashirov:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/2231

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

Metadata