Fix compatibility with procps 4.

Negative UIDs are no longer allowed.  Use a very high one instead.

Taken from upstream:

  https://github.com/ganeti/ganeti/commit/9cd67e6a81c66ed326d68ea8c3241d14eea6550b

diff --git a/test/py/ganeti.uidpool_unittest.py b/test/py/ganeti.uidpool_unittest.py
index b2f5bc5cf2..2d9227cbf5 100755
--- a/test/py/ganeti.uidpool_unittest.py
+++ b/test/py/ganeti.uidpool_unittest.py
@@ -106,23 +106,24 @@ def testRequestUnusedUid(self):
 
     # Check with a single, known unused user-id
     #
-    # We use "-1" here, which is not a valid user-id, so it's
-    # guaranteed that it's unused.
-    uid = uidpool.RequestUnusedUid(set([-1]))
-    self.assertEqualValues(uid.GetUid(), -1)
+    # We use 2^30+42 here, which is a valid UID, but unlikely to be used on
+    # most systems (even as a subuid).
+    free_uid = 2**30 + 42
+    uid = uidpool.RequestUnusedUid(set([free_uid]))
+    self.assertEqualValues(uid.GetUid(), free_uid)
 
     # Check uid-pool exhaustion
     #
-    # uid "-1" is locked now, so RequestUnusedUid is expected to fail
+    # free_uid is locked now, so RequestUnusedUid is expected to fail
     self.assertRaises(errors.LockError,
                       uidpool.RequestUnusedUid,
-                      set([-1]))
+                      set([free_uid]))
 
     # Check unlocking
     uid.Unlock()
     # After unlocking, "-1" should be available again
-    uid = uidpool.RequestUnusedUid(set([-1]))
-    self.assertEqualValues(uid.GetUid(), -1)
+    uid = uidpool.RequestUnusedUid(set([free_uid]))
+    self.assertEqualValues(uid.GetUid(), free_uid)
 
 
 if __name__ == "__main__":
uild/linux-container.scm'>
<input type='hidden' name='id' value='cdc69de97d4afec0c651b1ba686936272c9bcc85'/><select name='qt'>
<option value='grep'>log msg</option>
<option value='author'>author</option>
<option value='committer'>committer</option>
<option value='range'>range</option>
</select>
<input class='txt' type='search' size='10' name='q' value=''/>
<input type='submit' value='search'/>
</form>
</td></tr></table>
<div class='path'>path: <a href='/guix/log/?id=cdc69de97d4afec0c651b1ba686936272c9bcc85'>root</a>/<a href='/guix/log/gnu?id=cdc69de97d4afec0c651b1ba686936272c9bcc85'>gnu</a>/<a href='/guix/log/gnu/build?id=cdc69de97d4afec0c651b1ba686936272c9bcc85'>build</a>/<a href='/guix/log/gnu/build/linux-container.scm?id=cdc69de97d4afec0c651b1ba686936272c9bcc85'>linux-container.scm</a></div><div class='content'><table class='list nowrap'><tr class='nohover'><th class='left'>Age</th><th class='left'>Commit message (<a href='/guix/log/gnu/build/linux-container.scm?id=cdc69de97d4afec0c651b1ba686936272c9bcc85&amp;showmsg=1'>Expand</a>)</th><th class='left'>Author</th></tr>
<tr><td><span title='2023-01-30 22:24:27 +0100'>2023-01-30</span></td><td><a href='/guix/commit/gnu/build/linux-container.scm?id=0ef8fe22ed8985c9656835fc25ab3463d55b6669'>linux-container: 'container-excursion' forks to join the PID namespace.</a><span class='msg-avail'>...<span class='msg-tooltip'>Fixes &lt;https://issues.guix.gnu.org/61156&gt;.

* gnu/build/linux-container.scm (container-excursion): Add extra call to
'primitive-fork' and invoke THUNK in the child process.
* tests/containers.scm ("container-excursion"): Remove extra
'primitive-fork' call, now unnecessary.
("container-excursion*, /proc"): New test.
</span></span></td><td>Ludovic Courtès</td></tr>
<tr><td><span title='2023-01-30 22:24:27 +0100'>2023-01-30</span></td><td><a href='/guix/commit/gnu/build/linux-container.scm?id=52eb3db19cb9e5c294c86a8552a4baaa5b473672'>container: Correctly report exit status.</a><span class='msg-avail'>...<span class='msg-tooltip'>* gnu/build/linux-container.scm (container-excursion): Return the raw
status value.
* tests/containers.scm ("container-excursion, same namespaces"): Add
'status:exit-val' call.
* guix/scripts/container/exec.scm (guix-container-exec): Correctly
handle the different cases.
</span></span></td><td>Ludovic Courtès</td></tr>
<tr><td><span title='2022-09-24 17:59:04 +0200'>2022-09-24</span></td><td><a href='/guix/commit/gnu/build/linux-container.scm?id=00d5bb5d7f18555c250b4a6ef0b33b628acc3a3a'>linux-container: Mark socket pair as SOCK_CLOEXEC.</a><span class='msg-avail'>...<span class='msg-tooltip'>* gnu/build/linux-container.scm (run-container): Pass SOCK_CLOEXEC to
'socketpair'.
</span></span></td><td>Ludovic Courtès</td></tr>
<tr><td><span title='2022-09-20 19:24:31 +0200'>2022-09-20</span></td><td><a href='/guix/commit/gnu/build/linux-container.scm?id=6abdcef4a68e98f538ab69fde096adc5f5ca4ff4'>linux-container: 'container-excursion*' marks its FDs as FD_CLOEXEC.</a><span class='msg-avail'>...<span class='msg-tooltip'>Fixes &lt;https://issues.guix.gnu.org/57827&gt;.
Reported by Mathieu Othacehe &lt;othacehe@gnu.org&gt;.

Fixes a regression introduced with the Shepherd 0.9.2 upgrade in
1ba0e38267c9ff8bb476285091be6e297bbf136e, whereby IN and OUT would no
longer be closed when 'fork+exec-command/container' would call
'exec-command*' as part of the THUNK passed to 'container-excursion*'.

This is because the Shepherd 0.9.2 assumes file descriptors are properly
marked as O_CLOEXEC and, consequently, 'exec-command' no longer run the
close(2) loop prior to 'exec'.

* gnu/build/linux-container.scm (container-excursion*): Add calls to
'fcntl'.
</span></span></td><td>Ludovic Courtès</td></tr>