Replies: 2 comments 1 reply
|
The (or at least an) answer seems to clearing the build cache. This is pretty clearly a bug somewhere, but clearing the cache lets me work past it. |
0 replies
|
@abingham Hi! This repository is for Heroku's next-generation Cloud Native Buildpacks (CNBs), which are currently in preview and not yet usable directly on Heroku. From the error message, this appears to be an issue with the existing generation buildpacks instead, and specifically with the Python buildpack. For issues like this I would either open a support ticket (https://help.heroku.com) or file an issue here: |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
This probably isn't a buildpack issue per se, but I don't know where else to start. It appears to be a problem (bug?) in codon, but I can't find a forum for that.
In short: I replaced a symlink in my repo with a normal file, and now my deployments fail with the error:
requirements.txtis the file that used to be a symlink and is now a file. Assuming this isn't the place to really deal with this issue, where can I go? Or if this is the right place, what do I do?All reactions