Hi again, Maxim Cournoyer <maxim.courno...@gmail.com> writes:
> Hello Maxime, > > Maxime Devos <maximede...@telenet.be> writes: > >> Maxim Cournoyer schreef op za 11-06-2022 om 01:53 [-0400]: >>> I don't get it; how can the service runs fine in the instrumented VMs >>> the system tests use, and fail in my updated machine? Could it be a >>> fault in 'guix deploy'? >> >> Maybe the shepherd has the old (gnu build jami-service) module loaded >> and it doesn't know know to reload modules during reconfiguration? I verified that in the /gnu/store/fyd7rmvzhhqbk1f08c4pl7ahhlfgig40-shepherd-jami.scm file it was setting up the load path with everything needed, such as --8<---------------cut here---------------start------------->8--- (eval-when (expand load eval) (let ((extensions (quote ("/gnu/store/f6q4237n62lq7n8z3qyh3jx5iinb9myr-guile-packrat-0.1.1" "/gnu/store/l2f9gmd64w56nnhnlb63hg8f5crfvwln-guile-ac-d-bus-1.0.0-beta.0" "/gnu/store/is9f6ki7i2f6qk80ivvz7q1vvlibb96l-guile-fibers-1.0.0"))) (prepend (lambda (items lst) (let loop ((items items) (lst lst)) (if (null? items) lst (loop (cdr items) (cons (car items) (delete (car items) lst)))))))) (set! %load-path (prepend (cons "/gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import" (map (lambda (extension) (string-append extension "/share/guile/site/" (effective-version))) extensions)) %load-path)) (set! %load-compiled-path (prepend (cons "/gnu/store/zqgpayc87lfmcmncgzbp5v59hav8ww1c-module-import-compiled" (map (lambda (extension) (string-append extension "/lib/guile/" (effective-version) "/site-ccache")) extensions)) %load-compiled-path)))) --8<---------------cut here---------------end--------------->8--- The /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import directory contains: --8<---------------cut here---------------start------------->8--- $ find /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/build /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/build/dbus-service.scm /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/build/file-systems.scm /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/build/jami-service.scm /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/build/linux-container.scm /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/build/shepherd.scm /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/system /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/system/file-systems.scm /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/gnu/system/uuid.scm /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/build /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/build/bournish.scm /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/build/syscalls.scm /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/build/utils.scm /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/colors.scm /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/i18n.scm /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/profiling.scm /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/diagnostics.scm /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/memoization.scm /gnu/store/7kgdg6dmgncqirj3k07n02hq6kjyf4an-module-import/guix/records.scm --8<---------------cut here---------------end--------------->8--- and the referenced [...]/gnu/build/jami-service.scm file does contain the supposedly missing 'jami-service-available?' procedure. I'm suspecting that given the service makes use of Shepherd 0.9 features, perhaps it fails loading and the error is reported erroneously that way... a reboot would tell but I'm not in a position to do that at this moment (remote machine). Thanks, Maxim