1. Forum
  2. FidoNet
  3. ALT.OS.LINUX.MAGEIA

  • Mageia Site seems to be down

    From Doug Laidlaw@2:250/1 to All on Sun Jan 17 18:36:38 2021
    As I write, the Mageia Community link seems not to work. Maybe they are re-writing it for a big announcement?

    --- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Sun Jan 17 19:26:20 2021
    On Sun, 17 Jan 2021 13:36:38 -0500, Doug Laidlaw <[email protected]> wrote:

    As I write, the Mageia Community link seems not to work. Maybe they are re-writing it for a big announcement?

    https://www.mageia.org/en-gb/community/ is working here.

    Regards, Dave Hodgins

    --
    Change [email protected] to [email protected] for
    email replies.

    --- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Sun Jan 17 19:38:17 2021
    On Sun, 17 Jan 2021 13:36:38 -0500, Doug Laidlaw <[email protected]> wrote:

    As I write, the Mageia Community link seems not to work. Maybe they are re-writing it for a big announcement?

    Just adding a bit more info. I've seen no outages in the last couple of hours. The rc iso images are currently in qa testing, and will require as least one more rebuild to include fixes, before being considered for release to the general public. No big announcements in progress, that I'm aware of. :-)

    Regards, Dave Hodgins

    --
    Change [email protected] to [email protected] for
    email replies.

    --- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Daniel65@2:250/1 to All on Mon Jan 18 08:20:08 2021
    David W. Hodgins wrote on 18/01/21 06:38:
    On Sun, 17 Jan 2021 13:36:38 -0500, Doug Laidlaw
    <[email protected]> wrote:

    As I write, the Mageia Community link seems not to work.  Maybe they are
    re-writing it for a big announcement?

    Just adding a bit more info. I've seen no outages in the last couple of hours.
    The rc iso images are currently in qa testing, and will require as least
    one
    more rebuild to include fixes, before being considered for release to the general public. No big announcements in progress, that I'm aware of. :-)

    Regards, Dave Hodgins

    David, on the community page, https://www.mageia.org/en-gb/community/ ,
    I see the 'MGA8 is on its way' (Nov 3, 2020) and '8 in beta2' (Dec 13 2020).

    Any idea when MGA 8 (final) might be out?? (I figure my MGA 6 might be
    just a bit 'old'!!)
    --
    Daniel

    --- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Mon Jan 18 17:04:02 2021
    On Mon, 18 Jan 2021 03:20:08 -0500, Daniel65 <[email protected]> wrote:

    Any idea when MGA 8 (final) might be out?? (I figure my MGA 6 might be
    just a bit 'old'!!)

    As always, the answer is "When it's ready!". :-) The main holding block for the
    rc iso images right now is graphics not working on some very new hardware.

    What happens after the rc iso images are released to the public depends entirely
    on the results of the public testing. If deemed necessary, as second rc may be produced. If everything does go well, then a couple of weeks after the last rc is
    released, Mageia 8 will be released.

    While we do set target dates for ourselves, as per https://wiki.mageia.org/en/Mageia_8_Development
    we do not hold to arbitrary deadlines. The quality is more important than working
    to some fixed date to get something out.

    The rc iso images are working well for most testers, but there are a few where the
    installs are not working. Those issues are being investigated. How long they will
    take to fix or workaround remains to be seen.

    In addition to the rc iso testing of new installs, we are also conducting testing
    of upgrading from Mageia 7 to 8, mostly using mgaapplet.

    Upgrading from Mageia 6 directly to 8 is not supported, and extremely unlikely to
    work. Best to do a new install, including a new /home, and then after booting into the new install, copy data as needed from the old install. It is not recommended to copy config files, as the formats of many of them have changed.

    Regards, Dave Hodgins

    --
    Change [email protected] to [email protected] for
    email replies.

    --- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Mon Jan 18 17:52:54 2021
    On 2021-01-18, David W. Hodgins <[email protected]> wrote:
    On Mon, 18 Jan 2021 03:20:08 -0500, Daniel65
    <[email protected]> wrote:

    .....
    Upgrading from Mageia 6 directly to 8 is not supported, and extremely
    unlikely to
    work. Best to do a new install, including a new /home, and then after
    booting
    into the new install, copy data as needed from the old install. It is not recommended to copy config files, as the formats of many of them have
    changed.

    I assume that upgrading from 6 to 7, updating 7 and then going from 7 to
    8 is supported. Note sure what happens to the config file during that
    double transition. The problem with "copy data as needed" is that there
    could well be data that one does not realise that there is a problem
    with until a year after one did the transition. And saving a complete
    install from 6 for a year is expensive.

    --- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bobbie Sellers@2:250/1 to All on Mon Jan 18 18:01:51 2021
    On 1/18/21 9:52 AM, William Unruh wrote:
    On 2021-01-18, David W. Hodgins <[email protected]> wrote:
    On Mon, 18 Jan 2021 03:20:08 -0500, Daniel65 <[email protected]> wrote:

    ....
    Upgrading from Mageia 6 directly to 8 is not supported, and extremely unlikely to
    work. Best to do a new install, including a new /home, and then after booting
    into the new install, copy data as needed from the old install. It is not
    recommended to copy config files, as the formats of many of them have changed.

    I assume that upgrading from 6 to 7, updating 7 and then going from 7 to
    8 is supported. Note sure what happens to the config file during that
    double transition. The problem with "copy data as needed" is that there
    could well be data that one does not realise that there is a problem
    with until a year after one did the transition. And saving a complete
    install from 6 for a year is expensive.


    Well I have stuff here a lot older than a year from when I too
    was using Mageia but you can escape by moving to a Rolling Release
    such as PCLinuxOS 64. Even if something weird happens you can install
    without creating a new home. But if you do regular backups then you
    would already have the system as it was before the weird happened.
    Oh but you would have to do without the Poettering masterwork ie systemd.

    bliss -“Nearly any fool can use a computer. Many do.” After all here I am...

    --
    bliss dash SF 4 ever at dslextreme dot com

    --- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
    * Origin: dis-organization (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Mon Jan 18 18:20:05 2021
    On Mon, 18 Jan 2021 12:52:54 -0500, William Unruh <[email protected]> wrote:
    I assume that upgrading from 6 to 7, updating 7 and then going from 7 to
    8 is supported. Note sure what happens to the config file during that
    double transition. The problem with "copy data as needed" is that there
    could well be data that one does not realise that there is a problem
    with until a year after one did the transition. And saving a complete
    install from 6 for a year is expensive.

    Yes. My current primary install started as a Mageia 3 install, upgraded each release and currently running Mageia 7. I'll be upgrading it to Mageia 8 soon.

    You can keep /home, but don't be surprised by how many applications do not handle
    old config file formats well. It makes debugging problems much harder.

    If you do keep /home, I recommend that after the upgrade create a new user, and
    use that user to figure out which problems are due to a bug in the new software,
    and which are due to settings in /home. Mageia updates do not touch files in /home.
    Updates and upgrades requiring changes in /home are the user's responsibility.

    When we know about needed changes, the updates include README.urpmi files that are displayed when the update is installed that explain changes or deletions the user should make.

    It's much easier to use a new /home and copy data as needed from the old /home,
    then to go through the upgrade log(s) to ensure all necessary changes have been
    made, hence the recommendation not to reuse /home.

    Also, it's recommended to uninstall any third party software, and reinstall it after the upgrade, so it doesn't stop an upgrade half way through.

    Regards, Dave Hodgins

    --
    Change [email protected] to [email protected] for
    email replies.

    --- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)