Bug 327251 - samba client 3.2.0.0.fc9
Summary: samba client 3.2.0.0.fc9
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: samba
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Simo Sorce
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-11 04:53 UTC by Darwin H. Webb
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-10-11 13:01:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Darwin H. Webb 2007-10-11 04:53:38 UTC
Description of problem:
Pre1 3.2 on F8 devl
connection to winodws xp share pushing works fine but pulling from share gets
popup message invaild parm for smb// (press skip, cancel, close)
Pressing skip continues, files seem to be ok. (This occurred more often with
picture (jpeg, png, bmp) than data (rpm's iso's)

Version-Release number of selected component (if applicable):
samba-client-3.2.0.0.pre1.fc9

How reproducible:
Most all ways when pulling from share.

Steps to Reproduce:
1.rpm -Uvh 
open Places, click on Share Name, enter user and password,
select from share, copy, select /home/Dlownload, paste.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Simo Sorce 2007-10-11 13:01:02 UTC
F8 will ship with 3.0.26a please try with that package.
3.2.0.0pre1 has been currently retired while waiting on licensing evaluation.

Comment 2 Darwin H. Webb 2007-10-11 16:03:27 UTC
It still has a bug and that is what you s/b concerned about.
Samba-3.2 and 4.0 will be used by almost all Linux's and it doesn't matter one
bit about Licensing. Especially nit picking on a gpl version.
There are a half billion Windows uses and only a few million Fedora users.
It is impossible to exsit without samba.
I will use 3.2.0 in F8 weather Fedora likes it or not.
So tell the nit pickers to get real. 
This is samba, not nvidia.

Darwin


Comment 3 Simo Sorce 2007-10-11 16:29:44 UTC
Just to make it clear:
I *do* care about this bug, and I will test for it, that's why it is just
DEFERRED. The right place for this bug, right now, is upstream though.



Note You need to log in before you can comment on or make changes to this bug.