DMARC-Filter:	OpenDMARC Filter v1.4.2 delorie.com 51MBSiGM1375379
Authentication-Results:	delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results:	delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 51MBSiGM1375379
Authentication-Results:	delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=wkm2A5YD
X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 413CB3858C30
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1740223723;
	bh=LYJraujW6cX8GxOXElp4QzeF5Jxwu3RMsIkTl7txOWo=;
	h=To:Subject:In-Reply-To:References:Date:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=wkm2A5YD01j6Q4bRQYMlgvShrxN6yp7kOOiBny/ObOOKtXOvS3qvW0cNjDl1Rvoig
	5C62IFpGuKvHXxo0TYUGSuu4adFAg14HCDyrIG+rBbv5SErcGfZhS0679K/qqaUnNx
	A5yTmR78bzWzi3PMkAveOxxM0ba9czdkB7TObgHo=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org E60473858D20
ARC-Filter:	OpenARC Filter v1.0.0 sourceware.org E60473858D20
ARC-Seal:	i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1740223656; cv=none;
	b=E3PXr36tRe8tDQc9uf8hFVJjUBL7VFR6gYPmR2RaqspsBSZNItJqZnojUnlN0Xoz2Ix82miD1SyWfsWZQ8z+auh1f0hVhd/FF+d1nD0jKt7pHSvMT9/spcAq3l6iiU1WntjwYcJsbmWLLCelevsg7ry8zBJ1uKD9mIr0T8SVMcQ=
ARC-Message-Signature:	i=1; a=rsa-sha256; d=sourceware.org; s=key;
	t=1740223656; c=relaxed/simple;
	bh=p9IVRhdfe0vod/qu4lF0zgCD1bP8smB+tG9YWQ0+/IQ=;
	h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version;
	b=Tmsw9fVnY5RA8dNnKDdjeH5ZV6KNLDv/wf0BTokjPKKHH9GoZ35RUON0eCr5/bS5YbyT+7AGTxW10hd5l4XtpSDiAgoPq3tMxTHjqvJssmrla3fopgU5SBdrXWowfG8ieuUEnKxLipAw3/lRWXXlmZtbyyZlmG3EXnUUCuJGDhE=
ARC-Authentication-Results:	i=1; server2.sourceware.org
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org E60473858D20
To:	cygwin AT cygwin DOT com
Subject:	Re: Making a Cygwin 3.5.8 release? Fwd: All sparse file fixes
	available in cygwin-3_5-branch?
In-Reply-To:	<CALXu0UckhFdoJ1gsgmKq3CJ61+BKxr4nCqD2GbQoXTQ=1FQ-iw@mail.gmail.com>
	(Cedric Blancher via Cygwin's message of "Sat, 22 Feb 2025 08:17:00
	+0100")
References:	<CALXu0Ud9WJUfS2YgZNbAOBfs3u=27E+4c3tOSYkSApx08_1-Cw AT mail DOT gmail DOT com>
	<Z7Rmrl3tmQ5NjGAc AT calimero DOT vinschen DOT de>
	<CALXu0UdHm0uZjBqL0BaZw59KkM03wViHih5Qyc8WS0hinGraQg AT mail DOT gmail DOT com>
	<CALXu0UfQTmBMkB3Nt=+5vS-XazUaKuqgk7Tpa=5rO=W2FoXWJQ AT mail DOT gmail DOT com>
	<c13a115a-470c-4968-bebe-cbf5c9d2cf3f AT SystematicSW DOT ab DOT ca>
	<CALXu0UckhFdoJ1gsgmKq3CJ61+BKxr4nCqD2GbQoXTQ=1FQ-iw AT mail DOT gmail DOT com>
Date:	Sat, 22 Feb 2025 12:27:26 +0100
Message-ID:	<87r03qz0bl.fsf@Gerda.invalid>
MIME-Version:	1.0
X-purgate-server:	smtpa08
X-purgate-type:	clean
X-purgate:	clean
X-purgate-size:	1776
X-purgate-ID:	155817::1740223650-2A763DD5-E873959A/0/0
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.30
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
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:	ASSI via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	ASSI <Stromeko AT nexgo DOT de>
Errors-To:	cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

Cedric Blancher via Cygwin writes:
> We are VERY concerned that this plan will backfire. Basically nothing
> here works right now, and we are still trying to determinate the root
> causes. Plural. Too many bugs.

I've said it before, but if you really didn't recognize it until now:

Cygwin is a following a rolling release distribution model, which means
it can literally break at any time and for any length of time.

Now, I've also used (and am still using, albeit on a smaller scale)
Cygwin in a corporate / production environment (which I belive is what
you are talking about when you say "here"), so these things are in my
view necessary to even think about such a deployment:

 - independent (internal) access to all sources and binaries
 - a separate test and build environment
 - periodic test builds of packages and Cygwin itself
 - full control over the package selection including version locks and
   the ability to roll back single packages or even full installs

In the above scenario you could either decide to hold off on an update
or fork and fix it yourself.  If you can't do either of that, then sorry
to say: this is first and foremost your problem and you get to keep the
broken pieces.  Secondly, correlation is not causation; you have AFAICS
not yet shown that there is a bug in Cygwin.  Even if there was, you
still do not get to command what the project does to handle that
situation.  If you want to help it along, at least send actionable bug
reports, reproducers would be better, better yet would be patches.
 

Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

-- 
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 -