unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ng0 <contact.ng0@cryptolab.net>
To: Catonano <catonano@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: patched packages
Date: Tue, 4 Apr 2017 18:07:37 +0000	[thread overview]
Message-ID: <20170404180737.24w3lt7us4orbxwq@abyayala> (raw)
In-Reply-To: <CAJ98PDxSZ_f3C4Uir2t9M9+whcrODRdfZpCgf=qN9DM9grHi5Q@mail.gmail.com>

Catonano transcribed 2.4K bytes:
> I put some patches in gnu/packages/patches, I listed them in Makefile.in

You have to list patches in "gnu/local.mk" which is used by the top
Makefile.  Not very clear at first, I know.

Is this patch in a commit upstream, or is it something which could be
done with the (substitute) procedure (is that the correct term?)?

> and tried to make guix
> 
> I get this error
> 
>   GUILEC   gnu/packages/python.go
> make[2]: ***  Nessuna regola per generare l'obiettivo
> "gnu/packages/patches/python-genshi-0.7-disable-speedups-for-python34",
> necessario per "all-am".  Arresto.
> 
> which means:
> 
> No rule for generating the target
> "gnu/packages/patches/python-genshi-0.7-disable-speedups-for-python34"
> which is required by "all-am"
> 
> Genshi needs to be patched, in order to work.
> 
> As you can see here
> https://apps.fedoraproject.org/packages/python3-genshi
> 
> The last release doesn't compile with python > 3.3, one test fails and
> other small things.
> 
> I noticed that the Genshi in Fedora is patched to fix exactly those things.
> 
> The patches that I put in gnu/packages/patches are from the Fedora rpm
> 
> How do I correctly patch Genshi ?
> 
> Thanks in advance

  parent reply	other threads:[~2017-04-04 18:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 16:23 patched packages Catonano
2017-04-04 18:01 ` Catonano
2017-04-04 18:07 ` ng0 [this message]
2017-04-04 18:26   ` Catonano

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=20170404180737.24w3lt7us4orbxwq@abyayala \
    --to=contact.ng0@cryptolab.net \
    --cc=catonano@gmail.com \
    --cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).