(sorry if I broke the threading, not having a mail to reply to here)
> 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.
The question is, aren't most of these 192 GB useless by now?
Looking at what we currently have in our mirror dir, it seems there is a
lot of stuff there that could be gotten rid of. To me it really doesn't
make much sense to keep e.g. the 3.5.12-release from 2010 available on
all mirrors. Or a Maverick-iso from 2010. Other projects, e.g. CentOS,
solve this by only keeping the currently maintained versions on the main
mirror network, and at some point moving the things that are no longer
maintained to an archive site. This has a lot of advantages: That
content usually gets _extremely_ few requests, so it uses up far more
traffic to keep the mirrors updated than the mirrors will ever receive
requests for it. It also reduces the space usage on the mirrors. It
saves everyone space and traffic. And the few requests for archive
content can be handled by a server with very low bandwidth.
> 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.
> The primary mirror uses rsync rather than apt-mirror, and I suspect the
> same is true for the other mirrors.
We're running one of these mirrors at ftp.fau.de. Both your assumptions
are correct for us.
> (From Sláveks mail)
> If anyone is interested in synchronizing Preliminary Stable Builds or
> Preliminary Testing Builds, just let me know and I can also make them
> accessible via rsync
We would gladly mirror this _if_ there is a demand for it, i.e. we don't
spend more traffic syncing the mirror than the mirror will ever see
requests.
> 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.
As a TDE user myself, I would very much support the idea of putting the
PSBs, signed with a proper trinitydesktop.org and not a personal key,
onto the official mirror network. Rename them into "testing" builds so
it's clear what they are (that name is a lot more self-explaining than
"PSB").
Regards,
--
Michael Meier, FTP-Admin
Friedrich-Alexander-Universitaet Erlangen-Nuernberg
Regionales Rechenzentrum Erlangen
Martensstrasse 1, 91058 Erlangen, Germany
Tel.: +49 9131 85-28973, Fax: +49 9131 302941
rrze-ftp-admins(a)fau.de
blogs.fau.de/ftp/
Hi all,
by our joint effort we have gotten to the point where the list of issues
identified for R14.0.5 is empty. Please, do you have any more patches
that seems to be necessary before final freezing R14.0.5?
François, is everything ok to build on RPM distribution?
Cheers
--
Slávek
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
(Same on both 42.3 and 15.0)
# zypper se -s qt | grep -i gtk
| qtcurve-gtk2 | package | 1.8.19~git20150303-4.2 | x86_64 | OSS
i+ | trinity-gtk-qt-engine| package | 2:0.8-14.0.4_1.oss423 | x86_64 | TDE
i+ | trinity-gtk3-tqt-engine| package | 2:0.5-14.0.4_1.oss423 | x86_64 | TDE
TCC > GTK Styles & Fonts > GTK2 Styles:
WARNING: The Gtk-Qt theme engine is not installed. This means you
will not be able to use your TDE style in GTK2 applications.
Exactly what package is this warning referring to?
--
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
