unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: beffa@ieee.org, post@thomasdanckaert.be
Cc: guix-devel@gnu.org
Subject: Re: python-mistune
Date: Thu, 26 Jan 2017 08:32:20 +0100	[thread overview]
Message-ID: <bbcc530c-a73d-b894-b8a9-a528ed8c17d3@tobias.gr> (raw)
In-Reply-To: <CAKrPhPNrHPwkL63f4EXFB3koBB=qT1yFcC-Bt3GWUo8UYH+hRw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 908 bytes --]

Frederico,

On 25/01/17 21:58, Federico Beffa wrote:
> Hi Thomas,

Might you've confused Thomas & me? I'm the one who updated the package
in question. It should be fixed in master now[0].

> It seems that version 0.7.3 is not present from the source that you 
> indicated:

This was my first try at using the Pypi updater — which is really cool,
but it seems to have downloaded & hashed at least two packages[1] from a
new URI while leaving the old one in place.

Everything works fine here, then blows up on other folks' machines. Not
a great feeling. I'll keep using the ‘emacs && guix build && guix build’
updater for now. :-)

Anyone: does the updater use pypi-uri unconditionally? I don't remember
ignoring any warnings.

Kind regards,

T G-R

[0]: Commit eff8d773d65d031e67f492c790de3b4b48549883.
[1]: 5e217a8b4b47fc8914f623db5acf96d0e5099c2c fixes a similar issue.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 476 bytes --]

  reply	other threads:[~2017-01-26  7:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 20:58 python-mistune Federico Beffa
2017-01-26  7:32 ` Tobias Geerinckx-Rice [this message]
2017-01-26  7:43   ` python-mistune Tobias Geerinckx-Rice
2017-01-26  8:04   ` python-mistune Federico Beffa
2017-01-26 10:23     ` python-mistune Ludovic Courtès
2017-01-26 12:25       ` python-mistune Federico Beffa

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=bbcc530c-a73d-b894-b8a9-a528ed8c17d3@tobias.gr \
    --to=me@tobias.gr \
    --cc=beffa@ieee.org \
    --cc=guix-devel@gnu.org \
    --cc=post@thomasdanckaert.be \
    /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).