I believe @joshdata said that it would be best to do a clean install for the 18.04 branch once it is stable. However I have not been able to locate that comment.
I believe that #4 in this thread may be the message you are referring to…
LOL, I do not believe you … i have seen how you can spot things in server logs that an eagle would miss.
Wellllllllll Legally Blind in ONE eye technically.
That reply is regarding upgrading from 14.04. My question is in regards to updating from beta to stable.
I would be willing to install beta if the expected update path to stable doesn’t require a reinstallation of the OS.
Guys, guys, if you want to talk about @murgero being legally blind, go do that on another thread (perhaps a new one that is created for that). People come to this thread to talk about the migration from Ubuntu 14.04 to Ubuntu 18.04.
@JoshData would have to give the definitive answer on that … but my expectation would be that the next release would also duplicate as a newer version to upgrade to from the ubuntu_bionic branch… in other words, I would imagine that nothing more than the normal upgrade process would be needed. I would be shocked if this were not the case. We will await confirmation from the project maintainer.
I’m treating the
ubuntu_bionic branch as a release candidate, so the only changes that will happen on that branch from now until the release are fixing major problems that block a release. (Hopefully there won’t be any!)
ubuntu_bionic branch hopefully won’t change much from now until a release, upgrades will just be a
git pull and re-running the Mail-in-a-Box setup
setup/start.sh. So, at this point, I’m comfortable encouraging people to try out that branch and stick with it until a release.
Hello, in a fresh install 18.04 stumbled on
Mail-in-a-Box only supports being installed on Ubuntu 14.04, sorry. You are running: Ubuntu 18.04.1 LTS We can't write scripts that run on every possible setup, sorry.
What I followed was:
git clone https://github.com/mail-in-a-box/mailinabox cd mailinabox sudo setup/start.sh
I don’t know where you got those instructions from, but I have mentioned several times in several different places in these forums that you must run from the ubuntu_bionic branch. I have no idea how to switch branches, but here it is easier if you only download the ubuntu_bionic branch. You forgot the
--single-branch -b ubuntu_bionic.
So here is the instructions you should have followed, @blades :
$ git clone --single-branch -b ubuntu_bionic --depth=1 https://github.com/mail-in-a-box/mailinabox.git $ cd mailinabox # bash setup/start.sh
Ubuntu 18 install issue
Yes I managed to install it now, thank you.
At this link it says so about bionic.
See the setup guide for detailed, user-friendly instructions.
For experts, start with a completely fresh (really, I mean it) Ubuntu 18.04 LTS 64-bit machine. On the machine…
Clone this repository:
$ git clone https://github.com/mail-in-a-box/mailinabox $ cd mailinabox
Thank you, @blades. I have created a pull request to fix the documentation for the ubuntu_bionic branch, since it does not explain that you have to pick the ubuntu_bionic branch. @JoshData, would you mind looking at my Pull Request (Fixes installation Error #1497)?
Would like this project to contriue in the futrue and paying for that is not really an issue for me, I’m no (software) developer but this project is really cool and and would like to support it in the furure!!
Okay, what’s going on with the project? Is there a new version now?
v0.30 was released for Ubuntu 14.04 yesterday. @JoshData has promised to release the new version which will support Ubuntu 18.04 within a couple of days. On that note, I wonder if it will be v0.31 or will be v1.01 reflecting the status as a major change?
I am also hoping that the correct procedure will be posted prominently for those who still need to upgrade their box to v0.30 in preparation for a reinstall and upgrade to Ubuntu 18.04.
Good idea. I will post a strongly worded tweet.
I just made a Pull Request for mailinabox.email, if you would please take a look at it, @JoshData. I think it’s important to notify a user that a big change is around the corner, and documentation might be a little “iffy” while things are being changed.
Excellent idea! But not quite what I was meaning. I will PM you so not to add any additional confusion on the forum.