You are not using the OMV package repo
You are not using the OMV package repo
Myself and a couple others had the same problem. Is there another repo other than what is in your OMV 5 install guide?
And speaking of that, you can't add a repo without it being trusted and install a package from it. So, adding the repo to install the keyring package won't work anymore. wget/dpkg is probably a better method unless you want to put trusted in the repo line (I don't). Or even do what I do with omv-extras and write an shell install script.
Myself and a couple others had the same problem. Is there another repo other than what is in your OMV 5 install guide?
And speaking of that, you can't add a repo without it being trusted and install a package from it. So, adding the repo to install the keyring package won't work anymore. wget/dpkg is probably a better method unless you want to put trusted in the repo line (I don't). Or even do what I do with omv-extras and write an shell install script.
I can't confirm that, the vagrant box is using exactly the same script as the guide in the forum.
I can't confirm that, the vagrant box is using exactly the same script as the guide in the forum.
The vagrant Buster image must have extra packages and/or repos then. I'm quite familiar with installing OMV and it doesn't work with a base Buster install 
You can install the archive key and install it.
You can install the archive key and install it.
true
the vagrant box is using exactly the same script as the guide in the forum.
What version of python3-tornado is vagrant installing and from where? I think you should rebuild the salt-common package to use python3-tornado 5.1.
can't confirm that, the vagrant box is using exactly the same script as the guide in the forum.
I looked a little more into this. The vagrant image must be old and Buster has moved on. salt-common/salt-minion don't even compile from source because python3-tornado4 or python3-tornado << 5 don't exist in buster. So, I guess vagrant is the only way to test for now.
The Debian buster image for the vagrant box is used for OMV5 development. This is the fastest way to setup a dev system. So this is the current state for Debian 10 integration.
OMV will never build external packages, so we have to wait for official SaltStack packages.
The Debian buster image for the vagrant box is used for OMV5 development. This is the fastest way to setup a dev system. So this is the current state for Debian 10 integration.
I understand that but you are building on an old version. Maybe you should dist-upgrade that image in your script (I know it would be slower) to test against the current state of Buster? Personally, I don't want to use vagrant when developing/porting plugins. I like having running VMs on my VMware cluster. I know vagrant works with VMware but it is quite expensive.
OMV will never build external packages, so we have to wait for official SaltStack packages.
I just wanted something that works. So, I was trying to compile the Debian Sid source with the assumption that these might someday be in the Buster repo.
@votdev I know I am probably kicking a dead horse but I figured I would update the thread. Tthe vagrant image is from June which must still be using php 7.0. Current Buster is using php 7.3. I was able to build the salt packages and php-pam on up to date buster (here is anyone cares) and modify every reference in the openmediavault package to use php7.3 instead of php7.0 but the postinst script still fails. Frustrating since I finally have a little time to port plugins while on vacation but I can't get a working, updated OMV5 system 
OMV5 development is now on Debian Stretch because Buster has no Salt packages at the moment. I think changing to Buster will happen when it is released and the package repos are stable.
Trying to test TimeMachine via SMB as requested and now struggling. To check for TimeMachine support running on Buster would be a requirement due to shipping with Samba 4.9? But OMV5 installation fails and I don't think testing OMV5 on Stretch would be sufficient unless I get Samba 4.8 or above running there.
Am I missing something?
Hmm, why does the installation fail?
root@omv5:/home/tk# apt-get --yes --auto-remove --show-upgraded --allow-downgrades --allow-change-held-packages --no-install-recommends --option Dpkg::Options::="--force-confdef" --option DPkg::Options::="--force-confold" install postfix openmediavault-keyring openmediavault
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
openmediavault : Depends: php-pam but it is not going to be installed
E: Unable to correct problems, you have held broken packages.And
root@omv5:/home/tk# apt install php-pam
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
php-pam : Depends: phpapi-20151012 but it is not installable
E: Unable to correct problems, you have held broken packages.I am working on that. Need to adapt my pbuilder scripts because it seems there are some package dependency issues in Buster at the moment.
After that I will rebuild php-pam for Debian 10.
I am working on that
Great. Please ping me when done.
Alternatively I can also give OMV5 on Stretch with self-built Samba 4.9 a try if that makes any sense (I've been bitte more than twice with such attempts already so...)
Here is the php-pam package built on Debian 10 for OMV 5 - http://omv-extras.org/testing/usul/
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!