Forgive me if this is answered elsewhere, but I haven’t been able to puzzle it out.
When I try to install the pattern “lamp_server” with zypper on a fresh openSUSE 11.3 box I’m only getting the metapackage “patterns-openSUSE-lamp_server” installed, nothing else. Apache, MySQL, and PHP are all listed as “recommended” only.
I know how to install the packages individually, and I know I can force matters with the “–recommended” flag. Unfortunately installing the recommended packages also wants to throw in apparmor and sw_management, neither of which I want right now.
Am I overlooking something? The command I used:
zypper install -t pattern lamp_server
I appreciate any help you can provide. My main goal is to communicate this process to others, so I’d like to give them the option of the simpler pattern install.
Well that sounds familiar. Bug# 656952 in Novell’s BugZilla was something
I reported a few weeks ago with the following description:
<quote>
SUSE Studio 2010-12-01
Built a server starting w/OpenSUSE 11.3 JeOS as the base. Added lamp_server
pattern but Apache httpd was not added (went through to completion to verify).
Expected Results: LAMP Servers should include the Apache web server. Instead
it only shows as recommended software.
Actual Results: No web service that I could see.
</quote>
Perhaps this is not a SUSE Studio thing at all. No, not sure what to do
about it, but I’ll update the bug to see if it helps with its priority.
Good luck.
On 12/23/2010 12:36 PM, Jered wrote:
>
> Forgive me if this is answered elsewhere, but I haven’t been able to
> puzzle it out.
>
> When I try to install the pattern “lamp_server” with zypper on a fresh
> openSUSE 11.3 box I’m only getting the metapackage
> “patterns-openSUSE-lamp_server” installed, nothing else. Apache, MySQL,
> and PHP are all listed as “recommended” only.
>
> I know how to install the packages individually, and I know I can force
> matters with the “–recommended” flag. Unfortunately installing the
> recommended packages also wants to throw in apparmor and sw_management,
> neither of which I want right now.
>
> Am I overlooking something? The command I used:
>
> zypper install -t pattern lamp_server
>
> I appreciate any help you can provide. My main goal is to communicate
> this process to others, so I’d like to give them the option of the
> simpler pattern install.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
How did you perform a fresh install without getting sw_management installed, which is the yast module to manage your software packages? You must have removed packages from the default install. No offence meant
Even on a headless server (i.e. no graphic desktop), I’d still use yast, in it’s ncurses version. Last weekend I installed 11.3 on a headless server, no X, through a text install, incl. LAMP, by justing checking the box left of “LAMP server”.
Thanks for following up with the bug report, I appreciate it. It certainly didn’t strike me as intended behavior, and I had installed a pattern (devel_basis) prior to that with no issues. If no solutions come up I’ll just go at it the old-fashioned way, and update the doc if I can get lamp_server working another time.
And yes, some defaults were removed, which was part of why I wondered about it. But I had installed devel_basis with no issues, so it didn’t seem like zypper was installed incorrectly.
I’ll talk to the sysadmin creating the image about YAST (he’d said he left it off because the main YAST package wanted X as a prereq). Meanwhile I’ll give the install a try with ncurses YAST to see if it makes a difference. I’ll be honest, though, I’d much prefer to have it work through zypper instead of requiring YAST be installed for full package management functionality.
I’m afraid I get the same result with yast. To check that I didn’t leave anything out there - I installed the yast2_basis pattern, ran yast, searched for lamp_server, selected the pattern for install, and let it do its thing. Yast installed the same packages as zypper.
I’ll add “look at yast more” to my list of things to do though, thanks for having me look more closely at it. The yast2_basis pattern installs more than needed (infrared, ISDN, and others), but obviously that can be trimmed down.