Github messages for voidlinux
 help / color / mirror / Atom feed
From: hervyqa <hervyqa@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: inkscape: update to 1.2
Date: Wed, 01 Jun 2022 01:36:13 +0200	[thread overview]
Message-ID: <20220531233613.Rsc6VumYjmGgCuS4PWOfTG0vq9KBheYJxN1RvkWzi4U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35454@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

New comment by hervyqa on void-packages repository

https://github.com/void-linux/void-packages/pull/35454#issuecomment-1142739916

Comment:
[Maintainer says:](https://gitlab.com/inkscape/extras/extension-manager/-/issues/25#note_966699805)

> There's two separate issues: we don't package lockfile, because it's not a dependency of cachecontrol (it's only an optional depencency: https://github.com/ionrock/cachecontrol/blob/f93d8af93e6dcc98f6867d2a09d4f68f6acc135f/setup.py#L25). So lockfile needs to be added to pyproject.toml @pulsar17.
>
> Also lockfile is deprecated (https://github.com/ionrock/cachecontrol/issues/109) and hasn't been replaced in cachecontrol since 2016.

---

Currently there is no need to add `python3-lockfile`, because the package is only optional and even then deprecated.  means that inkscape 1.2 is now intentionally not fully supported for extensions manager.

But that's okay, because adding extensions can still be done manually by adding to `~/.config/inkscape/extensions/`


  parent reply	other threads:[~2022-05-31 23:36 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07  4:11 [PR PATCH] inkscape: update to 1.1.2 hervyqa
2022-02-07  5:15 ` hervyqa
2022-02-23 16:11 ` tibequadorian
2022-02-23 23:32 ` hervyqa
2022-02-23 23:33 ` hervyqa
2022-02-23 23:38 ` hervyqa
2022-05-18  3:41 ` [PR PATCH] [Updated] " hervyqa
2022-05-18  3:59 ` [PR PATCH] [Updated] inkscape: update to 1.2 hervyqa
2022-05-18  4:12 ` hervyqa
2022-05-18  5:05 ` hervyqa
2022-05-18  5:38 ` hervyqa
2022-05-18  8:52 ` [PR PATCH] [Updated] " hervyqa
2022-05-19 14:50 ` ericonr
2022-05-20  4:34 ` hervyqa
2022-05-21 15:54 ` ericonr
2022-05-21 15:55 ` ericonr
2022-05-21 23:05 ` hervyqa
2022-05-21 23:11 ` [PR PATCH] [Updated] " hervyqa
2022-05-21 23:19 ` hervyqa
2022-05-22  1:59 ` ericonr
2022-05-23 14:10 ` hervyqa
2022-05-23 14:12 ` hervyqa
2022-05-25  1:46 ` ericonr
2022-05-27 15:33 ` hsnfirdaus
2022-05-27 18:52 ` hervyqa
2022-05-31 23:36 ` hervyqa [this message]
2022-05-31 23:36 ` hervyqa
2022-06-23 10:13 ` [PR PATCH] [Updated] " hervyqa
2022-06-23 11:24 ` hervyqa
2022-06-23 11:44 ` hervyqa
2022-06-23 11:59 ` hervyqa
2022-06-30 18:53 ` [PR REVIEW] " ericonr
2022-06-30 20:05 ` hervyqa
2022-06-30 20:17 ` [PR PATCH] [Updated] " hervyqa
2022-06-30 20:27 ` hervyqa
2022-07-07  6:25 ` hervyqa
2022-07-09 13:09 ` hervyqa
2022-07-09 13:11 ` hervyqa
2022-07-09 19:00 ` oreo639
2022-07-09 19:01 ` oreo639
2022-07-09 19:09 ` oreo639
2022-07-10  0:01 ` [PR PATCH] [Updated] " hervyqa
2022-07-15  1:43 ` hervyqa
2022-07-15  2:24 ` inkscape: update to 1.2.1 hervyqa
2022-07-16  7:24 ` paper42
2022-07-16  8:50 ` [PR PATCH] [Updated] " hervyqa
2022-07-16  8:55 ` hervyqa
2022-07-17 20:15 ` [PR PATCH] [Updated] " hervyqa
2022-09-25  0:16 ` dmarto
2022-09-25  7:59 ` [PR PATCH] [Updated] " hervyqa
2022-09-25  8:40 ` hervyqa
2022-12-07  5:43 ` [PR PATCH] [Updated] " hervyqa
2022-12-07  6:12 ` [PR PATCH] [Updated] inkscape: update to 1.2.2 hervyqa
2023-01-08 22:16 ` manfredu
2023-01-08 22:17 ` manfredu
2023-01-08 22:27 ` paper42
2023-01-08 22:43 ` manfredu
2023-02-14 15:46 ` [PR PATCH] [Updated] " hervyqa
2023-02-14 15:49 ` hervyqa
2023-04-08 12:23 ` 1is7ac3
2023-04-28 15:42 ` [PR PATCH] [Updated] " hervyqa
2023-06-16  2:44 ` hervyqa
2023-06-26  0:42 ` [PR PATCH] [Closed]: " classabbyamp

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=20220531233613.Rsc6VumYjmGgCuS4PWOfTG0vq9KBheYJxN1RvkWzi4U@z \
    --to=hervyqa@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).