bug#23056: (no subject)
I've managed to get guix to build by running mount -t tmpfs tmp /tmp prior to building. I've tried it on two separate hard drives. Perhaps you can try and replicate my results? Kei
bug#23056: (no subject)
On 2016-03-21 18:50, l...@gnu.org wrote: Kei skribis: I've managed to get guix to build by running mount -t tmpfs tmp /tmp prior to building. I've tried it on two separate hard drives. OK, good. Perhaps you can try and replicate my results? No, I’d really need to know the answer to the questions at <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23056#8> to understand. :-) Ludo’. guix-daemon reported itself as version 0.9.0 Prior to my mounting /tmp as tmpfs, /tmp was just a folder under /. These details can be seen by using the GuixSD x86_64 USB install image.
bug#39955: wxmaxima: broken help menus
Hi all, I saw this bug as I was updating WxMaxima today. It seems the issue is with "filetype->GetOpenCommand()" function calls in src/wxMaxima.cpp (lines 3796 and 4078 specifically). These calls are used to find a browser that can open the HTML help files. We could hard-code a browser (e.g., icecat) as a stopgap while we debug the wxWidgets library to see what exactly is going wrong. Thoughts?
bug#42861: emacspeak won't shut up about TTS sync states
Hi there!
Sorry it took me a while to respond. I don't actively use the openmailbox email
account anymore. Please try this patch when you can. The sounds don't quite
work like they do on Debian yet, but at least emacspeak doesn't go on and on
about the TTS sync state and such.
Kei
From fcb7feadbd497e5d64c7867410bba894b277661f Mon Sep 17 00:00:00 2001
From: Kei Kebreau
Date: Sun, 28 Mar 2021 22:38:09 -0400
Subject: [PATCH] gnu: emacspeak: Fix Tclx and espeak server loading.
Fixes <https://issues.guix.gnu.org/42861>.
* gnu/packages/emacs-xyz.scm (emacspeak)[arguments]: In the 'configure' phase,
add Tclx library to the load path of Tcl in the espeak server script. Remove
'wrap-program' phase.
---
gnu/packages/emacs-xyz.scm | 25 -
1 file changed, 12 insertions(+), 13 deletions(-)
diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm
index ead2144b42..764a1cd99c 100644
--- a/gnu/packages/emacs-xyz.scm
+++ b/gnu/packages/emacs-xyz.scm
@@ -11987,8 +11987,18 @@ highlights quasi-quoted expressions.")
#:phases
(modify-phases %standard-phases
(replace 'configure
- (lambda _
+ (lambda* (#:key inputs outputs #:allow-other-keys)
(setenv "SHELL" (which "sh"))
+ ;; Ensure the tclespeak.so binary is found in the correct location
+ ;; by adding the path to the Tclx library to the Tcl $auto_path
+ ;; variable.
+ (with-fluids ((%default-port-encoding "ISO-8859-1"))
+ (substitute* "servers/espeak"
+ (("package require Tclx")
+ (string-append "set auto_path [linsert $auto_path 0 "
+ (assoc-ref inputs "tclx")
+ "/lib]\n"
+ "package require Tclx"
;; Configure Emacspeak according to etc/install.org.
(invoke "make" "config")))
(add-after 'build 'build-espeak
@@ -12016,18 +12026,7 @@ highlights quasi-quoted expressions.")
;; Install the convenient startup script.
(mkdir-p bin)
(copy-file "run" (string-append bin "/emacspeak")))
- #t))
- (add-after 'install 'wrap-program
- (lambda* (#:key inputs outputs #:allow-other-keys)
- (let* ((out (assoc-ref outputs "out"))
-(emacspeak (string-append out "/bin/emacspeak"))
-(espeak (string-append (assoc-ref inputs "espeak")
- "/bin/espeak")))
- ;; The environment variable DTK_PROGRAM tells emacspeak what
- ;; program to use for speech.
- (wrap-program emacspeak
- `("DTK_PROGRAM" ":" prefix (,espeak)))
- #t
+ #t)))
#:tests? #f)); no check target
(inputs
`(("emacs" ,emacs)
--
2.31.0
bug#42861: emacspeak won't shut up about TTS sync states
On Thu, 2021-04-01 at 17:30 +0200, Nicolas Goaziou wrote: > Hello, > > Kei writes: > > > Sorry it took me a while to respond. I don't actively use the openmailbox > > email > > account anymore. Please try this patch when you can. The sounds don't > > quite > > work like they do on Debian yet, but at least emacspeak doesn't go on and on > > about the TTS sync state and such. > > This is much better indeed. Thank you. > My pleasure! > On Debian espeak seems to be activated after loading ".emacs" file. How are you able to tell (aside from looking at the command line arguments)? I'm unable to distinguish the startup processes using Emacs on Debian and Guix even if I install "etc/emacspeak.sh" as the startup script instead of "run". > Here, the package spells out all configuration messages displayed on in > the minibuffer. > Unless I'm misunderstanding you, Emacspeak seems to do the same for me on Debian. For example, it reads "Active processes exist?..." and so on when exiting. Is this not proper behavior? Thanks, Kei
bug#42861: emacspeak won't shut up about TTS sync states
On Fri, 2021-04-02 at 16:44 +0200, Nicolas Goaziou wrote: > Hello, > > Kei writes: > > > How are you able to tell (aside from looking at the command line > > arguments)? > > I'm unable to distinguish the startup processes using Emacs on Debian and > > Guix > > even if I install "etc/emacspeak.sh" as the startup script instead of > > "run". > > On Debian, the voice kicks in after all the initial minibuffer > information is displayed, i.e., it starts when it is actually ready. On > Guix, see below. > > > > Here, the package spells out all configuration messages displayed on > > > in the minibuffer. > > > > > > > Unless I'm misunderstanding you, Emacspeak seems to do the same for me on > > Debian. For example, it reads "Active processes exist?..." and so on when > > exiting. Is this not proper behavior? > > It is, but I am speaking at the initial messages, when you start a fresh > Emacs session. > I'm having trouble replicating the issue you're having. When I run Emacspeak on Debian and Guix, the first thing I hear is "espeak one point five zero espeak". Also, when I place an infinite loop in my Emacs init file, Emacspeak is prevented from loading in both cases. Thanks, Kei
bug#27264: gnome-shell-3.24.2 consistently dies during initialization
l...@gnu.org (Ludovic Courtès) writes:
> Hi Mark,
>
> Mark H Weaver skribis:
>
>> Roel Janssen writes:
>>
>>> Ludovic Courtès writes:
>>>
>>>> Hi,
>>>>
>>>> Mark H Weaver skribis:
>>>>
>>>>> (.gnome-shell-real:11698): Gjs-WARNING **: JS ERROR: Error:
>>>> Requiring Rsvg, version none: Typelib file for namespace 'Rsvg'
>>>> (any version) not found
>>>>
>>>> Looks like the librsvg JS bindings are missing. Would it help to add
>>>> librsvg as an input to ‘gnome-shell’?
>>>>
>>>> Ludo’.
>>>
>>> Adding librsvg to gnome-shell solves this problem, however, a similar
>>> error for Geoclue2 occurs. I added 'geoclue' to the inputs, but that
>>> doesn't solve the problem.
I've found that adding gobject-introspection as a native-input to
geoclue first allows geoclue to generate the required typelib
file. FWIW, I'm writing this in an instance of gnome-shell.
>>
>> Thanks.
>
> Great, could you this fix if you haven’t already?
>
>> I have a question: Does GNOME 3 work for *anyone* in Guix now? If so,
>> that would be useful information. If not, I wonder why this got merged
>> into master.
>
> I think many of us use GTK+/GNOME applications, but fewer use GNOME, so
> I suppose we just didn’t test a full GNOME setup.
>
> Next time we should probably do that or, even better, have an automated
> test that logs in, takes a screenshot, and does some OCR to check
> whether we got something that looks like a GNOME screen.
>
> WDYT?
>
> Ludo’.
I definitely agree. To get gnome-shell running on machine required the
at least the attached patch (the librsvg upgrade is not necessary to my
knowledge). I get more warnings about gnome-shell trying and failing to
run the "ibus-daemon" command, a suggestion for geoclue to use
glib-networking for TLS/SSL support.
From ed08a066c075bf19f1ea92f4abd0d20dc61d59eb Mon Sep 17 00:00:00 2001
From: Kei Kebreau
Date: Thu, 8 Jun 2017 08:15:53 -0400
Subject: [PATCH] Fix gnome-shell.
---
gnu/packages/gnome.scm | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
index 84ae1cf2f..6528221a8 100644
--- a/gnu/packages/gnome.scm
+++ b/gnu/packages/gnome.scm
@@ -1066,7 +1066,7 @@ dealing with different structured file formats.")
(define-public librsvg
(package
(name "librsvg")
-(version "2.40.16")
+(version "2.40.17")
(source (origin
(method url-fetch)
(uri (string-append "mirror://gnome/sources/" name "/"
@@ -1074,7 +1074,7 @@ dealing with different structured file formats.")
name "-" version ".tar.xz"))
(sha256
(base32
-"0bpz6gsq8xi1pb5k9ax6vinph460v14znch3y5yz167s0dmwz2yl"
+"1k39gyf7f5m9x0jvpcxvfcqswdb04xhm1lbwbjabn1f4xk5wbxp6"
(build-system gnu-build-system)
(arguments
`(#:phases
@@ -2633,7 +2633,8 @@ output devices.")
(substitute* "configure"
(("/bin/true") (which "true"
(native-inputs
- `(("pkg-config" ,pkg-config)
+ `(("gobject-introspection" ,gobject-introspection)
+ ("pkg-config" ,pkg-config)
("intltool" ,intltool)))
(inputs
`(("avahi" ,avahi)
@@ -5090,6 +5091,7 @@ properties, screen resolution, and other GNOME
parameters.")
("evolution-data-server" ,evolution-data-server)
("gcr" ,gcr)
("gdm" ,gdm)
+ ("geoclue" ,geoclue)
("gjs" ,gjs)
("gnome-bluetooth" ,gnome-bluetooth)
("gnome-control-center" ,gnome-control-center)
@@ -5100,6 +5102,7 @@ properties, screen resolution, and other GNOME
parameters.")
("libcanberra" ,libcanberra)
("libcroco" ,libcroco)
("libgweather" ,libgweather)
+ ("librsvg" ,librsvg)
("libsoup" ,libsoup)
("mesa-headers" ,mesa-headers)
("mutter" ,mutter)
--
2.13.0
signature.asc
Description: PGP signature
bug#27264: gnome-shell-3.24.2 consistently dies during initialization
Mark H Weaver writes: > Marius Bakke writes: > >> Mark H Weaver writes: >> >>> I have a question: Does GNOME 3 work for *anyone* in Guix now? If so, >>> that would be useful information. If not, I wonder why this got merged >>> into master. >> >> I'm sorry, I don't actually use GNOME and should have tested it before >> pushing. I have been busy lately and didn't want to hold up the branch. > > In the future, I think that pushing an updated desktop environment to > master should only be performed by someone who is able and willing to > test it. Modern desktop environments are quite complex, and many things > can go wrong even if the code compiles. > I had intended to test GNOME as a whole before having it pushed to master, but the speed of my hardware is an impediment to updating the packages in a timely fashion. I'd be more than willing to take up learning how GNOME works and maintenance of the GNOME packages, but things will take longer (though that's certainly more tolerable than a broken GNOME desktop). >> It would be good to have a system test for GNOME and other DEs so we can >> catch these problems earlier. > > I agree that it would be good to have this, but it would require a > massive effort to produce a sufficiently comprehensive test suite to > render manual testing unnecessary. In the meantime, automated testing > is not an adequate substitute for user testing. To my mind, only > someone who actually uses the DE in question to do real work will be > able to meaningfully judge the result as usable. > >> I'll try to help fixing this later today, but feel free to revert the >> updates meanwhile. > > GNOME contains a great many components, and I don't fully understand > their interdependencies. It's not something that can be easily > reverted. > > Mark signature.asc Description: PGP signature
bug#27264: gnome-shell-3.24.2 consistently dies during initialization
Roel Janssen writes:
> Kei Kebreau writes:
>
>> l...@gnu.org (Ludovic Courtès) writes:
>>
>>> Hi Mark,
>>>
>>> Mark H Weaver skribis:
>>>
>>>> Roel Janssen writes:
>>>>
>>>>> Ludovic Courtès writes:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Mark H Weaver skribis:
>>>>>>
>>>>>>> (.gnome-shell-real:11698): Gjs-WARNING **: JS ERROR: Error:
>>>>>> Requiring Rsvg, version none: Typelib file for namespace 'Rsvg'
>>>>>> (any version) not found
>>>>>>
>>>>>> Looks like the librsvg JS bindings are missing. Would it help to add
>>>>>> librsvg as an input to ‘gnome-shell’?
>>>>>>
>>>>>> Ludo’.
>>>>>
>>>>> Adding librsvg to gnome-shell solves this problem, however, a similar
>>>>> error for Geoclue2 occurs. I added 'geoclue' to the inputs, but that
>>>>> doesn't solve the problem.
>>
>> I've found that adding gobject-introspection as a native-input to
>> geoclue first allows geoclue to generate the required typelib
>> file. FWIW, I'm writing this in an instance of gnome-shell.
>>
>>>>
>>>> Thanks.
>>>
>>> Great, could you this fix if you haven’t already?
>>>
>>>> I have a question: Does GNOME 3 work for *anyone* in Guix now? If so,
>>>> that would be useful information. If not, I wonder why this got merged
>>>> into master.
>>>
>>> I think many of us use GTK+/GNOME applications, but fewer use GNOME, so
>>> I suppose we just didn’t test a full GNOME setup.
>>>
>>> Next time we should probably do that or, even better, have an automated
>>> test that logs in, takes a screenshot, and does some OCR to check
>>> whether we got something that looks like a GNOME screen.
>>>
>>> WDYT?
>>>
>>> Ludo’.
>>
>> I definitely agree. To get gnome-shell running on machine required the
>> at least the attached patch (the librsvg upgrade is not necessary to my
>> knowledge). I get more warnings about gnome-shell trying and failing to
>> run the "ibus-daemon" command, a suggestion for geoclue to use
>> glib-networking for TLS/SSL support.
>>
>> From ed08a066c075bf19f1ea92f4abd0d20dc61d59eb Mon Sep 17 00:00:00 2001
>> From: Kei Kebreau
>> Date: Thu, 8 Jun 2017 08:15:53 -0400
>> Subject: [PATCH] Fix gnome-shell.
>>
>> ---
>> gnu/packages/gnome.scm | 9 ++---
>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
>> index 84ae1cf2f..6528221a8 100644
>> --- a/gnu/packages/gnome.scm
>> +++ b/gnu/packages/gnome.scm
>> @@ -1066,7 +1066,7 @@ dealing with different structured file formats.")
>> (define-public librsvg
>>(package
>> (name "librsvg")
>> -(version "2.40.16")
>> +(version "2.40.17")
>> (source (origin
>>(method url-fetch)
>>(uri (string-append "mirror://gnome/sources/" name "/"
>> @@ -1074,7 +1074,7 @@ dealing with different structured file formats.")
>>name "-" version ".tar.xz"))
>>(sha256
>> (base32
>> -"0bpz6gsq8xi1pb5k9ax6vinph460v14znch3y5yz167s0dmwz2yl"
>> +"1k39gyf7f5m9x0jvpcxvfcqswdb04xhm1lbwbjabn1f4xk5wbxp6"
>> (build-system gnu-build-system)
>> (arguments
>> `(#:phases
>> @@ -2633,7 +2633,8 @@ output devices.")
>> (substitute* "configure"
>> (("/bin/true") (which "true"
>> (native-inputs
>> - `(("pkg-config" ,pkg-config)
>> + `(("gobject-introspection" ,gobject-introspection)
>> + ("pkg-config" ,pkg-config)
>> ("intltool" ,intltool)))
>> (inputs
>> `(("avahi" ,avahi)
>> @@ -5090,6 +5091,7 @@ properties, screen resolution, and other GNOME
>> parameters.")
>> ("evolution-data-server" ,evolution-data-server)
>> ("gcr" ,gcr)
>> ("gdm" ,gdm)
>> + ("geoclue" ,geoclue)
>> ("gjs" ,gjs)
>> ("gnome-bluetooth" ,gnome-bluetooth)
>> ("gnome-control-center" ,gnome-control-center)
>> @@ -5100,6 +5102,7 @@ properties, screen resolution, and other GNOME
>> parameters.")
>> ("libcanberra" ,libcanberra)
>> ("libcroco" ,libcroco)
>> ("libgweather" ,libgweather)
>> + ("librsvg" ,librsvg)
>> ("libsoup" ,libsoup)
>> ("mesa-headers" ,mesa-headers)
>> ("mutter" ,mutter)
>
>
> I attached your patch plus adding geoclue-glib to the minus the librsvg
> upgrade.
>
> I can confirm gnome-shell works again. I don't get any geoclue-related
> warnings/errors. I do get warnings about missing a
> "org.freedesktop.impl.portal.PermissionStore" service.
>
> Kind regards,
> Roel Janssen
Marius pushed a patch covering everything so far except for the
geoclue-glib addition. Does using geoclue-glib get rid of the TLS/SSL
error? If so, I'll apply that as a separate patch.
Thanks in advance,
Kei
signature.asc
Description: PGP signature
bug#29256: maxima: The SGC segfault recovery test failed with memprotect_bad_fault_address, SGC disabled
Alex Vong writes: > Hello all, > > When I start maxima, I get the following warning message: > > The SGC segfault recovery test failed with > memprotect_bad_fault_address, SGC disabled > The SGC segfault recovery test failed with > memprotect_bad_fault_address, SGC disabled > Maxima 5.41.0 http://maxima.sourceforge.net > using Lisp GNU Common Lisp (GCL) GCL 2.6.12 > Distributed under the GNU Public License. See the file COPYING. > Dedicated to the memory of William Schelter. > The function bug_report() provides bug reporting information. > > Actually I encountered this problem quite a while ago after an update, > but I didn't report it since it was not fetal. When did you first notice this issue? > > Does anyone knows what's going on? > > Cheers, > Alex Hello Alex, This is my first time running into this issue. While I do get this warning message using the Maxima substitute from hydra.gnu.org, when I build Maxima 5.41.0 from source locally, this warning message does not appear. Is this the case for you as well? The message comes from the source code of GNU Common Lisp, but the GCL binary from hydra.gnu.org doesn't give this error when I run it. It seems like this comes down a bug in GCL set off by Maxima, a bug in Maxima, a reproducibility issue, or some combination of all of these. I'll be investigating this further. Thank you, Kei signature.asc Description: PGP signature
bug#29256: maxima: The SGC segfault recovery test failed with memprotect_bad_fault_address, SGC disabled
Alex Vong writes: > Kei Kebreau writes: > >> Alex Vong writes: >> >>> Hello all, >>> >>> When I start maxima, I get the following warning message: >>> >>> The SGC segfault recovery test failed with >>> memprotect_bad_fault_address, SGC disabled >>> The SGC segfault recovery test failed with >>> memprotect_bad_fault_address, SGC disabled >>> Maxima 5.41.0 http://maxima.sourceforge.net >>> using Lisp GNU Common Lisp (GCL) GCL 2.6.12 >>> Distributed under the GNU Public License. See the file COPYING. >>> Dedicated to the memory of William Schelter. >>> The function bug_report() provides bug reporting information. >>> >>> Actually I encountered this problem quite a while ago after an update, >>> but I didn't report it since it was not fetal. >> >> When did you first notice this issue? >> > I am afraid I cannot remember exactly when... > > I installed wxmaxima long ago and things worked fine for a long > time. One day, after updating wxmaxima, it showed the above warning and > started to crash nondeterministically when I typed things into the > message box. The crash was fixed quickly by another update, but the > warning persisted. > >>> >>> Does anyone knows what's going on? >>> >>> Cheers, >>> Alex >> >> Hello Alex, >> >> This is my first time running into this issue. While I do get this >> warning message using the Maxima substitute from hydra.gnu.org, when I >> build Maxima 5.41.0 from source locally, this warning message does not >> appear. Is this the case for you as well? >> > Same for me. I set --prefix during configure and install it > somewhere. It starts without the warning. > >> The message comes from the source code of GNU Common Lisp, but the GCL >> binary from hydra.gnu.org doesn't give this error when I run it. It >> seems like this comes down a bug in GCL set off by Maxima, a bug in >> Maxima, a reproducibility issue, or some combination of all of >> these. I'll be investigating this further. >> >> Thank you, >> Kei > > Thanks for looking at it! I turns out that the issue is with stratified garbage collection in GCL. The substitute from hydra.gnu.org does in fact give me the error when I run "(si::sgc-on t)" in the REPL. I'm preparing a patch to update GCL to the version used in Debian stable (GCL git tag "pathnames1.13") and we'll see if changing that definition on the master branch will do anything. signature.asc Description: PGP signature
bug#29256: maxima: The SGC segfault recovery test failed with memprotect_bad_fault_address, SGC disabled
Kei Kebreau writes: > > I turns out that the issue is with stratified garbage collection in > GCL. The substitute from hydra.gnu.org does in fact give me the error > when I run "(si::sgc-on t)" in the REPL. I'm preparing a patch to update > GCL to the version used in Debian stable (GCL git tag "pathnames1.13") and > we'll see if changing that definition on the master branch will do anything. On second thought, the patches applied to Debian Sid's GCL look useful as well. Anyway, keep an eye out for my update patch. signature.asc Description: PGP signature
bug#30436: bigloo@4.3b hash mismatch
l...@gnu.org (Ludovic Courtès) writes: > Amirouche Boubekki skribis: > >> On 2018-02-12 17:59, Leo Famulari wrote: >>> On Mon, Feb 12, 2018 at 05:43:35PM +0100, Amirouche Boubekki wrote: >>>> Trying to install bigloo@4.3b leads to a hash mismatch. >>>> >>>> This was reproduced by several people. >>> >>> Can you copy and paste the error message here? >> $ guix package -i bigloo@4.3b >> substitute: mise à jour de la liste des substituts depuis >> « https://mirror.hydra.gnu.org »... 100.0% >> guile: warning: failed to install locale >> warning: failed to install locale: Invalid argument >> >> Starting download of >> /gnu/store/zjpxaz1k3g4dwn26xaic7m1n7i3zfqyr-bigloo4.3b.tar.gz >> From ftp://ftp-sop.inria.fr/indes/fp/Bigloo/bigloo4.3b.tar.gz... >> ...3b.tar.gz 35.4MiB 192KiB/s 03:09 >> [] 100.0% >> output path >> `/gnu/store/zjpxaz1k3g4dwn26xaic7m1n7i3zfqyr-bigloo4.3b.tar.gz' should >> have sha256 hash >> `1xpzxjlq5g8j3jrb908kfaaa0pkynk4rd083hzvb08amhy68sx07', instead has >> `1x7xdgsls277zlf6gcaxs2cj62xj6yvb0qxh0ddmxfamvxba0cf4' > > The original tarball should be available at: > > > https://mirror.hydra.gnu.org/file/bigloo4.3b.tar.gz/sha256/1xpzxjlq5g8j3jrb908kfaaa0pkynk4rd083hzvb08amhy68sx07 > > … but it’s not. > > Kei, could you check if you still have the tarball with this hash and > how it differs from the current one? > > Unfortunately Bigloo’s maintainer tends to overwrite files in place so > it’s likely that the file was modified after Kei committed the upgrade. > > Thanks, > Ludo’. I do have the "original" tarball, but I don't know how I can transfer it to you for inspection (if that is even necessary). However, I have attached changelog differences between the two source trees. I'd send the full diffoscope report, but its size is about 127 megabytes! The difference seems to be a string of miscellaneous fixes and changes. --- old_bigloo4.3b/ChangeLog2018-01-29 10:04:09.0 -0500 +++ new_bigloo4.3b/ChangeLog2018-02-09 10:47:03.0 -0500 @@ -1,4 +1,120 @@ -2018-01-29 Manuel Serrano +2018-02-09 Manuel Serrano + Yet-another-Makefile-fix + <1763932ff2ff060de51989ce818ab1cd224838f9> [7947f41a] + + Minor-Makefile-fix +[a8d85a2b] + + Yet-another-date.scm-fix + <44f518d5e6f3275e509988fa5e3003cab2d7> [98898fda] + +2018-02-06 Manuel Serrano + Makefile-fix + <3b2d0fc135e596d0800d0eee5ab25bfb4b82> [2612fba3] + + Merge +[130abe75] + + Minor-Makefile-fix + <79bcb094f32b5a28dc5b0d888968c58a9ab0818b> [6c16c4a4] + + Makefile-fix + <98cd49042fc0b830c904d2e4cbf0f9ebe870fddd> [e23e37f6] + + LOGMSG-Tailrec-filter + <78328b0df14dcea576dedd2493931f30b5bbe8ce> [5d4d7d7e] + +2018-02-05 GitHub + Merge-pull-request-3-from-donaldsonjw-4.3b + <096570709b0453f5accea0db0c4fc85a6320c8c2> [6637c061] + +2018-02-04 Joseph Donaldson + Merge-remote-tracking-branch-upstream-4.3b-into-4.3b + <096570709b0453f5accea0db0c4fc85a6320c8c2> [1f770e59] + + Fix-recursive-inlining-optimization +[190cde8c] + +2018-02-03 Joseph Donaldson + Remove-debug-statements +[0e9f69ea] + + Enable-jvm-build-of-csv-and-improve-performance-of-csv-parsing + <912e710614388beddb539b016a7e4b12824c96d5> [c20fd097] + +2018-02-02 GitHub + Merge-pull-request-2-from-donaldsonjw-4.3b + <1950fc6e3d026c1fd4b2b11df319ba9bb85541ed> [4463d1aa] + +2018-01-31 Joseph Donaldson + Support-overlapped-copying-of-normal-vectors + <8b277ca36e1166055efb3271a5044950f3cd52b5> [8d412256] + + Patch-JVM-tests-again + <8c15efcd72feadcf51c7eb564c700d15c6a54204> [13dc2deb] + + Patch-JVM-tests + <69a51e9522d4f343f90a62fea8ecce3cb2348345> [a3d5e940] + + Travis-11 + <368a55be566a92cb23a2813c3e9ff78ee5d9f2aa> [9e05b800] + + Travis-10 + <72f3da176d09f0b92f6ac60440ccbf2bacb63427> [9c4c9bb7] + +2018-01-30 Manuel Serrano + Fix-configure-.afile +[5d5cef36] + + Travis-9 + <974e875adee44378bfd7d9d986570ec5a49744e9> [534a9b35] + + Travis-8 + <8d8b6885bf8c6bafae0b273870943b513d60add1> [ae82] + + Travis-7 + <5715e50963b8b320cbac6d74986abfc78f45807e> [19bc1b2e] + + Travis-6 + <4e03856d19b4c517ce5796bb572b6d88d5aaf513> [b7c21782] + + Travis-5-disable-gstreamer +[43bff7ff] + + Travis-4-disable-gstreamer +[3aa55b03] + + Travis-3 +[d5068355] + + Travis-again +[d95c4109] + + Fix-CI-travis-script +[b7fc
bug#30436: bigloo@4.3b hash mismatch
l...@gnu.org (Ludovic Courtès) writes: > Hello Kei, > > Kei Kebreau skribis: > >> l...@gnu.org (Ludovic Courtès) writes: > > [...] > >>> The original tarball should be available at: >>> >>> >>> https://mirror.hydra.gnu.org/file/bigloo4.3b.tar.gz/sha256/1xpzxjlq5g8j3jrb908kfaaa0pkynk4rd083hzvb08amhy68sx07 >>> >>> … but it’s not. >>> >>> Kei, could you check if you still have the tarball with this hash and >>> how it differs from the current one? >>> >>> Unfortunately Bigloo’s maintainer tends to overwrite files in place so >>> it’s likely that the file was modified after Kei committed the upgrade. >>> >>> Thanks, >>> Ludo’. >> >> I do have the "original" tarball, but I don't know how I can transfer it >> to you for inspection (if that is even necessary). However, I have >> attached changelog differences between the two source trees. I'd send >> the full diffoscope report, but its size is about 127 megabytes! The >> difference seems to be a string of miscellaneous fixes and changes. > > Yeah, that’s what I expected. :-/ Thanks for checking. > > Could you update the hash to the current hash in the ‘bigloo’ package > definition? Please add “Fixes <https://bugs.gnu.org/30436>.” to the > commit log so people can later see why we changed the hash. > > Thank you! > > Ludo’. Done! Thanks to all involved. signature.asc Description: PGP signature
bug#39955: wxmaxima: broken help menus
Christopher Howard writes:
> Hi, after a few months, I still have this problem, though the symptoms
> changed somewhat.
> Now, if I click on either the Help >> wxMaxima help menu, or the Help >>
> Maxima help menu,
> wxMaxima simply terminates, and the word "Aborted" is dumped to stderr.
Hi Christopher,
Can you try applying these two patches to see if they resolve this issue
on your machine?
>From 769eee72f408f31d77d261bf3b14479f8383873e Mon Sep 17 00:00:00 2001
From: Kei Kebreau
Date: Tue, 30 Jun 2020 17:07:48 -0400
Subject: [PATCH 1/2] gnu: wxmaxima: Update to 20.06.6.
* gnu/packages/maths.scm (wxmaxima): Update to 20.06.6.
[arguments]: Add 'patch-doc-path' phase.
---
gnu/packages/maths.scm | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/maths.scm b/gnu/packages/maths.scm
index 3991b2f88b..6f446d9118 100644
--- a/gnu/packages/maths.scm
+++ b/gnu/packages/maths.scm
@@ -3263,7 +3263,7 @@ point numbers.")
(define-public wxmaxima
(package
(name "wxmaxima")
-(version "20.04.0")
+(version "20.06.6")
(source
(origin
(method git-fetch)
@@ -3272,7 +3272,7 @@ point numbers.")
(commit (string-append "Version-" version
(file-name (git-file-name name version))
(sha256
-(base32 "0vrjxzfgmjdzm1rgl0crz4b4badl14jwh032y3xkcdvjl5j67lp3"
+(base32 "054f7n5kx75ng5j20rd5q27n9xxk03mrd7sbxyym1lsswzimqh4w"
(build-system cmake-build-system)
(native-inputs
`(("gettext" ,gettext-minimal)
@@ -3290,6 +3290,14 @@ point numbers.")
`(#:test-target "test"
#:phases
(modify-phases %standard-phases
+ (add-after 'unpack 'patch-doc-path
+ (lambda _
+ ;; Don't look in share/doc/wxmaxima-xx.xx.x for the
+ ;; documentation. Only licensing information is placed there by
+ ;; Guix.
+ (substitute* "src/Dirstructure.cpp"
+ (("/doc/wxmaxima-\\%s") "/doc/wxmaxima"))
+ #t))
(add-before 'check 'pre-check
(lambda _
;; Tests require a running X server.
--
2.27.0
>From a2c82a7c4743ce1ec578cfc890320fb72e96c8aa Mon Sep 17 00:00:00 2001
From: Kei Kebreau
Date: Thu, 30 Jul 2020 22:45:21 -0400
Subject: [PATCH 2/2] gnu: wxwidgets: Fix MIME type loading.
* gnu/packages/wxwidgets.scm (wxwidgets)[inputs]: Add shared-mime-info.
[arguments]: Update 'refer-to-inputs phase so wxWidgets looks in the correct
directory for MIME type information.
---
gnu/packages/wxwidgets.scm | 16 +++-
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git a/gnu/packages/wxwidgets.scm b/gnu/packages/wxwidgets.scm
index 7141b2f4b8..f3a7fdd7a4 100644
--- a/gnu/packages/wxwidgets.scm
+++ b/gnu/packages/wxwidgets.scm
@@ -37,6 +37,7 @@
#:use-module (gnu packages databases)
#:use-module (gnu packages freedesktop)
#:use-module (gnu packages gl)
+ #:use-module (gnu packages gnome)
#:use-module (gnu packages gstreamer)
#:use-module (gnu packages gtk)
#:use-module (gnu packages image)
@@ -75,6 +76,7 @@
("mesa" ,mesa)
("webkitgtk" ,webkitgtk)
("sdl" ,sdl)
+ ("shared-mime-info" ,shared-mime-info)
("xdg-utils" ,xdg-utils)))
(native-inputs
`(("pkg-config" ,pkg-config)))
@@ -97,11 +99,15 @@
#:phases
(modify-phases %standard-phases
(add-after 'unpack 'refer-to-inputs
- (lambda _
- (substitute* "src/unix/utilsx11.cpp"
- (("wxExecute\\(xdg_open \\+")
-(string-append "wxExecute(\"" (which "xdg-open") "\"")))
- #t)
+ (lambda* (#:key inputs #:allow-other-keys)
+ (let* ((mime (string-append (assoc-ref inputs "shared-mime-info")
+ "/share/mime")))
+ (substitute* "src/unix/utilsx11.cpp"
+ (("wxExecute\\(xdg_open \\+")
+ (string-append "wxExecute(\"" (which "xdg-open") "\"")))
+ (substitute* "src/unix/mimetype.cpp"
+ (("/usr(/local)?/share/mime") mime))
+ #t))
(home-page "https://www.wxwidgets.org/";)
(synopsis "Widget toolkit for creating graphical user interfaces")
(description
--
2.27.0
bug#39955: wxmaxima: broken help menus
This bug appears to have been fixed by the patches sent on July 31, pushed to master as commits e79fe4f675 and 93d9737d2b respectively. Thanks for reporting this, and please let us know if you continue to have issues with wxMaxima on Guix!
bug#44916: No option to add whisker menu to xfce panel after installing package xfce4-whiskermenu-plugin.
Hello all! Michael Rohleder writes: > Thank you for reporting! > > potentialuse...@postpro.net writes: >> After doing a fresh install of Guix system using the graphics >> install menu and picking the xfce option, I decided to substitute >> xfce's "Applications" menu with the "Whisker" menu. >> >> Thus, I used command "guix install xfce4-whiskermenu-plugin" to >> install the package. After a system reboot, I opened the menu for >> adding items to the xfce panel. However, the option "Whisker Menu" >> isn't there. >> >> I asked this problem on irc and irc user "mroh" told me that this >> plugin looks broken and they will try to fix it. They also asked me >> to make a bug report: >>> mroh | PotentailUser-53: that plugin does indeed looks broken: >> ~/.guix-profile/bin/xfce4-popup-whiskermenu: line 47: >> /gnu/store/clmv25gbfjrajvh8bsnhfj3w86kry004-xfce4-whiskermenu-plugin-2.4.6/bin/xfce4-panel: >> No such file or directory > > Here is a first try to fix this: > >>>From c0157162c35dea28fd4f65c0b8bc87425358e7db Mon Sep 17 00:00:00 2001 > From: Michael Rohleder > Date: Sat, 28 Nov 2020 16:10:15 +0100 > Subject: [PATCH] gnu: xfce4-whiskermenu-plugin: Fix installed shell script. > > * gnu/packages/xfce.scm (xfce4-whiskermenu-plugin): Fix installed shell > script. > [arguments]: Add phase fix-shell-script to substitute path to xfce4-panel. > -- cut -- > > Now, the shell script (path to xfce4-panel in the last line) looks fine, > but it still doesn't popup/display anything ;( The above patch partially fixes the script. The path to the gettext binary must be patched as well since gettext is used for printing the help menu. Aside from that, it seems like Xfce, when installed as a system-wide desktop environment, does not look in the user's Guix profile for plugins. Panel modules are located by Xfce in the directories listed in the X_XFCE4_LIB_DIRS environment variable. For my Xfce configuration, X_XFCE4_LIB_DIRS contains only /run/current-system/profile/lib/xfce4. To work around this issue on your own machine for the time being, you can add the desired Xfce plugins to the list of packages in your Guix operating system configuration. In the long-term, it will be worth determining the best way to add the proper directories from the user's Guix profile to the list of directories in X_XFCE4_LIB_DIRS. signature.asc Description: PGP signature
bug#44916: No option to add whisker menu to xfce panel after installing package xfce4-whiskermenu-plugin.
Hello again! If you are able, please take a look at patch #45062 linked below. I've slightly modified Michael's patch and added one of my own to take a shot at solving this issue. If it passes review (or no one says anything for a while), these changes will be applied to Guix proper. The patch is here: https://issues.guix.gnu.org/45062 Thanks, Kei signature.asc Description: PGP signature
bug#42861: emacspeak won't shut up about TTS sync states
On 4/2/21 10:44 AM, Nicolas Goaziou wrote: Hello, Kei writes: How are you able to tell (aside from looking at the command line arguments)? I'm unable to distinguish the startup processes using Emacs on Debian and Guix even if I install "etc/emacspeak.sh" as the startup script instead of "run". On Debian, the voice kicks in after all the initial minibuffer information is displayed, i.e., it starts when it is actually ready. On Guix, see below. Here, the package spells out all configuration messages displayed on in the minibuffer. Unless I'm misunderstanding you, Emacspeak seems to do the same for me on Debian. For example, it reads "Active processes exist?..." and so on when exiting. Is this not proper behavior? It is, but I am speaking at the initial messages, when you start a fresh Emacs session. Regards, I've pushed the patch as-is to master. If you are able to provide a method to replicate the issues you speak of here, please message me and we can open a bug report. Thanks, Kei Kebreau
