Re: wget (was Re: i686 core-updates failure.)

--- Original Message --- On Sunday, April 16th, 2023 at 5:06 PM, Andreas Enge wrote: > > > Am Sat, Apr 15, 2023 at 06:25:52PM + schrieb Kaelyn: > > > I tried to update the package definition to be able to build from git but > > it became a much bigger rabbit hole than I have the

Re: wget (was Re: i686 core-updates failure.)

Am Sat, Apr 15, 2023 at 06:25:52PM + schrieb Kaelyn: > I tried to update the package definition to be able to build from git but it > became a much bigger rabbit hole than I have the energy for at the moment. As an explanation, this may be because the git checkout contains gnulib as a submodu

Re: python-pytest on core-updates (was: i686 core-updates failure.)

Am Sat, Apr 15, 2023 at 01:20:07PM +0200 schrieb Andreas Enge: > The recent master/staging merge apparently broke python-pytest even on > x86_64, see message below, which should be sorted out first. With pytest repaired, your patch builds numpy successfully on both x86 architectures. Pushed, thank

Re: wget (was Re: i686 core-updates failure.)

--- Original Message --- On Saturday, April 15th, 2023 at 4:37 PM, Kaelyn wrote: > > > Hi, > > --- Original Message --- > On Saturday, April 15th, 2023 at 10:43 AM, Andreas Enge andr...@enge.fr wrote: > > > Am Fri, Apr 14, 2023 at 08:51:18PM -0400 schrieb Maxim Cournoyer: >

Re: wget (was Re: i686 core-updates failure.)

Hi, --- Original Message --- On Saturday, April 15th, 2023 at 10:43 AM, Andreas Enge wrote: > > Am Fri, Apr 14, 2023 at 08:51:18PM -0400 schrieb Maxim Cournoyer: > > > None, but are there wget uptsream reports about the problem? > > > I do not see anything at > https://gitlab.com/gnu

Re: python-pytest on core-updates (was: i686 core-updates failure.)

Am Fri, Apr 14, 2023 at 08:05:46PM + schrieb Kaelyn: > I just sent in https://issues.guix.gnu.org/62843 to disable the two tests for > i686 and armhf (disabling TestKind.test_all for armhf might not be needed, > but the Gentoo package definition suggests the huge array test will fail for > a

Re: wget (was Re: i686 core-updates failure.)

Am Fri, Apr 14, 2023 at 08:51:18PM -0400 schrieb Maxim Cournoyer: > None, but are there wget uptsream reports about the problem? I do not see anything at https://gitlab.com/gnuwget/wget Andreas

Re: wget (was Re: i686 core-updates failure.)

Hi, Simon Tournier writes: > Hi, > > Fixing ’wget’ for i686 would help for Java and Julia. Well, currently > ’wget’ is broken on core-updates for i686, > > https://ci.guix.gnu.org/build/709528/details > > And the 5 error seem similar (missing file?), i.e., read, > > FAIL: Test-hsts > ==

Re: i686 core-updates failure.

--- Original Message --- On Friday, April 14th, 2023 at 8:28 AM, Andreas Enge wrote: > > > Am Thu, Apr 13, 2023 at 06:25:47PM +0200 schrieb Andreas Enge: > > > For the Fortran bindings, I am hesitant as well. I think it is bad style > > to disable a test just because it fails ;-) Mayb

Re: i686 core-updates failure.

Hi Andreas, > This also did not work - timeout after 3600 seconds of silence, > the property is overwritten by the guix daemon, I think. > Anyway, as said before, I rather think this is a real problem with > the tests (maybe depending on some special situation on berlin if you > could build it on

Re: i686 core-updates failure.

Am Fri, Apr 14, 2023 at 10:25:25AM +0200 schrieb Andreas Enge: > I have just started a manual build on berlin and will keep you updated. This also did not work - timeout after 3600 seconds of silence, the property is overwritten by the guix daemon, I think. Anyway, as said before, I rather think t

Re: i686 core-updates failure.

Hi everyone, > At some point we have to make choices > > Guix has never achieved usability as a desktop system on non-Intel > systems. > > I've come to believe that having Guix work well on non-Intel systems > is, > in practice, incompatible with the rate at which

Re: i686 core-updates failure.

Hi, On ven., 14 avril 2023 at 17:12, Csepp wrote: > That is a pretty terrible direction to take. There are still plenty of > people who rely on old hardware who can't afford to buy new machines. > When discussing these issues, it is important to keep in mind that the > people who have enough sp

Re: i686 core-updates failure.

Hi Lars, On ven., 14 avril 2023 at 12:49, Lars-Dominik Braun wrote: > last time I tried this I was told Cuirass does not respect this property, > so I’ll leave your patch untouched, hoping someone more knowledgable > will push it – if it works. Ah ok… I did not know. Hum, I thought it had been

Re: i686 core-updates failure.

Andreas Enge writes: > Am Thu, Apr 13, 2023 at 01:23:15PM + schrieb jgart: >> My thoughts on this are that unless someone has the time to maintain >> those broken packages we should just remove them and clean up shop a >> bit. >> Is there a reason to keep around the broken packages? > > Wel

Re: i686 core-updates failure.

Hi Simon, > Thanks for checking. It also builds for me locally. So I guess, > > +(properties > + ;; 3 hours to avoid time-out in the check phase. > + `((max-silent-time . 10800))) > > would be helpful. And it should be inherited by 9.2.5 so it should > also build on CI. WDYT? la

Re: i686 core-updates failure.

Hi Andreas, On Fri, 14 Apr 2023 at 10:25, Andreas Enge wrote: > But the last output was > => galois_raytrace(normal) 4154 of 7358 [0, 0, 0] > after about 2 hours of builds. So each test takes only a few seconds and > then outputs something. So my guess would rather be that one hour of silenc

Re: i686 core-updates failure.

Am Thu, Apr 13, 2023 at 06:25:47PM +0200 schrieb Andreas Enge: > For the Fortran bindings, I am hesitant as well. I think it is bad style > to disable a test just because it fails ;-) Maybe someone with experience > in numpy can speak up. Well, given how many packages on i686 eventually depend on

Re: i686 core-updates failure.

Am Thu, Apr 13, 2023 at 10:57:38PM +0200 schrieb Simon Tournier: > --8<---cut here---start->8--- > building of `/gnu/store/i6h8q8jgqxli3mkfyw7lpwzf7gq6mrxk-ghc-8.10.7.drv' > timed out after 3600 seconds of silence > @ build-failed /gnu/store/i6h8q8jgqxli3mkfyw7lp

Re: wget (was Re: i686 core-updates failure.)

On Thu, 13 Apr 2023 at 22:37, Andreas Enge wrote: > Except for one: Would it make sense to try to depend on wget2 instead? I have no idea. )-: Do you mean replace all the occurrences of 'wget' by 'wget2'? Maybe only the occurrences of 'wget' by 'wget2' for the current broken packages on i686?

Re: i686 core-updates failure.

Am Thu, Apr 13, 2023 at 10:15:14PM +0200 schrieb Simon Tournier: > Thanks for checking. It also builds for me locally. So I guess, > +(properties > + ;; 3 hours to avoid time-out in the check phase. > + `((max-silent-time . 10800))) > would be helpful. I may misunderstand something,

Re: i686 core-updates failure.

On Thu, 13 Apr 2023 at 22:45, Andreas Enge wrote: > Am Thu, Apr 13, 2023 at 10:15:14PM +0200 schrieb Simon Tournier: > > Thanks for checking. It also builds for me locally. So I guess, > > +(properties > > + ;; 3 hours to avoid time-out in the check phase. > > + `((max-silent-time .

Re: wget (was Re: i686 core-updates failure.)

Am Thu, Apr 13, 2023 at 10:33:28PM +0200 schrieb Simon Tournier: > Fixing ’wget’ for i686 would help for Java and Julia. Well, currently > ’wget’ is broken on core-updates for i686, > And the 5 error seem similar (missing file?), i.e., read, > Any idea? I had a look, but no idea :( Except for on

wget (was Re: i686 core-updates failure.)

Hi, Fixing ’wget’ for i686 would help for Java and Julia. Well, currently ’wget’ is broken on core-updates for i686, https://ci.guix.gnu.org/build/709528/details And the 5 error seem similar (missing file?), i.e., read, --8<---cut here---start->8--- FAIL

Re: i686 core-updates failure.

Hi Lars, On Thu, 13 Apr 2023 at 22:02, Lars-Dominik Braun wrote: > > About GHC, I am trying to build ghc-8.10.7 on core-updates for i686. It > > could be nice to fix it. Well, I will be happy if someone™ beats me. ;-) > > GHC 8.10.7 on i686 built fine for me locally with all timeouts > disable

Re: i686 core-updates failure.

Hi Simon, > About GHC, I am trying to build ghc-8.10.7 on core-updates for i686. It > could be nice to fix it. Well, I will be happy if someone™ beats me. ;-) GHC 8.10.7 on i686 built fine for me locally with all timeouts disabled. 9.2.5 is not done yet, but is slowly processing through the tes

Re: i686 core-updates failure.

Simon Tournier writes: > On Thu, 13 Apr 2023 at 17:47, Ricardo Wurmus wrote: > >> I know that I won’t continue contributing to Guix if packages are >> removed with nonchalance. We speak of removing Pandoc, Haskell, and >> most of R. That would be nothing short of reckless. > > …well, the cur

Re: i686 core-updates failure.

Hi Ricardo, all, I totally agree with your words. A minor comment about the merge of core-updates… On Thu, 13 Apr 2023 at 17:47, Ricardo Wurmus wrote: > I know that I won’t continue contributing to Guix if packages are > removed with nonchalance. We speak of removing Pandoc, Haskell, and > mo

Re: i686 core-updates failure.

On Thu, 13 Apr 2023 at 17:31, Simon Tournier wrote: > All in all, no, it is possible to drop python-numpy for example [2]. :-) No, it is *not* possible! (My fingers had not been enough fast. ;-))

Re: i686 core-updates failure.

Hello, Am Thu, Apr 13, 2023 at 04:37:55AM + schrieb Kaelyn: > I forgot to mention that I had also tried updating to the latest numpy > (2.24.2), with the same tests failing. I agree the test failures in numpy > need to be resolved in some way for merging core-updates, since the failure > af

Re: i686 core-updates failure.

On Thu, Apr 13, 2023 at 11:53 AM Ricardo Wurmus wrote: > > Yes, this is only i686 and it’s worth thinking about whether to continue > supporting this architecture when developers seemingly don’t care about > it any more. But just removing foundational packages is akin to just > giving up. We hav

Re: i686 core-updates failure.

"jgart" writes: > My thoughts on this are that unless someone has the time to maintain those > broken packages we should just remove them and clean up shop a bit. > > Is there a reason to keep around the broken packages? Definitely not! It’s been difficult enough to get them added in the fir

Re: i686 core-updates failure.

Hi jgart, On Thu, 13 Apr 2023 at 13:23, "jgart" wrote: > Is there a reason to keep around the broken packages? Euh, maybe you have missed what the branch core-updates is. :-) For packages with many dependents, it is not possible to update them directly in master, because of two main reasons: 1

Re: i686 core-updates failure.

Am Thu, Apr 13, 2023 at 01:23:15PM + schrieb jgart: > My thoughts on this are that unless someone has the time to maintain those > broken packages we should just remove them and clean up shop a bit. > Is there a reason to keep around the broken packages? Well, we can certainly remove a few ho

Re: i686 core-updates failure.

My thoughts on this are that unless someone has the time to maintain those broken packages we should just remove them and clean up shop a bit. Is there a reason to keep around the broken packages? A news entry about the removals would also be helpful if we decide to remove them in order for peo

Re: i686 core-updates failure.

Hi, CC: teams for each ecosystem. About i686 core-updates failures, well I do not know where to start :-) when giving a look at: https://ci.guix.gnu.org/eval/391720/dashboard?system=i686-linux 1. Java Well, it seems broken because wget-1.21.3 .

Re: i686 core-updates failure.

Hi, --- Original Message --- On Wednesday, April 12th, 2023 at 9:31 PM, Andreas Enge wrote: > > > Hello, > > Am Wed, Apr 12, 2023 at 04:11:58PM + schrieb Kaelyn: > > > For the actual failures in python-numpy[2]: > > > you could always try whether an update solves the test fail

Re: i686 core-updates failure.

Hello, Am Wed, Apr 12, 2023 at 04:11:58PM + schrieb Kaelyn: > For the actual failures in python-numpy[2]: you could always try whether an update solves the test failures; the package has 2892 dependents, but anyway, the only option is fixing it and rebuilding all the 2892 dependents also on x

Re: i686 core-updates failure.

Hi Kaelyn, Kaelyn writes: > I call the dependency chain odd in that pulseaudio--which is near the heart > of a lot of Linux software that supports audio--is failing because > inkscape--a graphical vector editor--is a dependency of a tool designed to > extract API documentation from source cod

i686 core-updates failure.

Hi, I've been working on getting wine to build on core-updates, with the most recent blocker being python-numpy failing two tests on i686 (one of which is apparently too big for 32-bit systems, based on the comment in the Gentoo ebuild of python-numpy where they skip the test). I just poked thr