Please advise how to skip the duplicity update since it fails with my snap version.
Please note that I use a snap version of duplicity since I ran my MIAB on arm64 instance and there is no arm64 latest version of duplicity, thus the update fails:
I deleted it sudo rm -rf /bin/duplicity
I linked it to snap afterwards but update fails sudo ln -s /snap/bin/duplicity /bin/duplicity
Can I edit the setup script and skip the duplicity part?
This is the message:
Installing Mail-in-a-Box system management daemon...
FAILED: apt-get -y -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confnew install duplicity python3-pip virtualenv certbot rsync
-----------------------------------------
Reading package lists...
Building dependency tree...
Reading state information...
Package duplicity is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
@JoshData How can I skip the duplicity version check error as per above to achieve successful upgrade on arm64?
Here is the newest error message:
Nextcloud is already latest version
Installing Z-Push (Exchange/ActiveSync server)...
Installing Mail-in-a-Box system management daemon...
FAILED: apt-get -y -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confnew install duplicity python3-pip virtualenv certbot rsync
-----------------------------------------
Reading package lists...
Building dependency tree...
Reading state information...
Package duplicity is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'duplicity' has no installation candidate
-----------------------------------------
ubuntu@box:~$ Reading package lists...
Please don’t imply that I owe anyone my personal time beyond what I’ve stated that the project is committed to. If it’s such a pity to you, you can put in the effort yourself to figure it out.
Not running arm, but I have an exclude file for the duplicity package. I got an error at the very end of the MiaB update process but I’m now showing as running 71a.
Exclude duplicity like so:
sudo echo -e "# Duplicity is installed via snap\nPackage: duplicity\nPin: release *\nPin-Priority: -1" > /etc/apt/preferences.d/duplicity
Thanks: But I cannot get rid of this. Now I cannot install the old version as well:
ubuntu@box:~$ sudo apt install duplicity
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package duplicity is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'duplicity' has no installation candidate
Mine shows V71. But it looks like V71a is out now. I would try again with the new script. Then follow the steps in the fix if the error happens again.
Good luck!
Well, yes. That’s the idea. Installing duplicity via apt will not work because it’s been prevented from installation by the preferences file. If you would like to re-enable it for installation via apt, just remove the /etc/apt/preferences.d/duplicity file.
OK that did the job. Thanks @mokiejovis
So I removed the duplicity file. Reinstalled apt duplicity >> sudo apt install duplicity I got:
sudo duplicity --version
duplicity 0.8.21
Update 70 >> 71 just ran sudo mailinabox
It completed OK
Then, curl -s https://mailinabox.email/setup.sh | sudo -E bash
Update 71 >> 71a
Completed OK
Then, I did the snap hack from above
Hi there. Thanks for that. I re-ran the upgrade to 71a, then immediately ran the commands above. Manually instigated a backup, no errors were reported, checked backups & confirmed there was a newly created file. So appears to be all good. I appreciate the guidance.