|
Bugzilla – Full Text Bug Listing |
| Summary: | Build 905, update from 10.0: Media source does not contain the desired media | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Christoph Thiel <cthiel> |
| Component: | Installation | Assignee: | Jiri Srain <jsrain> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Stanislav Visnovsky <visnov> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | jsrain, jsuchome, snwint, suse-beta |
| Version: | Beta 9 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Christoph Thiel
2006-04-05 16:56:38 UTC
It seems, the "%2f" in the Url was encoded twice somewhere: 2006-04-05 07:47:58 <1> 10.10.100.202(3249) [YCP] Packages.ycp:500 [YCP] Packages.ycp:500 Initialize Package Manager: ftp://10.10.0.5/%2f%252fCDs/SUSE-Linux-10.1-Build_905-i386/CD1/ The question is, where this double-encoded url is from. Have you entered a "%2f" in the path of YaST Source entry dialog? No, I haven't entered the %2f! I just used the bootloader menu to specify the host + path for installation/update. Jiri (Steffen), it seems, that yast2 encodes the url it gets from linuxrc a second time or something like that. Can you please take a look on this? IIRC this came up after YaST had already installed some packages (please check the logs). And I guess linxurc is doing the right thing, as the initial part of the installation just works(tm) => YaST is to blame ;( Jiri, can you check the linuxrc -> yast2 code please? The problem mentioned in comment #2 is only problem of encoding for the log, but not for the real use (you can have look below in the code, that all packages from CD1 were correctly installed). So the problem is not there... I couldn't find the error in the log, would you be able to mention, which package was affected? No, I can't remember what packages was affected. Did you check the log for the error messages? I don't think the double encoded stuff was the problem, but rather the fact that I had to remove the %2f completly, when I got asked for it. As we discussed on Groupwise, please, try to reproduce, and in case of success, attach logs + install.inf. Might be a duplicate of bug #163784 or #163791 Yes, it looks so. *** This bug has been marked as a duplicate of 163791 *** |