samba and smbfs depend on an old version of samba-common

[Sam Illingworth]

Cannot install samba, so unable to create shares. Here are the errors Synaptic gives me if I try to install smbfs or samba:

smbfs:
  Depends: samba-common (=2:3.3.2-1ubuntu3) but 2:3.3.2-1ubuntu3.1 is to be installed

samba:
  Depends: samba-common (=2:3.3.2-1ubuntu3) but 2:3.3.2-1ubuntu3.1 is to be installed

[Thierry Carrez (ttx)]

Sounds like an incomplete archive sync, with half the samba package at ubuntu3.1 and half at ubuntu3. Running "sudo apt-get update" (or "Checking for updates") again should get you a mirror in a better sync.
Please confirm you can still reproduce this after that.

[Sam Illingworth (mazz0)]

OK, I've tried that, can still replicate.

Here's a screenshot showing the samba packages sorted by latest version; you're right - some are 3, some 3.1.

Funny thing is, if I go to Force Version on samba-common it lists the two options as

2:3.3.2-1ubuntu3.1 (now)
2:3.3.2-1ubuntu3 (Jaunty)

But I'm using Jaunty - why isn't the Jaunty version the one I have? If I select the Jaunty version it wants to remove smbclient, ubuntu-desktop and winbind.

[Chuck Short (zulcss)]

@Sam

You might want to try a different mirror then.

Regards
chuck

[Sam Illingworth (mazz0)]

Do you mean the "Download from" option on the first tab of Software Sources? I tried changing that a couple of times, no difference.

Can anyone replicate this? What's showing up under "latest version" for the various samba packages for you guys?

[Chuck Short (zulcss)]

Hi,

Please post your /etc/apt/sources.list

Thanks
chuck

[Sam Illingworth (mazz0)]

Attached

[Chuck Short (zulcss)]

No we are not able to reproduce.

Regards
chuck

[Sam Illingworth (mazz0)]

Well, I suppose it's good that it's not affecting other people, but I've never manually edited my sources file, and I've disabled every optional repo so I'm only looking at the standard Ubuntu ones, so this would still seem to be an Ubuntu bug. Hmm. Well, I'm planning on doing a fresh install when Karmic is out, so I imagine this will be resolved in three days! Well, not resolved, but it won't effect me any more, and since nobody else has subscribed I don't suppose it matters. I don't like just giving up though, something must have gone wrong and without having found out what we've no reason to assume that that bug isn't still in there somewhere, waiting, watching, slowly and surely drawing its plans against us...

[Gilles (ubuntugc1)]

I am having the same problem on Karmic (Mythbuntu 9.10 more exactly).

The version numbers are slightly different but the issue is the same (the SMBFS package wants a Samba common 2:3.4.0-3ubuntu5 whilst a 2:3.4.0-3ubuntu5.1 is installed.

I only use the standard main, universe and multiverse.

I wonder if samba common was updated via some security update but that the other stuff like smbfs and smbclient was not (and perhaps if I had installed smbfs before the security update then it would have worked and got the correct library?).

[Gilles (ubuntugc1)]

Attaching sources.list just in case (but as I said, only using the bog standard ubuntu repositories).

Note: Also did an update and broken package check.

[Gilles (ubuntugc1)]

I was able to fix my problem by forcing samba and samba-common back to 5 (instead of 5.1). I was then able to install smbfs and it is currently working fine.

Still, I suspect there must be a problem somewhere in the Ubuntu repository as, ideally, it would be preferable if simple users like me did not have to force a downgrade of the core samba server...

HTH

[neural_oD (nutter78)]

Hi - I too have this problem:

samba: Depends: samba-common (= 2:3.4.0-3ubuntu5) but 2:3.4.0-3ubuntu5.1 is to be installed

I'm using 9.10 64 bit

[gaintpune (ralf-milunchup)]

i can confirm the issue using ubuntu 9.10 AMD64.
samba: Depends: samba-common (= 2:3.4.0-3ubuntu5) but 2:3.4.0-3ubuntu5.1 is to be installed
smbfs: Depends: samba-common (= 2:3.4.0-3ubuntu5) but 2:3.4.0-3ubuntu5.1 is to be installed

[Thierry Carrez (ttx)]

It's an issue in repositories and mirrors, it shouldn't last for more than a day. Not a bug in samba itself, though it's potentially a bug in the mirror infrastructure.