On Mon, Oct 20, 2014 at 4:22 AM, Reindl Harald <h.rei...@thelounge.net> wrote: > > > Am 20.10.2014 um 04:02 schrieb Nico Kadel-Garcia: >> >> On Sun, Oct 19, 2014 at 5:26 AM, Reindl Harald <h.rei...@thelounge.net> >> wrote: >>> >>> >>> Am 19.10.2014 um 06:37 schrieb Nico Kadel-Garcia: >>>> >>>> >>>> On Sat, Oct 18, 2014 at 8:28 PM, Reindl Harald <h.rei...@thelounge.net> >>>> wrote:
>> It starts with the the fact that your script has not >> verified *any* of your RPM's, and reposync does not ordinarily verify >> file contents unless you activate GPG verification. So any partial >> transfer or interrupted transfer will effectively corrupted your local >> repo, especially if anything else is dependent on that package. Do >> take a look at the github scripts I pointed out, they do a more >> thorough job. > > > what are you talking about reposync all the time? You've a point, I was misreading your script. > frankly i have posted the whole source above > "/buildserver/repo-create.sh" can be read as "createrepo && chown && chmod > && rsync-to-failover maschine on the cluster" Mind you, putting this stuff in places like "/repo/cache" and "/buildserver" is a direct violation of the file system hierarchy, but that's your own local policy and potential problem. > */var/cache/yum/* is the source *after* ran updates on that machine ordinary > with yum - guess what - after that suceeded the RPM's GPG verified and > *that* is what i try to explain the whole time - yum don't need to know > about deltarpm and so other scripts using the yum-cache don't too I do think you'd be much better off with using rsync and a local mirror. You can point it to architectures and OS releases you aren't currently running, and point it to include all potential updates. Even your your setup, you can use 'yum --doanloadonly' and 'yum install *' to ensure the presence of more packages in /var/cache/yum >> Last, doing this on an individual machine does not scale You're >> chewing up disk space on each machine, and bandwitdh, with all the >> required 'repodata' downloads > > > WTF - no single other machine has *any* repo in the WAN configured *That* part was missing. You've configured your local hosts to all point to an individual mirror? And that local repo has *all* packages you might possibly install on the other machines? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
