Closed Jos512 closed 7 years ago
Hi @Jos512, thanks for letting me know. It seems that I didn't take the old Wercker configuration into account when I made some recent changes to how Pygments is installed. My apologies, I'll release a fix soon. In the meantime what you can do is to add disable_pygments: true
below the flags you already have. This will ensure it skips the pygments installation completely and allow your build to succeed.
Also, just for your information, Hugo released a 0.18.1 bugfix release. It is unrelated to the issue you're having here, but you might want to use it anyway.
Thanks @ArjenSchwarz , for the quick response and information. With that flag the deploy works.
Thanks for thinking along, I'm already using 0.18.1. :smile:
A couple of days after this was reported, Wercker started sending out emails that they'll be closing down the old stacks soon and that everyone should migrate to the Docker configuration. Because of that, I've decided I'm not going to spend time on fixing this when nobody will be able to actually use that fix.
I've configured wercker like this:
Now I do not use Pygments in my website. However, the build fails due to a problem with that package:
The same problem also happens when downgrading to 0.17: