Post #2919547
2026-04-23 16:35 UTC
@fossham@mastodon.radio If I get hit by a bus and all of my infrastructure stops, users are running Debian and they won’t be impacted by a lack of me.
I get where you’re coming from and your concerns, but simply I’ve been working on this for a specific community in the UK who are using & enjoying it and thought it would be nice to share my project wider.
I’ve enjoyed the learning and I’m proud of it so far, and what you’ve done is come across as telling me I’ve had a shitty idea & it’s a waste of everyone’s time because I should be contributing to Debian instead without reading about my/its background and the work I already do.
I don’t have a cybersecurity plan for linbpq, bpq’s qtsoundmodem or qt term TCP should a user choose to install them and I’m not sure John who writes those applications does either. The rest is usually covered by the standard DSAs. If not, we’ve failed in Debian and the normal disclosure applies.
If my project doesn’t match your threat model, I can only advise you to not run some guy’s iso in production. There are other ways you can get these exact same packages. Maybe just try it in the shack on occasion to see what packages there are!
Replies (1)
-
@fossham@mastodon.radio 2026-04-23 17:00
@red@woof.tech One thing that would make that process easier would be if you were to provide a list of which packages comprise the 95% that is available in Debian already, and which 5% are unique to your fork. Debian kindly provides such lists on https://www.debian.org/blends/ , so we can check which versions are available, which are lagging behind, and see what's missing. I would have enjoyed seeing something like its "hamradio" and "metapackages" links on your website.