Yum Repo Housekeeping

March 18, 2013 by · 8 Comments 

About 30 minutes ago I moved the yum repository files from the "media" folder on this domain to a dedicated subdomain of http://yum.jasonlitka.com.  This is simply a housekeeping measure. It's easier to keep track of those files when they're on a separate subdomain and it gives me the flexibility to easily spin them off to a separate server should the bandwidth requirements get out of control.  On that, a big thank you to Linode (referral link) for recently increasing your bandwidth limits by 10x and to Cloudflare for absorbing close to 50% of my traffic for the grand total of $0.00/month.

This shouldn't have any impact on running servers using the repository since the old location has a 301 redirect to the new one.  If you do hit a problem try a "yum clean all".  If that doesn't work then let me know.

On a semi-related note, I migrated servers about a month back and apparently didn't configure outbound email...  If you tried to use the contact form since the beginning of February then I didn't get your message.  Sorry.

Comments

8 Responses to “Yum Repo Housekeeping”
  1. Lucille says:

    Hi Jason,

    I did a yum clean all, and then a yum update, and I still got:

    http://www.jasonlitka.com/media/EL5Server/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
    Trying other mirror.
    Error: Cannot retrieve repository metadata (repomd.xml) for repository: utterramblings. Please verify its path and try again

    Should I change the baseurl in the utterramblings.repo file?

    Thanks,
    Lucille

  2. Jason says:

    @Lucille,

    That's related to the text below from the Yum Repository page:

    NOTE #1: If the above URL returns a 404 then try hard-coding $releasever to your EL version ('EL4' or 'EL5') and the $basearch to whatever is appropriate ('i386' or 'x86_64').

    I've added a 301 for that EL5Server path so your system works again, but you might want to consider updating the base url to avoid the double 301 redirect (from www to yum, then again to the correct path).

  3. Mitchell says:

    For what it's worth, I get the same thing. No support for EL6 maybe?

    I'm hard coding everything :

    http://yum.jasonlitka.com/EL6/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
    Trying other mirror.
    Error: Cannot retrieve repository metadata (repomd.xml) for repository: utterramblings. Please verify its path and try again

  4. Jason says:

    Mitchell,

    I do not provide packages for EL6 at this point.

  5. Steven Spencer says:

    Jason,

    I installed your version of httpd on a CentOS 5.9 server as part of an installation setup for some security packages (not least of all was mod_security, etc.) Anyway, the site owner is trying to get a PCI complaint scan, and it is reporting httpd-2.2.22-jason.1 as non-compliant. I'm thinking that it is a patched version of httpd and as such is compliant, but I guess at this point I'm not sure. If it is not compliant, could you just let me know? If it is, what can I use as justification for the scan?

    I appreciate any response.

    Thanks,
    Steve

  6. Dmitry says:

    Jason

    I am also getting :
    http://www.jasonlitka.com/media/EL6Server/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"

    I saw you said "I do not provide packages for EL6 at this point"

    Is it still the case?

    Thank you
    Dmitry

  7. jack chen says:

    Loaded plugins: langpacks
    http://www.jasonlitka.com/media/EL7/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
    Trying other mirror.

    One of the configured repositories failed (Jason's Utter Ramblings Repo),
    and yum doesn't have enough cached data to continue. At this point the only
    safe thing yum can do is fail. There are a few ways to work "fix" this:

    1. Contact the upstream for the repository and get them to fix the problem.

    2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

    3. Disable the repository, so yum won't use it by default. Yum will then
    just ignore the repository until you permanently enable it again or use
    --enablerepo for temporary usage:

    yum-config-manager --disable utterramblings

    4. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

    yum-config-manager --save --setopt=utterramblings.skip_if_unavailable=true

    failure: repodata/repomd.xml from utterramblings: [Errno 256] No more mirrors to try.
    http://www.jasonlitka.com/media/EL7/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

  8. Jason says:

    There are no packages available for EL6 or EL7.

This site is no longer updated. If you have a need for RHEL/CentOS LAMP Stack updates outside the normal channels, I recommend ART. https://updates.atomicorp.com/channels/