I assume this topic is not specific to one package but to the whole python packaging universe.As the software doesn't use a discoverabe build system the package needs
There is "backintime" which unittests do write to $HOME. I'm one of the new upstream maintainers and know that this isn't a good idea. It will take time to fix this.
About that problem there is a debian bug report nearly 4 years old
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940319
It tells that this is a problem because writing to HOME during build "is disabled on Debian auto-builders".
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 onNo.
Debian auto-builders" is outdated and today it is possible to write to HOME during build?
The usual solution is AFAIK to set a temporary $HOME inside d/rules
though.
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?
From an upstream point of view it's still bad for unit tests to doanything destructive in $HOME, because upstream developers who run the
The usual solution is AFAIK to set a temporary $HOME inside d/rules
though.
This means you've missed my explanation.The usual solution is AFAIK to set a temporary $HOME inside d/rules
though.
I was looking into https://salsa.debian.org/jmw/pkg-backintime/-/blob/debian/debian/rules
I don't see creation of a HOME or deactivation of a test.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 350 |
Nodes: | 16 (2 / 14) |
Uptime: | 09:43:44 |
Calls: | 7,625 |
Files: | 12,793 |
Messages: | 5,686,483 |