On 02/02/11 22:16, Nicolas Pouillard wrote:

On Wed, 02 Feb 2011 18:50:16 +0100, Peter Simons wrote:

...

Hi guys,

yesterday, I tried to install "haskell-pandoc" on a Linux/i686 machine, but Pacman was unable to download that binary package, because the file

haskell-pandoc-1.6.0.1-2-i686.pkg.tar.xz

had been deleted from the server, probably because an update to version 1.8.0.1-1 had become available. After figuring that out, I updated my database with "pacman -Sy", and that fixed the problem.

Still, I would have preferred the 1.6.0.1-2 version to remain available for some reasonable grace period, like 1 or 2 weeks. Our repository is extremely small,

$ du -sh ~haskell/* 75M /srv/haskell/i686 66M /srv/haskell/x86_64

..., so I guess it won't hurt to keep older packages around for a little while even after an update. Please don't delete any packages from that repository unless there's a good reason to, i.e. that they've been outdated for (at least) several days.

I don't know how you (the team) sync the repository, but I find it easier to remove the old version and add the new at the same time.

I've recently found the tool repo-clean (in AUR) for doing this.

A way to mitigate this would be to either keep at kill list of files to remove and when and/or having a separate repo for these archives.

Are there any tools that would make it easier to maintain such a kill list? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus

On 02/02/11 22:57, Peter Hercek wrote:

On 02/02/2011 11:26 PM, Magnus Therning wrote:

...

...

A way to mitigate this would be to either keep at kill list of files to remove and when and/or having a separate repo for these archives. Are there any tools that would make it easier to maintain such a kill list?

How about keeping the last two versions all the time. No need to have a kill list. And the repository is fairly small. It should not be a problem if it takes two times the size.

AFAICS repo-clean can't be used then; it always keeps only the very latest version of a package. Is there some other tool that is more configurable that can be used to automate such a policy? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus

Hi Nicolas,

I don't know how you (the team) sync the repository, but I find it easier to remove the old version and add the new at the same time.

I rsync the repository from andromeda into my local chroot sandbox, then I run 'makeworld', and then I rsync the modified repository back to the server. As far as I'm concerned, it doesn't matter whether I keep those old versions around or not, i.e. deleting the old versions doesn't simplify matters for me.

A way to mitigate this would be to either keep at kill list of files to remove and when and/or having a separate repo for these archives.

I believe the repo-clean utility http://code.google.com/p/repo-clean/ that Magnus mentioned could get the job done just fine. We could run that every 2 weeks or so to expire unused packages. It's not important to keep them around indefinitely, but I feel that we shouldn't delete them immediately at the time of an update either. Take care, Peter