Protection 360.
DATE:- 02-03-2021 RESPECTED CONSUMER, Hi, this email is from nortons security sign up by windscribe and the reason why we are sending this email to you because we like to inform you that the service which you have signed up with nortons security has expired. So the service will be Automatically renewed today and the renewal charges will be USD 299.99 for a 2 years contract and it will be automatically debited from your bank account because you have signed a contract with nortons security for auto-renewal . However, if you don't want to continue with our services you can call on this number+1 (512) -262-4379 .This is our cancellation department number and asks nortons security to cancel the service. If you wish to cancel the contract otherwise the contract will be renewed automatically and the money will be debited from your account and once it is debited from your bank account or your debit or credit card & you will be receiving the service call from the service team to give you the services. If you are unsatisfied with the services then we will instantly refund you your money back. Norton security THANK YOU SUPPORT NO:-+1 (512) -262-4379 . -- 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: segfault on 32bit cygwin snapshot
On Mon, 1 Mar 2021 21:25:42 +0900 Takashi Yano wrote: > On Mon, 1 Mar 2021 09:55:46 +0900 > Takashi Yano wrote: > > On Sun, 28 Feb 2021 19:48:28 +0100 > > Marco Atzeri wrote: > > > On 20.02.2021 23:29, Takashi Yano wrote: > > > > On Sat, 20 Feb 2021 22:01:38 +0100 > > > > Marco Atzeri wrote: > > > >> MC using latest snapshot 32bit 2021-02-19 (and 2021-02-10) > > > >> > > > >> now fails at startup with > > > >> > > > >> Exception: STATUS_ACCESS_VIOLATION at eip=61083736 > > > > > > > > Thanks for the report. I found the cause of this issue. > > > > I will submit a patch to fix it. > > > > > > > > > > mc is now fine with 2021-02-22 > > > > > > but I found another issue > > > > > > $ /usr/bin/lilypond > > > GNU LilyPond 2.20.0 > > > Segmentation fault (core dumped) > > > > > > on 3.1.7 it works fine > > > > I found this problem causes after the commit: > > > > commit 532b91d24e9496c7988b2b1dda7fc0e8b161f782 > > Author: Corinna Vinschen > > Date: Mon Dec 14 12:29:23 2020 +0100 > > > > Cygwin: Make sure newer apps get uname_x even when loading uname > > dynamically > > > > if an application built after API version 334 loads uname dynamically, > > it actually gets the old uname, rather than the new uname_x. Fix this > > by > > checking the apps API version in uname and call uname_x instead, if it's > > a newer app. > > > > Signed-off-by: Corinna Vinschen > > > > Reverting this commit solves the issue. > > > > Corinna, could you please have a look? > > The following check code does not work as expected if > newly build exe file is linked with old dll which calls > uname() as in this case. > > if (CYGWIN_VERSION_CHECK_FOR_UNAME_X) > return uname_x (in_name); > > Any idea? Ping Corinna? -- Takashi Yano -- 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: [ANNOUNCEMENT] Test: binutils-2.36.1-1, mingw64-{i686, x86_64}-binutils-2.36.1-1
On 2/28/2021 2:45 PM, Achim Gratz wrote: I encourage all Cygwin package maintainers to try building (and testing) their packages with the new binutils, but please do not (yet) release such packages until further notice. I just built emacs with the new binutils, both 64 bit and 32 bit. No problems building, and it seems to run fine. 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
GLM for MinGW at same version of the ones for CYGWIN?
Hello, with reference to this thread: https://cygwin.com/pipermail/cygwin/2020-December/247106.html recently, GLM for CYGWIN has been updated to 0.9.9.5. I'm wondering if it would be possible to do the same thing and update the GLM packages for MinGW to the same version. An update will simplify some things because, unlike 0.9.7, no additional patches are required. Sincerely. -- 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: segfault on 32bit cygwin snapshot
On Mar 2 20:03, Takashi Yano via Cygwin wrote: > On Mon, 1 Mar 2021 21:25:42 +0900 > Takashi Yano wrote: > > On Mon, 1 Mar 2021 09:55:46 +0900 > > Takashi Yano wrote: > > > On Sun, 28 Feb 2021 19:48:28 +0100 > > > Marco Atzeri wrote: > > > > On 20.02.2021 23:29, Takashi Yano wrote: > > > > > On Sat, 20 Feb 2021 22:01:38 +0100 > > > > > Marco Atzeri wrote: > > > > >> MC using latest snapshot 32bit 2021-02-19 (and 2021-02-10) > > > > >> > > > > >> now fails at startup with > > > > >> > > > > >> Exception: STATUS_ACCESS_VIOLATION at eip=61083736 > > > > > > > > > > Thanks for the report. I found the cause of this issue. > > > > > I will submit a patch to fix it. > > > > > > > > > > > > > mc is now fine with 2021-02-22 > > > > > > > > but I found another issue > > > > > > > > $ /usr/bin/lilypond > > > > GNU LilyPond 2.20.0 > > > > Segmentation fault (core dumped) > > > > > > > > on 3.1.7 it works fine > > > > > > I found this problem causes after the commit: > > > > > > commit 532b91d24e9496c7988b2b1dda7fc0e8b161f782 > > > Author: Corinna Vinschen > > > Date: Mon Dec 14 12:29:23 2020 +0100 > > > > > > Cygwin: Make sure newer apps get uname_x even when loading uname > > > dynamically > > > > > > if an application built after API version 334 loads uname dynamically, > > > it actually gets the old uname, rather than the new uname_x. Fix > > > this by > > > checking the apps API version in uname and call uname_x instead, if > > > it's > > > a newer app. > > > > > > Signed-off-by: Corinna Vinschen > > > > > > Reverting this commit solves the issue. > > > > > > Corinna, could you please have a look? > > > > The following check code does not work as expected if > > newly build exe file is linked with old dll which calls > > uname() as in this case. > > > > if (CYGWIN_VERSION_CHECK_FOR_UNAME_X) > > return uname_x (in_name); > > > > Any idea? > > Ping Corinna? I have no idea how we could fix that, other than by rebuilding the DLLs which call uname, too. We can't check the Cygwin build of all DLLs an executable is linked to. Corinna -- 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: Home directory was not created
On Mon, 1 Mar 2021 at 15:33, KAVALAGIOS Panagiotis (EEAS-EXT) wrote: > Dear all, > > Something went wrong to my Cygwin installation update (update is performed by > removing everything and installing again the new version). The home directory > of my user was not created, when you run Cygwin for the first time. When I > start Cygwin it defaults to the evil C:\Windows\System32!?!? > > -bash-4.4$ pwd > /cygdrive/c/WINDOWS/System32 > -bash-4.4$ cd > -bash: cd: /home/kavalpa: No such file or directory > -bash-4.4$ > > How this can be fixed in proper way, without causing any permission issues. These directories aren't normally created by the install scripts, but by the /etc/profile script the first time you create a login shell. You should see a message saying "Copying skeleton files. // These files are for the users to personalise their cygwin experience." when that happens. Therefore the key question here: how are you starting Cygwin? Adam -- 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
Uninstall python 2.7 fails - alternative dependencies
I attempted to remove all packages related to Python 2.7 from my cygwin installation. I am unable to remove four packages. python2 python27 python27-pip python27-setuptools There are over 500 packages that require python2 and over 700 packages which depend2 on python2. There are also around 90 packages that refer to both python2 and python3 packages. I have many of these packages installed. I suspect that at least some of these actually require either python2 or python3, but do not require both. To assist in supporting this kind of requirement, is there a way to create a package whose requirements are resolved by either of several other packages? For instance, could we have a package e.g. python-alternatives, that when required is satisfied by either python2 or python3. This mechanism might be useful for dealing with any set of packages that work with the alternatives system. Thanks for your consideration, Doug -- Doug Henderson, Calgary, Alberta, Canada - from gmail.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
Re: Uninstall python 2.7 fails - alternative dependencies
On Tue, 2 Mar 2021 at 17:33, Doug Henderson via Cygwin wrote: > To assist in supporting this kind of requirement, is there a way to > create a package whose requirements are resolved by either of several > other packages? > > For instance, could we have a package e.g. python-alternatives, that > when required is satisfied by either python2 or python3. This > mechanism might be useful for dealing with any set of packages that > work with the alternatives system. Yes, this function already exists in the form of the "provides" line in setup.hint files, discussed at https://cygwin.com/packaging-hint-files.html, although I don't believe the function is widely used. Per that page: If you think that another package has an incorrect dependency list, send email to cygwin-apps noting that fact. Adam -- 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
Fix to help novice users verify cygwin.com downloads
Hey I was searching for some articles about verifying files today and I came across this page: Cygwin FAQ (http://www.cygwin.com/faq.html) on your site. I noticed you recommend very thorough verification, using hashes and sigs. But usually the data file is downloaded much more than the hash or sig files. Users often don't verify. Just wanted to give you a heads up that we created a free open source program that both downloads and verifies in one step. So your users always verify. It's like "Cygwin FAQ", but it's a single command that downloads and verifies thoroughly: https://denova.com/open/safeget/developer/ Might be worth a mention on your page. Either way, keep up the awesome work! Cheers, Bob P.S. The best way to make sure downloaders verify files is to give them one command that downloads and verifies in one step. There's a free open source solution. -- 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: Home directory was not created
On 2021-03-02 01:08, KAVALAGIOS Panagiotis (EEAS-EXT) wrote: -Original Message- From: KAVALAGIOS Panagiotis (EEAS-EXT) Sent: 02 March 2021 08:15 To: cygwin@cygwin.com Subject: RE: Home directory was not created -Original Message- From: On Behalf Of Brian Inglis Sent: 01 March 2021 18:38 On 2021-03-01 08:33, KAVALAGIOS Panagiotis (EEAS-EXT) wrote: Something went wrong to my Cygwin installation update (update is performed by removing everything and installing again the new version). The home directory of my user was not created, when you run Cygwin for the first time. When I start Cygwin it defaults to the evil C:\Windows\System32!?!? -bash-4.4$ pwd /cygdrive/c/WINDOWS/System32 -bash-4.4$ cd -bash: cd: /home/kavalpa: No such file or directory -bash-4.4$ How this can be fixed in proper way, without causing any permission issues. By figuring out what went wrong during setup. Please respond attaching /var/log/setup.log.full and terminal or console log if possible. Otherwise just run setup-x86/_64 [-g] to upgrade without wiping everything to avoid such problems. The log is attached. I couldn't see any error except for the libgpg-error0 package that matches the "error" search term :) The home directory is created afterwards anyway at the first Cygwin execution, if it does not exist. Are you sure it is an installation error? I would rather avoid re-installing and fix the issue by creating the conditions and force Cygwin to create the home directory. [Hi Brian, I apologise for this personal e-mail. I have tried to send it twice to the list to no avail. It's not HTML and it does not appear to list's mail archive either. I have no idea what is going wrong.] zip 358KB > 256KB too big I think All postinstall steps failed because of BLODA or installation path: 2021/02/09 17:48:06 running: C:\Program Files\Cygwin\bin\dash.exe "/etc/postinstall/0p_000_autorebase.dash" 0 [main] dash (2296) shared_info::initialize: size of shared memory region changed from 49080 to 40888 2021/02/09 17:48:20 abnormal exit: exit code=-1073741819 ... Installing under Program\ Files causes issues because of space in path names and BLODA-like AV protections on those paths. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.] -- 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
texlive-collection-binextra & python
Ken can you check the python dependency of binextra ? https://cygwin.com/packages/summary/texlive-collection-binextra.html It pulls : python2, python27-pygments, python38-pygments It seems a bit too much 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: Uninstall python 2.7 fails - alternative dependencies
On 02.03.2021 18:32, Doug Henderson via Cygwin wrote: I attempted to remove all packages related to Python 2.7 from my cygwin installation. I am unable to remove four packages. python2 python27 python27-pip python27-setuptools Question: you can not remove because they are cross dependent or because they are pulled by other packages ? There are over 500 packages that require python2 and over 700 packages which depend2 on python2. much less $ cygcheck-dep -S -q -n python2| wc -w 124 $ cygcheck-dep -S -q -n python27| wc -w 145 and most are python2-* or python27-* packages There are also around 90 packages that refer to both python2 and python3 packages. I have many of these packages installed. I suspect that at least some of these actually require either python2 or python3, but do not require both. are you sure ? May be you are counting different releases ? Usually they should pull only one version of python. To assist in supporting this kind of requirement, is there a way to create a package whose requirements are resolved by either of several other packages? Not that I am aware For instance, could we have a package e.g. python-alternatives, that when required is satisfied by either python2 or python3. This mechanism might be useful for dealing with any set of packages that work with the alternatives system. Thanks for your consideration, Doug -- 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: texlive-collection-binextra & python
On 3/2/2021 3:36 PM, Marco Atzeri via Cygwin wrote: Ken can you check the python dependency of binextra ? https://cygwin.com/packages/summary/texlive-collection-binextra.html It pulls : python2, python27-pygments, python38-pygments It seems a bit too much Hi Marco, This happens because the pythontex package includes two versions of its scripts, one for python2 and one for python3. So cygport correctly detects the dependence on python2 (and python27-pygments). I could just remove the python2 versions of the scripts. That's what Debian does. 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
