tag 648148 pending thanks Hello all,
Ian Jackson [2012-06-11 1:55 +0100]: > Hi. Martin, you wrote: > > for testing build recipes I'd like to skip all the apt parts and run > > adt-run as normal user. This currently fails because it always tries > > to set up apt. > > I agree that this would be sensible. But I think the right answer is > to make this depend on the `root-on-testbed' testbed capability, not > on opts.user. As for the apt parts, autopkgtest was already fixed to not do the binary publishing unless it actually had something to publish. As for installing test depends, running as user with -null only really works for the trivial case of empty Depends:; arguably this isn't very interesting, but if we can't install dependencies then we can't run the test. As a corner case, it should be possible to detect that all dependencies are already installed and we don't install built binaries, but pbuilder-satisfy-dependencies doesn't support this. In short, in this situation it is easier to just run debian/tests/foo by hand and skip adt-run completely. In all others, it's not a biggie to run it with the -schroot runner (which works fine as user) or through sudo, so I don't care enough about this corner case to write lots of code around it. One remaining wart is this: $ adt-run ./ -d --- adt-virt-null [...] adt-run: & tree0t-s: [---------------------------------------- su: must be run from a terminal adt-run1: testbed executing test finished with exit status 1 That's easy to fix with what you mention (bind it to root-on-testbed): https://gitorious.org/autopkgtest/autopkgtest/commit/7d191312 (temporary clone of the git repo while alioth is offline) That's about as far as I'd like to go, so closing with above commit. Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
