From: bingulo <bingulo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: Orthanc-1.11.1
Date: Tue, 09 Aug 2022 18:51:17 +0200 [thread overview]
Message-ID: <20220809165117.e6I7Dxi6Sun_2-UBJIH0oXTuYhunTW29SMOqcxBaAa8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38537@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 498 bytes --]
New comment by bingulo on void-packages repository
https://github.com/void-linux/void-packages/pull/38537#issuecomment-1209628403
Comment:
> No, just depend on `python3`. We only support one version of py3 in the repository and I bump _every_ Python package when we do a minor version jump.
Of course, but I'm thinking on some case as version hold by user. In that example, the xbps shouldn't allow to upgrade python to 3.11 if the user holds Orthanc-Python on a version wich depends on 3.10.
next prev parent reply other threads:[~2022-08-09 16:51 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 17:30 [PR PATCH] " bingulo
2022-08-08 18:23 ` abenson
2022-08-08 18:30 ` [PR REVIEW] " ahesford
2022-08-08 18:30 ` ahesford
2022-08-08 18:30 ` ahesford
2022-08-08 18:30 ` Chocimier
2022-08-08 18:30 ` Chocimier
2022-08-08 18:30 ` Chocimier
2022-08-08 18:30 ` Chocimier
2022-08-08 18:30 ` Chocimier
2022-08-08 18:55 ` [PR PATCH] [Updated] " bingulo
2022-08-08 19:03 ` [PR REVIEW] " bingulo
2022-08-08 19:10 ` [PR PATCH] [Updated] " bingulo
2022-08-08 19:16 ` bingulo
2022-08-08 19:25 ` bingulo
2022-08-08 19:29 ` bingulo
2022-08-08 19:48 ` bingulo
2022-08-08 20:07 ` bingulo
2022-08-08 20:10 ` Chocimier
2022-08-08 20:33 ` [PR PATCH] [Updated] " bingulo
2022-08-08 20:34 ` [PR REVIEW] " bingulo
2022-08-08 20:35 ` bingulo
2022-08-08 20:39 ` bingulo
2022-08-08 21:52 ` classabbyamp
2022-08-09 1:37 ` [PR PATCH] [Updated] " bingulo
2022-08-09 1:37 ` [PR REVIEW] " bingulo
2022-08-09 2:50 ` [PR PATCH] [Updated] " bingulo
2022-08-09 2:51 ` bingulo
2022-08-09 14:36 ` [PR REVIEW] " Chocimier
2022-08-09 14:36 ` Chocimier
2022-08-09 14:36 ` Chocimier
2022-08-09 15:39 ` bingulo
2022-08-09 15:40 ` bingulo
2022-08-09 15:57 ` [PR PATCH] [Updated] " bingulo
2022-08-09 15:58 ` [PR REVIEW] " bingulo
2022-08-09 16:45 ` bingulo
2022-08-09 16:48 ` ahesford
2022-08-09 16:51 ` bingulo [this message]
2022-08-09 16:56 ` [PR PATCH] [Updated] " bingulo
2022-08-09 17:01 ` bingulo
2022-08-09 17:04 ` [PR PATCH] [Updated] " bingulo
2022-08-09 17:47 ` Chocimier
2022-08-09 17:53 ` bingulo
2022-08-09 17:53 ` bingulo
2022-08-09 20:12 ` [PR PATCH] [Updated] " bingulo
2022-08-10 1:26 ` bingulo
2022-08-10 2:26 ` bingulo
2022-08-10 2:31 ` bingulo
2022-08-10 2:37 ` bingulo
2022-08-11 16:43 ` [PR PATCH] [Updated] " bingulo
2022-08-24 22:36 ` bingulo
2022-10-13 19:52 ` bingulo
2022-11-15 22:18 ` anhangah
2022-11-17 13:46 ` anhangah
2022-11-17 13:54 ` anhangah
2022-11-17 13:59 ` anhangah
2022-11-17 14:03 ` New package: Orthanc-1.11.2 anhangah
2022-11-22 20:24 ` [PR PATCH] [Updated] " anhangah
2022-11-22 23:28 ` anhangah
2022-11-23 20:43 ` anhangah
2022-12-30 2:10 ` anhangah
2023-02-08 15:23 ` gcarlos64
2023-05-10 1:51 ` github-actions
2023-05-24 1:56 ` [PR PATCH] [Closed]: " github-actions
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=20220809165117.e6I7Dxi6Sun_2-UBJIH0oXTuYhunTW29SMOqcxBaAa8@z \
--to=bingulo@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).