[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Uploaded samba 2.0.6-1 (m68k) to erlangen



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.6
Date: Thu, 11 Nov 1999 12:08:15 -0500
Source: samba
Binary: samba-doc swat smbclient samba-common smbfs samba
Architecture: m68k
Version: 2.0.6-1
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon <buildd@kullervo.informatik.uni-erlangen.de>
Description: 
 samba      - A LanManager like file and printer server for Unix.
 samba-common - Samba common files used by both the server and the client.
 smbclient  - A LanManager like simple client for Unix.
 smbfs      - Mount and umount commands for the smbfs (2.0.x and 2.1.x kernels)
 swat       - Samba Web Administration Tool
Closes: 33240 37692 38040 38988 39512 42335 44131 44705 46432 46605 46992 47332 48186
Changes: 
 samba (2.0.6-1) unstable; urgency=low
 .
   * Samba 2.0.6 has been released. This is the first try of the Debian
     Samba packages. I know for sure that smbd won't work properly on
     2.0.x kernels because the patch that Wichert sent me does not apply
     to the new source/lib/util_sec.c in Samba 2.0.6. That file was
     completely re-written by Tridge.
   * Updated README.Debian.
   * A new client utility called smbspool appeared in Samba 2.0.6. I added
     this utility to the smbclient package, although I haven't tried it yet.
   * Added the symlink /sbin/mount.smbfs that points to /usr/bin/smbmount.
     This is to be able to type "mouont -t smbfs ...". This symlink goes
     in the smbfs package, of course.
   * This new release should close the following bugs (some of these
     are fixed for sure in this new upstream release, some others I could
     not reproduce but I believe they are fixed if they were real bugs.
     As always, please feel free to re-open the bugs if the problem is not
     solved).
       Closes: Bug#33240: icmp mask needs a bug workaround.
       Closes: Bug#37692: samba: Has problems detecting interfaces.
       Closes: Bug#38988: samba: Truly bizzare behavour from nmbd.
       Closes: Bug#46432: samba-2.0.5a-2: nmbd does not appear to broadcast
                           properly.
       Closes: Bug#44131: smbfs: no longer possible to set file and
                           directory-modes.
       Closes: Bug#46992: smbmount-2.2.x manpage wrong.
       Closes: Bug#42335: smbfs: missing options from the new 2.2.x commandline.
       Closes: Bug#46605: smbmnt segfaults.
       Closes: Bug#48186: smbmount.
       Closes: Bug#38040: smbfs: Please add /sbin/mount.smb [included].
       Closes: Bug#47332: smbmount: could -f and -P be added back?
   * Samba has been compiled with PAM support (closes: Bug#39512 - samba PAM
     module). To succesfully add PAM support, I created /etc/pam.d/samba and
     added this file as a conffile for the samba-common package. I also made
     samba-common depend on libpam-pwdb.
   * Added simple man pages for the wrapper scripts smbmount and smbmount.
     (Closes: Bug#44705 - Missing smbmount man page)
   * Installed libreadlineg2-dev in my system so smbclient now has a
     "history" command and libreadline support :-)
   * This time I did add a check to the smbmount wrapper script to see if
     the kernel has support for smbfs, as suggested by Jeroen Schaap
     <J.Schaap@physiology.medfac.leidenuniv.nl>. I mentioned in the changelog
     for samba-2.0.5a-3 that I did this but I forgot at the end.
Files: 
 f19b2e2c335eadec35110026cf62e878 872796 net optional samba_2.0.6-1_m68k.deb
 0d72dac88b85115f3fc76303991be1d4 281864 net optional samba-common_2.0.6-1_m68k.deb
 0a0d847fb643b817e671ce4573204c59 507258 net optional smbclient_2.0.6-1_m68k.deb
 7fec104943c02300dc4ad5b1a4d56c17 325518 net optional swat_2.0.6-1_m68k.deb
 e049cb2e856a62b9c9288599c399e4be 320708 otherosfs optional smbfs_2.0.6-1_m68k.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.8 (SunOS)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard <http://www.gnupg.org/>

iEYEARECAAYFAjg5FMkACgkQcS3JWD3Fdvf52wCdEuEMYc8eNZ5O7WsMJt4CkZQs
u8wAmQFrs4BhmEBCii0hyJBA8HpUFePY
=KOvS
-----END PGP SIGNATURE-----


Reply to: