From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Setup-x86(_64) (v2.889) ... just a question
Date: Tue, 06 Mar 2018 13:44:00 -0000 [thread overview]
Message-ID: <f07266fe2737c5feae7af41ea5bd68d3@xs4all.nl> (raw)
L.S.,
Just a question, meaning it may have been discussed in cygwin-apps,
but I have been reading that list for quite a while now.
Recently I reported a problem:
https://cygwin.com/ml/cygwin/2018-03/msg00042.html
(Another setup v2.889 regression? additional information)
Jon T. applied a big hammer to solve the problem ... (in short, in
the entry for cscope ,the version number in the "prev" subentry was
replaced as follows:
[prev]
version: 15.8a-2
(i.e. version number 15.8.0.1-2 was replaced by a "version number"
that is NOT part of the filename)
Today David Lee reported a related problem:
https://cygwin.com/ml/cygwin/2018-03/msg00083.html
(Setup problem (2.889 32-bit) )
I replayed what David described and confirmed the issue. Then I
downloaded and installed the most recent version of liblz4_1.
When setup (install mode) is invoked again, it wants to install the
previous version of liblz4_1 (of course!).
... so I applied Jon's big hammer to setup.ini and replaced
131-1 by 1.7.5-0 (version:) in the prev subentry (pkg liblz4_1)
That removed the issue (again, of course!).
However to my surprise /etc/setup/installed.db now lists:
64-@@ grep -e cscope -e lz4 /drv/e/Cygwin64-test/etc/setup/installed.db
cscope cscope-15.8a-2.tar.bz2 1 <==== artifical version number
liblz4_1 liblz4_1-1.7.5-0.tar.bz2 0 <==== ditto
These files do NOT exist. The file names were "artificially crafted".
The files that do exist, are:
64-@@ ls -l release/cscope release/lz4/liblz4_1
release/cscope:
total 700
-rw-r--r-- 1 Henri None 381409 Mar 6 13:18 cscope-15.8.0.1-2.tar.bz2
-rw-r--r-- 1 Henri None 330264 Mar 6 13:16 cscope-15.8b-1.tar.xz
release/lz4/liblz4_1:
total 52
-rw-r--r-- 1 Henri None 30408 Mar 6 12:37 liblz4_1-1.7.5-1.tar.xz
-rw-r--r-- 1 Henri None 17924 Mar 6 11:15 liblz4_1-131-1.tar.xz
Is this the future of setup? Meaning, is it the intention that it may
be possible that installed.db refers to files that do not exist?
Henri
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2018-03-06 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 13:44 Houder [this message]
2018-03-06 14:01 ` Setup-x86(_64) (v2.889) ... just a question (CORRECTION) Houder
2018-03-06 16:27 ` Setup-x86(_64) (v2.889) ... just a question Jon Turney
2018-03-06 17:14 ` Houder
2018-03-06 22:13 ` Achim Gratz
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=f07266fe2737c5feae7af41ea5bd68d3@xs4all.nl \
--to=houder@xs4all.nl \
--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).