From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: [RFC] python3-Django: remove package.
Date: Wed, 03 Feb 2021 15:15:27 +0100 [thread overview]
Message-ID: <20210203141527.23nAdpptfI-UNkyqDdv_3Q15B0QSL9IakK5ePx0qya0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28383@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1896 bytes --]
There's a merged pull request on the void-packages repository
[RFC] python3-Django: remove package.
https://github.com/void-linux/void-packages/pull/28383
Description:
Not maintained properly and a security risk.
I don't even know how useful this package is without any of the plugins. Anyway, it has CVEs from September (https://github.com/django/django/blob/stable/3.0.x/docs/releases/3.0.10.txt) and new ones now (https://github.com/django/django/blob/stable/3.0.x/docs/releases/3.0.12.txt) which prompted me to open this PR. If no one is going to maintain it properly, I don't think it should be in repos.
<!-- 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-02-03 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 13:41 [PR PATCH] " ericonr
2021-02-01 13:42 ` [PR PATCH] [Updated] " ericonr
2021-02-01 13:45 ` ericonr
2021-02-01 13:58 ` ericonr
2021-02-03 4:42 ` [PR PATCH] [Updated] " ericonr
2021-02-03 14:15 ` 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=20210203141527.23nAdpptfI-UNkyqDdv_3Q15B0QSL9IakK5ePx0qya0@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).