Re: TL;DR: About Distros, packages, Cygwin, volunteers

On 2021-01-04 21:37, Brian Inglis wrote: On 2021-01-04 08:11, Marco Atzeri via Cygwin wrote: On 04.01.2021 13:21, tommie.k...@alverservices.com wrote: But im struggling to see how I can upgrade openssl >1.1.1f Compliance checks state that we must have a more up to date version, I know that it

Re: OpenSSL

On 2021-01-04 08:11, Marco Atzeri via Cygwin wrote: On 04.01.2021 13:21, tommie.k...@alverservices.com wrote: But im struggling to see how I can upgrade openssl >1.1.1f Compliance checks state that we must have a more up to date version, I know that it exists (1.1.1g, 1.1.1h, 1.1.1i)

Re: [ITA] libspectre-0.2.9-1

On 05.01.2021 00:29, Lemures Lemniscati via Cygwin-apps wrote: On Mon, 4 Jan 2021 19:28:39 +0100, Marco Atzeri via Cygwin-apps On 04.01.2021 17:37, Lemures Lemniscati via Cygwin-apps wrote: On Tue, 05 Jan 2021 01:33:28 +0900, Lemures Lemniscati ITA for libspectre, which has been maintained by

Re: Is it possible to define the root directory in a cross compiled program

On 2021-01-04 18:34, Roger Kaufman wrote: When I cross compile the following program, opening /dev/null fails and instead the whole install path of /cygwin64/dev/null is visible. Is there a way to make fopen respect / as the root directory in a cross compiled program for windows? example

Is it possible to define the root directory in a cross compiled program

When I cross compile the following program, opening /dev/null fails and instead the whole install path of /cygwin64/dev/null is visible. Is there a way to make fopen respect / as the root directory in a cross compiled program for windows? example output... Roger@interocitor:~ $

Re: [ITA] libspectre-0.2.9-1

On Mon, 4 Jan 2021 19:28:39 +0100, Marco Atzeri via Cygwin-apps > On 04.01.2021 17:37, Lemures Lemniscati via Cygwin-apps wrote: > > On Tue, 05 Jan 2021 01:33:28 +0900, Lemures Lemniscati > >> ITA for libspectre, which has been maintained by Yaakov [1]. > >> > >> Now, the latest upstream of exif

Re: Setting env var CYGWIN for Cygwin service?

On Mon, Jan 4, 2021 at 3:08 PM Oleksandr Gavenko wrote: > /usr/bin/exim-config has line with: > > cygrunsrv -I exim -p /usr/bin/exim -e CYGWIN="${cygenv}" ... > > So it is the answer (as pointed by others). > > Still "procexp" doesn't show anything else besides PATH/WINDIR for "exim" > process.

Noticed that mintty starts non-login bash with "Win+R mintty Enter".

I interact with Cygwin via mintty launched as "Win+R mintty Enter". During first launch of "exim-config" script existed with an error: /usr/bin/exim-config: line 447: USER: unbound variable After looking into docs I got that mintty should be launched with a parameter "-". Probably it was

Re: Setting env var CYGWIN for Cygwin service?

On 2020-12-30, Oleksandr Gavenko via Cygwin wrote: > What way can I pass env var "CYGWIN" to the Cygwin service? Today I reinstalled Cygwin & Exim. "exim-config" script asked me: Enter the value of CYGWIN for the daemon: [] /usr/bin/exim-config has line with: cygrunsrv -I exim -p

RE: [cygwin] DD bug fails to wipe last 48 sectors of a disk

> From: Hashim Aziz > Sent: Monday, January 4, 2021 3:16 PM > > > From: Jason Pyeron > > Sent: 30 December 2020 1:35 AM > > To: mailto:cygwin@cygwin.com > > Subject: RE: [cygwin] DD bug fails to wipe last 48 sectors of a disk > > > > > -Original Message- > > >

[PATCH] cygport use shallow clone for branches and tags

--8<---cut here---start->8--- Subject: [PATCH] cygclass/git.cygclass: use shallow clones for branches and tags also --- cygclass/git.cygclass | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/cygclass/git.cygclass

Re: [RFE] calm needs to know about ZStandard compressed archives

Jon Turney writes: >> I think the right thing to do is to stop having actual packages for >> OBSOLETES and just emit the obsoltes: hint instead. > > Yeah, this change to cygport should be made and we can turn off > support for setup versions which don't understand the obsoletes: hint. The

Re: [ITA] libspectre-0.2.9-1

On 04.01.2021 17:37, Lemures Lemniscati via Cygwin-apps wrote: On Tue, 05 Jan 2021 01:33:28 +0900, Lemures Lemniscati ITA for libspectre, which has been maintained by Yaakov [1]. Now, the latest upstream of exif is 0.6.22 [2]. This line should be... ``Now, the latest upstream of libspectre

Re: Postinstall script errors for man* packages

Allen Hewes via Cygwin writes: > I think the recent man* package update has an issue in the postinstall script: Yes, the script got broken when it was generated for packaging. It's hopefully fixed now. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

Matt D. via Cygwin writes: > The normal behavior for both Windows and Linux is to create the > symbolic link whether the target exists or not. That's not the case on Windows or rather it has restrictions that can trip you up. On Windows you must specify if the symbolic link points to a directory

Re: [ITA] libspectre-0.2.9-1

On Tue, 05 Jan 2021 01:33:28 +0900, Lemures Lemniscati > ITA for libspectre, which has been maintained by Yaakov [1]. > > Now, the latest upstream of exif is 0.6.22 [2]. This line should be... ``Now, the latest upstream of libspectre is 0.2.9 [2].'' Regards, Lem

[ITA] libspectre-0.2.9-1

ITA for libspectre, which has been maintained by Yaakov [1]. Now, the latest upstream of exif is 0.6.22 [2]. A new candidate cygport file is placed at [3]. And, it's been tested on Cygwin AppVeyor CI (ID 1606: [4]). Generated package files are placed at [5] and [6]. Packaging is rearranged

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

On 1/4/2021 10:27 AM, Matt D. via Cygwin wrote: > I think there is a misunderstanding with how to set up your > environment to reproduce my test cases. I did state in the subject > "native symbolic links" but I can see that this can be misinterpreted > and I should have clarified. > > I am using

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

On 1/4/2021 10:27 AM, Matt D. via Cygwin (cygwin@cygwin.com) wrote: > I am using symbolic links native to Windows. My CYGWIN environment > variable has been set to "winsymlinks:nativestrict" and my account has > permission to make symbolic links. This is an issue specifically with > Cygwin; I have

[ANNOUNCEMENT] Updated: man-db-2.9.3-3

The man-db package version 2.9.3 is re-released to correct an error in generating the postinstall scripts and replaces the erroneous version, which was removed. Man-db is an implementation of the standard Unix documentation system accessed using the man command. It uses a Berkeley DB database

Updated: man-db-2.9.3-3

The man-db package version 2.9.3 is re-released to correct an error in generating the postinstall scripts and replaces the erroneous version, which was removed. Man-db is an implementation of the standard Unix documentation system accessed using the man command. It uses a Berkeley DB database

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

I think there is a misunderstanding with how to set up your environment to reproduce my test cases. I did state in the subject "native symbolic links" but I can see that this can be misinterpreted and I should have clarified. I am using symbolic links native to Windows. My CYGWIN environment

Postinstall script errors for man* packages

Hi, I think the recent man* package update has an issue in the postinstall script: Postinstall script errors Package: z/Perpetual zp_man-db-update-index.dash exit code 2 $ /etc/postinstall/zp_man-db-update-index.dash /etc/postinstall/zp_man-db-update-index.dash: line 4: syntax error near

Re: [ANNOUNCEMENT] Updated: less-563-1

Greetings, Marco Atzeri via Cygwin-announce via Cygwin! > New version 563-1 of >less > is available in the Cygwin distribution > CHANGES > Last upstream release > http://www.greenwoodsoftware.com/less/ > Also compiled with pcre regex Yes! Thank you! -- With best regards, Andrey Repin

Re: OpenSSL

On 04.01.2021 13:21, tommie.k...@alverservices.com wrote: Hey, sorry if this is the wrong place. Hi Tommie, this is the right place. But im struggling to see how I can upgrade openssl >1.1.1f Compliance checks state that we must have a more up to date version, I know that it exists

Testing is skipped on i686-AppVeyor for shared-mime-info 2.1

Hi! I'm preparing share-mime-info-2.1-1, updating to the latest upstream. My local-buildings run and check successfull both on i686 and x86_64 with a source tree [1]. But on AppVeyor [2], testing seems to be skipped on i686 arch, although src_test is called [3]... On the other hand, testing

Re: [RFE] calm needs to know about ZStandard compressed archives

On 03/01/2021 15:57, Achim Gratz wrote: Marco Atzeri via Cygwin-apps writes: We will also need to modify cygport to stop automatically add OBSOLETES as most of this packages never existed I think the right thing to do is to stop having actual packages for OBSOLETES and just emit the obsoltes:

Re: Fixing moreutils Git repo

On 04/01/2021 10:39, Adam Dinwoodie wrote: Somewhere along the way I seem to have unsubscribed from this list, and therefore managed to miss a bunch of development with the Git repositories at https://cygwin.com/git-cygwin-packages/. As a result I thought they were still naive repositories with

Re: [ITA] libexif-0.6.22-1

On Sun, 03 Jan 2021 10:51:30 +0100, Achim Gratz > Lemures Lemniscati via Cygwin-apps writes: > > So an expected libexiv-doc will contain > […] > > How about this rearrangement? > > That sounds OK to me. You don't need to do another update just for that > change of course. Thank you. I've just

[ANNOUNCEMENT] Updated: man-db-2.9.3-2

The man-db package version 2.9.3 is re-released to correct a packaging error and improve the perpetual index update postinstall script. Man-db is an implementation of the standard Unix documentation system accessed using the man command. It uses a Berkeley DB database in place of the

Updated: man-db-2.9.3-2

The man-db package version 2.9.3 is re-released to correct a packaging error and improve the perpetual index update postinstall script. Man-db is an implementation of the standard Unix documentation system accessed using the man command. It uses a Berkeley DB database in place of the

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

On 1/4/2021 5:36 AM, Matt D. via Cygwin wrote: > Did you try any of my test cases? This can't and doesn't work for the > reasons I outlined in my previous message: > > $ cp -av folder_a/a folder_b/ > 'folder_a/a' -> 'folder_b/a' > cp: cannot create symbolic link 'folder_b/a': No such file or

OpenSSL

Hey, sorry if this is the wrong place. But im struggling to see how I can upgrade openssl >1.1.1f Compliance checks state that we must have a more up to date version, I know that it exists (1.1.1g, 1.1.1h, 1.1.1i) But I can only seem to upgrade to 1.1.1f in Cygwin - is there a

Fixing moreutils Git repo

Somewhere along the way I seem to have unsubscribed from this list, and therefore managed to miss a bunch of development with the Git repositories at https://cygwin.com/git-cygwin-packages/. As a result I thought they were still naive repositories with no fancy logic or automation, and my first

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

Did you try any of my test cases? This can't and doesn't work for the reasons I outlined in my previous message: $ cp -av folder_a/a folder_b/ 'folder_a/a' -> 'folder_b/a' cp: cannot create symbolic link 'folder_b/a': No such file or directory $ cp -dv folder_a/a folder_b/ 'folder_a/a' ->

Re: Fortran Installation

On 04.01.2021 01:19, Lou Umscheid wrote: Thank you for the information. Do you have any suggestions on which compiler to use ie the most recent or the tried and true? I have 4.5 installed on my old T1600 system. by default run the most recent gcc-fortran-10.2.0-1 If you have problem, you