Re: [Samba] Verified bug in Woody Samba

2004-05-02 Thread Tony Whitmore
Jeremy Allison wrote:
On Sat, Apr 24, 2004 at 03:41:18PM -0500, blfs wrote:
OK, so I go to this page:

https://bugzilla.samba.org/enter_bug.cgi

Now what?

Samba 2.2 is not listed.


We are not accepting bugs against Samba 2.2 unless
they are security problems. Samba2.x is no longer
actively developed and is in security maintanence
mode only.
I suggest you file a bug with the Debian project
and ask them to update to a maintained version of
Samba.
Although Samba 3 isn't in the Debian stable tree, the forthcoming 
release of Debian 3.1 includes Samba 3.0.2a. Although this release has 
been a long time in development, there isn't a confirmed release date 
yet as the last few bugs are still being squished.

However, if you can't wait for that release, www.backports.org provides 
a Samba 3.0.2a package for Debian stable which I have tested and found 
to be OK at work. The website provides instructions on how to get 
packages via apt. The only thing that the backports.org packages were 
missing that I needed was "quota reporting" support, but I was able to 
recompile the packages quite easily to enable this option.

Cheers,

Tony
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Verified bug in Woody Samba

2004-05-01 Thread Jeremy Allison
On Sat, Apr 24, 2004 at 03:41:18PM -0500, blfs wrote:
> 
> - Original Message - 
> From: "Gerald (Jerry) Carter" <[EMAIL PROTECTED]>
> To: "blfs" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Saturday, April 24, 2004 9:38 AM
> Subject: Re: [Samba] Verified bug in Woody Samba
> 
> 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> > 
> > blfs wrote:
> > 
> > | How do I go about reporting this error?  I would also
> > | not mind taking the time to reprogram the code to fix
> > | this one bug, since it took me a week of frustration to
> > | find it.
> > 
> > https://bugzilla.samba.org/
> > 
> > 
> 
> 
> OK, so I go to this page:
> 
> https://bugzilla.samba.org/enter_bug.cgi
> 
> Now what?
> 
> Samba 2.2 is not listed.

We are not accepting bugs against Samba 2.2 unless
they are security problems. Samba2.x is no longer
actively developed and is in security maintanence
mode only.

I suggest you file a bug with the Debian project
and ask them to update to a maintained version of
Samba.

Cheers,

Jeremy.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Verified bug in Woody Samba

2004-04-26 Thread Gerald (Jerry) Carter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
blfs wrote:

| OK, so I go to this page:
|
| https://bugzilla.samba.org/enter_bug.cgi
|
| Now what?
|
| Samba 2.2 is not listed.
Sorry.  Thought you were on 3.0.  There is no further
development going on for the 2.2 branch.  If you can reproduce
this against 3.0.x, then let us know.




cheers, jerry
- --
Hewlett-Packard- http://www.hp.com
SAMBA Team -- http://www.samba.org
GnuPG Key   http://www.plainjoe.org/gpg_public.asc
"...a hundred billion castaways looking for a home." --- Sting
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFAjVmpIR7qMdg1EfYRAn6GAJ4gFWmwCHMaECTlBELJEkJQk5Ah8wCgt0Qg
/600h394hWThqbgbOs2ixko=
=B7zT
-END PGP SIGNATURE-
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


[Samba] Verified bug in Woody Samba; Where to report?

2004-04-25 Thread blfs
I have spent the last week trying to figure out 
why the command

smbclient -L win98server

kept crapping out.  After grepping through the
source code, I figured out the error was in
gethostbyname(I think).  

The solution to this problem is running the
command 

smbclient -L win98server -R bcast

instead.

But that still leaves it to the next person to figure 
this all out, and that is not really a good solution.

smbclient -L win98server 

should be a workable command.  

How do I go about reporting this error?

https://bugzilla.samba.org/enter_bug.cgi

has no category for Samba 2.2






-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Verified bug in Woody Samba

2004-04-24 Thread blfs

- Original Message - 
From: "Gerald (Jerry) Carter" <[EMAIL PROTECTED]>
To: "blfs" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, April 24, 2004 9:38 AM
Subject: Re: [Samba] Verified bug in Woody Samba


> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> blfs wrote:
> 
> | How do I go about reporting this error?  I would also
> | not mind taking the time to reprogram the code to fix
> | this one bug, since it took me a week of frustration to
> | find it.
> 
> https://bugzilla.samba.org/
> 
> 


OK, so I go to this page:

https://bugzilla.samba.org/enter_bug.cgi

Now what?

Samba 2.2 is not listed.

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Verified bug in Woody Samba

2004-04-24 Thread Gerald (Jerry) Carter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
blfs wrote:

| How do I go about reporting this error?  I would also
| not mind taking the time to reprogram the code to fix
| this one bug, since it took me a week of frustration to
| find it.
https://bugzilla.samba.org/





cheers, jerry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFAinvZIR7qMdg1EfYRAjKGAJ9iygUxN+IAd+fZwUJWSuedL4noTgCfbOch
CS37XpWV5q6PBtMZmlsUCSA=
=QLK4
-END PGP SIGNATURE-
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


[Samba] Verified bug in Woody Samba

2004-04-23 Thread blfs
I have spent the last week trying to figure out 
why the command

smbclient -L win98server

kept crapping out.  After grepping through the
source code, I figured out the error was in
gethostbyname(I think).  

The solution to this problem is running the
command 

smbclient -L win98server -R bcast

instead.

But that still leaves it to the next person to figure 
this all out, and that is not really a good solution.

smbclient -L win98server 

should be a workable command.  

How do I go about reporting this error?  I would also
not mind taking the time to reprogram the code to fix
this one bug, since it took me a week of frustration to
find it.  



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba