Commit 2d5772b9c7316c627362997925a33caf64f4f6ef
Hi Magnus, there seems to be a misunderstanding. I created the missing symlinks from repo.db.tar.gz to haskell.db.tar.gz in both the i686 and the x86_64 repository, so the change you made in that commit is no longer required. You can use the exact same repository for building in a chroot sandbox and for serving it to the public via Pacman. I hope this helps, Peter
On Thu, Feb 3, 2011 at 10:39, Peter Simons
Hi Magnus,
there seems to be a misunderstanding. I created the missing symlinks from repo.db.tar.gz to haskell.db.tar.gz in both the i686 and the x86_64 repository, so the change you made in that commit is no longer required. You can use the exact same repository for building in a chroot sandbox and for serving it to the public via Pacman.
Let's just keep them in the script; there's a bit risk they go missing since I've had issues with the repo DBs in the chroots. I don't trust them enough to just upload them anymore. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
Hi Magnus,
Let's just keep them in the script; there's a bit risk they go missing
I have maintained the repository using those two symlinks for 3 months or so, and I've never had a problem with them "going missing". On what occasion did those symlink disappear on your system? Take care, Peter
participants (2)
-
Magnus Therning -
Peter Simons