Hello.
During our final testing, we have found issues with one of our
architectures (ppc64le). Due to some time constraints in our respective
time zones, we won't be able to resolve this issue in a timely manner to do
any bitflipping for our release. This does not mean the content will
disappear from your mirror. They will remain locked until we have isolated
the issue and reissued fixed builds of powerpc content if necessary. In the
event there are fixes, you will be able to sync them …
[View More]normally from our
msync endpoint.
Thank you so much for your support of Rocky Linux. If there is anything you
need or if you feel you may be able to provide support or help to resolve
the issues we're facing, please let us know by reaching out directly or
joining our mattermost if you haven't already.
On Sat, 13 May 2023 at 07:35, Neil Hanlon via rocky-mirror-announce <
rocky-mirror-announce(a)lists.resf.org> wrote:
> Hello all,
>
> We are pleased to announce that Rocky Linux 9.2 is available for mirrors
> to sync from our mirror nodes in the US and
> Germany.
>
> US: msync.rockylinux.org
> EU: fra.msync.rockylinux.org
>
> Please note the fra nodes have a different rsync module layout which will
> be standardized in a future release. If you
> have already been using the frankfurt node, there is nothing you need to
> change.
>
> The artifacts available to mirrors are to be kept from the public in
> accordance with our bitflip procedure until the
> release has been thoroughly tested. If all goes well with tests, we intend
> to perform the bitflip (and release Rocky
> 9.2) on Monday during US business hours (East Coast). If anything changes
> to this affect, I will send a follow up email.
>
> Thank you very much for your continued support of Rocky Linux. If there is
> anything you need, please do not hesitate to
> reach out directly or via the mirrors list.
>
> Best,
> Neil
> _______________________________________________
> rocky-mirror-announce mailing list -- rocky-mirror-announce(a)lists.resf.org
> To unsubscribe send an email to rocky-mirror-announce-leave(a)lists.resf.org
>
--
-L
[View Less]
thank you Brian,
clear and updated.
Kari
--
Sent with Tutanota
22 Apr 2022, 07:46 by rocky-mirror(a)lists.resf.org:
> Hi Kari,
>
> Thank you for your interest in Rocky Linux! Instructions for adding your mirror to our mirror list are available at https://docs.rockylinux.org/guides/mirror_management/add_mirror_manager/
>
> V/R,
>
> Brian Clemens
> Project Manager
> Rocky Enterprise Software Foundation
>
>> On Apr 21, 2022, at 12:06, Karibu - Freedif.org…
[View More]via rocky-mirror <rocky-mirror(a)lists.resf.org> wrote:
>>
>> Hello,
>> I'm Kari, the admin of mirror.freedif.org, based in Singapore.
>>
>> I'd like to support Rocky community with a mirror there.
>> 1GBPS
>> https://mirror.freedif.org/Rocky/
>> rsync://mirror.freedif.org/Rocky/
>>
>> Let me know what other information you require.
>>
>> Thank you
>> Kari
>> --
>> Sent with Tutanota
>>
[View Less]
Dear Rocky enthusiasts,
I was wondering if there are any best practice recommendations about how
to sync the packages repos for on premise mirroring.
I don't want to keep a full-fledged copy of the official mirrors 'cause
I don't care about aarch64, source packages, ISOs and kickstart repos
(what are these for, anyway?).
One of the reasons for asking is that I'd like to preserve the metadata
for modular streams. As far as I can tell these are destroyed when the
metadata is recreated …
[View More]using createrepo/createrepo_c.
Another reason is that I'd like to keep only the latest (and perhaps the
previous) version of a package in order to save disk space. If an older
version of a package will ever be needed I'd still be able to fetch that
from a public mirror.
Is using "dnf reposync --arch=noarch --arch=x86_64 --delete
--download-metadata --newest-only --norepopath
--download-path=/path/to/local/repo --repoid=$REPO" the correct approach?
Thanks,
Uwe
[View Less]