Well, some french temparement here. I'm from Sweden but I appreciate it! :) :) :)

:)

Look at that in less 3 days.

https://git.archlinux.org/svntogit/packages.git/log/trunk?h=packages/libffi

At least they could test their change, but no they do not ...

So now I'm blocked in my work

jean-michel wrote:)

Look at that in less 3 days.

https://git.archlinux.org/svntogit/packages.git/log/trunk?h=packages/libffi

At least they could test their change, but no they do not ...

So now I'm blocked in my work

When I told you about this over email 3-4 days ago you didn't seem to give a shit, now it is KURWAA.. Kurba... that's not french, that's slavic for "dick", am I right?


All you have to do is link /usr/lib/libffi.so.6 to .so.7 and everything works. This is what I use testing, I want to see things break before everyone else does.

This is a major one, anything gtk3 breaks without libffi.so.6 and obviously they must be running a bottle neck trying to rebuild everything in their repositories because of this. Even my terminal wouldn't start after the llvm and ffi updates. It happened in Void some days before arch-testing.

you didn't seem to give a shit

Think again, however I was not more surprised because that was in testing. Now it's totally different because they pushed their shit from testing to stable without even checking that everything works. It's not acceptable.

It's Polish :)

:)

Well. pactree -r libffi showed me that they were not going to rebuild EVERYthing before it goes to stable, it is arch in its latest fashion, and things would break.

To my taste this is better than xbps (void) not allowing any upgrades till you manually force- removed and installed llvm (versions) and new ffi, before upgrades were allowed to go further. Once upgrades did occur then everything worked. Void never had this in the past, upgrading took care of everything, now it needs some manually hacking to move on. But it is very rare for anything in void to ever break because of incompatible libraries. It is impossible by design. So this is why I think this is a major choice between the one and the other... I appreciate void's coherence but I prefer the freedom to hack a bit beyond what big brother prescribes. I hear rpm uses the same logic of having specific libversions in the building template.

Everything is broken. Kleopatra is broken too, Falkon is broken ...

It's unacceptable.

This is the straw that broke the camel. Arch will succeed to disgust me from Linux I have to make a decision.

Hey, if you don't like arch make your own distribution ....
I am banning you from the arch forum then :)

At every people reading this thread.

Arch become more and more unstable, taking bad policies decision and so on.

The Obarun team is ready to become independent from Arch. We can provide a good distro keeping the packager (pacman) but providing stable tools to build a pkg correctly and mostly do not breaking your system.
We can do it. We have the knowledge, we have the passion, we have the concept but we don't have the money

We provide already a very good alternative concerning the service management and a rock solid boot.

We can do more but we need your help guys. Working 12 hours each day on Obarun (this is the case for a long time now) without any money cannot continue for a long time.

We need financial supports.

Please guys, consider to become a patreon at https://patreon.com/obarun. More supports and more tools can be developed and more your system will be stable.
Working on Obarun and running behind the money to pay the bills is not possible.

fungalnet wroteHey, if you don't like arch make your own distribution ....

Done

I am banning you from the arch forum then :)

I'm banning you because you want to ban me :D


Anyway, despite appearances I'm worse than a pitbull on his bones.

HOT polish bitbull DOG

Onions and mustard please