Irel_blocked-releases-page job on local build farm keeps failing

It appears that the hydro rosdistro cache has non safe_load-able YAML entries.

 ❯ wget http://repositories.ros.org/rosdistro_cache/hydro-cache.yaml.gz
--2019-02-14 17:40:14--  http://repositories.ros.org/rosdistro_cache/hydro-cache.yaml.gz
Resolving repositories.ros.org (repositories.ros.org)... 52.53.127.253
Connecting to repositories.ros.org (repositories.ros.org)|52.53.127.253|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 325081 (317K) [application/x-gzip]
Saving to: ‘hydro-cache.yaml.gz’

hydro-cache.yaml.gz               100%[============================================================>] 317.46K  --.-KB/s    in 0.08s   

2019-02-14 17:40:14 (4.06 MB/s) - ‘hydro-cache.yaml.gz’ saved [325081/325081]
steven@octobeast:~[127] ❯ gunzip hydro-cache.yaml.gz 
steven@octobeast:~ ❯ grep ar_sys hydro-cache.yaml 
    ar_sys:
      doc: {type: git, url: 'https://github.com/Sahloul/ar_sys.git', version: hydro-devel}
      source: {type: git, url: 'https://github.com/Sahloul/ar_sys.git', version: hydro-devel}
    </package>\n", ar_sys: !!python/str "<?xml version=\"1.0\"?>\n<package>\n\t<name>ar_sys</name>\n\
    >http://wiki.ros.org/ar_sys</url>\n\t<author email=\"sahloul@race.u-tokyo.ac.jp\"\

My inclination would just be to disable the job since we’re not going to modify the hydro distribution cache and at least on the official farm Indigo is approaching its end of support.

cc @tfoote for their thoughts.