From: Leo Famulari <leo@famulari.name>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Add python-pythondialog
Date: Sat, 6 Aug 2016 22:56:15 -0400 [thread overview]
Message-ID: <20160807025615.GA30934@jasmine> (raw)
In-Reply-To: <87vazhx82d.fsf@we.make.ritual.n0.is>
On Thu, Aug 04, 2016 at 08:16:42AM +0000, ng0 wrote:
> Leo Famulari <leo@famulari.name> writes:
>
> > On Thu, Jul 28, 2016 at 12:53:15PM +0200, Vincent Legoll wrote:
> >> And actually the patch is wrong, I think it's missing a closing paren
> >> for python2-pythondialog...
> >
> > I re-wrote it using the 'python2-variant' system, as attached. Does it
> > work for you?
> >
> > I'm not sure if that's the right approach, but the resulting package for
> > python2-pythondialog has the same result as before. What I mean is that
> > I was able to download a substitute from Hydra for it, even with this
> > new package definition.
> >
> > Also, I noticed that the Python 3 and Python 2 versions of this software
> > tend to be released concurrently, so I made the Python 2 package take
> > the version of the Python 3 package. Do you think that will work?
>
> Maybe.. I have no reference why I needed this in the first
> place. PyBitmessage dependeny? I would say it works for me, but I don't
> know exactly what the problem was outside of this thread.
Okay, well I just pushed it as 1ae44b802 :) So we have it if we need it.
prev parent reply other threads:[~2016-08-07 2:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 17:05 [PATCH] Add python-pythondialog ng0
2016-07-04 18:05 ` Leo Famulari
2016-07-04 18:28 ` ng0
2016-07-27 11:37 ` ng0
2016-07-27 12:17 ` Ben Woodcroft
2016-07-27 12:30 ` Vincent Legoll
2016-07-28 9:34 ` ng0
2016-07-28 10:52 ` Vincent Legoll
2016-07-28 10:53 ` Vincent Legoll
2016-08-02 20:21 ` Leo Famulari
2016-08-04 8:16 ` ng0
2016-08-07 2:56 ` Leo Famulari [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160807025615.GA30934@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ng0@we.make.ritual.n0.is \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).