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 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
Hi Uwe.
A simple reposync is fine, actually. My suggestion would be to drop the `--arch=noarch` flag you've specified. Our mirror manager likely will not respond to that request. `--arch=x86_64` by itself or no arch flag at all should be fine.
As an aside, the kickstart repos are actually a "point in time" set of repos, where they never update for the entirety of a minor release's 6 month life. This means it's when Rocky 8.X (in this case, 8.5) was released and some users want a baseline to start with instead of just installing everything brand new right away.
-L
On Thu, 10 Feb 2022 at 18:07, Uwe Sauter via rocky-mirror < rocky-mirror@lists.resf.org> wrote:
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 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
rocky-mirror mailing list -- rocky-mirror@lists.resf.org To unsubscribe send an email to rocky-mirror-leave@lists.resf.org
Hi Louis,
thanks for the quick response. I'm going to try and compare if specifing "--arch" makes any difference.
Regards,
Uwe
Am 11.02.22 um 02:45 schrieb Louis Abel:
Hi Uwe.
A simple reposync is fine, actually. My suggestion would be to drop the `--arch=noarch` flag you've specified. Our mirror manager likely will not respond to that request. `--arch=x86_64` by itself or no arch flag at all should be fine.
As an aside, the kickstart repos are actually a "point in time" set of repos, where they never update for the entirety of a minor release's 6 month life. This means it's when Rocky 8.X (in this case, 8.5) was released and some users want a baseline to start with instead of just installing everything brand new right away.
-L
On Thu, 10 Feb 2022 at 18:07, Uwe Sauter via rocky-mirror <rocky-mirror@lists.resf.org mailto:rocky-mirror@lists.resf.org> wrote:
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 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 _______________________________________________ rocky-mirror mailing list -- rocky-mirror@lists.resf.org <mailto:rocky-mirror@lists.resf.org> To unsubscribe send an email to rocky-mirror-leave@lists.resf.org <mailto:rocky-mirror-leave@lists.resf.org>--
-L
Follow-up:
If dnf reposync is called without --arch=noarch --arch=x86_64 it will also sync all i686 packagesfor which I'm not sure if I'll need them. On the other hand there's no reason to save these last few bytes so I'll do without --arch.
Thanks again,
Uwe
Am 11.02.22 um 08:33 schrieb Uwe Sauter:
Hi Louis,
thanks for the quick response. I'm going to try and compare if specifing "--arch" makes any difference.
Regards,
Uwe
Am 11.02.22 um 02:45 schrieb Louis Abel:
Hi Uwe.
A simple reposync is fine, actually. My suggestion would be to drop the `--arch=noarch` flag you've specified. Our mirror manager likely will not respond to that request. `--arch=x86_64` by itself or no arch flag at all should be fine.
As an aside, the kickstart repos are actually a "point in time" set of repos, where they never update for the entirety of a minor release's 6 month life. This means it's when Rocky 8.X (in this case, 8.5) was released and some users want a baseline to start with instead of just installing everything brand new right away.
-L
On Thu, 10 Feb 2022 at 18:07, Uwe Sauter via rocky-mirror <rocky-mirror@lists.resf.org mailto:rocky-mirror@lists.resf.org> wrote:
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 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 _______________________________________________ rocky-mirror mailing list -- rocky-mirror@lists.resf.org <mailto:rocky-mirror@lists.resf.org> To unsubscribe send an email to rocky-mirror-leave@lists.resf.org <mailto:rocky-mirror-leave@lists.resf.org>--
-L
-
Louis Abel -
Uwe Sauter