Re: Using Salsa-CI as pre-upload QA for Bullseye and Buster uploads: Lintian and Piuparts
Re-trying the Salsa CI again with the simple libarchive/buster package
(after getting frustrated with mailman/stretch errors a few months ago),
I note that:
- the piuparts job was flacky and needed a restart
- the test-crossbuild-arm64 doesn't seem compatible with buster (using
the new 'apt-get satisfy' command, for reasons I can't debug because of
a redacted "collapsed multi-line command" even in the raw log;
maybe it could written in a buster-compatible way, or otherwise just
dropped for buster because it's confusing.
My $0.02 :)
Debian LTS Team
On 14/11/2022 19:08, Abhijith PA wrote:
On 14/11/22 01:56 PM, Sylvain Beucler wrote:
On 12/11/2022 22:31, Otto Kekäläinen wrote:
I was wondering how common is it for DDs to use Salsa-CI while doing
quality assurance prior to Bullseye and Buster uploads?
I personally tend to run initial builds and dep-8 tests locally, because
when they fail, I have to re-run them manually to properly debug and fix the
(not to mention additional manual tests)
Same for me.
Also I do my LTS (security) work in a VM without access to my Debian
credentials (gpg, ssh) so I can e.g. run various vulnerability PoCs and
exploits with a reasonable peace of mind; which makes it inconvenient to
push to Salsa.
I have custom(tools to share clipboard from host etc) live image
that I run on QEMU (via libvirt commands) for testing PoCs, exploits
and final build.