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. (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) 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? cheers, Toby