Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #15002
| From | Simon McVittie <smcv@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Unittests writing to HOME (backintime) |
| Date | 2023-03-29 13:10 +0200 |
| Message-ID | <GeBQJ-fVcI-5@gated-at.bofh.it> (permalink) |
| References | <GeySS-fT6i-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, 29 Mar 2023 at 07:52:35 +0000, c.buhtz@posteo.jp wrote:
> My question now is why newer version of this package are uploaded then? I
> couldn't find that the tests where deactivated. Maybe this "disabled on
> Debian auto-builders" is outdated and today it is possible to write to HOME
> during build?
In compat level 13, debhelper will set $HOME to a temporary directory
during the build (see #942111).
The user's "official" home directory in the system user database
(getent passwd $(id -u) | cut -d: -f6) is still set to a directory that
does't exist (/nonexistent) on the official buildds.
>From an upstream point of view it's still bad for unit tests to do
anything destructive in $HOME, because upstream developers who run the
unit tests won't want their data destroyed, but it's harmless to do
non-destructive things like writing to ~/.cache.
smcv
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Unittests writing to HOME (backintime) c.buhtz@posteo.jp - 2023-03-29 10:00 +0200
Re: Unittests writing to HOME (backintime) Andrey Rakhmatullin <wrar@wrar.name> - 2023-03-29 11:50 +0200
Re: Unittests writing to HOME (backintime) c.buhtz@posteo.jp - 2023-03-29 12:10 +0200
Re: Unittests writing to HOME (backintime) Andrey Rakhmatullin <wrar@wrar.name> - 2023-03-29 15:10 +0200
Re: Unittests writing to HOME (backintime) buhtz@posteo.de - 2023-03-29 12:30 +0200
Re: Unittests writing to HOME (backintime) Simon McVittie <smcv@debian.org> - 2023-03-29 13:10 +0200
csiph-web