You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
10660c0 doc: move Guix uninstall instructions to INSTALL.md (Sjors Provoost)
68fab72 guix: OpenSSL test failure workaround (Sjors Provoost)
d612dca guix: reminder to migrate guix-daemon-original customization (Sjors Provoost)
8aa460c guix: add guile-gnutls and guile-json to install list (Sjors Provoost)
9b9991e guix: recommend mounting a tmpfs on /tmp (Sjors Provoost)
6822834 guix: bump recommended hash for manual installation (Sjors Provoost)
Pull request description:
I'm manually installing Guix on a fresh Ubuntu machine. Will be pushing more documentation fixes to this PR as I run into things.
1. Bump minimum hash to match time-machine bump in #25099. It's not necessary for the root Guix version to match the time-machine version in our build, because `guix build` will automatically perform an upgrade for the user, but imo it's better to get any build issues (in Guix itself) over with while the user is going though `INSTALL.md`, rather than during their first Guix build (of Bitcoin Core).
2. Recommend mapping a tmpfs to /tmp upfront, rather than in the troubleshooting section
3. Add `guile-gnutls` and `guile-json` to the table of stuff to install (avoids having to find out in the `./configure` phase)
4. Improve systemd doc
5. Workaround OpenSSL v1.1.1l and v1.1.1n test failure (change machine time)
6. Move uninstallation instructions to INSTALL.md, drop unused footnote / links
ACKs for top commit:
jamesob:
ACK bitcoin/bitcoin@10660c0
Tree-SHA512: ff1278b16f03ea9c63e23e97a852340ab824d5f6c64645cb70237dd828b9a439b4133b60cd2b89672573f6546e99419021d092e236f731908158a7aa6473b0ef
If you use an NVME (SSD) drive, you may encounter [cryptic build errors](#coreutils-fail-teststail-2inotify-dir-recreate). Mounting a [tmpfs at /tmp](https://ubuntu.com/blog/data-driven-analysis-tmp-on-tmpfs) should prevent this and may improve performance as a bonus.
173
+
170
174
#### Guile
171
175
172
176
##### Choosing a Guile version and sticking to it
@@ -334,6 +338,8 @@ packages in Debian at the time of writing.
334
338
|-----------------------|---------------------|
335
339
| guile-gcrypt | libgcrypt-dev |
336
340
| guile-git | libgit2-dev |
341
+
| guile-gnutls | (none) |
342
+
| guile-json | (none) |
337
343
| guile-lzlib | liblz-dev |
338
344
| guile-ssh | libssh-dev |
339
345
| guile-sqlite3 | libsqlite3-dev |
@@ -384,8 +390,9 @@ cd guix
384
390
```
385
391
386
392
You will likely want to build the latest release, however, if the latest release
387
-
when you're reading this is still 1.2.0 then you may want to use 95aca29 instead
388
-
to avoid a problem in the GnuTLS test suite.
393
+
when you're reading this is still 1.3.0 then you may want to use 998eda30 instead
394
+
to avoid the issues described in [#25099](
395
+
https://github.com/bitcoin/bitcoin/pull/25099).
389
396
390
397
```
391
398
git branch -a -l 'origin/version-*' # check for the latest release
@@ -609,6 +616,8 @@ systemctl enable guix-daemon
609
616
systemctl start guix-daemon
610
617
```
611
618
619
+
Remember to set`--no-substitute`in`$libdir/systemd/system/guix-daemon.service` and other customizations if you used them for`guix-daemon-original.service`.
620
+
612
621
##### If you installed Guix via the Debian/Ubuntu distribution packages
613
622
614
623
You will need to create a `guix-daemon-latest` service which points to the new
@@ -717,6 +726,19 @@ $ bzcat /var/log/guix/drvs/../...-foo-3.6.12.drv.bz2 | less
717
726
times, it may be `/tmp/...drv-1` or `/tmp/...drv-2`. Always consult the build
718
727
failure output for the most accurate, up-to-date information.
719
728
729
+
### openssl-1.1.1l and openssl-1.1.1n
730
+
731
+
OpenSSL includes tests that will fail once some certificate has expired. A workaround
### python(-minimal): [Errno 84] Invalid or incomplete multibyte or wide character
721
743
722
744
This error occurs when your `$TMPDIR` (default: /tmp) exists on a filesystem
@@ -774,15 +796,15 @@ The inotify-dir-create test fails on "remote" filesystems such as overlayfs
774
796
as non-remote.
775
797
776
798
A relatively easy workaround to this is to make sure that a somewhat traditional
777
-
filesystem is mounted at `/tmp` (where `guix-daemon` performs its builds). For
799
+
filesystem is mounted at `/tmp` (where `guix-daemon` performs its builds), see [/tmp on tmpfs](#consider-tmp-on-tmpfs). For
778
800
Docker users, this might mean [using a volume][docker/volumes], [binding
779
801
mounting][docker/bind-mnt] from host, or (for those with enough RAM and swap)
780
802
[mounting a tmpfs][docker/tmpfs] using the `--tmpfs` flag.
781
803
782
804
Please see the following links for more details:
783
805
784
806
- An upstream coreutils bug has been filed: [debbugs#47940](https://debbugs.gnu.org/cgi/bugreport.cgi?bug=47940)
785
-
- A Guix bug detailing the underlying problem has been filed: [guix-issues#47935](https://issues.guix.gnu.org/47935)
807
+
- A Guix bug detailing the underlying problem has been filed: [guix-issues#47935](https://issues.guix.gnu.org/47935), [guix-issues#49985](https://issues.guix.gnu.org/49985#5)
786
808
- A commit to skip this test in Guix has been merged into the core-updates branch:
0 commit comments