From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] yggdrasil: setpriv: libcap-ng is too old for "all" caps
Date: Wed, 30 Dec 2020 04:45:33 +0100 [thread overview]
Message-ID: <20201230034533.nlyf0o1j44oDOpi2GzV-Ci_XDKgOB6u_zvjgR2fdtzI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26188@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]
Closed issue by whoizit on void-packages repository
https://github.com/void-linux/void-packages/issues/26188
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
*output of ``xuname`` (part of xtools)*
```
~ $ xuname
Do you want to import this public key? [Y/n] Y
Void 5.8.18_1 x86_64 AuthenticAMD notuptodate rF
```
* package:
*affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
yggdrasil-0.3.14_2
### Expected behavior
### Actual behavior
### Steps to reproduce the behavior
```
~ $ doas /etc/sv/yggdrasil/run
setpriv: libcap-ng is too old for "all" caps
~ $ xrs libcap
[*] libcap-2.45_1 POSIX.1e capabilities suite
[-] libcap-devel-2.45_1 POSIX.1e capabilities suite - development files
[*] libcap-ng-0.8_2 Alternate POSIX capabilities library
[-] libcap-ng-devel-0.8_2 Alternate POSIX capabilities library - development files
[-] libcap-ng-progs-0.8_2 Alternate POSIX capabilities library - utilities
[-] libcap-ng-python-0.8_2 Alternate POSIX capabilities library - transitional dummy pkg
[-] libcap-ng-python3-0.8_2 Alternate POSIX capabilities library - Python3 bindings
[-] libcap-pam-2.34_1 POSIX.1e capabilities suite - PAM module
[*] libcap-progs-2.45_1 POSIX.1e capabilities suite - utilities
```
prev parent reply other threads:[~2020-12-30 3:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 21:55 [ISSUE] " whoizit
2020-11-07 19:28 ` Piraty
2020-11-07 20:57 ` jcgruenhage
2020-11-07 22:00 ` ericonr
2020-11-07 22:19 ` ericonr
2020-11-08 8:37 ` jcgruenhage
2020-11-08 14:24 ` ericonr
2020-12-30 3:45 ` ericonr
2020-12-30 3:45 ` ericonr [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201230034533.nlyf0o1j44oDOpi2GzV-Ci_XDKgOB6u_zvjgR2fdtzI@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).