Github messages for voidlinux
 help / color / mirror / Atom feed
From: begss <begss@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: telegram-tg-0.17.0
Date: Tue, 11 May 2021 19:01:32 +0200	[thread overview]
Message-ID: <20210511170132.6eVbKXGvxQ4FPW4YfpIk-ag2wuI_iLuB_rRQHBHl9sQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30458@inbox.vuxu.org>

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

New comment by begss on void-packages repository

https://github.com/void-linux/void-packages/pull/30458#issuecomment-838827252

Comment:
It's already a known issue and there is a better fix, I should have look at issues first.
https://github.com/alexander-akhmetov/python-telegram/issues/119
Looks like upstream won't change library detection behavior in the foreseeable future

  parent reply	other threads:[~2021-05-11 17:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-23 18:27 [PR PATCH] New package: telegram-tg-0.12.0 begss
2021-04-25 18:30 ` Piraty
2021-04-25 21:42 ` FollieHiyuki
2021-04-26 14:34 ` [PR PATCH] [Updated] " begss
2021-04-26 18:36 ` New package: telegram-tg-0.15.0 FollieHiyuki
2021-04-26 18:39 ` FollieHiyuki
2021-04-26 19:53 ` [PR REVIEW] " Piraty
2021-04-26 19:53 ` Piraty
2021-04-27 14:47 ` [PR PATCH] [Updated] " begss
2021-04-27 14:56 ` [PR PATCH] [Updated] New package: telegram-tg-0.16.0 begss
2021-04-27 14:59 ` begss
2021-04-27 20:07 ` begss
2021-05-01 14:53 ` [PR REVIEW] New package: telegram-tg-0.17.0 Piraty
2021-05-02  8:10 ` [PR PATCH] [Updated] " begss
2021-05-04  8:54 ` begss
2021-05-10  9:56 ` [PR REVIEW] " Piraty
2021-05-10 15:06 ` [PR PATCH] [Updated] " begss
2021-05-10 19:38 ` Piraty
2021-05-11 16:56 ` begss
2021-05-11 17:01 ` begss [this message]
2021-05-11 17:01 ` begss
2021-05-11 17:11 ` [PR PATCH] [Updated] " begss
2021-05-16 16:11 ` [PR REVIEW] " Piraty
2021-05-16 19:32 ` [PR PATCH] [Updated] " begss
2021-05-17 12:07 ` [PR PATCH] [Merged]: " Piraty

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=20210511170132.6eVbKXGvxQ4FPW4YfpIk-ag2wuI_iLuB_rRQHBHl9sQ@z \
    --to=begss@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).