From: RossComputerGuy <RossComputerGuy@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Cannot compile cmake with `-N` option
Date: Sun, 01 Nov 2020 16:30:10 +0100 [thread overview]
Message-ID: <20201101153010.i01M-EJYS3SamQ_nNcuW3vwP9AiKr_mjp2leC3FTV8s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26032@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]
New comment by RossComputerGuy on void-packages repository
https://github.com/void-linux/void-packages/issues/26032#issuecomment-720106216
Comment:
Alright, I merged in the fix for my repo but now I'm getting a utf8 error with ca-certificates:
```
=> ca-certificates-20200601_2: running do-pkg hook: 00-gen-pkg ...
=> Creating ca-certificates-20200601_2.x86_64.xbps for repository /home/ross/ExpidusOS/void-packages/hostdir/binpkgs ...
xbps-create: ERROR: cannot write ./usr/share/ca-certificates/mozilla/NetLock_Arany_=Class_Gold=_Főtanúsítvány.crt to archive: Can't translate pathname './usr/share/ca-certificates/mozilla/NetLock_Arany_=Class_Gold=_Főtanúsítvány.crt' to UTF-8
=> ERROR: Failed to created binary package: ca-certificates-20200601_2.x86_64.xbps!
```
I checked the pull requests and other issues, seems like nobody else has reported it. Yet again, this is an upstream issue:
```
=> ca-certificates-20200601_2: running pre-pkg hook: 999-collected-rdeps ...
libressl>=2.2.4_2 run-parts>=0
=> ca-certificates-20200601_2: running do-pkg hook: 00-gen-pkg ...
=> Creating ca-certificates-20200601_2.x86_64.xbps for repository /home/ross/void-packages/hostdir/binpkgs ...
xbps-create: ERROR: cannot write ./usr/share/ca-certificates/mozilla/NetLock_Arany_=Class_Gold=_Főtanúsítvány.crt to archive: Can't translate pathname './usr/share/ca-certificates/mozilla/NetLock_Arany_=Class_Gold=_Főtanúsítvány.crt' to UTF-8
=> ERROR: Failed to created binary package: ca-certificates-20200601_2.x86_64.xbps!
```
next prev parent reply other threads:[~2020-11-01 15:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 22:49 [ISSUE] " RossComputerGuy
2020-10-31 23:27 ` sgn
2020-10-31 23:44 ` sgn
2020-10-31 23:47 ` RossComputerGuy
2020-11-01 0:00 ` ericonr
2020-11-01 0:00 ` ericonr
2020-11-01 0:01 ` ericonr
2020-11-01 0:12 ` sgn
2020-11-01 0:16 ` RossComputerGuy
2020-11-01 0:25 ` sgn
2020-11-01 0:40 ` RossComputerGuy
2020-11-01 0:45 ` sgn
2020-11-01 0:45 ` [ISSUE] [CLOSED] " sgn
2020-11-01 0:47 ` RossComputerGuy
2020-11-01 0:47 ` sgn
2020-11-01 0:48 ` q66
2020-11-01 0:55 ` RossComputerGuy
2020-11-01 1:03 ` RossComputerGuy
2020-11-01 1:10 ` sgn
2020-11-01 4:36 ` RossComputerGuy
2020-11-01 6:27 ` RossComputerGuy
2020-11-01 12:40 ` sgn
2020-11-01 15:30 ` RossComputerGuy [this message]
2020-11-01 15:35 ` sgn
2020-11-01 15:37 ` RossComputerGuy
2020-11-01 15:48 ` RossComputerGuy
2020-11-01 15:59 ` sgn
2020-11-01 16:01 ` RossComputerGuy
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=20201101153010.i01M-EJYS3SamQ_nNcuW3vwP9AiKr_mjp2leC3FTV8s@z \
--to=rosscomputerguy@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).