public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: help needed - transition from 32bits to 64bits
Date: Thu, 15 Jun 2023 19:21:28 +0200	[thread overview]
Message-ID: <87jzw4bq07.fsf@Rainer.invalid> (raw)
In-Reply-To: <43976.2997253396$1686824142@news.gmane.org> (gh via Cygwin's message of "Thu, 15 Jun 2023 12:15:00 +0200")

gh via Cygwin writes:
> Currently, cygwin is in C:\cygwin, which I have moved to
> C:\cygwin-bck. I then want to install in the now almost empty
> C:\cygwin, but copying there the necessary config files so that
> setup-x86_64.exe knows which packages to download.

Create the new target directory (or just do a base installation) and
copy over /etc/setup/installed.db from your backup.  Then make sure the
versions in that file are all out-of-date w.r.t. the mirrors:

sed -i.bak -re 's/( .*-)[0-9.]+-[0-9]+\.tar/\10-0.tar/' /etc/setup/installed.db

Then run setup again and (modulo obsolete and removed packages) it will
install all those packages that your old installation was having.  Of
course you will then also have to copy / re-create any customizations
that you did directly in the installation tree (like in fstab.d or sshd
keys from your old installation).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

       reply	other threads:[~2023-06-15 17:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <43976.2997253396$1686824142@news.gmane.org>
2023-06-15 17:21 ` ASSI [this message]
     [not found] <648ae4b3.170a0220.7a40.c67dSMTPIN_ADDED_BROKEN@mx.google.com>
2023-06-15 12:47 ` marco atzeri
2023-06-15 12:58   ` Dan Harkless
2023-06-15 16:10     ` marco atzeri
2023-06-15 14:39   ` gh
2023-06-15 10:15 gh

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=87jzw4bq07.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).