similar to: upgarde smbd to 3.0.6 and keep winbind to 3.0.2a, possible ?

Hi I upgraded my rails application rails 2.3.8 from 2.3.5 like below gem install rails -v=2.3.8 Now in environemnt.rb RAILS_GEM_VERSION changed to ''2.3.8''. Now when I tried to a previous migration like rake db:migrate VERSION=20100714122104 I got warning like DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed_job/tasks, vendor/plugins/paperclip/tasks,

Hi, As I said yesterday, I worked on a solution for tdb format in order to manage easily new fields for this format. So I add small changes to init_sam_from_buffer and init_buffer_from_sam in this purpose. The data TDB_FORMAT_STRING became an array which contains the list of the different fields format which exist. When the tdb file is read, for each records, Samba will try the most recent

Hello I have samba-3.0.2 installed into /usr/local/samba/ by means of cd /usr/src/samba-3.0.2/source ./configure --with-acl-support make make install When I run pdbedit -L I get a segfault: oberon root # pdbedit -L Segmentation fault (core dumped) This occurs after samba of unknown version from these two: 3.0.1pre2 3.0.2 has been reinstalled with samba-3.0.2 (gdb) bt #0 0x400f9bf9 in free

I have recompiled pdbedit 3.0.2 with -g flag to be able to list sources from gdb when debugging pdbedit and discovered some more info but don't know how to interpret it: (gdb) frame 1 #1 0x0806c899 in init_sam_from_buffer (sampass=0x81b8c28, buf=0x81b8d78 "", buflen=208) at passdb/passdb.c:1462 1462 SAFE_FREE(domain); (gdb) print domain $8 = 0x10000 <Address

This is from the June 16 CVS, it also happens with June 15 but not with June 8. Basically, imap segfaults when opening my mbox. Some details are below: Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. #0 0x08094e5c in message_parse_header_next (ctx=0x80c8e10, hdr_r=0xbffff64c) at message-parser.c:755 755 if (msg[0] ==