On 12/15/2015 05:04 PM, Aleš Mareček wrote:
On a second thought, increasing the build number may be useful. I just
ran into the cyclic import issue again. Until I looked into the rpm I
wasn't sure if I got the newer packages.
----- Original Message -----
From: "Milan Kubík" <mku...@redhat.com>
To: "Petr Vobornik" <pvobo...@redhat.com>
Cc: "freeipa-devel" <email@example.com>, "Ales Marecek"
Sent: Tuesday, December 15, 2015 4:53:18 PM
Subject: Re: [Freeipa-devel] Testing FreeIPA 4.3 for GA
On 12/15/2015 04:35 PM, Petr Vobornik wrote:
On 12/15/2015 01:05 AM, Petr Vobornik wrote:
Blocking patches for FreeIPA 4.3 were pushed, ipa-4-3 branch was
created. Master branch is ready for 4.4 development.
A build is available for testing in my pvoborni/freeipa-4-3 COPR repo
 until the official 4.3 repo is created. The repo contains only this
build. The build is not pure upstream ipa-4-3 branch but rather a build
which will go to Fedora rawhide and official 4.3 copr repo - Fedora
downstream spec with the SELinux workaround applied .
* https://fedorahosted.org/freeipa/ticket/5469 - requires fix in PKI
* https://bugzilla.redhat.com/show_bug.cgi?id=1289930 - SELinux Policy
update needed for connection check
I have started drafting release page .
Copr contains a rebuild with a patch for ticket:
The build has exactly the same version as the one before. Ales, Milan,
do we want to differentiate that somehow?
The job uses fresh install of the rpms. The same version and build
shouldn't be a problem.
+1, I don't see any issue to use the "same" (not-yet-released) version.
Manage your subscription for the Freeipa-devel mailing list:
Contribute to FreeIPA: http://www.freeipa.org/page/Contribute/Code