I usually do a fresh install every time, but there are no CDs for 8 yet.

I decided to try an upgrade of 7. As often happens, the download was interrupted, and there was a message about newer packages conflicting
with existing ones.

The net-installer took me back to square one, but it didn't start a
fresh installation; it merely continued at the interruption point. I
have never seen that happen with installation media. It failed again at
the last minute, with one of the Xorg packages being named. I didn't
expect the installation to work without X, but the installer continued
to the setting-up screen. On rebooting, almost everything worked as
intended. The missing package for X did not become an update, and is
still not shown as being required. Kodi couldn't be installed from the
repos because of a GTK2 dependency failure, the user config in MCC
remained as before.

Minitube had developed a connection problem. An updated version (3.3)
in Cauldron fixed the problem, but the Qt libraries version in Mga 7.1
wasn't new enough. [ Minitube needs a Google API. The RPMS supply one,
but those building from source have to apply for their own.]

A clean installation, whenever possible, is still the better policy.

--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On 12/23/19 11:26 AM, Doug Laidlaw wrote:

I usually do a fresh install every time, but there are no CDs for 8 yet.

I don't even consider trying Cauldron until there's a DVD to test. Until
the developers believe it's stable enough for those first DVDs, it's not stable enough for me. I just don't have the patience to deal with it at
that stage.

YMMV.

I decided to try an upgrade of 7.  As often happens, the download was interrupted, and there was a message about newer packages conflicting
with existing ones.

The net-installer took me back to square one, but it didn't start a
fresh installation; it merely continued at the interruption point.  I
have never seen that happen with installation media.  It failed again at the last minute, with one of the Xorg packages being  named.  I didn't expect the installation to work without X, but the installer continued
to the setting-up screen.  On rebooting, almost everything worked as intended.  The missing package for X did not become an update, and is
still not shown as being required.  Kodi couldn't be installed from the repos because of a GTK2 dependency failure, the user config in MCC
remained as before.

Minitube had developed a connection problem.  An updated version (3.3)
in Cauldron fixed the problem, but the Qt libraries version in Mga 7.1 wasn't new enough. [ Minitube needs a Google API.  The RPMS supply one,
but those building from source have to apply for their own.]

A clean installation, whenever possible, is still the better policy.

Mageia's Mga7 update of Minitube 3.3 has cleared testing and is on the way.

TJ

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

On Tue, 24 Dec 2019 03:26:57 +1100, Doug Laidlaw wrote:

I usually do a fresh install every time, but there are no CDs for 8 yet.

Except for the network install cds released Dec 14
83M Dec 14 10:58 Mageia-Cauldron-netinstall-nonfree-x86_64.iso
52M Dec 14 10:51 Mageia-Cauldron-netinstall-x86_64.iso

I decided to try an upgrade of 7. As often happens, the download was interrupted,

Yeah, that can be a quite a hassle in cauldron. I always glance at
https://pkgsubmit.mageia.org/ to see if there are a bunch of builds in
progress and how long ago was the last package submitted/uploaded.

At the time of this post there were 5 in progress and
libfilezilla-0.19.3-1.mga7 daviddavid 1 hour ago 7 core/updates_testing uploaded 11 minutes
python-pillow-6.2.1-2.mga8 shlomif 1 hour ago cauldron core/release
uploaded 4 minutes

Which tells I need to wait for my mirror of choice to complete sync which
is normally half past the hour.

and there was a message about newer packages conflicting
with existing ones.

Since I pull all updates down first and with --test I see those, but
the install will remove those.

The net-installer took me back to square one, but it didn't start a
fresh installation; it merely continued at the interruption point. I
have never seen that happen with installation media. It failed again at
the last minute, with one of the Xorg packages being named.

That is odd, because a quick search at https://pkgsubmit.mageia.org/
does not show any xorg package.

I didn't
expect the installation to work without X, but the installer continued
to the setting-up screen. On rebooting, almost everything worked as intended. The missing package for X did not become an update, and is
still not shown as being required. Kodi couldn't be installed from the
repos because of a GTK2 dependency failure, the user config in MCC
remained as before.

Minitube had developed a connection problem. An updated version (3.3)
in Cauldron fixed the problem, but the Qt libraries version in Mga 7.1
wasn't new enough. [ Minitube needs a Google API. The RPMS supply one,
but those building from source have to apply for their own.]

A clean installation, whenever possible, is still the better policy.

I agree, I have done 3 Cauldron net installs, in the last 4 days.
Trying to get all the bugs out of my install scripts.

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

On Mon, 23 Dec 2019 11:26:57 -0500, Doug Laidlaw <laidlaws@hotkey.net.au> wrote:

I usually do a fresh install every time, but there are no CDs for 8 yet.
I decided to try an upgrade of 7. As often happens, the download was interrupted, and there was a message about newer packages conflicting
with existing ones.

This early in the development process for Mageia 8, expect things to be broken,
possibly for days at a time. Cauldron is the packagers playground until package
version freeze.

The net-installer took me back to square one, but it didn't start a
fresh installation; it merely continued at the interruption point. I
have never seen that happen with installation media. It failed again at

With the net-install, when it was restarted, newly built packages were available
so the upgrade was able to continue. With the classical install iso images the new
packages are only available if you also enable the online repositories. Without
those, if a problem is found that aborts the upgrade, it cannot bypass the problem.

A clean installation, whenever possible, is still the better policy.

It's far too early to bother starting upgrade testing. The packagers haven't yet
started making proposals to the council on what changes should be considered for inclusion, let alone decisions made. The schedule hasn't been proposed
yet either.

Before iso images are released, there is extensive upgrade testing. The best time to upgrade is shortly after iso release. Later, other updates that were not included in the upgrade testing may be present that cause new conflicts. Those get fixed if reported, but only if reported.

In my opinion, at this point cauldron should only be used by packagers, who need
it to ensure their own updates work.

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

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

On Mon, 23 Dec 2019 13:10:47 -0500, TJ wrote:

On 12/23/19 11:26 AM, Doug Laidlaw wrote:

I usually do a fresh install every time, but there are no CDs for 8 yet.

I don't even consider trying Cauldron until there's a DVD to test. Until
the developers believe it's stable enough for those first DVDs, it's not stable enough for me. I just don't have the patience to deal with it at
that stage.

YMMV.

I can agree to some extent. I watch https://pkgsubmit.mageia.org/ to
see when it gets down to a "low" number of changes per 3 hours or more
then do a clean install and check for failure messages in the journal,
just to see if there are any new bugs to be created. Reported mysqld did
not come up, bug fixed a day or so later.

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