glycin: update to 2.0.7

[ndpm13]

Testing the changes

• I tested the changes in this PR: briefly

Local build testing

• I built this PR locally for my native architecture, (x86_64-glibc)

@chrysos349

[oreo639]

• I tested the changes in this PR: NO

Loupe needs to be updated.

[ndpm13]

• I tested the changes in this PR: NO

You should test PRs before submitting them. As-is this breaks loupe.

even when the PR is a draft?

[oreo639]

even when the PR is a draft?

Ideally, yes. It should be tested locally along with its dependents first.
Draft just means "don't merge" which can be the case for a variety of reasons.

[ndpm13]

even when the PR is a draft?

Ideally, yes. It should be tested locally along with its dependents first. Draft just means "don't merge" which can be the case for a variety of reasons.

Noted 👍

[ndpm13]

Also if the loupe thing is gonna be a problem should I just make this glycin-2 ?

[oreo639]

Also if the loupe thing is gonna be a problem should I just make this glycin-2 ?

No, in this case loupe should be updated in this PR.
Although, I assume glycin 2.x will also break fractal which should also be updated.

[ndpm13]

Also if the loupe thing is gonna be a problem should I just make this glycin-2 ?

No, in this case loupe should be updated in this PR. Although, I assume glycin 2.x will also break fractal which should also be updated.

is a version bump like this good enough?

[balejk]

Ad the fractal update: have a look at https://github.com/void-linux/void-packages/pull/56776/files, you could also include the unbreaking and the rebuild prevention.

[ndpm13]

Ad the fractal update: have a look at https://github.com/void-linux/void-packages/pull/56776/files, you could also include the unbreaking and the rebuild prevention.

doesn't seem to do the trick, I got 16 GB of RAM on my machine and I keep running out of memory

[balejk]

From my experience, you need at least some 24 GiB of RAM to compile it for the archs that I was able to do it for. I left the others marked as broken because I was not able to compile it for them with 32 GiB of RAM.

[ndpm13]

From my experience, you need at least some 24 GiB of RAM to compile it for the archs that I was able to do it for. I left the others marked as broken because I was not able to compile it for them with 32 GiB of RAM.

That's kinda messed up 💀
I think I'll just skip Fractal for now....

[classabbyamp]

in #58506 I got it down to 5GB required to build with -j1. takes a little more if you have higher -j