• What is this Mga 7.1 ?

    From William Unruh@2:250/1 to All on Fri Aug 2 11:10:59 2019
    I am completely confused (and that is not what Mageia should be doing)
    There are now two releases, Magea 7 and Mageia 7.1 In the distributions,
    the 7.1 repository is a link to the 7 repository which would imply that
    there are two names which mean the same thing. It used to be that the .1
    was an update of the original coming out many months later. But now we
    have two numbers that apparently mean the same thing. But then in the
    iso, 7 and 7.1 are different (different sums)
    What is going on here? What is a poor user supposed to make of this? re
    there two releases that either are or are not the same thing?

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Fri Aug 2 13:21:34 2019
    On Fri, 2 Aug 2019 10:10:59 -0000 (UTC), William Unruh wrote:
    I am completely confused (and that is not what Mageia should be doing)
    There are now two releases, Magea 7 and Mageia 7.1 In the distributions,
    the 7.1 repository is a link to the 7 repository which would imply that there are two names which mean the same thing. It used to be that the .1
    was an update of the original coming out many months later. But now we
    have two numbers that apparently mean the same thing. But then in the
    iso, 7 and 7.1 are different (different sums)
    What is going on here? What is a poor user supposed to make of this? re
    there two releases that either are or are not the same thing?

    I would suggest your "poor user" would not know about the repository
    link and would pick the higher version for install. Pretty straight
    forward when you think about it.

    As for your link, an up to date 7 has the updates found in 7.1 and would
    be a waste of space to have a 7.0 and 7.1 repository.

    I suggest to you the the iso difference would be about installer fixes
    and would not normally be seen in the users's install packages.

    I would also suggest that there were several package updates since 7.0
    which made sense to include in 7.1 iso to give a user a better install experience on newer hardware.

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Fri Aug 2 14:15:07 2019
    On 2019-08-02, Bit Twister <BitTwister@mouse-potato.com> wrote:
    On Fri, 2 Aug 2019 10:10:59 -0000 (UTC), William Unruh wrote:
    I am completely confused (and that is not what Mageia should be doing)
    There are now two releases, Magea 7 and Mageia 7.1 In the distributions,
    the 7.1 repository is a link to the 7 repository which would imply that
    there are two names which mean the same thing. It used to be that the .1
    was an update of the original coming out many months later. But now we
    have two numbers that apparently mean the same thing. But then in the
    iso, 7 and 7.1 are different (different sums)
    What is going on here? What is a poor user supposed to make of this? re
    there two releases that either are or are not the same thing?

    I would suggest your "poor user" would not know about the repository
    link and would pick the higher version for install. Pretty straight
    forward when you think about it.

    As for your link, an up to date 7 has the updates found in 7.1 and would
    be a waste of space to have a 7.0 and 7.1 repository.

    I suggest to you the the iso difference would be about installer fixes
    and would not normally be seen in the users's install packages.

    I would also suggest that there were several package updates since 7.0
    which made sense to include in 7.1 iso to give a user a better install experience on newer hardware.

    7 came out about 2 weeks ago. Now 7.1? The normal procedure is to
    publish changes in core/updates, so someone who installed 7 would pick
    up those updates (since urpmi updates the system by looking in the
    updates section, not looking for changes in core/release.) Whereas 7.1
    would have the updated packages in core/release. urpmi --updates looks
    only in the updates directories.

    putting out 7.1 about 2 weeks after putting out 7 is just making no
    sense to me. Can you explain what happened?

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bobbie Sellers@2:250/1 to All on Fri Aug 2 15:21:06 2019
    On 8/2/19 6:15 AM, William Unruh wrote:
    On 2019-08-02, Bit Twister <BitTwister@mouse-potato.com> wrote:
    On Fri, 2 Aug 2019 10:10:59 -0000 (UTC), William Unruh wrote:
    I am completely confused (and that is not what Mageia should be doing)
    There are now two releases, Magea 7 and Mageia 7.1 In the distributions, >>> the 7.1 repository is a link to the 7 repository which would imply that >>> there are two names which mean the same thing. It used to be that the .1 >>> was an update of the original coming out many months later. But now we
    have two numbers that apparently mean the same thing. But then in the
    iso, 7 and 7.1 are different (different sums)
    What is going on here? What is a poor user supposed to make of this? re
    there two releases that either are or are not the same thing?

    I would suggest your "poor user" would not know about the repository
    link and would pick the higher version for install. Pretty straight
    forward when you think about it.

    As for your link, an up to date 7 has the updates found in 7.1 and would
    be a waste of space to have a 7.0 and 7.1 repository.

    I suggest to you the the iso difference would be about installer fixes
    and would not normally be seen in the users's install packages.

    I would also suggest that there were several package updates since 7.0
    which made sense to include in 7.1 iso to give a user a better install
    experience on newer hardware.

    7 came out about 2 weeks ago. Now 7.1? The normal procedure is to
    publish changes in core/updates, so someone who installed 7 would pick
    up those updates (since urpmi updates the system by looking in the
    updates section, not looking for changes in core/release.) Whereas 7.1
    would have the updated packages in core/release. urpmi --updates looks
    only in the updates directories.

    putting out 7.1 about 2 weeks after putting out 7 is just making no
    sense to me. Can you explain what happened?

    Go thou William and catch up on Mageia news. They had problems
    with installs to AMD's Ryzen 3000 machines unless done by network.
    they fixed it in 7.1 so I had to download more isos in case some
    one is smart enough to leave Ubuntu behind (in my SF-LUG capacity
    as distribution librarian).

    Keep up your reading,

    --
    bliss dash SF 4 ever at dslextreme dot com

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: dis-organization (2:250/1@fidonet)
  • From James Kerr@2:250/1 to All on Fri Aug 2 16:30:53 2019
    On 02/08/2019 14:15, William Unruh wrote:
    On 2019-08-02, Bit Twister <BitTwister@mouse-potato.com> wrote:
    On Fri, 2 Aug 2019 10:10:59 -0000 (UTC), William Unruh wrote:
    I am completely confused (and that is not what Mageia should be doing)
    There are now two releases, Magea 7 and Mageia 7.1 In the distributions, >>> the 7.1 repository is a link to the 7 repository which would imply that >>> there are two names which mean the same thing. It used to be that the .1 >>> was an update of the original coming out many months later. But now we
    have two numbers that apparently mean the same thing. But then in the
    iso, 7 and 7.1 are different (different sums)
    What is going on here? What is a poor user supposed to make of this? re
    there two releases that either are or are not the same thing?

    I would suggest your "poor user" would not know about the repository
    link and would pick the higher version for install. Pretty straight
    forward when you think about it.

    As for your link, an up to date 7 has the updates found in 7.1 and would
    be a waste of space to have a 7.0 and 7.1 repository.

    I suggest to you the the iso difference would be about installer fixes
    and would not normally be seen in the users's install packages.

    I would also suggest that there were several package updates since 7.0
    which made sense to include in 7.1 iso to give a user a better install
    experience on newer hardware.

    7 came out about 2 weeks ago. Now 7.1? The normal procedure is to
    publish changes in core/updates, so someone who installed 7 would pick
    up those updates (since urpmi updates the system by looking in the
    updates section, not looking for changes in core/release.) Whereas 7.1
    would have the updated packages in core/release. urpmi --updates looks
    only in the updates directories.

    putting out 7.1 about 2 weeks after putting out 7 is just making no
    sense to me. Can you explain what happened?


    See:

    https://blog.mageia.org/en/2019/07/16/mageia-7-1-mageia-7-with-ryzen-3000-hardw are-support/

    Jim


    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Fri Aug 2 18:32:27 2019
    On Fri, 02 Aug 2019 09:15:07 -0400, William Unruh <unruh@invalid.ca> wrote:

    7 came out about 2 weeks ago. Now 7.1? The normal procedure is to
    publish changes in core/updates, so someone who installed 7 would pick
    up those updates (since urpmi updates the system by looking in the
    updates section, not looking for changes in core/release.) Whereas 7.1
    would have the updated packages in core/release. urpmi --updates looks
    only in the updates directories.

    putting out 7.1 about 2 weeks after putting out 7 is just making no
    sense to me. Can you explain what happened?

    A few days after 7 was released, an update for systemd came out that
    was required for the system to be able to boot on the newest amd cpus.

    While systemd was blamed, it was amd that changed things. A workaround
    was added to systemd to handle the change. https://github.com/systemd/systemd/pull/12536/commits/1c53d4a070edbec8ad2d384ba 0014d0eb6bae077

    As the Mageia 7 iso images could not boot on such systems, the decision
    was made to release new iso images with the systemd fix, as well as
    other bug and translation fixes that had been released since the iso
    images for 7 had been created. The names had to be changed to avoid
    people accidentally getting the old iso images, so 7.1 was chosen.

    On installed systems, there is no difference between 7 and 7.1 other
    then the url used to access the same repositories.

    For booting the live or classical iso images, on the newest amd cpu
    systems, 7.1 is required. If you don't have one of those cpus, then
    7 works fine. This is all explained in the blog, release notes, etc. https://blog.mageia.org/en/2019/07/16/mageia-7-1-mageia-7-with-ryzen-3000-hardw are-support/

    Regards, Dave Hodgins

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

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Fri Aug 2 22:15:41 2019
    On Fri, 2 Aug 2019 13:15:07 -0000 (UTC), William Unruh wrote:
    On 2019-08-02, Bit Twister <BitTwister@mouse-potato.com> wrote:

    I would also suggest that there were several package updates since 7.0
    which made sense to include in 7.1 iso to give a user a better install
    experience on newer hardware.



    putting out 7.1 about 2 weeks after putting out 7 is just making no
    sense to me. Can you explain what happened?

    I did explain it. Besides some security fixes, I think there was a
    nvidia driver update which could have prevented problems, ralink,
    rtlwifi, iwlwifi, and kernel firmware, and microcode libraries to
    load firmware. There were about 75 package changes.
    That assumes the Classic DVD iso.


    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Doug Laidlaw@2:250/1 to All on Sat Aug 3 09:41:39 2019
    On 3/8/19 12:21 am, Bobbie Sellers wrote:
        Go thou William and catch up on Mageia news.  They had problems with installs to AMD's Ryzen 3000 machines unless done by network.
    they fixed it in 7.1 so I had to download more isos in case some
    one is smart enough to leave Ubuntu behind (in my SF-LUG capacity
    as distribution librarian).

        Keep up your reading,

    It was on the Community page. It further said that if you don't have a
    recent Ryzen card, you don't need to do anything.

    I always start from the Mageia community page, and go to the downloads
    only if it tells me to. It was my daughter who threw out the
    instructions for a purchase, then asked me what they said - a typical
    woman, who prefers the spoken word. She doesn't even look at a phone
    book, but rings Directory Assistance.

    Doug.

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From TJ@2:250/1 to All on Mon Aug 5 19:18:01 2019
    On 8/3/19 4:41 AM, Doug Laidlaw wrote:
    - a typical woman,

    It's certain that you aren't in MY family. Using those two words
    together around the women in my life will get you hospitalized.

    TJ

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Daniel60@2:250/1 to All on Tue Aug 6 11:14:38 2019
    TJ wrote on 6/08/2019 4:18 AM:
    On 8/3/19 4:41 AM, Doug Laidlaw wrote:
    - a typical woman,

    It's certain that you aren't in MY family. Using those two words
    together around the women in my life will get you hospitalized.

    TJ
    So what, TJ?? Are you surrounded by a-typical women?? Or is that
    anti-typical women??

    --
    Daniel

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From TJ@2:250/1 to All on Thu Aug 8 02:29:58 2019
    On 8/6/19 6:14 AM, Daniel60 wrote:
    TJ wrote on 6/08/2019 4:18 AM:
    On 8/3/19 4:41 AM, Doug Laidlaw wrote:
    - a typical woman,

    It's certain that you aren't in MY family. Using those two words
    together around the women in my life will get you hospitalized.

    TJ
    So what, TJ?? Are you surrounded by a-typical women?? Or is that anti-typical women??

    I am surrounded by women that bristle when stereotyped.

    And I don't blame them a bit. In my experience, there is no such thing
    as a "typical" woman. Or a "typical" man.

    TJ

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Daniel60@2:250/1 to All on Thu Aug 8 13:58:58 2019
    TJ wrote on 8/08/2019 11:29 AM:
    On 8/6/19 6:14 AM, Daniel60 wrote:
    TJ wrote on 6/08/2019 4:18 AM:
    On 8/3/19 4:41 AM, Doug Laidlaw wrote:
    - a typical woman,

    It's certain that you aren't in MY family. Using those two words
    together around the women in my life will get you hospitalized.

    TJ
    So what, TJ?? Are you surrounded by a-typical women?? Or is that
    anti-typical women??

    I am surrounded by women that bristle when stereotyped.

    And I don't blame them a bit. In my experience, there is no such thing
    as a "typical" woman. Or a "typical" man.

    TJ
    Hear!! Hear!! ;-)

    --
    Daniel

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