Magento refuses to upgrade 1.4.2.0 ===> 1.5.0.1 - upgrade

This is my first time using Magento. I upgraded this site from 1.4.1.1 to 1.4.2.0 without issue. Now trying to go to 1.5.0.1 it just seems to refuse at every turn. I tried by entering this key into Magento Connect:
magento-core/Mage_All_Latest
And it says this:
Ignoring installed package magento-core/Mage_All_Latest
Nothing to install
I tried to upgrade via SSH and got this:
Attempting to discover channel "magento-core"...
unknown channel "magento-core" in "magento-core/Mage_All_Latest"
invalid package name/package file "magento-core/Mage_All_Latest"
Cannot initialize 'magento-core/Mage_All_Latest', invalid or missing package file
Package "magento-core/Mage_All_Latest" is not valid
install failed
In the downloader I noticed a the downloader had a version 1.5.0.0 upgrade available. I thought maybe I needed the newest downloader before I could update all the packages. I upgraded just the downloader to 1.5.0.0 which worked. Then I tried the full upgrade again and now it is mega retarded with this:
Couldn't resolve host 'magento-core'
That’s cute isn't it? So I gave it once last whirl at the ssh console and i get this bad boy:
Attempting to discover channel "magento-core"...
Attempting fallback to https instead of http on channel "magento-core"...
unknown channel "magento-core" in "magento-core/Mage_All_Latest"
invalid package name/package file "magento-core/Mage_All_Latest"
install failed
I tried a forcing it via SSH but still no love. I reverted from a backup I made so I do not have downloader 1.5.0.0 any more. Now of course I am back to square one with it telling me there is nothing to install when I try to update via MC.
When I check in MC if there are any updates available it lists these two:
Mage_All_Latest Upgrade to 1.4.2.1 (stable) Metapackage for latest Magento 1.4 release
And the Mage Downloader 1.5.0.1 but I already installed these before and it did no good so I restored my backup before the failed update.
I was trying to ask this question Magento's Forums but they are a mess right now. Their captcha fails and threads close on their own so you get little to no help. I wouldn't be surprised if they did this on purpose in concert with their 1.5.0.1 release.

Go to the root of your website and execute these commands (Where index.php is):
wget http://www.magentocommerce.com/downloads/assets/1.5.0.1/magento-1.5.0.1.tar.gz
tar -zxvf magento-1.5.0.1.tar.gz
Skip the next 4 commands if you have your magento install in a folder called Magento:
cd magento
cp -rf * /home/bitscom/public_html
cd ../
rm -rf magento
rm magento-1.5.0.1.tar.gz
For a detailed explanation see my post on the offical magento forum: here My name is Veracious on there.
If your SSH account is anything other than your apache user (i.e.: root. you will get error 500 when trying to access the site do the the permissions on the new files you just extracted. To resolve that use chown and chgrp. For a detailed explanation once again see my post:
here

I think the location for the upgrades have changed. Instead of the:
magento-core/Mage_All_Latest
use:
community/Mage_All_Latest
As what mrdon has mentioned.

I couldn't upgrade through Magento Connect either. I followed these instructions for installing magento and it worked fairly well. I changed line 3 as below to copy the folders/files over my existing ones.
wget http://www.magentocommerce.com/downloads/assets/1.5.0.1/magento-1.5.0.1.tar.gz
tar -zxvf magento-1.5.0.1.tar.gz
cp magento/* magento/.htaccess .
chmod -R o+w media var
chmod o+w app/etc

I followed the instructions from the following post to upgrade from 1.4.1.1 to 1.5.0.1:
http://www.magentocommerce.com/boards/viewthread/219720/#t301761
Then flushed the cache and reindexed everything. Everything worked.
Don't forget to change magento folder ownership to your web server user. In my case I had to run
chown -R www-data:www-data /var/www/magento

Related

take long time installing and updating packages by wget on arch linux

I don't know why, when im downloding or installing or updating package, download speed is very slow?
and take very long time!!!!
when im working in windows my download speed is 1M but in arch is changable ,is between 50k to 100k?
im using wget in pacman.conf
I use reflector but it had nothing changed and my package download speed is to slow.
can i create list from pacman update package and then download those from windows and again install all packages in Arch?
Please consider reading the documentation about pacman performance here.
You can manually force pacman to refresh the package lists (mirror list) with:
pacman -Syyu
To answer your question about downloading out of arch, the first part of the following will be with laverna which is a software I maintain on AUR, and the second part will be with a package in official repository.
AUR
Download
We have 2 solutions:
Use git
Download snapshot
Using Git
Clone in the current folder the repository with
git clone https://aur.archlinux.org/packages/laverna/ .
Using Snapshot
Just wget the snapshot or download directly with the browser.
wget https://aur.archlinux.org/cgit/aur.git/snapshot/laverna.tar.gz
Official Repositories
You can easily get a download link the package web page.
For example with sqlite-doc the web page link is here and the download link (from a mirror) is here.
Back to Arch
Then back to arch, we have to build and install packages. To do so we navigate to the folder where you cloned/downloaded the package (cf. cd) then execute the following to build.
(Only if packageName-version.pkg.tar.xz doesn't exist)
makepkg
Finally, after makepkg you obtain a file in the current directory which is in our AUR example laverna-0.7.4-RC1-linux-x64.pkg.tar.xz.
To install the packageName-version.pkg.tar.xz file we just have to execute the following and answer the questions as usually.
sudo pacman -U laverna-0.7.4-RC1-linux-x64.pkg.tar.xz
Check out your network settings,ip dns route... sometimes this will solve download speed problem.
Find the fastest mirror.
$ cd /etc/pacman.d/
$ cp mirrorlist mirrorlist.bak
$ rankmirrors -n 6 mirrorlist.bak > mirrorlist
Check mirrors status https://www.archlinux.org/mirrors/status/.
You can see more from Archwiki Mirrors.
Hope this helps.

unknown target when doing a fly sync

I have spun up a VM and I am trying to login to my concourse server with the following:
Christoher:pipeline christopher$ fly --target chris login --team-name chris --concourse-url http://ld4370.mycompany.com
Then, I am receiving this message:
WARNING:
fly version (2.5.0) is out of sync with the target (2.4.0). to sync up, run the following:
fly -t chris sync
However, when I do the following, I get this issue:
Christoher:pipeline christopher$ fly -t chris sync
error: unknown target: chris
At first, I had an older version of fly. So I deleted fly in my /usr/local/bin directory and then downloaded the latest. Now I am ahead of the concourse version that I installed on my VM. I have taken a look at the fly documentation but have not figured out how to get around this.
As an immediate fix to your problem, you can download any version of fly from github https://github.com/concourse/concourse/releases.
Download concourse & fly new version 5.0.0 on Mac do the following:
Download the latest version from concourse website https://mockersf.github.io/docs/download.html
then open finder press CMD + Shift + .
it will make all your hidden files visible temporarily open your user/local/bin folder then drag the new version of concourse to the bin and click replace
do the same for the fly and now go in command line press fly --version and you should see the new version
Download/ update concourse and fly version 4 and below 4 Hi go to this website basically you need to install the relevant version https://gist.github.com/kevin-smets/f20afd45a24ab3f88d01b2049ce7744f
for example:
copy this command
curl -Lo fly https://github.com/concourse/concourse/releases/download/2.5.0/fly_darwin_amd64 && chmod +x fly && mv fly /usr/local/bin/
and changed the version v2.6.0 to v2.5.0 past it in the terminal and same goes for the below :
curl -Lo concourse
https://github.com/concourse/concourse/releases/download/v2.4.0/concourse_darwin_amd64 && chmod +x concourse && mv concourse /usr/local/bin
and it should work.
I had similar problem i wanted install the v4.2.2 and it worked. the idea is the get the same version

How to run PHP 5.5.4 mcrypt run on CentOS 6.4?

I am getting the following error:
PHP Warning: PHP Startup: Unable to load dynamic library
'/usr/lib/php/extensions/no-debug-non-zts-20121212/mcrypt.so' -
/lib64/libc.so.6: version `GLIBC_2.14' not found (required by
/usr/lib/php/extensions/no-debug-non-zts-20121212/mcrypt.so)
Does mcrypt require glibc 2.14?
We are running CentOS 6.4 (latest stable version of CentOS) and it comes with glibc 2.12 (can't really upgrade glibc as being a core part of OS, changing it will likely break lots of stuff)
How do I make my PHP 5.5.4 run mcsypt under these circumstances?
Current configuration (phpinfo output) is here.
I was also having issues installing mcrypt on my VPS dev server so I thought I would post my solution in the hopes that it helps someone. I am running Centos OS 6.5 and had upgraded PHP to 5.5.13 using the Webtatic EL yum repository. https://webtatic.com/packages/php55/
First shh into your server
ssh admin#domain.com
initially I was trying to do (which was not working):
yum update
yum install php-mcrypt
I then realized my mistake when I looked at php -v and realized php-common was conflicting as the above code was trying to load a dependency from 5.3.
I then executed the following correct commands:
rpm -Uvh http://mirror.webtatic.com/yum/el6/latest.rpm
yum update
yum install php55w-mcrypt
service httpd restart
This worked perfectly for me.
I also read while researching this issue that some people did have to add the extension to their .ini file manually by adding the following line but i did not have to do this.
extension=mcrypt.so
you can find the location of your php.ini file by looking at phpinfo(); and see which configuration it is loading. For me the following ini files were loading:
/etc/php.ini
/etc/php.d/mcrypt.ini
/var/www/vhosts/system/domain.com/etc/php.ini
If the installation is successful then you will see the extension when you echo phpinfo();
Try installing php-mcrypt using yum. That should pull in any other libraries you need to run it.
yum install php-mcrypt
In light of your update, it would appear that you are trying to use the MCrypt extension built from another PHP Source which was created by an updated GLIBC library. The only proper solution I can see is the following:
You first need to ensure you have libmcrypt, libmcrypt-devel, and mcrypt installed before continuing. Check your CentOS repository.
Download the PHP Source from http://php.net
Untar the downloaded source tar -zxf php-5.5.4.tar.gz
cd into the source cd php-5.4.4
Copy your current ./configure string. The whole thing!
Add support for Mcrypt --with-mcrypt=/usr and run the new configure command
make && make install
restart Apache and PHP-FPM
This will keep your current configuration just as CentOS has built it but with the additional support of MCrypt as you are looking to have. Once you've done this, you do not need to enable the MCrypt extension in your php.ini file as it will be built into PHP itself and will be automatically loaded for you now.
When in doubt, you can also read up on the installation here http://us1.php.net/manual/en/mcrypt.installation.php

memcache install for MAMP using wrong API version

I'm attempting to install memcache for MAMP. It seems to configure/make/install fine but I'm getting an error saying the API version is wrong:
[26-Oct-2012 17:40:51 UTC] PHP Warning: PHP Startup: memcache: Unable to initialize module
Module compiled with module API=20090626
PHP compiled with module API=20100525
These options need to match
in Unknown on line 0
I am using MAMP 2.1.1 on OS X Mountain Lion.
I'm using this memcache build:
http://pecl.php.net/package/memcache/2.2.7
I extracted the archive into this directory:
/Applications/MAMP/bin/php/php5.4.4/include/memcache-2.2.7
And then ran these commands from the extracted directory:
/Applications/MAMP/bin/php/php5.4.4/bin/phpize
./configure
make
sudo make install
No errors except what I noted above, which I am seeing in:
/Applications/MAMP/logs/php_error.log
Any ideas on how to fix this?
Ok so after a few hours of trying to figure this out, I was able to find the problem and fix it. I'm pretty much a huge noob when it comes to all of this stuff, but here is the best I can explain what I think I figured out:
So, when I ran first ran phpize on the module, it was configured for my system's default installation of php. I had to point php and phpize to my PATH in my .bash_profile
export PATH=/Applications/MAMP/Library/bin:/Applications/MAMP/bin/php/php5.4.3/bin:/usr/local/bin:$PATH:/opt/local/bin
Make sure to change the php version to what ever version you are running.
After adding this to your path, running phpize -v should return:
PHP Api Version: 20100412
Zend Module Api No: 20100525
Zend Extension Api No: 220100525
and running which phpize should return: /Applications/MAMP/bin/php/php5.4.3/bin/phpize
So then it was just a matter of deleting all of the files that were installed the first time, and running through the installation process again. I unzipped the downloaded file cd into the unzipped folder and ran:
/Applications/MAMP/bin/php/php5.4.3/bin/phpize
./configure
make
cp modules/memcache.so /Applications/MAMP/bin/php/php5.4.3/lib/php/extensions/no-debug-non-zts-20100525/
And boom done. It works!
This article helped me out a lot, even though it isn't related to memcache: http://drupal.org/node/1464236

Install with pecl to local dir on shared hosting

I'd like to install a PHP extension on a bluehost shared site; specifically the MongoDB driver. Since pecl is unable to write to the primary server directory that has all the installed extensions, I'd like to install the mongo.so file to a directory I specify under my home. The closest article I found on the web was:
http://www.site5.com/blog/programming/php/how-to-setup-your-own-php-pear-environment/20090624/
However, after following the steps when I use the "pecl install mongo" command, it still keeps trying to install to bluehost's central directory on the server.
According to my web host's technical support team, utilising the pecl installer attempts to install the extension server-wide rather than under your account only. My web host doesn't allow server-wide installations in their shared environment for security reasons and because they want to keep their fleet universally the same across the board. I suspect your host is the same.
However, they did suggest I download, configure and install the pecl package (pecl_http) in my account only (rather than server-wide) via the following manual process:
$ cd ~/
$ wget http://pecl.php.net/get/pecl_http
$ tar -zxvf pecl_http.tar.gz
$ cd pecl_http
$ phpize
$ ./configure --prefix=~/bin
$ make
$ make test
$ make install
A successful install will have created extname.so and put it into the
PHP extensions directory. You'll need to edit php.ini (in my case,
this was a copy of the standard php.ini file that I placed in the same
folder as the script using the extension) and add an
extension=extname.so line (in my case, extension=http.so) before you can use the extension.
http://www.php.net/manual/en/install.pecl.phpize.php
Note that the tilde character (~) in the above code refers to the home directory of the current user (e.g. /home/username on my host's server).
Issues you may run into
When using the tar command, a "cannot open: not a directory" error
appeared as pecl_http had been downloaded without a file extension.
This was easily corrected:
mv pecl_http pecl_http.tar.gz
When using the make install command, a "cp: cannot create regular
file...: Permission denied" errror appeared. I resolved this issue
by changing the ext_dir for pecl...
pecl config-set ext_dir /home/username/bin/extensions
...and re-running make install. I also had to copy the http.so extension to /home/username/bin/extensions and then reference that location in my php.ini file:
extension_dir = "/home/username/bin/extensions"
this sounds like you don't have root access to your server. if your need to compile anything you must be have root access permission to server, or maybe you must be one of the sudoers.