guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: python-pytest in references graph


From: bokr
Subject: Re: python-pytest in references graph
Date: Mon, 25 Jul 2022 15:12:15 +0200
User-agent: Mutt/1.10.1 (2018-07-13)

On +2022-07-25 08:23:57 +0200, Lars-Dominik Braun wrote:
> Hi,
> 
> > It should, but sometimes there are bugs in the package definition or 
> > build system, in this case causing python-rdflib to refer to the 
> > native-input python-pytest.  Likely it's the 'add-install-to-path' phase 
> > adding too much, a known issue, which could be solved by separating 
> > inputs and native-inputs on the build side when compiling natively (and 
> > not only when cross-compiling) (currently they are merged together into 
> > 'inputs'), though non-trivial.
> the issue is indeed a known bug https://issues.guix.gnu.org/25235
> 
> Lars
> 
>
what's up^H^H down with that URL??
-----------cut here---------------start------------->8---
[15:03 ~/bs]$ ping -c 3 issues.guix.gnu.org
PING issues.guix.gnu.org (141.80.181.40) 56(84) bytes of data.
64 bytes from 141.80.181.40 (141.80.181.40): icmp_seq=1 ttl=46 time=88.7 ms
64 bytes from 141.80.181.40 (141.80.181.40): icmp_seq=2 ttl=46 time=81.10 ms
64 bytes from 141.80.181.40 (141.80.181.40): icmp_seq=3 ttl=46 time=81.7 ms

--- issues.guix.gnu.org ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2ms
rtt min/avg/max/mdev = 81.727/84.125/88.669/3.214 ms
[15:03 ~/bs]$ wl-paste 
https://issues.guix.gnu.org/25235
[15:04 ~/bs]$ wget https://issues.guix.gnu.org/25235 >> gxiss23235.txt
--2022-07-25 15:05:57--  https://issues.guix.gnu.org/25235
Resolving issues.guix.gnu.org (issues.guix.gnu.org)... 141.80.181.40
Connecting to issues.guix.gnu.org (issues.guix.gnu.org)|141.80.181.40|:443... 
connected.
HTTP request sent, awaiting response... 502 Bad Gateway
2022-07-25 15:05:57 ERROR 502: Bad Gateway.
-----------cut here---------------end--------------->8---

--
Regards,
Bengt Richter



reply via email to

[Prev in Thread] Current Thread [Next in Thread]