[Spacewalk-list] question about repo's

Jesus M. Rodriguez jmrodri at gmail.com
Fri Jan 9 15:30:19 UTC 2009


On Fri, Jan 9, 2009 at 4:45 AM, Michiel van Es <michiele at info.nl> wrote:
> Hi,
>
> I am hosting spacewalk 3.0 on a CentOS 5.2 server and have 2 scripts for
> syncing the repo's and pushing the repo's to spacewalk.
>
> Both actions download and copy the rpm's.
>
> The reposync put the downloaded repo's in
>
> [root at devmx01 repodata]# cd /repodata/repositories
> [root at devmx01 repositories]# ls
> CentOS4_updates  CentOS5
> [root at devmx01 repositories]# cd
> [root at devmx01 repositories]# du -hs
> 12G     .
>
> Whis is 12 GB
>
> But then the push into Spacewalk also put the rpm's in /repodata/sattelite:
>
> [root at devmx01 repodata]# cd satellite/
> [root at devmx01 satellite]# du -hs
> 11G     .

I'm not sure why we're putting packages in /repodata/satellite unless your
/var also points to /repodata. I'm going to assume that is the case.
Spacewalk stores all of it's packages in /var/satellite which is why you would
see that duplication. Unfortunately, that is how it currently works.

> Now I have at 2 places the same rpm.
> Is it a possibility to remove the /repodata/repositories/*.rpm's ?

Once the rpms have been pushed to Spacewalk and land in /var/satellite,
we wouldn't need any other rpms just the ones in /var/satellite.

> I mean: why are the downloaded rpm's needed on both places on the
> filesystem?

We only needed them in /var/satellite.

> Is there a way to save some diskspace?
> We also want to use the rpmforge repo to sync (we use it on some of our
> CentOS clients) but we got not enough disk space to do so ;'-(
>
> Thanks in advance for any help.
>

Sincerely,
jesus




More information about the Spacewalk-list mailing list