Bug #17592
iuk: missing packages in buster
100%
Description
Ditto as Bug #17591 but this time for iuk’s test suite:
[DZ] folding deprecated options (module_finder, script_finder) into finder
[DZ] building distribution under .build/lopzvjvvfl for installation
[DZ] beginning to build Tails-IUK
[@Filter/ExtraTests] rewriting author test xt/author/critic.t
[@Filter/ExtraTests] rewriting author test xt/author/pod-syntax.t
[@Filter/ExtraTests] rewriting author test xt/author/no-tabs.t
[DZ] writing Tails-IUK in .build/lopzvjvvfl
Checking prerequisites...
test_requires:
! HTTP::Server::Simple::Static is not installed
! Sys::Filesystem is not installed
! Test::BDD::Cucumber is not installed
! Test::Fatal is not installed
! Test::Spec is not installed
ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the versions
of the modules indicated above before proceeding with this installation
Run 'Build installdeps' to install missing prerequisites.
[ skipped detailed output of detailed test failures ]
This is better once those packages are installed:
libhttp-server-simple-static-perl
libsys-filesystem-perl
libtest-bdd-cucumber-perl
libtest-fatal-perl
libtest-spec-perl
but I’m seeing failures due to a missing getfattr
command and due to a missing tails-transform-mirror-url
command. The former is fixed by installing the extra attr
package; the latter might be due to PATH
being set to include submodules/mirror-pool-dispatcher/bin
, which might then be reset when sudo
comes into play?
Files
Subtasks
History
#1 Updated by intrigeri 2020-04-05 06:24:04
Hi,
I’ve fixed the missing test suite deps on the topic branch.
I’ll submit for review once I have looked into Bug #17590.
> but I’m seeing failures due to […] a missing tails-transform-mirror-url
command. […] the latter might be due to PATH
being set to include submodules/mirror-pool-dispatcher/bin
, which might then be reset when sudo
comes into play?
I can’t reproduce this. May you please:
- verify that
submodules/mirror-pool-dispatcher/bin
does exist (just in casegit submodule update --init
was missed — we’re all humans :) - report this on a dedicated issue (so we can close this very issue without blocking on that other problem), including the output you see
?
#2 Updated by intrigeri 2020-04-05 06:37:22
- Status changed from Confirmed to In Progress
Applied in changeset commit:tails|fea8dd3d6d7711e0d271493551ec90454473bb4d.
#3 Updated by intrigeri 2020-04-05 06:38:14
- Status changed from In Progress to Needs Validation
- Assignee changed from intrigeri to CyrilBrulebois
- Target version set to Tails_4.5
- Feature Branch set to bugfix/17590-perl-test-suites-deps
#4 Updated by intrigeri 2020-04-05 06:40:10
- blocks Feature #16209: Core work: Foundations Team added
#5 Updated by CyrilBrulebois 2020-04-06 06:19:57
- File tails-iuk.log added
It might make sense to keep the issue here actually?
Checking the PATH set, and calling the script directly with the full path:
kibi@hamburg:~/work/clients/tails/release/master-checkout/config/chroot_local-includes/usr/src/iuk$ ${TAILS_GIT_CHECKOUT}/submodules/mirror-pool-dispatcher/bin/tails-transform-mirror-url
-bash: /home/kibi/work/clients/tails/release/release-checkout/submodules/mirror-pool-dispatcher/bin/tails-transform-mirror-url: /usr/bin/nodejs: bad interpreter: No such file or directory
nodejs
seems to only be listed in config/chroot_local-packageslists/tails-common.list
(but this might bring us back to the previous topic, as in: the test suite makes most sense in a Tails-like setup? Documenting that extra package shouldn’t be a big deal though).
With that extra package installed, the whole test suite (with overlayfs
) passes!
Log attached in case you’re curious about the few warning messages I’m seeing (and possible leftovers in temporary directories, I didn’t double check).
#6 Updated by intrigeri 2020-04-06 14:20:29
- Target version changed from Tails_4.5 to Tails_4.6
#7 Updated by intrigeri 2020-04-22 15:05:18
CyrilBrulebois wrote:
> Checking the PATH set, and calling the script directly with the full path:
>
> […]
>
> nodejs
seems to only be listed in config/chroot_local-packageslists/tails-common.list
(but this might bring us back to the previous topic, as in: the test suite makes most sense in a Tails-like setup? Documenting that extra package shouldn’t be a big deal though).
Good catch! Fixed in commit:96565e889e956cef35014cc1ce64738934d1eebd
#8 Updated by intrigeri 2020-04-22 15:05:56
- Status changed from Needs Validation to Resolved
- % Done changed from 0 to 100
Applied in changeset commit:tails|0b8505045f7055ac2ec52d0c264533dd53442a84.