From: chrysos349 <chrysos349@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] glib: update to 2.80.0.
Date: Thu, 21 Mar 2024 22:08:52 +0100 [thread overview]
Message-ID: <20240321210852.7014F22759@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49446@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
New comment by chrysos349 on void-packages repository
https://github.com/void-linux/void-packages/pull/49446#issuecomment-2013739798
Comment:
i think python3-packaging is supposed to be in glib-devel depends.
otherwise, there will be the error, like this
```
[87/144] Generating gdbus source libsecret/secret-dbus-generated.c
FAILED: libsecret/secret-dbus-generated.c
/usr/bin/gdbus-codegen --c-generate-autocleanup all --interface-prefix org.freedesktop.Secret. --c-namespace _SecretGen --body --output libsecret/secret-dbus-generated.c ../libsecret/org.freedesktop.Secrets.xml
Traceback (most recent call last):
File "/usr/bin/gdbus-codegen", line 53, in <module>
from codegen import codegen_main
File "/usr/share/glib-2.0/codegen/codegen_main.py", line 30, in <module>
from . import dbustypes
File "/usr/share/glib-2.0/codegen/dbustypes.py", line 22, in <module>
from . import utils
File "/usr/share/glib-2.0/codegen/utils.py", line 22, in <module>
import packaging.version
ModuleNotFoundError: No module named 'packaging'
```
next prev parent reply other threads:[~2024-03-21 21:08 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 20:10 [PR PATCH] " oreo639
2024-03-21 20:22 ` [PR PATCH] [Updated] [WIP] " oreo639
2024-03-21 20:23 ` oreo639
2024-03-21 20:50 ` oreo639
2024-03-21 21:04 ` oreo639
2024-03-21 21:08 ` chrysos349 [this message]
2024-03-21 21:16 ` oreo639
2024-03-21 21:18 ` oreo639
2024-03-21 21:24 ` [PR PATCH] [Updated] " oreo639
2024-03-21 21:31 ` oreo639
2024-03-22 0:15 ` oreo639
2024-03-22 0:48 ` oreo639
2024-03-22 7:29 ` oreo639
2024-03-22 7:58 ` oreo639
2024-03-22 7:58 ` oreo639
2024-03-22 8:00 ` oreo639
2024-03-22 8:03 ` oreo639
2024-03-22 8:19 ` oreo639
2024-03-22 8:20 ` oreo639
2024-03-22 8:20 ` oreo639
2024-03-22 8:20 ` oreo639
2024-03-22 8:22 ` oreo639
2024-03-22 23:13 ` [PR PATCH] [Updated] " oreo639
2024-03-23 0:09 ` oreo639
2024-03-23 0:12 ` [PR PATCH] [Updated] " oreo639
2024-03-23 0:14 ` oreo639
2024-03-24 9:14 ` oreo639
2024-04-14 8:38 ` [PR PATCH] [Updated] " oreo639
2024-04-14 21:44 ` oreo639
2024-04-17 2:23 ` oreo639
2024-04-17 2:32 ` oreo639
2024-04-17 2:37 ` oreo639
2024-04-17 2:40 ` [PR PATCH] [Updated] " oreo639
2024-04-17 2:44 ` oreo639
2024-04-17 2:46 ` oreo639
2024-04-17 2:53 ` [PR PATCH] [Updated] " oreo639
2024-04-17 2:53 ` oreo639
2024-04-17 3:21 ` oreo639
2024-04-17 3:36 ` oreo639
2024-04-17 3:47 ` [PR PATCH] [Updated] " oreo639
2024-04-17 3:49 ` oreo639
2024-04-17 23:36 ` oreo639
2024-04-18 0:28 ` oreo639
2024-04-18 3:02 ` oreo639
2024-04-18 3:25 ` [PR PATCH] [Merged]: " oreo639
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=20240321210852.7014F22759@inbox.vuxu.org \
--to=chrysos349@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).