Error while installing Magento Blue theme.

We used to get tickets complaining that the customers are not able to install Magento Blue theme via Magento Connect. When you try to install you may get the below error.

ERROR:
Via magento connect
magento-core/Interface_Frontend_Default_Default_Blue  requires package "magento-core/Interface_Frontend_Default" (version  >= 1.3.1, version <= 1.4.0, excluded versions: 1.4.0), installed  version is 1.4.0.0
Install Errors
No valid packages found
PEAR  ERROR: install failed

magento-core/Interface_Frontend_Default
magento-core/Mage_Core_Modules

To fix this, login to your account via SSH and navigate to the Magento installation folder and execute the below command.

Install Interface_Frontend_Default correct version


./pear install magento-core/Interface_Frontend_Default

And then the Blue theme

./pear install magento-core/Interface_Frontend_Default_Default_Blue

You can get help for pear command by executing

pear help 

And to list Channels

pear list-channels Registered Channel

Tweet This Post

How to create a RPM from source package(Creating CSF RPM)

We create RPM’s from the Source for a package. As an initial step, compile and install the source using normal procedures just to confirm all necessary libraries/dependencies are met.

Here I am explaining the whole process to create an RPM for CSF that could be  installed on cPanel servers.

Getting ready with the Source Files:

Download Latest CSF from here : http://www.configserver.com/free/csf.tgz

Extract the tarball.

[root@server new]# tar -xvf csf.tgz
[root@server new]# ls
csf  csf.tgz

Install to check all libraries/dependencies are met.

[root@server csf]# cd csf
[root@server csf]# sh install.cpanel.sh
*WARNING* TESTING mode is enabled - do not forget to disable it in the configuration
Installation Completed

We confirmed all libraries/dependencies are met for installing CSF.  We need to rename the tarball to define a version so that it could be used in the SPEC file.

[root@server csf]# cd ..
[root@server new]# ls
csf  csf.tgz
[root@server new]#mv csf csf-0.0.1
[root@server new]# tar -cvf csf-0.0.1.tar.gz csf-0.0.1

0.0.1 defines the version. (Can assign any). Now we are ready with the source file for CSF csf-0.0.1.tar.gz that could be used to generate RPM.

Building the RPM:

Install RPMBUILD tool:

[root@server ~]# yum install rpm-build

We never build RPM’s as ‘root’ users, but as normal users, because root can alter any file on the system, it was easy to inadvertently alter a running system by adding extraneous files or removing important files during interim builds of an RPM. Earlier RPM’s were build as root user but recently the RPM system changed to allow any user to build RPMs in a home directory. Building an RPM without the privileges of root prevents changes to core system files and hence we are on the safer side.

Initial Set-up:

We need to create a directory hierarchy for the rpm build tool to work with. To begin with, create a directory under your home directory which will act as the root directory for the build process. Lets make a directory ‘csfrpm’ under home directory for this purpose.

[sage@server ~]$ mkdir -p /home/your_username/csfrpm

[sage@server ~]$ cd /home/your_username/csfrpm

Create Five sub-directories under csfrpm.

[sage@server csfrpm]$ mkdir BUILD RPMS SOURCES SPECS SRPMS

• BUILD: BUILD is used as a space to compile the software.
• RPMS: RPMS contains the binary RPM that rpmbuild builds.
• SOURCES: SOURCES is for source code.
• SPECS: SPECS contains your spec file or files—one spec file per RPM you want to build.
• SRPMS: SRPMS contains the source RPM built during the process.

[sage@server csfrpm]$ ls
BUILD  RPMS  SOURCES  SPECS  SRPMS

Copy the source code that we have created(csf-0.0.1.tar.gz) to the SOURCES folder. Make sure that the owner  for source file is your_username.

[sage@server ~]$ cp csf-0.0.1.tar.gz /home/your_username/csfrpm/SOURCES/

Create the SPEC file:

SPEC file is noting but the configuration for rpmbuild tool.

[sage@server csfrpm]$ vi SPECS/csf.spec

# This is a sample spec file for csf

%define _topdir         /home/your_username/csfrpm
%define name            csf
%define release         0
%define version         0.0.1
BuildRoot: %{_tmppath}/%{name}-%{version}-root
Summary:                GNU csf
License:                GPL
Name:                   %{name}
Version:                %{version}
Release:                %{release}
Source:                 %{name}-%{version}.tar.gz
Group:                  Security/Tools

%description
A Stateful Packet Inspection (SPI) firewall, Login/Intrusion Detection and Security application for Linux servers.

%prep
%setup -q

%install
./install.cpanel.sh prefix=$RPM_BUILD_ROOT/usr/local

%clean
%{__rm} -rf %{buildroot}

%files
%defattr(-,root,root,0755)

Finally Build the RPM:

[sage@server csfrpm]$ rpmbuild -v -bb --clean SPECS/csf.spec

You can see the result if everything went fine:

Processing files: csf-0.0.1-0
Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/csf-0.0.1-root
Wrote: /home/your_username/csfrpm/RPMS/i386/csf-0.0.1-0.i386.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.84469
+ umask 022
+ cd /home/your_username/csfrpm/BUILD
+ cd csf-0.0.1
+ /bin/rm -rf /var/tmp/csf-0.0.1-root
+ exit 0
Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.84469
+ umask 022
+ cd /home/yuor_username/csfrpm/BUILD
+ rm -rf csf-0.0.1
+ exit 0

The RPM is written to /home/your_username/csfrpm/RPMS/i386/csf-0.0.1-0.i386.rpm

Tweet This Post

SupportSages – Semidedicated plans – Includes Sales + Billing + Support + Server Mgmt for $1800 per month

Let us handle every aspects of web hosting!! Sales + Billing + Ticket based Support + Tweets based support + Forum support + Server Management + Live Chat (L1 + L2 + Sales chats)

Such a 24/7 semi-dedicated team is available for $1800 per month.

Main aspects of semi-dedicated team

• 24/7 Helpdesk + LiveChat
• 4 RedHat certified Engineers (RHCE is just a qualification, but the real value is in the passion for the job. If you feel any of the engineer lacks the passion, he won’t continue in the team) who can handle support desk and sales as well + 1 semi-dedicated billing personnel
• Each tech can handle around 10-15 L1/L2 tickets a shift and team as a whole can solve around 30-40 tickets a shift. Multiple responses to a ticket is considered here as well.
• 24/7 Proactive Server Monitoring
• 24/7 Server Management
• Team of four techs + A LIII shift supervisor (shared by 2-3 such teams) + A Quality Manager (one per shift)
• You will get in touch with all four and the quality manager through IM. Any of the server issues can be addressed through IM.
• L1+L2 issues will have 15 minutes response time and 6 hours resolution time.
• LIII issues by this team “may” take 24 hours resolution time.
• They can support twitter based support

Currently available semi-dedicated team can handle Windows, Linux and FreeBSD issues with equal ease.

Our L1+L2 response times and resolution times are NOT average response time and is met for every tickets.

How to Order ?

http://www.supportsages.com/order/cart.php?a=add&pid=82

Once you order, team allocation will take around 24 hours time.

Contact Us

If you have any questions, please email sales [ at ] supportsages.com or contact our sales personnels at any of the IMs

AIM : SupportSages
MSN : supportsages@gmail.com
Gtalk : supportsages@gmail.com

or you can contact us via Live Chat option in the site or even through our contact us page http://supportsages.com/contact_us.html

Tweet This Post