|
Bugzilla – Full Text Bug Listing |
| Summary: | YaST2 warnings, autoyast writes aliases without colon | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Bernhard Walle <bwalle> |
| Component: | YaST2 | Assignee: | Peter Varkoly <varkoly> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | varkoly |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
AutoYaST file
YaST2 logs ag_fetchmail.diff mailtable.diff |
||
Created attachment 159632 [details]
AutoYaST file
Created attachment 159643 [details]
YaST2 logs
Created attachment 161474 [details] ag_fetchmail.diff > sh: /etc/sysconfig/fetchmail: [No such file or directory] This should fix it. Created attachment 161478 [details] mailtable.diff These two are triggered by the "aliases" part of the profile and fixed by this patch. > Use of uninitialized value in split at > /usr/share/YaST2/modules/MailTableInclude.pm line 185 (#1) Harmless. > Use of uninitialized value in print at > /usr/share/YaST2/modules/MailTableInclude.pm line 204 (#1) This is actually a real bug. $oseparator was wrongly initialized only in Read, so when writing /etc/aliases we miss the mandatory colon separator. Peter, please apply the patch from comment 3. I will apply the other one to yast2.rpm. yast2-2.15.54 submitted patch applied in svn |
During AutoYaST installation via VNC, I saw following warnings on the console *** Starting YaST2 *** Xlib: extension "XInputExtension" missing on display ":0.0". sh: /etc/sysconfig/fetchmail: Datei oder Verzeichnis nicht gefunden Use of uninitialized value in split at /usr/share/YaST2/modules/MailTableInclude.pm line 185 (#1) (W uninitialized) An undefined value was used as if it were already defined. It was interpreted as a "" or a 0, but maybe it was a mistake. To suppress this warning assign a defined value to your variables. To help you figure out what was undefined, perl tells you what operation you used the undefined value in. Note, however, that perl optimizes your program and the operation displayed in the warning may not necessarily appear literally in your program. For example, "that $foo" is usually optimized into "that " . $foo, and the warning will refer to the concatenation (.) operator, even though there is no . in your program. Use of uninitialized value in print at /usr/share/YaST2/modules/MailTableInclude.pm line 204 (#1)