bug#65769: greetd-wlgreet-sway-session result is blinking cursor

2024-11-01 Thread chris
A week or two ago, wlgreet-sway-session started booting a blinking cursor again. I used ssh to get in, disable it and reconfigure and never took another look. Just now, per your advice, added "users" to `greeter-supplementary-groups`, reconfigured and rebooted and it works again! -- 好きなものを、好きな

bug#65769: greetd-wlgreet-sway-session result is blinking cursor

2024-11-01 Thread chris
David, What a beautiful investigation and summary! Adding "greeter-supplementary-groups" to my users supplementary-groups list now. Thank you! Chris -- 好きなものを、好きなもので、好きなように作る。

bug#72214: small issues re issues.guix.gnu.org

2024-07-20 Thread chris
At issues.gnu.org ~100 of these warnings appear in firefox browser console here, ``` An unexpected value of 1rem was found while parsing the height attribute. An unexpected value of 1rem was found while parsing the width attribute. ``` The browser tries to request a favicon ``` GET https://issues.

bug#71951: guix home reconfigure, no such file or directory

2024-07-10 Thread chris
On 7月05日 金, Juliana Sims wrote: > Hello, > > [...] > > If that isn't the issue, I'm of no further help ;) > > Best, > Juli The issue is resolved and guix home reconfigure is again working. A runtime error occurs in the imported file and the reconfigure process fails in the strange way that it

bug#71951: guix home reconfigure, no such file or directory

2024-07-10 Thread chris
Juli Juli, Your suggestion is apt. Commenting-out a 'primitive-load' call from guix.home.scm, guix home recognizes and processes the file. I tried using 'guile -the-primitive-loaded-file.scm' and, no errors appeared. I'm not sure how to troubleshoot the issue, but with your suggestion it may become possible to fix guix home here, Thank you, Chris

bug#71952: documentation inaccuracy?

2024-07-05 Thread chris
This section of the documentation seems innacurate, https://guix.gnu.org/manual/devel/en/html_node/Invoking-guix-home.html#index-home-generations > When specifying a negative value such as -1, you must precede it with -- to > prevent it from being parsed as an option. For example: > > guix home

bug#71951: guix home reconfigure, no such file or directory

2024-07-05 Thread chris
Today guix home reconfigure is not working on this system. Not sure how to troubleshoot or fix the issue. ```bash guix home reconfigure guix.home.scm guix home: error: failed to load 'guix.home.scm': そのようなファイルやディレクトリはありません÷ guix home reconfigure -L /home/bumble/software/guix-home/ guix.home.scm

bug#68948: highlight error, cannot open filetypes.conf: No such file or directory

2024-03-28 Thread chris
Below changes at the highlight package resolve the issue here but may adversely affect "highlight-gui" functionality. Will wait for https://issues.guix.gnu.org/70047 before trying to proceed, ```diff - #:make-flags #~(let ((confdir (string-append %output -

bug#68948: temp fix

2024-03-27 Thread chris
The following workaround can be used, ``` HLDIRS=$(guix build highlight); # returns two directories HLDIR="${HLDIRS##*[[:space:]]}"; # returns the second dir, after whitespace DATADIR="$HLDIR/etc/highlight/"; echo "(highlight (package bug))" | highlight --data-dir=$DATADIR -O xterm256 --syntax lis

bug#69667: build of sway-1.9-checkout.drv failed

2024-03-10 Thread chris
All issues were resolved by removing grimshot and wlgreet

bug#69667: build of sway-1.9-checkout.drv failed

2024-03-10 Thread chris
On 3月10日 日, 宋文武 wrote: > > Hello, sway build fine for me (and CI), this seems like a disk or > filesystem issue on your side. Booting to sway 1.9 results in a flashing screen and its necessary to restart and boot to a previous generation. This system uses seat and wlgreet. Have not tried to de

bug#69667: build of sway-1.9-checkout.drv failed

2024-03-10 Thread chris
On 3月10日 日, 宋文武 wrote: > > Hello, sway build fine for me (and CI), this seems like a disk or > filesystem issue on your side. Removing grimshot resolved the issue for me.

bug#69667: build of sway-1.9-checkout.drv failed

2024-03-08 Thread chris
guix home reconfigure fails at sway-1.9. The bottom of the drv file shows this, ``` `source is at 'sway-1.9-checkout' Backtrace: 10 (primitive-load "/gnu/store/5ahfcp5009pgdh17lg5y01w4vhv…") In ice-9/eval.scm: 619:8 9 (_ #(#(# "swa…") #)) In ice-9/boot-9.scm: 142:2 8 (dynamic-wi

bug#69655: WARNING: Use of 'load' in declarative module

2024-03-08 Thread chris
rd.conf'. Starting service gpg-agent Service gpg-agent has been started. Service gpg-agent started. Service gpg-agent running with value (("ssh" . #) ("browser" . #) ("extra" . #) ("std" . #)). Succesfully started 2 services in the background ``` Any help or advice is appreciated. Thank you, Chris

bug#68948: highlight error, cannot open filetypes.conf: No such file or directory

2024-02-07 Thread chris
Sergey, I believe you intended a related message for the debbugs service, but only sent the message to my mail address. I am unsure and want to avoid showing impoliteness, I rephrased your message a bit below. Thank you, Chris --- the highlight error goes away after copying

bug#68948: highlight error, cannot open filetypes.conf: No such file or directory

2024-02-06 Thread chris
t/" did not resolve the error. Any advice is welcome. Thank you :) Chris

bug#68512: Qutebrowser 3, no sound from pipewire-only system

2024-01-26 Thread chris
is. If you share links to documentation or examples I will read those. It would be nice to use the home-pipewire-service rather than manage these files myself. Thank you and thank you for any further suggestions or advice you may give, Chris

bug#68512: Qutebrowser 3, no sound from pipewire-only system

2024-01-26 Thread chris
On 1月26日 金, Clément Lassieur wrote: > > Maybe you should check your GUILE_LOAD_PATH and > GUILE_LOAD_COMPILED_PATH. That's where guile finds the guix modules. > They might include folders from an old guix. I'm not sure how to investigate or verify that but here is the result of echo $ echo $GU

bug#68512: done

2024-01-26 Thread chris
done

bug#68512: Qutebrowser 3, no sound from pipewire-only system

2024-01-26 Thread chris
On 1月26日 金, Sergey Trofimov wrote: > > 0.3.77 is the previous version, from a month ago. Is your checkout fresh? > Did you `guix pull`? yes `guix pull` has been used :|

bug#68512: Qutebrowser 3, no sound from pipewire-only system

2024-01-26 Thread chris
uot; >" lib \"" pipewire > "/lib/alsa-lib/libasound_module_ctl_pipewire.so\"\n" >"}\n"))) > --8<---cut here---end--->8--- The above does work :) thank you. I'm interested to explore writing a function that wraps g-exp behaviour to return a package as store path string and might do that outside of this ticket. Thank you for your kind help and correspondence, Chris

bug#68512: Qutebrowser 3, no sound from pipewire-only system

2024-01-25 Thread chris
h, /gnu/store/kqw8zs84px1vzw98yv9xax4rc0n612qy-pipewire-0.3.77 The $(guix build pipewire) command returns this, /gnu/store/8572wxb5138hanhvn1lbfdm1kicxsd2k-pipewire-1.0.0 Thanks, Chris

bug#68512: Qutebrowser 3, no sound from pipewire-only system

2024-01-25 Thread chris
ules (gnu packages linux) (gnu packages build-tools) (gnu packages package-management)) (guix build pipewire) ``` running the file fails with this message: ``` Wrong type to apply: # ``` Thanks in advance for any recommendations or advice. Thank you for conversing with me and helping me thus far, Chris

bug#68512: Qutebrowser 3, no sound from pipewire-only system

2024-01-25 Thread chris
; sleep 2 && (wireplumber &)) ``` Then separately started pipewire and wireplumber "manually" from the shell. The socket files were created and when qutebrowser sound could be heard. Thank you Sergey, Chris

bug#68512: Qutebrowser 3, no sound from pipewire-only system

2024-01-17 Thread chris
On 1月17日 水, chris wrote: > Sound did not work, but messages in the qutebrowser process output were > slightly different. foreign text translates as: "host dropped", The english variant of the same message is probably "Host is down"

bug#68512: Qutebrowser 3, no sound from pipewire-only system

2024-01-17 Thread chris
ています [1588:1588:0117/013614.588043:ERROR:alsa_util.cc(204)] PcmOpen: plug:default,ホストが落ちています ``` These messages differ from the earlier messages that basically said "file not found". Thanks for helping me. I will sleep now and maybe try more things tomorrow, Chris

bug#68512: Qutebrowser 3, no sound from pipewire-only system

2024-01-16 Thread chris
On 1月16日 火, Sergey Trofimov wrote: > How is pipewire configured on your system? The thing is that qtwebengine@5 > is linked with PulseAudio and ALSA libraries, but @6 is linked only with > alsa. You probably miss pipewire-alsa compatibility configuration. Do you > use home-pipewire-service-type?

bug#68512: Qutebrowser 3, no sound from pipewire-only system

2024-01-16 Thread chris
On 1月16日 火, chris wrote: > For convenience, links to the upstream qt.scm file > * https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/qt.scm#n2933 >qtwebengine-5 args > * https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/qt.scm#n2998 >qtwebengine

bug#68512: Qutebrowser 3, no sound from pipewire-only system

2024-01-16 Thread chris
For convenience, links to the upstream qt.scm file * https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/qt.scm#n2933 qtwebengine-5 args * https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/qt.scm#n2998 qtwebengine (qtwebengine-6) Thanks for any input

bug#68512: Qutebrowser 3, no sound from pipewire-only system

2024-01-16 Thread chris
Possibly this was the change from Iyzsong which enabled sound here, ```sh $ git diff fbbbc2088ce933d83f5b0be75308fdcb6b40fa57 d9368572abd3683bed4263eb5e149bb404baee59 diff --git a/gnu/packages/qt.scm b/gnu/packages/qt.scm index 76e9e519c7..01327f6ccf 100644 --- a/gnu/packages/qt.scm +++ b/gnu/pac

bug#68483: Qutebrowser QT platform plugin could not be initialized

2024-01-16 Thread chris
Hey everyone the close email is sent and two separate issues opened, linked below, * https://issues.guix.gnu.org/68512 Qutebrowser 3, no sound from pipewire-only system, * https://issues.guix.gnu.org/68513 Qutebrowser 3, PermissionError qtwebengine_devtools_resources.pak

bug#68513: Qutebrowser 3, PermissionError qtwebengine_devtools_resources.pak

2024-01-16 Thread chris
When starting Qutebrowser 3, the shell process shows these messages related to a permission error. The messages include a CJK error that is rendered by debbugs as "??" and the message basically translates as "no permission" ```sh $ qutebrowser 08:17:14 ERROR: Failed to copy webengine resources,

bug#68512: Qutebrowser 3, no sound from pipewire-only system

2024-01-16 Thread chris
Hello, The latest qutebrowser v3 from this pipewire-only system has no sound. Related messages from the shell process pasted below include CJK characters which debbugs renders as "??", all CJK messages translate as "file or directory not found" ``` ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) u

bug#68483: closing

2024-01-16 Thread chris
closing

bug#68483: Qutebrowser QT platform plugin could not be initialized

2024-01-16 Thread chris
I'm not sure what the correct protocol or etiquette is but I think this issue could be closed by sending an email to 68483-d...@debbugs.gnu.org Maybe the 'done' email should be sent from Sergey who provided the solution? I would like to close this issue and open new separate issues for sound and

bug#68483: Qutebrowser QT platform plugin could not be initialized

2024-01-16 Thread chris
The snippet should be attributed to Sergey, my apology for incorrectly editing the reply

bug#68483: Qutebrowser QT platform plugin could not be initialized

2024-01-16 Thread chris
On 1月16日 火, Sergey Trofimov wrote: > > Clément Lassieur writes: > > --8<---cut here---start->8--- > (simple-service 'qtwayland-vars-service > home-environment-variables-service-type > `(("QT_PLUGIN_PATH" . ,(file-append qtwayland "/lib/qt6/plugins")) >

bug#68483: Qutebrowser QT platform plugin could not be initialized

2024-01-16 Thread chris
Qutebrowser 3 does not have sound and this appears in the process output. "そのようなファイルやディレクトリはありません" means "the file or directory is not found". ``` [3158:3158:0116/000131.568005:ERROR:interface_endpoint_client.cc(694)] Message 4 rejected by interface blink.mojom.WidgetHost ALSA lib pcm_dmix.c:1075

bug#68483: Qutebrowser QT platform plugin could not be initialized

2024-01-15 Thread chris
On 1月15日 月, chris wrote: > On 1月16日 火, Sergey Trofimov wrote: > > > > Here you go: > > ```sh > > qtw=$(guix build qtwayland@6)/lib/qt6/plugins > > QT_PLUGIN_PATH=$qtw QT_QPA_PLATFORM_PLUGIN_PATH=$qtw/platforms qutebrowser > > -s qt.force_platform way

bug#68483: Qutebrowser QT platform plugin could not be initialized

2024-01-15 Thread chris
On 1月15日 月, chris wrote: > On 1月16日 火, Sergey Trofimov wrote: > > > > Here you go: > > ```sh > > qtw=$(guix build qtwayland@6)/lib/qt6/plugins > > QT_PLUGIN_PATH=$qtw QT_QPA_PLATFORM_PLUGIN_PATH=$qtw/platforms qutebrowser > > -s qt.force_platform wayl

bug#68483: Qutebrowser QT platform plugin could not be initialized

2024-01-15 Thread chris
On 1月16日 火, Sergey Trofimov wrote: > > Here you go: > ```sh > qtw=$(guix build qtwayland@6)/lib/qt6/plugins > QT_PLUGIN_PATH=$qtw QT_QPA_PLATFORM_PLUGIN_PATH=$qtw/platforms qutebrowser -s > qt.force_platform wayland > ``` > > Maybe a qutebrowser-wayland package variant should be defined to do t

bug#68483: Qutebrowser QT platform plugin could not be initialized

2024-01-15 Thread chris
On 1月15日 月, Josselin Poiret wrote: > Hi chris, > > chris writes: > > > Related to https://issues.guix.gnu.org/67289#7 > > > > Here is the qutebrowser 3 process shell output. Would anyone recommend a > > solution? > > ``` > > $ qutebrowser >

bug#68483: Qutebrowser QT platform plugin could not be initialized

2024-01-15 Thread chris
Related to https://issues.guix.gnu.org/67289#7 Here is the qutebrowser 3 process shell output. Would anyone recommend a solution? ``` $ qutebrowser 20:40:33 WARNING: Could not find the Qt platform plugin "wayland" in "" 20:40:33 CRITICAL: This application failed to start because no Qt platform p

bug#66182: rm -r /root/.cache/guix # works

2023-09-24 Thread chris
The issue is resolved here. Per irc discussion, root's guix cache was removed ``` sudo rm -r /root/.cache/guix sudo rm -r /root/.cache/guile ``` After that, `guix pull` and `sudo guix system reconfigure guix.system.scm` succeeded

bug#66182: git error: object not found when running system reconfigure

2023-09-24 Thread chris
't know how to resolve. Thanks for any advice, Chris Backtrace: In guix/ui.scm: 2286:10 19 (run-guix-command _ . _) In ice-9/boot-9.scm: 1752:10 18 (with-exception-handler _ _ #:unwind? _ # _) In guix/status.scm: 859:3 17 (_) 839:4 16 (call-with-status-report _ _) In guix/scripts/sys

bug#65769: greetd-wlgreet-sway-session result is blinking cursor

2023-09-08 Thread chris
Josselin sent this message intended for the thread and I think they are okay with re-pasting here, > Usually elogind is responsible (through a PAM module) for creating this > runtime directory. If you're not using elogind, you'll need to create this > directory yourself somehow. I don't reall

bug#65769: greetd-wlgreet-sway-session result is blinking cursor

2023-09-08 Thread chris
On 9月08日 金, ( wrote: > I believe that may have been moi :) This is really odd. I seem to be > the only person who has ever managed to make it work (though there's a > bit of a reporting bias there in that people who do manage probably > won't bring it up...) > > It would be great if anyone tryi

bug#65769: no elogind

2023-09-06 Thread chris
Josselin, > Do you use elogind? No. elogind is not used.

bug#65769: wlgreet-sway-session

2023-09-05 Thread chris
The greeter works after creating /run/user/986/wayland-1.lock and changing the owner of /run/user/986 and /run/user/986/wayland-1.lock to "greeter". This seems to be a bug.

bug#65769: wlgreet-sway-session

2023-09-05 Thread chris
This directory for the greeter user does not exist in the system /run/user/986

bug#65769: wlgreet-sway-session

2023-09-05 Thread chris
In case the attachment is not-accessible, important last lines of sway-greeter.388.log are pasted here. ``` 00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayland-1.lock check permissions 00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile /run/user/986/wayla

bug#65769: wlgreet-sway-session

2023-09-05 Thread chris
Attached to this message is the content of /tmp/sway-greeter.388.log 00:00:00.000 [INFO] [sway/main.c:338] Sway version 1.8.1 00:00:00.000 [INFO] [sway/main.c:339] wlroots version 0.16.2 00:00:00.003 [INFO] [sway/main.c:120] Linux guix-xps 6.4.12 #1 SMP PREEMPT_DYNAMIC 1 x86_64 GNU/Linux 00:00:00.

bug#65769: greetd-wlgreet-sway-session result is blinking cursor

2023-09-05 Thread chris
Hello and thank you in advance for reading me. When defining wlgreet-sway-session in my system config, the result is a blinking cursor. There is no login screen. To login or issue any command, it is necessary to switch to a different tty with something like Alt+fn+F2. In irc, I messaged the use

bug#65541: want this patch

2023-09-03 Thread chris
As a CJK user hoping Julien's patch is accepted soon, this message is my "+1".

bug#49337: Guix pull fails on my Talos II

2023-08-10 Thread Chris Marusich
yesterday and take advantage of the new guix locate command. > > Chris I vote that we close this bug report. > > Thanks, > > Joshua > > FYI, my friend is running Chimera Linux on said Talos II. >

bug#64488: qtbase and qmake are showing incorrect include folders

2023-07-09 Thread Chris Cochrun
I can't use qmake to access info in the qtdeclarative package. Even if both are installed in the same profile or shell. I hope someone smarter than me knows how to fix that. Also, first time posting in the mailing list, so I hope I did it all right. -- *Chris* /Praising God in all things!/

bug#57990: Add package: python-mat2 (remove metadata from images to improve privacy)

2022-09-23 Thread Chris Marusich
Apologies for the top post. I noticed this email and wanted to point you to prior work, in case it proves useful: https://issues.guix.gnu.org/31307#14 On Thu, Sep 22, 2022 at 12:24 PM Maxime Devos wrote: > > > On 22-09-2022 13:38, Dr. Arne Babenhauserheide wrote: > > > > Tobias Geerinckx-Rice

bug#56667: test failures tests/channels.scm and tests/texlive.scm

2022-07-21 Thread Chris Keschnat via Bug reports for GNU Guix
Ludovic Courtès writes: > Hi, > > Chris Keschnat skribis: > >> test-name: channel-news, one entry >> location: /home/ck/tmp/guix/tests/channels.scm:323 >> source: >> + (test-assert >> + "channel-news, one entry" > > [...] > &g

bug#56667: test failures tests/channels.scm and tests/texlive.scm

2022-07-20 Thread Chris Keschnat via Bug reports for GNU Guix
sion "59745") (propagated-inputs (list texlive-cm texlive-hyphen-base texlive-knuth-lib texlive-plain texlive-tex)) (home-page "https://www.tug.org/texlive/";) (synopsis "Plain TeX macros for Physicists") (description "TeXsis is a TeX macro package which provides useful features for typesetting\nresearch papers and related documents. For example, it includes support\nspecifically for: Automatic numbering of equations, figures, tables and\nreferences; Simplified control of type sizes, line spacing, footnotes, running\nheadlines and footlines, and tables of contents, figures and tables; Specialized\ndocument formats for research papers, preprints and \"e-prints\", conference\nproceedings, theses, books, referee reports, letters, and memoranda; Simplified\nmeans of constructing an index for a book or thesis; Easy to use double column\nformatting; Specialized environments for lists, theorems and proofs, centered or\nnon-justified text, and listing computer code; Specialized macros for easily\nconstructing ruled tables. TeXsis was originally developed for physicists, but\nothers may also find it useful. It is completely compatible with Plain TeX.") (license lppl)) #f) test-name: texlive->guix-package location: /home/ck/tmp/guix/tests/texlive.scm:161 source: + (test-assert + "texlive->guix-package" + (mock ((guix build svn) + svn-fetch + (lambda* (url +revision +directory +#:key +(svn-command "svn") +(user-name #f) +(password #f) +(recursive? #t)) +(mkdir-p directory) +(with-output-to-file + (string-append directory "/foo") + (lambda () (display "source") + (let ((result + (texlive->guix-package + "texsis" + #:package-database + (lambda _ %fake-tlpdb + (match result + (('package +('inherit + ('simple-texlive-package + "texlive-texsis" + ('list + "bibtex/bst/texsis/" + "doc/man/man1/" + "doc/otherformats/texsis/base/" + "tex/texsis/base/" + "tex/texsis/config/") + ('base32 (? string? hash)) + #:trivial? + #t)) +('propagated-inputs + ('list + 'texlive-cm + 'texlive-hyphen-base + 'texlive-knuth-lib + 'texlive-plain + 'texlive-tex)) +('home-page "https://www.tug.org/texlive/";) +('synopsis "Plain TeX macros for Physicists") +('description (? string? description)) +('license 'lppl)) + #t) + (_ (begin + (format #t "~s~%" result) + (pk 'fail result #f))) actual-value: #f result: FAIL Am I doing anything wrong? I tried reading the results but cannot figure out what is wrong. . [1] https://guix.gnu.org/manual/en/html_node/Building-from-Git.html Thank you Chris

bug#51466: bug#53355: guix shell --check: confusing error message

2022-06-25 Thread Chris Marusich
Hi Maxime, Maxime Devos writes: > Chris Marusich schreef op za 25-06-2022 om 02:07 [-0700]: >> It turns out that it is probably not OK to rely on shell redirection >> in >> this case, after all.  For example, "dash does not support multi- >> digit &g

bug#53355: guix shell --check: confusing error message

2022-06-25 Thread Chris Marusich
Hi Ludo & Everyone, Chris Marusich writes: > Is it OK to rely on shell redirection? It turns out that it is probably not OK to rely on shell redirection in this case, after all. For example, "dash does not support multi-digit file descriptors": https://bugs.launchpad.net/ub

bug#51466: bug#53355: guix shell --check: confusing error message

2022-06-19 Thread Chris Marusich
at fixes this issue, also. Unless you have more feedback, I'll go ahead and push both patches to master in a few days. -- Chris PGP: https://savannah.gnu.org/people/viewgpg.php?user_id=106836 From c4fee9e63f8cb694de86ae46bd1e2e4c692eb6f6 Mon Sep 17 00:00:00 2001 From: Chris Marusich

bug#53355: guix shell --check: confusing error message

2022-05-23 Thread Chris Marusich
inal hack (echo a few times) is OK, or perhaps we need something else. How would you like to proceed? Is it OK to rely on shell redirection? -- Chris PGP: https://savannah.gnu.org/people/viewgpg.php?user_id=106836 From 9a1cef589abf01b61e22656f44c76441f4c50ffd Mon Sep 17 00:00:00 2001 From: C

bug#51466: bug#53355: guix shell --check: confusing error message

2022-02-13 Thread Chris Marusich
ot; "LS_COLORS") ;;; (variable "GUILE_LOAD_COMPILED_PATH=/gnu/store/hvcq6yjfjjc7060pq09zm1rj02mivg4h-profile/lib/guile/3.0/site-ccache:/gnu/store/hvcq6yjfjjc7060pq09zm1rj02mivg4h-profile/share/guile/site/3.0" "GUILE_LOAD_COMPILED_PATH") ;;; (variable "INFOPATH=/gnu/store/h

bug#51466: bug#53355: guix shell --check: confusing error message

2022-02-01 Thread Chris Marusich
sich@suzaku:~/guix-master $ --8<---cut here---end--->8--- The presence of the "$" in front of LIBRARY_PATH seems suspicious: ;;; (variable "$ LIBRARY_PATH=/gnu/store/hvcq6yjfjjc7060pq09zm1rj02mivg4h-profile/lib" "$ LIBRARY_PATH") I'm not sure why the "$" is being added. I tried various things to remove it. I tried explicitly setting PS1 to an empty string in my ~/.bashrc. I also tried setting it explicitly to an empty string in /etc/profile. Maybe if we can figure out where that "$ " prefix is coming from, we can resolve this issue? -- Chris PGP: https://savannah.gnu.org/people/viewgpg.php?user_id=106836 signature.asc Description: PGP signature

bug#53355: guix shell --check: confusing error message

2022-01-24 Thread Chris Marusich
ONFIG_PATH"' in env, PKG_CONFIG_PATH=/gnu/store/hvcq6yjfjjc7060pq09zm1rj02mivg4h-profile/lib/pkgconfig [0] [env] marusich@suzaku:~/guix-master $ echo out of env, PKG_CONFIG_PATH="$PKG_CONFIG_PATH" out of env, PKG_CONFIG_PATH=/gnu/store/hvcq6yjfjjc7060pq09zm1rj02mivg4h-profile/lib/pkgconfig [0] [env] marusich@suzaku:~/guix-master $ --8<---cut here---end--->8--- It seems this issue happens regardless of whether I use pre-inst-env or run Guix from a "guix pull" installation. -- Chris PGP: https://savannah.gnu.org/people/viewgpg.php?user_id=106836 signature.asc Description: PGP signature

bug#53355: guix shell --check: confusing error message

2022-01-18 Thread Chris Marusich
I can avoid the problem by passing the `--container' option in this case. What's really going on here? It's good to be able to look at this feature with the eyes of a newbie, since I'm very used to using "guix environment", but "guix shell" is totally new to me. I thought it would be a good opportunity to provide feedback. -- Chris PGP: https://savannah.gnu.org/people/viewgpg.php?user_id=106836 signature.asc Description: PGP signature

bug#52943: Cannot build guix as part of guix system reconfigure after commit 224d437fb4 on aarch64

2022-01-16 Thread Chris Marusich
Hi, Chris Marusich writes: > If nobody has further comments, I will commit the attached version to > master in about 24 hours. I've committed this in 24c3485bb3ffc05e687ef6513ac287b8d3048bab. We still need to update the "guix" package, so even if you run "guix pul

bug#52943: Cannot build guix as part of guix system reconfigure after commit 224d437fb4 on aarch64

2022-01-15 Thread Chris Marusich
aarch64-linux with this patch suggests that maybe the current behavior is OK, after all. I've made some rather trivial modifications to your patch, mainly to make it conform to our required ChangeLog format. If nobody has further comments, I will commit the attached version to master

bug#52908: 'tests/guix-system.sh' fails on aarch64-linux

2022-01-08 Thread Chris Marusich
Hi Maxime, Aiko, and Leo, Maxime Devos writes: > Chris Marusich schreef op do 06-01-2022 om 20:32 [-0800]: >> +    (if (string-prefix? "x86_64" >> system) > > There's a target-x86-64? procedure in (guix utils) you could use

bug#52943: Cannot build guix as part of guix system reconfigure after commit 224d437fb4 on aarch64

2022-01-08 Thread Chris Marusich
/gnu/store/kmgva3hbpk1bv0gvx5s4w01n0fdvd2l9-libffi-3.3/lib/../lib:/gnu/store/zf87w2xccli6yvxpplfwd82gcgm6jyrd-libunistr ing-0.9.10/lib:/gnu/store/3jr84ajdz821y480c454pqrswxbhgzlq-glibc-2.33/lib:/gnu/store/l0hnwrv8ma03shjg84a03s05wmj7a0sk-gcc-10.3.0-lib/lib:/gnu/store/3jr84ajdz821y480c454pqrswxbhgzlq-glibc-2.33/lib/../lib:/gnu/store/l0hnwrv8ma03shjg84a03s05 wmj7a0sk-gcc-10.3.0-lib/lib/gcc/powerpc64le-unknown-linux-gnu/10.3.0/../../../../lib] --8<---cut here---end--->8--- Maybe this information can help somehow. It seems fishy that on aarch64-linux, there is no NEEDED entry for ld-linux-aarch64.so.1 in the ELF files under consideration. As shown above, a similar entry DOES exist on both x86_64-linux and powerpc64le-linux. For this reason, it seems plausible that maybe the missing NEEDED entry is bad. However, I don't really know enough to say whether it's indicative of a problem with our aarch64-linux port. Is there an aarch64-linux or ELF expert in the room who can help? :-) It also seems fishy that, on powerpc64le-linux, file-needed/recursive apparently resolves ld64.so.2 successfully, even though it simultaneously includes it in the "failed to resolve" list. Confusing as that is to me, I don't know if that's really related to the aarch64-linux issue. More investigation is needed... -- Chris PGP: https://savannah.gnu.org/people/viewgpg.php?user_id=106836 signature.asc Description: PGP signature

bug#52908: 'tests/guix-system.sh' fails on aarch64-linux

2022-01-06 Thread Chris Marusich
is fix is in. Thank you for the review! Aiko, can you confirm that after running "guix pull" the issue is resolved on your end, too? -- Chris PGP: https://savannah.gnu.org/people/viewgpg.php?user_id=106836 From 79260c8695cc5e3cd64f5b01e262369d5a67f141 Mon Sep 17 00:00:00 2001 From: Ch

bug#52908: 'tests/guix-system.sh' fails on aarch64-linux

2022-01-05 Thread Chris Marusich
f354966730dde4ef3) explains that it must be updated twice: ;; If you are updating this package because it fails to build, you need to ;; actually update it *twice*, as the installer is pointing to the N-1 guix ;; package revision. I'll let you know once I've done that. -- Chris PGP: https://savannah.gnu.org/people/viewgpg.php?user_id=106836 signature.asc Description: PGP signature

bug#52908: 'tests/guix-system.sh' fails on aarch64-linux

2022-01-05 Thread Chris Marusich
ry for fixing "guix pull" problems like this. If you still believe it's necessary, can you help me to understand why it's necessary? Leo Famulari writes: > On Mon, Jan 03, 2022 at 08:43:27PM -0700, Aiko Kyle wrote: >> I'll defer to you and Leo for that judgment!

bug#52908: 'tests/guix-system.sh' fails on aarch64-linux

2022-01-03 Thread Chris Marusich
6d7c7b1f7f2e57fc2468ef1: git am /tmp/patch For the record, the SHA-256 hash value of the patch file is 6650872d41068f6031633d2720553eeb05e7d650a51723dfdd2a3c2df3df294e. If you run "sha256sum /tmp/patch", do you see the same hash value? -- Chris PGP: https://savannah.gnu.org/people/v

bug#52908: 'tests/guix-system.sh' fails on aarch64-linux

2022-01-03 Thread Chris Marusich
ervice-type)' instead $3 = # scheme@(guix-user)> (sddm-service) guix repl: warning: 'sddm-service' is deprecated, use '(@ (gnu services xorg) sddm-service)' instead guix repl: warning: 'sddm-service' is deprecated, use 'sddm-service-type' instead $4 =

bug#24841: close 24841

2021-07-29 Thread Chris Marusich
Hi, As there has been no more feedback recently, I will now close this bug report. -- Chris signature.asc Description: PGP signature

bug#48941: [powerpc64le-linux] libfaketime CLOCK_MONOTONIC test hangs

2021-07-22 Thread Chris Marusich
076688, st_atim = {tv_sec = 140737488347824, tv_nsec = 140737488348952}, st_mtim = {tv_sec = 1, tv_nsec = 8}, st_ctim = {tv_sec = 0, tv_nsec = 140737352442432}, __glibc_reserved4 = 140737488347904, __glibc_reserved5 = 8, __glibc_reserved6 = 268442956} thread = 140737348563184 ret = 0x7fffe300 timer_getoverrun_timerid1 = -7816 timer_getoverrun_timerid2 = 32767 (gdb) --8<---cut here---end--->8--- I'll forward this information to upstream and ask if they need more. I'll also let them know which version of the libraries (e.g., glibc) are being used, since they said it might help to know. -- Chris signature.asc Description: PGP signature

bug#48941: [powerpc64le-linux] libfaketime CLOCK_MONOTONIC test hangs

2021-07-22 Thread Chris Marusich
irectories. That's what I'm trying to figure out. In a --pure environment using only Guix-built tools, one would expect that I would not have to set LD_LIBRARY_PATH. However, if I can't figure it out, that's another trick I can try. -- Chris signature.asc Description: PGP signature

bug#49516: [core-updates] glibc-2.31 patches fail to apply

2021-07-21 Thread Chris Marusich
Ludovic Courtès writes: > Hi! > > Chris Marusich skribis: > >> As an aside, when do we remove old versions of glibc? > > Good question. I’d say it’s enough to keep 3 versions in total. > Currently the main (only?) use case for these is when computing locale > dat

bug#48941: [powerpc64le-linux] libfaketime CLOCK_MONOTONIC test hangs

2021-07-20 Thread Chris Marusich
-start->8--- $ type -P gdb /gnu/store/32fjhp30k34fh0g9f1gmgcj8pc5wldq6-profile/bin/gdb --8<---cut here---end--->8--- I also tried running gdb by invoking it via that absolute file name, and it still errored out in the same way. I&

bug#49337: Guix pull fails on my Talos II

2021-07-10 Thread Chris Marusich
Hi Tobias, Were you able to "guix pull" successfully? -- Chris signature.asc Description: PGP signature

bug#49516: [core-updates] glibc-2.31 patches fail to apply

2021-07-10 Thread Chris Marusich
Chris Marusich writes: > On core-updates, the glibc-2.31 patch no longer apply cleanly. Looks like the other old glibc versions explicitly declare their patches, like this: --8<---cut here---start->8--- (define-public glibc-2.30 (package

bug#49516: [core-updates] glibc-2.31 patches fail to apply

2021-07-10 Thread Chris Marusich
e commit which introduced the failure is 87961fc965b96ac0c7a5909ac2faab2d023b5339. The problem does not occur on the prior commit. For glibc-2.31, commit 87961fc965b96ac0c7a5909ac2faab2d023b5339 effectively removed the glibc-hurd-signal-sa-siginfo.patch and modified libc-hurd-clock_gettime_mono

bug#49218: texlive-latex-base fails to build: "missing engine: luajithbtex"

2021-07-06 Thread Chris Marusich
Hi, I've committed the patch as 68b0e0d511c2873603636e9f783ff59aac4b7612 on core-updates. I'm closing this bug report. Chris Marusich writes: > - Will LuaJIT ever support the powerpc64le architecture? Until it does, > I guess we can't use LuaJIT on powerpc64le at all,

bug#49220: luajit doesn't support powerpc64le

2021-07-06 Thread Chris Marusich
Hi, Efraim Flashner writes: > On Thu, Jun 24, 2021 at 11:15:01PM -0700, Chris Marusich wrote: >> Hi LuaJIT community, >> >> Is anyone in the LuaJIT community actively working on adding support for >> the powerpc64le architecture? Specifically, I am wondering about t

bug#24841: Cross-building bootstrap binaries fail in current master

2021-07-05 Thread Chris Marusich
comments, I'll close this bug report in a week or two. -- Chris signature.asc Description: PGP signature

bug#49360: Updating cataclysm-dda to 0.F

2021-07-04 Thread Chris Lemmer-Webber
Nicolas Goaziou writes: > Hello, > > Chris Lemmer-Webber writes: > >>> There are two options. >>> >>> 1) We could mess with the build phase order, do a make install, then a >>>fresh make clean, then make again with the tiles support on: >&g

bug#49360: Updating cataclysm-dda to 0.F

2021-07-03 Thread Chris Lemmer-Webber
Chris Lemmer-Webber writes: > Hello! > > Here's a quick paste at the start of what's necessary to make this > change: > > #+BEGIN_SRC diff > diff --git a/gnu/packages/games.scm b/gnu/packages/games.scm > index 831f6079f2..c2a8e4bb43 100644 > --- a/gnu/pa

bug#49360: Updating cataclysm-dda to 0.F

2021-07-03 Thread Chris Lemmer-Webber
;LOCALIZE=1" "LANGUAGES=all" failed with status 2 There are two options. 1) We could mess with the build phase order, do a make install, then a fresh make clean, then make again with the tiles support on: https://github.com/CleverRaven/Cataclysm-DDA/issues/42598#issuecomment-667702746 2) But that seems strange so we could make a separate cataclysm-dda-tiles output. We already do a similar thing for crawl and crawl-tiles, so why not? What do people think? I'm leaning towards (2). - Chris

bug#49337: Guix pull fails on my Talos II

2021-07-02 Thread Chris Marusich
Hi, FYI, I was able to successfully "guix pull" from 83f8b6d (Apr 09) to c33e200 (Jul 02) just now on my own POWER9 machine (a Blackbird). -- Chris signature.asc Description: PGP signature

bug#49337: Guix pull fails on my Talos II

2021-07-02 Thread Chris Marusich
", did you just run "guix pull" or did you pass some options in? I.e., were you trying to pull to a specific branch or commit? If you are pulling using a channel file (e.g., ~/.config/guix/channels.scm), could you share it? Does "guix build po4a" successfully build po4a? Does "guix build -d po4a" show the same derivation as above (/gnu/store/bbvxcaa31h006wg2kp1ysly55hkm56hn-po4a-0.63.drv)? -- Chris signature.asc Description: PGP signature

bug#49220: LuaJIT on powerpc64le-linux-gnu (POWER9)?

2021-06-24 Thread Chris Marusich
428 | #error "No support for PowerPC 64 bit mode (yet)" | ^ make[1]: *** No rule to make target 'vm_ppc64.dasc', needed by 'host/buildvm_arch.h'. Stop. make[1]: Leaving directory '/tmp/guix-build-luajit-2.1.0-beta3.drv-0/LuaJIT-2.1.0-beta3/src&

bug#49220: luajit doesn't support powerpc64le

2021-06-24 Thread Chris Marusich
#x27;. Stop. make[1]: Leaving directory '/tmp/guix-build-luajit-2.1.0-beta3.drv-0/LuaJIT-2.1.0-beta3/src' make: *** [Makefile:113: default] Error 2 --8<---cut here---end--->8--- This has downstream impacts, such as being unable to build LuaJITTeX. If

bug#49218: texlive-latex-base fails to build: "missing engine: luajithbtex"

2021-06-24 Thread Chris Marusich
ed9b8518cfb3ac502f48132fd8 Author: Leo Le Bouter Date: Mon Feb 8 04:47:03 2021 +0100 gnu: texlive-latex-base: Fix compilation on powerpc64le*. * gnu/packages/tex.scm (texlive-latex-base)[arguments]: LuaJIT is not ported to powerpc64le* yet. Update replacement 'build phase to add &quo

bug#49100: make check fails: %derivation-cache

2021-06-22 Thread Chris Marusich
the > ‘hash-clear!’ call from ‘call-with-external-store’. Sorry - but yes, that's all it did. I removed the hash-clear! call. I've gone ahead and committed this as 7f0af119a1e3ea9d0ae53811b619437b3e942702 on core-updates. -- Chris signature.asc Description: PGP signature

bug#47698: [powerpc64le-linux] "check" package fails to build

2021-06-18 Thread Chris Marusich
Committed to core-updates in bcdc13454c4afab37b650d4bbfa95e539060619f. -- Chris signature.asc Description: PGP signature

bug#49100: make check fails: %derivation-cache

2021-06-18 Thread Chris Marusich
refer to two different things in the past (see: 3182539875a67f5989c73c3c654fe3138bbc275c). Note also that even after applying this fix, some tests relying on call-with-external-store still fail when run (see: bug 47018). -- Chris signature.asc Description: PGP signature

bug#48941: [powerpc64le-linux] libfaketime CLOCK_MONOTONIC test hangs

2021-06-11 Thread Chris Marusich
Hi, Since I'm not sure how to proceed, I've reported this upstream and asked for help: https://github.com/wolfcw/libfaketime/issues/335 -- Chris signature.asc Description: PGP signature

bug#48941: [powerpc64le-linux] libfaketime CLOCK_MONOTONIC test hangs

2021-06-09 Thread Chris Marusich
;8--- In spite of this, the test hangs on powerpc64le-linux. Out of curiosity, I tried NOT setting FAKETIME_COMPILE_CFLAGS, but the behavior was the same: it still got stuck forever on powerpc64le-linux. -- Chris signature.asc Description: PGP signature

  1   2   3   4   >