Greetings, Warren Young!
> On Jan 10, 2016, at 4:52 PM, Juan Miguel Navarro Martínez wrote:
>>
>> No software version can live forever
> Indeed, not even Linux.
> There’s a thread over on the CentOS mailing list right now started by
> someone who’s trying to get something working on CentOS 3, w
On 2016-01-11 16:58, Christian-Manuel Röderer wrote:
is anyone else experiencing problems with the current versions of the
lxml package for python 3 (python-lxml-3.2.3-1 and
python-lxml-3.4.4-1, 64 bit)?
Those are for Python 2.7. For Python 3.4 you need python3-lxml.
--
Yaakov
--
Problem rep
Dear list,
is anyone else experiencing problems with the current versions of the
lxml package for python 3 (python-lxml-3.2.3-1 and
python-lxml-3.4.4-1, 64 bit)? It seems to install correctly (and so do
the dependencies) but then it seems to be incomplete:
$ python3.4
Python 3.4.3 (default, May
On Mon, 11 Jan 2016, Erik Soderquist wrote:
Date: Mon, 11 Jan 2016 15:26:39 -0500
From: Erik Soderquist
Subject: Re: Windows XP Support
Greetings, Erik,
On Mon, Jan 11, 2016 at 2:59 PM, cyg Simple wrote:
Arguments like this is the reason I had to spend years searching through
COBOL code for
Hi there,
I'm using a python wrapper (python-magic,
https://github.com/ahupp/python-magic) checking some filetypes in a small
script. The wrapper works fine under Unix-like system, but I got an access
violation error under cygwin. I already tried an older version of file
including libmagic from
On Mon, Jan 11, 2016 at 2:59 PM, cyg Simple wrote:
> Arguments like this is the reason I had to spend years searching through
> COBOL code for 2 digit years. Old habits seem hard to die. Either
> upgrade or forever pay the penalty yourself to keep the old code running.
Actually I agree wholehear
On 1/11/2016 12:05 PM, Erik Soderquist wrote:
> On Sun, Jan 10, 2016 at 6:52 PM, Juan Miguel Navarro Martínez wrote:
>> No software version can live forever, ...
>
> Personally, I have to disagree with this statement, or at least offer
> an amendment...
>
> I have some things still running in DO
Hi Cygwin friends and users,
I released TEST version 2.4.0-0.18 of Cygwin. This is the last test
release if nothing unexpected happens. I plan to release officially
on Friday.
What's new:
---
- New, unified implementation of POSIX permission and ACL handling. The
new ACLs now stor
On Jan 11 09:25, Warren Young wrote:
> On Jan 11, 2016, at 4:52 AM, Corinna Vinschen
> wrote:
> >
> > Continuing support for XP and Server 2003 is really becoming a
> > burden. It requires to code and maintain workarounds which are not
> > required anymore in newer OSes, so I really would like
On Jan 11 16:13, Henri wrote:
> Corinna Vinschen cygwin.com> writes:
> > Can you please provide the socket testcase?
>
> Trying to send you what you ask for (using gmane.org, I have to copy/paste)
Thanks! I applied a patch and created a new developer snapshot. I'll
also upload a new cygwin tes
On Jan 10, 2016, at 4:52 PM, Juan Miguel Navarro Martínez
wrote:
>
> No software version can live forever
Indeed, not even Linux.
There’s a thread over on the CentOS mailing list right now started by someone
who’s trying to get something working on CentOS 3, which is about three years
younge
Windows XP still accounts for about 10% of desktop users... Similar to the
total number of Mac users.
Maybe some browser OS stats from cygwin.com would be illuminating.
Jon
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
On Mon, Jan 11, 2016 at 9:38 AM, wilson wrote:
> I'd like to say a sincere thank you to Corina (and the rest of the team) for
> supporting XP for this long, and I hope she stays so busy the issue of
> removing XP support never becomes a priority. :)
I rather expect it will more be a matter of a bu
On Sun, Jan 10, 2016 at 6:52 PM, Juan Miguel Navarro Martínez wrote:
> No software version can live forever, ...
Personally, I have to disagree with this statement, or at least offer
an amendment...
I have some things still running in DOS 5 in a virtual machine because
that is the most effective
On Jan 10, 2016, at 5:12 AM, Herbert Stocker wrote:
>
> WinXP is still a good OS.
That was only true while Microsoft was maintaining it. Now there are many
known security vulnerabilities which will never be patched.
I expect there are other problems with it, too, like incorrect time zone
sup
On Jan 11, 2016, at 4:52 AM, Corinna Vinschen wrote:
>
> Continuing support for XP and Server 2003 is really becoming a
> burden. It requires to code and maintain workarounds which are not
> required anymore in newer OSes, so I really would like to get rid of
> that stuff.
I seem to recall you
On 1/11/2016 7:41 AM, Warren Young wrote:
On Jan 9, 2016, at 2:11 AM, Zac G. Al Wakeel wrote:
For the archives, would you say which software was causing the problem?
I was using Avast, free software.
Then I recommend uninstalling it and switching to Windows Defender. I predict
that yo
Corinna Vinschen cygwin.com> writes:
> Can you please provide the socket testcase?
Trying to send you what you ask for (using gmane.org, I have to copy/paste)
- t_stat3.c:
/*\
* Copyright (C) Michael Ker
On Jan 11 15:35, Henri wrote:
> Corinna Vinschen cygwin.com> writes:
>
> > > > As a final point, I also tested FIFOs and (unix domain) sockets.
> > > >
> > > > FIFOs pass the test, sockets do not.
> > >
> > > Yes, that's expected. The underlying hack^Wmethod is the same for sockets
> > > and p
On Jan 9, 2016, at 2:11 AM, Zac G. Al Wakeel wrote:
>
>> For the archives, would you say which software was causing the problem?
>
> I was using Avast, free software.
Then I recommend uninstalling it and switching to Windows Defender. I predict
that your problems will not return.
--
Problem
Corinna Vinschen cygwin.com> writes:
> > > As a final point, I also tested FIFOs and (unix domain) sockets.
> > >
> > > FIFOs pass the test, sockets do not.
> >
> > Yes, that's expected. The underlying hack^Wmethod is the same for sockets
> > and pipes, while FIFOs have a real path on a real f
On Jan 10 13:12, Herbert Stocker wrote:
Hi, i have read that beginning this month Cygwin wants to drop support
for Windows XP. Though the home page and FAQ entry 12 do not talk
about this. Are they out of date or is WinXP still supported?
So far, nothing has changed, XP is still supported. I
On Jan 8 17:30, Corinna Vinschen wrote:
> On Jan 8 17:12, Houder wrote:
> > On 2016-01-08 16:19, Corinna Vinschen wrote:
> > >On Jan 4 10:24, Houder wrote:
> > >>On 2016-01-04 09:52, Marco Atzeri wrote:
> > >>>On 04/01/2016 09:03, Houder wrote:
> > Hi Corinna,
> >
> > I have been lo
On Jan 10 13:12, Herbert Stocker wrote:
> Hi,
>
> i have read that beginning this month Cygwin wants to drop support
> for Windows XP. Though the home page and FAQ entry 12 do not talk
> about this. Are they out of date or is WinXP still supported?
So far, nothing has changed, XP is still suppor
On Jan 10 22:54, Bryan Henry wrote:
> Hi Corinna,
>
> Sorry for the delay getting back to you. I tested out the cygpath
> binary from the latest snapshot and confirmed that it fixes my issue.
> Thank for you making the change!
You're welcome. Thanks for testing.
Corinna
--
Corinna Vinschen
On Jan 10 05:04, John Hood wrote:
> On 1/9/2016 9:41 AM, Corinna Vinschen wrote:
> >I fixed the code and took the opportunity to clean it up a little using
> >>basically the (fixed) patch I proposed two days ago.
> >>
> >>I've just uploaded new developer snapshots tohttps://cygwin.com/snapshots/
>
Hello
I am trying to upgrade Cygwin on Win7 remotely through sshd, using
some small scripts but without success it always show:
Changing gid back to original
running: c:\cygwin\bin\dash.exe "/etc/postinstall/0p_000_autorebase.dash"
abnormal exit: exit code=-1073741819
running: c:\cygwin\b
27 matches
Mail list logo
