> No. Tests, just like package builds, should not assume that they will
> run on an empty system. Please file bugs, ideally in Debian, when that
> doesn't happen. If necessary I'll propose a change to the README to make
> this clear.
this is a rather arrogant attitude.
- There is no documentation what autopkg tests can assume. Telling people what they cannot assume without telling them what they can assume is not a productive way forward.
- Debian only runs autopkg tests on amd64, the likeliness getting any patch accepted without telling expectations on the testbed and without having a way for Debian to reproduce an issue, is not very high.
Proposing just a README change without any other communication is no way forward.
> No. Tests, just like package builds, should not assume that they will
> run on an empty system. Please file bugs, ideally in Debian, when that
> doesn't happen. If necessary I'll propose a change to the README to make
> this clear.
this is a rather arrogant attitude.
- There is no documentation what autopkg tests can assume. Telling people what they cannot assume without telling them what they can assume is not a productive way forward.
- Debian only runs autopkg tests on amd64, the likeliness getting any patch accepted without telling expectations on the testbed and without having a way for Debian to reproduce an issue, is not very high.
Proposing just a README change without any other communication is no way forward.
Disappointed, Matthias