Hi, When I issue the command "sudo dnf upgrade", and it decides it needs to update and refresh all repositories, with the command I've just issued I noticed that it refreshed the google-chrome repository twice. Why is DNF doing that when there is only one repository definition in the .repo file, unlike the standard Fedora .repo files which have 3 repositories defined (not necessarily all active).
regards, Steve
On 26 Nov 2024, at 22:21, Stephen Morris steve.morris.au@gmail.com wrote:
Hi, When I issue the command "sudo dnf upgrade", and it decides it needs to update and refresh all repositories, with the command I've just issued I noticed that it refreshed the google-chrome repository twice. Why is DNF doing that when there is only one repository definition in the .repo file, unlike the standard Fedora .repo files which have 3 repositories defined (not necessarily all active).
Please share the complete dnf output you see when this happens next. Without that it’s hard to say what might be happening. Also include output of `dnf repolist`.
Barry
regards, Steve
<OpenPGP_0x1EBE7C07B0F7242C.asc>
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Wed, 2024-11-27 at 09:20 +1100, Stephen Morris wrote:
When I issue the command "sudo dnf upgrade", and it decides it needs to update and refresh all repositories, with the command I've just issued I noticed that it refreshed the google-chrome repository twice. Why is DNF doing that when there is only one repository definition in the .repo file, unlike the standard Fedora .repo files which have 3 repositories defined (not necessarily all active).
We can't tell without actually seeing what it's doing.
We could only make guesses. Part way through some problem occurred, so it started again? A switch in mirrors?
On 27/11/24 12:59, Tim via users wrote:
On Wed, 2024-11-27 at 09:20 +1100, Stephen Morris wrote:
When I issue the command "sudo dnf upgrade", and it decides it needs to update and refresh all repositories, with the command I've just issued I noticed that it refreshed the google-chrome repository twice. Why is DNF doing that when there is only one repository definition in the .repo file, unlike the standard Fedora .repo files which have 3 repositories defined (not necessarily all active).
We can't tell without actually seeing what it's doing.
We could only make guesses. Part way through some problem occurred, so it started again? A switch in mirrors?
I forced a refresh and below is the info requested. I've also just noticed that the refresh and load is also being done twice for the Fedora 41 repository as well. I've also listed the contents of the google-chrome.repo.
sudo dnf update --refresh [sudo] password for steve: Updating and loading repositories: Fedora 41 - x86_64 100% | 2.5 KiB/s | 4.3 KiB | 00m02s Fedora 41 openh264 (From Cisco) - x86_64 100% | 1.7 KiB/s | 989.0 B | 00m01s RPM Sphere - Basearch 100% | 3.6 KiB/s | 3.0 KiB | 00m01s RPM Fusion for Fedora 41 - Free - Updates 100% | 6.5 KiB/s | 10.7 KiB | 00m02s RPM Fusion for Fedora 41 - Nonfree 100% | 10.0 KiB/s | 16.4 KiB | 00m02s RPM Sphere - Noarch 100% | 4.3 KiB/s | 3.0 KiB | 00m01s Fedora 41 - x86_64 - Updates 100% | 5.2 KiB/s | 4.8 KiB | 00m01s google-chrome 100% | 4.0 KiB/s | 1.3 KiB | 00m00s RPM Fusion for Fedora 41 - Free 100% | 9.9 KiB/s | 12.0 KiB | 00m01s RPM Fusion for Fedora 41 - Nonfree - Updates 100% | 9.6 KiB/s | 14.8 KiB | 00m02s Copr repo for gnome-shell-extensions owned by bedsteler20 100% | 1.0 KiB/s | 1.5 KiB | 00m02s Copr repo for neurofedora-extra owned by @neurofedora 100% | 4.6 KiB/s | 1.5 KiB | 00m00s Copr repo for PyCharm owned by phracek 100% | 5.9 KiB/s | 1.8 KiB | 00m00s Docker CE Stable - x86_64 100% | 9.8 KiB/s | 3.5 KiB | 00m00s Fedora 41 - x86_64 100% | 291.0 KiB/s | 453.9 KiB | 00m02s google-chrome 100% | 3.5 KiB/s | 3.3 KiB | 00m01s Repositories loaded. Nothing to do.
sudo dnf repolist repo id repo name copr:copr.fedorainfracloud.org:bedsteler20:gnome-shell-extensions Copr repo for gnome-shell-extensions owned by bedsteler20 copr:copr.fedorainfracloud.org:group_neurofedora:neurofedora-extra Copr repo for neurofedora-extra owned by @neurofedora copr:copr.fedorainfracloud.org:phracek:PyCharm Copr repo for PyCharm owned by phracek docker-ce-stable Docker CE Stable - x86_64 fedora Fedora 41 - x86_64 fedora-cisco-openh264 Fedora 41 openh264 (From Cisco) - x86_64 google-chrome google-chrome
rpmfusion-free RPM Fusion for Fedora 41 - Free rpmfusion-free-updates RPM Fusion for Fedora 41 - Free - Updates rpmfusion-nonfree RPM Fusion for Fedora 41 - Nonfree rpmfusion-nonfree-updates RPM Fusion for Fedora 41 - Nonfree - Updates rpmsphere RPM Sphere - Basearch rpmsphere-noarch RPM Sphere - Noarch updates Fedora 41 - x86_64 - Updates cat /etc/yum.repos.d/google-chrome.repo [google-chrome] name=google-chrome baseurl=https://dl.google.com/linux/chrome/rpm/stable/x86_64 enabled=1 gpgcheck=1 gpgkey=https://dl.google.com/linux/linux_signing_key.pub
regards, Steve
On Thu, 2024-11-28 at 09:19 +1100, Stephen Morris wrote:
I forced a refresh and below is the info requested. I've also just noticed that the refresh and load is also being done twice for the Fedora 41 repository as well. I've also listed the contents of the google-chrome.repo.
sudo dnf update --refresh [sudo] password for steve: Updating and loading repositories: Fedora 41 - x86_64 100% | 2.5 KiB/s | 4.3 KiB | 00m02s Fedora 41 openh264 (From Cisco) - x86_64 100% | 1.7 KiB/s | 989.0 B | 00m01s RPM Sphere - Basearch 100% | 3.6 KiB/s | 3.0 KiB | 00m01s RPM Fusion for Fedora 41 - Free - Updates 100% | 6.5 KiB/s | 10.7 KiB | 00m02s RPM Fusion for Fedora 41 - Nonfree 100% | 10.0 KiB/s | 16.4 KiB | 00m02s RPM Sphere - Noarch 100% | 4.3 KiB/s | 3.0 KiB | 00m01s Fedora 41 - x86_64 - Updates 100% | 5.2 KiB/s | 4.8 KiB | 00m01s google-chrome 100% | 4.0 KiB/s | 1.3 KiB | 00m00s RPM Fusion for Fedora 41 - Free 100% | 9.9 KiB/s | 12.0 KiB | 00m01s RPM Fusion for Fedora 41 - Nonfree - Updates 100% | 9.6 KiB/s | 14.8 KiB | 00m02s Copr repo for gnome-shell-extensions owned by bedsteler20 100% | 1.0 KiB/s | 1.5 KiB | 00m02s Copr repo for neurofedora-extra owned by @neurofedora 100% | 4.6 KiB/s | 1.5 KiB | 00m00s Copr repo for PyCharm owned by phracek 100% | 5.9 KiB/s | 1.8 KiB | 00m00s Docker CE Stable - x86_64 100% | 9.8 KiB/s | 3.5 KiB | 00m00s Fedora 41 - x86_64 100% | 291.0 KiB/s | 453.9 KiB | 00m02s google-chrome 100% | 3.5 KiB/s | 3.3 KiB | 00m01s Repositories loaded. Nothing to do.
Looking through the above, and just taking a few salient things out of it for reading clarity:
Fedora 41 - x86_64 100% | 2.5 KiB/s | 4.3 KiB | 00m02s Fedora 41 - x86_64 100% | 291.0 KiB/s | 453.9 KiB | 00m02s
google-chrome 100% | 4.0 KiB/s | 1.3 KiB | 00m00s google-chrome 100% | 3.5 KiB/s | 3.3 KiB | 00m01s
I can only see *them* appearing twice. Since I'm not watching your system as it's running, I could make this guess:
On my system parallel loads were allowed. That means two or more things are downloading at the same time. Sometimes the writing to the console of the progress of a download gets interrupted, and *one* thing being downloaded once *appears* twice. The earlier, shorter, progress note hadn't actually finished when the text looked like it had.
Or it could be an interruption, or stall, and a resume of a download.
Either way, I don't see as anything to be concerned about.
If you really wanted to check, you could just update one repo by itself. You'd have to disable all the other repos, though.
Watching my own system I saw an oddity that took a bit of observation to understand: As several things were downloading, the one at the bottom of the list had enormous speed and size that didn't make sense. It was the total speed and downloads, of everything, as things progressed, not that particular item. As soon as that item at the bottom had finished and new item took its place, the list moved up one and I could see the actual much smaller speed and size of that item. I think the outputted info could have been formatted better, with a running total below instead of alongside the last item on the list.
sudo dnf repolist repo id repo name copr:copr.fedorainfracloud.org:bedsteler20:gnome-shell-extensions Copr repo for gnome-shell-extensions owned by bedsteler20 copr:copr.fedorainfracloud.org:group_neurofedora:neurofedora-extra Copr repo for neurofedora-extra owned by @neurofedora copr:copr.fedorainfracloud.org:phracek:PyCharm Copr repo for PyCharm owned by phracek docker-ce-stable Docker CE Stable - x86_64 fedora Fedora 41 - x86_64 fedora-cisco-openh264 Fedora 41 openh264 (From Cisco) - x86_64 google-chrome google-chrome rpmfusion-free RPM Fusion for Fedora 41 - Free rpmfusion-free-updates RPM Fusion for Fedora 41 - Free - Updates rpmfusion-nonfree RPM Fusion for Fedora 41 - Nonfree rpmfusion-nonfree-updates RPM Fusion for Fedora 41 - Nonfree - Updates rpmsphere RPM Sphere - Basearch rpmsphere-noarch RPM Sphere - Noarch updates Fedora 41 - x86_64 - Updates
Looking through the repolists above, I don't see anything listed twice, excepting that google-chrome has the same repo id (left column) as its repo name (right column). Other things have differences between their ID and their NAME.
cat /etc/yum.repos.d/google-chrome.repo [google-chrome] name=google-chrome baseurl=https://dl.google.com/linux/chrome/rpm/stable/x86_64 enabled=1 gpgcheck=1 gpgkey=https://dl.google.com/linux/linux_signing_key.pub
Looks normal enough. You can see its [ID] and name= are the same. Compare that with another repo to see what I mean.
On 28/11/24 15:21, Tim via users wrote:
On Thu, 2024-11-28 at 09:19 +1100, Stephen Morris wrote:
I forced a refresh and below is the info requested. I've also just noticed that the refresh and load is also being done twice for the Fedora 41 repository as well. I've also listed the contents of the google-chrome.repo.
sudo dnf update --refresh [sudo] password for steve: Updating and loading repositories: Fedora 41 - x86_64 100% | 2.5 KiB/s | 4.3 KiB | 00m02s Fedora 41 openh264 (From Cisco) - x86_64 100% | 1.7 KiB/s | 989.0 B | 00m01s RPM Sphere - Basearch 100% | 3.6 KiB/s | 3.0 KiB | 00m01s RPM Fusion for Fedora 41 - Free - Updates 100% | 6.5 KiB/s | 10.7 KiB | 00m02s RPM Fusion for Fedora 41 - Nonfree 100% | 10.0 KiB/s | 16.4 KiB | 00m02s RPM Sphere - Noarch 100% | 4.3 KiB/s | 3.0 KiB | 00m01s Fedora 41 - x86_64 - Updates 100% | 5.2 KiB/s | 4.8 KiB | 00m01s google-chrome 100% | 4.0 KiB/s | 1.3 KiB | 00m00s RPM Fusion for Fedora 41 - Free 100% | 9.9 KiB/s | 12.0 KiB | 00m01s RPM Fusion for Fedora 41 - Nonfree - Updates 100% | 9.6 KiB/s | 14.8 KiB | 00m02s Copr repo for gnome-shell-extensions owned by bedsteler20 100% | 1.0 KiB/s | 1.5 KiB | 00m02s Copr repo for neurofedora-extra owned by @neurofedora 100% | 4.6 KiB/s | 1.5 KiB | 00m00s Copr repo for PyCharm owned by phracek 100% | 5.9 KiB/s | 1.8 KiB | 00m00s Docker CE Stable - x86_64 100% | 9.8 KiB/s | 3.5 KiB | 00m00s Fedora 41 - x86_64 100% | 291.0 KiB/s | 453.9 KiB | 00m02s google-chrome 100% | 3.5 KiB/s | 3.3 KiB | 00m01s Repositories loaded. Nothing to do.
Looking through the above, and just taking a few salient things out of it for reading clarity:
Fedora 41 - x86_64 100% | 2.5 KiB/s | 4.3 KiB | 00m02s Fedora 41 - x86_64 100% | 291.0 KiB/s | 453.9 KiB | 00m02s
google-chrome 100% | 4.0 KiB/s | 1.3 KiB | 00m00s google-chrome 100% | 3.5 KiB/s | 3.3 KiB | 00m01s
I can only see *them* appearing twice. Since I'm not watching your system as it's running, I could make this guess:
On my system parallel loads were allowed. That means two or more things are downloading at the same time. Sometimes the writing to the console of the progress of a download gets interrupted, and *one* thing being downloaded once *appears* twice. The earlier, shorter, progress note hadn't actually finished when the text looked like it had.
Or it could be an interruption, or stall, and a resume of a download.
Either way, I don't see as anything to be concerned about.
If you really wanted to check, you could just update one repo by itself. You'd have to disable all the other repos, though.
Watching my own system I saw an oddity that took a bit of observation to understand: As several things were downloading, the one at the bottom of the list had enormous speed and size that didn't make sense. It was the total speed and downloads, of everything, as things progressed, not that particular item. As soon as that item at the bottom had finished and new item took its place, the list moved up one and I could see the actual much smaller speed and size of that item. I think the outputted info could have been formatted better, with a running total below instead of alongside the last item on the list.
I wasn't so much concerned about it, I was just curious why it was happening, and until I produced that list I hadn't noticed that the Fedora 41 repository was also appearing twice. I have also noticed that the last entry in the downloads was showing the total download speed. I have my system configured for parallel downloads, I have it set to 8 atm, it used to be 3, and what seems to have changed with that is that instead of showing the 3 parallel downloads in a single line cycling through the names of the downloading packages, it now displays a separate progress line for each download. The fact I have the number of parallel downloads set to 8 is obvious when the packages are being downloaded, hence if parallelism is at play here, why consistently those two rather than others as well? With these changes I have noticed another anomaly that may have always been there but not noticed until now, with the last column that displays the time for the download, the last line displayed shows the time as a negative value counting up towards 0. I have seen it get -00m00s before the download finishes and then display the actual length of time when the download finishes. The other observation I have made with this, is the length of time it takes to download all the packages is significantly less than the time it takes to install all the packages, which is also potentially not surprising.
sudo dnf repolist repo id repo name copr:copr.fedorainfracloud.org:bedsteler20:gnome-shell-extensions Copr repo for gnome-shell-extensions owned by bedsteler20 copr:copr.fedorainfracloud.org:group_neurofedora:neurofedora-extra Copr repo for neurofedora-extra owned by @neurofedora copr:copr.fedorainfracloud.org:phracek:PyCharm Copr repo for PyCharm owned by phracek docker-ce-stable Docker CE Stable - x86_64 fedora Fedora 41 - x86_64 fedora-cisco-openh264 Fedora 41 openh264 (From Cisco) - x86_64 google-chrome google-chrome rpmfusion-free RPM Fusion for Fedora 41 - Free rpmfusion-free-updates RPM Fusion for Fedora 41 - Free - Updates rpmfusion-nonfree RPM Fusion for Fedora 41 - Nonfree rpmfusion-nonfree-updates RPM Fusion for Fedora 41 - Nonfree - Updates rpmsphere RPM Sphere - Basearch rpmsphere-noarch RPM Sphere - Noarch updates Fedora 41 - x86_64 - Updates
Looking through the repolists above, I don't see anything listed twice, excepting that google-chrome has the same repo id (left column) as its repo name (right column). Other things have differences between their ID and their NAME.
I was checking for those two entries being listed twice as well and not seeing it, hence eliminating a possible issue of two different repo having duplicate entries, and I was also expecting the repo id and repo display name to be different, which also wasn't a concern.
cat /etc/yum.repos.d/google-chrome.repo [google-chrome] name=google-chrome baseurl=https://dl.google.com/linux/chrome/rpm/stable/x86_64 enabled=1 gpgcheck=1 gpgkey=https://dl.google.com/linux/linux_signing_key.pub
Looks normal enough. You can see its [ID] and name= are the same. Compare that with another repo to see what I mean.
Yep, I looked at that as well, and I've seen those being different in other repos when I've been in the situation of having to type in the repo contents from scratch.
regards, Steve
On Fri, 2024-11-29 at 09:13 +1100, Stephen Morris wrote:
I have the number of parallel downloads set to 8 is obvious when the packages are being downloaded, hence if parallelism is at play here, why consistently those two rather than others as well?
Dunno. I could guess that those servers are under continual heavy load and things might hiccup more noticeably.
On 29/11/24 16:24, Tim via users wrote:
On Fri, 2024-11-29 at 09:13 +1100, Stephen Morris wrote:
I have the number of parallel downloads set to 8 is obvious when the packages are being downloaded, hence if parallelism is at play here, why consistently those two rather than others as well?
Dunno. I could guess that those servers are under continual heavy load and things might hiccup more noticeably.
I ran another dnf upgrade this morning and got the same issue with the google-chrome repository, but also the docker and Fedora updates repositories, so I guess it is potentially random.
regards, Steve
Tim:
Dunno. I could guess that those servers are under continual heavy load and things might hiccup more noticeably.
Stephen Morris:
I ran another dnf upgrade this morning and got the same issue with the google-chrome repository, but also the docker and Fedora updates repositories, so I guess it is potentially random.
It could be anything. Their end, your end, either has a momentary hiccup and resumes. It could be a race condition in the dnf program, where the incidental timing of one download finishing creates a new line in the textual output, in the wrong spot.
(on 2024-11-26, Stephen Morris said)
When I issue the command "sudo dnf upgrade", and it decides it needs to update and refresh all repositories, with the command I've just issued I noticed that it refreshed the google-chrome repository twice. Why is DNF doing that when there is only one repository definition in the .repo file, unlike the standard Fedora .repo files which have 3 repositories defined (not necessarily all active).
I'm only at F-40, but I often see the same sort of thing (no google- chrome repository for me) now and in past releases. I've never thought it was a problem, but I could be wrong. Just maybe this will help?... - - - - - - bash.6[~]: dnf --refresh upgrade dnf Fedora 40 - x86_64 111 kB/s | 32 kB 00:00 Fedora 40 openh264 (From Cisco) - x86_64 4.9 kB/s | 989 B 00:00 Fedora 40 - x86_64 - Updates 176 kB/s | 29 kB 00:00 Fedora 40 - x86_64 - Updates 1.8 MB/s | 4.3 MB 00:02 RPM Fusion for Fedora 40 - Free 10 kB/s | 3.6 kB 00:00 RPM Fusion for Fedora 40 - Free - Updates 16 kB/s | 3.3 kB 00:00 RPM Fusion for Fedora 40 - Nonfree 30 kB/s | 6.8 kB 00:00 RPM Fusion for Fedora 40 - Nonfree - Updates 31 kB/s | 6.3 kB 00:00 slack 4.0 kB/s | 1.8 kB 00:00 slack 4.1 kB/s | 2.9 kB 00:00 Dependencies resolved. Nothing to do. Complete! bash.7[~]: - - - - - - bash.7[~]: dnf repolist repo id repo name fedora Fedora 40 - x86_64 fedora-cisco-openh264 Fedora 40 openh264 (From Cisco) - x86_64 rpmfusion-free RPM Fusion for Fedora 40 - Free rpmfusion-free-updates RPM Fusion for Fedora 40 - Free - Updates rpmfusion-nonfree RPM Fusion for Fedora 40 - Nonfree rpmfusion-nonfree-updates RPM Fusion for Fedora 40 - Nonfree - Updates slack slack updates Fedora 40 - x86_64 - Updates bash.8[~]: - - - - - -
On 29/11/24 04:51, home user via users wrote:
(on 2024-11-26, Stephen Morris said)
When I issue the command "sudo dnf upgrade", and it decides it needs to update and refresh all repositories, with the command I've just issued I noticed that it refreshed the google-chrome repository twice. Why is DNF doing that when there is only one repository definition in the .repo file, unlike the standard Fedora .repo files which have 3 repositories defined (not necessarily all active).
I'm only at F-40, but I often see the same sort of thing (no google- chrome repository for me) now and in past releases. I've never thought it was a problem, but I could be wrong. Just maybe this will help?...
bash.6[~]: dnf --refresh upgrade dnf Fedora 40 - x86_64 111 kB/s | 32 kB 00:00 Fedora 40 openh264 (From Cisco) - x86_64 4.9 kB/s | 989 B 00:00 Fedora 40 - x86_64 - Updates 176 kB/s | 29 kB 00:00 Fedora 40 - x86_64 - Updates 1.8 MB/s | 4.3 MB 00:02 RPM Fusion for Fedora 40 - Free 10 kB/s | 3.6 kB 00:00 RPM Fusion for Fedora 40 - Free - Updates 16 kB/s | 3.3 kB 00:00 RPM Fusion for Fedora 40 - Nonfree 30 kB/s | 6.8 kB 00:00 RPM Fusion for Fedora 40 - Nonfree - Updates 31 kB/s | 6.3 kB 00:00 slack 4.0 kB/s | 1.8 kB 00:00 slack 4.1 kB/s | 2.9 kB 00:00 Dependencies resolved. Nothing to do. Complete! bash.7[~]:
bash.7[~]: dnf repolist repo id repo name fedora Fedora 40 - x86_64 fedora-cisco-openh264 Fedora 40 openh264 (From Cisco) - x86_64 rpmfusion-free RPM Fusion for Fedora 40 - Free rpmfusion-free-updates RPM Fusion for Fedora 40 - Free - Updates rpmfusion-nonfree RPM Fusion for Fedora 40 - Nonfree rpmfusion-nonfree-updates RPM Fusion for Fedora 40 - Nonfree - Updates slack slack updates Fedora 40 - x86_64 - Updates bash.8[~]:
I'm in the situation where I don't remember ever seeing this before the upgrade to F41. It may have always been happening and the changes in the dnf displays with DNF5 may be making it more obvious. I have seen refreshes, since upgrading to F41, where it has only refreshed the fedora updates repository and it has listed that twice, but without looking at the .repo definition I assumed it was because was refreshing the updates repository and the updates source repository and both of them had the same display name.
regards, Steve
On Fri, 2024-11-29 at 09:21 +1100, Stephen Morris wrote:
I assumed it was because was refreshing the updates repository and the updates source repository and both of them had the same display name.
The source repo is usually not enabled. And therefore completely ignored during general updates, as far as I'm aware.
On 29/11/24 16:27, Tim via users wrote:
On Fri, 2024-11-29 at 09:21 +1100, Stephen Morris wrote:
I assumed it was because was refreshing the updates repository and the updates source repository and both of them had the same display name.
The source repo is usually not enabled. And therefore completely ignored during general updates, as far as I'm aware.
I've checked the fedora updates repo and the source repo is indeed not enable, so it wasn't that. I thought I might have had it enabled as in the past I've been in a situation where having the kernel headers installed was not good enough for a package install, I had to enable the source repository for the install to proceed (I don't remember exactly what its dependency was).
regards, Steve
On Sat, 2024-11-30 at 10:09 +1100, Stephen Morris wrote:
I've checked the fedora updates repo and the source repo is indeed not enable, so it wasn't that. I thought I might have had it enabled as in the past I've been in a situation where having the kernel headers installed was not good enough for a package install, I had to enable the source repository for the install to proceed (I don't remember exactly what its dependency was).
Looking at things quickly, as well as the various long-named repos, there's plain Fedora with the original installation files, but individual Fedora repos for different CPU architectures, Fedora's own updates are a separate Fedora update repo.
I find that things mostly "just work." The people that have trouble seem to be the ones that bodge things up themselves, and just keep painting themselves into a corner. And the ones that never to fresh installs, and find some problem caused by release upgrades over release upgrades that other people didn't (or other people just lived with, or fixed up, without saying anything about it).
In the olden days, it was often the people that insisted on installing absolutely every package, and would install mutually exclusive things, and half-baked programs that were far from ready for general use.
On 30/11/24 20:14, Tim via users wrote:
On Sat, 2024-11-30 at 10:09 +1100, Stephen Morris wrote:
I've checked the fedora updates repo and the source repo is indeed not enable, so it wasn't that. I thought I might have had it enabled as in the past I've been in a situation where having the kernel headers installed was not good enough for a package install, I had to enable the source repository for the install to proceed (I don't remember exactly what its dependency was).
Looking at things quickly, as well as the various long-named repos, there's plain Fedora with the original installation files, but individual Fedora repos for different CPU architectures, Fedora's own updates are a separate Fedora update repo.
I find that things mostly "just work." The people that have trouble seem to be the ones that bodge things up themselves, and just keep painting themselves into a corner. And the ones that never to fresh installs, and find some problem caused by release upgrades over release upgrades that other people didn't (or other people just lived with, or fixed up, without saying anything about it).
Using the upgrade mechanisms to move to a new release of Fedora is how I upgrade. I have specific views on this which I won't air because nobody will like them.
In the olden days, it was often the people that insisted on installing absolutely every package, and would install mutually exclusive things, and half-baked programs that were far from ready for general use.
That was probably me, there used to be installation media for Fedora (I going back a long time) which installed both gnome and kde together. The disappearance of that annoyed me (or at least not being able to find it anymore) as I want both installed, and I don't like having to install just the gnome version and then having to install kde from the repositories, I want to install both at the same time.
regards, Steve
Tim:
In the olden days, it was often the people that insisted on installing absolutely every package, and would install mutually exclusive things, and half-baked programs that were far from ready for general use.
Stephen Morris:
That was probably me, there used to be installation media for Fedora (I going back a long time) which installed both gnome and kde together. The disappearance of that annoyed me (or at least not being able to find it anymore) as I want both installed, and I don't like having to install just the gnome version and then having to install kde from the repositories, I want to install both at the same time.
Installing a bunch of things isn't a problem (until you discover a conflict that someone else didn't). But there were people who insisted on they must install absolutely everything. As well as the potential for there being more problems the more things installed, there were packages that were mutually exclusive (you can't have both at the same time). And there's zero point into trying to install Nvidia packages when you don't have Nvidia hardware, for example.
-
Barry -
home user -
Stephen Morris -
Tim