public inbox for
 help / color / mirror / Atom feed
From: Christian Franke <>
Subject: Re: How to get setup to *re*install a package from the command line
Date: Thu, 8 Sep 2022 08:00:34 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Eliot Moss wrote:
> I've not been able to find a way to get setup, when used from the command
> line, to *re*install an existing package, so as to repair any brokenness.
> For context, I had my disk get trashed and restored from a cloud backup.
> However, that tool is not entirely competent about everything, e.g., 
> links.

Often such backup tools cannot handle reparse points, so for the future 
you might want to set CYGWIN=winsymlinks:lnk or ...:sys. The latter 
requires that the tool handles SYSTEM files properly.

Another problem might occur if incremental backups are used: If a DLL is 
rebased, the write timestamp does not change because memory mapped files 
are used. Then there is (AFAIK) no way to detect file modification 
except comparing its data with previous backup. A full rebase after 
restore should help then.

> Most programs work ok, but others clearly are not quite right.  So I 
> want to
> try re-installing all installed packages.  But there does not seem to 
> be any
> way to get command line setup to Reinstall something that is already
> installed, though the GUI tool can certainly do it.

If data in /etc/setup is still intact, a quick way with the GUI should 
be run to the recent 2.921 RC release of setup, select the "Up To Date" 
view and then press and hold Ctrl+R.


  parent reply	other threads:[~2022-09-08  6:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08  2:54 Eliot Moss
2022-09-08  5:28 ` ASSI
2022-09-08  6:00 ` Christian Franke [this message]
2022-09-08 14:31   ` Eliot Moss

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).