handle release-upgrades (texlive 2012 -> 2013) about heroku-buildpack-tex HOT 12 CLOSED

+1 not sure how to fix this.

from heroku-buildpack-tex.

more exact, this could be two cases:

1. upgrade to 2014 when we have a release
2. (perhaps) upgrade from a 2012-version created by https://github.com/holiture/heroku-buildpack-tex

from heroku-buildpack-tex.

As it stands doing an install with this buildpack, I get the "your current version is too old(2012)" Im not sure how to get past this and install this build pack. It has all I need, hopefully you can help.

from heroku-buildpack-tex.

that is number 2 ;)

When you use multipack , you can just add heroku-buildpack-clearcache once to clear your buildpack-cache.
Then all will be fine.

from heroku-buildpack-tex.

I'm running into a similar issue because tlmgr wants version 2014 now and my repository seems to come with 2012:

=====> Detected Framework: TeX Live
-----> compiling wget
       download
       configure
       make
       make install
tlmgr: The TeX Live versions supported by the repository
  (2014--2014)
do not include the version of the local installation
  (2012).
 !     Push rejected, failed to compile Multipack app

Any idea how to solve this? If wget downloads TeX Live from ctan.org (see TEXLIVE_INSTALLER_URL which is defined in bin/compile), that should actually be the latest version (2014) of TeX Live already, shouldn't it? What's wrong here?

Can anybody help?

from heroku-buildpack-tex.

@mwaclawek do you want to keep the old version or upgrade?

from heroku-buildpack-tex.

@syphar What do you think? I didn't know how to update as I thought that URL should already be the latest TeX Live. So here's a pull request to keep the current version.

If you can make the buildpack update, that's fine as well.

from heroku-buildpack-tex.

@mwaclawek you can just get to the most up-to-date version by clearing the buildpack cache (see this #1 (comment)).

I have to think about a better upgrade path and possibly a way to either keep old versions or upgrade ...

Thanks for the PR, didn't know about this option.

from heroku-buildpack-tex.

@syphar Tried clearing the cache, didn't work. Maybe there's something that this buildpack does not clear?

Upgrading would give us the most recent version. But hardcoding the version as I did in the pull request prevents the buildpack from breaking every 12 months. Maybe we should do that with version 2013 or 2014 then.

from heroku-buildpack-tex.

works currently by clearing the cache.

Hardcoding the year won't be a solution to me. Of course the buildback will continue to work, but it will be an old version of texlive without any fixes.

Happy to review and merge a PR if there is a good solution to this.

from heroku-buildpack-tex.

I'm new to the ruby stack and so I apologize if I misunderstood a step, however I cleared the cache as suggested and still am having this issue.

While trying to deploy, this is my .buildpacks file:

https://github.com/heroku/heroku-buildpack-ruby.git
https://github.com/perplexes/heroku-buildpack-clearcache
https://github.com/peterkeen/heroku-buildpack-vendorbinaries.git
https://github.com/Thermondo/heroku-buildpack-tex.git

For the vendorbinaries, I'm using the following vendor_urls to get pandoc:

https://s3.amazonaws.com/docverter-binaries/pandoc-1.12.0.2.tar.gz
https://s3.amazonaws.com/docverter-binaries/pandoc-templates-1.12.0.2.tar.gz

However, when I push to heroku I watch it remove the cache of all the gems and then get the following error:

remote: removed directory: ‘/app/tmp/cache/vendor’
remote: =====> Downloading Buildpack: https://github.com/peterkeen/heroku-buildpack-vendorbinaries.git
remote: =====> Detected Framework: VendorBinaries
remote: -----> Found a .vendor_urls file
remote:        Vendoring https://s3.amazonaws.com/docverter-binaries/pandoc-1.12.0.2.tar.gz
remote: =====> Downloading Buildpack: https://github.com/Thermondo/heroku-buildpack-tex.git
remote: =====> Detected Framework: TeX Live
remote: tlmgr: The TeX Live versions supported by the repository
remote:   (2013--2015)
remote: do not include the version of the local installation
remote:   (2012).
remote:  !     Push rejected, failed to compile Multipack app
remote:
remote: Verifying deploy....
remote:
remote: !   Push rejected to factotum.
remote:

Am I misunderstanding something here?

from heroku-buildpack-tex.

clearing the buildpack cache should be done only on the command line (see http://stackoverflow.com/questions/14368027/how-can-i-flush-the-heroku-buildpack-cache-dir)

not in the .buildpacks file

from heroku-buildpack-tex.