delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2006/01/31/08:17:41

X-Spam-Check-By: sourceware.org
Message-ID: <43DF6369.2020904@byu.net>
Date: Tue, 31 Jan 2006 06:17:29 -0700
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: Ismael Valladolid Torres <ivalladt AT punkass DOT com>
CC: cygwin AT cygwin DOT com
Subject: Re: Bash got messed after update
References: <20060131094946 DOT GA1908 AT spma33>
In-Reply-To: <20060131094946.GA1908@spma33>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Ismael Valladolid Torres on 1/31/2006 2:49 AM:
> I just installed using setup.exe the readline devel package, and as
> usual some other packages got updated. Later when opening an xterm
> I've noticed some oddities in my bash session, i.e. cwd is `/' instead
> of `~', running `ls --color' gives a strange color to directories, `.' is
> in my path when I'm not putting it there in any of my setup files,
> `/usr/local/bin' is no longer in my path, etc.

Sounds like your installation lost track of where $HOME should be set to,
so it is not picking up any of your setup files, explaining the follow-on
behavior changes.

> 
> All these symptoms even after rebooting.

Rebooting won't rerun postinstall scripts.  It is easiest to explicitly
rerun setup.exe and reinstall the packages (such as bash) that had botched
postinstall runs.  If, after that, you still have problems, the attached
output of cygcheck -svr is essential to us helping you.

> 
> Yes, an xterm window running bash was open, this should not be an
> issue, should it?

Actually, it would be an issue.  Bash can't upgrade itself while bash is
running, which makes all postinstall scripts suspect.  Upgrades work best
when all cygwin processes are halted.

> 
> 2006/01/31 09:42:16 Installing file://C:\cygwin/http%3a%2f%2fftp.rediris.es%2fmirror%2fcygwin/release/cygwin/cygwin-1.5.19-4.tar.bz2
> 2006/01/31 09:42:17 io_stream_cygfile: fopen failed 13 Permission denied
> 2006/01/31 09:42:17 Failed to open cygfile:///usr/bin/cygwin1.dll for writing.
> 2006/01/31 09:42:20 Scheduled reboot replacement of file C:\cygwin/bin//cygwin1.dll with C:\cygwin/bin//cygwin1.dll.new
> 
> The same as before.

You aren't quite painting an accurate picture - you upgraded more than
just bash; you also picked up an upgrade to cygwin.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD32Np84KuGfSFAYARAhzuAKC6dGP3tM4lfL9lSGhZAl8CAH3OZACgsQy5
tYPnv7jyYVpYfoy85aj5ik0=
=RYFU
-----END PGP SIGNATURE-----

--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019