bug#54812: ‘guix system reconfigure’ closes SSH connections

[Ludovic Courtès]

Ludovic Courtès  skribis:

> With OpenSSH turned into inetd style in commit
> 808b9e850491c7b1d867a5f1f4d5ee6f61f345d4, the service upgrade code used
> by ‘guix system reconfigure’ and ‘guix deploy’ wrongfully decides that
> the ‘sshd-*’ transient services corresponding to individual SSH
> connections should be closed:

Fixed with:

  eeb8ac43c8 services: shepherd: Do not unload transient services.
  a2c759c830 services: herd: Report whether a service is transient.

Ludo’.

bug#54828: ssh disconnects when reconfiguring system

[Vagrant Cascadian]

Ever since switching to a system generation using the new shepherd
0.9.0, whenever I'm reconfiguring my system over an ssh connection, the
ssh connection drops out during the switch...

I hadn't noticed this happening before using the new shepherd.

Thankfully I always use tmux or screen and can just reconnect and resume
where I left off... but it is still a bit disconcerting!


live well,
  vagrant


signature.asc
Description: PGP signature

bug#54770: Non-root LUKS devices unusable after Shepherd upgrade

[Christoph Weiss]

I ran into the same issue (no prompt but instead about 32 times the 
message "Nothing to read on input.")


I bisected this issue myself (starting before the fix was pushed) and 
arrived at 400c9ed3d779308e56038305d40cd93acb496180 as the culprit.


However, even with the current master 
(aa5716703fd4603dd89ce9b55f555b7aa85f4c9b), the issue has not been fixed 
for me.


Please let me know if I should provide any specific info.

Thank you.

bug#54820: build-systems: inconsistent use of standard-packages

[Maxime Devos]

Hartmut Goebel schreef op za 09-04-2022 om 18:24 [+0200]:
> Build-systems are adding „@(standard-packages)“ inconsistently to 
> „host-packages“ or „build-packages”. For one developing a new 
> build-system it is not clear which is the correct form.
> 
> Some (e.g. texlive, ruby, python) add it to „host-inputs“)

FWIW, the latest version of 
corrects it for font-build-system.

> [...]
> Some add it to „build-inputs (e.g. gnu, cmake, qt):
> [...]

The reason in cross-compilation support:

  * host-inputs ≈ inputs  
  * build-inputs ≈ native-inputs 

There's also this comment from (guix build-system)

  ;; Here we use build/host/target in the sense of the GNU tool chain (info
  ;; "(autoconf) Specifying Target Triplets").
  (build-inputs  bag-build-inputs;list of packages
 (default '()))
  (host-inputs   bag-host-inputs ;list of packages
 (default '()))

And (autoconf)Specifying Target Triplets:

'--build=BUILD-TYPE'
 the type of system on which the package is being configured and
 compiled.  It defaults to the result of running 'config.guess'.
 Specifying a BUILD-TYPE that differs from HOST-TYPE enables
 cross-compilation mode.

'--host=HOST-TYPE'
 the type of system on which the package runs.  By default it is the
 same as the build machine.  Specifying a HOST-TYPE that differs
 from BUILD-TYPE, when BUILD-TYPE was also explicitly specified,
 enables cross-compilation mode.

(standard-packages) contains a tar, gzip, awk ... which are typically only
needed as native-inputs, so they go in 'build-inputs'.

There's also the complication that the cross-compilation system of glibc
is apparently different from other packages:

;; The cross-libc is really a target package, but for bootstrapping
;; reasons, we can't put it in 'host-inputs'.  Namely, 'cross-gcc' is a
;; native package, so it would end up using a "native" variant of
;; 'cross-libc' (built with 'gnu-build'), whereas all the other packages
;; would use a target variant (built with 'gnu-cross-build'.)
(target-inputs (if (and target implicit-cross-inputs?)
   (standard-cross-packages target 'target)
   '()))

Also, (standard-packages) only contains a non-cross-compiling gcc, so
(standard-cross-packages) (used when cross-compiling) adds a cross-compiling
gcc.

Greetings,
Maxime.


signature.asc
Description: This is a digitally signed message part

bug#54820: build-systems: inconsistent use of standard-packages

[Hartmut Goebel]

Build-systems are adding „@(standard-packages)“ inconsistently to 
„host-packages“ or „build-packages”. For one developing a new 
build-system it is not clear which is the correct form.


Some (e.g. texlive, ruby, python) add it to „host-inputs“)

 (host-inputs `(,@(if source
  `(("source" ,source))
  '())
    ,@inputs
 ;; Keep the standard inputs of 'gnu-build-system'.
 ,@(standard-packages)))

Some add it to „build-inputs (e.g. gnu, cmake, qt):

    (build-inputs `(,@(if source
  `(("source" ,source))
  '())
    ,@`(("cmake" ,cmake))
    ,@native-inputs
    ,@(if target
  ;; Use the standard cross inputs of
  ;; 'gnu-build-system'.
  (standard-cross-packages target 'host)
  '())
    ;; Keep the standard inputs of 'gnu-build-system'.
    ,@(standard-packages)))


Expected:

Either

a) review and align the code of all build-systems, or

b) add a comment to every build-system briefly explaining why in host 
resp. build-packages here,


c) document how and why to use which form.

Since as far as I've seen there is no detailed „How to write a 
build-system“, developers (well, me :-) tend to develop new 
build-systems based on existing ones. Thus (a) or (b) seem the easier 
and quicker solution.



Reproduce:

grep -A5 -B5 standard-packages guix/build-system/*.scm

--
Regards
Hartmut Goebel

| Hartmut Goebel  | h.goe...@crazy-compilers.com   |
| www.crazy-compilers.com | compilers which you thought are impossible |

bug#53147: Hunspell dictionaries unavailable in LibreOffice

[Roman Riabenko]

Hello

У нд, 2022-01-09 у 21:29 +0100, Ludovic Courtès пише:
> I think this is a relatively recent regression, but I’m not sure.

Please note that there is a similar open issue from 2020:
https://issues.guix.gnu.org/41390

Roman

bug#40116: GDM: Memory leak in .gnome-shell-real process

[Luis Felipe via Bug reports for GNU Guix]

Ok, the issue is gone :)

---
Luis Felipe López Acevedo

publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

bug#52808: Guix home should not assume that all targets are dot files

[Andrew Tropin]

On 2022-04-08 20:18, Ludovic Courtès wrote:

> Hi Andrew,
>
> Andrew Tropin  skribis:
>
>> Those patches introduce a breaking change, but the surface and number of
>> people affected should be small if everyone migrated to
>> xdg-configuration-files.  It removes the special handling of dot files
>> in symlink-manager and doesn't add a leading dot automatically.
>>
>> Please, merge them on April 8.
>>
>> From 1b556cda9716eba31a8a6dd9d3c263988de26ccf Mon Sep 17 00:00:00 2001
>> From: Andrew Tropin 
>> Date: Tue, 29 Mar 2022 11:28:30 +0300
>> Subject: [PATCH 1/2] home: symlink-manager: Remove appending of leading dot.
>>
>> * gnu/home/services.scm (xdg-configuration-files-directory): Add leading dot.
>> * gnu/home/services.scm (xdg-configuration-files-service-type): Change name.
>> * gnu/home/services/shells.scm (add-shell-profile-file,
>> zsh-get-configuration-files, add-zsh-dot-configuration,
>> add-zsh-xdg-configuration, add-bash-configuration): Add leading dots.
>> * gnu/home/services/symlink-manager.scm (update-symlinks-script): Remove
>> leading dot.
>
> [...]
>
>> From 5e1f45fa9ea1aca16843dc85d7d21fd46f3cfcb8 Mon Sep 17 00:00:00 2001
>> From: Andrew Tropin 
>> Date: Tue, 29 Mar 2022 12:47:39 +0300
>> Subject: [PATCH 2/2] home: Add home-xdg-data-files-service-type.
>>
>> * gnu/home/services.scm (home-xdg-data-files-service-type): New variable.
>> * gnu/home/services/symlink-manager.scm (update-symlinks-script): Add a 
>> proper
>> handling for XDG_DATA_HOME value.
>> * gnu/home/services/xdg.scm (home-xdg-mime-applications-service-type): Use
>> home-xdg-data-files service.
>
> Pushed as 20645d8467852990413c1ea9cf81cec82d23defd.
>
> Thanks!
>
> Ludo’.

Hi Ludo,

Thank you very much!

Can you merge other patches from this thread too, please?

-- 
Best regards,
Andrew Tropin


signature.asc
Description: PGP signature

bug#54815: Unknown Horizons 2019.1 fails to start

[Luis Felipe via Bug reports for GNU Guix]

SYSTEM INFORMATION

Generation 54   Mar 24 2022 11:42:45(current)
  guix ab98b51
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: ab98b51ef1304e975da127e3092d01dcc7f02657

unknown-horizons 2019.1


STEPS TO REPRODUCE

1. guix shell unknown-horizons -- unknown-horizon


EXPECTED RESULT

The game starts.


UNEXPECTED RESULT

The game fails to start with the following error:

guix shell unknown-horizons -- unknown-horizons
/gnu/store/cyrgvpvh6wi15m4ffcdn3s55jypp8yqk-fifengine-0.4.2/lib/python3.9/site-packages/fife/extensions/pychan/widgets/widget.py:1038:
 SyntaxWarning: "is" with a literal. Did you mean "=="?
  if len(margin) is 4:
/gnu/store/cyrgvpvh6wi15m4ffcdn3s55jypp8yqk-fifengine-0.4.2/lib/python3.9/site-packages/fife/extensions/pychan/widgets/widget.py:1044:
 SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif len(margin) is 3:
/gnu/store/cyrgvpvh6wi15m4ffcdn3s55jypp8yqk-fifengine-0.4.2/lib/python3.9/site-packages/fife/extensions/pychan/widgets/widget.py:1050:
 SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif len(margin) is 2:
/gnu/store/cyrgvpvh6wi15m4ffcdn3s55jypp8yqk-fifengine-0.4.2/lib/python3.9/site-packages/fife/extensions/pychan/widgets/widget.py:1056:
 SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif len(margin) is 1:
/gnu/store/cyrgvpvh6wi15m4ffcdn3s55jypp8yqk-fifengine-0.4.2/lib/python3.9/site-packages/fife/extensions/pychan/widgets/widget.py:1068:
 SyntaxWarning: "is" with a literal. Did you mean "=="?
  if len(padding) is 4:
/gnu/store/cyrgvpvh6wi15m4ffcdn3s55jypp8yqk-fifengine-0.4.2/lib/python3.9/site-packages/fife/extensions/pychan/widgets/widget.py:1074:
 SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif len(padding) is 3:
/gnu/store/cyrgvpvh6wi15m4ffcdn3s55jypp8yqk-fifengine-0.4.2/lib/python3.9/site-packages/fife/extensions/pychan/widgets/widget.py:1080:
 SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif len(padding) is 2:
/gnu/store/cyrgvpvh6wi15m4ffcdn3s55jypp8yqk-fifengine-0.4.2/lib/python3.9/site-packages/fife/extensions/pychan/widgets/widget.py:1086:
 SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif len(padding) is 1:
/gnu/store/cyrgvpvh6wi15m4ffcdn3s55jypp8yqk-fifengine-0.4.2/lib/python3.9/site-packages/fife/extensions/pychan/widgets/animationicon.py:193:
 SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if anim is not "":
/gnu/store/cyrgvpvh6wi15m4ffcdn3s55jypp8yqk-fifengine-0.4.2/lib/python3.9/site-packages/fife/extensions/pychan/widgets/curvegraph.py:164:
 SyntaxWarning: "is" with a literal. Did you mean "=="?
  if coordinates is None or len(coordinates) is 0:
/gnu/store/cyrgvpvh6wi15m4ffcdn3s55jypp8yqk-fifengine-0.4.2/lib/python3.9/site-packages/fife/extensions/pychan/widgets/linegraph.py:157:
 SyntaxWarning: "is" with a literal. Did you mean "=="?
  if coordinates is None or len(coordinates) is 0:
/gnu/store/cyrgvpvh6wi15m4ffcdn3s55jypp8yqk-fifengine-0.4.2/lib/python3.9/site-packages/fife/extensions/pychan/widgets/pointgraph.py:157:
 SyntaxWarning: "is" with a literal. Did you mean "=="?
  if coordinates is None or len(coordinates) is 0:
Traceback (most recent call last):
  File 
"/gnu/store/5kah2sx0bzp77l3fjbg4mx0y7a2w3wkb-unknown-horizons-2019.1/bin/.unknown-horizons-real",
 line 381, in 
main()
  File 
"/gnu/store/5kah2sx0bzp77l3fjbg4mx0y7a2w3wkb-unknown-horizons-2019.1/bin/.unknown-horizons-real",
 line 122, in main
ret = horizons.main.start(options)
  File 
"/gnu/store/5kah2sx0bzp77l3fjbg4mx0y7a2w3wkb-unknown-horizons-2019.1/lib/python3.9/site-packages/horizons/main.py",
 line 113, in start
horizons.globals.fife = Fife()
  File 
"/gnu/store/5kah2sx0bzp77l3fjbg4mx0y7a2w3wkb-unknown-horizons-2019.1/lib/python3.9/site-packages/horizons/engine/engine.py",
 line 46, in __init__
self._setting = Settings(PATHS.USER_CONFIG_FILE, 
PATHS.SETTINGS_TEMPLATE_FILE)
  File 
"/gnu/store/5kah2sx0bzp77l3fjbg4mx0y7a2w3wkb-unknown-horizons-2019.1/lib/python3.9/site-packages/horizons/engine/settings.py",
 line 39, in __init__
self._settings_serializer.load(settings_file)
  File 
"/gnu/store/cyrgvpvh6wi15m4ffcdn3s55jypp8yqk-fifengine-0.4.2/lib/python3.9/site-packages/fife/extensions/serializers/simplexml.py",
 line 132, in load
self._validateTree()
  File 
"/gnu/store/cyrgvpvh6wi15m4ffcdn3s55jypp8yqk-fifengine-0.4.2/lib/python3.9/site-packages/fife/extensions/serializers/simplexml.py",
 line 386, in _validateTree
for c in self._root_element.getchildren():
AttributeError: 'xml.etree.ElementTree.Element' object has no attribute 
'getchildren


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

publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

bug#54812: ‘guix system reconfigure’ closes SSH connections

[Ludovic Courtès]

With OpenSSH turned into inetd style in commit
808b9e850491c7b1d867a5f1f4d5ee6f61f345d4, the service upgrade code used
by ‘guix system reconfigure’ and ‘guix deploy’ wrongfully decides that
the ‘sshd-*’ transient services corresponding to individual SSH
connections should be closed:

--8<---cut here---start->8---
$ sudo guix system reconfigure …
[…]
guix system: chargeur d'amorçage correctement installé sur « (/dev/sda) »
0,0 Mo seront téléchargés
 module-import-compiled  20KiB  
 1.2MiB/s 
00:00 [##] 100.0%
The following derivation will be built:
  /gnu/store/n99ahnnw94cay1drg499kxsg5ma6598p-upgrade-shepherd-services.scm.drv

0,0 Mo seront téléchargés
 module-import-compiled  20KiB  
 1.8MiB/s 
00:00 [##] 100.0%
construction de 
/gnu/store/n99ahnnw94cay1drg499kxsg5ma6598p-upgrade-shepherd-services.scm.drv...
shepherd: Removing service 'sshd-1'...
shepherd: Service sshd-1 has been stopped.
shepherd: Transient service sshd-1 unregistered.
shepherd: Done.
shepherd: Removing service 'sshd-3'...
shepherd: Service sshd-3 has been stopped.
shepherd: Transient service sshd-3 unregistered.
shepherd: Done.
shepherd: Service swap-swap could not be started.
shepherd: Service host-name has been started.
shepherd: Service user-homes has been started.
shepherd: Service sysctl has been started.
shepherd: Service host-name has been started.
shepherd: Service term-console could not be started.
shepherd: Service bluetooth has been started.
Pour compléter la mise à jour, lancez « herd restart SERVICE » pour arrêter,
mettre à jour et redémarrer tous les services qui n'ont pas été redémarrés
automatiquement.
Lancez « herd status » pour visualiser la liste des services de votre système.
--8<---cut here---end--->8---

I think the solution is to leave transient services untouched.

Unfortunately, the status sexp returned by ‘services->sexp’ currently
lacks information about whether a service is transient.

Ludo’.