I was setting up a new CentOS Stream mirror and decided to use the CentOS-Stream-nodebug module to save on disk space. While pulling it down I noticed that there still seemed to be some debug content (at least in the aarch64 folder) getting pulled down. Is this intentional or do you need to make a config change on your end?
CentOS-Stream-nodebug
Thanks!
Metadata Update from @zlopez: - Issue tagged with: centos-stream
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue tagged with: centos-common-infra, low-trouble, medium-gain
Let me have a look as they were configured before content landed and it can be that the rsync filter still let some pkgs be pulled. TBH, most people want a 1:1 matching mirror with mirror.stream.centos.org, which these days contains everything , including src.rpm and debuginfo pkgs (starting from stream 9, nothing is pushed to vault.centos.org or debuginfo.centos.org)
@ramereth : the current module has exclude = *debuginfo*.rpm so can you come with an example/path of such file that would still be downloaded ?
exclude = *debuginfo*.rpm
@arrfab so this provides a few issues as this doesn't remove the whole debug directory from my end. This is leaving files such as *debugsource*.rpm and also the repodata folder. This may leave some users to think we do provide the debug repo when we don't fully include all the files for it and thus a partial repo.
*debugsource*.rpm
repodata
In the past, I've used an exclude file such as the following in my rsync excludes on Fedora:
- 9-stream/*/*/debug - SIGs/*/*/*/*/debug
Now you might be able to condense this to the following:
- */*/*/debug - */*/*/*/*/debug
But you'll need to test it.
I gave it a quick try, as initially we had a filter in place without any data/content. The new pushed rsync module as this:
exclude = *debuginfo*.rpm *debug/tree/repodata/* *debugsource* *kernel-rt-*debug* *kernel-debug*
So that should drastically reduce the packages set and also excluding the repodata
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Looks like this still needs a little bit of tweaking in two places:
Everything under the 9-stream still shows some empty directories in the debug folders. Here's an example:
9-stream
/data/ftp/pub/centos-stream/9-stream/RT/x86_64/debug /data/ftp/pub/centos-stream/9-stream/RT/x86_64/debug/tree /data/ftp/pub/centos-stream/9-stream/RT/x86_64/debug/tree/Packages /data/ftp/pub/centos-stream/9-stream/RT/x86_64/debug/tree/repodata
Also, under the SIG folders I see some repodata folders that still have data. It looks as though the directory structure is slightly different under the SIGs folder. An example:
/data/ftp/pub/centos-stream/SIGs/9-stream/hyperscale/aarch64/packages-experimental/debug /data/ftp/pub/centos-stream/SIGs/9-stream/hyperscale/aarch64/packages-experimental/debug/repodata /data/ftp/pub/centos-stream/SIGs/9-stream/hyperscale/aarch64/packages-experimental/debug/repodata/repomd.xml /data/ftp/pub/centos-stream/SIGs/9-stream/hyperscale/aarch64/packages-experimental/debug/repodata/1b71a1685fbff8994b1d3645f590116abc9000abcea81891fa2aee1e5c153d89-primary.xml.gz /data/ftp/pub/centos-stream/SIGs/9-stream/hyperscale/aarch64/packages-experimental/debug/repodata/37898f094252c41a311251ad78fe1f905c42bda826a58282ebe87b740e4595c1-other.xml.gz /data/ftp/pub/centos-stream/SIGs/9-stream/hyperscale/aarch64/packages-experimental/debug/repodata/4674e620423ab137eed2357b480541998a7b01196726401b31ce5f1f17920c06-primary.sqlite.bz2 /data/ftp/pub/centos-stream/SIGs/9-stream/hyperscale/aarch64/packages-experimental/debug/repodata/9bd1610d1e8bc73b902f22affc2d3314618f0a867d468930c06a3bbbe8d55126-filelists.xml.gz /data/ftp/pub/centos-stream/SIGs/9-stream/hyperscale/aarch64/packages-experimental/debug/repodata/b982150a119b1ac40692bf8e4537812c67a42080cec065fc33c8c9261e2678a0-other.sqlite.bz2 /data/ftp/pub/centos-stream/SIGs/9-stream/hyperscale/aarch64/packages-experimental/debug/repodata/e2e0abb01006dad412142eba7cda8f38ae4ace461979db7375e7a68619e619bf-filelists.sqlite.bz2
Metadata Update from @ramereth: - Issue status updated to: Open (was: Closed)
Yeah, I forgot that SIGs had different layout for debug repodata, so it was now added in the template that is pushed to all nodes :
exclude = *debuginfo*.rpm *debug/tree/repodata/* *debugsource* *kernel-rt-*debug* *kernel-debug* *debug/repodata/*
WRT empty directory, that's not a problem per se, as there is no package normally landing (filtered out by the exclude= line) and same for repodata.
You can still fine tune your pull script if you want to selectively tune that too
Login to comment on this ticket.