On Tue, 29 Aug 2023 13:42:26 -0400, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:

> On Tue, 29 Aug 2023 05:52:09 -0400, marc <marc@noneofyour.business> wrote:
>> @DavidHodgins: I wonder what makes the mirror-kernel-org down for such a
>> long time? Isn't that the most important channel for all distros to
>> update? Seems not very professional to me...
>
> We don't control the mirrors. I suspect that whoever normally monitors the
> syncing and the email used to report problems was not available.
>
> http://mirrors.kernel.org/mageia/distrib/9/x86_64/media/core/release/media_info/
> shows it started syncing again. As it includes syncing all of the new cauldron,
> it will take several hours to finish. Then we have to wait at least a day for
> the mirrors that sync from it to sync too.
>
> https://mirrors.mageia.org/status gets updated every ten minutes iirc.

kernel.org is fully synced now. Thomas reported that it was a networking issue
at kernel.org that caused them to switch to a backup system, but they neglected
to notify mageia, and that backup system was not authorized to access the
primary mirror.

So it was a communication issue. They thought the problem was on our end, we
thought it was on their end, as the cause not being communicated clearly.

It will likely take a day for the other 9 mirrors that sync from kernel.org
to fully sync.

Regards, Dave Hodgins

On 8/29/23 22:59, David W. Hodgins wrote:
> On Tue, 29 Aug 2023 13:42:26 -0400, David W. Hodgins
> <dwhodgins@nomail.afraid.org> wrote:
>
>> On Tue, 29 Aug 2023 05:52:09 -0400, marc <marc@noneofyour.business>
>> wrote:
>>> @DavidHodgins: I wonder what makes the mirror-kernel-org down for such a
>>> long time? Isn't that the most important channel for all distros to
>>> update? Seems not very professional to me...
>>
>> We don't control the mirrors. I suspect that whoever normally monitors
>> the
>> syncing and the email used to report problems was not available.
>>
>> http://mirrors.kernel.org/mageia/distrib/9/x86_64/media/core/release/media_info/
>> shows it started syncing again. As it includes syncing all of the new
>> cauldron,
>> it will take several hours to finish. Then we have to wait at least a
>> day for
>> the mirrors that sync from it to sync too.
>>
>> https://mirrors.mageia.org/status gets updated every ten minutes iirc.
>
> kernel.org is fully synced now. Thomas reported that it was a networking
> issue
> at kernel.org that caused them to switch to a backup system, but they
> neglected
> to notify mageia, and that backup system was not authorized to access the
> primary mirror.
>
> So it was a communication issue. They thought the problem was on our
> end, we
> thought it was on their end, as the cause not being communicated clearly.
>
> It will likely take a day for the other 9 mirrors that sync from kernel.org
> to fully sync.
>
> Regards, Dave Hodgins

Thanks for the explanation, Dave. I'll be patient.

Wouldn't it be an idea to mention this status info on the blog.mageia.org?

BTW What strikes me, is that even MGA8 today is not fully synced on any
of the mirors. Most show that the software is 12 hours old.

Marc.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Markus Robert Kessler escreveu:
> Hello everyone!
>
> I run several machines with MGA7. I didn't want to switch to MGA8,
> because the makers of Mageia were working on MGA9 to release for
> more than two years now, and I waited for MGA9 to directly replace
> MGA7. That was my favourite.
>
> But, as it looks like, MGA9 is still under development. They say,
> that there are still lots of packages that persistently refuse to
> compile.
>
> Does someone have experience with MGA9 Cauldron yet?
>
> Can this be deployed for normal office applications, VPN, video
> conferencing, some multimedia like cutting videos, playing SW
> synthesizers and such tasks, without the risk that everything turns
> to dust after the next "update testing"?
>
> What, if MGA9 Cauldron will be made to MGA9 stable one day? Can
> everything be kept, and only the package repo definitions have to
> be updated?
>
> Lots of questions, I know :-)
>
> But, I need these machines for doing my job and some MGA7 packages
> are too outdated to be still used. There is also limited
> feasibility to selectively backport newer packages, because the
> dependencies go through the roof.
>
> Thanks for any idea!
>
My approach to this would be to install Mageia 9 on another partition
and use multiboot. If something goes terribly wrong, just start Mageia
7 again.

- --

Abraços

Gilberto F da Silva

Mageia release 9 (Official) for x86_64
Kernel: 6.4.9-desktop-2.mga9
Desktop: KDE

-----BEGIN PGP SIGNATURE-----
Comment: +-----------------------------------------------------+
Comment: ! https://t.me/Gilberto_F_da_Silva !
Comment: +-----------------------------------------------------+

iF0EARECAB0WIQR6BybJIKBLy3+8xXcnG6Ba0yEbDgUCZO+UBgAKCRAnG6Ba0yEb
Dr0YAJ9SYtT3iE8UCRvwYTRd2bOWPQEqtwCfeDr2hQsnJ/EpWPAfjZ9gbru/I5c=
=NJ/Q
-----END PGP SIGNATURE-----

On Wed, 30 Aug 2023 05:32:07 -0400, marc <marc@noneofyour.business> wrote:

> On 8/29/23 22:59, David W. Hodgins wrote:
>> On Tue, 29 Aug 2023 13:42:26 -0400, David W. Hodgins
>> <dwhodgins@nomail.afraid.org> wrote:
>>
>>> On Tue, 29 Aug 2023 05:52:09 -0400, marc <marc@noneofyour.business>
>>> wrote:
>>>> @DavidHodgins: I wonder what makes the mirror-kernel-org down for such a
>>>> long time? Isn't that the most important channel for all distros to
>>>> update? Seems not very professional to me...
>>>
>>> We don't control the mirrors. I suspect that whoever normally monitors
>>> the
>>> syncing and the email used to report problems was not available.
>>>
>>> http://mirrors.kernel.org/mageia/distrib/9/x86_64/media/core/release/media_info/
>>> shows it started syncing again. As it includes syncing all of the new
>>> cauldron,
>>> it will take several hours to finish. Then we have to wait at least a
>>> day for
>>> the mirrors that sync from it to sync too.
>>>
>>> https://mirrors.mageia.org/status gets updated every ten minutes iirc.
>>
>> kernel.org is fully synced now. Thomas reported that it was a networking
>> issue
>> at kernel.org that caused them to switch to a backup system, but they
>> neglected
>> to notify mageia, and that backup system was not authorized to access the
>> primary mirror.
>>
>> So it was a communication issue. They thought the problem was on our
>> end, we
>> thought it was on their end, as the cause not being communicated clearly.
>>
>> It will likely take a day for the other 9 mirrors that sync from kernel.org
>> to fully sync.
>>
>> Regards, Dave Hodgins
>
> Thanks for the explanation, Dave. I'll be patient.
>
> Wouldn't it be an idea to mention this status info on the blog.mageia.org?
>
> BTW What strikes me, is that even MGA8 today is not fully synced on any
> of the mirors. Most show that the software is 12 hours old.

The issue at kernel.org was resolved yesterday. While the status page currently
shows red, the dates indicate it's ok. It's red as updates are being worked on
after a week or so of updates being on hold during the final iso testing. Most of
the 9 mirrors that sync from kernel.org are in the same state.

The blog will be updated soon. Same with things like the download links,
various web pages, etc.

Regards, Dave Hodgins

On Wed, 30 Aug 2023 05:32:07 -0400, marc <marc@noneofyour.business> wrote:
> BTW What strikes me, is that even MGA8 today is not fully synced on any
> of the mirors. Most show that the software is 12 hours old.

That's partly due to the way the status is determined.

When there's no updates for more than the period shown, and then there is
an update, all mirrors will be shown as being behind for that period.

So if it's been 12 hours since an update was created in one of the updates
testing repos for the stable releases, or in the release repos for cauldron,
and then one is created, all mirrors are at least 12 hours out-of-date until
they sync again. Tier 1 mirrors sync at least once per hour. Other mirrors
usually sync less often.

Regards, Dave Hodgins

On Wed, 30 Aug 2023 15:09:58 -0400, Gilberto F da Silva <gfs1989@gmx.net> wrote:
> My approach to this would be to install Mageia 9 on another partition
> and use multiboot. If something goes terribly wrong, just start Mageia
> 7 again.

I still use opera from Mageia 4 for email, usenet, rss, etc. After I installed
Mageia 5, I temporarily added the Mageia 4 repos, installed opera, and then
removed the mga4 repos (keeping a copy of the rpm packages). When I upgrade to
the next release, I uninstall those mga4 packages to ensure they don't cause
problems, do the upgrade, and then re-install them. This install has been
upgraded each release starting with mga3. The prior releases were on another
system that failed after a lightning strike, before I bought a ups and this
system.

Regards, Dave Hodgins

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David W. Hodgins escreveu:
> On Wed, 30 Aug 2023 15:09:58 -0400, Gilberto F da Silva
> <gfs1989@gmx.net> wrote:
>> My approach to this would be to install Mageia 9 on another
>> partition and use multiboot. If something goes terribly wrong,
>> just start Mageia 7 again.
>
> I still use opera from Mageia 4 for email, usenet, rss, etc. After
> I installed Mageia 5, I temporarily added the Mageia 4 repos,
> installed opera, and then removed the mga4 repos (keeping a copy of
> the rpm packages). When I upgrade to the next release, I uninstall
> those mga4 packages to ensure they don't cause problems, do the
> upgrade, and then re-install them. This install has been upgraded
> each release starting with mga3. The prior releases were on
> another system that failed after a lightning strike, before I
> bought a ups and this system.

Just like you, I get upset when an app I like is discontinued. I
really liked superkaramba but it got to the point where it only worked
on openSUSE. It no longer worked in Slackware or Mageia. I redid the
themes used by me for conky and abandoned superkaramba for good.
Struggling to run an old program when there are other current options
working doesn't seem like a good way to spend time. There is Opera on
the flathub. https://flathub.org/pt-BR/apps/search?q=opera

- --

Abraços

Gilberto F da Silva

Mageia release 9 (Official) for x86_64
Kernel: 6.4.9-desktop-2.mga9
Desktop: KDE

-----BEGIN PGP SIGNATURE-----
Comment: +-----------------------------------------------------+
Comment: ! https://t.me/Gilberto_F_da_Silva !
Comment: +-----------------------------------------------------+

iF0EARECAB0WIQR6BybJIKBLy3+8xXcnG6Ba0yEbDgUCZPB1YwAKCRAnG6Ba0yEb
DktmAJ9Hc+njABhaXU988TM7HSQ3d3qPzACfSxkZ4O4BrQ0x4niCMGh8PdkLjcE=
=vEIn
-----END PGP SIGNATURE-----

On Thu, 31 Aug 2023 07:11:31 -0400, Gilberto F da Silva <gfs1989@gmx.net> wrote:
> Just like you, I get upset when an app I like is discontinued. I
> really liked superkaramba but it got to the point where it only worked
> on openSUSE. It no longer worked in Slackware or Mageia. I redid the
> themes used by me for conky and abandoned superkaramba for good.
> Struggling to run an old program when there are other current options
> working doesn't seem like a good way to spend time. There is Opera on
> the flathub. https://flathub.org/pt-BR/apps/search?q=opera

So far, it just works. No struggle involved. Handles simple web pages, email
using pop3/pop3s/imap/imaps, usenet, and rss feeds. It has other features too
such as irc support, but other then testing it at one point, haven't use that
much. For web pages that don't work in it (most things other then Mageia sites),
it was easy to customize to add opening links in firefox or chromium.

I have 308,000 email and usenet messages stored in it that I've chosen to keep
for one reason or another, and around 18,500 messages that I've sent. Having
this archive makes it much easier to keep track of how and/or why things were
done or fixed.

Opera stopped producing this program with opera 4.16. What they distribute now
is just a web browser that is a customized version of chromium. No support for
things like email or usenet.

Eventually I'll have to switch to a different program, but until it starts
requiring a lot of effort to keep, it fits with the way I do things with the
qa team.

Regards, Dave Hodgins

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David W. Hodgins escreveu:
> On Thu, 31 Aug 2023 07:11:31 -0400, Gilberto F da Silva
> <gfs1989@gmx.net> wrote:
>> Just like you, I get upset when an app I like is discontinued. I
>> really liked superkaramba but it got to the point where it only
>> worked on openSUSE. It no longer worked in Slackware or Mageia. I
>> redid the themes used by me for conky and abandoned superkaramba
>> for good. Struggling to run an old program when there are other
>> current options working doesn't seem like a good way to spend
>> time. There is Opera on the flathub.
>> https://flathub.org/pt-BR/apps/search?q=opera

> Eventually I'll have to switch to a different program, but until it
> starts requiring a lot of effort to keep, it fits with the way I do
> things with the qa team.

Since 2,453,398 (someday at the beginning of 2.005) I keep a personal
diary. I chose to use flat text instead of using a text processor like
Word or some equivalent. Even so I had to change several times the way
I performed it. At first I used some version of Windows and PGP 6.X

Over time, it was difficult to get the new PGP versions, the method it
used to encrypt using the clipboard began to have difficulties with
BOM used by the OpenOffice, which add some characters at the beginning
of the text.

At some point I had to rewrite the routine of the OpenOffice BASIC
headers in some other language when I decided to use Emacs. I also
adopted UTF8 instead of the code pages. I had to convert the old files
to UTF8.

I wrote the texts and then used KGPG to encrypt them. Now I use EMACS
internal functions to do this.

They have often occurred that I have to change the way you do tasks.

- --

Abraços
Gilberto F da Silva
Mageia release 9 (Official) for x86_64
Kernel: 6.4.9-desktop-2.mga9
Desktop: KDE
-----BEGIN PGP SIGNATURE-----
Comment: +-----------------------------------------------------+
Comment: ! https://t.me/Gilberto_F_da_Silva !
Comment: +-----------------------------------------------------+

iF0EARECAB0WIQR6BybJIKBLy3+8xXcnG6Ba0yEbDgUCZPHV2AAKCRAnG6Ba0yEb
DkxmAJ9UnIgup7toQozDwWPfydmzGrA1YQCgiAsvRzf17HCNkLwcYcTKxp6Y7MI=
=o9bY
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David W. Hodgins escreveu:
> On Thu, 31 Aug 2023 07:11:31 -0400, Gilberto F da Silva
> <gfs1989@gmx.net> wrote:
>> Just like you, I get upset when an app I like is discontinued. I
>> really liked superkaramba but it got to the point where it only
>> worked on openSUSE. It no longer worked in Slackware or Mageia. I
>> redid the themes used by me for conky and abandoned superkaramba
>> for good. Struggling to run an old program when there are other
>> current options working doesn't seem like a good way to spend
>> time. There is Opera on the flathub.
>> https://flathub.org/pt-BR/apps/search?q=opera
>
> So far, it just works. No struggle involved. Handles simple web
> pages, email using pop3/pop3s/imap/imaps, usenet, and rss feeds. It
> has other features too such as irc support, but other then testing
> it at one point, haven't use that much. For web pages that don't
> work in it (most things other then Mageia sites), it was easy to
> customize to add opening links in firefox or chromium.
>
> I have 308,000 email and usenet messages stored in it that I've
> chosen to keep for one reason or another, and around 18,500
> messages that I've sent. Having this archive makes it much easier
> to keep track of how and/or why things were done or fixed.
>
> Opera stopped producing this program with opera 4.16. What they
> distribute now is just a web browser that is a customized version
> of chromium. No support for things like email or usenet.

Unfortunately it happens a lot of programs that we like to be
discontinued or modified so that we don't like it anymore. In theory,
Open Source would solve it. In fact we cannot modify sources codes.

- --
Abraços
Gilberto F da Silva
Mageia release 9 (Official) for x86_64
Kernel: 6.4.9-desktop-2.mga9
Desktop: KDE
-----BEGIN PGP SIGNATURE-----
Comment: +-----------------------------------------------------+
Comment: ! https://t.me/Gilberto_F_da_Silva !
Comment: +-----------------------------------------------------+

iF0EARECAB0WIQR6BybJIKBLy3+8xXcnG6Ba0yEbDgUCZPHdmwAKCRAnG6Ba0yEb
DvfQAJ4yFExsIkReV/A8L0Lnf38ITqPqKACfSsrtO2TZAUpC20QzGJ8b8zxWIXE=
=fO+O
-----END PGP SIGNATURE-----

On 1/9/23 22:48, Gilberto F da Silva wrote:

>
> Unfortunately it happens a lot of programs that we like to be
> discontinued or modified so that we don't like it anymore. In theory,
> Open Source would solve it. In fact we cannot modify sources codes.
>
>

It's called progress. The authors seem to cast about looking for stuff
to change purely to appear to be doing something.

As some would unkindly suggest

"Re-arranging the deck chairs on the Titanic"

--
Running KDE on x86_64 5.15.126-desktop-1.mga8
Mageia release 8

This morning the mgaapplet finally announced that the upgrade from MGA8
to MGA9 was ready to install. Mirror servers here in Europe were lagging
behind untill two days ago.

In exactly twenty minutes the more than 2500 rpm's were downloaded and
installed.

Reboot went flawlessly. Now up-and-running smoothly.

Thanks to all that helped building this new distro.

It's time for me to donate again to the Mageia foundation. Wish that
more users would do this.

Regards,

Marc.

On Tue, 05 Sep 2023 11:17:33 +0200 marc wrote:

> This morning the mgaapplet finally announced that the upgrade from MGA8
> to MGA9 was ready to install. Mirror servers here in Europe were lagging
> behind untill two days ago.
>
> In exactly twenty minutes the more than 2500 rpm's were downloaded and
> installed.
>
> Reboot went flawlessly. Now up-and-running smoothly.
>
> Thanks to all that helped building this new distro.
>
> It's time for me to donate again to the Mageia foundation. Wish that
> more users would do this.
>
> Regards,
>
> Marc.

Just for the records:

A 'urpmi --auto-update' made my system try to get new packages from
cauldron, which now is MGA10.

To prevent mcc from doing so, I edited /etc/urpmi/urpmi.cfg
by changing every occurrence of 'cauldron' into '9'.

I simply did this in vi: ':%s/cauldron/9/'

Now, a 'urpmi --auto-update', as well as mcc ==> update makes the machine
take new packages from MGA9.

Markus

--
Please reply to group only.
For private email please use http://www.dipl-ing-kessler.de/email.htm

On 2023-10-01, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
> On Tue, 05 Sep 2023 11:17:33 +0200 marc wrote:
>
>> This morning the mgaapplet finally announced that the upgrade from MGA8
>> to MGA9 was ready to install. Mirror servers here in Europe were lagging
>> behind untill two days ago.
>>
>> In exactly twenty minutes the more than 2500 rpm's were downloaded and
>> installed.
>>
>> Reboot went flawlessly. Now up-and-running smoothly.
>>
>> Thanks to all that helped building this new distro.
>>
>> It's time for me to donate again to the Mageia foundation. Wish that
>> more users would do this.
>>
>> Regards,
>>
>> Marc.
>
> Just for the records:
>
> A 'urpmi --auto-update' made my system try to get new packages from
> cauldron, which now is MGA10.
>
> To prevent mcc from doing so, I edited /etc/urpmi/urpmi.cfg
> by changing every occurrence of 'cauldron' into '9'.
>
> I simply did this in vi: ':%s/cauldron/9/'
>
> Now, a 'urpmi --auto-update', as well as mcc ==> update makes the machine
> take new packages from MGA9.
>

Yes, that is a problem. That is presumably why Mageia had a link from9
to cauldron before 9 was released, and probably soon from 10 to
cauldron.

>

On 2023-10-02, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
> On Mon, 02 Oct 2023 11:03:25 -0400, William Unruh <unruh@invalid.ca> wrote:
>
>> On 2023-10-01, Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
>>> On Tue, 05 Sep 2023 11:17:33 +0200 marc wrote:
>>>
>>>> This morning the mgaapplet finally announced that the upgrade from MGA8
>>>> to MGA9 was ready to install. Mirror servers here in Europe were lagging
>>>> behind untill two days ago.
>>>>
>>>> In exactly twenty minutes the more than 2500 rpm's were downloaded and
>>>> installed.
>>>>
>>>> Reboot went flawlessly. Now up-and-running smoothly.
>>>>
>>>> Thanks to all that helped building this new distro.
>>>>
>>>> It's time for me to donate again to the Mageia foundation. Wish that
>>>> more users would do this.
>>>>
>>>> Regards,
>>>>
>>>> Marc.
>>>
>>> Just for the records:
>>>
>>> A 'urpmi --auto-update' made my system try to get new packages from
>>> cauldron, which now is MGA10.
>>>
>>> To prevent mcc from doing so, I edited /etc/urpmi/urpmi.cfg
>>> by changing every occurrence of 'cauldron' into '9'.
>>>
>>> I simply did this in vi: ':%s/cauldron/9/'
>>>
>>> Now, a 'urpmi --auto-update', as well as mcc ==> update makes the machine
>>> take new packages from MGA9.
>>>
>>
>> Yes, that is a problem. That is presumably why Mageia had a link from9
>> to cauldron before 9 was released, and probably soon from 10 to
>> cauldron.
>
> The link doesn't normally get added until after iso testing starts, though
> there is no reason it couldn't be done sooner.

Yes, I discovered that with 10. However, one should not be installing
say 10/cauldron before iso testing has started anyway, and I suspect the
Kessler did not not install 9/cauldron before iso testing started
anyway.

Unless you are an official tester there seems no point in doing so.
Although making the link earlier, probably does not have many downsides,
except perhaps encouraging the naive to install the new version before
it is ready.
>
> Regards, Dave Hodgins