From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-memory_allocator: update to 0.1.3.
Date: Sun, 09 Oct 2022 20:37:08 +0200 [thread overview]
Message-ID: <20221009183708.Y_eMdos9W-jOGe35bqqy_37CF26Pyr__XaNROGoen0U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39840@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/39840#issuecomment-1272603441
Comment:
This looks like a transient failure in `xlocate -S`?
https://github.com/void-linux/void-packages/actions/runs/3214795672/jobs/5255433612#step:10:1
I don't think there are any file conflicts here:
```
$ xbps-query -f python3-memory_allocator
/usr/lib/python3.10/site-packages/memory_allocator/__init__.pxd
/usr/lib/python3.10/site-packages/memory_allocator/__init__.py
/usr/lib/python3.10/site-packages/memory_allocator/memory.pxd
/usr/lib/python3.10/site-packages/memory_allocator/memory_allocator.pxd
/usr/lib/python3.10/site-packages/memory_allocator/memory_allocator.so
/usr/lib/python3.10/site-packages/memory_allocator/signals.pxd
/usr/lib/python3.10/site-packages/memory_allocator/test.so
/usr/lib/python3.10/site-packages/memory_allocator-0.1.3-py3.10.egg-info/PKG-INFO
/usr/lib/python3.10/site-packages/memory_allocator-0.1.3-py3.10.egg-info/SOURCES.txt
/usr/lib/python3.10/site-packages/memory_allocator-0.1.3-py3.10.egg-info/dependency_links.txt
/usr/lib/python3.10/site-packages/memory_allocator-0.1.3-py3.10.egg-info/not-zip-safe
/usr/lib/python3.10/site-packages/memory_allocator-0.1.3-py3.10.egg-info/requires.txt
/usr/lib/python3.10/site-packages/memory_allocator-0.1.3-py3.10.egg-info/top_level.txt
```
next prev parent reply other threads:[~2022-10-09 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 16:26 [PR PATCH] " tornaria
2022-10-09 18:37 ` tornaria [this message]
2022-10-11 4:49 ` [PR PATCH] [Merged]: " 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=20221009183708.Y_eMdos9W-jOGe35bqqy_37CF26Pyr__XaNROGoen0U@z \
--to=tornaria@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).