News for hackers. Stuff that matters.
Re:Debian must ship reproducible packages by iamnothere on Sunday May 10, 2026 @09:23AM (#48083781)
A warning is sufficient. Old tech should continue to work, for preservation and archival reasons.
Re:Debian must ship reproducible packages by PunchyHamster on Sunday May 10, 2026 @01:37PM (#48086027)
just archiving binary artifacts and source packages is enough

Reproducibility adds nothing here

Re:Debian must ship reproducible packages by MomsAVoxell on Monday May 11, 2026 @02:13AM (#48091568)
It sure does: no need to keep the binaries around if they are reproducible.
Re:Debian must ship reproducible packages by tardedmeme on Sunday May 10, 2026 @06:10PM (#48088662)
I've long ago realized that archival needs to be a separate task left to archivists and archive systems. If you take it into account when designing a live system it's liable to seriously compromise your system design.

Say you're making a chat app - you wouldn't incorporate a delete feature, and you might be tempted to use some kind of blockchain to prove all messages were delivered without gaps. But if you ignore archival needs you design something similar to IRC which is much simpler.

Re:Debian must ship reproducible packages by iamnothere on Monday May 11, 2026 @09:59AM (#48095122)
That depends on your user base. If your group of target users includes professional, corporate, or governmental use, then you absolutely need to build in signing and archival for legal reasons. If your users include people who may only connect occasionally or with flaky connections, then you need a robust way to ensure that messages are held for delivery and that all messages are delivered in order. Basic chat (without delivery guarantees or archival) is already solved by IRC, long ago.