Re: OCaml (was Re: Graphical login broken on core-updates)

Csepp writes: > I'm pretty sure I added uring for Mirage stuff, which no one uses yet > except me, so yeah, not blocking. > Although I'm not looking forward to fixing it on my next rebase. I'm using ocaml-uring via ocaml-eio. I'll have a look at the build issue. -pukkamustard

Re: OCaml (was Re: Graphical login broken on core-updates)

Hm, it seems to build: https://ci.guix.gnu.org/build/891468/details pukkamustard writes: > Csepp writes: > >> I'm pretty sure I added uring for Mirage stuff, which no one uses yet >> except me, so yeah, not blocking. >> Although I'm not looking forward to fixing it on my next rebase. > > I'm

Re: OCaml (was Re: Graphical login broken on core-updates)

Am Thu, Apr 13, 2023 at 07:33:49AM + schrieb pukkamustard: > I'm using ocaml-uring via ocaml-eio. I'll have a look at the build > issue. Hm, whatever happened, maybe Simon's patch also solved this problem, maybe it was a non-deterministic build failure, but I am getting ocaml-uring through the

Re: Time travel accident

Simon Tournier writes: > I have, > > --8<---cut here---start->8--- > $ guix gc --list-dead | grep 9gfmn1yra7rzavxb9wppqi4lpdvqid8c > finding garbage collector roots... > determining live/dead paths... > /gnu/store/9gfmn1yra7rzavxb9wppqi4lpdvqid8c-inferior-scrip

Powerpc on core-updates

Hello, recently I claimed that powerpc was repaired, but I must have made a mistake. It is still completely broken: https://ci.guix.gnu.org/eval/391720/dashboard?system=powerpc64le-linux due to this: https://issues.guix.gnu.org/61879 It does not look easy to fix, but might be *the* blocker

Re: A friendlier API for operating-system declarations

Hi Edouard, Edouard Klein skribis: > For my clients and my own use, I use a layer on top of operating-system > declarations in which I create functions that take an os as a first > argument, and return an os. > > With the help of the handy -> macro, I can chain them, thus allowing an > easy stac

Re: Powerpc on core-updates

I may as well try to provide a patch. It is untested even on x86_64, since it requires quite a few rebuilds. If it works on powerpc, it should probably be made conditional on the architecture to avoid a world rebuild. I do not know whether this is possible in the patches field in an origin. Andrea

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: rrdtool hash mismatch

On Thu, 13 Apr 2023 at 11:52, Simon Tournier wrote: > Well, Aleksandr, would you like to give a try for updating this change > in the Guix recipe? Ah, already done with . :-) Thanks! Cheers, simon

Re: OCaml (was Re: Graphical login broken on core-updates)

Hi, On Thu, 13 Apr 2023 at 08:05, pukkamustard wrote: > Hm, it seems to build: https://ci.guix.gnu.org/build/891468/details On Thu, 13 Apr 2023 at 10:09, Andreas Enge wrote: > Hm, whatever happened, maybe Simon's patch also solved this problem, > maybe it was a non-deterministic build failure

Re: staging merge into master

Hi Maxim, On Wed, 12 Apr 2023 at 23:27, Andreas Enge wrote: > Am Wed, Apr 12, 2023 at 11:18:26PM +0200 schrieb Josselin Poiret: >> I don't have a particularly strong opinion either way, but if you do >> merge it, could you make sure to also merge master into c-u and launch a >> CI evaluation rig

Re: rrdtool hash mismatch

Hi, Details about Josselin’s message. :-) On Wed, 12 Apr 2023 at 18:47, Aleksandr Vityazev wrote: > it outputs an error > sha256 hash mismatch for > /gnu/store/icyq4d3fsbbf2yw3dmg7cxgb05qzfd3q-rrdtool-1.7.2.tar.gz: > expected hash: 1nsqra0g2nja19akmf9x5y9hhgc35ml3w9dcdz2ayz7zgvmzmm6d1 > actual

Examples of transient shepherd services?

Hi, Are there any examples that demonstrate how a custom non make-inetd-constructor transient shepherd service can be made and destroyed? Regards, Bruno

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.

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: bug#61879: Powerpc on core-updates

Andreas Enge writes: > In the file >libstdc++-v3/src/c++17/floating_from_chars.cc > previous functions have code like this: > #if _GLIBCXX_USE_CXX11_ABI > buffer_resource mr; > pmr::string buf(&mr); > #else > string buf; > if (!reserve_string(buf)) > return make_result(first, 0,

Re: bug#61879: Powerpc on core-updates

Am Thu, Apr 13, 2023 at 02:46:00PM +0100 schrieb Christopher Baines: > Thanks for figuring this out Andreas! I've managed to apply this change > in the relevant place, and it appears to work. Good news, thanks! > + #$@(if (and (target-ppc64le?) > + (version>=? (packa

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.

"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.

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.

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, 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.

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.

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 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: herd stop hangs

Hi, Vladilen Kozin skribis: > $ sudo herd start my-service > starts without a hitch, but > > $ sudo stop my-service > simply hangs for the default 5sec until Shepherd SIGKILLs it (as per > /var/log/messages) and even after that console where I run the herd stop > command doesn't get released unt

Re: Examples of transient shepherd services?

Hi Bruno, Bruno Victal skribis: > Are there any examples that demonstrate how a custom non > make-inetd-constructor > transient shepherd service can be made and destroyed? There’s a toy example in ‘tests/transient.sh’, but that’s all. Inetd is the only real use case so far. Ludo’.

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: GOOPS-less Shepherd

Hi, Bodertz skribis: > I don't have strong feelings either way, and the change won't really > affect me too much, but what benefit is there in breaking things? From > what I understand from your message, users' configs will stop working in > a few months when 1.0.x releases (or with the macro w

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: GOOPS-less Shepherd

Hi, Liliana Marie Prikler skribis: > Am Donnerstag, dem 06.04.2023 um 22:16 +0200 schrieb Ludovic Courtès: >> What’s at stake, mostly, is the ability to reconfigure a long-running >> shepherd instance.  Once 1.0.x is in Guix, ‘guix system reconfigure’ >> will most likely fail to upgrade services

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

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: herd stop hangs

> (I guess the second command is ‘sudo herd stop my-service’.) If you > interrupt the ‘herd’ command, does ‘sudo herd status’ and similar > commands still respond? ‘sudo herd stop myservice’ exactly. Sorry about that. Herd continues to function. Appears that somehow SIGTERM has no effect or it

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: wget

Am Thu, Apr 13, 2023 at 10:43:31PM +0200 schrieb Simon Tournier: > 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? Yes, assuming that wget2 is the future and wget a thing of the past. But it

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: Contributing Guix Home services

Hi Tanguy! Tanguy LE CARROUR skribis: > This doesn't answer the question "how complete need a service be to make > it to master?", though. But I've a lot of re-write to do before submitting > patches > anyway! Sorry for not noticing earlier! There’s no formal rule, but I think that what we’ve