[ITP] bzip3 1.3.0
Hello, [ITP] A new package proposal: bzip3 - bzip3 - libbzip3_0 - libbzip3-devel SUMMARY: Better and stronger spiritual successor to BZip2 HOMEPAGE: https://github.com/kspalaiologos/bzip3 SRC_URI: https://github.com/kspalaiologos/bzip3/archive/refs/tags/1.3.0.tar.gz LICENSE: LGPL-3.0-or-later Corresponding Linux/Unix packages are searched: - https://repology.org/project/bzip3/versions Cygportfile: - https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/playground.git;a=shortlog;h=refs/heads/bzip3 Packages, logs: - https://github.com/cygwin/scallywag/actions/runs/4643575116
Mail delivery failed: returning message to sender
This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: cygwin@cygwin.com Domain watersportmotoren.nl has exceeded the max defers and failures per hour (5/5 (100%)) allowed. Message discarded. Reporting-MTA: dns; echidna.dudesquare.nl Action: failed Final-Recipient: rfc822;cygwin@cygwin.com Status: 5.0.0 -- 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
Re: Howto fix C:\cygwin acl after backup/restore?
On 2023-04-07 14:36, Thomas Schweikle via Cygwin wrote:
How can C:\cygwin ACL be fixed after a backup/restore (file by file, not image).
The program seems to force canonical ACL while restoring.
How do i get back ACL as they are right after installing cygwin?
Docs did not help here. They discussed Windows-ACL to POSIX-ACL or simple
rwxrwxrwx POSIX rights used on most *nix machines, but at no point where
concrete ACL shown as they are supposed to be applied to the installed C:\cygwin
tree.
Any idea? Any script? Any existing command to recreate recommended ACLs?
For the Cygwin root directory, normal u+rwx,go+rx perms are sufficient.
For other Cygwin files where perms are significant, you should use Cygwin
backup/restore utilities e.g. rsync, tar, cpio, etc.
Without some image of Cygwin ACLs, you can not restore them as they were, as in
the setfacl(1) example:
$ getfacl source_file | setfacl -f - target_file
or an equivalent en masse.
For user created files and scripts, use relevant normal permissions.
For installed files, if you have a complete and current package cache directory,
you can compare the installation to the latest archive of each package under
/{x86_64,noarch}/release/ looping thru:
tar -d -C / -f
/{x86_64,noarch}/release//.../...--.tar.*z*
e.g.
$ tar -d -C / -f ~/mirror/x86_64/release/bash/bash-4.4.12-3.tar.xz
/bin/tar: etc/postinstall/bash.sh: Warning: Cannot stat: No such file or
directory
usr/bin/bash.exe: Uid differs
usr/bin/bash.exe: Gid differs
usr/bin/bashbug: Mode differs
usr/bin/bashbug: Uid differs
usr/bin/sh.exe: Not linked to usr/bin/bash.exe
usr/include/bash/alias.h: Uid differs
...
which is very verbose, or do your own perms comparison vs the outputs from
looping thru:
tar -tv -C / -f
/{x86_64,noarch}/release//.../...--.tar.*z*
(*always remembering that all Cygwin installation tar file paths are relative to
the Cygwin root directory / and need adjusted for use*) sort and group the files
and directories which differ by tar permissions, and feed the lists of files and
directories in a loop to e.g.:
/bin/xargs -P `nproc` -a .lst /bin/chmod
to safely batch and parallelize the changes, or background each command
in the loop:
/bin/xargs -a .lst /bin/chmod &
to parallelize the workload.
The Windows directory cache will buffer the changes, and it might be good to:
$ sync -f /usr /etc
to flush updates to disk: the second arg, if to the same file system, may have
to wait until the first has completed, unless the command detects that.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
--
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
Changing user home to overlap Windows user home possible? Or a bad idea?
Hi! Is it possible to have the same home for Windows and cygwin? Using "C:\Users\" for Cygwin home setting mount points for users? Or is this a bad idea? Or is it something which has some drawbacks you've to decide to live with? At the moment the most ugly drawback is duplication of various data needed within "C:\cygwin\home\" and "C:\Users\". Would be nice if I could overlay both. -- Thomas OpenPGP_0x27AE2304B4974851.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature -- 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
Howto fix C:\cygwin acl after backup/restore?
Hi! How can C:\cygwin ACL be fixed after a backup/restore (file by file, not image). The program seems to force canonical ACL while restoring. How do i get back ACL as they are right after installing cygwin? Docs did not help here. They discussed Windows-ACL to POSIX-ACL or simple rwxrwxrwx POSIX rights used on most *nix machines, but at no point where concrete ACL shown as they are supposed to be applied to the installed C:\cygwin tree. Any idea? Any script? Any existing command to recreate recommended ACLs? -- Thomas OpenPGP_0x27AE2304B4974851.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature -- 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
Re: bash shell script: recently running, now failing
On 2023-04-06 06:21, Andrey Repin via Cygwin wrote: I have a "hash bang" bash shell script i.e. first line #! /bin/sh or equivalently #! /bin/bash By default, sh is bash in base Cygwin installation. Q3 - at 1/8 the size of bash and sh, I am not at all sure of the role and reach of dash. Should the edit (dash replacing bash/sh) be incorporated elsewhere or would this be a bad idea (and retained only locally in what is indeed an eccentric and one-off context)? I'm replacing /bin/sh with dash as I've found that even in POSIX mode, bash allows for a lot of bash'izms in scripts, which would not otherwise run under (d?a)?sh. See the post-install script attached. You should use either a hard link or copy of d/ash from/to /bin/ to allow it (or any shell) to be used from Windows cmd shells or Scheduled Tasks, which do not recognise Cygwin /usr mounts or symlinks, but can be run with elevated privileges and at sometimes more useful points than user cron jobs. For example, "manually" restarting Cygwin services after delayed startup, stopping Cygwin services and processes before upgrades, and cleaning up cron jobs that have not finished. You should also consider changing the sh man page. -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut -- Antoine de Saint-Exupéry -- 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
Re: Fwd: Error running setup-x86_64.exe: syntax error in setup.zst
FYI apps - fixed 20 minutes after your post - noted on original Cygwin thread On 2023-04-07 03:20, Daisuke Fujimura via Cygwin-apps wrote: I think it's the effect of the latest gnubg package, can anyone fix it? https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/gnubg.git;a=blobdiff;f=gnubg.cygport;h=559ae03f174cbcd3ad7ab3fcca11ad210f45ed0f;hp=471f68c78804b0da14e7a22fa9befce86cc2521e;hb=0961ac54da1a03e8c747281f8359449636dd0db7;hpb=522ffd2cf1f6fb831f14b239058d5f589a176917 On Fri, Apr 7, 2023 at 10:45 AM, Keith Thompson wrote: Running setup-x86_64.exe on a Windows 10 laptop, I get this error message: https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line 30182: syntax error, unexpected $undefined, expecting COMMA or NL https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line 30182: unrecognized line 30183 (do you have the latest setup?) https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line 30203: syntax error, unexpected $undefined, expecting COMMA or NL https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line 30203: unrecognized line 30204 (do you have the latest setup?) (I can't copy the text from the message box so I retyped it.) I re-downloaded setup-x86_64.exec, and it's identical to the one on my laptop. I'm using the mirrors.kernel.org mirror. The setup.zst from mirrors.dotsrc.org is identical. I decompressed setup.zst and I do see something suspicious on the indicated lines. Here's line 30182: build-depends: \, bison, cygport, dblatex, docbook2X, flex, gettext-devel, libGLU-devel, libcairo-devel, libcanberra-gtk-devel, libcurl-devel, libfreetype-devel, libglib2.0-devel, libgmp-devel, libgtk2.0-devel, libgtkglext1.0-devel, libpango1.0-devel, libpng-devel, libreadline-devel, libsqlite3-devel, libxslt, python3-devel, texinfo Line 30203 is similar. I don't see a lone backslash anywhere else in the file. The setup.zst from mirrors.sonic.net does *not* have problematic build-depends lines. (Switching to a different mirror might be a workaround, but I haven't tried it yet.) The "bad" setup.zst has "setup-timestamp: 1680813730" (Thu 2023-04-06 20:42:10 UTC). The "good" setup.zst has "setup-timestamp: 1680795371" (Thu 2023-04-06 15:36:11 UTC). The bad one is about 5 hours newer than the good one. I'm concerned that the bad setup.zst might propagate to other mirrors.
Re: Error running setup-x86_64.exe: syntax error in setup.zst
On Fri, Apr 7, 2023 at 2:40 AM Jon Turney wrote: > > On 07/04/2023 02:44, Keith Thompson via Cygwin wrote: > > Running setup-x86_64.exe on a Windows 10 laptop, I get this error message: > > > > https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line > > 30182: syntax error, unexpected $undefined, expecting COMMA or NL > > https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line > > 30182: unrecognized line 30183 (do you have the latest setup?) > > https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line > > 30203: syntax error, unexpected $undefined, expecting COMMA or NL > > https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line > > 30203: unrecognized line 30204 (do you have the latest setup?) > > > > (I can't copy the text from the message box so I retyped it.) > > Protip: Ctrl-C should work on a message box. Yes, it does! You can't select part of the text and there's no visual feedback, but if you select the message box and type Ctrl-C, it works. That's going to be useful. > > I re-downloaded setup-x86_64.exec, and it's identical to the one on my > > laptop. > > > > I'm using the mirrors.kernel.org mirror. > > The setup.zst from mirrors.dotsrc.org is identical. > > I decompressed setup.zst and I do see something suspicious on the > > indicated lines. > > > > Here's line 30182: > > > > build-depends: \, bison, cygport, dblatex, docbook2X, flex, > > gettext-devel, libGLU-devel, libcairo-devel, libcanberra-gtk-devel, > > libcurl-devel, libfreetype-devel, libglib2.0-devel, libgmp-devel, > > libgtk2.0-devel, libgtkglext1.0-devel, libpango1.0-devel, > > libpng-devel, libreadline-devel, libsqlite3-devel, libxslt, > > python3-devel, texinfo > > > > Line 30203 is similar. I don't see a lone backslash anywhere else in the > > file. > > Yeah, this is wrong. > > I need to investigate further why the mechanisms which should have > caught this didn't. > > > The setup.zst from mirrors.sonic.net does *not* have problematic > > build-depends lines. > > (Switching to a different mirror might be a workaround, but I haven't > > tried it yet.) > > > > The "bad" setup.zst has "setup-timestamp: 1680813730" (Thu 2023-04-06 > > 20:42:10 UTC). > > The "good" setup.zst has "setup-timestamp: 1680795371" (Thu 2023-04-06 > > 15:36:11 UTC). > > The bad one is about 5 hours newer than the good one. > > I'm concerned that the bad setup.zst might propagate to other mirrors. > This is fixed as of setup-timestamp: 1680860048 > > Thanks very much for reporting this. > > Apologies for the inconvenience. The mirror I use (mirrors.kernel.org) now has a setup.zst with a newer timestamp (1680869581) and without the stray backslashes. -- 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
stunnel 5.69-1
stunnel 5.69-1 is now available in Cygwin. This release has bug fixes and minor improvements. Please see the upstream changelog[1] for the full list. stunnel is a program that allows you to encrypt arbitrary TCP connections inside TLS (Transport Layer Security, the successor to Secure Sockets Layer (SSL)). stunnel can allow you to secure non-TLS-aware daemons and protocols (like POP, IMAP, LDAP, etc) by having stunnel provide the encryption, requiring no changes to the daemon's code. Andrew E. Schulman [1]https://www.stunnel.org/NEWS.html
[ANNOUNCEMENT] stunnel 5.69-1
stunnel 5.69-1 is now available in Cygwin. This release has bug fixes and minor improvements. Please see the upstream changelog[1] for the full list. stunnel is a program that allows you to encrypt arbitrary TCP connections inside TLS (Transport Layer Security, the successor to Secure Sockets Layer (SSL)). stunnel can allow you to secure non-TLS-aware daemons and protocols (like POP, IMAP, LDAP, etc) by having stunnel provide the encryption, requiring no changes to the daemon's code. Andrew E. Schulman [1]https://www.stunnel.org/NEWS.html -- 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
Re: Error running setup-x86_64.exe: syntax error in setup.zst
On 07/04/2023 02:44, Keith Thompson via Cygwin wrote: Running setup-x86_64.exe on a Windows 10 laptop, I get this error message: https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line 30182: syntax error, unexpected $undefined, expecting COMMA or NL https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line 30182: unrecognized line 30183 (do you have the latest setup?) https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line 30203: syntax error, unexpected $undefined, expecting COMMA or NL https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line 30203: unrecognized line 30204 (do you have the latest setup?) (I can't copy the text from the message box so I retyped it.) Protip: Ctrl-C should work on a message box. I re-downloaded setup-x86_64.exec, and it's identical to the one on my laptop. I'm using the mirrors.kernel.org mirror. The setup.zst from mirrors.dotsrc.org is identical. I decompressed setup.zst and I do see something suspicious on the indicated lines. Here's line 30182: build-depends: \, bison, cygport, dblatex, docbook2X, flex, gettext-devel, libGLU-devel, libcairo-devel, libcanberra-gtk-devel, libcurl-devel, libfreetype-devel, libglib2.0-devel, libgmp-devel, libgtk2.0-devel, libgtkglext1.0-devel, libpango1.0-devel, libpng-devel, libreadline-devel, libsqlite3-devel, libxslt, python3-devel, texinfo Line 30203 is similar. I don't see a lone backslash anywhere else in the file. Yeah, this is wrong. I need to investigate further why the mechanisms which should have caught this didn't. The setup.zst from mirrors.sonic.net does *not* have problematic build-depends lines. (Switching to a different mirror might be a workaround, but I haven't tried it yet.) The "bad" setup.zst has "setup-timestamp: 1680813730" (Thu 2023-04-06 20:42:10 UTC). The "good" setup.zst has "setup-timestamp: 1680795371" (Thu 2023-04-06 15:36:11 UTC). The bad one is about 5 hours newer than the good one. I'm concerned that the bad setup.zst might propagate to other mirrors. This is fixed as of setup-timestamp: 1680860048 Thanks very much for reporting this. Apologies for the inconvenience. -- 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
Fwd: Error running setup-x86_64.exe: syntax error in setup.zst
I think it's the effect of the latest gnubg package, can anyone fix it? https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/gnubg.git;a=blobdiff;f=gnubg.cygport;h=559ae03f174cbcd3ad7ab3fcca11ad210f45ed0f;hp=471f68c78804b0da14e7a22fa9befce86cc2521e;hb=0961ac54da1a03e8c747281f8359449636dd0db7;hpb=522ffd2cf1f6fb831f14b239058d5f589a176917 -- Forwarded message - From: Keith Thompson via Cygwin Date: Fri, Apr 7, 2023 at 10:45 AM Subject: Error running setup-x86_64.exe: syntax error in setup.zst To: Cc: Keith Thompson Running setup-x86_64.exe on a Windows 10 laptop, I get this error message: https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line 30182: syntax error, unexpected $undefined, expecting COMMA or NL https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line 30182: unrecognized line 30183 (do you have the latest setup?) https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line 30203: syntax error, unexpected $undefined, expecting COMMA or NL https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line 30203: unrecognized line 30204 (do you have the latest setup?) (I can't copy the text from the message box so I retyped it.) I re-downloaded setup-x86_64.exec, and it's identical to the one on my laptop. I'm using the mirrors.kernel.org mirror. The setup.zst from mirrors.dotsrc.org is identical. I decompressed setup.zst and I do see something suspicious on the indicated lines. Here's line 30182: build-depends: \, bison, cygport, dblatex, docbook2X, flex, gettext-devel, libGLU-devel, libcairo-devel, libcanberra-gtk-devel, libcurl-devel, libfreetype-devel, libglib2.0-devel, libgmp-devel, libgtk2.0-devel, libgtkglext1.0-devel, libpango1.0-devel, libpng-devel, libreadline-devel, libsqlite3-devel, libxslt, python3-devel, texinfo Line 30203 is similar. I don't see a lone backslash anywhere else in the file. The setup.zst from mirrors.sonic.net does *not* have problematic build-depends lines. (Switching to a different mirror might be a workaround, but I haven't tried it yet.) The "bad" setup.zst has "setup-timestamp: 1680813730" (Thu 2023-04-06 20:42:10 UTC). The "good" setup.zst has "setup-timestamp: 1680795371" (Thu 2023-04-06 15:36:11 UTC). The bad one is about 5 hours newer than the good one. I'm concerned that the bad setup.zst might propagate to other mirrors. -- 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
Re: Error running setup-x86_64.exe: syntax error in setup.zst
>> I'm concerned that the bad setup.zst might propagate to other mirrors. Yes, identical error arising at https://cygwin.mirror.uk.sargasso.net/x86_64/setup.zst and elsewhere. -- 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
