Github messages for voidlinux
 help / color / mirror / Atom feed
From: jchook <jchook@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Skype segfaults when joining a call
Date: Tue, 02 Mar 2021 07:52:48 +0100	[thread overview]
Message-ID: <20210302065248.JZbPByuM-3hSSQzqQqjMTm72_o6t4WJl9G0IKyxZ0Pg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29164@inbox.vuxu.org>

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

New comment by jchook on void-packages repository

https://github.com/void-linux/void-packages/issues/29164#issuecomment-788657914

Comment:
If I had to guess the problem I would guess the find/replace on a binary:

```sh
	vsed -i usr/bin/skypeforlinux -e "s;share/;lib/;g"
```

Perhaps if we started with the RPM instead of the DEB? Or used links?

We can gesture vaguely toward this when it involves modifying binaries:
- [x]  I generally don't use the affected packages but briefly tested this PR

  parent reply	other threads:[~2021-03-02  6:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 16:00 [ISSUE] " jchook
2021-03-02  6:41 ` jchook
2021-03-02  6:43 ` jchook
2021-03-02  6:46 ` jchook
2021-03-02  6:48 ` jchook
2021-03-02  6:52 ` jchook
2021-03-02  6:52 ` jchook [this message]
2021-03-02 13:46 ` ericonr
2021-03-02 13:59 ` mobinmob
2021-03-02 14:04 ` mobinmob
2021-03-02 14:22 ` mobinmob
2021-03-02 20:00 ` jchook
2021-03-04 20:07 ` mobinmob
2021-03-05 23:07 ` jchook
2021-03-05 23:35 ` jchook
2021-04-27 23:50 ` ericonr
2021-05-29 14:34 ` mobinmob
2021-05-31  9:52 ` mobinmob
2021-06-06  2:33 ` jchook
2021-06-06  2:33 ` [ISSUE] [CLOSED] " jchook

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=20210302065248.JZbPByuM-3hSSQzqQqjMTm72_o6t4WJl9G0IKyxZ0Pg@z \
    --to=jchook@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).