Fergus wrote:
> Setup stalled:
>
> Fatal Error: Uncaught Exception
> Thread: DialogProc
> Type: 9Exception
> Message: Package validation failure for
> release/gdbm/gdbm-1.8.3-9-src.tar.bz2
> AppErrNo: 1
>
> Incidentally gdbm-1.8.3-20 installed perfectly well into [1.7].
Try a different mirror. I
Setup stalled:
Fatal Error: Uncaught Exception
Thread: DialogProc
Type: 9Exception
Message: Package validation failure for
release/gdbm/gdbm-1.8.3-9-src.tar.bz2
AppErrNo: 1
Incidentally gdbm-1.8.3-20 installed perfectly well into [1.7].
Fergus
--
Unsubscribe info: http://cygwin.com/m
The upcoming Cygwin 1.7.0 release adds so many APIs and improves so much
functionality that it probably deserves a separate designation in
config.guess. For reference, notice the size of the most recent beta
announcement: http://cygwin.com/ml/cygwin-announce/2009-02/msg00018.html
For an example o
There was an unintended API change in this release, which caused the
cygncurses-8.dll to not be backwards compatible with previous DLLs of
the same name.
Sorry for the inconvenience.
--
Charles Wilson
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http:
There was an unintended API change in this release, which caused the
cygncurses-8.dll to not be backwards compatible with previous DLLs of
the same name.
Sorry for the inconvenience.
--
Charles Wilson
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http:
There was an unintended API change in the associated ncurses release. As
part of rolling back to the earlier known-good ncurses package, the
updated terminfo must also be rolled back.
Sorry for the inconvenience.
--
Charles Wilson
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simpl
There was an unintended API change in this release, which caused the
cygncurses-8.dll to not be backwards compatible with previous DLLs of
the same name.
Sorry for the inconvenience.
--
Charles Wilson
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http:
David Rothenberger wrote:
>
> Rolling back libncurses8 and terminfo to the previous release solves the
> problem for me. Recompiling lynx from source with the new libncurses8
> and terminfo packages also fixes the problem.
>
Confirmed bug. I've pulled the release.
Upstream has silently changed
On Thu, Feb 26, 2009 at 09:33:07PM -0500, Jason Pyeron wrote:
>> From: cygwin-ownerX
Oh! Is that who it came from?
>> [mailto:cygwin-ownerX
Yes. Got that the first time.
>> Sent: Thursday, February 26, 2009 18:36
Hmm. It's 10:18PM here.
>> To: cygwinX
What? You're responding to email to
> -Original Message-
> From: cygwin-ow...@cygwin.com
> [mailto:cygwin-ow...@cygwin.com] On Behalf Of Christopher Faylor
> Sent: Thursday, February 26, 2009 18:36
> To: cygwin@cygwin.com
> Subject: Re: Another long pathname question
>
> On Thu, Feb 26, 2009 at 02:29:57PM -0500, Greg Fre
On Thu, Feb 19, 2009 at 09:27:34AM -0500, Christopher Faylor wrote:
>On Thu, Feb 19, 2009 at 09:16:50AM -0500, Andrew Schulman wrote:
>>I'm compiling screen for 1.7. The configure script has a test for a "usable"
>>pipe implementation, which passes, and another one for a "working" pipe
>>implement
On Thu, Feb 26, 2009 at 02:29:57PM -0500, Greg Freemyer wrote:
>If the path is short, it uses the full long directory name as
>expected. If the path exceeds 260, it reverts to using the 8.3 names,
>thus giving a workaround that will allow you to descend deeper into a
>directory structure.
>
>Inter
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
jamesmikedup...@googlemail.com wrote:
I am not able to really see what is going on, process explorer says
cygwin1!aclcheck
Otherwise, I have seen it hang in some function that I cannot remember
exactly ascii convert or something and other vista kernel functions.
Basically, I would like to kn
OKAY, I have some passwd questions & problems associated with cygwin 1.7.
PRIOR to 1.7, my UID/GID for "Paul" account was 501/401 and all of my
files have correct ownership. When I created /etc/passwd via:
cd /etc
mkpasswk -l -p $HOME >x
vim x { changed: UID/GID to 501/4
Simple test case. This application uses the C locale (by virtue of the fact
that we did not use setlocale(), and evidenced by mb_cur_max of 1). On Linux,
this correctly shows wctomb rejecting the conversion (0x100 is too big to fit
in a 1-byte sequence) with EILSEQ, but newlib currently trunca
Dave Korn wrote:
> you should definitely see if it reproduces under 1.7
I tried the latest 1.7 and it hangs instead of segfaulting (less than 500k
iterations).
This seems like a pretty major problem for any intensive multithreaded
application. Though infrequent, it has produced a rather large r
On Thu, Feb 26, 2009 at 4:19 AM, Corinna Vinschen
wrote:
> On Feb 25 18:58, Greg Freemyer wrote:
>> I just read the release email for 1.7.0
>>
>> In part it says:
>>
>> - Fallout from the long path names: If the current working directory is
>> longer than 260 bytes, or if the current working dir
On 2/26/2009 9:55 AM, Sivaram Neelakantan wrote:
"Larry Hall (Cygwin)" writes:
Morten Kjærulff wrote:
On Thu, Feb 26, 2009 at 12:10 AM, Larry Hall (Cygwin)
wrote:
Morten Kjærulff wrote:
Hi,
On my machine#2 I just installed lynx, but it just exit without
telling anything. Then I went to my
Hi there,
I would like to first thank the entire cygwin team for providing such
a great tool that saved me countless times in corporate hell.
Now, I compiled large application that I am working on from another platform
with gcc on cygwin in vista, and I found that it does not even startup proper
"Larry Hall (Cygwin)" writes:
> Morten Kjærulff wrote:
>> On Thu, Feb 26, 2009 at 12:10 AM, Larry Hall (Cygwin)
>> wrote:
>>> Morten Kjærulff wrote:
Hi,
On my machine#2 I just installed lynx, but it just exit without
telling anything. Then I went to my machine#1 where lynx wa
> Has the correct version of 'tack' been built and packaged? It appears that
> version 1.05
> was built and packaged as version 1.06-1.
>
> $ cygcheck -c tack
> Cygwin Package Information
> Package VersionStatus
> tack 1.06-1 OK
>
>
> $ tack -V
> tack v
On Feb 26 10:10, Corinna Vinschen wrote:
> On Feb 25 19:20, Greg Freemyer wrote:
> > On Wed, Feb 25, 2009 at 6:01 PM, Larry Hall (Cygwin)
> > wrote:
> > > Greg Freemyer wrote:
> > >
> > >
> > >> Time to experiment with Cygwin 1.7
> > >>
> > >> I know the whole package is still considered test. H
On Feb 26 10:39, Frank Fesevur wrote:
> 2009/2/26 Corinna Vinschen:
> > On Feb 25 16:12, Frank Fesevur wrote:
> >> Since this is a security fix, will there be a 1.5 update as well?
> >
> > Well, actually I have no intention to update 1.5.x packages anymore.
>
> I understand you want us to start us
2009/2/26 Corinna Vinschen:
> On Feb 25 16:12, Frank Fesevur wrote:
>> Since this is a security fix, will there be a 1.5 update as well?
>
> Well, actually I have no intention to update 1.5.x packages anymore.
I understand you want us to start using 1.7, but in the announcement
of 1.7.0-41 you wri
On Feb 25 18:58, Greg Freemyer wrote:
> I just read the release email for 1.7.0
>
> In part it says:
>
> - Fallout from the long path names: If the current working directory is
> longer than 260 bytes, or if the current working directory is a virtual
> path (like /proc, /cygdrive, //server),
On Feb 25 16:12, Frank Fesevur wrote:
> 2009/2/25 Corinna Vinschen:
> > I've just updated the Cygwin 1.7 version of OpenSSH to 5.2p1-1.
> >
> > This is a new major upstream release. It fixes a security related issue
> > and introdues a lot of new features. The Cygwin release is created
> > from t
On Feb 25 19:20, Greg Freemyer wrote:
> On Wed, Feb 25, 2009 at 6:01 PM, Larry Hall (Cygwin)
> wrote:
> > Greg Freemyer wrote:
> >
> >
> >> Time to experiment with Cygwin 1.7
> >>
> >> I know the whole package is still considered test. How stable is the
> >> actual dll(s). Especially as relates
On Feb 26 00:28, Paul McFerrin wrote:
> Corinnia:
> I finally got cygwin 1.7 swapped-in to try to reproduce my problem.
> Good news, after a few hours of pinging a website, ZERO ERRORS for now.
> Since it is an intermittent error, I'll let it run at 6 seconds interval
> until tomorrow.
>
>
29 matches
Mail list logo