From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: zimoun <zimon.toutoune@gmail.com>, Guix Devel <guix-devel@gnu.org>
Subject: Re: [core-updates-frozen] Tryton broken
Date: Thu, 2 Dec 2021 09:57:47 +0100 [thread overview]
Message-ID: <4020db9a-833e-d1c2-4d9c-65b78460ef4a@crazy-compilers.com> (raw)
In-Reply-To: <CAJ3okZ0DeOX77Of7J8DHSEfEP+bnj--zR3UqxZ92NfmN4cDAxg@mail.gmail.com>
Hi,
TL;DR: I'll take care of this within the next few days.
Am 01.12.21 um 17:44 schrieb zimoun:
Many thanks for providing this info and the links.
> The issue with 'trythond-*' is the new phase `sanity-check' for
> python-build-system.
The way trytond modules are intended (by the maintainers) to be
installed is *very* special. Thus I'm not astound to find sanity checks
for end-points failing - end points are simply not supported by trytond
for trytond modules as one would expect in Python.
> Any chance that someone give a look before the merge? Otherwise,
> these broken packages could land to master; which would be sad.
trytond itself and tryton seem okay. So I suggest to remove the phase
sanity-check to all failing packages due to this check. Hopefully only a
few trytond- module are effected - those containing scripts.
I'll take care of this within the next few days.
--
Regards
Hartmut Goebel
| Hartmut Goebel |h.goebel@crazy-compilers.com |
|www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2021-12-02 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 16:44 [core-updates-frozen] Tryton broken zimoun
2021-12-02 8:57 ` Hartmut Goebel [this message]
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
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=4020db9a-833e-d1c2-4d9c-65b78460ef4a@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@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).