[SOLVED]Eclipse and .svn Android AIDL Problem Август 17, 2009
Posted by russenreaktor in android, develop, eclipse, programming.Tags: android, eclipse
add a comment
Today after adding my android project to svn repository I got
syntax error entries /src/.svn line 1 Android AIDL Problem
After searching internet for solutions I installed subversion plug-in (did not helped) but this…
It is worked for me:
- Delete your project from eclipse (not from disk).
- «File»->»New..»->»Project»->»Android Project»
- in «New Adroid Project»-Dialog selected «create project from existing source» (find your project on HDD)->»Finish»
my .classpath-file
<?xml version="1.0" encoding="UTF-8"?><classpath>
<classpathentry kind="src" path="src"/>
<classpathentry kind="src" path="gen"/>
<classpathentry kind="con" path="com.android.ide.eclipse.adt.ANDROID_FRAMEWORK"/>
<classpathentry kind="output" path="bin"/></classpath>
I got an error saying «This client is too old to work with working copy ‘…’ «. How can I fix it without upgrading Subversion? Май 6, 2009
Posted by russenreaktor in develop.add a comment
«Sometimes the working copy metadata format changes incompatibly between minor releases. For example, say you have a working copy created with Subversion 1.4.4, but one day you decide to try out Subversion 1.5.0. Afterwards, you attempt to switch back to 1.4.4, but it doesn’t work — it just gives the above error.
This is because 1.5.0 upgraded your working copy format to support some new features (in this case, changelists, the keep-local flag, and variable-depth directories). Although 1.4.4 doesn’t know anything about these new features, it can at least recognize that the working copy format has been upgraded to something higher than it can handle.
1.5.0 upgraded the working copy for a good reason: it realizes that 1.4.4 does not know about these new features, and that if 1.4.4 were to meddle with the working copy metadata now, important information might be lost, possibly causing corruption (see issue #2961, for example).
But this automatic upgrade behavior can be annoying, if you just want to try out a new release of Subversion without installing it permanently. For this reason, we distribute a script that can downgrade working copies when doing so is safe:
http://svn.collab.net/repos/svn/trunk/tools/client-side/change-svn-wc-format.py
Run that script with the «–help» option to see how to use it. As future versions of Subversion are released, we will try to keep this FAQ entry up-to-date with potential downgrade scenarios and their implications.» subversion.tigris.org
How To Install Firebug In Browsers Other Than Firefox Март 16, 2009
Posted by russenreaktor in develop.add a comment
«Firebug Lite makes it possible to put Firebug into any web browser! You should be able to use it with Internet Explorer, Opera, Safari, Chrome, and any other browser that supports JavaScript. Firebug Lite is written in JavaScript, so you can include it on a webpage with the following code:
Or even better you can use this bookmarklet:
Firebug Lite» makeuseof.com
Learn CSS Positioning in Ten Steps Март 12, 2009
Posted by russenreaktor in develop.add a comment
«This tutorial examines the different layout properties available in CSS: position:static, position:relative, position:absolute, and float.» barelyfitz.com
Useful XUL links Январь 12, 2009
Posted by russenreaktor in develop.add a comment
- Eclipse Plugin http://eclipsexul.sourceforge.net/update-site
- Firefox Plugins
- Extension Developer http://ted.mielczarek.org/code/mozilla/extensiondev/ https://addons.mozilla.org/en-US/firefox/addon/7434
- Chrome List http://www.gijsk.com/mozilla/chromelist/ https://addons.mozilla.org/en-US/firefox/addon/4453
MySQL migration: MyISAM to InnoDB Декабрь 30, 2008
Posted by russenreaktor in develop.add a comment
«Change TYPE=ISAM to TYPE=INNODB
The second step is to edit the db1.sql dump file with a text editor and change the table type to InnoDB. Make of copy of the dump file before you edit it in case you need to restore it later. Here is a sample table definition:
CREATE TABLE audience_def (
AUDIENCE_NO int(10) unsigned NOT NULL auto_increment,
DESCRIPTION varchar(150) default NULL,
STATUS varchar(10) default NULL,
PRIMARY KEY (AUDIENCE_NO)
) TYPE=ISAM;
For each table definition in the dump file, change the TYPE=ISAM to TYPE=INNODB. If your database is very large, the dump file may be too large to fit in your text editor. If so, you can use a batch editor like sed to make the changes.» linux.com
SOLVED: tortoise(svn) + putty(ssh) + pageant = no password input needed Октябрь 29, 2008
Posted by russenreaktor in develop, linux, windows.Tags: linux, pageant, putty, ssh, svn, tortoise, windows
add a comment
«Lets do this step by step:
- login to your server
- type: ssh-keygen -b 1024 -t dsa -N passphrase -f mykey
- change «passphrase» to a secret keyword only you know
- type: ls -l mykey*
We just created a SSH2 DSA key with 1024 bit keyphrase. You will see two files. One named «mykey» and one named «mykey.pub». As you might guess, the .pub file is the public key file, the other is the private one. Next create a user on the server with a home directory:
- type: useradd -m myuser
You will have a directory under /home with the name «myuser», create a new directory in «myuser» called «.ssh»:
- type: cd /home/myuser
- type: mkdir .ssh
Then go to the directory where you created your keys and copy the public key to the .ssh userfolder with the following command:
- type: cp mykey.pub /home/myuser/.ssh/authorized_keys
or if you already have some keys in place
- type: cat mykey.pub >> /home/myuser/.ssh/authorized_keys
Please pay attention to the filename, it really must be «authorized_keys». In some old OpenSSH implementations, it was «authorized_keys2″. Now download the private key file to your client computer. Remember, the file was «mykey»
————————————————————
SSH key generation and connection check (client)
————————————————————
Grab the tools we need for doing SSH on windows on this site:
http://www.chiark.greenend.org.uk/~sgtatham/putty/
Just go to the download section and get «Putty», «Plink», «Pageant» and «Puttygen»
In order to use the private key we get from the server, we have to convert it to a putty format. This is because the private key file format is not specified by some standard body. To do this we simple open «puttygen» and open the «conversions» menu and chose «Import Key». Then browse to your file «mykey» which you got from the server enter your provided passphrase upon creation of the key. Finally click «Save private key» and save the file as «mykey.PPK» somewhere on disk.
Now we are ready to use this key for the first time to test the connection. In order to do this, we open the program «putty» and create a new session like this:
Session->HostName: Hostname or IP Adress of your server
Session->Protocol: SSH
Session->Saved Sessions: MyConnection
SSH->Prefered SSH Protocol version: 2
SSH->Auth->Private Key file for auth: $PATH$\mykey.PKK (replace $PATH$ with real path to the mykey.PKK file)
Then go back to Session tab and hit «save» button. You will see «MyConnection» in the list of available connections.» tortoisesvn.net
