Maxim Cournoyer writes:
> Hello,
>
> When selecting a file in Nautilus and clicking right-click ->
> Compress... and selected zip with password, attempting to proceed fails
> with the message "encryption not supported".
>
> The code path this supposedly uses is gnome-autoar, which itself uses
Maxim Cournoyer writes:
> Hi,
>
> Connecting an Android phone via USB to a Guix System that has GNOME
> installed, and selecting the transfer mode to be USB/media, I'd expect
> it to appear in Nautilus, the same it does in other mainstream
> distributions. Instead, nothing happens.
>
> In
Hello,
I'm running GNU Guix on Ubuntu 22.04.2 GNU/Linux, and in the recent
twenty days or so I started seeing the following error:
--8<---cut here---start->8---
$ guix pull
Updating channel 'guix' from Git repository at
I don't remember why we did that. The constraints for that file are:
- it's not required to install it
- it must be built before the manuals are generated (it's used for translations)
- it should be built, since otherwise it takes a long time to run
- it has no dependencies
- it's not actually
I noticed that evaluation failures are not (not always?) being reported
with a ❎ as it used to be. For example:
https://ci.guix.gnu.org/eval/418466
It is marked as successful but it has zero build jobs:
https://ci.guix.gnu.org/eval/418466/dashboard
The evaluation log on berlin shows a
This is not related to the dancefloor. Someone on IRC mentioned that
"make clean-go" leaves a stray file guix/build/po.go.
I suppose that it should be added to Makefile.am in the line
that currently reads:
GOBJECTS = $(MODULES:%.scm=%.go) guix/config.go $(dist_noinst_DATA:%.scm=%.go)
but would
Am Fri, Apr 21, 2023 at 09:59:37AM +0200 schrieb Simon Tournier:
> Because it is two “mailing lists“ under the hood: guix-patches and bug-guix.
> Last, on the pragmatic side, I do not know if the CI is following
> bug-guix and if it tries to extract patches from it.
Ah indeed, I suppose it does
Hi,
On Thu, 20 Apr 2023 at 18:55, Andreas Enge wrote:
> Am Thu, Apr 20, 2023 at 03:25:17PM +0200 schrieb Simon Tournier:
>> See #62967 [1] for an attempt. I am rebuilding to detect the potential
>> problem.
>
> Not sure why we need a second issue... All this should work, let us wait
> till
