Github messages for voidlinux
 help / color / mirror / Atom feed
From: Frick-David <Frick-David@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Update to Python 3.9 appears to break multiple python packages in a Docker Container
Date: Mon, 30 Nov 2020 04:16:19 +0100	[thread overview]
Message-ID: <20201130031619.qCBASSiVUvaWv11C9f7eGC9KZuPuCZYxx_cu0oLRkKA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25606@inbox.vuxu.org>

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

New comment by Frick-David on void-packages repository

https://github.com/void-linux/void-packages/issues/25606#issuecomment-735520816

Comment:
@ahesford what you wrote seemed to fix the error . I was not using the python containers as those are based on Debian, not void. I do believe it much have been something in Docker's caching. Thanks for pointing that out. You were correct to close the issue. Thanks!

      parent reply	other threads:[~2020-11-30  3:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14 18:41 [ISSUE] " Frick-David
2020-10-14 19:26 ` ahesford
2020-10-14 19:51 ` ahesford
2020-11-05 14:15 ` ahesford
2020-11-30  3:16 ` Frick-David [this message]

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=20201130031619.qCBASSiVUvaWv11C9f7eGC9KZuPuCZYxx_cu0oLRkKA@z \
    --to=frick-david@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).