Bug 635820

Summary: switch warning in the YaST Samba Server module
Product: [openSUSE] openSUSE 11.3 Reporter: Lars Müller <lmuelle>
Component: YaST2Assignee: Lukas Ocilka <locilka>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Enhancement    
Priority: P3 - Medium CC: hendrikw, opensuse-wagnerm, opensuse.lietuviu.kalba, samba-maintainers
Version: Final   
Target Milestone: Factory   
Hardware: All   
OS: openSUSE 11.3   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: No
Marketing QA Status: --- IT Deployment: ---

Description Lars Müller 2010-08-31 10:40:03 UTC
I called YaST Samba Server on a 11.3 system and got a pop up message stating:

"Switch will be removed from the Perl core distribution in the next major release. Please install it from CPAN. It is being used at /usr/share/YaST2/modules/SambaServer.pm, line 17."
Comment 1 Mindaugas Baranauskas 2010-09-01 06:44:54 UTC
The similar is with YaST2 HTTP server module:

Switch will be removed from the Perl core distribution in the next major release. Please install it from CPAN. It is being used at /usr/share/YaST2/modules/YaPI/HTTPD.pm, line 299.
Comment 2 Lars Müller 2010-09-01 10:07:29 UTC
Adding Michal as he's the author of YaST http server.

And this sounds more and more like a generic YaST issue.

@YaST dudes: Had there been a discussion on yast-devel at http://lists.opensuse.org/yast-devel/ about this?
Comment 3 Lars Müller 2010-09-01 10:09:03 UTC
Passing into need info state from Michael to get his attention.
Comment 4 Michal Zugec 2010-09-07 08:00:07 UTC
Juergen, could you write us more details (when it will be splitted)?
Is it enough to add perl-Switch package into specfile?
Comment 5 Hendrik Woltersdorf 2010-11-16 19:42:57 UTC
I got the same error message in openSUSE 11.4 milestone 3 of 6.
btw: This bug seems to be a duplicate of bug #621474.
Comment 6 Lukas Ocilka 2011-01-07 09:27:12 UTC
Fixed in yast2-samba-server 2.20.2
Comment 7 Lukas Ocilka 2011-01-07 09:28:52 UTC
*** Bug 621474 has been marked as a duplicate of this bug. ***