On Thu, Jul 23, 2020 at 04:44:08PM -0400, Leo Famulari wrote: > This should be fixed with commit > 5f63905096e456097fca206f56ce9257f72faf64 That commit actually broke `guix pull` as shown below. Sorry! ------ Backtrace: In ice-9/boot-9.scm: 222:29 19 (map1 _) 222:29 18 (map1 _) 222:29 17 (map1 _) 222:29 16 (map1 _) 222:17 15 (map1 (((gnu packages kde)) ((gnu packages libevent)) ((gnu packages libidn)) ((gnu packages #)) ((?)) ?)) 3297:17 14 (resolve-interface (gnu packages kde) #:select _ #:hide _ #:prefix _ #:renamer _ #:version _) In ice-9/threads.scm: 390:8 13 (_ _) In ice-9/boot-9.scm: 3223:13 12 (_) In ice-9/threads.scm: 390:8 11 (_ _) In ice-9/boot-9.scm: 3507:20 10 (_) 2806:4 9 (save-module-excursion _) 3527:26 8 (_) In unknown file: 7 (primitive-load-path "gnu/packages/kde" #) In ice-9/eval.scm: 626:19 6 (_ #) 293:34 5 (_ #) 173:47 4 (_ #(# #)) 159:9 3 (_ #(# #)) 191:35 2 (_ #(# #)) 223:20 1 (proc #(# #)) In unknown file: 0 (%resolve-variable (7 . qtbase) #) ERROR: In procedure %resolve-variable: error: qtbase: unbound variable ------ I fixed it by moving qtbase-for-krita package to (gnu packages qt) and pushed as 0448bfe2d769998ba33c288a07738e13b02113a4. I'm not sure exactly what's wrong but my hunch is that there is a module dependency cycle.