Originally posted by Setif
View Post
Announcement
Collapse
No announcement yet.
Arch Linux Now Provides Debug Packages, Debuginfod Integration
Collapse
X
-
Originally posted by Almindor View Post
Wow what a clusterfuck. I didn't know snowflakes took over Arch as well...
Comment
-
Originally posted by bug77 View Post
Tbh that page says 700+ packages, but by the time I checked it, the list was already down to 500 something. Many of them were clones, too (64 and 32 bit variants of the same package). Considering some of them are blocked by bugs, that list isn't that scary.
There was a bit of actual feedback here and there: the query is not really correct, it has many duplicates (apparently Firefox developer contributed about 100 packages itself to that count), and includes some testing packages. Some are not up-to-date for various reasons, including bugs.
I'm glad that bugs are not merged in. For a data point on stability and robustness, I migrated an Arch install from a broken USB stick yesterday. The USB stick suddenly became read-only in 2018. I had a few conflicts to manually solve, but otherwise the install upgraded cleanly from 2018 to 2022... That's a single datapoint, but I've had smaller updates fail on non-rolling distributions.
Now, with debug packages, and more importantly debuginfo integration, I'll be able to make useful debug reports for crashes I was not expecting, while keeping my system updated. Anybody knows how quickly new packages are added? Is manual intervention needed from the packagers? I currently use my non-stripped version of sway and wlroots, keeping in sync with arch packages would be better.
- Likes 2
Comment
-
Originally posted by M@yeulC View Post
Yes, if you want bleeding edge, try the testing repos. Reading that mailing list thread is just wasted time. People being rude to each other.
There was a bit of actual feedback here and there: the query is not really correct, it has many duplicates (apparently Firefox developer contributed about 100 packages itself to that count), and includes some testing packages. Some are not up-to-date for various reasons, including bugs.
I'm glad that bugs are not merged in. For a data point on stability and robustness, I migrated an Arch install from a broken USB stick yesterday. The USB stick suddenly became read-only in 2018. I had a few conflicts to manually solve, but otherwise the install upgraded cleanly from 2018 to 2022... That's a single datapoint, but I've had smaller updates fail on non-rolling distributions.
Now, with debug packages, and more importantly debuginfo integration, I'll be able to make useful debug reports for crashes I was not expecting, while keeping my system updated. Anybody knows how quickly new packages are added? Is manual intervention needed from the packagers? I currently use my non-stripped version of sway and wlroots, keeping in sync with arch packages would be better.
- Likes 2
Comment
-
Originally posted by bug77 View Post
Tbh that page says 700+ packages, but by the time I checked it, the list was already down to 500 something. Many of them were clones, too (64 and 32 bit variants of the same package). Considering some of them are blocked by bugs, that list isn't that scary.
Going over that "discussion" (discarding all the trans attention whoring), it seems there's a major problem with some maintainers and way forward for packages that are under their control. It would seem people have trouble submitting update diffs purely for bureaucratic reasons.
Comment
-
Originally posted by Almindor View Post
That's good but what about glibc then? Being behind by a year is somewhat laughable. The package in Arch is on 2.33 which was released over a year ago now and the last update on the package itself is from May 2021. It seems like it's been abandoned?
Going over that "discussion" (discarding all the trans attention whoring), it seems there's a major problem with some maintainers and way forward for packages that are under their control. It would seem people have trouble submitting update diffs purely for bureaucratic reasons.
All community maintened distros have issues from time to time. Be it political, technical or personal. Hopefully it is resolved soon, but I wouldn't cry doom over a singular thing like that.
One thing that could help is migrating to a git repo for the packages. That would more easily allow third party pull requests. I read somewhere that this is an ongoing effort.
- Likes 2
Comment
-
Originally posted by Vorpal View PostOne thing that could help is migrating to a git repo for the packages. That would more easily allow third party pull requests. I read somewhere that this is an ongoing effort.
- Likes 1
Comment
Comment