Arch Linux User Repository

what about make -j1 ? so not in parallel compilation.

Unfortunately, it reliably crashes the process (out of memory). The PKGBUILD also does not respect setting MAKEFLAGs. I did change the make -j [...] calls to make -j2 [...] which looked good at first, but unfortunately ended in errors not finding zen::formatError (or something similar) :(

the update on my 16gb laptop almost hangs the systems. lots of cc1plus running at 100% cpu.

another system with 8GB i use can't even compile it and kde kills the konsole app for causing OOM.

maybe this removal caused it? - MAKEFLAGS="-jnproc"

@tee

First of all thanks for maintaining the package. Afair it was broken for a considerable time in the past - used the -bin myself then - so the -bin just became more popular and it takes some time for people to show up here?

Also people with 32 GB RAM or maybe 16 GB plus decent swap may not even notice, but eventually someone from the 8 GB crowd will be hit and show up. :shrug:

But I'm happy you take the time to resolve it. :+1:

@tee "Note there were no concerns upon update 1 Week Ago, only now."

I can't say anything about that, I have currently installed the 14.3-1 and wanted to do my weekly system updates yesterday. I guess a lot of people will do like that or similar. Have you ever tried to update on a system, e.g. virtual machine with 4 or 8 GB RAM?

@tee "Oops Wrong @Its @schlaefer not @Jthundley"

Ah, it would make more sense. But is not true either. But schlaefer and I have actually already talked about the problem in another forum. You can see the thread in the EndavourOS Forum, which ultimately led to the reports of Schlaefer and me: https://forum.endeavouros.com/t/freefilesync-aur-update-bringen-bringen-zum-uberlaufen/7401010101

I am there "kde1". There I describe my problem with the update try from Freefilesync.

Schlaefer points to me there: "Problem in the last PKGBuild change, it is best to report on the AUR side."

I (kde1) answer: "Hey, great, I just saw, you have already reported there !: +1: I was just thinking about how I best write it ... (Apart from the fact that I am not yet registered there. But would of course have been a good opportunity, sooner or later it will be something like that ...) "

The next morning I registered here, since you @tee have posted in the meantime, "if there's a second object that I'll revert".

I wrote that again in the EndavourOS forum, that I have now registered there to leave a comment.

But then the whole thread in the EndeavourOS forum was probably just self-talk, my second registration there as kde1 was just so that I could register here now to take down my previous first post! ;)

oops wrong @ its @Schlaefer not @Jthundley

@tee "... may as well be a sock puppet of @JThundley."

Ha ha, funny! No, I'm not. Why so paranoid? And why JThundley of all people?! (Don't take it personally @JThundley!) He recommends the freefilesync-bin to users who "don't want" to compile. So, according to JThundley's definition, I "don't want" to compile because I don't have 64 GB of RAM?!

JThundley's comment doesn't fit the intention of my comment at all.

I only registered here, because I use Freefilesync on several systems and can no longer update. Now I would have to switch to the "outdated" freefilesync-bin on all systems, or possibly even the Flatpak version (but I'd actually like to keep my systems as free of Flatpak as possible).

I just wanted to show, that there's someone else having problems with version 14.4-1, and I registered here specifically for that reason. Because only those who speak up can be heard. I just wanted to join in, sorry!

Of course, comments like these don't exactly encourage others to come forward and possibly share their problems, if you immediately assume they might be someone else's clone...

(translated with the help of google-translation!)

@kdeler just joined today, may as well be a sock puppet of @Schlaefer.

Note there were no concerns upon update 1 week ago, only now.

In any case I'll revert for the next release to avoid a mass rebuild.

The same problem as kdeler. Not in a VM, but 8 GB RAM and Swap. kswapd0 is running nearly at 100% sometimes. Any other process max. 9%.

@tee "... But if there's a second objection then I'll revert."

I use several virtual machines, all of which only have 4 GB of RAM. So far, installing and updating freefilesync has been no problem. My host computer has 16 GB, after all. I also have a laptop with 8 GB of RAM. On all systems, the RAM fills up within a very short time when I try to update to 14.4-1, and nothing works anymore.

It would be a real shame, if that were the way things were intended from now on.

Okay, yes, there's also the freefilesync-bin, which I could possibly use as a fallback. However, it's currently (already) marked as outdated.