2017.06.09 22:05 "Re: [Tiff] [PATCH] Unix/Linux CI support for GitHub and Travis", by Aaron Boxer

+1 for GitLab. Very happy with my account there.

On Fri, Jun 9, 2017 at 6:00 PM, Roger Leigh <rleigh@codelibre.net> wrote:

On 09/06/17 22:23, Even Rouault wrote:

> On vendredi 9 juin 2017 22:10:49 CEST Roger Leigh wrote:
>
> > On 09/06/17 14:18, Bob Friesenhahn wrote:
>
> > > On Fri, 9 Jun 2017, rleigh@codelibre.net wrote:
>
> > >> Thank you. One problem I noticed is that the build/travis-ci script
>
> > >> does not have executable permissions, which is needed to build. I
>
> > >> think with CVS that requires a chmod +x of the ,v file in the
>
> > >> repository if was not set when initially added.
>
> > >
>
> > > This seems to be a shell script which wants to be run with /bin/sh.

>> As

>
> > > such, it could be executed like '/bin/sh build/travis-ci' (or

>> whatever

>
> > > is needed for the context in which it is used) without any execute

>> bits

>
> > > set. This would also help for operating systems or filesystems which
>
> > > have no notion of an execute bit.
>
> >
>
> > If it's not possible to tweak the executable bit, I can certainly

>> switch

>
> > to invoking the script by hand. Since it's only ever going to be run on
>
> > Unix platforms via the .travis.yml, we don't need to worry about
>
> > filesystems with no execute bit.
>

> Yes please do so. The adminstrator has just informed me that they have > issues to SSH connect to the server currently.

>>

That doesn't sound good, hope they regain access soon. Related to that, is there any plan to move fully over to git? The existing mirror works pretty well; all my recent patches are generated directly with it. Could we create a libtiff organisation on GitHub or GitLab? Unfortunately, "libtiff" is taken on github, as is "tiff". But libtiff is available on GitLab.

I've attached the patches to invoke the script directly (0002) plus the original fixes (0001).