<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Lightweight Debian Archive Scripts</title>
	<atom:link href="http://www.mattb.net.nz/blog/2005/10/26/lightweight-debian-archive-scripts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mattb.net.nz/blog/2005/10/26/lightweight-debian-archive-scripts/</link>
	<description>Matt Browns thoughts on Life, Linux and lots of other things...</description>
	<pubDate>Tue, 02 Dec 2008 22:11:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Steve Kemp</title>
		<link>http://www.mattb.net.nz/blog/2005/10/26/lightweight-debian-archive-scripts/#comment-7</link>
		<dc:creator>Steve Kemp</dc:creator>
		<pubDate>Wed, 26 Oct 2005 19:46:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattb.net.nz/blog/?p=23#comment-7</guid>
		<description>Thanks a lot for sharing those - they're almost exactly what I was looking for!

The scanning and building I can use as-is, although what I want to do with the built packages differs so I'll have to code that part up myself.</description>
		<content:encoded><![CDATA[<p>Thanks a lot for sharing those - they&#8217;re almost exactly what I was looking for!</p>
<p>The scanning and building I can use as-is, although what I want to do with the built packages differs so I&#8217;ll have to code that part up myself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Goswin von Brederlow</title>
		<link>http://www.mattb.net.nz/blog/2005/10/26/lightweight-debian-archive-scripts/#comment-6</link>
		<dc:creator>Goswin von Brederlow</dc:creator>
		<pubDate>Wed, 26 Oct 2005 16:15:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattb.net.nz/blog/?p=23#comment-6</guid>
		<description>For the archive I realy suggest using reprepro. It does not include incoming processing but everything else. You just point it to a changes file and tell it what distribution to put it under and the rest is automatic, including Release.gpg files.

Reprepro can also pull in sources and debs from multiple sources and mix them all up (or keep them in seperate distributions). With that you can easily mix in your local partial debian mirror next to the local archive all with the one software.

The configuration is trivial, a small RFC822 text file for what the repository carries and another smaller one for source to fetch from.


Once you have the archive I suggest running wanna-build, buildd and sbuild. If you want to test out packages before uploading them it is best to test them on the same build system. If w-b+buildd is too complicated for you I still have the amd64 archive scripts on alioth which do a simpler job in shell.

MfG
   Goswin</description>
		<content:encoded><![CDATA[<p>For the archive I realy suggest using reprepro. It does not include incoming processing but everything else. You just point it to a changes file and tell it what distribution to put it under and the rest is automatic, including Release.gpg files.</p>
<p>Reprepro can also pull in sources and debs from multiple sources and mix them all up (or keep them in seperate distributions). With that you can easily mix in your local partial debian mirror next to the local archive all with the one software.</p>
<p>The configuration is trivial, a small RFC822 text file for what the repository carries and another smaller one for source to fetch from.</p>
<p>Once you have the archive I suggest running wanna-build, buildd and sbuild. If you want to test out packages before uploading them it is best to test them on the same build system. If w-b+buildd is too complicated for you I still have the amd64 archive scripts on alioth which do a simpler job in shell.</p>
<p>MfG<br />
   Goswin</p>
]]></content:encoded>
	</item>
</channel>
</rss>
