unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Wiktor Zelazny <wzelazny@vurv.cz>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: "56389@debbugs.gnu.org" <56389@debbugs.gnu.org>
Subject: bug#56389: ruby-nokogiri may be non-deterministic
Date: Fri, 7 Oct 2022 06:54:25 +0000	[thread overview]
Message-ID: <Yz/NHHIFmqXahPNO@319guix> (raw)
In-Reply-To: <87tu7szwch.fsf@gmail.com>

On Thu, Jul 07, 2022 at 01:06:06PM -0400, Maxim Cournoyer wrote:
>
> Wiktor Zelazny <wzelazny@vurv.cz> writes:
>
> > ruby-nokogiri@1.10.9 to be exact. Did not check @1.12.5. Guix version
> > 4d126e776239cc2e9b2e39718d0a1051f4a9bbc3.
>
> I checked, and only 1.10.9 is nondeterministic.  We should work toward
> eliminating 1.10.9.

Hi Maxim,

Sorry for responding so late.

The 1.10.9 comes with the TODO

   ;; TODO: In the next rebuild cycle, provide texlive a version of ruby-hydra
   ;; that does not depend on byebug and rspec, so that their dependencies can
   ;; be updated more freely.  For now pin this version to avoid rebuilds.

ruby-nokogiri@1.10.9 is an indirect input of ruby-hydra, which in turn
is an input of texlive-hyphen-package. So nothing can be done until the
“next texlive rebuild cycle”. How long are the cycles, and is the
current one coming to an end soon by a chance?

WŻ

      reply	other threads:[~2022-10-07  6:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05  5:09 bug#56389: ruby-nokogiri may be non-deterministic Wiktor Zelazny
2022-07-05  5:15 ` Wiktor Zelazny
2022-07-07 17:06   ` Maxim Cournoyer
2022-10-07  6:54     ` Wiktor Zelazny [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=Yz/NHHIFmqXahPNO@319guix \
    --to=wzelazny@vurv.cz \
    --cc=56389@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.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).