On Mon, Jul 2, 2012 at 11:03 AM, Toby Corkindale <toby.corkindale@strategicdata.com.au> wrote:
On 30/06/12 01:42, Trent W. Buck wrote:
Toby Corkindale wrote:
On 29/06/12 11:50, Trent W. Buck wrote:
Toby Corkindale wrote:
So far, repo management software I've seen will purge the older version out when you upload a new one.
echo >>Release NotAutomatic: yes # Workaround #272557.
This will prevent all upgrades from that repo unless a human explicitly requests them. e.g. "apt-get dist-upgrade" will skip them. This flag is what debian/experimental uses.
Nonono, I mean the repository management software deletes the package from the repository. I'm OK with the pinning and stuff on the client side.
See also reprorepo, or http://cyber.com.au/~twb/snarf/apt-ftparchive for a cheapass alternative.
I want the repository to maintain multiple versions of the same package.
Either of the above should handle that fine.
Both Edward and yourself have said that, but I can't figure out how to configure it as such -- I can't seem to work out how though -- reprepro deletes stuff out of the database once a new version comes in, and I am really struggling to find an option that prevents that.
Sorry, I can't help there; ICBF learning reprepro (I can't even spell it reliably!) which is why I have my cheaparse script. As you can see, it doesn't do anything to the debs, it just creates the metadata files.
(It's not good enough to keep the .deb file in a directory -- it needs to be in the Packages.gz file as well or clients won't know about it)
That's what the script I linked to does.
I don't suppose you have a config handy from a repo that's already configured to do this that you can paste in here?
That's what the script I linked to creates.
PS: I would still recommend reprorepo over my own thing, because it deals with multiple suites and so on, rather than a single flat dir. Also it's supported by Debian and stuff :P
Yeah, given that we want to support multiple distributions, and do like having things that are actually supported upstream, I'd like to stay with one of the official systems.
You said before that Reprepro could do what I want, but then you said you CBF learning Reprepro to explain how to use it.. Could I just check, have you actually, definitely seen Reprepro support the feature I want? I'd hate to spend ages trying to learn to configure it, only to find out that you were mistaken.
thanks, Toby
On much deeper inspection it looks like it can't. I hadn't realised the multiples of packages in our repository was considered a bug (fixed by deleteunreferenced) so my apologies. You can have multiple source tracking however this does not exist for packages. http://anonscm.debian.org/gitweb/?p=mirrorer/reprepro.git;a=blob_plain;f=doc...
3.1) Can I have two versions of a package in the same distribution? ------------------------------------------------------------------- Sorry, this is not possible right now, as reprepro heavily optimizes at only having one version of a package in a suite-type-component-architecture quadruple. You can have different versions in different architectures and/or components within the same suite. (Even different versions of a architecture all package in different architectures of the same suite). But within the same architecture and the same component of a distribution it is not possible.