Heat about to take over

LeBron James driving to the basket over the tower of Roy Hibbert.

Interesting couple of weeks for Miami Heat – Indiana Pacers back to back match up over the weeks. They have been like two tales of the same movie. From the initial dominance of the team and then cooling off enough to finish the game loosing.

LeBron however was a story that started on the previous game wtih an accident on her ankle and a gametime decision whenever he would play or not. Of course many people knew he wouldn’t miss this game at all.

The game was excellent specially when you analyze how the Miami Heat came about, as the Pacers started dominating the tempo of the game.

Even if Miami was pick pocketing and generating turnovers like crazy, the real battle was at the foul chart. When Hibbert reached it’s 4th foul and got him out of the game, he was able to leave the basket and Flash really took advantage of it. The same goes to Bosh who step up and embraced his role and was able to outsmart Hibbert and take him out of the basket.

The most important part is that Miami is now breathing on the neck of the Pacers and could start the takeover of the east. With Oklahoma City doing the same on the west coast. The Thunder just much on the San Antonio Spurs and the only other team hanging at the top is the Blazers.

Advertisement

Update on the OpenUpgrade migration

After some detailed review of the logs and re-watching the conference on OpenUpgrade I was able to identify key things about the way the migration take place:

1. Carefully reviewing the error message.
2. Understand the script is not bulletproof and seems to preffer debug than skipping errors.
3. Keep your SQL hat at arm reach.

I was able to run openupgrade with some success but there was a lot of missed shots and even this one is still not a hit yet, but is getting closer.

The Main error had to do with two tables, res_users which hold the application users, and res_company that holds the clients.  We can first look at error log:

2013-12-17 06:49:50,310 28794 ERROR astro_migrated openerp.osv.orm: Can’t find field ‘context_tz’ in the following view parts composing the view of object model ‘res.users’:

 * res.users.form

 

Either you wrongly customized this view, or some modules bringing those views are not compatible with your current data model

2013-12-17 06:49:50,311 28794 ERROR astro_migrated openerp.osv.orm: Can’t find field ‘menu_tips’ in the following view parts composing the view of object model ‘res.users’:

* res.users.form

Either you wrongly customized this view, or some modules bringing those views are not compatible with your current data model

2013-12-17 06:49:50,312 28794 ERROR astro_migrated openerp.osv.orm: Can’t find field ‘context_lang’ in the following view parts composing the view of object model ‘res.users’:

 * res.users.form

 

Either you wrongly customized this view, or some modules bringing those views are not compatible with your current data mod

The other table is the one related with the fields property_reserve_and_surplus_account, and the security_lead. for the res.company table.

3699 ERROR astro_migrated openerp.osv.orm: Can’t find field ‘property_reserve_and_surplus_account’ in the following view parts composing the view of object model ‘res.company’:
* res.company.form.inherit

3699 ERROR astro_migrated openerp.osv.orm: Can’t find field ‘security_lead’ in the following view parts composing the view of object model ‘res.company’:
* res.company.mrp.config

The next step is to review the way the error as I login to the migrated database shows up on the screen and the actual error that sends:

ProgrammingError: column res_users.alias_id does not exist
LINE 1: …CT res_users.”menu_id”,res_users.”gmail_password”,res_users….
                                                                               ^

This error basically tells me that the res_users is wrong due to some missing information regarding the column res_user.alias_id. I still need to crack this one, but fortunately this will help me solve the rest and would be able to finally get the migration concluded.

I can almost be certain this has to do with the database and that there have been issues related with SQL queries.

Contributing to OpenERP translated documentation

So this is my official contribution to the project, I’ve decided to spend some time translating the strings from the OpenERP documentation. The OpenERP book holds a good amount of information about what the history, development and goals of the OpenERP project. I also appreciate the way this book have been put together, as opposed to spend time describing each screen and talking on how to use it. This book spend time looking at the tool as a business people, accentuating on the business goal. For example, titles like “How to better manage your books”, as opposed to a more boring “Accounting Module”.

The localization in Spanish have been lagging greatly mainly because the way to contribute is a bit obscure. I found out the system itself is not obscure since they use a standard Launchpad-Open Source translation tool based on PO files. The way the po are managed online is very similar to the Pootle application.

The next step is to become legit on the Launchpad application, which allow my user to get fully integrated on the OpenERP teams. I added myself to the OpenERP-Mexico group, and the OpenERP-Documentation group.

The Spanish localization is located under the 7.0 branch, where you click on translations. And are presented with a table of different languages and the progress for each language. There you can select the preferred language and then are presented with the different type of localization projects including the book, contents, contribute, faqs, index, install, legal, odoo, usability-book, etc.

My main goal is the book one which listed around 6544 with 6453 untranslated and 305 for review. You can check the project here.

One thing that was noticed earlier today was that I need to be part of the Spanish team in order to get my reviews and comments approved. You can see me already on the team either as pending or if this post is rather old, I will hopefully be approved.

Graph showing the different openerp project for the spanish locale.

Blueberry Pie

Thinking about having blueberry pie for Xmas. I talked to my mom about plans to have it done with this stuffing since here in Mexico is a bit hard to come across a massive bag of blueberries.

Installing OpenERP 6.1 and 7.0 on the same Linux Box

After a few rants and raves thrown at the #openobject channel on IRC about why Ubuntu is not the only Linux in time. I was able to get solved some of the issues involved with installing different OpenERP instances and also remember some of the steps that were required to install a general OpenERP system.

First remember that most of the packages will come from PIP but in case some of the packages got issues is important to rely on your distro packages.

The first pain point could be setting up the postgresql database. I experience some issues trying to run postgresql 9.0 and downgrade to 8.5. So first lesson learned is that both database work fine with OpenERP.

Another point is to watch out for the psycopg2 module, in my environment it was best to get it from my repo, since I use mandriva, I need to do:

urpmi python-psycopg2 python-imaging python-pychart

This allowed me to get the openerp-server server running. Another key thing here is to remember to open different ports, so is important to open like this:

openerp6/openerp-server.py –xmlrpc-port=1800
openerp7/openerp-server.py –xmlrpc-port=8059

This is important to get the correct applications running on the different ports. You will end up with localhost:1800 for 6.1 and localhost:8059 for 7.0.

One important thing regarding postgresql is that I wasn’t able to start the services as I should so instead I have to run the server manually doing the following command:

postgres -D /var/lib/pgsql/data/

Following the tutorial on installing openerp v6.1 on ubuntu, I should be able to get the services started from init.d.