Hi,
I encountered a strange behavior when using a guix.scm file to build and
run test in an emacs project. The project is called issue.el[0].
I have the following guix.scm:
---✀
(use-modules
((guix licenses) #:prefix
Giovanni Biscuolo writes:
> Hi André
>
> I was able to swith back to a previous profile generation and use
> emacs-telega again, see below
Hi Giovanni!
It's working for me too, following your steps!
So, I believe we're agreeing that the commit we referred to should be
reverted. Correct?
This fails on the first try:
--8<---cut here---start->8---
$ guix shell -D -f guix.scm --root=env-test
Backtrace:
10 (primitive-load "/home/rekado/.config/guix/current/bin/guix")
In guix/ui.scm:
2238:7 9 (run-guix . _)
2201:10 8
Hi,
"pelzflorian (Florian Pelz)" skribis:
> zimoun writes:
>> The culprit seems the package ’qtserialport’ in ’packages-builder’ from
>> (apps packages builder). Maybe introduced by commit
>> 1ef04fb2288dade3ad2883026ae286a68ef13a1e.
>
> This was a first failing commit for me too, but the
Julien Lepiller skriver:
> Again this is exactly where I was blocked. There is a checksum being
> generated in classlist files from java code during the build. The classlist
> file is exactly the same as the one in master, so it's correctly generated.
> Fowever, at some point, the process
Hi André
I was able to swith back to a previous profile generation and use
emacs-telega again, see below
current emacs-telega is still broken, AFAIK
André A. Gomes writes:
> Giovanni Biscuolo writes:
[...]
>> André please could you try to switch back to a previous profile
>> generation and
On Mon Sep 12, 2022 at 10:32 PM CDT, bdju via Bug reports for GNU Guix wrote:
> After upgrades I no longer have the `dragon` command that is used by the
> dragon-drop package, making the program unusable. The package is still
> in my manifest file that I applied, still shows up in a search, and I
