bug#45856:

[musics--- via Bug reports for GNU Guix]

Yes that's right. I'd better work with the shadowsocks-rust  or new packages... 
Thank you.

bug#45856: Done

[musics--- via Bug reports for GNU Guix]

Done

bug#45895: Channel authentication should start at the current commit(s)

[Ludovic Courtès]

Hi!

Currently, the first ‘guix pull’ (when ~/.cache/guix is empty)
authenticates starting from the introductory commit.  For the ‘guix’
channel, that’s 11K commits today, which takes about a minute to process
on modern hardware.

Authentication should instead consider the current commits, as returned
by ‘guix describe’, authenticated, and start from there.

For example, if you install Guix 1.3, authentication should start at the
‘v1.3’ commit.

Ludo’.

bug#45896: Non-pull ‘guix’ should know its channels

[Ludovic Courtès]

Related to , we have the problem that
the ‘guix’ command coming from the ‘guix’ package doesn’t know its
provenance: ‘guix describe’ errors out.

We should fix it by storing a meta-data file within the ‘guix’ package.

Likewise, on foreign distros, /usr/local/bin/guix may point to a ‘guix
pull’-guix, but because of the symlink, ‘guix describe’ won’t work:

--8<---cut here---start->8---
$ type -P guix
/home/ludo/.config/guix/current/bin/guix
$ guix describe
Generacio 171   Jan 11 2021 11:38:39(nuna)
  guix 458cb25
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 458cb25b9e7e7c954f468023abea2bebb5d8c75b
$ ln -s $(type -P guix) /tmp
$ /tmp/guix describe
guix describe: error: failed to determine origin
hint: Perhaps this `guix' command was not obtained with `guix pull'? Its
version string is 458cb25b9e7e7c954f468023abea2bebb5d8c75b.
--8<---cut here---end--->8---

We should probably store proper provenance info directly in the ‘guix’
output, just like we store the commit ID in (guix config).

Ludo’.

bug#45901: GNOME Fonts takes about 20 seconds to display fonts

[Luis Felipe via Bug reports for GNU Guix]

## Steps to reproduce

The following steps assume you are using Guix System with GNOME desktop.

1. Open the command prompt (ALT+F2)
2. Run gnome-font-viewer


## Expected result

GNOME Fonts starts and displays the fonts available (system and user fonts?) 
with their corresponding names and thumbnails.


## Unexpected result

+ GNOME Fonts starts, but the font view is empty and there is no visual sign of 
content being loaded.
+ The fonts are listed after waiting for about 20 seconds.
+ The fonts have no preview thumbnails (I heard Christopher Baines was looking 
into this particular issue)


## System information

GNOME 3.34.2
GNOME Fonts (gnome-font-viewer) 3.30.0
GNU Guix 5b785b2
On Hard Disk Drive


---
Luis Felipe López Acevedo
https://luis-felipe.gitlab.io/

bug#45448: Emacs can't load org mode after last update

[Michael Rohleder]

Pierre Langlois  writes:
> Great! I've just pushed with commit
> cd11f6a2bd703f0859aec05c0873186b734d6d74, adding a comment to remove
> this phase when the issue is resolved upstream.

I think, with this commit, this can be closed.


signature.asc
Description: PGP signature

bug#45909: rust@1.47.0, rust-1.48.0 and rust-1.49.0 broken

[Christopher Baines]

The recent llvm 11.0.0 -> 11.0.1 change seems to have broken rust on the
master branch.

bug#45909: rust@1.47.0, rust-1.48.0 and rust-1.49.0 broken

[Leo Famulari]

On Fri, Jan 15, 2021 at 11:50:13PM +, Christopher Baines wrote:
> The recent llvm 11.0.0 -> 11.0.1 change seems to have broken rust on the
> master branch.

If anyone is wondering why we didn't notice failures of packages that
depend on rust, the canonical 'rust' packages is rust-1.45, but these
failures seem to only affect later versions of rust.

bug#45911: authorized-fields is not/badly documented

[raingloom]

guix archive --authorize started issuing a warning some time ago
pointing to "authorized-keys" in "operating-system".

* that is not a valid field of operating-system
* there is no such item in the Guix info page's index
* the relevant example loads a single key from a file, without
  indicating what the syntax of the file is
* trying to store /etc/guix/signing-key.pub as a Scheme file results in
  a parser error due to the hexadecimal syntax being incompatible with
  some Scheme syntax weirdness

So, how the hecc do I add keys permanently the Official Way? Because I
have no idea. I'll try to update the docs when I figure it out.
OOoor... the person who introduced the change could document it. :|

bug#45911: authorized-fields is not/badly documented

[Ricardo Wurmus]

raingloom  writes:

> guix archive --authorize started issuing a warning some time ago
> pointing to "authorized-keys" in "operating-system".
>
> * that is not a valid field of operating-system

That’s right.  It’s a field of guix-configuration, which is documented
in 10.8.1 Base Services.

-- 
Ricardo