unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tanguy Le Carrour <tanguy@bioneland.org>
To: Pierre Langlois <pierre.langlois@gmx.com>
Cc: go.wigust@gmail.com, 42511@debbugs.gnu.org
Subject: [bug#42511] [PATCH v2 1/2] gnu: python-slugify: Update to 4.0.1.
Date: Mon, 27 Jul 2020 12:56:15 +0200	[thread overview]
Message-ID: <20200727105615.xq2eaverkr5iecpw@melmoth> (raw)
In-Reply-To: <87v9i9iafn.fsf@gmx.com>

Le 07/27, Pierre Langlois a écrit :
> Tanguy Le Carrour writes:
> > Le 07/25, Pierre Langlois a écrit :
> >> Tanguy Le Carrour writes:
> >> 
> >> > * gnu/packages/patches/python-slugify-depend-on-unidecode.patch: Delete file.
> >> […]
> >> I remember adding this patch, without it csvkit doesn't build […]
> >> I'm not familiar enough with the python build/test process to know for
> >> sure if this is an issue with csvkit or python-slugify. We could just
> >> package the python-text-unidecode package, but AFAIU the
> >> python-unidecode package we already have is equivalent so it should be
> >> OK. But somehow csvkit's check procedure doesn't see that.
> >> 
> >> Should we keep this patch around? Or maybe somebody has a better idea of
> >> what's going on? I realise now I should have added a comment here :-).
> >
> > Thanks for raising the issue!
> > As we already have `python-text-unidecode`, I tried patching `csvkit` and
> > it builds again. But I haven't tried `csvkit` itself!
> > Does it sound like a proper solution to you?
> 
> Oh, I didn't realise we already had this package, yep, that sounds great
> to me!

Submitted as #42556. I guess the commit message should contain "fix"…
but right now, `csvkit` is not (yet) broken.

-- 
Tanguy




  reply	other threads:[~2020-07-27 10:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24  8:16 [bug#42511] [PATCH 0/2] gnu: python-cookiecutter: Update to 1.7.2 Tanguy Le Carrour
2020-07-24  8:17 ` [bug#42511] [PATCH 1/2] gnu: python-slugify: Update to 4.0.1 Tanguy Le Carrour
2020-07-24  8:17   ` [bug#42511] [PATCH 2/2] gnu: python-cookiecutter: Update to 1.7.2 Tanguy Le Carrour
2020-07-25 10:36   ` [bug#42511] [PATCH 1/2] gnu: python-slugify: Update to 4.0.1 Oleg Pykhalov
2020-07-25 17:23 ` [bug#42511] [PATCH v2 " Tanguy Le Carrour
2020-07-25 17:23   ` [bug#42511] [PATCH v2 2/2] gnu: python-cookiecutter: Update to 1.7.2 Tanguy Le Carrour
2020-07-25 17:59   ` [bug#42511] [PATCH v2 1/2] gnu: python-slugify: Update to 4.0.1 Pierre Langlois
2020-07-27  8:43     ` Tanguy Le Carrour
2020-07-27  9:17       ` Pierre Langlois
2020-07-27 10:56         ` Tanguy Le Carrour [this message]
2020-07-27 20:08 ` [bug#42511] [PATCH v3 1/3] " Tanguy Le Carrour
2020-07-27 20:08   ` [bug#42511] [PATCH v3 2/3] gnu: csvkit: Fix problem caused by the update of python-slugify Tanguy Le Carrour
2020-07-27 20:08   ` [bug#42511] [PATCH v3 3/3] gnu: python-cookiecutter: Update to 1.7.2 Tanguy Le Carrour
2020-07-29 22:30 ` bug#42511: [PATCH 0/2] " Marius Bakke

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=20200727105615.xq2eaverkr5iecpw@melmoth \
    --to=tanguy@bioneland.org \
    --cc=42511@debbugs.gnu.org \
    --cc=go.wigust@gmail.com \
    --cc=pierre.langlois@gmx.com \
    /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).