From: reivilibre <reivilibre@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Revert "python3-poetry-core: update to 1.3.1."
Date: Fri, 07 Oct 2022 13:38:59 +0200 [thread overview]
Message-ID: <20221007113859.ejQ4itDUdKuYIiBTyA-IFFs8XB3S178TzEyB5crNkXw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39777@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
New comment by reivilibre on void-packages repository
https://github.com/void-linux/void-packages/pull/39777#issuecomment-1271480156
Comment:
> pointless dependency checks
The dependency checks are not pointless; they prevent you from running Synapse with out of date deps, which isn't hard to do due to the absolute minefields in installing Python packages. They were added after getting enough bug reports from people doing that, which ultimately takes a lot of time and effort to respond to.
> Synapse really doesn't seem to have its act together wrt dependency handling
Problem is that everything is a damned if you do, damned if you don't situation. There are many ways to install Synapse and distro packages are but some of them :).
We do make a lot of effort to keep things workable for distro packages but having old versions break under our feet because of dependency changes is also a massive pain to deal with. If you're aware of better ways of doing this then let us know.
next prev parent reply other threads:[~2022-10-07 11:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 17:29 [PR PATCH] " icp1994
2022-10-06 17:41 ` ahesford
2022-10-06 17:51 ` icp1994
2022-10-06 18:04 ` ahesford
2022-10-06 18:12 ` icp1994
2022-10-06 19:10 ` ahesford
2022-10-07 11:38 ` reivilibre [this message]
2022-10-07 12:11 ` ahesford
2022-10-07 13:20 ` reivilibre
2022-10-07 14:33 ` [PR PATCH] [Closed]: " ahesford
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=20221007113859.ejQ4itDUdKuYIiBTyA-IFFs8XB3S178TzEyB5crNkXw@z \
--to=reivilibre@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).