Re: Problems with the samba update

[Patrick Olson <compman@internetcds.com>]

> > I am going to assume that version is from unstable (also known as potato) 
> > since my Samba is older.  In that case, there was mention of a bug in that
> > version of Samba that makes it need a 2.2.x kernel.  The message at this
> > address has a better explanation than I can give:
> 
> So... I guess I need to downgrade to the version from Slink (I'm not
> planning to move to 2.2 since some other stuff I use won't work with it).
> Can I then mark it somehow as "non-upgradeable", so apt won't automatically
> upgrade it later?

Maybe temporarily.  The maintainer knows about it, it's listed at
http://www.debian.org/Bugs/db/40/40645.html 

I guess the web server is case sensitive, as I had to type it in with the
capital B in Bugs to make it work.  Darn picky thing.

There might be an alternative to a downgrade.  After looking at the bug
report, it looks like the problem is when it's built on a system running a
2.2.x kernel and glibc2.1 but only if you're running a 2.0.x kernel.  To
me, that means it might work if you got the source and built it yourself. 

If you were using dselect, you could use = to put a hold on the package
once you've downgraded it.  I'm afraid I don't know much about apt. 

Could someone enlighten both of us as to the method of putting a hold on
packages when apt is involved?


Hope this helps,

Patrick Olson