-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224

> We have private partial mirrors of various repositories which we
> use for testing packages and then to install the packages on each
> box.  These private partial mirrors are synced nightly.
>
> Because of a bug in lftp we can't use Tim's neat redirector and
> instead we mirror Trinity from mirrorservice.org.
>
> Last night there was no change in our partial Trinity mirror.
>
> The night before some old files were deleted but no new files
> were added.
>
> The night before that mirroring seemed to be working normally.
> It brought in a few dozen files from tdeartwork and tdebase.
>
> Also I see nightly builds updating on mirrorservice.org.  I
> wonder if RC2 updates are backed up behind nightly build
> updates.  If so I wonder if it would be better to serve the
> volatile but lightly used nightly builds directly so that
> the less volatile and more heavily used releases could more
> readily migrate to the public mirrors.

Yes, the R14 update is probably backed up behind the nightlies.  Problem
is, if I disable the nightly mirror mirrorservice.org will purge all of
the nightly files, causing the TDE servers to re-upload over 50 GB of data
(this is something I cannot afford to do).

I have had a couple of offers in the past for hosting a primary mirror
with push rsync; while I have been hesitant to make mirrorservice.org a
secondary mirror due to its high availability and bandwidth I may have to
do this anyway.  Any changes would not occur until after R14 release and
full sync, so this decision will be delayed for now

Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iFYEARELAAYFAlSB5qgACgkQLaxZSoRZrGG/QADeKGKg/CRIYaxiydT5Bc58EfQq
QRDqYP80VgXVewDffF+mrJxWgWE6k3J9LIXlAe57EKvjUEunKVKYAw==
=/85g
-----END PGP SIGNATURE-----