bug#48945: PostgreSQL + Cuirass Errors
Hi, Is there any update about this issue? I receive same "division by zero" error after running cuirass for a while. deleting the records with `starttime` equal to 0 from `builds` table, cuirass could start again. but the issue happens again after a while. -- Reza Alizadeh Majd PantherX Team https://pantherx.org
bug#44463: Skeleton files in sub-directories are not writable
Hi Guix,
trying to add a new skeleton file in a sub-directory in newly created
users home, skeleton files add in read-only mode.
since there shouldn't be any difference between adding a skeleton file
in user home directory, or in a sub-directory under user's home, I
assume this might be a bug related to skeleton file creation.
following configuration could be used to reproduce this issue:
--8<---cut here---start->8---
(use-modules (gnu))
(define (test-skeletons)
(append
`(("test" ,(computed-file
"test"
(with-imported-modules '((guix build utils))
#~(begin
(use-modules (guix build utils))
(mkdir-p #$output)
("foo" ,(plain-file "foo" "foo is writable"))
("test/bar" ,(plain-file "bar" "bar is read-only")))
(default-skeletons)))
(operating-system
(host-name "guix.test")
(timezone "Asia/Tehran")
(locale "en_US.utf8")
(bootloader (bootloader-configuration
(bootloader grub-bootloader)
(target "/dev/sda")))
(file-systems (cons (file-system
(device (file-system-label "my-root"))
(mount-point "/")
(type "ext4"))
%base-file-systems))
(skeletons (test-skeletons)))
--8<---cut here---end--->8---
generated skeleton files status:
--8<---cut here---start->8---
root@guix ~# ll
total 4
-rw-r--r-- 1 root root 15 Nov 5 14:05 foo
-rw-r--r-- 2 root root 15 Nov 5 14:05 test/
root@guix ~# ll
-r--r--r-- 1 root root 15 Nov 5 14:05 bar
--8<---cut here---end--->8---
Regards,
Reza
--
Reza Alizadeh Majd
PantherX Team
https://www.pantherx.org/
bug#41847: qTox build failure
On Sun, 14 Jun 2020 14:30:56 +0300 Efraim Flashner wrote: > > It looks like both tests that fail expect to have network > connectivity. Since there's no network inside the container then > disabling those tests is the best option. > > If you want you can suggest upstream that they test for network > connectivity before running those tests. > Thanks, yes I also assumed that these failed tests were related to network conectivity issues, so I just submitted the regarding patches: http://issues.guix.gnu.org/41851 -- Reza Alizadeh Majd PantherX Team https://www.pantherx.org/
bug#41847: qTox build failure
ithout_proxy() Could not resolve hostname, or invalid IP address QDEBUG : TestCore::startup_without_proxy() "Connecting to a bootstrap node..." QSYSTEM: TestCore::startup_without_proxy() Could not resolve hostname, or invalid IP address QSYSTEM: TestCore::startup_without_proxy() Could not resolve hostname, or invalid IP address QDEBUG : TestCore::startup_without_proxy() "Connecting to a bootstrap node..." QDEBUG : TestCore::startup_without_proxy() "Connecting to a bootstrap node..." QSYSTEM: TestCore::startup_without_proxy() attempted to send message with network family 10 (probably IPv6) on IPv4 socket QDEBUG : TestCore::startup_without_proxy() "Connecting to a bootstrap node..." QDEBUG : TestCore::startup_without_proxy() "Connecting to a bootstrap node..." QSYSTEM: TestCore::startup_without_proxy() attempted to send message with network family 10 (probably IPv6) on IPv4 socket QDEBUG : TestCore::startup_without_proxy() "Connecting to a bootstrap node..." QSYSTEM: TestCore::startup_without_proxy() Could not resolve hostname, or invalid IP address QSYSTEM: TestCore::startup_without_proxy() Could not resolve hostname, or invalid IP address QDEBUG : TestCore::startup_without_proxy() "Connecting to a bootstrap node..." QSYSTEM: TestCore::startup_without_proxy() Could not resolve hostname, or invalid IP address QSYSTEM: TestCore::startup_without_proxy() Could not resolve hostname, or invalid IP address QDEBUG : TestCore::startup_without_proxy() "Connecting to a bootstrap node..." QDEBUG : TestCore::startup_without_proxy() "Connecting to a bootstrap node..." QDEBUG : TestCore::startup_without_proxy() "Connecting to a bootstrap node..." QSYSTEM: TestCore::startup_without_proxy() attempted to send message with network family 10 (probably IPv6) on IPv4 socket QDEBUG : TestCore::startup_without_proxy() "Connecting to a bootstrap node..." QSYSTEM: TestCore::startup_without_proxy() Could not resolve hostname, or invalid IP address QSYSTEM: TestCore::startup_without_proxy() Could not resolve hostname, or invalid IP address QDEBUG : TestCore::startup_without_proxy() "Connecting to a bootstrap node..." QDEBUG : TestCore::startup_without_proxy() "Connecting to a bootstrap node..." QSYSTEM: TestCore::startup_without_proxy() attempted to send message with network family 10 (probably IPv6) on IPv4 socket QDEBUG : TestCore::startup_without_proxy() "Connecting to a bootstrap node..." QSYSTEM: TestCore::startup_without_proxy() Could not resolve hostname, or invalid IP address QSYSTEM: TestCore::startup_without_proxy() Could not resolve hostname, or invalid IP address QDEBUG : TestCore::startup_without_proxy() "Connecting to a bootstrap node..." FAIL! : TestCore::startup_without_proxy() 'spyCore.wait(timeout)' returned FALSE. () Loc: [/tmp/guix-build-qtox-1.17.2.drv-0/qTox-1.17.2/test/core/core_test.cpp(118)] QWARN : TestCore::startup_with_invalid_proxy() Core starting without LAN discovery. Peers can only be found through DHT. QDEBUG : TestCore::startup_with_invalid_proxy() using proxy "Test" : 9985 QDEBUG : TestCore::startup_with_invalid_proxy() Proxy and UDP enabled, this is a security risk, forcing TCP only QSYSTEM: TestCore::startup_with_invalid_proxy() bad proxy, error code: 5 QWARN : TestCore::startup_with_invalid_proxy() Core starting without LAN discovery. Peers can only be found through DHT. QDEBUG : TestCore::startup_with_invalid_proxy() using proxy "Test" : 9985 QDEBUG : TestCore::startup_with_invalid_proxy() Proxy and UDP enabled, this is a security risk, forcing TCP only QSYSTEM: TestCore::startup_with_invalid_proxy() bad proxy, error code: 5 PASS : TestCore::startup_with_invalid_proxy() PASS : TestCore::cleanupTestCase() Totals: 3 passed, 1 failed, 0 skipped, 0 blacklisted, 90235ms * Finished testing of TestCore * --8<---cut here---end--->8--- --8<---cut here---start->8--- 6/14 Test #6: test_bsu .***Failed0.04 sec * Start testing of TestBootstrapNodesUpdater * Config: Using QtTest library 5.12.7, Qt 5.12.7 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.5.0) PASS : TestBootstrapNodesUpdater::initTestCase() FAIL! : TestBootstrapNodesUpdater::testOnline() 'result.size() > 0' returned FALSE. () Loc: [/tmp/guix-build-qtox-1.17.2.drv-0/qTox-1.17.2/test/net/bsu_test.cpp(58)] PASS : TestBootstrapNodesUpdater::testLocal() PASS : TestBootstrapNodesUpdater::cleanupTestCase() Totals: 3 passed, 1 failed, 0 skipped, 0 blacklisted, 7ms * Finished testing of TestBootstrapNodesUpdater * --8<---cut here---end--->8--- is it acceptable to bypass these two tests and submit a patch with updated version of `qTox` ? -- Reza Alizadeh Majd PantherX Team https://www.pantherx.org/
bug#41847: qTox build failure
Hello, Trying to build `qTox`, I receive following errors: --8<---cut here---start->8--- /gnu/store/7aq38bbvgx69788bkx3r5gsyjha17l0y-gtk+-2.24.32/include/gtk-2.0/gtk/gtktypeutils.h:236:64: error: ‘GTypeDebugFlags’ is deprecated [-Werror=deprecated-declarations] voidgtk_type_init (GTypeDebugFlagsdebug_flags); --8<---cut here---end--->8--- --8<---cut here---start->8--- /gnu/store/7aq38bbvgx69788bkx3r5gsyjha17l0y-gtk+-2.24.32/include/gtk-2.0/gtk/gtktooltips.h:73:12: error: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Werror=deprecated-declarations] GTimeVal last_popdown; --8<---cut here---end--->8--- I also check the build status of `qTox` on substitute server, and it seems that the build is also failed there: https://ci.guix.gnu.org/log/p88cprqdjgrm5mn59w4mlpcpb2276kl6-qtox-1.16.3 -- Reza Alizadeh Majd PantherX Team https://www.pantherx.org/
bug#38926: pcmanfm-qt unable to open files by double click
related patch submitted: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39004 -- Regards Reza Alizadeh Majd PantherX Team
bug#38926: pcmanfm-qt unable to open files by double click
Hi Danny, > I don't think that will work. According to the glib source code[1], the > variable is read at runtime of the final program. oh, your right !!! I incorrectly thought that GIO_LAUNCH_DESKTOP is a preprocessor macro. > What you could do is use your wrap-program in pcmanfm-qt, but with > GIO_LAUNCH_DESKTOP (value like above) instead of PATH. That should fix > pcmanfm-qt and I don't see any forward incompatibility or side effects > introduced by it either. Also, glib would be unmodified. > > The downside would be that we would have to patch other broken programs > one by one (after *finding* them). > > But I would still be in favor of that fix for now. Could you try it and > send a patch? OK, so I fix and test pcmanfm-qt following this approach and submit the regarding patch. -- Regards Reza Alizadeh Majd PantherX Team
bug#38926: pcmanfm-qt unable to open files by double click
Hi, On Mon, Jan 6, 2020, at 8:08 PM, Danny Milosavljevic wrote: > > Or, for a complete fix, patch glib-2.60.6/gio/gdesktopappinfo.c > > > > tmp = "gio-launch-desktop" > > > > to say > > > > tmp = "/gnu/store/xyz-glib-.../bin/gio-launch-desktop"; > > > > instead. The latter has the advantage that it magically fixes ALL the > > applications. > > When I try that, I get a circular dependency between the "bin" and the > "out" outputs. > > To be continued... > I faced same issue. using `substitute*` . using following patch `glib` builds successfully: --8<---cut here---start->8--- diff --git a/gnu/packages/glib.scm b/gnu/packages/glib.scm index 528b67e6cf..9f34fe59bc 100644 --- a/gnu/packages/glib.scm +++ b/gnu/packages/glib.scm @@ -302,6 +302,12 @@ shared NFS home directories.") (number->string (parallel-job-count))) ;; Do not run tests marked as "flaky". (invoke "meson" "test" "--no-suite" "flaky"))) +(add-before 'build 'patch-gio-launch-desktop + (lambda* (#:key outputs #:allow-other-keys) + (let ((bin-path (assoc-ref outputs "bin") "/bin")) + (setenv "GIO_LAUNCH_DESKTOP" + (string-append bin-path "/bin/gio-launch-desktop")) + #t))) ;; TODO: meson does not permit the bindir to be outside of prefix. ;; See https://github.com/mesonbuild/meson/issues/2561 ;; We can remove this once meson is patched. --8<---cut here---end--->8--- but the build process takes too much time and I'm waitingfor other related packages to be built and test if the issue is resolved or not. -- Regards Reza Alizadeh Majd PantherX Team
bug#38926: pcmanfm-qt unable to open files by double click
Hi,
> Unfortunately, that way is not acceptable.
>
> Long story short, please make it a regular input. The reasoning is below:
>
> Guix has better modularity than most of the other distributions that exist.
OK, I got your point, so I think following patch could be acceptable now:
--8<---cut here---start->8---
diff --git a/gnu/packages/lxqt.scm b/gnu/packages/lxqt.scm
index 5a3708e30a..fdadb03dda 100644
--- a/gnu/packages/lxqt.scm
+++ b/gnu/packages/lxqt.scm
@@ -1000,7 +1000,17 @@ components to build desktop file managers which belongs
to LXDE.")
(substitute* '("autostart/CMakeLists.txt")
(("DESTINATION \"\\$\\{LXQT_ETC_XDG_DIR\\}")
"DESTINATION \"etc/xdg"))
- #t)
+ #t))
+ (add-after 'install 'wrap-executable
+ (lambda* (#:key outputs inputs #:allow-other-keys)
+ (let ((out (assoc-ref outputs "out"))
+ (glib-bin (string-append (assoc-ref inputs "glib") "/bin")))
+ (display "[=] ")
+ (display glib-bin)
+ (newline)
+ (wrap-program (string-append out "/bin/pcmanfm-qt")
+ `("PATH" ":" prefix (,glib-bin)))
+ #t))
(home-page "https://lxqt.org/;)
(synopsis "File manager and desktop icon manager")
(description "PCManFM-Qt is the Qt port of PCManFM, the file manager of
(END)
--8<---cut here---end--->8---
so please let me know, if any other issues are still exists.
--
Regards
Reza Alizadeh Majd
PantherX Team
bug#38926: pcmanfm-qt unable to open files by double click
Hi,
there is an issue with `pcmanfm-qt`. when we try to open a known file using
double click, we receive following error:
--8<---cut here---start->8---
Failed to execute child process “gio-launch-desktop” (No such file or directory)
--8<---cut here---end--->8---
since `gio-launch-desktop` is located in `bin` output of `glib` package,
adding that as a propagated input for `pcmanfm-qt` fixes this issue.
--8<---cut here---start->8---
diff --git a/gnu/packages/lxqt.scm b/gnu/packages/lxqt.scm
index 5a3708e30a..2337daa7c3 100644
--- a/gnu/packages/lxqt.scm
+++ b/gnu/packages/lxqt.scm
@@ -991,6 +991,8 @@ components to build desktop file managers which belongs to
LXDE.")
`(("pkg-config" ,pkg-config)
("qttools" ,qttools)
("lxqt-build-tools" ,lxqt-build-tools)))
+(propagated-inputs
+ `(("glib" ,glib "bin")))
(arguments
'(#:tests? #f ; no tests
#:phases
--8<---cut here---end--->8---
is this change is acceptable? if so I can submit a regarding patch to
`guix-patches` mailing list.
--
Regards
Reza Alizadeh Majd
PantherX Team
bug#38651: connman integration issue after recent updates
here is a sample configuration file that I used to reproduce the issue:
(use-modules (gnu)
(gnu system nss)
(gnu packages gnome)
(gnu packages vim)
(srfi srfi-1))
(use-service-modules desktop networking ssh xorg)
(use-package-modules screen ssh certs tls connman)
(operating-system
(host-name "panther")
(timezone "Asia/Tehran")
(locale "en_US.utf8")
;; Boot in "legacy" BIOS mode
(bootloader (bootloader-configuration
(bootloader grub-bootloader)
(target "/dev/sda")))
(file-systems (cons (file-system
(device (file-system-label "my-root"))
(mount-point "/")
(type "ext4"))
%base-file-systems))
(users (cons (user-account
(name "user")
(comment "default user")
(group "users")
(supplementary-groups '("wheel" "audio" "video"))
(home-directory "/home/user"))
%base-user-accounts))
(packages (cons* openssh nss-certs gnutls cmst
%base-packages))
(services (cons* (service gnome-desktop-service-type)
(service openssh-service-type
(openssh-configuration
(port-number 22)
(permit-root-login #t)
(authorized-keys
`(("user" ,(local-file "/etc/vagrant.pub"))
("root" ,(local-file "/etc/vagrant.pub"))
(service connman-service-type)
(remove (lambda (service)
(eq? (service-kind service)
network-manager-service-type))
%desktop-services)))
(name-service-switch %mdns-host-lookup-nss))
--
Regards
Reza Alizadeh Majd
PantherX Team
bug#38651: connman integration issue after recent updates
Hi Guix, I'm using `connman` + `cmst` for network management on my guix machine, recently after I updated the system, I receive following message after login and `cmst` can't communicate with `connman`. I also tried with `econnman` interface and received same error: ``` Error Name: org.freedesktop.DBus.Error.AccessDenied Error Message: Rejected send message, 3 matched rules; type="method_call", sender=":1.108" (uid=1000 pid=3870 comm="cmst ") interface="net.connman.Manager" member="GetTechnologies" error name="(unset)" requested_reply="0" destination="net.connman" (uid=0 pid=369 comm="/gnu/store/1ld7hpvnhcr5wjxd15bvgbwvd50j8i04-connma") ``` I also tried to modify `connman` package and add policy to connman debus config, based on suggested details in: https://forum.obarun.org/viewtopic.php?pid=3075#p3075 but the problem still occurs. -- Regards Reza Alizadeh Majd PantherX Team
bug#37407: node package build failed
Hello Guix, pull the latest changes from guix, build process of `node` package is failed. it seems that recent update of `openssl` broke the build process of that (and also `ungoogled-chomium` which `node` is a dependecy of). build process of `node` package fails during `check` phase with following error: ok 2312 sequential/test-util-debug --- duration_ms: 5.801 ... ok 2313 sequential/test-vm-timeout-rethrow --- duration_ms: 1.255 ... make: *** [Makefile:445: test-ci-js] Error 1 Test suite failed, dumping logs. Backtrace: 4 (primitive-load "/gnu/store/pw7ws5ml94jxl98kyjz51i885gm…") In ice-9/eval.scm: 191:35 3 (_ _) In srfi/srfi-1.scm: 863:16 2 (every1 # …) In /gnu/store/gfprsx2m62cvqbh7ysc9ay9slhijvmal-module-import/guix/build/gnu-build-system.scm: 799:28 1 (_ _) 369:6 0 (check #:target _ #:make-flags _ #:tests? _ # _ # _ # _) /gnu/store/gfprsx2m62cvqbh7ysc9ay9slhijvmal-module-import/guix/build/gnu-build-system.scm:369:6: In procedure check: Throw to key `srfi-34' with args `(#)'. builder for `/gnu/store/vk49dlkkixsik0fw9gsmnqn4jmgfw099-node-10.15.3.drv' failed with exit code 1 build of /gnu/store/vk49dlkkixsik0fw9gsmnqn4jmgfw099-node-10.15.3.drv failed View build log at '/var/log/guix/drvs/vk/49dlkkixsik0fw9gsmnqn4jmgfw099-node-10.15.3.drv.bz2'. guix build: error: build of `/gnu/store/vk49dlkkixsik0fw9gsmnqn4jmgfw099-node-10.15.3.drv' failed maybe preventing the test execution could be a quick workaround to prevent this package build failure. Regards, Reza
bug#36378: Guix Cuirass Issue with Input channels
Hi, Does anyone checked steps to reproduce this issue? Is it occur for anyone else? Best, Reza
bug#36378: Guix Cuirass Issue with Input channels
Hi Ludo,
>
> I find it hard to believe this has anything to do with the name starting
> with ‘p’.
>
> If you change back from ‘_pkginput’ to ‘pkginput’, does it fail again?
>
yes, renaming the input name back to `pkginput` I received same error
again.
It is so strange for me, but I had various tests, and received same results
on each attempt.
steps to reproduce this issue:
1. install GuixSD on a virtual machine
2. update package repository using `guix pull`
3. install cuirass using `guix package -i cuirass`
4. create an spec file with following contents:
--8<---cut here---start->8---
(list
'((#:name . "hello-spec")
(#:load-path-inputs . ("guix"))
(#:package-path-inputs . ())
(#:proc-input . "guix")
(#:proc-file . "build-aux/cuirass/gnu-system.scm")
(#:proc . cuirass-jobs)
(#:proc-args . ((subset . ("hello" "wget"))
(systems . ("x86_64-linux"
(#:inputs . (((#:name . "guix")
(#:url . "git://git.savannah.gnu.org/guix.git")
(#:load-path . ".")
(#:branch . "master")
(#:no-compile? . #t))
((#:name . "pkginput")
(#:url . "git://git.savannah.gnu.org/guix/guix-cuirass.git")
(#:load-path . ".")
(#:branch . "master")
(#:no-compile? . #t))
--8<---cut here---end--->8---
5. run cuirass manually using following command shows the issue:
`cuirass --listen=0.0.0.0 --port=8082 -D test.db -S spec.scm`
6. removing the `test.db` and rename the `pkginput` to `_pkginput`
cuirass starts without problem.
7. restore back the name of `_pkginput` to `pkginput`, remove the
`test.db` file, and re run the cuirass, same error occurs again.
Best,
Reza
