On Wed, 3 Aug 2005, Stein Somers wrote:
Unfortunately, I was too eager to try the upgrade to note the version it
was upgraded from.
FYI, the information about all of your upgrades done via Cygwin setup
(including the version you upgraded from) can be obtained from
/var/log/setup.log.
I think
Igor Pechtchanski wrote:
FYI, the information about all of your upgrades done via Cygwin setup
(including the version you upgraded from) can be obtained from
/var/log/setup.log.
I actually checked this file on my machine (and all others changed
recently) and couldn't find anything relevant.
On 8/3/05, Igor Pechtchanski wrote:
On Wed, 3 Aug 2005, Stein Somers wrote:
Unfortunately, I was too eager to try the upgrade to note the version it
was upgraded from.
FYI, the information about all of your upgrades done via Cygwin setup
(including the version you upgraded from) can be
On Wed, 3 Aug 2005, Joshua Daniel Franklin wrote:
On 8/3/05, Igor Pechtchanski wrote:
On Wed, 3 Aug 2005, Stein Somers wrote:
Unfortunately, I was too eager to try the upgrade to note the version it
was upgraded from.
FYI, the information about all of your upgrades done via Cygwin
Stein Somers wrote:
In short, cygwin 1.5.17-1 good, 1.5.18-1 bad. As Gerrit wrote from the
start.
Just as a point of strange coincidence, cygwin 1.5.17-1 good, 1.5.18-1 bad
seems to be the case with the recent Python and Postgres problems reported
as well. Also both appear on the surface
On Aug 3 15:38, Jon A. Lambert wrote:
Stein Somers wrote:
In short, cygwin 1.5.17-1 good, 1.5.18-1 bad. As Gerrit wrote from the
start.
Just as a point of strange coincidence, cygwin 1.5.17-1 good, 1.5.18-1
bad seems to be the case with the recent Python and Postgres problems
Corinna Vinschen wrote:
http://cygwin.com/problems.html
I've already done gone and did that.
I'm happy on existing configuration.
I withdraw my casual observation.
--
J Lambert
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
On Aug 3, 2005, at 3:38 PM, Jon A. Lambert indited:
Stein Somers wrote:
In short, cygwin 1.5.17-1 good, 1.5.18-1 bad. As Gerrit wrote from
the
start.
Just as a point of strange coincidence, cygwin 1.5.17-1 good,
1.5.18-1 bad seems to be the case with the recent Python and
Postgres
8 matches
Mail list logo
