From: masato9000 <masato9000@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: TurboVNC is missing a jar file
Date: Tue, 01 Jun 2021 06:27:57 +0200 [thread overview]
Message-ID: <20210601042757.wwP1JDSh0RNCAK0RKzHI5QSHi2Tv_tuLAyTuMHcJTvY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21066@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
New comment by masato9000 on void-packages repository
https://github.com/void-linux/void-packages/issues/21066#issuecomment-851795230
Comment:
Issue +1year at the time of comment but...
For anyone wondering what the deal is...
It's more than a .jar file missing, it's all of them. And it's because they're not getting built. Attempting to do so will fail at present.
Getting them built would require _at least_ libjpeg-turbo to also be rebuilt as it needs to have the Java wrapper built to be used by this project. Note, that package is also a dep for several other packages, so touching it may not only affect this one.
If anyone decides to adopt the packages and tackle that, it'll _probably_ take care of the issue. Until someone decides its worth their while to do so, you can always use the
I like this particular viewer (don't care about the server, I usually use X11VNC) but for me, it's simple enough to snag the prebuilts from Sourceforge and run it from my homedir than worry about a void-native build.
next prev parent reply other threads:[~2021-06-01 4:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 8:24 [ISSUE] " Ypnose
2021-06-01 4:27 ` masato9000 [this message]
2022-04-16 2:02 ` github-actions
2022-04-30 2:13 ` [ISSUE] [CLOSED] " github-actions
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=20210601042757.wwP1JDSh0RNCAK0RKzHI5QSHi2Tv_tuLAyTuMHcJTvY@z \
--to=masato9000@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).