On Tue, May 06, 2003 at 02:17:14AM +0200, Carlos E. R. wrote:
changed the build to 666 ;)
Ah! :-)
Indeed ;)
... I mean, so long as the build is higher than any available patch it *ought* to 'win', right?
Yes, it should.
Cool...
I have used that trick before. Normally Suse does not update rpm's version for a suse version. But when you change the suse version then your rpm will be lower version than the new version and will be replced - ugh, I'm not explaining myself too well, am I? O:-)
Idunno... it's not too bad... reminded me a little of: http://www.nightattheopera.net/contract.html ;D
Ok, I mean that it will be honored till you upgrade the distro.
Or I figure out what *really* is the matter, and... well whereever that might lead...
Evenso, it seems more like a workaround... to me a padlock means "locked" period. (?)
Do you mean to say that the padlock or taboo setting, which did not work in suse 8.1, is not working either in suse 8.2? :-O
Too bad :-(
Yeah... I thought that *got* fixed in 8.1, though? Oh well, now at least I know to look out for it :-P Another question: Do you guys see my From: correctly? I don't, and haven't since I introduced folder-hooks in my .muttrc, in order to switch identity when replying to mail in my band-folder... (which happened a couple of days *before* I installed 8.2 and hence *should* be unrelated to the sasl-problem) Cheers, Jon Clausen -- If we can't be free, at least we can be cheap!