HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
void-linux
void-packages
Shell2018–2026
void-linux / void-packages

void-packages

The Void source packages collection

Systems & Infrastructure
Explore on GitHubRead Hacker News discussions
22Distinct people
26Mentions
0Explicit recommenders
3.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The Void source packages collection

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year26 dated mentions

Observed mentions: 2018-12-30 06:33:53 UTC to 2026-07-01 11:15:31 UTC.

02462018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC303
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC505
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC606
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC312
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC303
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC202

What Hacker News says

26 sources
fao_·May 31, 2026
I think people are very justifiably angry that a very stable, well trusted tool, has started to immediately go downhill. The Linux Mint Timeshift tool has an issue open documenting a number of regressions that are currently open on the rsync issues page, that were only introduced post-vibecoding (https://github.com/linuxmint/timeshift/issues/548), one of those links goes to a larger aggregate of bugs reported downstream (https://github.com/void-linux/void-packages/issues/60825). I think it is incredibly rational and sane, given the reputation of vibecoded software as-such (where every professional who loves it is saying "you have to hold it in this very specific way so it doesn't cause bugs, and also you should probably only use it for version 0s so you can map out the domain"), for people to be angry that their load-bearing industry stan
Read the rest
dard backup tool that is very, very well respected is suddenly pulling the rug out from under them because the maintainer wants to "add more features" and is doing it in what is clearly an unsafe way. Also from the timeshift thread: > not sure if this is just me, but after updating rsync, my cpu usage got so bad during my daily backups that i had to stop timeshift from running forever Or, phrased differently - People are frustrated and annoyed that the tool they trusted with their backups and data are seeing a huge number of regressions and new bugs that break their entire backup infrastructure, all because the main dev is vibecoding that software. Vibecoding experts like Simon Wilson explicitly state that vibecoding is 'viable' in the sense of "only if you hold the tool in a specific way", and this person is either not doing that, or that statement is untruthful. If you actually read the thread in question and just skim over the argument two people are having, there are multiple reports from users in industrial and government settings that now have to go through whole processes to update this software, simply because the software has become immediately untrustworthy in a way that directly harms users and defeats the entire point of the software in question. I think I would also be mad if I relied on this software for my 500gb+ backups, and I wonder how many more issues have been introduced that we simply won't learn about until a company has a $10 million dollar data loss because they were not testing their backups consistently.
In Please Do Not Vibe Fuck Up This Software
homebrewer·Jul 19, 2025
Just a reminder that it doesn't have to be this way, and the Debian problem is mostly self-inflicted and caused by decades of backwards compatibility. You don't have to suffer it if you control what's running on your machines. Let's see how btop (mentioned in the article) is packaged by other distributions. Alpine: one very transparent and easy to understand shell script with about 20 LOC: https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/c... Arch: same thing (there are a couple more files there, one of them is for an optional new version checker, the other is automatically generated): https://gitlab.archlinux.org/archlinux/packaging/packages/bt... Void Linux: unlike the previous two, this uses a declarative language; it's still very short and easy to understand (though I prefer the imperative approach): https://github.com/void-
Read the rest
linux/void-packages/blob/master/srcp... Chimera Linux: same as Void: https://github.com/chimera-linux/cports/blob/master/user/bto... I often write Alpine & Arch packages, and it's honestly a joy. For most programs it takes just a few minutes, how the result works is obvious to anybody even moderately familiar with Linux.
In Debcraft – Easiest way to modify and build Debian packages
onli·Apr 24, 2025
I'm using void. https://github.com/void-linux/void-packages/issues/26415 gives an insight, though it doesn't explain the whole problem, if I remember correctly what maintainers wrote elsewhere. > ROCm is a train wreck to compile from source but can be done with sufficient bloodymindedness. Yeah, I did that myself. Not impossible, just a bit annoying and time consuming. The issue I ran into then was exactly picking the gpu model (incredible that this is even necessary) and not having the gfx1032 available, see https://github.com/void-linux/void-packages/issues/26415#iss... for what I was following back then. I tried to edit the configuration for the gfx1032 anyway, but it did not succeed. Side note: Already having to know which card corresponds to which code is annoying, and completely unnecessary. They could also just map the consumer fac
Read the rest
ing name. But that would be too easy I assume.
In AMD Publishes Open-Source Driver for GPU Virtualization, Radeon "In the Roadmap"
anonbanker·May 12, 2024
Every day, Ted Unangst is vindicated more and more[1] for his work forking OpenSSL. If you do a little digging, you'll see that there was no real technical reason why your distro of choice has abandoned implementing LibreSSL[2][3], or just never implemented it at all[4]. They just somehow wanted to keep using the faulty software with exploit mitigation countermeasures[5][6]. Totally organic. 1. https://flak.tedunangst.com/post/analysis-of-openssl-freelis... 2. https://wiki.gentoo.org/wiki/LibreSSL 3. https://github.com/void-linux/void-packages/issues/20935 4. https://lwn.net/Articles/841664/ 5. https://marc.info/?l=openbsd-misc&m=139698531410614&w=2 6. https://marc.info/?l=openbsd-misc&m=139698608410938&w=2
In 16 years of CVE-2008-0166 – Debian OpenSSL Bug
arp242·Nov 3, 2023
Classic "everyone is using the software wrong, but it's the fault of everyone, and not the software". Some distros like Void seem to patch this out.[1] From mandoc/mdocml's mandoc_char(7) [2] In roff(7) documents, the minus sign is normally written as ‘\-’. In manual pages, some style guides recommend to also use ‘\-’ if an ASCII 0x2d “hyphen-minus” output glyph that can be copied and pasted is desired in output modes supporting it, for example in -T utf8 and -T html. But currently, no practically relevant manual page formatter requires that subtlety, so in manual pages, it is sufficient to write plain ‘-’ to represent hyphen, minus, and hyphen-minus. Which is the common-sense thing to do. Meanwhile, GNU projects become increasingly less relevant due to obnoxiousness like this. In general the amount of wankery of "the correct hyphen" is s
Read the rest
taggering. [1]: https://man.openbsd.org/mandoc_char [2]: https://github.com/void-linux/void-packages/blob/20c66829134...
In Hyphens, minus, and dashes in Debian man pages
bitofhope·Oct 13, 2022
>I'm definitely not in favor of fossilizing Unix, but there's a difference between avoiding fossilization and the kind of minimal, mathematical purity that we see GNU Grep trying to impose here. I can't really see the difference. Adding a deprecation warning to stderr in a non-POSIX command 15 years after deprecation notice is among the smallest possible changes to [GNU's Not] Unix I can think of. Even then, the change is trivially silenced by deleting a single line in a shell script or two[1] and seems that some distros already do that for you[2]. Yes, this will break something for someone[3] and I might well be that someone. You truly have my sympathies. But if you want to run a system for a decade and a half without ever needing changes, stick to POSIX. You can't have your fossils and eat them too. [1] https://git.savannah.gnu.org/cgit
Read the rest
/grep.git/commit/src/egrep.... [2] https://github.com/void-linux/void-packages/pull/39340 [3] https://xkcd.com/1172/
In We are stuck with egrep and fgrep (unless you like beating people)
phillipseamore·Apr 23, 2021
They might be returning different results depending on the user-agent because: curl "https://github.com/void-linux/void-packages" | grep -i download | grep -i zip Gives a regular <a> with the href correctly set to the zip archive: <a class="..." rel="nofollow" data-hydro-click="..." data-hydro-click-hmac="..." data-ga-click="..." data-open-app="link" href="/void-linux/void-packages/archive/refs/heads/master.zip">
In [dead]

Showing the 15 most recent of 26 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.