Re: msmtp depends on Gnome!?
On 2018-03-28 15:50, Stephen Paul Carrier wrote: > msmtp is billed as a light-weight SMTP client and I would like to use > it with cron instead of ssmtp. > What's not light-weight is its dependency on libgnome-keyring0 which > has more dependencies that eventually bring in Gnome. This is for a > headless workstation. > Is it possible to remove or replace this dependency so that msmtp can > be installed without enlarging the size of the install by such a factor? Look at the other packages under the Mail category e.g. email, mailutils, nmh. I've poked around with some of them, and most are pretty easy to set up and use, depending on your requirements. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: git-review-1.26.0-1
git-review has been updated to 1.26.0. DESCRIPTION: git-review is a tool that helps submitting git branches to gerrit for review. QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. -- David Rothenberger daver...@acm.org -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug in Python3 ('tempfile' and 'subprocess')
Hi,
Using freshly-updated Cygwin 64-bit under Windows 7 Enterprise Ver 6.1
and Python 3 version 3.6.4.
Executing the following script:
import subprocess
import _hashlib
import _sha3
subprocess.run('pwd')
always results in 'BlockingIOError: [Errno 11] Resource temporarily
unavailable'. I saw this error first in a script that imported
'tempfile' together with 'subprocess'. I then managed to narrow down
the problem to the '_sha3' module. Notice that you need to import both
'_hashlib' and '_sha3' *in that order*.
This problem makes it impossible to use 'tempfile' and 'subprocess' in
the same script. My workaround is currently to disable '_sha3' in
'/usr/lib/python3.6/hashlib.py' by adding at line 62:
__always_supported = __always_supported[0:8]
This problem only happens in Cygwin 64, 32-bit Cygwin works ok.
Can anyone reproduce this problem?
Best regards,
Giuseppe
--
Giuseppe B. Scelsi (giuseppe.sce...@analog.com)
Senior Design Engineer, Analog Devices Australia Pty Ltd
Unit 3, 97 Lewis Road, Wantirna, Victoria, 3152, AUSTRALIA
Direct: +61 3 9881 9909 Main: +61 3 9881
Fax: +61 3 9881 9988 Web: www.analog.com/au
Embedded & Digital Signal Processing Software.
This communication is proprietary and confidential.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: msmtp depends on Gnome!?
On 28/03/2018 22:50, Stephen Paul Carrier wrote: What's not light-weight is its dependency on libgnome-keyring0 which has more dependencies that eventually bring in Gnome. This is for a headless workstation. Gnome doesn't just contain the desktop libraries, it also contains the libraries for gobject. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
msmtp depends on Gnome!?
Dear cygwin people, msmtp is billed as a light-weight SMTP client and I would like to use it with cron instead of ssmtp. What's not light-weight is its dependency on libgnome-keyring0 which has more dependencies that eventually bring in Gnome. This is for a headless workstation. Is it possible to remove or replace this dependency so that msmtp can be installed without enlarging the size of the install by such a factor? Thanks! Stephen Carrier -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: X Windows does not launch under the 20180309 snapshot
> On 2018-03-11 17:10, Denis Excoffier wrote: > > Hello, > > Difficult for me to give more detail: X Windows does not launch under the > last snapshot (dated 20180309), > while everything goes well under the previous one (dated 20180220). > With the updates shown in the cygwin-cvs mailing list up to (and including) 2018-03-26, all seems fine now. Thanks. Regards, Denis Excoffier. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Filemode change by windows applications
Greetings, Eliot Moss! > On 3/28/2018 10:40 AM, Eliot Moss wrote: >> On 3/28/2018 10:11 AM, Andrey Repin wrote: >> and is there anything I can do to prevent windows applications from setting the execute bit on my files? >>> >>> No, and you will be unable to use Windows associations, if you clear >>> execute bit >>> on documents. >> >> Interesting that you think so, Andrey. I just tested this on my Windows 10 >> Surface Book. I used Windows Explorer to navigate to a folder where I had >> cleared the x bits from a .docx file (setting mode to 660 with chmod in >> Cygwin), and clicking on the file opened Word on the file just fine. Maybe >> this behavior is dependent on some other things as well? > Here is getfacl output for the file in question: > # file: Progress Letters S16.docx > # owner: moss > # group: moss > user::rw- > group::--- > group:SYSTEM:r-x#effective:r-- > group:Cygwin:rwx#effective:rw- > mask:rw- > other:--- If you ANSOLUTELY remove execute bit (this is often happens on samba shares managed by POSIX ACL for example, when you create file with POSIX tools before Samba have a say about permissions), things break hard. > So there are underlying x bits of some kind, but Cygwin does display > mode 660 via ls -l (for example). > Still, we entirely agree that there is not really a way to prevent a > Windows program from setting the x bits. Here is getfacl from another > file in the same folder, reflecting how Word sets the permissions: > # file: Progress Letters S17.docx > # owner: moss > # group: moss > # flags: -s- > user::rwx > group::--- > group:SYSTEM:r-x > group:Cygwin:rwx > mask:rwx > other:r-x > I think the key difference is "mask". Cygwin way of treating Windows ACL's is still kind of mystery to me. I know they works… somehow. But I prefer to stay away from them, where possible. I need interoperability over "zealous POSIX compatibility". -- With best regards, Andrey Repin Wednesday, March 28, 2018 19:10:43 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Filemode change by windows applications
On 3/28/2018 10:27 AM, Kjetil Østerås wrote: Do you know where I can find documentation or source code that describes the mapping that cygwin implements? See: https://cygwin.com/cygwin-ug-net/ntsec.html This is referenced in the Cygwin FAQ. It's complicated, but I think the doc explains it. Corinna (or someone) can correct us if the doc is not up to date ... As for source code, all the source for Cygwin is available. Probably not for the average user of Cygwin to try to dig into, since you need pretty deep knowledge of both Windows APIs and of Posix semantics, but everything is there, and useful patches will always be considered. Regards - Eliot -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Filemode change by windows applications
On 3/28/2018 10:40 AM, Eliot Moss wrote: On 3/28/2018 10:11 AM, Andrey Repin wrote: and is there anything I can do to prevent windows applications from setting the execute bit on my files? No, and you will be unable to use Windows associations, if you clear execute bit on documents. Interesting that you think so, Andrey. I just tested this on my Windows 10 Surface Book. I used Windows Explorer to navigate to a folder where I had cleared the x bits from a .docx file (setting mode to 660 with chmod in Cygwin), and clicking on the file opened Word on the file just fine. Maybe this behavior is dependent on some other things as well? Here is getfacl output for the file in question: # file: Progress Letters S16.docx # owner: moss # group: moss user::rw- group::--- group:SYSTEM:r-x#effective:r-- group:Cygwin:rwx#effective:rw- mask:rw- other:--- So there are underlying x bits of some kind, but Cygwin does display mode 660 via ls -l (for example). Still, we entirely agree that there is not really a way to prevent a Windows program from setting the x bits. Here is getfacl from another file in the same folder, reflecting how Word sets the permissions: # file: Progress Letters S17.docx # owner: moss # group: moss # flags: -s- user::rwx group::--- group:SYSTEM:r-x group:Cygwin:rwx mask:rwx other:r-x I think the key difference is "mask". Regards - Eliot -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Filemode change by windows applications
On 3/28/2018 10:11 AM, Andrey Repin wrote: and is there anything I can do to prevent windows applications from setting the execute bit on my files? No, and you will be unable to use Windows associations, if you clear execute bit on documents. Interesting that you think so, Andrey. I just tested this on my Windows 10 Surface Book. I used Windows Explorer to navigate to a folder where I had cleared the x bits from a .docx file (setting mode to 660 with chmod in Cygwin), and clicking on the file opened Word on the file just fine. Maybe this behavior is dependent on some other things as well? Regards - Eliot -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Filemode change by windows applications
Hi Eliot, Do you know where I can find documentation or source code that describes the mapping that cygwin implements? 2018-03-28 15:06 GMT+02:00 Eliot Moss : > On 3/28/2018 3:09 AM, Kjetil Østerås wrote: > > I notice that when I edit and save a file in a windows application this >> file sometimes get the execute file permission set in cygwin. Some windows >> applications do this and some don't. For instance in my setup if i modify >> a >> .c file using Meld then the execute bit is set, however when I modify the >> same file with sublime text 3 then the execute bit is not set. >> >> Why does this happen? and is there anything I can do to prevent windows >> applications from setting the execute bit on my files? >> > > The Windows file permissions (access control) is substantially different > from the Posix model that Cygwin attempts to present. The mapping from > Windows to Posix that Cygwin implements is arguably the best / most > reasonable mapping between the disparate schemes, and has been carefully > refined over time. But it is just a mapping from the underlying scheme. > > So, if some Windows program sets permissions a particular way, that it how > they show up under Cygwin. To answer your question more directly: No, you > can't prevent a Windows program from setting (the underlying access modes > that translate to what is presented as) the execute bit under Cygwin - > short of preventing the programs from accessing the file altogether, > presumably not what you want. > > File access translation is perhaps one of the roughest edges that Cygwin > *tries* to smooth over. I think it does a good job with what it has, but > the Windows scheme is complex and there is no perfect way to do this. > > Note, though, that there is no good way to prevent a Unix program from > setting execute bits on a particular file either (well, the umask, and > possibly ACLs may give you some control if you want to go to the bother). > It's just that Unix programs don't tend to set that bit unless they are > creating an executable. > > Someone more versed in the Windows access control scheme and the intention > of various permissions might be able to clarify why some many Windows > programs think it is a good thing to set the access mode(s) that Cygwin > reflects as the x bit ... > > Regards - Eliot Moss > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > -- Kjetil Østerås -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Filemode change by windows applications
Greetings, Kjetil Østerås! > I notice that when I edit and save a file in a windows application this > file sometimes get the execute file permission set in cygwin. Some windows > applications do this and some don't. For instance in my setup if i modify a > .c file using Meld then the execute bit is set, however when I modify the > same file with sublime text 3 then the execute bit is not set. > Why does this happen? This is how Windows operates. Please do not use Windows programs inside Cygwin installation tree. > and is there anything I can do to prevent windows > applications from setting the execute bit on my files? No, and you will be unable to use Windows associations, if you clear execute bit on documents. -- With best regards, Andrey Repin Wednesday, March 28, 2018 17:09:24 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Problem with NC.1.107
Greetings, Jay Cotton! > Just installed nc 1.107-4 expecting to use it to debug some code. > This is what I get when I try to run it. > $ nc 192.168.1.135 23 > bash: /usr/bin/nc: Permission denied [C:\Programs\Cygwin_64\bin]$ nc.exe 192.168.1.1 23 ♥ Dlink-Router login: [C:\Programs\Cygwin_64\bin]$ Since nc does not reply to --version, I have no way to tell if it's the same you are running with. > The file permissions are messed up. > $ file /usr/bin/nc > /usr/bin/nc: writable, executable, regular file, no read permission > I don't see the PE32+ executable (console) x86-64, for MS Windows > string. > here is the file in /usr/bin > $ ls -l nc* > -rwxr-xr-x 1 lbmgm lbmgm 24576 Mar 19 2013 nc.exe > I looked at the make file, it seems to be o.k. for generating a > runable program. (uses gcc) but I don't have enough stuff installed > to allow a build. -- With best regards, Andrey Repin Wednesday, March 28, 2018 17:07:26 Sorry for my terrible english...
Re: Problem with NC.1.107
On 27/03/2018 20:13, Jay Cotton wrote: Just installed nc 1.107-4 expecting to use it to debug some code. This is what I get when I try to run it. $ nc 192.168.1.135 23 bash: /usr/bin/nc: Permission denied most Antivirus block the nc program Reards Marco -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Filemode change by windows applications
On 3/28/2018 3:09 AM, Kjetil Østerås wrote: I notice that when I edit and save a file in a windows application this file sometimes get the execute file permission set in cygwin. Some windows applications do this and some don't. For instance in my setup if i modify a .c file using Meld then the execute bit is set, however when I modify the same file with sublime text 3 then the execute bit is not set. Why does this happen? and is there anything I can do to prevent windows applications from setting the execute bit on my files? The Windows file permissions (access control) is substantially different from the Posix model that Cygwin attempts to present. The mapping from Windows to Posix that Cygwin implements is arguably the best / most reasonable mapping between the disparate schemes, and has been carefully refined over time. But it is just a mapping from the underlying scheme. So, if some Windows program sets permissions a particular way, that it how they show up under Cygwin. To answer your question more directly: No, you can't prevent a Windows program from setting (the underlying access modes that translate to what is presented as) the execute bit under Cygwin - short of preventing the programs from accessing the file altogether, presumably not what you want. File access translation is perhaps one of the roughest edges that Cygwin *tries* to smooth over. I think it does a good job with what it has, but the Windows scheme is complex and there is no perfect way to do this. Note, though, that there is no good way to prevent a Unix program from setting execute bits on a particular file either (well, the umask, and possibly ACLs may give you some control if you want to go to the bother). It's just that Unix programs don't tend to set that bit unless they are creating an executable. Someone more versed in the Windows access control scheme and the intention of various permissions might be able to clarify why some many Windows programs think it is a good thing to set the access mode(s) that Cygwin reflects as the x bit ... Regards - Eliot Moss -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: ruby-puppet-lint-2.3.5-1
The following packages have been updated in the Cygwin distribution: * ruby-puppet-lint-2.3.5-1 * ruby-puppet-lint-doc-2.3.5-1 puppet-lint is a command line tool that checks your Puppet manifests against the Puppetlabs style guide and alerts you to any discrepancies. This is an update to the latest upstream release. Dave. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Filemode change by windows applications
Hi, I notice that when I edit and save a file in a windows application this file sometimes get the execute file permission set in cygwin. Some windows applications do this and some don't. For instance in my setup if i modify a .c file using Meld then the execute bit is set, however when I modify the same file with sublime text 3 then the execute bit is not set. Why does this happen? and is there anything I can do to prevent windows applications from setting the execute bit on my files? -- Kjetil Østerås -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
