From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: duplicate between packages (libuninameslist)
Date: Sun, 02 May 2021 07:49:41 +0200 [thread overview]
Message-ID: <87mttd8z2i.fsf@Rainer.invalid> (raw)
In-Reply-To: <20210502104704.FED5.50F79699@gmail.com> (Lemures Lemniscati via Cygwin-apps's message of "Sun, 02 May 2021 10:47:06 +0900")
Lemures Lemniscati via Cygwin-apps writes:
> When I updated libuninameslist packages, I've moved the files from
> libuninameslist[01] into libuninameslist-devel.
>
> So, duplication will last until libuninamelist0 is removed.
That is one of the things setup can't handle very well, but you can use
cygcheck to see if the duplicate got removed during installation. In
this particular case I'd think there is not much of a problem.
> To reduce the duplication, I should make libuninameslist0-20091231-2
> in some way (e.g. removing duplicated files, or renaming them).
The problem is not that there is duplication among different versions of
the poackage (which is unavoidable when you move files between
packages), but that the order of removal and installation is not
deterministic.
> I wonder what is a good way...
You might think that re-releasing would fix things, but then you'd need
to ensure that eveybody had updated to before the re-release already.
That generally doesn't work. We could eventually use package
transactions (libsolv supports that) to really ensure things work
correctly, but we're missing lots of bits to make that happen.
So I have this at the moment for instance:
Missing file: /usr/lib/debug/usr/bin/ncdump.exe.dbg from package netcdf-debuginfo
Missing file: /usr/lib/debug/usr/bin/ncgen.exe.dbg from package netcdf-debuginfo
netcdf-debuginfo 4.8.0-2 Incomplete
which is the problem that originally prompted Marco to look for
duplicates I guess. But I'm updating my instzallation quite often, so
it's unlikely I miss an intermediate version.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2021-05-02 5:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 3:45 duplicate between packages Marco Atzeri
2021-05-01 21:48 ` Ken Brown
2021-05-02 1:47 ` duplicate between packages (libuninameslist) Lemures Lemniscati
2021-05-02 4:54 ` Marco Atzeri
2021-05-02 5:49 ` Achim Gratz [this message]
2021-05-04 17:13 ` duplicate between packages Jon Turney
2021-05-20 16:26 ` Ken Brown
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=87mttd8z2i.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@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).