Package manager successfully installs all the packages I tell it to with the exception of one I need the most.

I can install the open-ssh package and tell it to reinstall on next boot, but it fails to do so.  This causes the loss of it's use until manually reinstalling and setting up the configurations I use, which are deleted in the same boot.

No matter how many time I ask it to reinstall, it fails.

 

The package and it's related install configurations are indeed installed in the directory for a reinstall.  There is nothing in the Go script excluding the "ssh" package. Its dependent package "ssl" reinstall okay.

 

Can someone point me in the correct direction, please?  This a real nuisance since I am usually in a rush to get the server back running again after a crash of the ESXi server it is running under. That doesn't happen very often but like I said, it will happen at the most inconvenient times.

 

Thanks, in advance.

Victor

Package manager successfully installs all the packages I tell it to with the exception of one I need the most.

I can install the open-ssh package and tell it to reinstall on next boot, but it fails to do so.  This causes the loss of it's use until manually reinstalling and setting up the configurations I use, which are deleted in the same boot.

No matter how many time I ask it to reinstall, it fails.

 

The package and it's related install configurations are indeed installed in the directory for a reinstall.  There is nothing in the Go script excluding the "ssh" package. Its dependent package "ssl" reinstall okay.

 

Can someone point me in the correct direction, please?  This a real nuisance since I am usually in a rush to get the server back running again after a crash of the ESXi server it is running under. That doesn't happen very often but like I said, it will happen at the most inconvenient times.

 

Thanks, in advance.

Victor

The packages are installed in alpha order.  ssh is probably being installed BEFORE its dependent library, and therefore probably failing when you attempt to start it.

 

Add a specific line or two in the config/go script to invoke them in the correct order,

or rename the /boot/packages/?.auto_install files involved to alternate names, so they are installed in the correct order.

Thanks Joe,  I kinda suspected that but had no way to know for sure.  Your suggestion for renaming,etc, should show what's going on.  I did not know you could do that.  Thanks again and will try at the earlist opportunity and get back.

 

Vic

Joe, you hit the nail on the head.  Renaming or forcing by using a script works fine across reboots.

Thanks for the tip.

 

I really think this should be resolved by the package installer tho.

Just my 2 cents.

 

Thanks again.

 

Vic

Joe, you hit the nail on the head.  Renaming or forcing by using a script works fine across reboots.

Thanks for the tip.

 

I really think this should be resolved by the package installer tho.

Just my 2 cents.

 

Thanks again.

 

Vic

Glad you resolved it.

Unfortunately, you will need to live with its limitations or add the code to manage infinate combinations of packages and conflicting dependencies yourself. (Or, as I said, rename the interdependent  *.auto_install files so they work for your specific combination of installed packages.  It is exactly why  packages are loaded in alpha order.

 

It is a small miracle we have a package manager at all.

 

Joe L.