24 Jun
2018
24 Jun
'18
6:59 p.m.
On Sun June 24 2018 10:14:39 Slávek Banko wrote:
at mirror.xcer.cz, colleague has not yet made the
removal of distributions
that are no longer build for Preliminary Stable Builds. Therefore, packages
for these distributions are still available on mirror.xcer.cz. While on
mirror.ppa.trinitydesktop.org is cleaning old packages more actively. This
is why the content may vary. Both of these mirrors are synchronized from my
main server using apt-mirror. Therefore, removing old packages can be done
differently on each mirror.
If you want to synchronize Preliminary Stable Builds repository to your
mirror, I can setup rsync on mirror.ppa.trinitydesktop.org. Would it be
useful for you?
// Retitled and moved from trinity-users to trinity-devel.
Hi Slavek,
The mirrors are here to serve TDE so the question is what would be useful to
TDE devs and users?
Here's a little background FYI.
(1) The primary mirror has roughly 240GB of which 192GB is currently in use.
This can be increased but of course none of us want to spend more money
on renting data center disk space than necessary. I don't know how much
disk space is available for TDE on the secondary mirrors.
27G ./cdimages
1.7G ./git-images
14G ./libreoffice-trinity
38M ./openldap
24G ./releases
62G ./trinity
384M ./trinity-builddeps
1.5G ./trinity-builddeps-r14.0.0
929M ./trinity-builddeps-v3.5.13
1.5G ./trinity-nightly-build-dependencies
412K ./trinity-nightly-builds-01
41G ./trinity-r14.0.0
20G ./trinity-v3.5.13
553M ./ulab
(2) I have not yet exceeded monthly transfer limits and hope not to do so.
I can serve normal traffic and new releases but please contact mirror
admins before any overall reorganization which could be done more
efficiently with mv than rsync.
(3) I am not personally in direct contact with any of the other mirrors, even
though they all pull from us. Contact between the mirror admins has AFAIK
always been through Tim. We created the primary mirror to alleviate
bandwidth problems at Tim's build farm in the past when all mirrors
pulled direct from him.
(4) The primary mirror uses rsync rather than apt-mirror, and I suspect the
same is true for the other mirrors.
(5) I appreciate heads up on any planned major changes to mirror content so
I can increase monitoring and if necessary change mirroring parameters.
It might be best to provide such heads up off-list because ...
(6) To avoid overloading build farm bandwidth, it is best not to announce
releases until they are fully mirrored. If users start pulling unmirrored
files they are served from the build farm, overloading its bandwidth and
slowing mirroring, so things get very slow for everyone.
As a TDE user myself I would find it convenient but not critical if there
were fewer differences between PSB and Stable. Ideally they would be in
the same repo pool - like Debian testing and stable.
--Mike