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.
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
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
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
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 482 |
Nodes: | 16 (2 / 14) |
Uptime: | 39:49:10 |
Calls: | 9,566 |
Files: | 13,656 |
Messages: | 6,141,728 |