This script is used to automatically fix issues within xml documentation
files.
The script is *for now* intended to be used ad-hoc, and the commits to
be examined.
A future discussion will define whether:
* This commit and scripts are kept.
* The script is extended for common use.
The biggest issue right now with the script is that it *could* in theory
destroy a valid space-less varlistentry.
The script could, in practical use, be changed and extended to normalize
some parts of the XML files, mainly:
* A common quoting style for attributes
* Fix-up some weird formatting automatically that xmlformat doesn't
catch
(cherry picked from commit bc0421c4cf18c431ece8d6a19f723159316f55ff)
The other definitions broke term, cmdsynopsis and arg tags; spaces
inside were removed, making workdsrun-ininstead of keeping them spaced.
(cherry picked from commit aa59151c21c353923b3f003662f17f2210c63c57)
The Datadog agent requires `gohai` to be available on its `$PATH` in
order to collect certain metrics.
It would previously start up and collect certain types of metrics, but
log errors related to the missing gohai binary.
This commit configures the systemd-unit to make gohai available at
runtime.
This fixes#39810.
(cherry picked from commit f4c87183df72a71d3d12c20bb2d99f68207dce8f)
service failed to start because of MemoryDenyWriteExecute = true,
which seems not to work on i686
(cherry picked from commit f4ec18aaaca9e46b4f304d2a7f5f06bd6222c0e5)
If docker is enabled, start mesos-slave.service after docker.service
to avoid a race condition that could result in mesos-slave to fail
with "Failed to create docker: Timed out getting docker version"
(cherry picked from commit ec00b6fbb3669e1852f537a8b624c6102f3eeb32)
- refactor into single file for all versions
- improve timing, prevent non-deterministic failures
- fix tests for i686-linux
(cherry picked from commit 13f83ba05fbf8a70a497f3136f35e7fe604d0bc0)
- adapt netcat options to libressl-nc
- wait for services to be started and accepting connections
(cherry picked from commit 840e5d8bda527bb0986efee9df0d45b6e59521d2)
... to avoid race condition between udevd renaming and
networkd configuring interfaces (39069)
Fixes non-deterministic failure of
nixos.tests.predictable-interface-names.vm-test-run-predictableInterfaceNames-with-networkd
(cherry picked from commit 236703f9f3ac1d0904d63940d00f885dfeeb854b)
... with release-small.nix
Tests for small channel should be a subset of tests for full channel.
(cherry picked from commit f8d047da50dbc7d012a8d322b4d5e5a0b639733c)
xdotool failed in rare cases when a window was already created
but not yet decorated by the window manager.
also prevent a (never observed but possible) race condition
(cherry picked from commit 6891bda37071bbecdb343ff941ba893511f5fd70)
This is a very very very ugly workaround and it's because Chromium seems
to eat keystroke for a few seconds after a new window is created.
I haven't found a better solution yet, so let's at least unbreak the
test until we come up with a better way.
Thanks to @vcunat for bringing this to my attention and also doing the
initial bisect.
The change that brought up this problem was 2b29e401531306d044f797a5dfa,
which updated Chromium from version 65.0.3325.181 to version
66.0.3359.117. Unfortunately the upstream changelog[1] is way too large
to actually guess what the breaking change is.
[1]: https://chromium.googlesource.com/chromium/src/+log/65.0.3325.181..66.0.3359.117?pretty=fuller&n=10000
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @bendlas, @vcunat
(cherry picked from commit 1b1b76f70a9dbf59ad8e833f9de3a60f14cf5471)
This adds some documentation about importing modules external to
Nixpkgs, which provides context for documenting
NIXOS_EXTRA_MODULE_PATH.
Closes#30376
(cherry picked from commit 1cc97befd5550732fd155d04cdd9eca3f5024dbc)
@cleverca found this bug in the declarative hooks config. Any shell
variables referenced in a hook script would get expanded by the hooks
directory builder.
Prevent variable expansion by quoting the here doc limit string.
(cherry picked from commit 3e446ecd564611953c75caf97a855285ef30ba38)
Signed-off-by: Domen Kožar <domen@dev.si>
This reverts commit 68c4605f1a251b97cb0fcde251ce52d498e2cef8.
Gitlab has been fixed
(cherry picked from commit 94f5e5ad14e99700e82576167515ba784dbfe98b)
The previous code for this accidentally picked up a "p" when computing the partition number.
This logic should be more robust
fixes#39491
(cherry picked from commit 3a47c7e8f67c6ece266f570d6db9598856512ede)
Following legacy packing conventions, `isArm` was defined just for
32-bit ARM instruction set. This is confusing to non packagers though,
because Aarch64 is an ARM instruction set.
The official ARM overview for ARMv8[1] is surprisingly not confusing,
given the overall state of affairs for ARM naming conventions, and
offers us a solution. It divides the nomenclature into three levels:
```
ISA: ARMv8 {-A, -R, -M}
/ \
Mode: Aarch32 Aarch64
| / \
Encoding: A64 A32 T32
```
At the top is the overall v8 instruction set archicture. Second are the
two modes, defined by bitwidth but differing in other semantics too, and
buttom are the encodings, (hopefully?) isomorphic if they encode the
same mode.
The 32 bit encodings are mostly backwards compatible with previous
non-Thumb and Thumb encodings, and if so we can pun the mode names to
instead mean "sets of compatable or isomorphic encodings", and then
voilà we have nice names for 32-bit and 64-bit arm instruction sets
which do not use the word ARM so as to not confused either laymen or
experienced ARM packages.
[1]: https://developer.arm.com/products/architecture/a-profile
(cherry picked from commit ba52ae50488de85a9cf60a3a04f1c9ca7122ec74)
Nothing probably uses this, but let's be pedantic and have the
pre-included channel on the install media be as close as possible to
what 'nix-channel --update' will give them.
The only remaining difference is that the channel adds programs.sqlite,
which is fundamentally unfixable.
(cherry picked from commit bd77849b2f5b15f17a40f1142e8a90a02c6c8ddd)
The old trezord is obsolete and no longer functions with Trezor's password manager app.
(cherry picked from commit a60e17438ea38d048b690d4fa6c2c67053479463)
- mkfs.fat needs `-n` to set a partition label, not `-L`.
- create /mnt/boot before mounting
- leave out detailed LVM example as advanced users already how to create
LVs while it is detracting for novices.
Re #38674
(cherry picked from commit bca80d67a065de4b875a131ef97dd11cb29c46ba)
This is needed because simp_le expects two certificates in fullchain.pem, leading to error:
> Not enough PEM encoded messages were found in fullchain.pem; at least 2 were expected, found 1.
We now create a CA and sign the key with it instead, providing correct fullchain.pem.
Also cleanup service a bit -- use PATH and a private temporary directory (which
is more suitable).
(cherry picked from commit 4fc0b4edca7e48755538d4436b98baff5901a752)
exportReferencesGraph is deprecated and doesn't have the generated
initial Nix database contain the SHA256 of the contents of the store
paths, which breaks various things under Nix 2.0.
(cherry picked from commit 487be791d783c706369a1a0740e03a0bb60d8f1f)
With #36556, a check was introduced to make sure the user and group
names do not exceed their respective maximum length. This is in part
because systemd also enforces that length, but only at runtime.
So in general it's a good idea to catch as much as we can during
evaluation time, however the maximum length of the group name was set to
16 characters according groupadd(8).
The maximum length of the group names however is a compile-time option
and even systemd allows more than 16 characters. In the mentioned pull
request (#36556) there was already a report that this has broken
evaluation for people out there.
I have also checked what other distributions are doing and they set the
length to either 31 characters or 32 characters, the latter being more
common.
Unfortunately there is a difference between the maximum length enforced
by the shadow package and systemd, both for user name lengths and group
name lengths. However, systemd enforces both length to have a maximum of
31 characters and I'm not sure if this is intended or just a off-by-one
error in systemd.
Nevertheless, I choose 32 characters simply to bring it in par with the
maximum user name length.
For the NixOS assertion however, I use a maximum length of 31 to make
sure that nobody accidentally creates services that contain group names
that systemd considers invalid because of a length of 32 characters.
Signed-off-by: aszlig <aszlig@nix.build>
Closes: #38548
Cc: @vcunat, @fpletz, @qknight
(cherry picked from commit 99ba1cb4245694874d63e84994f32d58d726ed21)
- Rectifies diverging CSS by combining
nixos/nixpkgs docs CSS
- Moves our custom Highlight.js loader in to
the hljs package
- Switches the nixos docs to use SVG
callouts too
(cherry picked from commit 8f33464ca7a603301cf9a5a213be23ca701d6cce)
Samuel Dionne-Riel
Rob Vermaas
Vincent Ambo
Sarah Brofeldt
Philipp Hausmann
Sander van der Burg
Eelco Dolstra
Robin Gloster
xeji
Uli Baum
Jean-Baptiste Giraudeau
Jan Malakhovski
Jean-Baptiste Giraudeau
bricewge
Tristan Helmich
AmineChikhaoui
Graham Christensen
Linus Heckemann
John Ericson
aszlig
Ryan Mulligan
Jörg Thalheim
Rodney Lorrimar
Franz Pletz
Vladimír Čunát
Matthew Justin Bauer
Ihor Antonov
John Ericson
Sarah Brofeldt
Michael Raskin
Eric Litak
Tuomas Tynkkynen
Giumo X. Clanjor (哆啦比猫/兰威举)
Silvan Mosberger
Russell O'Connor
Bas van Dijk
Matthieu Coudron
Christian Kauhaus
Nikolay Amiantov
Daiderd Jordan
Tim Steinbach
Ben Wolsieffer
Tuomas Tynkkynen
Wout Mertens
Tim Engler
Johannes Lötzsch
Joachim Schiele
volth
nyanloutre