keeping track of packages breaking

15 March 2018, 19:41:27

Hi, i would like to suggest if we could make some sort of sticky thread for all packages that break or some sort of list that users can edit whenever a package is built with the wrong version of a .so file. I don't mind that happening from time to time, im actually enjoying this, kinda. That would be convenient so the maintainers can quickly see every broken dependency in a single place and the users can easily keep track. Idk if such a system already exists, but right now i see people just making a new thread on this forum whenever there is an issue about a broken package, which is not very centralized.

Most recent is seemingly an issue with libpsl, that is not up to date with important stuff like networkmanager.
I also had a problem with libpoppler recently, and libcdio a while ago.

Re: keeping track of packages breaking

Reply #1 – 15 March 2018, 19:51:11

I agree.
I was also thinking about creating some thread or page on wiki or something similar to this.
Because i also found few of these packages / error but as always i was able to fix critical errors in minutes and small in hours.
But you can bet on it that users will always create new threads for same thing / error.

As i think about it, the best solution seems to be new page on wiki, which anyone can update / edit as they wish (i will be watching over it)

Well to be honest recently a lot of packages in Artix stable and also in gremlins (testing) are from some staging / unstable repos which is making things more complicated.