Skip to content

Instantly share code, notes, and snippets.

@donaldh

donaldh/proxy-env.sh

Created August 23, 2017 21:59
Show Gist options
  • Save donaldh/268495e892d566dcbfd7102daa603089 to your computer and use it in GitHub Desktop.
Save donaldh/268495e892d566dcbfd7102daa603089 to your computer and use it in GitHub Desktop.
Download ZIP
Building PNDA mirror behind proxy
Raw
proxy-env.sh
export http_proxy=http://proxy:80
export https_proxy=http://proxy:80
export JAVA_FLAGS="-Dhttp.proxyHost=proxy -Dhttp.proxyPort=80 -Dhttps.proxyHost=proxy -Dhttps.proxyPort=80 -Dhttp.nonProxyHosts=localhost,127.0.0.1,proxy"
export JAVA_OPTS="$JAVA_FLAGS"
export MAVEN_OPTS="$JAVA_FLAGS"
Raw
settings.xml
<settings>
<proxies>
<proxy>
<id>default</id>
<active>true</active>
<protocol>http</protocol>
<host>proxy</host>
<port>80</port>
</proxy>
</proxies>
</settings>
@donaldh
Copy link
Author

donaldh commented Sep 4, 2017 •
edited
Loading

python-carbon seems to get missed when building mirror_rpm

Yes, create_mirror_rpm.sh can completely miss rpms if the versions don't match. For example:

yumdownloader --resolve --archlist=x86_64 --destdir $RPM_REPO_DIR $RPM_PACKAGE_LIST
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirrors.usinternet.com
 * epel: mirrors.mit.edu
 * extras: repo1.sea.innoscale.net
 * updates: repo1.sea.innoscale.net
No Match for argument redis-3.2.3-1.el7
...

Script continues past this.

@donaldh
Copy link
Author

donaldh commented Sep 4, 2017

As reported by the create_mirror script the create_mirror_rpm script is very problematic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment