all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Guix Devel <guix-devel@gnu.org>,
	Hartmut Goebel <h.goebel@crazy-compilers.com>
Subject: [core-updates-frozen] Tryton broken
Date: Wed, 1 Dec 2021 17:44:16 +0100	[thread overview]
Message-ID: <CAJ3okZ0DeOX77Of7J8DHSEfEP+bnj--zR3UqxZ92NfmN4cDAxg@mail.gmail.com> (raw)

Hi,

The branch core-updates-frozen will be merged soon.  Among some
breakage here or there, one block of broken packages is about 'tryton'
[1]: each points are sorted by alphabetical order, and the mouse on
the red point should provide the name of the package, then click leads
to the evaluation and from there you can access to the list of
dependencies, find the tryton broken one, click again, for instance
trytond-country, and last access to the log [2].

Well, this dashboard allow to quickly see the broken blocks.  To
directly find trytond-country, it is easy to go via:

https://ci.guix.gnu.org/search?query=spec%3Acore-updates-frozen+system%3Ax86_64-linux+trytond-country

The issue with 'trythond-*' is the new phase `sanity-check' for
python-build-system.

Any chance that someone give a look before the merge?  Otherwise,
these broken packages could land to master; which would be sad.

Cheers,
simon

1: <https://ci.guix.gnu.org/eval/50268/dashboard>
2: <https://ci.guix.gnu.org/build/1805859/log/raw>


             reply	other threads:[~2021-12-01 16:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 16:44 zimoun [this message]
2021-12-02  8:57 ` [core-updates-frozen] Tryton broken Hartmut Goebel
2021-12-03 13:41   ` Hartmut Goebel
2021-12-14  8:15     ` zimoun
2021-12-19 10:48       ` Hartmut Goebel

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJ3okZ0DeOX77Of7J8DHSEfEP+bnj--zR3UqxZ92NfmN4cDAxg@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.