Hi Peter,
This is indeed not nice. Guix does not provide a useful package that would
reinstall boot configuratipn because boot configuration is managed together
with the rest of the system configuration.
You need to update your /etc/config.scm to declare more entries, and
reconfigure. Here
Hello,
This bug was closed, but I couldn't find what was the resolution of the
problem. Could someone please clarify, for my own education and also so
that it gets documented in the bug report?
--
Thanks
Thiago
Hi,
Ludovic Courtès writes:
> Hi,
>
> Maxim Cournoyer skribis:
>
>> I've researched more on the topic, and it appears what I had on mind is
>> rather systemd's socket *notification* (what they call 'sdNotify')
>> rather than activation. Activation is just to lazy start things... it
>>
Hi,
Ludovic Courtès writes:
> Hi,
>
> Maxim Cournoyer skribis:
>
>> I lost track of the details -- is this problem still likely to bite us
>> in the future, or was something committed to mitigate against it?
>
> “Time bombs” are the worst of non-reproducibility bugs because (1) we
> don’t have
Hi,
Christopher Rodriguez writes:
> Hello all,
>
> I'm currently switching from using the monolithic texlive package to a
> bunch of the broken-out, smaller ones. However, when texlive-bin is
> installed (and thus, when luaotfload-tool is available), the environment
> variable $TEXMFCACHE is
Hi,
Marius Bakke writes:
> Hello,
>
> 'guix build python2-urllib3' currently gives:
>
> /gnu/store/cx22ny550g97klf499yqgzx9mpvvkx1f-python2-python2-urllib3-1.26.4
>
> Adding '--no-grafts' gives the expected file name.
>
> Note that up until commit 2f97a666a564fea0fdcff00a0513aa8b4c2d60fe, the
Hi,
Maxim Cournoyer writes:
> Hi,
>
> Maxim Cournoyer writes:
>
> [...]
>
>> lrwxrwxrwx 1 nixbld nixbld 9 Jul 15 19:18 vala -> vala-0.54
>> lrwxrwxrwx 1 nixbld nixbld 10 Jul 15 19:18 vala-0.54 -> valac-0.54
>> lrwxrwxrwx 1 nixbld nixbld 10 Jul 15 19:18 valac -> valac-0.54
>>
Hi again!
Peter 写道：
On the 1.3.0 image, F1 to reboot just locks up the computer with
a black screen. Necessary to hold down power button to
force-power-off computer
to restart it.
Ouch. Thanks for taking the time to report this bug.
Using the GUIX snapshot image does not have this issue,
Hi,
Our vala packages bundle themselves via bundled bootstrap binaries.
When I asked in #vala on the irc.gnome.org, I was pointed to
https://gitlab.gnome.org/ricotz/vala-bootstrap as a possible solution.
Thanks,
Maxim
Peter 写道：
This means it was not reading the partition table correctly.
Could you explain this part? E.g., did you run ‘wipefs -a’ to
erase the old file system metadata? Partition tables do not
specify file system information.
Guix can take responsibility only for its own drive
Follow-up: 1.3.0 installer couldn't be used again, will submit another bug
for the reason why separately.
Using the snapshot 520v5sznglla0z1g3mz6pfsml88b8gxx-image.iso did not have
the error 1.3.0 did trying to format/write to the partition and the install
was able to complete.
So it seems as if
Hi,
For some bizarre reason, even though it worked last night, today the 1.3.0
usb could no longer establish an internet connection on the intel wired
ethernet. Just a red screen saying no connectivity.
The issue is specific to 1.3.0. The other OSes could use the lan fine, and
the GUIX snapshot
Hi,
On the 1.3.0 image, F1 to reboot just locks up the computer with a black
screen. Necessary to hold down power button to force-power-off computer to
restart it.
Using the GUIX snapshot image does not have this issue, reboot works
normally with the later image.
Best,
Peter
Hi,
This is with the latest snapshot.
This is minor because it was being formatted anyway, but the issue is that
I had created a raw unformatted partition outside of GUIX, but the GUIX
partitioner tool was seeing it as possessing a filesystem of EXT4 already,
when in fact it should have been
Hi,
This is a particularly AWFUL user experience bug. Installing GUIX to a
partition only lists GUIX in the grub boot menu afterward despite the
existence of other bootable OSes on the drive.
Ok fine thinks I, I will just need to manually run grub's mkconfig to force
re-detection. But this
Hi,
Maxim Cournoyer writes:
[...]
> lrwxrwxrwx 1 nixbld nixbld 9 Jul 15 19:18 vala -> vala-0.54
> lrwxrwxrwx 1 nixbld nixbld 10 Jul 15 19:18 vala-0.54 -> valac-0.54
> lrwxrwxrwx 1 nixbld nixbld 10 Jul 15 19:18 valac -> valac-0.54
> -rwxr-xr-x 1 nixbld nixbld 147248 Jul 15 19:18
Hi,
t...@envs.net writes:
> the bin/vala-0.54 shell script executes bin/valac-0.54 which executes
> bin/.valac-0.54-real.
> it should execute bin/.vala-0.54-real instead.
>
> expected (was the case before guix's update):
> $ vala hello.vala
> Hello, World!
> $ ls
> hello.vala
>
> actual:
> $
Hi,
Leo Famulari writes:
> I notice that tests/publish.scm crashes consistently when run "by hand"
> with `make check` on ci.guix.gnu.org:
>
> --
> $ make check -j1
> [...]
> PASS: tests/profiles.scm
> make[4]: *** [Makefile:5520: tests/publish.log] Error 134
> make[4]: Leaving directory
Hi!
Thanks all for your support. :-)
I’ve pushed these new REPL commands as
4ce7f1fb24a111f3e92d5b889d1271bebf109d09, including a new “Using Guix
Interactively” section in the manual to document it. Feedback welcome!
I’m sure we can add more REPL commands as we better see what useful
Ludovic Courtès skribis:
> I observe the following weird behavior, where the first invocation
> wrongfully expands ‘-D gnutls’ into a list of package specs, whereas the
> other invocations (only slightly different) lead to calls to
> ‘package->development-manifest’ as expected:
This had to due
Hi, I confirm it was with the 1.3.0 installer. I have since downloaded the
snapshot installer but I haven't tested it yet. However I would need to be
careful testing because this time around I have created raw unformatted
partitions in Windows disk manager because it annoys me how different
Hi,
Maxim Cournoyer skribis:
> Ludovic Courtès writes:
[...]
guix package: error: profile contains conflicting entries for glib
guix package: error: first entry: glib@2.62.6
/gnu/store/xr6zfqxklmr7skalljn5i071xmgqxbrm-glib-2.62.6
guix package: error:... propagated
Hi,
Maxim Cournoyer skribis:
> I lost track of the details -- is this problem still likely to bite us
> in the future, or was something committed to mitigate against it?
“Time bombs” are the worst of non-reproducibility bugs because (1) we
don’t have workarounds other than changing the system
Hi Peter,
Peter skribis:
> I did manual partitioning because I didn't want to wipe the other
> partitions out.
>
> Set / and /home partitions, formatted as EXT4.
>
> Crashes as soon as it writes the changes, displays the backtrace and
> restarts the installer.
Ouch. Could you confirm it was
Hi,
Maxim Cournoyer skribis:
> I've researched more on the topic, and it appears what I had on mind is
> rather systemd's socket *notification* (what they call 'sdNotify')
> rather than activation. Activation is just to lazy start things... it
> probably wouldn't help here, rather it seems
Am Freitag, dem 15.07.2022 um 01:07 + schrieb Jacob Hrbek:
> Steps to reproduce:
> 1. Install any flatpak app from a GNOME environment
> 2. Try to launch the app from activities (the gnome menu accessible
> through super-key) and expect it to not find it
>
> To fix this i was told that the
Minimal reproducer:
--8<---cut here---start->8---
(use-modules (gnu services configuration)
(gnu packages mail))
(define-configuration/no-serialization home-goimapnotify-configuration
(package
(package go-gitlab.com-shackra-goimapnotify)
27 matches
Mail list logo
