[X2Go-Dev] (Jenkins Question) Rebuilding "main" packages for EPEL 5.

[Michael DePaulo]

On Dec 21, 2014 8:33 PM, "Michael DePaulo" <mikedep333 at gmail.com> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x2go.org/pipermail/x2go-dev/attachments/20141231/a2c82f78/attachment.html>