Hi,
Long before I heard about reprepro, I also wrote my own Python script to
manage my local and remote Debian repositories (and I'm still using it):
http://people.debian.org/~frn/fmdr
documented at:
http://people.debian.org/~frn/fmdr.txt
To follow the pattern on
On 31 Jul 2007 09:53:16 -0400, Ian Zimmerman [EMAIL PROTECTED] wrote:
Let me describe my situation: I have a flat (single directory) archive
of personal debs. I see absolutely no point in maintaining code names
and suites and what not. So I put the debs into /var/local/debian
(which apache
Am Dienstag, den 31.07.2007, 09:53 -0400 schrieb Ian Zimmerman:
[..]
Neil I get:
Neil Failed to fetch
Neil http://www.linux.codehelp.co.uk/packages/unstable/amd64/Release
Neil Unable to find expected entry Packages in Meta-index file (malformed
Release file?)
And this is my main
Hi,
Here is how I manage my people.d.o repo. The following is
~/bin/update-archive:
#!/bin/bash
# -*- Mode: Sh -*-
# update_archive ---
# Author : Manoj Srivastava ( [EMAIL PROTECTED] )
# Created On : Tue May 10 10:14:46 2005
# Created On
Neil Time for a bug report, I think. But in order to actually get the
Neil thing working, I need more help.
Have you ever filed the report? I can't find it searching on b.d.o.
Neil I get:
Neil Failed to fetch
Neil http://www.linux.codehelp.co.uk/packages/unstable/amd64/Release
Neil Unable to
On 31 Jul 2007 09:53:16 -0400
Ian Zimmerman [EMAIL PROTECTED] wrote:
Neil Time for a bug report, I think. But in order to actually get the
Neil thing working, I need more help.
I wish you'd included the fact that the original email is from:
Date: 2006-07-28 21:09 +100
It's very confusing
Ian And this is my main question: have you figured out what causes this error?
Neil Yes - the error is caused by not using reprepro.
Neil :-)
I am afraid from my POV this is not particularly funny. The
documentation (i.e. the apt manual and the secure apt wiki) doesn't
mention reprepro (or
Le mardi 31 juillet 2007 à 12:51 -0400, Ian Zimmerman a écrit :
Neil reprepro doesn't force these on you but it does not stop you
Neil adding them later either.
Ian OK, I'll take a look at reprepro.
I did. reprepro still wants me to have a pool and dists subdirectories,
at the very
On 31 Jul 2007 12:51:39 -0400, Ian Zimmerman [EMAIL PROTECTED] wrote:
I did. reprepro still wants me to have a pool and dists subdirectories,
at the very least. This just makes it more complicated to maintain,
in particular to upload the debs.
I don't think reprepro is the right tool for my
Ian I don't think reprepro is the right tool for my job, either.
Ian Again, this is _not_ a mirror. It is just a bunch of debs (about
Ian 30 right now) that I build myself on a desktop machine, then upload
Ian to share with other client machines.
Ian
Ian Is _anyone_ else doing this? Seems like
On 31 Jul 2007 13:59:34 -0400, Ian Zimmerman [EMAIL PROTECTED] wrote:
Cameron How is uploading complicated? I added a post-upload script to
Cameron dupload so I can just do (on any machine) dupload --to sid
Cameron foo.changes apt-get update and it all just works, I don't
Cameron even have to
On 31 Jul 2007 13:59:34 -0400
Ian Zimmerman [EMAIL PROTECTED] wrote:
I see that I have to describe exactly what I do from the point of build.
In the source directory of a package, I do
fakeroot debian/rules binary
that will create a file ../foo.deb,
then
dput foo_version_arch.changes
George Danchev wrote:
On Tuesday 25 July 2006 21:20, Neil Williams wrote:
--cut--
That's what I used to use but this method can't be used with
mini-dinstall. It looks like your repository is a single subdirectory
whereas mine uses multiple subdirectories for the multiple
architectures. Each
I demand that Neil Williams may or may not have written...
[snip]
I'm now trying a brute force method:
$ cp /home/neil/Release.amd64 ./Release
$ md5sum Packages Release
$ md5sum Packages.gz Release
$ echo SHA1: ./Release
$ sha1sum Packages ./Release
$ sha1sum Packages.gz ./Release
Darren Salt wrote:
What I use for my repository is attached. (Licence is GPL = v2.)
Excellent! Thank you!
I've tweaked it a little so far to accept the architecture name as the
first command option and I'm running it manually after changing into
each directory. It should be simple to automate
I'm trying to sort out my trivial apt repository properly so that my
sponsor can obtain my packages more easily.
I've generated a gpg key to sign the Release files and I'm using
mini-dinstall on the server. It appears to be working, Release and
Release.gpg are created and gpg can verify that the
On Tue, Jul 25, 2006 at 02:33:04PM +0100, Neil Williams wrote:
[...]
I've generated a gpg key to sign the Release files and I'm using
mini-dinstall on the server. It appears to be working, Release and
Release.gpg are created and gpg can verify that the signature is good.
[...]
Yet apt-get
Jeremy Stanley wrote:
On Tue, Jul 25, 2006 at 02:33:04PM +0100, Neil Williams wrote:
[...]
I've generated a gpg key to sign the Release files and I'm using
mini-dinstall on the server. It appears to be working, Release and
Release.gpg are created and gpg can verify that the signature is good.
18 matches
Mail list logo
