From: lfdebrux <lfdebrux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] xuname says notuptodate even when system is up to date when not run as root
Date: Sat, 30 Jan 2021 09:54:41 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28322@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
New issue by lfdebrux on void-packages repository
https://github.com/void-linux/void-packages/issues/28322
Description:
### System
* xuname: Void 5.10.11_1 x86_64-musl GenuineIntel notuptodate rF (but I am up to date)
* package: xtools-0.62_1
### Expected behavior
When I have just run `xbps-install -Su` xuname does not say `notuptodate`, even if I'm not running it as root.
### Actual behavior
```
$ sudo xbps-install -u
$ xuname
Do you want to import this public key? [Y/n]
Void 5.10.11_1 x86_64-musl GenuineIntel notuptodate rF
```
### Steps to reproduce the behavior
I believe the problem is related to the output of `xbps-install -Mun`, which when not run as root asks about importing a public key:
```
$ xbps-install -Mun
`https://alpha.de.repo.voidlinux.org/current/musl' repository has be
en RSA signed by "Void Linux"
Fingerprint: 60:ae:0c:d6:f0:95:17:80:bc:93:46:7a:89:af:a3:2d
Do you want to import this public key? [Y/n]
```
If I run `sudo xbps-install -Mun` then no message is printed, and then if I run `sudo xuname` then it correctly reports that my system is up to date.
next reply other threads:[~2021-01-30 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 8:54 lfdebrux [this message]
2021-01-30 12:20 ` Johnnynator
2021-01-30 13:35 ` lfdebrux
2021-01-30 17:09 ` Anachron
2021-01-30 17:27 ` Duncaen
2021-01-30 21:21 ` lfdebrux
2021-01-30 21:21 ` [ISSUE] [CLOSED] " lfdebrux
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28322@inbox.vuxu.org \
--to=lfdebrux@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).