I have noticed something when upgrading from beta2 to beta4. The install process detected it was beta2 and upgraded but the browser still showed beta2 even after refresh. I did not reboot. I ran the install again and this time the browser showed beta4 but the output of the install was almost like a fresh install except that it didn't overwrite my data.
Is this expected to run the install twice?
Also, I'm trying to see how the upgrade copy process and what is in /etc/airtime relate. For example, when I upgrade, I have to correct liquidsoap.cfg since the icecast password goes back to default. But it seems the upgrade did not affect the liquidsoap in /etc/airtime. That is still correct. But what is being used in /usr/lib is incorrect. Is /etc/airtime still being used or are the liquidsoap_scripts being copied directly to /usr/lib?
Posts: 389Member, Administrator, Sourcefabric Team
Hi Verheek -
We are actually writing the upgrade scripts this week; only a fresh install
works with the betas. The release next tues will include the upgrade
scripts.
> **
> Hi,
>
> I have noticed something when upgrading from beta2 to beta4. The install
> process detected it was beta2 and upgraded but the browser still showed
> beta2 even after refresh. I did not reboot. I ran the install again and this
> time the browser showed beta4 but the output of the install was almost like
> a fresh install except that it didn't overwrite my data.
>
> Is this expected to run the install twice?
>
> Also, I'm trying to see how the upgrade copy process and what is in
> /etc/airtime relate. For example, when I upgrade, I have to correct
> liquidsoap.cfg since the icecast password goes back to default. But it seems
> the upgrade did not affect the liquidsoap in /etc/airtime. That is still
> correct. But what is being used in /usr/lib is incorrect. Is /etc/airtime
> still being used or are the liquidsoap_scripts being copied directly to
> /usr/lib?
>
> Thanks,
> Jeremy
>