Hi team,
please, check out the issues. They were updated recently (or just
waiting for the review):
https://pagure.io/lib389/issue/77
https://pagure.io/lib389/issue/raw/files/6047ac156e06192837271afc2770a83f7f3206400669537bb1d8f43ab7b9a434-Guidelines-for-using-pytest-and-lib389_47541162.html
http
https://pagure.io/389-ds-base/issue/48081
https://pagure.io/389-ds-base/issue/raw/files/f42429499528aa390d9bbaa02ed82eae90e693866a6456beaa04b4cd0eb9911c-0001-CI-tests-PasswordCheckSyntax.patch
___
389-devel mailing list -- 389-devel@lists.fedoraproject.or
Hi William,
On Tue, Aug 01 2017 at 16:00:23 +1000, William Brown wrote:
> Hi all,
>
> Last night on IRC we were discussing the curious case of lib389. I think
> this is a discussion we should have at some point.
>
> The question really boils down to - "is lib389 a seperate project? Or is
> it part
On Tue, Aug 01, 2017 at 04:00:23PM +1000, William Brown wrote:
> My vote is to merge them. I came to this decision because I believe that
> this will make development against multiple branches easier with regard
> to testing and backport of patches. For example, we'll know that lib389
> that's insi
https://pagure.io/389-ds-base/issue/48081
https://pagure.io/389-ds-base/issue/raw/files/2411b2d29d9ffe07a512347365b1085f8743634aa431a8fb663a3151a7429dae-0001-CI-tests-PasswordCheckSyntax.patch
___
389-devel mailing list -- 389-devel@lists.fedoraproject.or
https://pagure.io/lib389/issue/87
https://pagure.io/lib389/issue/raw/files/9d484648d1fd332992c9404869d5b34b57688775c2a2f0223da0dda4ea67a401-0001-Ticket-87-Update-accesslog-regec-for-HR-etimes.patch
___
389-devel mailing list -- 389-devel@lists.fedoraproj
On Tue, 2017-08-08 at 08:00 +0200, Bernhard M. Wiedemann wrote:
> in order to make builds reproducible.
> See https://reproducible-builds.org/ for why this is good
> and https://reproducible-builds.org/specs/source-date-epoch/
> for the definition of this variable.
> ---
> buildnum.pl | 2 +-
> 1
> >
> > -- Merging lib389 to 389-ds-base
> >
...
> > * Testing DS is guaranteed to work. Right now we have rapid change in
> > lib389 and the tests in say 1.3.5 or 1.2.11.x are unlikely to work with
> > latest lib389.
> Another problem here is that tests are not backported to the older
> branches.
Hi,
While at pyconau I was very quiet - because I was working toward a major
goal that I have had for a while.
This patch allows a perl-less install of the 389-ds server:
https://pagure.io/389-ds-base/issue/49348
https://pagure.io/389-ds-base/issue/raw/files/fe5ffea4d8cbcd9f0a806aecf39d523684ece
