Fwd: Commit 2d5772b9c7316c627362997925a33caf64f4f6ef
I accidentally sent the following just to Peter.
/M
---------- Forwarded message ----------
From: Magnus Therning
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?
They have never disappeared on my system, but then I never have found a need for them either. What I meant is that they may go missing when I manually re-create the repo DB on andromeda to make sure the repo DB is proper. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
Hi Magnus,
[The symlinks] have never disappeared on my system, but then I never have found a need for them either.
the reason why we need those symlinks is that the repository is served to the public being called 'haskell', but we build it under the name of 'repo'. Consequently, Pacman expects the repository database to be called 'haskell.db.tar.gz' when our users run it, but inside of the chroot build, Pacman wants that database to be called 'repo.db.tar.gz'. The easiest solution I've found to remedy that problem is to create a symlink as follows: ln -s repo.db.tar.gz haskell.db.tar.gz That solution is by no means ideal, but it works. Of course, an even better solution would be to modify our chroot builds so that they call the repository they're building 'haskell' instead of 'repo', then this entire problem would just cease to exist. If anyone knows how to accomplish that, please share the information! Take care, Peter
On Thu, Feb 3, 2011 at 13:46, Peter Simons
Hi Magnus,
> [The symlinks] have never disappeared on my system, but then I never > have found a need for them either.
the reason why we need those symlinks is that the repository is served to the public being called 'haskell', but we build it under the name of 'repo'. Consequently, Pacman expects the repository database to be called 'haskell.db.tar.gz' when our users run it, but inside of the chroot build, Pacman wants that database to be called 'repo.db.tar.gz'.
The easiest solution I've found to remedy that problem is to create a symlink as follows:
ln -s repo.db.tar.gz haskell.db.tar.gz
That solution is by no means ideal, but it works. Of course, an even better solution would be to modify our chroot builds so that they call the repository they're building 'haskell' instead of 'repo', then this entire problem would just cease to exist. If anyone knows how to accomplish that, please share the information!
The easiest solution I found was to never upload the repo.db* files at all, just the packages, then use ssh to log in and run repo-add on andromeda. All of it automated in a script. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
participants (2)
-
Magnus Therning -
Peter Simons