From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: docker-compose, python3-docker, python3-docker-pycreds
Date: Sun, 26 Sep 2021 14:49:37 +0200 [thread overview]
Message-ID: <20210926124937.7MM2EXSqSkr1RyTQfFV5P2QGl1ULaysit1HBZmKaxN8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33029@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
There's a merged pull request on the void-packages repository
docker-compose, python3-docker, python3-docker-pycreds
https://github.com/void-linux/void-packages/pull/33029
Description:
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
I have also used it heavily in the past day, due to updating several compose plays.
On top of updating to the newer version, I have also cleaned up the dependencies; for example six has not been required for more than an year (in compose, less in docker), and docker-pycreds, has been merged into docker-py (python3-docker) also for more than an year, as no other packages use it (at least in Void repos), I have also opted to remove it.
prev parent reply other threads:[~2021-09-26 12:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 4:10 [PR PATCH] " dmarto
2021-09-20 5:10 ` [PR PATCH] [Updated] " dmarto
2021-09-20 5:11 ` dmarto
2021-09-20 5:12 ` dmarto
2021-09-20 5:17 ` dmarto
2021-09-20 5:18 ` dmarto
2021-09-20 5:19 ` dmarto
2021-09-20 5:24 ` [PR PATCH] [Updated] " dmarto
2021-09-20 5:27 ` dmarto
2021-09-20 18:19 ` dmarto
2021-09-21 22:11 ` paper42
2021-09-22 5:51 ` dmarto
2021-09-23 19:49 ` [PR PATCH] [Updated] " dmarto
2021-09-23 20:02 ` dmarto
2021-09-24 8:31 ` [PR REVIEW] " paper42
2021-09-24 8:31 ` paper42
2021-09-24 14:54 ` [PR PATCH] [Updated] " dmarto
2021-09-24 14:54 ` [PR REVIEW] " dmarto
2021-09-26 12:49 ` paper42 [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=20210926124937.7MM2EXSqSkr1RyTQfFV5P2QGl1ULaysit1HBZmKaxN8@z \
--to=paper42@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).