X-Recipient: archive-cygwin AT delorie DOT com
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org E60833857C65
Authentication-Results: sourceware.org; dmarc=none (p=none dis=none)
 header.from=ext.eeas.europa.eu
Authentication-Results: sourceware.org; spf=pass
 smtp.mailfrom=Panagiotis DOT KAVALAGIOS AT ext DOT eeas DOT europa DOT eu
From: "KAVALAGIOS Panagiotis (EEAS-EXT)"
 <Panagiotis DOT KAVALAGIOS AT ext DOT eeas DOT europa DOT eu>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: RE: [cygwin] Re: jansi bug adds spaces to output from maven build
 using java on w10
Thread-Topic: [cygwin] Re: jansi bug adds spaces to output from maven build
 using java on w10
Thread-Index: AQHW44N13Peq6ZD3skK+z5UGS1o29KoaNCUQ///8rICAAB2kUA==
Date: Wed, 6 Jan 2021 09:14:57 +0000
Message-ID: <cb6509362a7e46aa9cdcf95e6a0b78bb@BELBRU-EXMP101.eeas.europa.eu>
References: <CAPjM6w-mPf5h=xR2MK-cu-Eb7g313A3cZBcOuQ=ygTL2_dOmFw AT mail DOT gmail DOT com>
 <20201229223820 DOT 7a010585bbfd0973faf618ae AT nifty DOT ne DOT jp>
 <c8ad9cbf914e4594bc8ba9c15e61e882 AT BELBRU-EXMP101 DOT eeas DOT europa DOT eu>
 <011701d6e37a$420c83c0$c6258b40$@pdinc.us>
 <88c1f732eb6f4d29913d550e9bd8d58b AT BELBRU-EXMP101 DOT eeas DOT europa DOT eu>
 <bef1bdda-0296-ef61-39e5-e2525276a127 AT SystematicSw DOT ab DOT ca>
 <a62b788116ea47adb39e160d01404216 AT BELBRU-EXMP101 DOT eeas DOT europa DOT eu>
 <4140720e-16c9-215c-bc88-85b30a269b7f AT SystematicSw DOT ab DOT ca>
In-Reply-To: <4140720e-16c9-215c-bc88-85b30a269b7f@SystematicSw.ab.ca>
Accept-Language: en-GB, el-GR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.51.5.118]
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737
 definitions=2021-01-06_05:2021-01-06,
 2021-01-06 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam
 score=0 mlxlogscore=886
 adultscore=0 bulkscore=0 lowpriorityscore=0 impostorscore=0 mlxscore=0
 phishscore=0 priorityscore=1501 suspectscore=0 clxscore=1015
 malwarescore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1
 engine=8.12.0-2009150000 definitions=main-2101060056
X-Spam-Status: No, score=-4.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 KAM_NUMSUBJECT, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

> -----Original Message-----
> From: Cygwin <cygwin-bounces AT cygwin DOT com> On Behalf Of Brian Inglis
> 
> On 2021-01-06 00:53, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
> > I know exactly what are my options and believe me, there are more than
> > the one reported here. In my case, we need to update Cygwin Git in our
> > machines, so a solution to stick to 3.0.7 and update only Git is also fine.
>  >
> > However, we have performed a full update and found the issue with
> > maven in our pilot phase. My interest is not personal for my machine,
> > but to prepare a Cygwin package to push the update to all developers.
> > I need only to know when there will be the new release that will
> > include a fix for this issue as I am not aware of the Cygwin release
> > schedule. Based on the information, we can decide what option fits better
> our institution.
> As Cygwin is an unfunded all-volunteer project, there are no expected
> response times for issues or release schedules, and responses and releases
> happen whenever package maintainers have sufficient interest to read the
> list or reason to issue an update, and enough free time in their personal lives
> to respond or complete the build, testing, documentation updates,
> packaging, and release processes. Some of us try to help them out by trying
> to provide timely and useful responses with suggestions or workarounds.
> 
> As you are a member of an organization with funding, it is up to you to do
> whatever your organization requires in terms of timing and can support
> internally, including using snapshots, or building your own package releases
> from sources.

I understand that even a rough estimation is not possible and we have to forget the solution 2 of a Cygwin release. We will choose among the other solutions proposed so far. Thank you very much.

Panos

Application Architect
CONSULIAT (under contract with the EEAS)
BA.BS.3.IS
Office: EEAS B100 Floor 5 Area 048
Rue Belliard 100, 1000 Brussels
Phone: +32 2 584 6017

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