From: hholst80 <hholst80@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] remove cowsay as it promote drug use (bong.cow)
Date: Fri, 27 Oct 2023 01:15:15 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46920@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
New issue by hholst80 on void-packages repository
https://github.com/void-linux/void-packages/issues/46920
Description:
### Is this a new report?
Yes
### System Info
Void x86_64
### Package(s) Affected
cowsay
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
The upstream repository is archived and contains content that the void maintainers does not want. I assume that Void linux does not promote drug use (smoking crack in a bong pipe is bad, mkay) I think it would be safest for us all if the cowsay package is removed completely.
### Expected behaviour
Void package should be safe to use.
### Actual behaviour
cowsay should follow suite of all other linux distros and remove bong.cow at a minimum or preferably remove it completely, as it is unmaintained by upstream and void package maintainers seems to fall short of keeping security tight.
### Steps to reproduce
1. install cowsay
2. run `cowsay -f bong 'Kids, drugs are cool!'`
next reply other threads:[~2023-10-26 23:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 23:15 hholst80 [this message]
2023-10-26 23:46 ` ahesford
2023-10-26 23:46 ` classabbyamp
2023-10-26 23:46 ` [ISSUE] [CLOSED] " ahesford
2023-10-27 11:11 ` hholst80
2023-10-27 11:13 ` hholst80
2023-10-27 11:13 ` hholst80
2023-10-27 11:16 ` hholst80
2023-10-27 11:33 ` ahesford
2023-10-27 14:20 ` sgn
2023-10-27 14:21 ` sgn
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46920@inbox.vuxu.org \
--to=hholst80@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).