Github messages for voidlinux
 help / color / mirror / Atom feed
From: ar-jan <ar-jan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Update python3-aiohttp_socks to 0.5.5 and add dependencies
Date: Mon, 01 Feb 2021 19:36:09 +0100	[thread overview]
Message-ID: <20210201183609.j8qS9M5hSswksqgTeEy0YWdGHJPVvLvdQTj2nl--YGI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28272@inbox.vuxu.org>

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

New comment by ar-jan on void-packages repository

https://github.com/void-linux/void-packages/pull/28272#issuecomment-771067875

Comment:
I can build all included new packages and the updated package locally with `xbps-src pkg -Q`, but for some reason the CI keeps failing on some arches. Any clues?

  parent reply	other threads:[~2021-02-01 18:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 19:13 [PR PATCH] New package: python3-python-socks-1.2.0 ar-jan
2021-01-27 21:48 ` [PR PATCH] [Updated] " ar-jan
2021-01-27 22:05 ` ar-jan
2021-01-27 22:23 ` ar-jan
2021-01-27 23:02 ` ar-jan
2021-01-28 15:10 ` [PR REVIEW] " sgn
2021-01-28 16:53 ` ar-jan
2021-01-28 17:25 ` [PR PATCH] [Updated] " ar-jan
2021-01-28 17:28 ` ar-jan
2021-01-28 17:49 ` ar-jan
2021-01-28 17:57 ` ar-jan
2021-01-28 18:04 ` ar-jan
2021-01-29 16:53 ` ar-jan
2021-01-30 18:34 ` [PR REVIEW] New package: python3-socks-1.2.0 Chocimier
2021-01-30 18:34 ` Chocimier
2021-01-30 21:54 ` [PR PATCH] [Updated] " ar-jan
2021-02-01 18:00 ` ar-jan
2021-02-01 18:34 ` Update python3-aiohttp_socks to 0.5.5 and add dependencies ar-jan
2021-02-01 18:36 ` ar-jan [this message]
2021-02-02 18:17 ` [PR PATCH] [Updated] " ar-jan
2021-02-02 22:26 ` ar-jan
2021-02-08 18:31 ` ar-jan
2021-03-08 18:15 ` ar-jan
2021-03-08 18:15 ` [PR PATCH] [Closed]: " ar-jan

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=20210201183609.j8qS9M5hSswksqgTeEy0YWdGHJPVvLvdQTj2nl--YGI@z \
    --to=ar-jan@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).