<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>coffeecoders.de &#187; trac</title>
	<atom:link href="http://coffeecoders.de/tag/trac/feed/" rel="self" type="application/rss+xml" />
	<link>http://coffeecoders.de</link>
	<description>professional devs at work</description>
	<lastBuildDate>Thu, 11 Feb 2010 10:35:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>trac: upgrading trac with easy_install fails with &#8220;unexpected HTML page found&#8221;</title>
		<link>http://coffeecoders.de/2009/08/trac-upgrading-trac-with-easy_install-fails-with-unexpected-html-page-found/</link>
		<comments>http://coffeecoders.de/2009/08/trac-upgrading-trac-with-easy_install-fails-with-unexpected-html-page-found/#comments</comments>
		<pubDate>Sat, 22 Aug 2009 10:55:09 +0000</pubDate>
		<dc:creator>stevie</dc:creator>
				<category><![CDATA[common]]></category>
		<category><![CDATA[administration]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[trac]]></category>

		<guid isPermaLink="false">http://coffeecoders.de/?p=240</guid>
		<description><![CDATA[When installing or upgrading trac on a Debian-like linux machine you might want to use the easy approach of the python setuptools. Trac can be installed or upgraded by using: easy_install http://svn.edgewall.org/repos/trac/branches/0.11-stable Since the release of Subversion 1.5 the version of easy_install included in the Debian repository ran into a compatibility issue. Instead of working [...]]]></description>
			<content:encoded><![CDATA[<p>When installing or upgrading trac on a Debian-like linux machine you might want to use the easy approach of the python setuptools. Trac can be installed or upgraded by using:</p>
<p><code>easy_install http://svn.edgewall.org/repos/trac/branches/0.11-stable</code></p>
<p>Since the release of Subversion 1.5 the version of easy_install included in the Debian repository ran into a compatibility issue. <span id="more-240"></span>Instead of working as expected it always complained:</p>
<p><code>error: Unexpected HTML page found at http://svn.edgewall.org/repos/trac/branches/0.11-stable</code></p>
<p>The problem seems to be that the SVN-Web-Output generated by Subversion 1.5+ is not being understanded by setuptools. In the <a href="http://trac-hacks.org/ticket/5512">issue tracker</a> for the trac-plugin-project <a href="http://www.trac-hacks.org">trac-hacks.org</a> I found the easiest way to solve this problem. You will use the setuptools to update itself and then you won&#8217;t have problems anymore:</p>
<p><code>easy_install -U setuptools</code></p>
<p>PS: This problem also occured when trying to install plugins from trac-hacks.org since they also use SVN 1.5+.</p>
]]></content:encoded>
			<wfw:commentRss>http://coffeecoders.de/2009/08/trac-upgrading-trac-with-easy_install-fails-with-unexpected-html-page-found/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>trac: Solving sqlite-issues when upgrading from Debian etch to lenny</title>
		<link>http://coffeecoders.de/2009/02/trac-solving-sqlite-issues-when-upgrading-from-debian-etch-to-lenny/</link>
		<comments>http://coffeecoders.de/2009/02/trac-solving-sqlite-issues-when-upgrading-from-debian-etch-to-lenny/#comments</comments>
		<pubDate>Mon, 09 Feb 2009 14:06:41 +0000</pubDate>
		<dc:creator>stevie</dc:creator>
				<category><![CDATA[common]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[python]]></category>
		<category><![CDATA[trac]]></category>

		<guid isPermaLink="false">http://coffeecoders.de/?p=128</guid>
		<description><![CDATA[On my dev-server I had to upgrade to the newer version of debian lenny (which will be released as stable version this week). The upgrade went fine but after it was finished trac (0.11.2.1 ) refused to start, throwing the error message DatabaseError: file is encrypted or is not a database According to the ticket [...]]]></description>
			<content:encoded><![CDATA[<p>On my dev-server I had to upgrade to the newer version of debian lenny (which will be released as stable version this week).</p>
<p>The upgrade went fine but after it was finished <a href="http://trac.edgewall.org/">trac (0.11.2.1 )</a> refused to start, throwing the error message</p>
<blockquote><p>DatabaseError: file is encrypted or is not a database</p></blockquote>
<p><span id="more-128"></span>According to the <a href="http://trac.edgewall.org/ticket/2585">ticket system of trac</a> the problem is the wrong version of sqlite which is used by trac. Sadly all my efforts to make the database useable again failed with the error message above.</p>
<p>After some research I discovered another way to let trac use the default sqlite3 but keeping my data alive. <a href="http://pacopablo.com/irclogs/2008/10/21">This chatlog</a> states a simple way to convert your sqlite2 database to the newer sqlite3-format. Here is a quick walkthrough:</p>
<ol>
<li>Install the packages sqlite (v2) and sqlite3 (guess the version <img src='http://coffeecoders.de/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  )

<div class="wp_codebox_msgheader"><span class="right"><sup><a href="http://www.ericbess.com/ericblog/2008/03/03/wp-codebox/#examples" target="_blank" title="WP-CodeBox HowTo?"><span style="color: #99cc00">?</span></a></sup></span><span class="left"><a href="javascript:;" onclick="javascript:showCodeTxt('p128code3'); return false;">View Code</a> BASH</span><div class="codebox_clear"></div></div><div class="wp_codebox"><table><tr id="p1283"><td class="code" id="p128code3"><pre class="bash" style="font-family:monospace;"><span style="color: #c20cb9; font-weight: bold;">aptitude</span> <span style="color: #c20cb9; font-weight: bold;">install</span> sqlite sqlite3</pre></td></tr></table></div>

</li>
<li>Dump the old database and convert it to sqlite3

<div class="wp_codebox_msgheader"><span class="right"><sup><a href="http://www.ericbess.com/ericblog/2008/03/03/wp-codebox/#examples" target="_blank" title="WP-CodeBox HowTo?"><span style="color: #99cc00">?</span></a></sup></span><span class="left"><a href="javascript:;" onclick="javascript:showCodeTxt('p128code4'); return false;">View Code</a> BASH</span><div class="codebox_clear"></div></div><div class="wp_codebox"><table><tr id="p1284"><td class="code" id="p128code4"><pre class="bash" style="font-family:monospace;"><span style="color: #7a0874; font-weight: bold;">cd</span> <span style="color: #000000; font-weight: bold;">/</span>path<span style="color: #000000; font-weight: bold;">/</span>to<span style="color: #000000; font-weight: bold;">/</span>trac-repos
<span style="color: #7a0874; font-weight: bold;">cd</span> db
<span style="color: #c20cb9; font-weight: bold;">mv</span> trac.db trac.db.old-sqlite2
sqlite trac.db.old-sqlite2 .dump <span style="color: #000000; font-weight: bold;">|</span> sqlite3 trac.db
<span style="color: #c20cb9; font-weight: bold;">chown</span> www-data:www-data trac.db
<span style="color: #000000; font-weight: bold;">/</span>etc<span style="color: #000000; font-weight: bold;">/</span>init.d<span style="color: #000000; font-weight: bold;">/</span>apache2 restart</pre></td></tr></table></div>

</li>
</ol>
<p>And you&#8217;re done. The old database is now named <em>trac.db.old-sqlite2</em> in case you need it for whatever reason. The new one is named with the default name <em>trac.db</em> so trac will use this one if not specified otherwise in <em>conf/trac.ini</em>.</p>
<p>I hope this tip saves you from some worries after upgrading to Debian Lenny. Keep on coding!</p>
]]></content:encoded>
			<wfw:commentRss>http://coffeecoders.de/2009/02/trac-solving-sqlite-issues-when-upgrading-from-debian-etch-to-lenny/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
