Github messages for voidlinux
 help / color / mirror / Atom feed
From: kyx0r <kyx0r@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ERROR: Failed to mount / private (Invalid argument)
Date: Mon, 26 Apr 2021 15:07:49 +0200	[thread overview]
Message-ID: <20210426130749.daYbb21jytKdwuGYdQLwwTl-pyvnWOBz04h1iSEzkwA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30496@inbox.vuxu.org>

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

New comment by kyx0r on void-packages repository

https://github.com/void-linux/void-packages/issues/30496#issuecomment-826821266

Comment:
Funny how you are more concearned about me being entitled brat more than the series of technical problems and limitations that I have presented you with. Alas I conclude that xbps-src is not a very user freedom respecting software, as I can't do the things I expect to work normally with any kind of software. BTW, I did read the README and followed it step by step, however it still did not work and gave me some certificate verification error on download, which I am not even going to bother with (and no that was not because my clock is out of sync). 

If you ever get this thing working in TempleOS let me know. Thanks :)

  parent reply	other threads:[~2021-04-26 13:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25 17:07 [ISSUE] " kyx0r
2021-04-25 17:18 ` kyx0r
2021-04-25 17:24 ` kyx0r
2021-04-26  0:21 ` [ISSUE] [CLOSED] " sgn
2021-04-26  0:23 ` sgn
2021-04-26  0:23 ` sgn
2021-04-26  0:41 ` sgn
2021-04-26  3:05 ` kyx0r
2021-04-26  3:45 ` kyx0r
2021-04-26  6:17 ` Chocimier
2021-04-26 11:16 ` q66
2021-04-26 13:07 ` kyx0r [this message]
2021-04-26 13:43 ` ericonr
2021-04-26 16:16 ` sgn
2021-04-26 16:35 ` sgn
2021-04-26 23:35 ` q66
2021-04-26 23:38 ` kyx0r

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=20210426130749.daYbb21jytKdwuGYdQLwwTl-pyvnWOBz04h1iSEzkwA@z \
    --to=kyx0r@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).