unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org, Mathieu Lirzin <mthl@gnu.org>
Subject: Re: guix weather issue? (was Re: guix package builds, subsitutes and --no-build)
Date: mer, 27 feb 2019 09:21:56 +0100	[thread overview]
Message-ID: <87d0nd4p5n.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <874l8pu1sw.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3035 bytes --]

Hi Chris,

Chris Marusich <cmmarusich@gmail.com> writes:

> Giovanni Biscuolo <g@xelera.eu> writes:
>
>> AFAIU the issue is "guix weather" reporting on the availability related
>> to current master and not of user commit: am I wrong?
>
> I'm not sure.  That would explain the issue you saw.  I haven't checked
> the code.  Maybe you could take a peek?  If "guix weather" is using
> master branch and ignoring the current channel configuration, it seems
> like it might be unintended behavior.

I'll try to understand guix weather code (guix/guix/scripts/weather.scm)
but I'm pretty new to Guile and Guix so it will be a long study for me

...so sorry, but for now do not count on me for a timely report on this
:-)

>> a little (digression
>>
>>   anyway even if that is not the issue, users should have some way to
>>   check if a substitute is available for their current commit, so they
>>   can decide if they are willing to locally build or not.

[...]

> I agree it would be nice if one could control the behavior more easily.
> However, someone needs to put in the time to design and implement the
> solution.  So far, I think people with time and energy have chosen
> instead to focus on improving substitute availability, in the hopes that
> it will prove more useful in the long term.

yes I'm aware of this and I find this is not a priority for Guix,
improving substitutes availability is

> Would you be interesting in working on it?

yes but for me "it's a long way to the top if you (me) wanna
rock'n'roll" :-)

[...]

> I have attempted to reproduce the issue using that information.  When I
> ran "guix pull" to use the same version of Guix you were using
> (a4fc80254a53b46b33f138d1009ddd044b8cb6be) and then ran "guix weather",
> I saw the same output as you (i.e., ci.guix.info reported that the
> substitute was available).  However, when I ran...
>
>   guix package \
>        --substitute-urls=https://ci.guix.info \
>        -p /tmp/test-profile \
>        -m /tmp/manifest.scm
>
> ...Guix began downloading chromium from ci.guix.info.  The contents of
> /tmp/manifest.scm is the same manifest you provided.  So, unfortunately
> this means I wasn't able to reproduce the issue you experienced.
> Everything seems to be working correctly on my end.

could you please report here the exact substitute derivation you got?

on Monday Ricardo told us:

>> --8<---------------cut here---------------start------------->8---
>> $ guix package -i ungoogled-chromium
>> substitute: updating substitutes from 'https://ci.guix.info'... 100.0%
>> building /gnu/store/4mvzzx2jmr4r4p2kx0hcvwr9s9lvx0gd-ungoogled-chromium-72.0.3626.109.drv...
>> \ 'set-paths' phase^C
>> --8<---------------cut here---------------end--------------->8---
>
>There is no such derivation on the server at berlin.guixsd.org.

It wold be interesting to see what derivation you got this time

Thanks!
Giovanni

[...]

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-02-27  8:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87pnrm76ta.fsf@roquette.mug.biscuolo.net>
     [not found] ` <20190220214442.GA22965@jasmine.lan>
2019-02-21 15:14   ` ci.guix.info 504 gateway timeout (was Re: guix package builds, subsitutes and --no-build) Giovanni Biscuolo
2019-02-21 15:49     ` Ricardo Wurmus
2019-02-21 16:32       ` Mathieu Lirzin
2019-02-21 17:03         ` Giovanni Biscuolo
2019-02-21 18:29           ` Ricardo Wurmus
2019-02-22  4:46           ` Chris Marusich
2019-02-23 13:01         ` Alex Vong
2019-02-22  3:41     ` Chris Marusich
2019-02-25 13:11       ` Giovanni Biscuolo
2019-02-25 13:17         ` Ricardo Wurmus
2019-02-25 13:22           ` Ricardo Wurmus
2019-02-25 14:53             ` Giovanni Biscuolo
2019-02-25 15:10               ` Ricardo Wurmus
2019-02-25 15:37                 ` Mathieu Lirzin
2019-02-25 15:49                   ` Ricardo Wurmus
2019-02-25 16:18                     ` guix weather issue? " Giovanni Biscuolo
2019-02-26  7:07                       ` Chris Marusich
2019-02-26  9:33                         ` Giovanni Biscuolo
2019-02-27  7:29                           ` Chris Marusich
2019-02-27  8:21                             ` Giovanni Biscuolo [this message]
2019-02-27 17:53                               ` Chris Marusich
2019-02-27  8:26                             ` Björn Höfling
2019-03-03 16:06         ` ci.guix.info 504 gateway timeout " Mark H Weaver
2019-03-04 18:56           ` Leo Famulari
2019-02-25 19:13     ` swedebugia
2019-02-25 20:26       ` Giovanni Biscuolo
2019-02-25 20:31       ` Ricardo Wurmus
2019-02-25 20:46         ` Leo Famulari
2019-02-26 10:26           ` Giovanni Biscuolo

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=87d0nd4p5n.fsf@roquette.mug.biscuolo.net \
    --to=g@xelera.eu \
    --cc=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mthl@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.
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).