[Pki-devel] Testing on Fedora 20

[Nathan Kinder]

On 09/10/2013 11:02 AM, Ade Lee wrote:
> Hi guys,
>
> Sending to internal because there are some machine names here ...
>
> I have been testing dogtag on fedora 20.  There are a number of problems
> right now, for which I am in the process of resolving and creating
> patches.
>
> In particular, resteasy has been upgraded to version 3.0.3., which
> contains support for JAX_RS 2.0.  JAX_RS 2.0 has a specification for
> client side API as well as interceptors/filters.  As a result, a number
> of the calls we currently make have been changed or deprecated.  I have
> a patch to resolve this and allow us to build which I will post shortly.
>
> There are also changes to the tomcat startup scripts.  Having the dogtag
> instance start up correctly will require changes to pkispawn, the
> startup scripts and maybe others.  Still working through those ...
>
> In any case, all these changes will need to be checked into 10.1
> eventually, and the build in F20 will need to be rebased to 10.1.  At
> ths point, though, in order to develop on 10.1, you will need to have a
> fedora 20 machine.
>
> We do need to do this rebase and make this switch sooner rather than
> later so that we can shake out any f20 bugs.  On the other hand, f20 is
> not yet in alpha phase (should be there soon).  To mitigate the
> risk/delay in 10.1 development, we could:
>
> 1. Just make the switch.  As soon as I can build and run pkispawn to
> create a CA (and do basic tests) on F20, check in - and have everyone go
> to F20.
>
> 2. Create a branch off master for continued 10.1 work for those who want
> to continue on F18/F19, at least temporarily.
>
> FWIW, I'm for option 1.  It did not take too long for me to create an
> F20 machine, and I have been able to run eclipse and compile there with
> no problems.
+1.  I think we should just go with option 1.  Dogtag 10.1 is targeted 
for F20 and later only anyway.
>
> Below are instructions on how I did it:
>
> 1. Create an F19 machine.  In my case, I created a VM in the IDM lab
> using the f19-developer-template.  If you guys have not used the IDM
> lab, I strongly recommend it.
>
> 2. Add the following file: /etc/yum.repos.d/rhel20.repo
>
> [fedora20]
> name=Fedora 20 - $basearch
> failovermethod=priority
> baseurl=http://download.fedoraproject.org/pub/fedora/linux/development/20/$basearch/os/
> mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-20&arch=$basearch
> enabled=1
> #metadata_expire=7d
> gpgcheck=1
> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch
>
> [fedora20-debuginfo]
> name=Fedora 20 - $basearch - Debug
> failovermethod=priority
> baseurl=http://download.fedoraproject.org/pub/fedora/linux/development/20/$basearch/debug/
> mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-debug-20&arch=$basearch
> enabled=0
> metadata_expire=7d
> gpgcheck=1
> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch
>
> [fedora20-source]
> name=Fedora 20 - Source
> failovermethod=priority
> baseurl=http://download.fedoraproject.org/pub/fedora/linux/development/20/source/SRPMS/
> mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-source-20&arch=$basearch
> enabled=0
> metadata_expire=7d
> gpgcheck=1
> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch
>
> 3. yum install fedup
> 4. setenforce 0   --> prob not necessary, but thats how I had it.  In
> fact, I'd do all of this in permissive just to be safe.
> 5. fedup-cli --network 20 --instrepo fedora20
> 6. reboot
> 7. I needed to make sure I had the latest versions of selinux-policy,
> selinux-policy-targeted and libsemanage.  These are the latest ones in
> koji (3.12.1-79) and libsemanage-2.1.10-9.fc20.x86_64.  In my case, I
> had to actually download them.
>
> Comments?
>
> Ade
>
>
> _______________________________________________
> Pki-devel mailing list
> Pki-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/pki-devel