The RealPlayer-10.0.5.756-20050513 ebuild fails to download the rpm because of a missing certificate Reproducible: Always Steps to Reproduce: 1. emerge -f realplayer 2. 3. Actual Results: Calculating dependencies ...done! >>> emerge (1 of 1) media-video/realplayer-10.0.5 to / >>> Downloading https://helixcommunity.org/download.php/1343/RealPlayer-10.0.5.756-20050513.i586.rpm --22:06:22-- https://helixcommunity.org/download.php/1343/RealPlayer-10.0.5.756-20050513.i586.rpm => `/usr/portage/distfiles/RealPlayer-10.0.5.756-20050513.i586.rpm' Resolving helixcommunity.org... 207.188.25.135 Connecting to helixcommunity.org|207.188.25.135|:443... connected. ERROR: Certificate verification error for helixcommunity.org: unable to get local issuer certificate To connect to helixcommunity.org insecurely, use `--no-check-certificate'. Unable to establish SSL connection. !!! Couldn't download RealPlayer-10.0.5.756-20050513.i586.rpm. Aborting. !!! Fetch for /usr/portage/media-video/realplayer/realplayer-10.0.5.ebuild failed, continuing... !!! Some fetch errors were encountered. Please see above for details. Setting --no-check-certificate in FETCHCOMMAND fixes the problem. I realise this is a client configuration error (no local issuer certificate present), but shoudln't the ebuild contain instructions to create such a cert? Or let portage create a default cert for cases such as these and manage it transparently.
*** This bug has been marked as a duplicate of 101457 ***
