Re: Local mirror problems.
On Fri, 16 Dec 2005 14:20:42 +0100 Goswin von Brederlow <[EMAIL PROTECTED]> wrote: > > Austin Denyer <[EMAIL PROTECTED]> writes: > > > Hi. > > > > As we are getting more and more amd64 boxen here, we've decided to > > run our own internal mirror (we currently have an internal mirror > > of i386). > > Since the mirror is internal and rsync puts quite some stress on the > server I recommend using reprepro instead. The drawback is that you > loose the archive signature (and get a new signature by reprepro) and > reprepro doesn't mirror install images. The advantage is that you can > mix debian.org, security.debian.org and amd64.debian.net all into one > local archive. Thanks - I'll take a look at that. Regards, Ozz. pgpnkY6ONNZSv.pgp Description: PGP signature
Re: Local mirror problems.
On Wed, 14 Dec 2005 20:57:17 -0500 Anthony DeRobertis <[EMAIL PROTECTED]> wrote: > > Austin Denyer wrote: > > > Now, if I ssh to the mirror, > > debian-amd64/debian-amd64/pool/main/m/manpages/manpages_2.16-1_all.deb > > is a symlink to the file in the regular mirror > > (debian-amd64/debian/pool/main/m/manpages/manpages_2.16-1_all.deb) > > and I can follow the link manually. > > Confirm that your FTP/HTTP/whatever server is set to follow symlinks. > Some don't by default as a security measure. As far as I'm aware, the symlink configuration issue you mention is usually caused by the ftp server running in a chroot environment. Ours is not, as this particular server is internal only. If it matters, it is running proftp. Regards, Ozz. pgprIiJiwkiJB.pgp Description: PGP signature
Re: Local mirror problems.
Austin Denyer <[EMAIL PROTECTED]> writes: > Hi. > > As we are getting more and more amd64 boxen here, we've decided to run > our own internal mirror (we currently have an internal mirror of i386). Since the mirror is internal and rsync puts quite some stress on the server I recommend using reprepro instead. The drawback is that you loose the archive signature (and get a new signature by reprepro) and reprepro doesn't mirror install images. The advantage is that you can mix debian.org, security.debian.org and amd64.debian.net all into one local archive. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Local mirror problems.
Austin Denyer wrote: > Now, if I ssh to the mirror, > debian-amd64/debian-amd64/pool/main/m/manpages/manpages_2.16-1_all.deb > is a symlink to the file in the regular mirror > (debian-amd64/debian/pool/main/m/manpages/manpages_2.16-1_all.deb) > and I can follow the link manually. Confirm that your FTP/HTTP/whatever server is set to follow symlinks. Some don't by default as a security measure. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Local mirror problems.
Hi. As we are getting more and more amd64 boxen here, we've decided to run our own internal mirror (we currently have an internal mirror of i386). I set the mirror up according to the How-To at: http://amd64.debian.net/~joerg/mirror.html I used the secondary mirror setup, as we already have the /debian tree mirrored, and there was no sense in pulling another ~18Gb of duplicate files. That section of the How-To has a "real-life" scenario at the end that exactly matches my setup: Real-Life Scenario: You mirror :debian-amd64/debian-amd64 to /home/ftp/debian-amd64, so the files end up living in /home/ftp/debian-amd64/debian-amd64. Assume you have your regular Debian mirror in /home/ftp/debian, then you need to create a symlink called debian in /home/ftp/debian-amd64 which points to /home/ftp/debian to actually get the link farm to work. Now, this works fine for the amd64-specific files, but anything it has to pull from the regular mirror (non-amd64-specific) produce errors. Here is an example from the update I did today: === Get:1 ftp://mirror unstable/main libkpathsea4 3.0-12 [78.3kB] Get:2 ftp://mirror unstable/main tetex-bin 3.0-12 [4014kB] Get:3 ftp://mirror unstable/main manpages 2.16-1 [407kB] Err ftp://mirror unstable/main manpages 2.16-1 Unable to fetch file, server said '/debian-amd64/debian-amd64/pool/main/m/manpages/manpages_2.16-1_all.deb: No such file or directory ' Get:4 ftp://mirror unstable/main manpages-dev 2.16-1 [1116kB] Get:5 ftp://mirror unstable/main libcupsys2-dev 1.1.23-13 [91.3kB] Get:6 ftp://mirror unstable/main libcupsys2 1.1.23-13 [80.0kB] Get:7 ftp://mirror unstable/main libcupsimage2 1.1.23-13 [57.7kB] Get:8 ftp://mirror unstable/main cupsys 1.1.23-13 [8975kB] Get:9 http://debian.csail.mit.edu unstable/main manpages 2.16-1 [407kB] Get:10 ftp://mirror unstable/main menu 2.1.27 [387kB] Get:11 ftp://mirror unstable/main menu-xdg 0.2.2 [4210B] Get:12 http://debian.csail.mit.edu unstable/main manpages-dev 2.16-1 [1116kB] Get:13 http://debian.csail.mit.edu unstable/main menu-xdg 0.2.2 [4210B] Fetched 15.2MB in 5s (2706kB/s) == Now, if I ssh to the mirror, debian-amd64/debian-amd64/pool/main/m/manpages/manpages_2.16-1_all.deb is a symlink to the file in the regular mirror (debian-amd64/debian/pool/main/m/manpages/manpages_2.16-1_all.deb) and I can follow the link manually. Any clues? Regards, Ozz. pgpeHhlz3Gh0t.pgp Description: PGP signature
