* gnu/build/chromium-extension.scm (make-crx): Pass #:keep-mtime? #t to
COPY-RECURSIVELY. Remove defunct FAKETIME workaround. While at it, pack the
extension in the scratch working directory instead of the transient
store-mapped /tmp.
* gnu/build/chromium-extension.scm (make-crx): Delay with-imported-modules
until the builder code.
(crx->chromium-json): Remove needless define* while at it.
* gnu/build/chromium-extension.scm (chromium-json->profile-object): Remove
variable.
(file-sha256): New variable.
(make-chromium-extension): Rename OUTPUT parameter to prevent conflict.
Adjust other variable names for clarity.
[inputs]: Clear.
[arguments]: Inline and simplify the final transformation with a gexp.
* gnu/packages/php.scm (php)[source]: Add patch.
* gnu/packages/patches/php-openssl_x509_checkpurpose_basic.patch: New file.
* gnu/local.mk (dist_patch_DATA): Add it.
Thanks to Diego Nicola Barbato <dnbarbato@posteo.de>
Loading the framebuffer-coreboot module simply fails with EINVAL on a
non-Corebooted system. Crashing the system with a kernel panic is not
a reasonable reaction to loading valid modules on unsupported hardware.
The kernel should log an error, which the user is expected to see.
Bogus module names will still be fatally reported by linux-modules.drv.
* gnu/build/linux-modules.scm (load-linux-module*):
Ignore EINVAL errors when operating recursively.
Without this, the kernel cannot write to the display until the
full-featured driver module (often i915) is loaded from the root file
system.
If the root file system is encrypted, the initrd's passphrase prompt
won't make it to the screen, and the fully responsive system will appear
frozen whilst waiting for user input.
* gnu/packages/aux-files/linux-libre/4.4-i686.conf,
gnu/packages/aux-files/linux-libre/4.4-x86_64.conf,
gnu/packages/aux-files/linux-libre/4.14-i686.conf,
gnu/packages/aux-files/linux-libre/4.14-x86_64.conf,
gnu/packages/aux-files/linux-libre/4.19-i686.conf,
gnu/packages/aux-files/linux-libre/4.19-x86_64.conf,
gnu/packages/aux-files/linux-libre/5.4-i686.conf,
gnu/packages/aux-files/linux-libre/5.4-x86_64.conf,
gnu/packages/aux-files/linux-libre/5.10-i686.conf,
gnu/packages/aux-files/linux-libre/5.10-x86_64.conf,
gnu/packages/aux-files/linux-libre/5.15-i686.conf,
gnu/packages/aux-files/linux-libre/5.15-x86_64.conf:
Mark simple framebuffers as generic system ones and enable ‘Google’
firmware drivers to enable Coreboot table support and its dependent
framebuffer driver module.
* gnu/system/linux-initrd.scm (default-initrd-modules):
Add the framebuffer_coreboot and simplefb modules on x86 systems.
The package was never compatible with Python 3. Not adding a deprecated
package variant, because going from Python 3 to Python 2 is a breaking
change and it’s unlikely anyone ever used the package anyway (it was
likely broken).
* gnu/packages/python-science.scm (python-pyflow): Move…
(python2-pyflow): …here.
[arguments]: Use Python 2.
It seems a function inside python-flask moved to a different module.
* gnu/packages/python-web.scm (python-flask-restful)[arguments]: Add
phase rewriting imports from flask.helpers to flask.scaffold.
Judging by the documentation
(https://jupyter.readthedocs.io/en/latest/use/jupyter-directories.html)
_DIR can only be a single value, whereas _PATH supports :-delimited
values and extends _DIR with extra directories.
* gnu/packages/python-xyz.scm (python-jupyter-core)[native-search-paths]:
Replace _DIR with _PATH.
(python-nbconvert)[arguments]: Unset JUPYTER_CONFIG_PATH during tests.
(python-notebook)[arguments]: Dito.
This is the only hammer I know for dealing with module cycles and
effectively fixes, for example, ‘guix show nss’ today.
It's also a very poor solution.
* gnu/packages/certs.scm (nss-certs)[version, source]: Copy verbatim
from the nss package rather than referring to it at the top level.
Reported by several users of #guix.
