On Thu, Dec 01, 2022 at 01:02:45PM +0100, Paul Gevers wrote: > And right after hitting the send button I realized that my reasoning is at > least partially flawed. The testbed will always update glibc, because the > testbed is build from testing, and glibc hasn't migrated yet. Still, it's a > weird pattern.
Is there still something that sudo can do here? I fixed an issue in the ldap autopkgtest¹ recently, but your logs looks like the test gets further than the place where this issue errors out. Would more output in the test help? What is the canonical way to write a test that can have its verbosity turned up for debugging, how is this wish communicated to a system that runs the tests in an automated way? Can a mere mortal DD run an autopkgtest on a porterbox? Greetings Marc
