[GeoMoose-users] Errors building geomoose from source

[Dan Little]

Ye ole Line Endings strike again. Thanks to @Jeff McKenna
<jmckenna at gatewaygeomatics.com> for the PR and GH action to check things!

On Tue, Apr 7, 2026 at 9:15 AM Christopher Hughes via GeoMoose-users <
geomoose-users at lists.osgeo.org> wrote:

> I'm assuming it's just an issue on Windows, and that it's dependent on how
> you've set up git. On my latest installs of git I've just chosen the
> default options for line endings, which were to convert to CRLF on
> checkout, and back to LF on commit.
>
> On one of my other servers I had it setup to make no changes to line
> endings - this issue doesn't show up on that server.
>
>
> --
> Chris Hughes
>
> GIS Analyst
> Lincoln County GIS Department
> 880 NE 7th St. l Newport, OR 97365
> Tel: (541) 574 1283
>
> ------------------------------
> *From:* GeoMoose-users <geomoose-users-bounces at lists.osgeo.org> on behalf
> of Jim Klassen via GeoMoose-users <geomoose-users at lists.osgeo.org>
> *Sent:* Tuesday, April 7, 2026 6:31 AM
> *To:* geomoose-users at lists.osgeo.org <geomoose-users at lists.osgeo.org>
> *Subject:* Re: [GeoMoose-users] Errors building geomoose from source
>
> I presume when we upgraded the checker that it now has a default rule
> about line endings.
>
> Do we need a .gitattributes file to with something like
>
>     *.less text eol=lf
>
> ??
>
> Are we doing sane things with normalizing line endings in the repo or is
> it a free-for-all?  (Either having git convert them for window or forcing
> everything to always be LF)?  I'd worry about converting them causing
> inconsistencies in the builds (in case we care), but not converting them
> causing notepad.exe to fail.
>
> Off the top of my head, I think the git default is to auto-detect if it
> think a file is a text file, and if so it will convert line endings on
> Windows.
>
> On 4/6/26 8:53 PM, Dan Little via GeoMoose-users wrote:
>
> Let me check on this in the morning. I suspect we got an errant formatting
> issue... I'm not having the problem locally but I've been juggling a lot of
> branches.
>
> On Mon, Apr 6, 2026 at 1:32 PM Christopher Hughes via GeoMoose-users <
> geomoose-users at lists.osgeo.org> wrote:
>
> I've run into a recent issue building geomoose from source (following the
> process at Developer Quickstart for Windows — GeoMoose documentation
> <https://cas5-0-urlprotect.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fdocs.geomoose.org%2f3.x%2fquickstarts%2fdevelop%2don%2dwindows.html&umid=1ed60d5d-3286-11f1-90f3-000d3a366e53&rct=1775568714&auth=dc2ed28abfc38f9dccdc580b0625a9783b471d36-c94480ab5042c1cc51d75acf6ad619e82cdd78cc>
> ).
>
> After cloning geomoose and running npm install, npm run build fails at the
> checking formatting part - it gives me formatting warnings for all the
> .less files with a comment to run Prettier to fix them, and then aborts.
> Running prettier on the files with warnings fixes the issues, and then npm
> run build succeeds. Looking at the changed files, it looks like it only
> changed the line endings.
>
> This doesn't happen when building on 3.15, only when building on the
> 3.15-beta.
>
> I was just curious if anyone else has run into this (it might be Windows
> specific). Running Prettier on the .less files fixes it, but it'd be nice
> to not have to do that each time.
>
> Chris
>
> --
> Chris Hughes
>
> GIS Analyst
> Lincoln County GIS Department
> 880 NE 7th St. l Newport, OR 97365
> Tel: (541) 574 1283
>
> _______________________________________________
> GeoMoose-users mailing list
> GeoMoose-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geomoose-users
>
>
> _______________________________________________
> GeoMoose-users mailing listGeoMoose-users at lists.osgeo.orghttps://lists.osgeo.org/mailman/listinfo/geomoose-users
>
>
> _______________________________________________
> GeoMoose-users mailing list
> GeoMoose-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geomoose-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20260411/d6404efe/attachment.htm>