Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Wed, 24 Sep 2003 16:18:38 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: tim DOT gunter AT bioscrypt DOT com cc: cygwin AT cygwin DOT com Subject: Re: Setup cant open package database error? In-Reply-To: <20030924200342.GB2264@bioscrypt.com> Message-ID: References: <20030924163349 DOT GA508 AT bioscrypt DOT com> <20030924200342 DOT GB2264 AT bioscrypt DOT com> Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 24 Sep 2003, Tim Gunter wrote: > On Wed, Sep 24, 2003 at 03:40:09PM -0400, Igor Pechtchanski wrote: > > If you moved the tarballs, setup won't be able to find them, and will > > re-download them. The log files don't matter, and will be created anew > > (the ones that matter sit in /var/log, anyway). > > i have not moved any of the tarballs that the last few updates have > downloaded, only tarballs from some months ago. when i look in the > directory where the new tarballs are supposed to be going, there > are no recently modified files except for setup.ini. shouldn't > there be the tarballs for the files setup is downloading and trying > to install? The setup package cache is just what it says: a cache. If you wish, you can blow the whole thing away, and setup will reconstruct it eventually. Some of the older (unneeded) packages will not be re-downloaded. For a smarter way to clean your cache, search this list for "clean_setup.pl". > > Make sure /etc/setup and /etc/setup/installed.db are writeable by you. > > both are writeable by me. installed.db, however, is an empty file. > there are installed.db.new and installed.db.old files which are > both non-empty. > > any ideas? > thanks for your help Igor. > --tim Setup doesn't overwrite /etc/setup/installed.db in place. Instead it creates /etc/setup/installed.db.new, writes the necessary content to it, then removes /etc/setup/installed.db and renames the .new file. I'm guessing the remove operation fails for you -- check the Windows ACLs on /etc/setup, is your user allowed to delete files? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- 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/