First, make sure you have the prerequisites installed:

yum groupinstall 'Development Tools' 
yum groupinstall 'Development Libraries' # Ignore for CentOS 6.5
yum install fribidi-devel gtk+ yasm webkitgtk-devel gstreamer-devel gstreamer-plugins-base-devel bzip2-devel
yum install libgudev1-devel libnotify-devel libass-devel libsamplerate-devel libogg-devel libtheora-devel libvorbis-devel

Checkout the latest version from SVN Download the latest version from their website, build it without GTK support:

cd /usr/local/src/
wget -O HandBrake-0.9.9.tar.bz2 http://handbrake.fr/rotation.php?file=HandBrake-0.9.9.tar.bz2
tar -jxvf HandBrake-0.9.9.tar.bz2
cd HandBrake-0.9.9
./configure --launch --disable-gtk
cp build/HandBrakeCLI /usr/local/bin/

The –launch argument will start HandBrake’s gmake script that will download the other libraries it needs, compile them, and then statically link them to the HandBrakeCLI executable it builds. This can take a little while, depending on your available resources, and it requires an internet connection. If you get build errors complaining about missing *.h files, make sure you have the lib*-devel installed for that missing header.

Note: The trunk will likely be updated soon-ish, so if you’re looking for 0.9.9 specifically you can get the source from SourceForge.

Edit: Looks like they removed public access to SVN.

The post Install HandBrake CLI v0.9.9 on CentOS 6.4 appeared first on DanDev.com.

So, you want to run python code in PHP, eh? Why you might ask? Well, I’m not quite sure. I haven’t run in to a use case for it myself, but I can see where you might need to do some heavy-duty maths or maybe there is a python library that you require for some custom algorithm or something.

Good news! There is a PECL library you can use for this task: http://pecl.php.net/package/python
Unfortunately, it hasn’t been updated in over 4 years at the time of this writing and was in alpha at the time of the last release.
However! The maintainer appears to still be working on the package, but over a GitHub: https://github.com/jparise/php-python
Unfortunately, it still doesn’t compile on PHP 5.4 (in Fedora at least)
However! I got it to work with some minor tweaks.

Here is the process that works with the current PHP version (5.4.8 at the time of this writing) linking to python 2.7:

Install build tools and minimum deps:

yum groupinstall "Development Tools"
yum install php-common php-pear php-devel python python-devel wget

Get a copy of the latest version of php-python:

git clone https://github.com/jparise/php-python.git php-python

Apply the patch to fix C syntax errors. Note that this patch is likely to be broken and/or not necessary some time in the future when php-python is updated. But the changes are simple so you can apply them manually if they are still needed in future versions. Gist also available here: https://gist.github.com/drener/7149541

wget http://www.dandev.com/other/post_content/php-python_20121112.diff
patch -p0 < php-python_20121112.diff

Build the module

cd php-python
phpize
./configure
make
make install

After this is complete you need to edit your php.ini to enable the new module. Add a line like this:

extension=python.so

Once php.ini is updated you should be able to see the "python" module listed in the "php -m" modules list, and you should be able to use the python functions. Restart Apache if you are using mod_php to load the updated php.ini file. The examples folder on GitHub has some code you can use to see the Python features in action: https://github.com/jparise/php-python/tree/master/examples

Good luck!

The post Compiling php-python on Fedora Linux appeared first on DanDev.com.

Oct  2 21:12:05 phptest sshd[31998]: error: buffer_get_ret: trying to get more bytes 4 than in buffer 0
Oct  2 21:12:05 phptest sshd[31998]: fatal: buffer_get_int: buffer error

Check your public key in ~/.ssh/authorized_keys or ~/.ssh/authorized_keys2 in a text editor and make sure each key is on one line. The prefix “ssh-rsa” followed by a space and then your key should all be on one line, and you might also have a comment after that describing the key. If your key spans multiple lines you will often get an error similar to the above message in your /var/log/secure log file.

You usually only see this when you’re trying to connect using key-based authentication. The error is caused by extra newlines in the authorized_keys list. When copying a public key out of PuttyGen(or similar key-generation software), because the key spans multiple lines, you can end up with extra newlines in the text when it gets copied to the clipboard.

The post SSHD Error: buffer_get_ret: trying to get more bytes 4 than in buffer 0 appeared first on DanDev.com.

1. (Re)start the Windows Installer service
   1. Right-click on Computer
   2. Click Manage
   3. Expand Services and Applications
   4. Select Services
   5. Scroll down to “Windows Installer”
   6. Right-click or double-click on it and make sure it is started and NOT disabled
2. Run “sfc /scannow” from a command prompt as Administrator
   1. Should see something like: windows resource protection found some corrupt files but was unable to fix them
      1. Check the log to see if the problem is a corrupt file such as “msi.dll”
         1. Do this by searching for “cannot repair”
      2. If that is the case you can restore this file from the Windows DVD by:
         1. Insert the Windows DVD in the drive, cancel the autorun if it pops up
         2. Open 7-zip and browse to “install.wim” in the DVD:\Sources folder (open it)
         3. Inside you will find numbered folders corresponding to the windows version, open yours:

            1=Home Basic

            2=Home Premium

            3=Professional

            4=Ultimate

         4. Browse to the folder for the version you have installed, and you can copy/extract the file(s) you need. In my case I needed “msi.dll” in the #\Windows\System32 folder
         5. Note that if you are restoring a sensitive file such as this that you have to take ownership of the original file to rename/remove it before you can restore this file from the DVD, and ideally set the restored file back to the original owner and permission.
         6. Also note that the “msi.dll” file is owned by “TrustedInstaller”, so if you are getting a security error you need to take ownership of the file to replace it and then restore TrustedInstaller as the owner. If you can’t find it when you “check” the name use “NT SERVICE\TrustedInstaller”
3. Restore an earlier restore point(not verified to work but try it..)
4. Run the repair option from the installer DVD
5. Reinstall Windows

Hope this helps someone.

The post Windows Installer has stopped working appeared first on DanDev.com.