Just downloaded the full 1.5.1 Tarball.

Installed new TKL Magento 11.1 build.

Before running anything I dropped the Tarball onto the Magento folder then expanded.

TKL FileManager warned that this might overwrite some files.

Now when I run Magento, it is still indicating version 1.42 in the Footer.  I don't believe this is TKL's footer, but rather the standard Magento Footer.

How to accomplish an upgrade?

Magento wants to have PHP-APC running but I can't get it to function after installing

apt-get install php-apc

(Page Loads blank, even after deleting cache and session files in Magento).

I was able to get APC to stick in the Patch version last fall.

Any thoughts?

Somehow ./mage mage-setup wants both APC and XCACHE installed but they cannot coexist int he system (they do the same thing).

With XCache installed our site is at least working (not upgrading).

So, I have removed APC again (but still get a PHP, failed to load ...apc.so error when I reun mage-setup from ssh (get the same for XCache if APC is installed rather than Xcache.. PHP seems to want both)... but can't have both.

Though this is "part" of the issue, as noted earlier, cannot upgrade the raw build 1.4.2 out of the box w/ no attempted apc installs and removals inside it.

I cannot find reference to xcache or apc in any of my php.ini files  (3 of them)

I just came back at this from another angle and I have gotten the new system to show up intact (so far).

In SSH an Subversion from my /var/www folder

svn checkout http://svn.magentocommerce.com/source/branches/1.5

This created a Folder called /var/www/1.5

I Turned off Apache

Renamed /var/www/magento to /var/www/magento1.4

renamed /var/www/1.5 to /var/www/magento

FTP Copied to local magento/1.4  and local magento.1.5 folders both sets of :

/var/www/.../media

/var/www/.../downloader

/var/www/.../app/etc/local.xml

Renamed 1.5 version /media and /downloader to /media1.5 and /downloader1.5

FTP'd up to new (1.5 version Magento) the full 1.4 folders of /media and /downloader

/var/www/.../media/

/var/www/.../downloader/

and installed the nonexistant (assuming a new install is about to happen)

/var/www/.../app/etc/local.xml

Site is displaying as a footer:

Help Us to Keep Magento Healthy - Report All Bugs (ver. 1.5.0.1)

		"If you wish to proceed downloading Magento packages online, please set all Magento folders to have writable permission for the web server user (example: apache) or set up FTP Connection on the Magento Connect Manager Settings tab."

Back to the original Xcache Apc Conflict....

Magento Connect is throwing a Maintenance Flag but not allowing any meaning ful updates.

Will Run a TKLBAM restore to get back to where we were. 

Found a refernce to apc.so in conf.d that should allow a more traditional upgrade (discussed last week).

Don't follow the above path unless you just want to install your data to a fresh install.  Extensions are very problematic, as is Magento Connect and Upgrading, as we can see with all this.

Ok,  Some guidance would be appreciated now.

Magento upgrades are documented to be difficult.  Moving from 1.4.x to 1.5.01 seems exceedingly so because they are changing the "Magento Connect" process...  Most posts I am finding say "don't use" Magento Connect.  I referenced the use of SVN above, but many posts are recomending WGET as shiftwizard does on the final post (as of now) elsewhere in this forum at http://www.turnkeylinux.org/forum/general/20100916/tklpatch-magento

So, it seems that I have indeed installed Subversion to my Magento Directory.  SVN Status tells me that branch 1.5.0.1 is there, but I can see that I am still actually running 1.4.2.0.  Documents about how to use wget to "drop over" Magento to make a good upgrade are more to the point than build from scratch reference to SVN  (this does not seem to be the nature of SVN from my first view however).

What is the best way to "write" the 1.5.0.1 build over my 1.4.2.0 build without starting from scratch.  I like the idea of a simple SVN command (now that I have a Mass of files otherwise clogging my Magento Folder.

But before we go there, is it really correct that every folder has a folder of the same name directly instide it (as in /var/www/magento/app/app... or ...magento/var/var ).  These appear to be the SVN packages "ready for action"..  if so, how to engage them?

I have citations on how to use wget  (see Page 33-34) applying to versions 1.3 magento...   http://www.savantmultimedia.com/print/Magento%201.3%20PHP%20Developer%E2%80%99s%20Guide.pdf 

(however, they then say to issue this command which makes no sense to me -- I would think I want to issue a "overwrite command, but do so only on files that are not part of my working system, but rather just the core"

mv magento/* magento/.htaccess .

followed by chmod o+w...

I expect both routes can work.  I want to maintain my existing "extension" set which I have actually upgraded, so now it is just the Core that I want to overwrite.

Thoughts on how to proceeed?  Is there a one line SVN command that will put this in motion?

thanks in advance for any comments.

L. Arnold

Command that installed SVN to Magento:

http://www.magentocommerce.com/svn

Checkout Command (several "probably want to" statements, but reference to "force" and spedify folder to overwrite that is not in above reference --  needs to be more specific as to what is needed)

http://inchoo.net/ecommerce/magento/installing-magento/

Shell Script to reset ownership on a directory and then commit all changes

http://thedrupalblog.com/shell-script-reset-permissions-and-commit-all-subversion-changes-directory

WGet Instructions:

http://www.magentocommerce.com/wiki/groups/227/installing_magento_via_shell_ssh

A few links to SVN instructions:

http://serverfault.com/questions/150641/how-to-use-ubuntu-lucid-server-as-svn-trac-server

http://artis.imag.fr/~Xavier.Decoret/resources/svn/index.html

I am mainly looking for the "how now" path, but it would be good to get this settled for the longer term as well.

-------

Exploring SVN help now;  probably better than most "linked citations" for what to do it seems.

svn help

svn help export

svn help import

svn help checkout

svn help checkin  (does not exist  -  wanting to undo my Checkout command and use force)

Others wanting to do the same:

http://stackoverflow.com/questions/2058617/magento-subversion-svn-getting-a-development-environment-started

Module Manager - seemingly aimed at the same problem:

http://code.google.com/p/module-manager/

SVN Redmin Upgrade discussion on TKL (20 some steps...)

http://www.turnkeylinux.org/forum/support/20100104/how-upgrade-redmine-087

If properly implemented a 11.2 (or 11.1.5.01 to use Magento Version terms) Magento to get over this hump.  Could definitely do the trick! (though TBO, I was not, as yet, tried to move another install from RC 11 to 11.1 via TKLBAM) -- this actually would move Magento from 1.4.1.1 to 1.4.2.0 in my understanding.

Is magento "Patch Manageable" in the TKL sense?

Well, it worked with a "raw" Magento system taking it up to 1.5.0.1 Magento.  (UPDATE:  Worked on our Full DATA Version Also..)

1. Install Magento VM.
2. Run TKLBAM to get it in  the system (backup for the sake of it)
3. (I would like to try running TKL-BAM restore from Production Machine to get a Test Machine, but I am waiting for a terminally long Backup on the image I want).
4. Open SSH: https://yourserver:12320
5. install Subversion in SSH " apt-get install subversion" from Root Line
6. cd /var/www
7. (then issue the following command in its entirety (forget the link that I am seeing)

   svn export --force http://svn.magentocommerce.com/source/branches/1.5 magento

8. Open Webmin https://yourserver:12321, then go to File Manager
9. find /var/www/magento/var/sessions(delete all sessions)
10. find /var/www/magento/var/cache (delete all cache) - but leave the folder intact
11. cd /var/www
12. chown -R www-data:www-data /var/www/magento  (so that Magento Connect lets you in)
13. Upload to your Magento Root folder the file:  magento-cleanup.php which can be found on magentoconnect

14. open http://yourserver/magento-connect.php

15. back to filemanager (delete or rename magento-connect.php)

16. open http://yourserver   (you need to wait a little bit for the Database to be updated)

So this worked for me on a "newly born" TKL Magento 11.1    (now time to try with our data sets, but the Backup is Still Running over there).

I am optimistic.  This is the Footer (finally) which tells us the Version it is actuall Running!  Magento Connect Manager is also up to date (1.5.0.1)

In Settings, go to Magento Connect and reinstall (via menu dropdown) all listed extensions.

Nice new Interface...  Faster system too. Several bugs disappeared at first viewing.

Reinstall solved the initial crash that occurred prior to reinstall (actually had to force reboot Ubuntu prior to extension reinstall - having tried to open a control panel on one of the extensions)  Works now fine.

Over the Rubicon..  yes!  finally.

The quick way for a fast build (and to remove the overhead of SVN that I describe above)

After you install theTKL Magento Appliance --  proceed in Webshell(:12320)

Go to your www folder (var/www)

then issue the 1.5.1 or 1.6.1 command below

wget http://www.magentocommerce.com/downloads/assets/1.5.1.0/magento-1.5.1.0....

OR

wget http://www.magentocommerce.com/downloads/assets/1.6.1.0/magento-1.6.1.0....

then expand the file (do just one at a time!) so that they upgrade 1.4.2 into the correct folders.

go to

magento/var/cache   .. issue command..  rm -R *

magento/var/session.. issue command.  rm-R *

Then Be sure your Ownership is set up right so that Downloader (and I am sure more) will run

chown -R  www-data:wwwdata /var/www/magento

run magento-cleanup.php or something similar  (search the web for this).

Open the Magento Site.  Takes a while but should upgrade you to a Fresh Build.

sounds like authorize.net has not fully cleared the account but it could be something with your dns etc.  generally api connections take a few tries...  see if you can get a paypal connection. or slme other api to work.  i have not used authorize.net...  sorry for the formatting.  my android wont even capitalize or do a line feed in this text box.

At this point Magento has been upgraded many times since 1.4.2.

Probably best to check for "New References" to the process.

I will note that I have had difficulty doing TKLBAM migrations where an old TKL Backup is restored to a NEW TKL Magento Image.  

Worth some new testing and conversations.