X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 7FFA9385840A
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1632555341;
	bh=1zrDUx8Ea3PwAKnaerRfIxSVDP3jsa7H0UWtyIz9D4g=;
	h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=BLaC3Vp8LcVa7I8LbV96Dygdc/eRBCqPl1D8JEUaIkuocGDHN4R3cb9L3KdY5I8IQ
	dg+2mWljCTcI4jTGlyUCgAu/E1mT2ZdqwHKi1gbW8eXVaOUpHTfyxrv7tl/e7seCi7
	uyAKxHalpQZbquS7degRUgPxujVrEUskOykjS5c4=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org B86BC3858403
X-UI-Sender-Class:	01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Message-ID:	<964c99d4-fec2-789f-f730-5f98d3aa77c0@gmx.com>
Date:	Sat, 25 Sep 2021 10:34:57 +0300
MIME-Version:	1.0
User-Agent:	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
	Thunderbird/91.1.1
Subject:	Re: cloc: hashbang header has "perl" twice
To:	cygwin AT cygwin DOT com
References:	<5ab467d9-5f0e-2a80-d509-35b899c0e07b AT gmx DOT com>
In-Reply-To:	<5ab467d9-5f0e-2a80-d509-35b899c0e07b@gmx.com>
X-Provags-ID:	V03:K1:MPeWQioS82DMDa1r2KdQguaMz87agONJWYO1bgPuDuo7QypKxfE
	j4jVIcinf34Fbw6OxEd3G6e6edU211hlFVn7NJajl7ykoH40UqwmWpiK5qmqjmkRqI/ZNf8
	pFzO0VHcYOKaNrDtNOuTn81ayaQyDsC9mhFdNiqTX5N1eWP1Cl4OXrkZxwC9WoEHTpRG6gn
	LDOrn/03cfiPdkyJ1aG3w==
X-UI-Out-Filterresults:	notjunk:1;V03:K0:WlpwO0+Iw2o=:VE3D8A/dayzGFUxAqkhsnA
	cQ3IBNrw8IGaGhqsLBnVbGTtnlb5qYswHXIq/k6KM7J/YtcPvS3Tar5AqsaAoyY9ZpNpoccr2
	Q25Ewg4VRvyJV2sddhMkL383qCtok7iohB8xq6PKV9Mp92QJgC1DnRLOEuf2oPn8SHYnEWJFB
	tG2KZGOXpoHr8LVkWsyJcSqEBh1fsMmMYoEbUhCKf1bAdUE/KX8OJxbN8rlbO+w+xpeJRib3S
	P79nMEwskoG2cTXdTUzcIUs4uHPFQP5HKnxCEWchQOxoOlw/g1C/0Fm/MGoL3mOlgdvJvOvXy
	ZarI6mdKwhXR9lRJHUW6qkfU05Eg/7mr7O9j1cEEeek1GQypkMKfk65uh8Mx5YCPdIkBrx1Nl
	3vwcNOxAa4DgANt+jnAXq1QEfmyOzzk3lgCnqUDXYGbY8mixNYbN/k1Uxg+oP/1eOux4cv0fj
	rtpVoLwQTpascmXG2um15eU2JBzv8NZ8Pc26/LXomC8yP4kuz/mEhyucDG/e5o5Cja9JA0xwN
	YWP2QdNnV3AwgbvuTqFmep70Zim4NVZs52YBsf9p/N+NnGZxhgPAwjCixYG14bAWoVNiCmrr5
	wOZ6yTEUBRt08qVLD//pyJOf0qLwBdiSkhaHCOtHkA8fgxKX2O/qNLmroR0Wf2eoxC2wgxH+A
	xNCyeuyTXNNc9SLvVOwDrxxGWmy5IucfdGZzbDMqrMoQcuN8+vDHU38X1Hvk4hfFDTxt/eiE5
	AE4YCcUozFhyt5i84JLnF+ePA9jrNMTQ2wjDg8NW+UTjANbAxl5ERYBb0+84ew85hNKBAcW2o
	p65JLt/BjT7Jj8uzizjAufMXA1R2U0w8zbkI5eM/36b9bvhApFVHW20VDwt3ZIZtYS8YF2ZH9
	v0ch0pzUGNdgCF4M/neJ3siOF/sEFlN3wsiP4pQY2dDIFVyXE6BNlK2H0hC9vPFaLjE322aCy
	gMhpagr+9SyMf3iekrzBWcG2k9QYIJOxjeI98tmDNIZKS691LEKDl3IRzZThiS6abXaSVt/KA
	Bg74o0ATcbMzky5sfTVCNkvE5uM5Lf4ykFT2XtPNsRtXKe428ftk/mYf5vN5GQy/L6gkQ8TPc
	9h+PVq4AnrRyXs=
X-Spam-Status:	No, score=2.8 required=5.0 tests=BAYES_00, BODY_8BITS,
	DKIM_SIGNED, DKIM_VALID, FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,
	NICE_REPLY_A, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE,
	SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4
X-Spam-Level:	**
X-Spam-Checker-Version:	SpamAssassin 3.4.4 (2020-01-24) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Eyal Rozenberg via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Eyal Rozenberg <eyalroz1 AT gmx DOT com>
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 18P7Zgw3028929

I'm not sure how bug reporting "etiquette" works here on the list, but -
I was sort of expecting an acknowledgement. Or - was I wrong to post my
bug report here in the first place?

I have another bug (two actually) to report regarding meld, and I want
to get that report right and not have it lost in the noise.

Eyal

On 22/09/2021 17:20, Eyal Rozenberg via Cygwin wrote:
> I'm using:
>
> Package              Version                        Status
> cloc                 1.82+20190726+git608f376-1     OK
>
> updated today. The first line of /usr/bin/cloc is:
>
> #!/usr/bin/perl perl
>
> while it should just be:
>
> #!/usr/bin/perl
>
> (like it is on my Linux machine)
>
> Obviously this causes an error when running cloc:
>
> Can't open perl script "perl": No such file or directory
>
>
> I would also suggest that you consider using a newer version of cloc, as
> there have been several releases since 1.82
>
> Eyal
>

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -