Can't use local deb binaries on a readonly testbed
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | autopkgtest (Ubuntu) |
Wishlist
|
Unassigned | ||
Bug Description
In the ubuntu-ota-tests project, the debian/control defines a python package python3-
If we run
$ adt-run --unbuilt-tree . --- ssh -s adb
We will get:
dpkg-buildpackage: error: fakeroot not found, either install the fakeroot
package, specify a command with the -r option, or run this as root
blame: .
badpkg: rules build failed with exit code 2
adt-run [09:57:07]: ERROR: erroneous package: rules build failed with exit code 2
Exit request sent.
If we run:
$ bzr bd --result-dir=/tmp -- -uc -us
$ adt-run --binary /tmp/python3-
We will get:
sh: 1: cannot create /etc/apt/
Exit request sent.
<VirtSubproc>: failure: copydown destination failed, status 2
adt-run [09:49:48]: ERROR: testbed failed: cannot send to testbed: ['BrokenPipeError: [Errno 32] Broken pipe\n']
I think the right solution for this case is the second one, using a built-tree, and send the deb to the testbed. So what we are missing is to install those debs in the tmp directory just as the rest of dependencies.
| Leo Arias (elopio) wrote : | #1 |
| Barry Warsaw (barry) wrote : | #2 |
Of course, when we reuse python3-
| Leo Arias (elopio) wrote : | #3 |
Another possible workaround is to make the device writable, install fakeroot, and then make it read-only again. This is not ideal of course, as we want to keep the device read-only. I'm just mentioning it, but don't try it at home.
| Leo Arias (elopio) wrote : | #4 |
Making the device writable and installing all the packages required for the build is not an option either. In the end we get the same error as when we build the package on the host:
sh: 1: cannot create /etc/apt/
| summary: |
- Can't run tests that require build in a readonly testbed + Can't use local deb binaries on a readonly testbed |
| Changed in autopkgtest (Ubuntu): | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| Changed in autopkgtest (Ubuntu): | |
| assignee: | nobody → Martin Pitt (pitti) |
| Changed in autopkgtest (Ubuntu): | |
| assignee: | Martin Pitt (pitti) → nobody |


We can use some workarounds, like hack the PYTHONPATH, or cd into the directory that has the python package, so it will be found in the cwd. We might need both things for some tests.
What will make the tests easier is just to have it installed.