Bug 500395

Summary: Repository from local iso-image with cyrillic simbols in path
Product: [openSUSE] openSUSE 11.1 Reporter: 1 2 <mmouxe>
Component: YaST2Assignee: Jan Kupec <jkupec>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P3 - Medium CC: forgotten_ny8t7SHjD_
Version: Final   
Target Milestone: ---   
Hardware: i586   
OS: openSUSE 11.1   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: screenshot of yast's answer
YaST log files

Description 1 2 2009-05-02 20:36:48 UTC 
User-Agent:       Opera/9.63 (X11; Linux i686; U; Edition IBIS; ru) Presto/2.1.1

All good if using latin symbols in path, but if using cyrillic (russian language) symbols in path to iso - reposytory can't connect.

Reproducible: Always

Steps to Reproduce:
1. Make directory with cyrillic name and copy there iso-image openSUSE-11.1-DVD-i586.iso,
2. Open YaST > Reposytories > Add > Local iso-image > Next
3. Specify path to image and click Next
Actual Results:  
YaST can't create repository
Comment 1 1 2 2009-05-02 20:39:03 UTC 
Created attachment 289558 [details]
screenshot of yast's answer
Comment 2 chen zhen 2009-05-05 04:36:16 UTC 
*** Bug 500405 has been marked as a duplicate of this bug. ***
Comment 3 Arvin Schnell 2009-05-05 08:37:48 UTC 
Please provide YaST logs, see http://en.opensuse.org/YaST/Bugs.
Comment 4 1 2 2009-05-05 11:27:12 UTC 
Created attachment 290028 [details]
YaST log files
Comment 5 Jan Kupec 2009-05-07 12:09:47 UTC 
I'll look at this in a few weeks.
Comment 6 Jan Kupec 2009-12-16 16:44:47 UTC 
Hi! This has been fixed in oS 11.2 in both zypper and YaST.

Note however that in YaST you must create the URL via the 'local iso image' option - that way it gets properly encoded.

e.g.
file:///local/jkupec/tmp/вещи
becomes
file:///local/jkupec/tmp/%D0%B2%D0%B5%D1%89%D0%B8

If you are creating the repository by giving the URL directly, YaST does not encode it (it already expects the encoded form).

We will improve this later by trying to find out whether the user gave an encoded URL or not, much like firefox or other web browsers do.