Auto Upgrade i-MSCP 1.5.3 to Debian 10 Buster

  • Hello Everybody,


    One of my systems running on Debian 9 was setup for automatic updates and in sources list "stable" was defined instead of stretch, so when Debian 10 was launched it started to update the packages. Fortunately I managed to stop the upgrade mid-way and apparently only non-critical packages were upgraded in the process, although /etc/issue says Debian GNU/Linux 10 \n \l the system has quite a lot of packages that need to be upgraded.


    These are the packages that still need to be upgraded :


    My questions are :


    1. Is it safe to perform a full-upgrade to Debian 10 without breaking i-MSCP ?

    2. If not, any suggestions on what to do next besides a full reinstall of Debian 9 ?

    3. Should I leave the system in this state until support is added to i-MSCP for Debian 10 ?

    4. Any idea when support for Debian 10 will be included in i-MSCP ? - last question is for Nuxwin


    Thanks!

  • 1. I would check if the packages which are used for i-MSCP are still compatible with it and check if any i-MSCP related parts are changed. But I wouldnt recommend it (to fully upgrade).

    2. If it works like it is not, let it this way. If something doesnt work, try "apt-get install -f".

    3. I would check for errors and abnormal behaviors. If somethings off and you cant fix it the easy way then you should search how to downgrade (which is possible with a bit of work).

    4. My guess is that he waits a bit till everything is a bit smoothed out.



    Edit:

    I am still wondering why did you use dist-upgrade? Simply update and upgrade should be fine enough. :-/

    . :)

    Edited once, last by Iceman ().

  • I am still wondering why did you use dist-upgrade? Simply update and upgrade should be fine enough. :-/


    I think I got used this way :)


    Anyway, thanks for your reply, I think I'll just leave it like this for a while, if something breaks I'll just re-install it, I wanted to switch tu Ubuntu 18 for some time now, this might be the perfect excuse :)

  • You problem is the source.list

    In your list you will find this

    Code
    1. deb http://deb.debian.org/debian/ stable main contrib non-free
    2. deb-src http://deb.debian.org/debian/ stable main contrib non-free

    Now "Debian 10" is stable and your "Debian 9" got the packages to upgrade.

    If you don't want to upgrade change the lines

    Code
    1. deb http://deb.debian.org/debian/ oldstable main contrib non-free
    2. deb-src http://deb.debian.org/debian/ oldstable main contrib non-free


    The same problem is under Debian 8

    Code
    1. deb http://deb.debian.org/debian/ oldoldstable main contrib non-free
    2. deb-src http://deb.debian.org/debian/ oldoldstable main contrib non-free

    The word "oldstable" is now "oldoldstable"

  • Back with an update :)


    I couldn't help myself and I finished the full upgrade to Debian 10. I thought well, if it's gonna break I'm just gonna reinstall it, maybe even switch to Ubuntu 18.04. So I've made all the backups and finished the upgrade and rebooted the server. Fortunately, besides a small bind problem which wouldn't start with "localhost" in the masters section of named.conf.local, which I had to switch to 127.0.0.1 in order to make bind start again, everything else seems to work fine, the panel is running, websites are ok, and the mail system is good. I'm now running i-MSCP 1.5.3-2018 on Debian 10 without any problems (at least not discovered yet)


    Just in case someone else accidentally starts an upgrade :)


    Cheers