April 2025 Milwaukee Linux Users Group (MLUG) - Virtual Meeting Link

[Roger M. Jenson]

Use the following link to Join us for the April 2025 Milwaukee Linux
Users Group virtual meeting.

https://meet.jit.si/SensitiveInsectsBlastElse

Topics:

Adding disks to a Dell XPS 8500

        ToughArmor MB608SP-B Rugged Full Metal 6 Bay 2.5" SATA HDD &
SSD Removable Drive Enclosure Backplane Cage for 5.25" Bay


Server remote access with ZeroTier


Linux Commands to Have Some Fun in the Terminal


Best Regards,
Roger M. Jenson

[Tom]

Yo gang,

 

I am having issues updating my Fedora 40 workstation install.

 

If I specify a package or some number of packages, it can usually update them. I did stuff like this:

sudo dnf update kernel* grub* lib*

 

And that works.

 

But just plain

 

sudo dnf -y update

 

Doesn't-- it goes through all the motions, and downloads it all, then says

Error: Transaction test error:

File /usr/libs/.build-id/longhexvalue from install of dotnet-sdk-8.0-8.0.114-1.rc40.x86_64 CONFLICTS with file from package jellyfin-server-10.10.7-1.fc40.x86_64

 

Some other updates I've tried:

 

# dnf update jellyfin-server

Last metadata expiration check: 3:24:14 ago on Tue 22 Apr 2025 12:12:03 PM CDT.

Dependencies resolved.

Nothing to do.

Complete!

 

# dnf update jellyfin-server*

Last metadata expiration check: 3:24:18 ago on Tue 22 Apr 2025 12:12:03 PM CDT.

Dependencies resolved.

Nothing to do.

Complete!

 

I tried to update dotnet* but that fails with a conflict with jellyfin-server, as above.

 

A command like dnf update code* just reports "nothing to do."

 

I can still do updates as long as I avoid the dotnet ones. That means I can't just give a blanket dnf update command, but I've been doing them manually, using wildcards, so the huge number of updates that are needed is now a little smaller.

 

Any ideas?

 

[Tom]

UPDATE:

I ran:

dnf update -y --exclude=dotnet*

 

...and this succeeded. It reported skipping aspnetcore-runtime-8.0 but I don't have a lot of out of date packages anymore.

 

So I tried

dnf update dotnet*

...which again failed as described below.