|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast2-Product-Creator: unexpected EOF while looking for matching `'' | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Vladimir Botka <vbotka> |
| Component: | YaST2 | Assignee: | Marcus Schaefer <ms> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | jsuchome |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | yast2 log files | ||
|
Description
Vladimir Botka
2008-08-26 10:08:30 UTC
Created attachment 235440 [details]
yast2 log files
Jiri, bug in yast2-product-creator or in kiwi? Please, attach your config.xml. It should be located in /var/lib/YaST2/product-creator/images/suse-live-stick. Ping. (BTW, I assume the problem is that you are using cd/dvd package repository in the configuration) Ping! [SOLVED] After disabling CD/DVD from sources the build is running as expected. Thank you and sorry for the delay. Marcus, please add a better error handling for CD/DVD sources. See the one in initial comment, it is not helpful at all. I already added the zypper error message to be displayed in such a case. Additionally I now added a log excerpt for any error happening at that stage I also found that zypper handles errors not easy to the user. If you pass 100 packages to zypper to become installed and one doesn't exist zypper complains about that at the beginning but proceeds installing 99 packages before it exits with an error code != 0. All in all it does things correctly but a user has no clue why it exits unsuccessful because 100 lines or more above one line of an error was printed. This also should be changed if you complain about kiwi not providing good error messages :-) fixes in 2.77 Thanks Ad zypper: i agree, but what should be changed? Should zypper print an error summary at the end of the process? Or should it not continue in case of missing packages when in non-interactive mode? I think it should not continue in case of missing packages when in non-interactive mode. This immediately gives the user an impression what was wrong and according to the package count it reduces the time a user "waits for an error" Thanks for taking care of this I remember we fixed this also for code10 some time ago. Zypper > 0.12.7 will have the fix, too. It did report not found packages, but did not exit. Now it exits in non-interactive mode. |