Reprepro - Revision history

imported_>amigadave: Category:Software

2010-02-11T12:28:04Z

← Older revision		Revision as of 12:28, 11 February 2010
Line 1:		Line 1:
	[http://mirrorer.alioth.debian.org/ reprepro] is a tool to create and manage debian package repositories. This page documents its installation on stage.maemo.org, the Maemo repository server. Note that this is not the tool that maemo.org uses.		[http://mirrorer.alioth.debian.org/ reprepro] is a tool to create and manage debian package repositories. This page documents its installation on stage.maemo.org, the Maemo repository server. Note that this is not the tool that maemo.org uses.


	''' Preparation '''		''' Preparation '''
Line 84:		Line 83:
	http://alioth.debian.org/scm/viewvc.php/checkout/mirrorer/docs/manual.html?revision=HEAD&root=mirrorer<br>		http://alioth.debian.org/scm/viewvc.php/checkout/mirrorer/docs/manual.html?revision=HEAD&root=mirrorer<br>
	http://www.debian-administration.org/articles/286<br>		http://www.debian-administration.org/articles/286<br>

			[[Category:Software]]

imported_>jeremiah at 22:36, 24 January 2010

2010-01-24T22:36:05Z

← Older revision		Revision as of 22:36, 24 January 2010
Line 1:		Line 1:
	[http://mirrorer.alioth.debian.org/ reprepro] is a tool to create and manage debian package repositories. This page documents its installation on stage.maemo.org, the Maemo repository server.		[http://mirrorer.alioth.debian.org/ reprepro] is a tool to create and manage debian package repositories. This page documents its installation on stage.maemo.org, the Maemo repository server. Note that this is not the tool that maemo.org uses.

imported_>jeremiah at 01:54, 30 December 2009

2009-12-30T01:54:45Z

← Older revision		Revision as of 01:54, 30 December 2009
Line 14:		Line 14:
	inoticoming and reprepro are maintained and written by the same person.		inoticoming and reprepro are maintained and written by the same person.

	So, in short, I've installed these packages and their dependencies on the repository server: reprepro, libdb4.2, and inotincoming. ~~I've been advised by Bernhard Link, the author of reprepro, not to instal libdb by hand, just let reprepro pull it in as a dependency.)~~		So, in short, I've installed these packages and their dependencies on the repository server: reprepro, libdb4.2, and inotincoming.

	-- Note: explicitly stating libdb4.2 does not make much sense here. aptitude will get whatever version of that crappy lib reprepro needs just fine.		-- Note: explicitly stating libdb4.2 does not make much sense here. aptitude will get whatever version of that crappy lib reprepro needs just fine.

imported_>jeremiah at 01:53, 30 December 2009

2009-12-30T01:53:52Z

← Older revision		Revision as of 01:53, 30 December 2009
Line 14:		Line 14:
	inoticoming and reprepro are maintained and written by the same person.		inoticoming and reprepro are maintained and written by the same person.

	So, in short, I've installed these packages and their dependencies on the repository server: reprepro, libdb4.2, and inotincoming. (I ~~used this command:~~		So, in short, I've installed these packages and their dependencies on the repository server: reprepro, libdb4.2, and inotincoming. I've been advised by Bernhard Link, the author of reprepro, not to instal libdb by hand, just let reprepro pull it in as a dependency.)
	~~aptitude install~~ reprepro ~~inoticoming libdb4~~.2)

	-- Note: explicitly stating libdb4.2 does not make much sense here. aptitude will get whatever version of that crappy lib reprepro needs just fine.		-- Note: explicitly stating libdb4.2 does not make much sense here. aptitude will get whatever version of that crappy lib reprepro needs just fine.

132.230.30.159 at 18:42, 29 December 2009

2009-12-29T18:42:44Z

← Older revision		Revision as of 18:42, 29 December 2009
Line 16:		Line 16:
	So, in short, I've installed these packages and their dependencies on the repository server: reprepro, libdb4.2, and inotincoming. (I used this command:		So, in short, I've installed these packages and their dependencies on the repository server: reprepro, libdb4.2, and inotincoming. (I used this command:
	aptitude install reprepro inoticoming libdb4.2)		aptitude install reprepro inoticoming libdb4.2)

			-- Note: explicitly stating libdb4.2 does not make much sense here. aptitude will get whatever version of that crappy lib reprepro needs just fine.


Line 27:		Line 29:

	Here we're putting the directories under the /srv/ directory so that we can isolate them from the rest of our web content. I have installed nginx to serve the repos because it is small and fast.		Here we're putting the directories under the /srv/ directory so that we can isolate them from the rest of our web content. I have installed nginx to serve the repos because it is small and fast.

			-- Note: If you try this at home, it's usually a good idea to only make one repository and the different projects just different distributions within that. (Unless you have a reason against that, of course).

imported_>jeremiah at 20:13, 28 December 2009

2009-12-28T20:13:11Z

← Older revision		Revision as of 20:13, 28 December 2009
Line 41:		Line 41:
	Components: free non-free		Components: free non-free
	Description: Maemo.org package repositories for diablo		Description: Maemo.org package repositories for diablo
			Log: /var/log/repos/

	''' Logging '''		''' Logging '''

imported_>jeremiah at 20:11, 28 December 2009

2009-12-28T20:11:39Z

← Older revision		Revision as of 20:11, 28 December 2009
Line 41:		Line 41:
	Components: free non-free		Components: free non-free
	Description: Maemo.org package repositories for diablo		Description: Maemo.org package repositories for diablo

			''' Logging '''

			I have tried to make reprepro as verbose as possible, at least to start with. The logs are held in a directory along with the inoticoming logs in /var/log/repos/.

imported_>jeremiah at 19:28, 28 December 2009

2009-12-28T19:28:37Z

← Older revision		Revision as of 19:28, 28 December 2009
Line 48:		Line 48:
	sudo reprepro -Vb . includedeb diablo /home/jeremiah/maemo-perl-packages/libv-perl_0.13-1_all.deb		sudo reprepro -Vb . includedeb diablo /home/jeremiah/maemo-perl-packages/libv-perl_0.13-1_all.deb

	~~Note that I am calling that command from /srv/extras~~ - ~~you'll need to make sure~~ reprepro ~~knows~~ where you are ~~so that it can find~~ the ~~right configuration file for the repo you want to add packages to~~.		The -b flag tells reprepro where its base dir is, here represented by the current dir (.) but you can export a variable with REPREPRO_BASE_DIR. Those type of directories are all configurable with reprepro and well documented in the man pages.

	Here is the output from that command, showing how reprepro created the needed directories and also added a tracking database as well as exported indexes;		Here is the output from that command, showing how reprepro created the needed directories and also added a tracking database as well as exported indexes;

imported_>jeremiah at 18:10, 28 December 2009

2009-12-28T18:10:03Z

← Older revision		Revision as of 18:10, 28 December 2009
Line 4:		Line 4:
	''' Preparation '''		''' Preparation '''

	Before setting up the repositories, it ~~is a~~ good idea to have a separate		Before setting up the repositories, I read that it might be good idea to have a separate partitions for the repositories. From the reprepro man pages: "The most annoying problem not yet worked around is database corruption when the
	~~partition~~ for the repositories. From the reprepro man pages: "The most
	annoying problem not yet worked around is database corruption when the
	disk runs out of space. Ideally put the database on another partition to		disk runs out of space. Ideally put the database on another partition to
	avoid that." So it seems clear that a large disk is necessary for the package		avoid that." So it seems clear that a large disk is necessary for the package
	repositories~~. If one is going to create a replicated repository structure,~~		repositories.
	~~one can use drbd since that is now included in the linux kernel as of 2.6.33~~.

	reprepro has some dependencies, notably Berkeley DB, and it recommends		reprepro has some dependencies, notably Berkeley DB, and it recommends
	gnupg-agent and inoticoming. Using inotify and inoticoming to check for		gnupg-agent and inoticoming. Using inotify and inoticoming to check for
	incoming packages is also central to the repo system, it's worth noting that		incoming packages is also central to the repo system, it's worth noting that
	inoticoming and reprepro are maintained and ~~even~~ written by the same person.		inoticoming and reprepro are maintained and written by the same person.

	So, in short, I've installed these packages and their dependencies on the repository server: reprepro, libdb4.2, and inotincoming. (I used this command:		So, in short, I've installed these packages and their dependencies on the repository server: reprepro, libdb4.2, and inotincoming. (I used this command:
Line 23:		Line 20:
	''' Set up '''		''' Set up '''

	The first step ~~in creating a repo with reprepo is~~ to create ~~a directory under~~		The first step I took was to create directories for the binary deb packages:
	~~which~~ the binary deb packages ~~will be stored, along with the data for that set of packages.~~

	mkdir /srv/extras/		mkdir /srv/extras/
Line 30:		Line 26:
	mkdir /srv/extras-testing/		mkdir /srv/extras-testing/

	~~In this case we have three directories under which we will have our 'distros'.~~		Here we're putting the directories under the /srv/ directory so that we can isolate them from the rest of our web content. I have installed nginx to serve the repos because it is small and fast.
	~~These high-level directories are specific to Maemo, you can choose to create~~
	~~just one directory or change the names.~~ Here we're putting the directories under
	the /srv/ directory so that we can isolate them from the rest of our content.

imported_>jeremiah at 16:28, 28 December 2009

2009-12-28T16:28:21Z

← Older revision		Revision as of 16:28, 28 December 2009
Line 80:		Line 80:
	''' More information '''		''' More information '''

	http://wiki.debian.org/HowToSetupADebianRepository		http://wiki.debian.org/HowToSetupADebianRepository<br>
	http://alioth.debian.org/scm/viewvc.php/checkout/mirrorer/docs/manual.html?revision=HEAD&root=mirrorer		http://alioth.debian.org/scm/viewvc.php/checkout/mirrorer/docs/manual.html?revision=HEAD&root=mirrorer<br>
	http://www.debian-administration.org/articles/286		http://www.debian-administration.org/articles/286<br>