poppler 0.51 fails to download

[leighmetcalf]

 Attempting to fetch poppler-0.51.0.tar.xz from http://sea.us.distfiles.macports.org/macports/distfiles/poppler

This fails for every site I have checked. Also, when I look at the repositories directly, only 0.50 is available, not 0.51. macports will not install new packages as it keeps trying to install poppler, whether or not the new packages need it.

[leighmetcalf]

main.log from attempt to install poppler

[mf2k (Frank Schima)]

The Milestone field is for use by Macports team members only, please do not set it. In the future, please use WikiFormatting, fill in the Port field and Cc the port maintainers (port info --maintainers poppler), if any.

[kencu (Ken)]

Thanks for the report. When this happens, you can download the file directly yourself if needed. It's a security issue based on an older security setup on your system, that will be worked out in time.

In your log, you see this:

poppler-0.51.0.tar.xz does not exist in /opt/local/var/macports/distfiles/poppler

so the file will go in /opt/local/var/macports/distfiles/poppler. Go there

cd /opt/local/var/macports/distfiles/poppler

now you need another way to download it. I like wget. You can also use a current web browser. install wget sudo port -v install wget. Hopefully that goes in smoothly.

Then look at your log for a source for the file that is _not_ macports. I see this one (and notice the failed security issue showing up):

notice:fetch --->  Attempting to fetch poppler-0.51.0.tar.xz from https://poppler.freedesktop.org/
debug:fetch Fetching distfile failed: Failed to connect to poppler.freedesktop.org port 443: Connection refused

now that you're in the proper folder, as noted above, and you know the name of the file, download it manually

sudo wget https://poppler.freedesktop.org/poppler-0.51.0.tar.xz

you will find that goes along with no troubles, and then you go back to your sudo port -v upgrade outdated.

if you find another security error, just do the same thing.

[mojca (Mojca Miklavec)]

I believe this has been resolved after automatic mirroring has ben deployed again.