Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Add missing python_version=2 to packages the require it
Date: Sat, 25 Apr 2020 16:36:20 +0200	[thread overview]
Message-ID: <20200425143620.l2U1yGcjh9g8rvbNTjnCALu2qPZ2Pbmq-wpM_EeWrOY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21328@inbox.vuxu.org>

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

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/21328#issuecomment-619388857

Comment:
I forgot to add the `#unverified` comment, but have added it in the latest push. The point is not to get the correct version in all of these packages, but to restore the default behavior to allow these packages to build as before the behavior change. I don't have the resources to check all packages at the moment.

Because you know hugin and soundconverter are py3, I've updated those packages. I've also noticed that qytdl pulls in py3 depenedents, so I've updated that template as well. The gdb package uses version-agnostic python modules, but the template specifies python3 dependencies so I've changed that one too.

  parent reply	other threads:[~2020-04-25 14:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-25 13:54 [PR PATCH] " ahesford
2020-04-25 14:15 ` [PR PATCH] [Updated] " ahesford
2020-04-25 14:16 ` Chocimier
2020-04-25 14:35 ` [PR PATCH] [Updated] " ahesford
2020-04-25 14:35 ` ahesford
2020-04-25 14:36 ` ahesford [this message]
2020-04-25 14:41 ` [PR PATCH] [Merged]: " Chocimier

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=20200425143620.l2U1yGcjh9g8rvbNTjnCALu2qPZ2Pbmq-wpM_EeWrOY@z \
    --to=ahesford@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).