From: bluej99 <bluej99@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Chromium seemingly has incomplete dependencies
Date: Fri, 04 Feb 2022 05:56:42 +0100 [thread overview]
Message-ID: <20220204045642.xSTmB_acrw9ukuyFIUcgONk7DTK3nVwVh3Ci8CaZths@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35387@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
New comment by bluej99 on void-packages repository
https://github.com/void-linux/void-packages/issues/35387#issuecomment-1029633194
Comment:
> I do not have `electron13` installed and I've had no issues with `chromium`, so I'm unsure of this.
This is what others also told me. I'm not sure where I screwed up. I've decided to keep electron13 installed just for this reason
prev parent reply other threads:[~2022-02-04 4:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 21:34 [ISSUE] " bluej99
2022-02-04 4:53 ` abenson
2022-02-04 4:56 ` [ISSUE] [CLOSED] " bluej99
2022-02-04 4:56 ` bluej99 [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=20220204045642.xSTmB_acrw9ukuyFIUcgONk7DTK3nVwVh3Ci8CaZths@z \
--to=bluej99@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).