Your message dated Tue, 21 Aug 2018 20:57:37 +0200
with message-id <09a5d4a6-f993-3c7c-7440-47093ea7e...@debian.org>
and subject line Re: Bug#904870: fixed in autopkgtest 5.4.2?
has caused the Debian Bug report #904870,
regarding autopkgtest: calls su with an empty username, thus fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
904870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: autopkgtest
Version: 5.4.1
Severity: grave
Justification: renders package unusable
Dear autopkgtest Maintainers,
In various situations autopkgtest calls /bin/su with an empty string for
the username. The old su (from login) ignored this, but newer su
versions (from util-linux 2.32-0.2) do not accept this, and abort.
Personally I think autopkgtest got lucky that this worked before, but
this probably was not a valid thing to do.
One of the affected lines:
https://sources.debian.org/src/autopkgtest/5.4.1/lib/adt_testbed.py/#L1096
Example output from autopkgtest:
autopkgtest [15:52:36]: test supported-algos: [-----------------------
su: user does not exist
autopkgtest [15:52:36]: test supported-algos: -----------------------]
Unexpected error:
Traceback (most recent call last):
File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 717, in mainloop
command()
File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 646, in command
r = f(c, ce)
File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 584, in cmd_copyup
copyupdown(c, ce, True)
File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 469, in copyupdown
copyupdown_internal(ce[0], c[1:], upp)
File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 494, in
copyupdown_internal
copyup_shareddir(sd[0], sd[1], dirsp, downtmp_host)
File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 408, in
copyup_shareddir
shutil.copy(tb, host)
File "/usr/lib/python3.6/shutil.py", line 241, in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
File "/usr/lib/python3.6/shutil.py", line 120, in copyfile
with open(src, 'rb') as fsrc:
FileNotFoundError: [Errno 2] No such file or directory:
'/tmp/autopkgtest.zwqy11/supported-algos-stdout'
autopkgtest [15:52:36]: ERROR: testbed failure: cannot send to testbed:
[Errno 32] Broken pipe
autopkgtest [15:52:36]: Binaries: resetting testbed apt configuration
Note that tests that say "Restrictions: needs-root" do not appear to hit
those code paths.
I might try to come up with a patch if no one beats me to it.
Chris
--- End Message ---
--- Begin Message ---
Version: 5.4.2
On 21-08-18 14:23, Nicholas D Steeves wrote:
> Control: reopen -1
> I ran into this just now with autopkgtest 5.5 (inside LXC, or schroot)
> when the host system is using either 4.4 or 5.4.1~bpo9+2.
Yes, the bug is still present in 4.4 and 5.4.1~bpo9+2 as the BTS will
happily tell you. It is the host autopkgtest that provides the commands.
autopkgtest inside the LXC or whatever doesn't do anything and is
completely useless to have that installed, unless you are testing
autopkgtest itself or need it as a dependency for you test.
> Will this be solved if 5.5 is backported?
If you update the host to use that, yes.
> As a consequence, does this
> also mean all stretch systems with sid autopkgtest chroots must switch
> to using backported autopkgtests?
I guess so. There is nothing we can do about that. But it is good that
you remind us of the missing backports. I'll try to upload it tonight.
Paul
signature.asc
Description: OpenPGP digital signature
--- End Message ---
