I am unable to file bugreports for samba-3.3.
When I log inn as myself, I come to the bugzilla homepage. There I click "enter new bug" on the left.
Then I get to choose from:
BuildFarm: Product to track bad machines in the build farm
CifsVFS: CIFS file system for the Linux kernel
mod_auth_ntlm_winbind: Winbind Authentication Module for Apache
PIDL: Perl IDL Compiler
rsync: faster, flexible replacement for rcp and scp
Samba 3.0: SAMBA_3_0 subversion branch (historical) Now located at git://git.samba.org/samba.git (v3-0-test) CIFS File/Print/Authentication server (including client and server components)
Samba 3.2: Samba 3.2 release series providing CIFS File/Print/Authentication server (including client and server components)
Samba 4.0: The SAMBA_4_0 branch - unreleased and still under major development.
Samba Web: Sambaweb module and Samba.org web content
Samba 3.3 is not a choice at i should be.
I have tried this from firefox 3.0.4, safari 3.2, internet explorer 7.0.
I have tried it from 2 different ISP's (home and at work)
I have tried with or without a proxyserver inbetween.
I havee tried creating a brand new account for my self - same problem.
My goal is to post bug-reports for samba-3.3 ad we are deplying a samba-3.3-fileserver at my job soon and are hitting som problems we beleve could be bugs.
I can confirm this problem since I also doesn't see the choice Samba 3.3 on the page https://bugzilla.samba.org/enter_bug.cgi
Works for me, but marking as fixed since I'm assuming someone caught this today.
This works for you, it works for Karolyn and maybe all other members og the samba team. (I have som mails with Karloyn on samba-technical about it).
It still doesn't work for me and I believe it could be a problem for other users at well. Could you try creating a new "testuser" for your self? I am pretty sure you then will be able to reproduce the problem, using the testuser.
I can confirm that for a new test user I created, this is correct. The 3.3 product does *NOT* show up.
I'm a little stumped why. Just looking at the product in MySQL it looks the same as the rest to me. I'll try to get with others to see if we can figure out why.
Should be fixed now.
Works great now, thanks!