Hi Michael, ----- Original message ----- > On Dec 21, 2014 8:33 PM, "Michael DePaulo" <[email protected]> wrote: > > > > Hi Mike#1 and others, > > > > I want to rebuild the "main" packages for EPEL 5 so that we can fix bug > #699. I've already rebuilt and tested the "nightly" EPEL 5 packages; bug > #699 was successfully fixed on them. > > > > However, it appears that in order to rebuild any package for EPEL 5, I > must rebuild them for every release of every Linux distro. > > http://jenkins.x2go.org:8080/view/All%20Releases/?auto_refresh=false > > > > Should I just do that via Jenkins? Or would it be disruptive? For > example, would users be prompted to update even when they do not have > to? I think that would happen for EPEL users at least, because the > nightly EPEL 5 nx-libs packages now have "git20141222" in their version > strings. (nx-libs.git was last updated 2 weeks ago, but I rebuilt it > under nightly on 2014-12-22 (UTC +1:00).) > > > > -Mike > > Mike#1, please advise. > > -Mike#2
for special builds I use the x2go-admin account on Japsand, the command should be similar to this NO_DELAY=1 FORCE_BUILD=1 RPM_BUILD_FOR="epel:5" x2go-build+upload-rpm-package nx-libs main Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976148 GnuPG Key ID 0x25771B13 mail: [email protected], http://das-netzwerkteam.de _______________________________________________ x2go-dev mailing list [email protected] http://lists.x2go.org/listinfo/x2go-dev
