• [OT] Another FYI: Update repositories.

    From Doug Laidlaw@2:250/1 to All on Wed Nov 6 12:27:08 2019
    I found myself unable to download some more recent libraries I needed.
    I kept getting a message that the old ones were still required. This
    had happened before, and I knew that there was a simple answer.

    In my repositories, I had enabled the main "32-bit" release and I had
    marked the "32-bit Updates" only as an update medium. That apparently
    has the effect that MCC will update what is there, but can't substitute
    a new package that is in "Updates." Whatever it does, the solution was
    to check the box in the left-hand column.

    Look at what is enabled by default. For an update repo, both boxes are checked.

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Wed Nov 6 12:58:59 2019
    On Wed, 06 Nov 2019 07:27:08 -0500, Doug Laidlaw <laidlaws@hotkey.net.au> wrote:

    In my repositories, I had enabled the main "32-bit" release and I had
    marked the "32-bit Updates" only as an update medium. That apparently
    has the effect that MCC will update what is there, but can't substitute
    a new package that is in "Updates." Whatever it does, the solution was
    to check the box in the left-hand column.
    Look at what is enabled by default. For an update repo, both boxes are checked.

    The updates checkbox simply sets a flag indicating that the repo will contain updates. The other box controls whether or not the repo is enabled, regardless of the whether it's an update repo or not. If it's not enabled, it is ignored.

    Regards, Dave Hodgins

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

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From TJ@2:250/1 to All on Thu Nov 7 15:05:47 2019
    On 11/6/19 7:58 AM, David W. Hodgins wrote:
    On Wed, 06 Nov 2019 07:27:08 -0500, Doug Laidlaw
    <laidlaws@hotkey.net.au> wrote:

    In my repositories, I had enabled the main "32-bit" release and I had
    marked the "32-bit Updates" only as an update medium.  That apparently
    has the effect that MCC will update what is there, but can't substitute
    a new package that is in "Updates."  Whatever it does, the solution was
    to check the box in the left-hand column.
    Look at what is enabled by default.  For an update repo, both boxes are
    checked.

    The updates checkbox simply sets a flag indicating that the repo will contain
    updates. The other box controls whether or not the repo is enabled, regardless
    of the whether it's an update repo or not. If it's not enabled, it is ignored.

    Regards, Dave Hodgins


    Yes.

    Doug, the main "core" repositories contain the packages as they were
    when Mageia 7 Official was released. Those will not be changed for the
    life of Mageia 7.

    All current updates, including those in the updated Mageia 7.1 release
    that were different from the original release, are in the "updates" repositories.

    That's the way Mageia's repositories have been organized since the
    beginning of the distro.

    TJ

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Fri Nov 8 16:54:15 2019
    On 2019-11-07, TJ <TJ@noneofyour.business> wrote:
    On 11/6/19 7:58 AM, David W. Hodgins wrote:
    On Wed, 06 Nov 2019 07:27:08 -0500, Doug Laidlaw
    <laidlaws@hotkey.net.au> wrote:

    In my repositories, I had enabled the main "32-bit" release and I had
    marked the "32-bit Updates" only as an update medium.  That apparently
    has the effect that MCC will update what is there, but can't substitute
    a new package that is in "Updates."  Whatever it does, the solution was >>> to check the box in the left-hand column.
    Look at what is enabled by default.  For an update repo, both boxes are >>> checked.

    The updates checkbox simply sets a flag indicating that the repo will
    contain
    updates. The other box controls whether or not the repo is enabled,
    regardless
    of the whether it's an update repo or not. If it's not enabled, it is
    ignored.

    Regards, Dave Hodgins


    Yes.

    Doug, the main "core" repositories contain the packages as they were
    when Mageia 7 Official was released. Those will not be changed for the
    life of Mageia 7.

    All current updates, including those in the updated Mageia 7.1 release
    that were different from the original release, are in the "updates" repositories.

    Actually no. Mga7.1 was different from 7.0 not in the packages, but
    rather in installation scripts. If you look at many repositories, 7.1 is
    a link to 7.





    That's the way Mageia's repositories have been organized since the
    beginning of the distro.

    TJ

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From TJ@2:250/1 to All on Sat Nov 9 13:49:58 2019
    On 11/8/19 11:54 AM, William Unruh wrote:
    On 2019-11-07, TJ <TJ@noneofyour.business> wrote:
    On 11/6/19 7:58 AM, David W. Hodgins wrote:
    On Wed, 06 Nov 2019 07:27:08 -0500, Doug Laidlaw
    <laidlaws@hotkey.net.au> wrote:

    In my repositories, I had enabled the main "32-bit" release and I had
    marked the "32-bit Updates" only as an update medium.  That apparently >>>> has the effect that MCC will update what is there, but can't substitute >>>> a new package that is in "Updates."  Whatever it does, the solution was >>>> to check the box in the left-hand column.
    Look at what is enabled by default.  For an update repo, both boxes are >>>> checked.

    The updates checkbox simply sets a flag indicating that the repo will
    contain
    updates. The other box controls whether or not the repo is enabled,
    regardless
    of the whether it's an update repo or not. If it's not enabled, it is
    ignored.

    Regards, Dave Hodgins


    Yes.

    Doug, the main "core" repositories contain the packages as they were
    when Mageia 7 Official was released. Those will not be changed for the
    life of Mageia 7.

    All current updates, including those in the updated Mageia 7.1 release
    that were different from the original release, are in the "updates"
    repositories.

    Actually no. Mga7.1 was different from 7.0 not in the packages, but
    rather in installation scripts. If you look at many repositories, 7.1 is
    a link to 7.


    I respectfully disagree, in part. I suppose I could have worded my reply better, explaining things more fully and being far too wordy, but yours
    is not precisely correct, either.

    There is actually no Official Mageia "7.1." There is only Mageia "7."
    But, while the main purpose of the 7.1 isos was for adding support for
    new hardware, an additional purpose was to make an installation from
    those isos(at the time of release) the same as a fully-updated 7
    installation (at the time of the 7.1 isos). So, many of the packages on
    the isos were packages that had been updated since the release of 7.
    That is what I meant by "updated 7.1 release."

    There are no "7.1" repositories. The contents of the 7 main "core" repositories were not changed by the release of the 7.1 isos. There are
    also no packages in any of the 7 repositories that are labeled "mga7.1."
    In theory, assuming the hardware was supported, if today a user were to install Mageia from an Official "7" iso and then get all pending updates
    from the repositories, he would get the same result as he would if he installed from a "7.1" iso and got all the pending updates from that point.

    I say "in theory" because of the upgrade option. At the moment, upgrades
    are not working well, for several reasons. Some of our testers have been successful, but others have not been. For me, one upgrade test in
    VirtualBox was issue-free, while one on real hardware was a dismal
    failure. The developers are working on it.



    That's the way Mageia's repositories have been organized since the
    beginning of the distro.

    TJ


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