[ANNOUNCEMENT] Updated: guile-3.0.5-1
Version 3.0.5-1 of
guile3.0
libguile3.0-devel
libguile3.0_1
have been uploaded for cygwin.
CYGWIN NOTE
"guile" package has been obsoleted
The package postinstallation script uses alternatives(8)
to install a symlink for /usr/bin/{guile,guild,guile-config}
programs.
CHANGES
Latest upstream releases.
https://www.gnu.org/software/guile/news/gnu-guile-305-released.html
DESCRIPTION
Guile is an implementation of the Scheme programming language,
supporting the Revised5 and most of the Revised6 language
reports, as well as many SRFIs.
Guile is designed to help programmers create flexible applications
that can be extended by users or other programmers with plug-ins,
modules, or scripts.
HOMEPAGE
https://www.gnu.org/software/guile/
Regards
Marco Atzeri
If you have questions or comments, please send them to the
cygwin mailing list at: cygwin (at) cygwin (dot) com .
--
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
Updated: guile-3.0.5-1
Version 3.0.5-1 of
guile3.0
libguile3.0-devel
libguile3.0_1
have been uploaded for cygwin.
CYGWIN NOTE
"guile" package has been obsoleted
The package postinstallation script uses alternatives(8)
to install a symlink for /usr/bin/{guile,guild,guile-config}
programs.
CHANGES
Latest upstream releases.
https://www.gnu.org/software/guile/news/gnu-guile-305-released.html
DESCRIPTION
Guile is an implementation of the Scheme programming language,
supporting the Revised5 and most of the Revised6 language
reports, as well as many SRFIs.
Guile is designed to help programmers create flexible applications
that can be extended by users or other programmers with plug-ins,
modules, or scripts.
HOMEPAGE
https://www.gnu.org/software/guile/
Regards
Marco Atzeri
If you have questions or comments, please send them to the
cygwin mailing list at: cygwin (at) cygwin (dot) com .
Re: Cygwin version control location
On 17.01.2021 07:31, Kyle Marek via Cygwin wrote: On 1/17/21 12:56 AM, Marco Atzeri via Cygwin wrote: On 17.01.2021 06:01, Kyle Marek via Cygwin wrote: Hello, Where are the version control repositories for packages missing from https://cygwin.com/git/ and https://cygwin.com/git-cygwin-packages/ like bash and git? Thank you, Kyle Marek use the source packages. The version control is not implemented or updated for most of the packages. I am slowing moving mine to the central repository at https://cygwin.com/git-cygwin-packages/ Is there an archive of previous versions? any mirror should have several previous releases each one with its own source package EG with a mirror near me in Germany: ftp://ftp-stud.hs-esslingen.de/pub/Mirrors/sources.redhat.com/cygwin/x86_64/release/bash/ Datei:bash-4.4.11-2-src.tar.xz 9166 KB 23.01.2017 01:00:00 Datei:bash-4.4.12-3-src.tar.xz 9168 KB 27.01.2017 01:00:00 Datei:bash-4.4.5-1-src.tar.xz 9163 KB 13.12.2016 01:00:00 Regards Marco -- 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: [PATCH cygport] A patch to add a flag __SKIP_LIST_DEPS_LUA
Lemures Lemniscati via Cygwin-apps writes: > Alpine linux has multiple versions of lua, also [1]. > And packages names have periods in them when lua-versions are > specified [2]. I still consider Alpine a special snowflake despite their gains in container environments since they tend to have their own package splits. > Among cygwin packages, guile packages have dots in their package names. Nobody said things were consistent. > And, I'm wondering about no-dot-in-the-version scheme... What should we > do if its version comes to 5.10 or higher (just a hypothecical example). > It will be lua510-* without dots, but I would feel uneasy for it (just > in my opinion). We will cross that bridge when we get there. > Does it mean that we should have a way to rebase such dynamic objects > automatically? Well, the first step is to make sure that packaged and locally installed stuff stays separate (for Perl this is the distinction between vendor and site distributions) and set up a sensible precedence order. Next is that users might not have admin rights, so there's a separation between local system and local user to consider (Perl: local::lib). Once you have that sorted then yes, you need to think about when and how to do the rebase of any dynamic objects you are going to produce. For Perl I managed to insert an automatic ephemeral rebase, but only for i686 and packages built with ExtUtils::MakeMaker (so that build tests can actually work without having to do an extra step). The local installations should be taken care of via the autorebase facilities, although that requires cooperation from the system admin for user installations. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
Re: Cygwin version control location
On 1/17/21 12:56 AM, Marco Atzeri via Cygwin wrote: On 17.01.2021 06:01, Kyle Marek via Cygwin wrote: Hello, Where are the version control repositories for packages missing from https://cygwin.com/git/ and https://cygwin.com/git-cygwin-packages/ like bash and git? Thank you, Kyle Marek use the source packages. The version control is not implemented or updated for most of the packages. I am slowing moving mine to the central repository at https://cygwin.com/git-cygwin-packages/ Is there an archive of previous versions? -- 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: Cygwin version control location
On 17.01.2021 06:01, Kyle Marek via Cygwin wrote: Hello, Where are the version control repositories for packages missing from https://cygwin.com/git/ and https://cygwin.com/git-cygwin-packages/ like bash and git? Thank you, Kyle Marek use the source packages. The version control is not implemented or updated for most of the packages. I am slowing moving mine to the central repository at https://cygwin.com/git-cygwin-packages/ -- 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: pylint: ImportError: No module named pkg_resources
On 17.01.2021 00:18, Oleksandr Gavenko via Cygwin wrote: After installing pylint: setup.exe -p pylint I expected I can use the package: pylint /dev/null Traceback (most recent call last): File "/usr/bin/pylint", line 5, in from pkg_resources import load_entry_point ImportError: No module named pkg_resources I tried to add package: python-setuptools as suggested by: https://stackoverflow.com/questions/7446187/no-module-named-pkg-resources and now it works. Noted. I will look on it as it was anyway built for python2 that is now EOL So need to be rebuilt to work with python3 I believe that x86_64/setup.bz2 is broken: depends2: python, python-logilab-astng, python-logilab-common It doesn't mention python-setuptools. Or it might be that /usr/bin/pylint should be rewritten to avoid dependency to setuptools. This explain the status problem: $ grep -e "pylint" -e "logilab" cygwin-pkg-maint pylint ORPHANED (Jari Aalto) python-logilab-astng ORPHANED (Jari Aalto) python-logilab-commonORPHANED (Jari Aalto) I guess one is also dead upstream (or was totally re-shaffled) but I need to look again . Thanks for the report Marco -- 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: GitHub automation for Cygwin builds [Was: Updated: moreutils v0.65-1]
On 16.01.2021 23:31, Ken Brown via Cygwin-apps wrote: On 1/16/2021 3:33 PM, Adam Dinwoodie wrote: On Sat, 16 Jan 2021 at 20:22, Adam Dinwoodie wrote: Version 0.65-1 of moreutils has been uploaded and should be coming soon to a distribution server near you. I assume you're quoting from https://cygwin.com/packaging/build.html. Scallywag does have some limitations currently, but I think the statement you quoted is obsolete. I often have Scallywag deploy my packages, as does Jon Turney. The limitations I've bumped into are: 1. Scallywag will time out after an hour on each arch until now I was hit only during test. But I stil need to deploy on our Git some of the heavy packages 2. Several of my packages fail to build on x86 because of gcc crashes. 3. sometimes the failure is not in the build, but in missing or imperfect testing I think these limitations are outweighed by the fact that a Scallywag build is automatically triggered by a push to an official source repo (https://cygwin.com/packaging/repos.html). All maintainers can use this without any special setup. +1 Ken but of course Adam, more options are always better, Thank for sharing Marco
Cygwin version control location
Hello, Where are the version control repositories for packages missing from https://cygwin.com/git/ and https://cygwin.com/git-cygwin-packages/ like bash and git? Thank you, Kyle Marek -- 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: [PATCH cygport] A patch to add a flag __SKIP_LIST_DEPS_LUA
On Sat, 16 Jan 2021 07:50:52 +0100, ASSI > Lemures Lemniscati via Cygwin-apps writes: > > And I'm trying to package luarocks for lua5.3 and lua5.4 > > (lua5.3-luarocks and lua5.4-luarocks) by a single cygport file. > > The packages should be named lua53-luarocks and lua54-luarocks (no dot > in the version number), like OpenSUSE (they seem to be the only > distribution with a multi-version lua and that particular naming scheme > you've chosen). Alpine linux has multiple versions of lua, also [1]. And packages names have periods in them when lua-versions are specified [2]. [1]: https://pkgs.alpinelinux.org/packages?name=lua5.4 https://pkgs.alpinelinux.org/packages?name=lua5.3 https://pkgs.alpinelinux.org/packages?name=lua5.2 https://pkgs.alpinelinux.org/packages?name=lua5.1 [2]: https://pkgs.alpinelinux.org/packages?name=lua* Among cygwin packages, guile packages have dots in their package names. [3]: https://cygwin.com/packages/summary/guile3.0-src.html https://cygwin.com/packages/summary/guile2.2-src.html https://cygwin.com/packages/summary/guile2.0-src.html https://cygwin.com/packages/summary/guile1.8-src.html And, I'm wondering about no-dot-in-the-version scheme... What should we do if its version comes to 5.10 or higher (just a hypothecical example). It will be lua510-* without dots, but I would feel uneasy for it (just in my opinion). > A different question is if you really want to package this particular > feature. Just like all the other "package managers" that come with a > specific language or interpreter I'd expect this one to need (maybe > extensive) modifications to work correctly on Cygwin, especially if it > ends up building dynamic objects. Does it mean that we should have a way to rebase such dynamic objects automatically? > That's one reason I discourage the > use of CPAN on Cygwin, since folks tend to shoot themself into the foot > more often than not by using it. All right. Maybe, I should calm myself down. I will try simply to build subpackges for lua-5.4.2 (test), for the time being. Regards, Lem
Re: Can't open display issue from CMD
Am 16.01.2021 um 05:40 schrieb Marco Atzeri via Cygwin: It seems the remote machine is expecting to run a X interface by default. Or could it be that the local machine has ssh X11 forwarding turned on (for this remote machine)? Turning it off explicitly (-x flag) would turn it off, so if that changes the outcome, you know what happened. Running ssh in -v (verbose) may also help with telling what's going on. -- 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
pylint: ImportError: No module named pkg_resources
After installing pylint: setup.exe -p pylint I expected I can use the package: pylint /dev/null Traceback (most recent call last): File "/usr/bin/pylint", line 5, in from pkg_resources import load_entry_point ImportError: No module named pkg_resources I tried to add package: python-setuptools as suggested by: https://stackoverflow.com/questions/7446187/no-module-named-pkg-resources and now it works. I believe that x86_64/setup.bz2 is broken: depends2: python, python-logilab-astng, python-logilab-common It doesn't mention python-setuptools. Or it might be that /usr/bin/pylint should be rewritten to avoid dependency to setuptools. -- http://defun.work/ -- 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: Noticed that mintty starts non-login bash with "Win+R mintty Enter".
On 2021-01-05, Jason Pyeron wrote: > I do not put Cygwin in my windows PATH, (anymore since about 10 years ago). Sometimes it is useful to have GNU utils at hands. I use Far Commander and in order to find directory size I type: du -s -m NAME Also having Cygwin staff in PATH allows to start program elevated easily ( NAME ). > I use an environment where settings are lost at logoff, so I have become > accustomed to launching it from the command prompt. > > I have not found it too difficult to type > > c:\cygwin64\bin\mintty /bin/bash -l It won't be productive for my workflow. I own dev PC, not restricted to corporate policies and launch mintty hundred times a day (have CDPATH and other convenience set as the environment is permanent). Though I might get rid of Cygwin from PATH too. For starting Emacs I wrote wrapper that run it elevated (and hides that irritating console as I use emacs-w32) - it is a pleasure to be able to edit Windows /etc/hosts from within Emacs )) Same wrapper can be written for Mintty and placed to PATH. Though I wouldn't do that because all IDEs are rely on git.exe from Cygwin... It is pity that Mercurial comes with "shell" launcher, so cannot be used by non-Cygwin programs. -- http://defun.work/ -- 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: Noticed that mintty starts non-login bash with "Win+R mintty Enter".
On 2021-01-07, Kamran via Cygwin wrote: > Even: Win | mintty - > > opens up mintty with admin account. Cool, I use a lot but didn't know you can pass args! -- http://defun.work/ -- 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: GitHub automation for Cygwin builds [Was: Updated: moreutils v0.65-1]
On 1/16/2021 3:33 PM, Adam Dinwoodie wrote:
On Sat, 16 Jan 2021 at 20:22, Adam Dinwoodie wrote:
Version 0.65-1 of moreutils has been uploaded and should be coming
soon to a distribution server near you.
In case anyone's interested or has thoughts:
As part of working on this release, I've been playing with GitHub's
automation tools. The entire build / test / package / release / upload
process was performed using free ephemeral GitHub-managed VMs. At
least in theory, this reduces the manual work for future releases to:
- Commit a version of the Cygport file with an updated version number.
- Create a tag and push that tag to GitHub
- Wait for the confirmation email to arrive
- Send the announcement email
This is obviously serving a similar purpose to the automated builds
that Scallywag provides; I'm not sure I'd have bothered with this
project had I not already been most of the way through it before I
spotted Scallywag existed. I suspect in theory Scallywag's access to
the Cygwin servers means it's potentially more powerful, but Scallywag
also comes with some general caveats ("at this stage, this is only
probably useful for verifying that BUILD_REQUIRES is correct"),
I assume you're quoting from https://cygwin.com/packaging/build.html. Scallywag
does have some limitations currently, but I think the statement you quoted is
obsolete. I often have Scallywag deploy my packages, as does Jon Turney.
The limitations I've bumped into are:
1. Scallywag will time out after an hour on each arch.
2. Several of my packages fail to build on x86 because of gcc crashes.
I think these limitations are outweighed by the fact that a Scallywag build is
automatically triggered by a push to an official source repo
(https://cygwin.com/packaging/repos.html). All maintainers can use this without
any special setup.
Ken
Re: How to reinstall everything?
Cheers. I'll ask for these to be added to that repository and have them attributed to you. Any particular license? Hamish On 16/01/2021 21:02, Marco Atzeri via Cygwin wrote: > On 16.01.2021 20:55, Hamish McIntyre-Bhatty via Cygwin wrote: >> In reply to Marco Atzeri: >> >> """ >> Some time ago I put a script here: >> https://stackoverflow.com/questions/46829532/cygwin-save-package-selections-for-later-reinstall >> >> >> """ >> >> This has been very useful for me. Is this in a git/other repository >> somewhere? If not, I think it might aid discovery for it to go with >> some other useful scripts in this repository: >> https://github.com/michaelgchu/Cygwin_Specific_Repo. >> >> What do you think of this idea Marco? >> >> Hamish McIntyre-Bhatty >> > > feel free to use it. I never store anywhere other than stackoverflow. > Attached the current version, I don't rememeber if I changed > it in the meantime. > > Attached another that you can find useful > it uses cygcheck and binutils to provide the list of first level > packages containing the needed DLL's > > $ cyg-dependency.sh /usr/bin/octave-5.2.0.exe > /usr/bin/cygwin1.dll => cygwin-3.1.7-1 > /usr/bin/cygX11-6.dll => libX11_6-1.7.0-1 > /usr/bin/cyggcc_s-seh-1.dll => libgcc1-10.2.0-1 > /usr/bin/cygstdc++-6.dll => libstdc++6-10.2.0-1 > KERNEL32.dll => Windows System > > I found useful to avoid some screwup > > Regards > Marco > > > -- > 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 0x87B761FE07F548D6.asc Description: application/pgp-keys signature.asc 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: How to reinstall everything?
On 16.01.2021 20:55, Hamish McIntyre-Bhatty via Cygwin wrote:
In reply to Marco Atzeri:
"""
Some time ago I put a script here:
https://stackoverflow.com/questions/46829532/cygwin-save-package-selections-for-later-reinstall
"""
This has been very useful for me. Is this in a git/other repository somewhere?
If not, I think it might aid discovery for it to go with some other useful
scripts in this repository: https://github.com/michaelgchu/Cygwin_Specific_Repo.
What do you think of this idea Marco?
Hamish McIntyre-Bhatty
feel free to use it. I never store anywhere other than stackoverflow.
Attached the current version, I don't rememeber if I changed
it in the meantime.
Attached another that you can find useful
it uses cygcheck and binutils to provide the list of first level
packages containing the needed DLL's
$ cyg-dependency.sh /usr/bin/octave-5.2.0.exe
/usr/bin/cygwin1.dll => cygwin-3.1.7-1
/usr/bin/cygX11-6.dll => libX11_6-1.7.0-1
/usr/bin/cyggcc_s-seh-1.dll => libgcc1-10.2.0-1
/usr/bin/cygstdc++-6.dll => libstdc++6-10.2.0-1
KERNEL32.dll => Windows System
I found useful to avoid some screwup
Regards
Marco
#!/bin/bash
# Create a batch file to reinstall using setup-{ARCH}.exe
# all packages or the ones reported as incomplete
print_error=1
if [ $# -eq 1 ]
then
if [ $1 == "-I" ]
then
lista=$(mktemp)
cygcheck -c | grep "Incomplete" > $lista
print_error=0
fi
if [ $1 == "-A" ]
then
lista=$(mktemp)
cygcheck -cd | sed -e "1,2d" > $lista
print_error=0
fi
fi
if [ $# -eq 2 ]
then
if [ $1 == "-f" ]
then
lista=$2
print_error=0
fi
fi
# error message if options are incorrect.
if [ $print_error -eq 1 ]
then
echo -n "Usage : " $(basename $0)
echo " [ -A | -I | -f filelist ]"
echo " create cyg-reinstall-{ARC}.bat from"
echo " options"
echo "-A : All packages as reported by cygcheck"
echo "-I : incomplete packages as reported by cygcheck"
echo "-f : packages in filelist (one per row)"
exit 1
fi
if [ $(arch) == "x86_64" ]
then
A="x86_64"
else
A="x86"
fi
# writing header
echo -n -e "setup-${A}.exe " > cyg-reinstall-${A}.bat
# option -x remove and -P install
# for re-install packages we need both
if [ $1 == "-I" ]
then
awk 'BEGIN{printf(" -x ")} NR==1{printf $1}{printf ",%s", $1}' ${lista} >>
cyg-reinstall-${A}.bat
fi
awk 'BEGIN{printf(" -P ")} NR==1{printf $1}{printf ",%s", $1} END { printf
"\r\n pause "}' ${lista} >> cyg-reinstall-${A}.bat
# execution permission for the script
chmod +x cyg-reinstall-${A}.bat
#!/bin/bash
if [ $# -ne 1 ]
then
echo "Usage : " $0 "file_name"
echo "Find package dependency from dll dependency"
exit 1
fi
a=1
# mypath=$(echo $PATH | tr ":" " ")
mypath="/usr/bin /usr/lib/lapack"
windir=$(cygpath -u ${WINDIR})"/System32"
for i in $(objdump -x $1 |grep "DLL Name:" |sed -e "s/\tDLL Name: //g"| tr
"\r" " " )
do
if [ $i = "KERNEL32.dll" ]
then
echo -n $i
echo -n " => "
echo " Windows System"
else
fullname=$(find ${mypath} -maxdepth 1 -name $i)
if [ -z "${fullname}" ]
then
fullname=$(find ${windir} -maxdepth 1 -iname $i)
if [ -z "${fullname}" ]
then
echo -n $i
echo " => NOT on PATH, Unknown"
else
echo -n $i
echo -n " => "
echo " Windows System"
fi
else
echo -n $fullname
echo -n " => "
package=$(cygcheck -f $fullname )
if [ -z "$package" ]
then
echo "NOT on ANY Package (system one?)"
else
echo $package
fi
fi
fi
done
--
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
GitHub automation for Cygwin builds [Was: Updated: moreutils v0.65-1]
On Sat, 16 Jan 2021 at 20:22, Adam Dinwoodie wrote:
> Version 0.65-1 of moreutils has been uploaded and should be coming
> soon to a distribution server near you.
In case anyone's interested or has thoughts:
As part of working on this release, I've been playing with GitHub's
automation tools. The entire build / test / package / release / upload
process was performed using free ephemeral GitHub-managed VMs. At
least in theory, this reduces the manual work for future releases to:
- Commit a version of the Cygport file with an updated version number.
- Create a tag and push that tag to GitHub
- Wait for the confirmation email to arrive
- Send the announcement email
This is obviously serving a similar purpose to the automated builds
that Scallywag provides; I'm not sure I'd have bothered with this
project had I not already been most of the way through it before I
spotted Scallywag existed. I suspect in theory Scallywag's access to
the Cygwin servers means it's potentially more powerful, but Scallywag
also comes with some general caveats ("at this stage, this is only
probably useful for verifying that BUILD_REQUIRES is correct"),
whereas I think with care this could replace local builds today.
The configuration to make this work is almost entirely in
,
and I expect the modifications to make this work for most other
packages would be straightforward. I'm hoping to make the process and
required configuration simpler, by creating a pre-defined GitHub
action that hides most of the boilerplate.
If you're curious, you can see the full build output for the final
release build at
.
[ANNOUNCEMENT] Updated: moreutils v0.65-1
Version 0.65-1 of moreutils has been uploaded and should be coming soon to a distribution server near you. This is an update to the latest upstream release; it includes the following changes: - vipe: Added --suffix option. Thanks, Pål Grønås Drange. - ifdata: fail when -ph is given but no hwaddr is available (Closes: #386755) Thanks, Nicolas Schier Moreutils is a "collection of the unix tools that nobody thought to write long ago when unix was young." From the upstream website, https://joeyh.name/code/moreutils/: Probably the most general purpose tool in moreutils so far is sponge(1), which lets you do things like this: % sed "s/root/toor/" /etc/passwd | grep -v joey | sponge /etc/passwd There are lots more listed below, and I'm always interested to add more to the collection, as long as they're suitably general-purpose, and don't duplicate other well-known tools. - chronic: runs a command quietly unless it fails - combine: combine the lines in two files using boolean operations - errno: look up errno names and descriptions - ifdata: get network interface info without parsing ifconfig output - ifne: run a program if the standard input is not empty - isutf8: check if a file or standard input is utf-8 - lckdo: execute a program with a lock held - mispipe: pipe two commands, returning the exit status of the first - parallel: run multiple jobs at once - pee: tee standard input to pipes - sponge: soak up standard input and write to a file - ts: timestamp standard input - vidir: edit a directory in your text editor - vipe: insert a text editor into a pipe - zrun: automatically uncompress arguments to command -- 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
Updated: moreutils v0.65-1
Version 0.65-1 of moreutils has been uploaded and should be coming soon to a distribution server near you. This is an update to the latest upstream release; it includes the following changes: - vipe: Added --suffix option. Thanks, Pål Grønås Drange. - ifdata: fail when -ph is given but no hwaddr is available (Closes: #386755) Thanks, Nicolas Schier Moreutils is a "collection of the unix tools that nobody thought to write long ago when unix was young." >From the upstream website, https://joeyh.name/code/moreutils/: Probably the most general purpose tool in moreutils so far is sponge(1), which lets you do things like this: % sed "s/root/toor/" /etc/passwd | grep -v joey | sponge /etc/passwd There are lots more listed below, and I'm always interested to add more to the collection, as long as they're suitably general-purpose, and don't duplicate other well-known tools. - chronic: runs a command quietly unless it fails - combine: combine the lines in two files using boolean operations - errno: look up errno names and descriptions - ifdata: get network interface info without parsing ifconfig output - ifne: run a program if the standard input is not empty - isutf8: check if a file or standard input is utf-8 - lckdo: execute a program with a lock held - mispipe: pipe two commands, returning the exit status of the first - parallel: run multiple jobs at once - pee: tee standard input to pipes - sponge: soak up standard input and write to a file - ts: timestamp standard input - vidir: edit a directory in your text editor - vipe: insert a text editor into a pipe - zrun: automatically uncompress arguments to command
Re: How to reinstall everything?
In reply to Marco Atzeri: """ Some time ago I put a script here: https://stackoverflow.com/questions/46829532/cygwin-save-package-selections-for-later-reinstall """ This has been very useful for me. Is this in a git/other repository somewhere? If not, I think it might aid discovery for it to go with some other useful scripts in this repository: https://github.com/michaelgchu/Cygwin_Specific_Repo. What do you think of this idea Marco? Hamish McIntyre-Bhatty 0x87B761FE07F548D6.asc Description: application/pgp-keys signature.asc 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: misterious GIT failure (SOLVED)
On 1/16/2021 12:22 PM, matthew patton wrote: On Friday, January 15, 2021, 12:48:16 PM EST, Ken Brown via Cygwin wrote: > but it would be appreciated if you would confirm this by testing a snapshot. I have confirmed that running snapshot build Cygwin1.dll from 2021-01-13 handles symlinks in the PATH as expected. Thanks for testing! Ken -- 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: misterious GIT failure (SOLVED)
On Friday, January 15, 2021, 12:48:16 PM EST, Ken Brown via Cygwin wrote: > but it would be appreciated if you would confirm this by testing a snapshot. I have confirmed that running snapshot build Cygwin1.dll from 2021-01-13 handles symlinks in the PATH as expected. -- 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
[ANNOUNCEMENT] Updated: Perl distributions
The following Perl distributions have been updated to their latest release version available on CPAN: x86/x86_64 -- perl-Gtk2-SourceView2-0.12-1 perl-Gtk2-Unique-0.07-1 noarch -- perl-Alien-Build-2.38-1 perl-DateTime-Calendar-Julian-0.103-1 perl-Module-ScanDeps-1.30-1 perl-Net-HTTP-6.20-1 perl-PAR-1.017-1 perl-Role-Tiny-2.002003-1 perl-Tie-Cycle-1.226-1 perl-URI-5.06-1 Notes = The following distributions have been deprecated upstream after several years of effectively being out of maintenace already: perl-Gnome2-1.048-1 perl-Gnome2-Canvas-1.006-1 perl-Gnome2-GConf-1.047-1 perl-Gnome2-Rsvg-0.12-1 perl-Gnome2-VFS-1.084-1 perl-Gnome2-Vte-0.12-1 perl-Gnome2-Wnck-0.18-1 perl-Gtk2-GladeXML-1.008-1 perl-Gtk2-SourceView2-0.12-1 perl-Gtk2-Spell-1.05-1 perl-Gtk2-Unique-0.07-1 There will be no further updates of these on Cygwin, which means that these distributions can no longer be used after the update of Perl to version 5.32 or later. -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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
Updated: Perl distributions
The following Perl distributions have been updated to their latest release version available on CPAN: x86/x86_64 -- perl-Gtk2-SourceView2-0.12-1 perl-Gtk2-Unique-0.07-1 noarch -- perl-Alien-Build-2.38-1 perl-DateTime-Calendar-Julian-0.103-1 perl-Module-ScanDeps-1.30-1 perl-Net-HTTP-6.20-1 perl-PAR-1.017-1 perl-Role-Tiny-2.002003-1 perl-Tie-Cycle-1.226-1 perl-URI-5.06-1 Notes = The following distributions have been deprecated upstream after several years of effectively being out of maintenace already: perl-Gnome2-1.048-1 perl-Gnome2-Canvas-1.006-1 perl-Gnome2-GConf-1.047-1 perl-Gnome2-Rsvg-0.12-1 perl-Gnome2-VFS-1.084-1 perl-Gnome2-Vte-0.12-1 perl-Gnome2-Wnck-0.18-1 perl-Gtk2-GladeXML-1.008-1 perl-Gtk2-SourceView2-0.12-1 perl-Gtk2-Spell-1.05-1 perl-Gtk2-Unique-0.07-1 There will be no further updates of these on Cygwin, which means that these distributions can no longer be used after the update of Perl to version 5.32 or later. -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
[ANNOUNCEMENT] Updated: cddlib-094m-1
Version 094m-1 of packages cddlib (source only) cddlib-devel cddlib-tools cddlib0 cddlibgmp0 are available in the Cygwin distribution: CHANGES Latest upstream release DESCRIPTION The C-library cddlib is a C implementation of the Double Description Method of Motzkin et al. for generating all vertices (i.e. extreme points) and extreme rays of a general convex polyhedron in R^d. HOMEPAGE https://people.inf.ethz.ch/fukudak/cdd_home/ Marco Atzeri If you have questions or comments, please send them to the cygwin mailing list at: cygwin (at) cygwin (dot) com . -- 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
Updated: cddlib-094m-1
Version 094m-1 of packages cddlib (source only) cddlib-devel cddlib-tools cddlib0 cddlibgmp0 are available in the Cygwin distribution: CHANGES Latest upstream release DESCRIPTION The C-library cddlib is a C implementation of the Double Description Method of Motzkin et al. for generating all vertices (i.e. extreme points) and extreme rays of a general convex polyhedron in R^d. HOMEPAGE https://people.inf.ethz.ch/fukudak/cdd_home/ Marco Atzeri If you have questions or comments, please send them to the cygwin mailing list at: cygwin (at) cygwin (dot) com .
Re: Can't open display issue from CMD
please reply to the mailing list On 16.01.2021 06:36, Sal Bellofiore wrote: Hi Marco, Thanks for the prompt response. The reason why I don't get asked for a password is because I have setup the RSA public key, and that works fine. When you say to check the remote scripts, what scripts are you referring to? I am not running any remote (Linux) scripts, I am only sending commands like pwd, ls -la, etc. Thanks Sal as also Achim reported the login scripts on the Linux server. https://www.gnu.org/software/bash/manual/html_node/Bash-Startup-Files.html#Bash-Startup-Files When you open a remote shell, it runs its login script: "When Bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable" -- 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
