bug#38529: Make --ad-hoc the default for guix environment proposed deprecation mechanism

2019-12-21 Thread Gábor Boskovits
Ricardo Wurmus ezt írta (időpont: 2019. dec. 20., Pén 22:32): > > zimoun writes: > > > Then you ask one question: "Should Guix be volatile software?" with > > the subtitle "Software developers should avoid traumatic changes". > > Nothing more. > > Well, I answer you by trying to fill the gap. No

bug#38529: Make --ad-hoc the default for guix environment proposed deprecation mechanism

2019-12-21 Thread Konrad Hinsen
Hi Ricardo, > I wonder if we should simply bump the version number to indicate that > this is a breaking change? That's a possibility, but who ever looks at Guix version numbers? > Another more difficult option would be to do what responsible API > developers on the web do: to version their API

bug#38700: Yoshimi 1.6.1 source hash mismatch

2019-12-21 Thread Ludovic Courtès
Hi! We’re getting a hash mismatch for Yoshimi and ci.guix.gnu.org doesn’t have it in cache: --8<---cut here---start->8--- $ guix build yoshimi -S La jena derivo estos konstruata: /gnu/store/iz0h16wnnz4jf3h2fj8y6dzbkchw71g7-yoshimi-1.6.1.tar.bz2.drv building

bug#38529: Make --ad-hoc the default for guix environment proposed deprecation mechanism

2019-12-21 Thread Ludovic Courtès
Hi! Ricardo Wurmus skribis: > I’m just chiming in here to say that feelings of frustration are very > valid reasons to make or object to a change. Guix is or can be a very > important piece of software — if it remains reliable in the toolbox of > those using it. > > It is difficult striking the

bug#38700: Yoshimi 1.6.1 source hash mismatch

2019-12-21 Thread Ricardo Wurmus
Ludovic Courtès writes: > We’re getting a hash mismatch for Yoshimi and ci.guix.gnu.org doesn’t > have it in cache: […] > Ricardo or anyone who might have the previous Yoshimi tarball, could you > take a look? I ran guix gc earlier today, so I no longer have the tarball :( It’s a new release,

bug#38702: install fails with missing patch

2019-12-21 Thread Ricardo Wurmus
I recently built an installer image from a few commits before 4e09f57af8ee9ac3e7bd5a7a904c4cb6d8d44d9d. It boots fine and the installer works up to the actual system installation, which then aborts with an error indicating that the file python-pep8-stdlib-tokenize-compat.patch could not be found.

bug#38703: installion cannot be cancelled

2019-12-21 Thread Ricardo Wurmus
When I first tried to install one of the new build servers for ci.guix.gnu.org I forgot that the firewall rules prevent these servers from accessing ci.guix.gnu.org via its public IP address. I started the installation process and waited … When I realized that I had to first add the internal IP t