Clarified in the documentation of 4.2.
** Changed in: enblend
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384674
Title:
enblend running out of temp
An afterthought, much my trouble was caused because hugin did override a
valid TMPDIR enviroment variable even though I did not enter any value
for the tempdir in hugin GUI preferences..
Did not test if this still happens with newest hugin.
--
You received this bug notification because you are a
** Changed in: enblend
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384674
Title:
enblend running out of temp space: poor diagnostics and configuration
po
OK -- even at the danger of loosing focus let me
try to explain each your points.
> enblend-4.1.1-3.fc19.i686
The latest release in the Stable
Branch is 4.1.3. We are already preparing 4.1.4.
OTOH, the Development Branch of course holds
much more goodies.
> The TMPDIR ought also be men
Thank you both for your suggestions.
I am using enblend with the hugin frontend on Fedora.
enblend-4.1.1-3.fc19.i686
$ enblend -V
enblend 4.1.1
I noticed the 4.2 version in the mercurial repo appears to have more
verbose output and more documentation which would have helped a lot in
my case.
T
The environment variable `TMPDIR' controls the placement of temporary files
as documented in section "Tuning Memory Usage" of the Enblend and Enfuse
manuals.
The actual, assigned directory for the ImageCache can easily be inquired by
calling Enblend or Enfuse with the option pair `--verbose --vers
