<?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>Martin Pitt &#187; launchpad</title>
	<atom:link href="http://www.piware.de/tag/launchpad/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.piware.de</link>
	<description>addicted to Ubuntu development</description>
	<lastBuildDate>Tue, 07 Feb 2012 19:53:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
		<item>
		<title>Apport crash processing now enabled for Maverick</title>
		<link>http://www.piware.de/2010/07/apport-crash-processing-now-enabled-for-maverick/</link>
		<comments>http://www.piware.de/2010/07/apport-crash-processing-now-enabled-for-maverick/#comments</comments>
		<pubDate>Mon, 05 Jul 2010 13:46:06 +0000</pubDate>
		<dc:creator>pitti</dc:creator>
				<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[announcement]]></category>
		<category><![CDATA[Apport]]></category>
		<category><![CDATA[bugs]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[launchpad]]></category>
		<category><![CDATA[QA]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://www.piware.de/?p=346</guid>
		<description><![CDATA[The Debian import freeze is settled, the first rush of major changes went into Maverick, and the dust now has settled a bit. Thus it&#8217;s time to turn back some attention to crashes and quality in general. This morning I created maverick chroots for the Apport retracers, and they are currently processing the backlog. I [...]]]></description>
			<content:encoded><![CDATA[<p>The Debian import freeze is settled, the first rush of major changes went into Maverick, and the dust now has settled a bit. Thus it&#8217;s time to turn back some attention to crashes and quality in general.</p>
<p>This morning I created maverick chroots for the <a href="https://wiki.ubuntu.com/Apport#Launchpad-based auto-retracer">Apport retracers</a>, and they are currently processing the backlog. I also uploaded a new Apport package which now enables crash reporting by default again.</p>
<p>Happy segfaulting!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.piware.de/2010/07/apport-crash-processing-now-enabled-for-maverick/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>lpshell &#8211; convenient launchpadlib script</title>
		<link>http://www.piware.de/2010/01/lpshell-convenient-launchpadlib-script/</link>
		<comments>http://www.piware.de/2010/01/lpshell-convenient-launchpadlib-script/#comments</comments>
		<pubDate>Tue, 12 Jan 2010 21:48:01 +0000</pubDate>
		<dc:creator>pitti</dc:creator>
				<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[launchpad]]></category>
		<category><![CDATA[python]]></category>
		<category><![CDATA[script]]></category>

		<guid isPermaLink="false">http://www.piware.de/?p=270</guid>
		<description><![CDATA[These days I often use launchpadlib in my projects for scripting access/modifications in Launchpad. While launchpadlib has quite a good API documentation, this only covers the method calls, not the attributes or collections. So it often takes some poking and trying until you figure out how to access/change things. I found myself typing the same [...]]]></description>
			<content:encoded><![CDATA[<p>These days I often use <a href="https://launchpad.net/launchpadlib">launchpadlib</a> in my projects for scripting access/modifications in Launchpad. While launchpadlib has quite a good <a href="https://launchpad.net/+apidoc/">API documentation</a>, this only covers the method calls, not the attributes or collections. So it often takes some poking and trying until you figure out how to access/change things.</p>
<p>I found myself typing the same things over and over, so I finally wrote a little script called <code>lpshell</code>:</p>
<blockquote><pre>
#!/usr/bin/python -i
import code, os, sys
from launchpadlib.launchpad import Launchpad, STAGING_SERVICE_ROOT, EDGE_SERVICE_ROOT
lp = Launchpad.login_with('test', STAGING_SERVICE_ROOT)
</pre>
</blockquote>
<p>This logs into Launchpad and gives you an interactive Python shell with an &#8220;lp&#8221; object:</p>
<blockquote><pre>
$ lpshell
>>> lp.bugs[439482].duplicate_of
<bug at https://api.staging.launchpad.net/beta/bugs/432598>
</pre>
</blockquote>
<p><strong>Update:</strong> I committed this to ubuntu-dev-tools now, renamed to <code>lp-shell</code> for consistency with the other <code>lp-*</code> commands.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.piware.de/2010/01/lpshell-convenient-launchpadlib-script/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Automated release tarball upload to Launchpad</title>
		<link>http://www.piware.de/2009/09/automated-release-tarball-upload-to-launchpad/</link>
		<comments>http://www.piware.de/2009/09/automated-release-tarball-upload-to-launchpad/#comments</comments>
		<pubDate>Sat, 05 Sep 2009 14:50:57 +0000</pubDate>
		<dc:creator>pitti</dc:creator>
				<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[launchpad]]></category>
		<category><![CDATA[release]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[tarball]]></category>

		<guid isPermaLink="false">http://martinpitt.wordpress.com/?p=99</guid>
		<description><![CDATA[I often do upstream releases of my upstream projects that I do on Launchpad, mostly for Apport and jockey. But doing this has been quite tedious until now: You have to go to the project page, pick the series (usually &#8220;trunk&#8221;), create a new release, create a new milestone along the way, then go to [...]]]></description>
			<content:encoded><![CDATA[<p>I often do upstream releases of my upstream projects that I do on Launchpad, mostly for <a href="https://launchpad.net/apport">Apport</a> and <a href="https://launchpad.net/jockey">jockey</a>. But doing this has been quite tedious until now: You have to go to the project page, pick the series (usually &#8220;trunk&#8221;), create a new release, create a new milestone along the way, then go to &#8220;add download file&#8221;, and upload your .tar.gz and .tar.gz.asc.</p>
<p>Because this is rather inconvenient, I don&#8217;t do as many upstream releases as I should. But thanks to our tireless launchpadlib developers it is now possible to automate all that, so I wrote a new script <a href="http://bazaar.launchpad.net/%7Eubuntu-dev/ubuntu-dev-tools/trunk/annotate/head%3A/lp-project-upload">lp-project-upload</a> which does all that in a simple command:</p>
<pre>
  $ lp-project-upload apport 1.8.2 apport-1.8.2.tar.gz
  Release 1.8.2 could not be found for project. Create it? (Y/n) y
 </pre>
<p>The script is based on Brad Crittenden&#8217;s <a href="http://blog.launchpad.net/api/recipe-for-uploading-files-via-the-api">recipe for uploading project files</a>, and I added the creation of milestones and releases.</p>
<p>The script is contained in current Karmic&#8217;s <code>ubuntu-dev-tools</code> package now. Enjoy, and of course feel free to extend it for changelogs, release notes, etc.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.piware.de/2009/09/automated-release-tarball-upload-to-launchpad/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
	</channel>
</rss>

