0
1
I am installing a cygwin onto a new machine from local discs made in 2015. I am using an old set of packages because the process for approving new files for is extremely onerous. The package folders are located in
C:\cygwinV2015install\http%3a%2f%2fcygwin.parentingamerica.com%2f\x86_64\release
I initiate the install using:
setup-x86_64.exe --no-admin
The setup executable and the package folders are the only files that I retained from 2015.
The Root Install Directory
is C:\cygwin64
. I chose to install for Just Me
rather than All Users
. The Local Package Directory
is specified as C:\cygwinV2015install\http%3a%2f%2fcygwin.parentingamerica.com%2f
.
In the Select Packages
screen, I select Curr
, which stands for Globally select the version that is currently considered the most stable. (RECOMMENDED)
. The checkbox for Hide obsolete packages
is enabled.
The problem is that I can't select many packages at once using the Category
View
If
View
isCategory
, the only thing showing isNo packages found
, regardless of the filter (Default
,Install
,Reinstall
,Uninstall
)If
View
isFull
, I see a long list of packages, where every entry in the 1st column (entitledNew
) saysSkip
. I can click onSkip
one row at a time, and between the package version andSkip
.If
View
isPending
, I see the packages that have been toggled away fromSkip
in theFull
View
If
View
isUp To Date
, the only thing showing isNothing to Install/Update
If
View
isNot Installed
, I see the same things as whenView
isFull
(which makes sense, since nothing is installed).
I really don't want to operate outside of Category
View
because I'm sure I'll miss something. What am I missing in terms of getting setup to work as it normally does? I want to be able to use Category
View
and see more than No Packages found
.
AFTERNOTE: From experimenting on a different computer, it seems that no matter what path I specify for Local Package Directory
, the packages show up in the Select Packages
list under Category
View
. This means that the setup program is storing the path of the packages somewhere else. Does anyone know where? If I can access that parameter, I might be able to make the setup program behave properly on the new computer.
FIRST ATTEMPTED SOLUTION: Thanks to Matzeri, I followed this page to create a *.bat file that specified all the packages:
setup-x86_64.exe --no-admin --local-package-dir C:\cygwinV2015install -P _autorebase,_autorebase,_update-info-dir,a2ps,...,zip,zlib0
pause
The *.bat file was created on the computer with cygwin
installed, and executed on the computer in which I want to install cygwin. I added the --no-admin
myself because I don't have admin rights. I placed it in C:\cygwinV2015install
, which also contains the mirror folder http%3a%2f%2fcygwin.parentingamerica.com%2f
. When I run the *.bat file, however, it launches the same setup GUI as if I directly ran setup-x86_64.exe
. The Select Packages
panel doesn't seem to recognize any packages. Here is what shows, depending on the View
:
Full
View
:Nothing to Install/Update
Pending
View
:Nothing to Install/Update
Up To Dat
View
:Nothing to Install/Update
Not Installed
:Nothing to Install/Update
Category
View
:No packages Found
For Category
View
, it doesn``t matter whether I filter by Default
, Install
, Reinstall
, or Uninstall
.
In the *.bat file, I also specified --local-package-dir C:\cygwinV2015install\http%%3a%%2f%%2fcygwin.parentingamerica.com%%2f
, with the same result. (The double "%" signs act as a single "%" in a *.bat file).
Note that I removed all *.ini files in the subtree rooted at C:\cygwinV2015install
. The text therein says that they are autogenerated.
Is there anything else that could be causing the packages to go unrecognized?
NEW INFO: If I create a new folder c:\cygwinV2015install5
and put setup executable, the mirror folder, and the *.bat file into it, I can run setup-x86_64.exe --no-admin
and see the (skipped) packages in Full
View
-- as long as --local-package-dir
is specified to be the mirror folder. not c:\cygwinV2015install5
. However, there are far too many packages to manually switch away from Skip
. Since I can only see the packages when I create a virgin folder c:\cygwinV2015install5
, it means that setup
is storing its knowledge of packages elsewhere, and setup
only looks again for packages when a new local package directory. I tried to take advantage of this by using the *.bat file in a new folder c:\cygwinV2015install6
, but alas, no luck. Still get the same results as FIRST ATTEMPTED SOLUTION
above. Note that I added the --local-install
option to the *.bat file, and I also tried --no-verify
; no difference.
MORE NEW INFO: I'm beginning to suspect the following failure mode:
setup
only recognizes packages when the local package directory is browsed to via thesetup
GUI, NOT if it is specified via command line option--local-package-dir
Evidence of this is that the
Select Packages
list is empty regardless of whether I specify the local package directory asc:\cygwinV2015install*
orc:\cygwinV2015install*\http%%3a%%2f%%2fcygwin.parentingamerica.com%%2f
(the asterisk is any integer to ensure that I'm working with a virgin directory)The moment I browse to a local package directory using the GUI, I can see the packages in
Full
View
, but not inCategory
View
However, I suspect that when I do this, I lose all the package specifications specified using the -P option in the *.bat file
Evidence of this is that all the packages show up as
Skip
(strictly speaking, however, I'm not sure if they would have shown up otherwise if they were properly seen bysetup
without browsing via the GUI)There are way too many packages to toggle away from
Skip
manuallyWith the hierarchical organizatio of
Category
View
, there might be some chance of selecting the high level packages and having the dependency assurance function select the low level packages and libraries
If I am right, then the problem can be solved by getting the setup executable to recognized the packages based on the --local-package-dir
argument, without having to browse to a folder in the GUI. Failing that, I would need a way to toggle the Skip
selection for the packages en masse.
The main mystery stumping me is why the packages aren't recognized, and when they are, why they don't show up in Category
View
in the typical hierarchical fashion. Is there some kind of config file needed in one of the folders in order for this functionality to work correctly?
I assume you want to duplicate an existing installation, so you can consider https://stackoverflow.com/questions/46829532/cygwin-save-package-selections-for-later-reinstall
– matzeri – 2017-11-21T16:22:31.547Thanks, matzeri. I added a section
FIRST ATTEMPTED SOLUTION
reflecting the result of using the page that you cited. – user36800 – 2017-11-21T20:01:44.770I used the currently downloadable setup executable to create another snapshot of the currently available install files from http://cygwin.parentingamerica.com. It turns out that file .../http%3a%2f%2fcygwin.parentingamerica.com%2f/x86_64/setup.ini is created in the process. From this page, it seems to be at least one essential file that I need (and which I did not have).
– user36800 – 2017-11-22T04:49:49.023