piotras / heroku-buildpack-gettext Goto Github PK

When used together with heroku/python buildpack to build a Django-based project, it has to be set as the first buildpack in order to handle correctly the Django's compilemessages command.

The issue is related to the fact at that moment no others buildpacks have already created the .heroku folder so the buildpack fails to install gettext.

...

-----> Installing gettext...
remote: tar: /tmp/build/.heroku: Cannot open: No such file or directory

Hi,

This is a question, not a bug .

I installed Buildpacks, but I have a question, how to use the command compilemessages after install Buildpacks .

Thanks
Addo

GNU gettext is now part of the heroku-16:build image, see
heroku/base-images#90

Hi,
I tried to use your buildpack for Django Translation/Internationalization and here is error I get during deploy:

remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Fetching set buildpack https://github.com/piotras/heroku-buildpack-gettext.git... done
remote: -----> Gettext library app detected
remote: -----> Installing gettext...
remote: -----> done in /app/gettext
remote: -----> Using set buildpack heroku/python
remote: -----> Python app detected
remote: $ pip install -r requirements.txt
remote:
remote: $ python manage.py collectstatic --noinput
remote: 56 static files copied to '/app/hpqr/staticfiles', 1 unmodified,
8 post-processed.
remote:
remote: -----> Running post-compile hook
remote: CommandError: Can't find msgfmt. Make sure you have GNU gettext tools 0.
15 or newer installed.

>heroku buildpacks
=== .... Buildpack URLs
1. https://github.com/piotras/heroku-buildpack-gettext.git
2. heroku/python

bin/post_compile looks like this:

python manage.py compilemessages
python manage.py collectstatic --noinput

My name is Jon Byrum and I’m a product manager at Heroku. Your buildpack is one of the top 200 most popular buildpacks on Heroku!

I would like to invite you to publish your buildpack early in our Buildpack Registry, before it is made available to the general public (expected early July).

To register your buildpack, visit: https://addons-next.heroku.com/buildpacks
Documentation: https://devcenter.heroku.com/articles/buildpack-registry

Why register?

• By registering early you’ll be able to grab your preferred namespace for the buildpack
• After registering, your buildpack will be available to all Heroku users when they run heroku buildpacks:search. In the future, we will only display registered buildpacks on elements.heroku.com/buildpacks
• The Buildpack Registry makes it easy for you to publish a new version of your buildpack, as well as roll back if there are errors

Recommended naming conventions:

• We recommend that you use the same namespace (e.g., jbyrum) with Buildpack Registry that you use on GitHub
• In general, avoid using "buildpack" in the name of your registered buildpack
  • For example: If your Github repo is github.com/foobar/heroku-buildpack-elixir, then we recommend a name like "foobar/elixir"

It would be greatly appreciated if you could publish before June 18th, as we prepare to make the feature publicly available. Registering a buildpack should take approximately 5 minutes.

If you have any questions about registering (or run into any issues), please email:
[email protected]

We're getting the following failures trying to deploy an Heroku app using this buildpack

remote: =====> Downloading Buildpack: https://github.com/piotras/heroku-buildpack-gettext
remote: =====> Detected Framework: Gettext library
remote: -----> Installing gettext...
remote: 
remote: gzip: stdin: not in gzip format
remote: tar: Child returned status 1
remote: tar: Exiting with failure status due to previous errors
remote: 
remote:  !     Push rejected, failed to compile Multipack app

This looks to be because https://s3-eu-west-1.amazonaws.com/midgard-heroku/gettext.tar.gz gives

<Error><Code>AllAccessDisabled</Code><Message>All access to this object has been disabled</Message><RequestId>E31CCE48B62CAA05</RequestId><HostId>B4g1o/69P3Efb58iqkirXk73BAJtC7y48gZztb6NuoV3F9ZeX4Al9dkU6J8SmUMTnAFBnog+YYU=</HostId></Error>

We're using this in production so this is blocking our deploys.
Can you fix, or upload the tarball to another location so we can refer to it in another buildpack?