Bug 144971 - yast installation source from local directory causes error when there is a space in the path
Summary: yast installation source from local directory causes error when there is a sp...
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Enhancement
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-23 21:31 UTC by Tim Fechtner
Modified: 2006-12-11 16:12 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
screenshot (215.93 KB, image/png)
2006-01-23 21:32 UTC, Tim Fechtner
Details
error message (580 bytes, text/plain)
2006-01-23 21:33 UTC, Tim Fechtner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Fechtner 2006-01-23 21:31:25 UTC
When you use yast to install varios rpms from a local directory, and in the path to the directory is a space, then the installation will fail. (However adding the directory as source works without problems, only later the installation fails). Here I used the path

/home/timi/Documents/OOo_2.0.151_LinuxIntel_install/SRC680_m151_native_packed-1_en-US.8998/RPM S/

as example. When I rename the directory from "RPM S" to "RPMS" and to the necessary changes for the installation sources, than the installation works fine.

I'll attach a screenshot and the error message of the installation.
Comment 1 Tim Fechtner 2006-01-23 21:32:46 UTC
Created attachment 64615 [details]
screenshot
Comment 2 Tim Fechtner 2006-01-23 21:33:14 UTC
Created attachment 64616 [details]
error message
Comment 3 Michael Gross 2006-01-24 17:47:32 UTC
I think this problem is known and was intended that way because of how the parser handles these paths. Nontheless maby this can be enhanced one day.
Jiri: Please comment on that.
Comment 4 Jiri Srain 2006-07-17 13:39:16 UTC
The URL handling in 10.1 should handle this properly