From: duncancmt <duncancmt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: flatpak segfaults on remote-add on aarch64 musl
Date: Wed, 09 Sep 2020 20:34:32 +0200 [thread overview]
Message-ID: <20200909183432._G9ZEzcanki09e75h3XpT3BdaMtzEwunAY8-j9p-LQM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24783@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
New comment by duncancmt on void-packages repository
https://github.com/void-linux/void-packages/issues/24783#issuecomment-689741746
Comment:
```
$ sudo xbps-pkgdb -a
ERROR: device-mapper: hash mismatch for /etc/sv/dmeventd/run.
ERROR: device-mapper: files check FAILED.
ERROR: mdocml: hash mismatch for /etc/cron.daily/makewhatis.
ERROR: mdocml: files check FAILED.
ERROR: pinebookpro-base: hash mismatch for /var/lib/alsa/asound.state.
ERROR: pinebookpro-base: files check FAILED.
ERROR: linux-firmware: /usr/lib/firmware/rockchip/dptx.bin mtime mismatch (current: 1598729144, stored 1590307167)
ERROR: linux-firmware: files check FAILED.
```
Those are all files I manually edited as part of installing my system.
next prev parent reply other threads:[~2020-09-09 18:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 14:56 [ISSUE] flatpak segfaults on remote-add duncancmt
2020-09-09 14:58 ` flatpak segfaults on remote-add on aarch64 musl ericonr
2020-09-09 16:09 ` duncancmt
2020-09-09 16:21 ` ericonr
2020-09-09 16:28 ` duncancmt
2020-09-09 16:32 ` ericonr
2020-09-09 16:33 ` duncancmt
2020-09-09 18:13 ` duncancmt
2020-09-09 18:17 ` duncancmt
2020-09-09 18:18 ` ericonr
2020-09-09 18:19 ` ericonr
2020-09-09 18:34 ` duncancmt [this message]
2020-09-09 19:03 ` ericonr
2020-09-09 19:03 ` ericonr
2020-10-12 1:03 ` duncancmt
2020-10-12 1:03 ` [ISSUE] [CLOSED] " duncancmt
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=20200909183432._G9ZEzcanki09e75h3XpT3BdaMtzEwunAY8-j9p-LQM@z \
--to=duncancmt@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).