Rafael
* Santiago Vila <sanv...@debian.org> [2023-12-15 12:59]:
El 13/12/23 a las 9:27, Rafael Laboissière escribió:
i.e. you may rely on a writable $HOME if it's for a "good cause" (i.e.
dh_auto_test).
So, the simple question: Should this not be also implemented in dh_octave_check
as well, which is what octave-vibes was using?
Thanks for bringing this to my knowledge. However, I do not quite understand
the text above. Does it mean that, when the package Build-Depends on
debhelper-compat = 13, then $HOME will be set automatically to a writable
directory? Well, octave-vibes that compatibility level of debhelper, but the
autobuilders set HOME=/nonexistent/.
Sorry, I don't really know for sure.
I just remember this case where the debhelper feature allowed for an "easy" fix:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025654
There is something that I definitively do not understand here. Let's
take your build log for octave-vibes:
https://people.debian.org/~sanvila/build-logs/202312/octave-vibes_0.2.0-8_amd64-20231205T162533.194Z
We see that debhelper-compat = 13 is used (line #76) in the build.
However, we see the following in line #3199:
User Environment
----------------
[…]
HOME=/sbuild-nonexistent
[…]
It seems that your building system is setting HOME to an non-existent
directory. How do you explain that ?
Best,
Rafael
