Setup-x86(_64) (v2.889) ... just a question

Setup-x86(_64) (v2.889) ... just a question

[Houder]

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

Re: Setup-x86(_64) (v2.889) ... just a question (CORRECTION)

[Houder]

On 2018-03-06 14:39, Houder wrote:
> 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.
[snip]

I should have added:

... next I decided to install the previous versions of both cscope and
liblz4_1.

> 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

--
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

Re: Setup-x86(_64) (v2.889) ... just a question

[Jon Turney]

On 06/03/2018 13:39, Houder wrote:
[...]> 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?

Not only the future, but the present and past, as well.

Despite appearances, these aren't filenames, but versions encoded in 
peculiar way, for backwards compatibility.  See [1].

[1] https://cygwin.com/ml/cygwin/2018-02/msg00037.html

--
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

Re: Setup-x86(_64) (v2.889) ... just a question

[Houder]

On 2018-03-06 16:38, Jon Turney wrote:
> On 06/03/2018 13:39, Houder wrote:
> [...]> 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?
> 
> Not only the future, but the present and past, as well.
> 
> Despite appearances, these aren't filenames, but versions encoded in
> peculiar way, for backwards compatibility.  See [1].
> 
> [1] https://cygwin.com/ml/cygwin/2018-02/msg00037.html

package_db.cc (package::flush() ):

   /*
      In INSTALLED.DB 3, lines are: 'packagename version flags', where
      version is encoded in a notional filename for backwards
      compatibility, and the only currently defined flag is user-picked
      (bit 0).
    */

Got it. Thank you. Made a note of this for myself.

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

Re: Setup-x86(_64) (v2.889) ... just a question

[Achim Gratz]

Houder writes:
> 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?

The entries in that file have not been referring to actual file names
for at least a decade if not longer.  It's just been kept that way in
order to stay compatible with any known and unknown consumers of that
data.  The only real meaning is the _version_ that setup knows to be
installed (the packagename is the first part of the line and just
repeated for the version part that still looks liek a filename).

For setup itself, the file name to be installed doesn't need to match
anything at all (it wouldn't even need a .tar.xz suffix to fihgure out
the file type), but there's a naming convention that gets followed.
It's mostly so that one can look at the install log and understand what
has been installed or more easily find a file to manually install.


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

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

--
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