unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: bdju <bdju@tilde.team>
Cc: 43685@debbugs.gnu.org
Subject: bug#43685: xonotic player ID and stats reporting are broken
Date: Tue, 29 Sep 2020 12:58:18 +0200	[thread overview]
Message-ID: <87v9fwj1dh.fsf@nckx> (raw)
In-Reply-To: <C5ZH42A70H95.TM31JKCBOQDP@masaki>

[-- Attachment #1: Type: text/plain, Size: 930 bytes --]

Hullo bdju,

bdju via Bug reports for GNU Guix 写道:
> This isn't working. I asked in the #xonotic IRC and it sounds 
> like this
> sometimes happens from a certain file being left out of distro 
> packages.
> "it tends to happen when using linux distro packages that omit
> key_0.d0pk" is the exact quote.

We don't omit the file.  It's in the root of the upstream 
xonotic-0.8.2.zip & is copied to <xonotic-data>/share/xonotic 
which is then symlinked to <xonotic>/share/xonotic:

  λ ls $(guix build xonotic)/share/xonotic
  data/  key_0.d0pk  server/

Perhaps the engine has trouble finding it, or perhaps it's not the 
reason for your missing stats after all.

I'm downloading the (gig of) sources to take a closer look on the 
bus.

> This stats reporting does not seem like a privacy concern, and 
> it's
> optional, so I doubt it was broken on purpose.

Certainly not!

Thanks,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2020-09-29 10:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29  1:48 bug#43685: xonotic player ID and stats reporting are broken bdju via Bug reports for GNU Guix
2020-09-29 10:58 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-09-29 19:52   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-05-03 15:18     ` bdju via Bug reports for GNU Guix
2022-12-21 23:04 ` bug#43685: xonotic player ID and starts " Denis 'GNUtoo' Carikli

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v9fwj1dh.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=43685@debbugs.gnu.org \
    --cc=bdju@tilde.team \
    --cc=me@tobias.gr \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).