From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] 98-fixup-gir-path: ugly hack that needs to be fixed
Date: Sun, 24 Jan 2021 22:08:30 +0100 [thread overview]
Message-ID: <20210124210830.udZbO-xIRlIfnEJP8KKR7IDsoMtb2kc3I-WKM-PgQyk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27437@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
Closed issue by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/27437
Description:
With @q66 working on cleaning up the lib32/lib64 issues with our cross toolchains and me trying them on my [`musl-1.2.1`](https://github.com/pullmoll/void-packages/commits/musl-1.2.1) branch this old and ugly hack started to fail because the `cp -a` would try to copy a directory over a symbolic link.
I managed to make this hack even uglier, i.e. hacked the ill conceived hack to somehow work again, while really the underlying issue needs to be solved.
See https://github.com/pullmoll/void-packages/commit/b52e90e61300559c45a3e0efee0a10d96097f7fc for the gory details.
I hope someone finds time and is sufficiently skilled to see where the original issue stems from.
/me am not.
Edit: WTF upload MP4 and MOV? Where is github moving to?
prev parent reply other threads:[~2021-01-24 21:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-26 3:27 [ISSUE] " pullmoll
2020-12-26 18:41 ` newbluemoon
2020-12-26 19:00 ` pullmoll
2020-12-26 19:29 ` pullmoll
2020-12-26 22:16 ` pullmoll
2020-12-27 13:55 ` pullmoll
2020-12-29 22:17 ` pullmoll
2020-12-29 22:17 ` pullmoll
2020-12-30 7:52 ` newbluemoon
2020-12-30 15:40 ` sgn
2020-12-30 15:44 ` newbluemoon
2020-12-30 16:42 ` ericonr
2020-12-30 16:56 ` pullmoll
2020-12-30 17:04 ` pullmoll
2020-12-30 23:38 ` sgn
2021-01-19 14:25 ` ericonr
2021-01-24 21:08 ` ericonr [this message]
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=20210124210830.udZbO-xIRlIfnEJP8KKR7IDsoMtb2kc3I-WKM-PgQyk@z \
--to=ericonr@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).