New problem - Can't install working version of Samba

[Tom P]

Ok, I got past the problem I had upgrading Fedora to version 40. 

Now I can't install a newer version of Samba.

First of all, is it a problem that dnf tells me I have 1591 things installed that have "fc37" in their names, despite being on fedora 40? I did this:

dnf update -y

<nothing to do>

rpm -qa | grep fc37

and got 1591 packages.

There none with fc39 or fc38 or fc39 or fc40 in their names. There are 12 packages matching fc35.

Now, my latest problem seems to be a screwed up repo issue. Whenever I tell it to install samba, I get some old 4.17 version tagged with "fc37"

I'm just doing dnf install samba here. 

i know there's a 4.22 version out there. I'm currently building it from source, but that failed last time.  I think the failure mode was

1. Did ./configure - worked

2. Did make - worked

3. Did make install - worked too

4. Did systemctl start smb - No unit called smb found

5. Did systemctl start nmb - No unit called nmb found.

I'm running the make / make install again. Takes for-bloody-ever!

Help! 

--

--
Tom Peters • a50m...@gmail.com • N9QQB (amateur radio) • Six meters: The Magic Band
"HEY YOU" (loud shouting) • Second Tops (Set Dancing) • FIND ME ON FACEBOOK
43° 7' 17.2" N by 88° 6' 28.9" W • Elevation 815' • Grid Square EN53wc
LAN/Telecom Analyst • Open-source Dude • Musician • Registered Linux User 385531

[Isaiah C]

Tom,

It looks like you might have some stale entries in /etc/yum/repos.d/.  It's unclear if you are using dnf's system-upgrade plugin to do these upgrades, which does a lot of work to clean up old repos.  That being said it isn't infallable and can leave some stuff behind.  You may need to grep through your repo files to find any references to older versions of Fedora.  Once you have done that you will likely want to run `dnf distro-sync --refresh`

Regarding your services failing to start, if memory serves me correctly, building smb from source does not create unit files for you; you will likely need to build those from scratch.

Cheers!

Isaiah

[Tom P]

Ah! /etc/repos.d is the directory where that gets stored. That's key info, thanks for that. I will dig into that and see if I can clean up. 

I am able to get my compiled-from-source Samba to run, but the unit files I devised are kludgy and don't quite work right. 

The main problem I'm having hasn't changed or improved. The pentest group scanned this machine with nmap and it reports an old version of smbd is running. So I embarked on an odyssey of trying to install a new version (which failed, as I explained) and finally resorted to compiling it from source. Now that I've (sort of but not completely) go that working, it reports EXACTLY the same version! Arrrg!

Any insights into that greatly appreciated. 

-T

--
Homepage: http://www.milwaukeelug.org/home
This forum online: https://groups.google.com/forum/#!forum/MilwaukeeLUG
---
You received this message because you are subscribed to the Google Groups "Milwaukee Linux User's Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to MilwaukeeLUG...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/MilwaukeeLUG/31510d85-cdc5-41b0-b242-f86d8097abf0n%40googlegroups.com.

[Isaiah C]

I'm not looking at it right now, but if I recall correctly, unless you specificy a path prefix when running "./configure" it will drop the daemon binary into /usr/local/samba/sbin.  Did you update your unit file to reflect the changed binary path? 

Cheers