Re: Maintaining personal backports
On Mon, Jul 20, 2009 at 08:55:30PM -0400, Kumar Appaiah wrote:
> On Mon, Jul 20, 2009 at 10:19:29AM -0500, Kumar Appaiah wrote:
> > > If you are looking for small private archive:
> > > http://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_small_public_package_archive
> > >
> > > Also debi command in devscript may reduce dpkg -i.
> >
> > Thanks for that. It'd be nice to automate the build process as well
> > though, and combine it with these tools.
>
> So, I used Osamu's reference to create a small repository for myself,
...
> I am looking to Wikify this, with full procedure on how to set up the
> mirror, the pbuilder/cowbuilder build environment and finally building
> packages.
Please consider wiki.debian.org as place.
> But before that, I'd appreciate it if others can suggest
> workarounds for the following kludges:
> #!/bin/sh
>
> if [ ! -n "$1" ];
> then
> echo "Usage: `basename $0` <sid_package>"
> exit 1;
> fi
>
> sudo cowbuilder --configfile ~/.pbuilderrc-lenny --build $(basename "$FILE")
If you use pbuilder, why you need to force such thing.
If I were you and using pbuilder, I edit tar.gz file contents. Make
chroot image have /etc/apt/sources.list pointing to local private
archive aceslinc too. (I guess you can do the same with cowbuilder.
> dupload -t aceslinc /var/cache/pbuilder/result/$(basename "${FILE%.dsc}")_amd64.changes
If you get the whole thing running, it will e nice article for wiki.
Osamu
Reply to: