From: Marius Bakke <mbakke@fastmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>,
guix-devel@gnu.org, Leo Famulari <leo@famulari.name>
Cc: 25177@debbugs.gnu.org
Subject: Re: python-tests: python-oslosphinx fixed. Please evaluate.
Date: Mon, 20 Feb 2017 00:00:21 +0100 [thread overview]
Message-ID: <87bmtxkcqi.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170218181854.49ea3b17@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
Danny Milosavljevic <dannym@scratchpost.org> writes:
> Hi,
>
> so we finally got to the bottom of the problem with python-oslosphinx.
> It should be fixed now (the main fix is in python-pbr-minimal).
Thanks a lot for this!
>
> @Leo: Can you please start a new evaluation of python-tests?
I pushed some other fixes recently and built most of `guix package -A
python`, so I think we're ready for a new evaluation. I suggest we do a
new evaluation on 'master' after fixing the most critical packages so we
can include this in 'core-updates'. How does that sound?
These packages are known to fail still:
python-dendropy
python2-fastlmm
python2-bandit
python-openid
python-axolotl
+ Many of the python2 variants of the openstack family libraries (oslo
etc), which seems to have a unittest2 version mismatch. Should be
easy to fix, but let's get some substitutes first :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-02-19 23:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 17:18 python-tests: python-oslosphinx fixed. Please evaluate Danny Milosavljevic
2017-02-19 23:00 ` Marius Bakke [this message]
2017-02-21 4:16 ` Leo Famulari
2017-02-21 7:50 ` Ricardo Wurmus
2017-02-21 17:30 ` Ricardo Wurmus
2017-02-21 17:47 ` bug#25177: " Leo Famulari
2017-02-21 22:15 ` Ricardo Wurmus
2017-02-22 12:42 ` Ricardo Wurmus
2017-02-22 12:57 ` Marius Bakke
2017-02-21 22:21 ` Ben Woodcroft
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=87bmtxkcqi.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=25177@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).