[X2Go-Dev] Fedora builds in Jenkins
Hi everyone, Currently, Jenkins is building for the following versions of Fedora: 19 20 21 22 Rawhide (24) However, 19, 20 and 21 have all reached end-of-life. Fedora 21's EOL was 2015-12-01. Unless there are any objections, I will disable builds for Fedora 19, 20 and 21 next weekend. I will also enable builds for 23 at that time. Enabling builds for 23 will probably consist of copying over /etc/mock/*.cfg files from a working Fedora ( or EPEL) RPM because the "mock" package in Debian is out-of-date and does not provide them. This is how Mike#1 and I enabled builds for F21 and F22 in the 1st place.[1] [2] [1] https://packages.debian.org/wheezy-backports/all/mock/filelist [2] https://packages.debian.org/jessie/all/mock/filelist -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] Fedora builds in Jenkins
On 01/23/2016 08:55 AM, Mihai Moldovan wrote: On 23.01.2016 04:07 PM, Mike DePaulo wrote: Currently, Jenkins is building for the following versions of Fedora: 19 20 21 22 Rawhide (24) However, 19, 20 and 21 have all reached end-of-life. Fedora 21's EOL was 2015-12-01. Unless there are any objections, I will disable builds for Fedora 19, 20 and 21 next weekend. We've been discussing this on a previous dev meeting. While these versions reached EOL, carrying them as long they do not break (and dropping them IF they break) causes no harm. On the pro side, if we were to disable them, we'd save about 30 minutes build time for each version. So far, these old versions haven't caused me a lot of pain and FC19 is actually a bit special, too, being the FC version EPEL6 was based upon. But you have separate EPEL builds already, right? So I don't see the point in keeping F19 for that reason. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] libzip - do we even use it?
Hi Alex, I am working on releasing a new build of X2Go Client for Windows 4.0.5.0-x with security updates, when I noticed that libzip has a security update available. Upon further investigation, it looks like we do not even use libzip: 1. "Dependency Walker" shows that we do not link X2Go Client for Windows against it. 2. X2Go Client for Windows 4.0.5.0 seems to work without it. 3. X2Go Client for Windows 4.0.0.3 (the last release before I resumed maintianing it) didn't even include it. 4. I grepped the "x2goclient" source tree for "libzip" at 3.99.0.0, 4.0.0.0 and 4.0.5.0 and there were no matches. You were the one who updated the wiki to state that we need libzip, so I figured I would ask you. http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient?rev=1363699682 -Mike ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] Fedora builds in Jenkins
On 23.01.2016 04:07 PM, Mike DePaulo wrote: > Currently, Jenkins is building for the following versions of Fedora: > 19 > 20 > 21 > 22 > Rawhide (24) > > However, 19, 20 and 21 have all reached end-of-life. Fedora 21's EOL > was 2015-12-01. > > Unless there are any objections, I will disable builds for Fedora 19, > 20 and 21 next weekend. We've been discussing this on a previous dev meeting. While these versions reached EOL, carrying them as long they do not break (and dropping them IF they break) causes no harm. On the pro side, if we were to disable them, we'd save about 30 minutes build time for each version. So far, these old versions haven't caused me a lot of pain and FC19 is actually a bit special, too, being the FC version EPEL6 was based upon. Sure, we could disable these builds, but does it help us any? Back then, I opted to keep them and the other seemed to be on board, because they are not causing additional maintenance or anything else. If you feel strongly about it, bring the discussion up again (mailing list shall be good enough, I guess, but other people might object...) I don't care one way or the other personally, keeping them vs. disabling them makes no difference for me. > I will also enable builds for 23 at that time. > > Enabling builds for 23 will probably consist of copying over > /etc/mock/*.cfg files from a working Fedora ( or EPEL) RPM because the > "mock" package in Debian is out-of-date and does not provide them. > This is how Mike#1 and I enabled builds for F21 and F22 in the 1st > place.[1] [2] NACK, please let me handle this. I've already replaced all mock config files once - because the Debian package only shipped outdated ones - with those from the mock upstream repository. Further, the config files need to be copied and other changes applied as well, so it's not a trivial replacement process. Mihai signature.asc Description: OpenPGP digital signature ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
