- Package:
- supervisor
- Source:
- supervisor
- Submitter:
- Steve Langasek
- Date:
- 2019-11-05 22:09:03 UTC
- Severity:
- minor
Package: supervisor Version: 4.1.0-1 Severity: minor Tags: patch User: ubuntu-devel@lists.ubuntu.com Usertags: origin-ubuntu focal ubuntu-patch Dear maintainers, The supervisor package currently build-depends on python3-all, which causes its test suite to be run at build time against all supported versions of python3. This is unnecessary, since supervisor is an application package and will only ever be used at runtime against the current version of python3. The only reason I noticed this is because python3.8 has been added as a supported, non-default version of python3 in Ubuntu, and supervisor 4.0.4 was not compatible with python3.8. I'd suggest the attach patch, to avoid the build failing in the future on build-time tests that are not relevant to the functioning of the binary package. Cheers,
FWIW, I disagree on this patch. I think this is exactly what one would want. The test failure provides awareness of an incompatibility. The sooner the better. I don't think there's benefit to waiting until the default is changed to discover this. Scott K
Hello Steve, build-time I see that you decided to upload 4.1.0u1 to Ubuntu before syncing 4.1.0-1 from Debian, if you look at the upstream changelog, you will notice that 4.1.0 solved some python 3.8 issue, did you check if this solved the compatibility issue you detected before doing the u1 upload? I would recommend checking if that's not the case, and if not, I would be happy to forward the issue (or maybe even patch it) upstream, so I appreciate if you could help me understand how the issue was detected and how I can navigate through Ubuntu's QA myself, I would gladly help reducing the delta between the distros. Regards,
Yes, 4.1.0 does build with python3.8, which I discovered in the process of trying to prepare a fixed build for 4.0.4 (the current package at the time I started). I went ahead anyway with submitting this bug because I think it's still per se correct to only build-depend on python3 here instead of python3-all, regardless of whether the new upstream version happens to be compatible with python3.8. Cheers,