Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things

Re: Mirror a package repository on the fly.

by 5mi11er (Deacon)
on May 22, 2008 at 05:48 UTC ( #687877=note: print w/replies, xml ) Need Help??

in reply to Mirror a package repository on the fly.

After editing the get options stuff, and then having to deal with an incorrectly functioning File::Temp problem (didn't know where the temp directory was, even after setting the appropriate environment variable), I'm now running into this:
     Cannot find a valid baseurl for repo: <name your repo here>
base, update, extras, they all failed.

Any suggestions?


  • Comment on Re: Mirror a package repository on the fly.

Replies are listed 'Best First'.
Re^2: Mirror a package repository on the fly.
by 5mi11er (Deacon) on May 23, 2008 at 19:54 UTC
    Ok, figured out that I had to not use the new "mirrorlist" scheme, but the old "baseurl" scheme within the repo configuration file.

    So, it appears to work, but is only caching some .xml files, not the downloads themselves. That doesn't make much sense to me, if it's able to save the .xml files, it should certainly be able to save the megabytes worth of actual package files.

    Seems I'm talking to myself at this point, but if anyone is actually reading this and has any suggestions, I'm listening.


      I am glad you liked the code.
      Please post the command options you used and some log output.

      Where is your mirror root located?
      This is not quite clear in the pod, but doesn't matter which is your baseurl on yum.repos.d, as all files will be downloaded from the external mirror. This is something I'll change.

      The new scheme would be:

      * If the local repository do not have the file, get it upstream using the baseurl.
      * Besides this, respect 'no-cache' pragmas.

      I'll post some code tomorrow.


Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://687877]
[stevieb]: Corion: the problem with that is the 2.36 represents the underlying C library I've wrapped, which is why I want to use incrementals after the real version number. I've emailed modules@ to see if they can expedite the process for me...
[stevieb]: normally, it takes three days to delete, in case you want to change your mind

How do I use this? | Other CB clients
Other Users?
Others lurking in the Monastery: (11)
As of 2017-01-19 15:09 GMT
Find Nodes?
    Voting Booth?
    Do you watch meteor showers?

    Results (170 votes). Check out past polls.