Bug#983367: gvfs: autopkg test always fails on qemu testbed

[Ryutaroh Matsumoto]

Hi Simon,
Thank you very much for the explanation.
Previously reported another issue to src:libnfs
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983362
seems to be caused by the same machanism.

Should #983362 and #983367 be merged and reassigned to autopkgtest?

Bes regards, Ryutaroh

From: Simon McVittie <smcv at debian.org>
Subject: Re: Bug#983367: gvfs: autopkg test always fails on qemu testbed
Date: Tue, 23 Feb 2021 08:39:16 +0000

> On Tue, 23 Feb 2021 at 11:20:49 +0900, Ryutaroh Matsumoto wrote:
>> I made an autopkg qemu testbed by debci setup -f -s sid -a amd64 -b qemu.
>> Then I run autopkgtest -B -U -u debci gvfs -- qemu
>> It always fails with
> ...
>> sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
>> sudo: a password is required
> 
> This test needs to run as an ordinary user who can sudo, and autopkgtest
> doesn't support that. Just running as root doesn't work: the gvfs tests
> expect to run in an ordinary user's login session, so that the gvfs
> daemons themselves run as that user, but the test escalates privileges to
> root to set up things like Samba to test against.
> 
> I'm told this works in Ubuntu, because Ubuntu runs tests in cloud images
> with passwordless sudo available for the 'ubuntu' user by default.
> 
> We probably need a new needs-sudo restriction that will make autopkgtest
> set up the ordinary user to have passwordless sudo.
> 
>     smcv