From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: empathy: remove package.
Date: Mon, 22 Mar 2021 02:04:20 +0100 [thread overview]
Message-ID: <20210322010420.N2ycmwouMTJBONSmUULmGoidBjmPC3NHrcyijA11t74@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28963@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1941 bytes --]
There's a closed pull request on the void-packages repository
empathy: remove package.
https://github.com/void-linux/void-packages/pull/28963
Description:
Has been abandonware for at least three years, as seen in [1].
This is not great for a network exposed messenger, though it hasn't
received any CVEs as far as I could find.
It is also a blocker for enchant 1.x removal, though this is easy to fix
with the patch from [2]. I decided not to go with this option for the
reason listed above.
[1] https://gitlab.gnome.org/GNOME/empathy/-/commit/37976f61d8dddc950a9b7d3b1417d784b331927f
[2] https://gitlab.gnome.org/GNOME/empathy/-/merge_requests/3
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
prev parent reply other threads:[~2021-03-22 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 22:24 [PR PATCH] " ericonr
2021-02-21 22:54 ` Gottox
2021-03-22 1:04 ` ericonr
2021-03-22 1:04 ` ericonr [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=20210322010420.N2ycmwouMTJBONSmUULmGoidBjmPC3NHrcyijA11t74@z \
--to=ericonr@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).