3 ms·
> Alarmed at the prospect of being unable to trust all 24,000-plus Debian packages, most of which are built on package maintainers’ laptops, the Debian Project
by koolba 10y ago
> Alarmed at the prospect of being unable to trust all 24,000-plus Debian packages, most of which are built on package maintainers’ laptops, the Debian Project has pushed hard over the last three years to make as many packages reproducibly buildable as possible. As of this writing, 91 percent have achieved that goal, and the project hopes to hit 100 percent in 2017.
91% already? That's pretty impressive! I remember when they first started discussing this but haven't tracked the progress at all. Happy to see how far long it's come.
- mikepurvis 10y ago> most of which are built on package maintainers’ laptops Gracious, is that really true? My experience of interacting with Debian/Ubuntu is via launchpad.net, where you push the dsc (source tarball + patches + metadata), and the server takes care of producing binary archives for the supported architectures.
- BuuQu9hu 10y agoFor the most popular architecture amongst developers (amd64 right now, i386 earlier), that was true until the last couple of years where Debian supports source-only uploads.
- rlpb 10y agoUbuntu does source-only uploads. Binaries cannot be uploaded by anyone; everything is built on Launchpad's infrastructure (managed by Canonical). Debian traditionally has done source-and-binary uploads for the maintainer's architecture (usually amd64), and builds for other architectures via the its buildd infrastructure (managed by contributors, AIUI). More recently it is possible to do source-only uploads to Debian now, but I'm told it doesn't work for new packages.