From: "Benjamin" <benjamin@uvy.fr>
To: 63250@debbugs.gnu.org
Subject: bug#63250: package dante : socksify: error: dante client not built with preloading support
Date: Wed, 03 May 2023 15:55:36 +0200 [thread overview]
Message-ID: <CSCON2VSU156.3J9X3VHN2OD93@robot.uvy.fr> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1125 bytes --]
Hello,
Dante package is not compiled with preloading support but it
could be
To reproduce :
guix shell dante w3m
echo "<hmtl><h1> Hello </h1> <p> World ! </p> </html>" | (
export SOCKS_SERVER="127.0.0.1:1"
exec socksify w3m -T text/html -dump
)
Following error is returned
error: dante client not built with preloading support.
Here is the result without socksify
```
echo "<hmtl><h1> Hello </h1> <p> World ! </p> </html>" | (w3m -T text/html -dump)
```
For additional information, I faced the problem when using the "html"
filter of aerc
cat /gnu/store/...aerc.../share/aerc/filters/html
```
#!/gnu/store/rib9g2ig1xf3kclyl076w28parmncg4k-bash-minimal-5.1.16/bin/sh
# aerc filter which runs w3m using socksify (from the dante package) to prevent
# any phoning home by rendered emails
export SOCKS_SERVER="127.0.0.1:1"
exec socksify w3m \
-I UTF-8 \
-T text/html \
-cols $(tput cols) \
-dump \
-o display_imageúlse \
-o display_link_number=true
```
It seems that there was also these problem on the side of nixos :
https://github.com/NixOS/nixpkgs/issues/73697
next reply other threads:[~2023-05-07 7:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 13:55 Benjamin [this message]
2023-12-20 7:18 ` bug#63250: package dante : socksify: error: dante client not built with preloading support Nguyễn Gia Phong via Bug reports for GNU Guix
2024-02-15 16:18 ` Simon Tournier
2024-02-18 8:33 ` Nguyễn Gia Phong via Bug reports for GNU Guix
2024-02-19 16:33 ` Simon Tournier
2024-02-19 20:44 ` Benjamin via Bug reports for GNU Guix
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=CSCON2VSU156.3J9X3VHN2OD93@robot.uvy.fr \
--to=benjamin@uvy.fr \
--cc=63250@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.