4 ms·
- FLAVOR: Ubuntu Desktop, Ubuntu Server, Ubuntu Core - HEADLINE: Build from source, minimize deltas from upstream, and quit poisoning the Debian ecosystem. -
by hedora 10y ago
- FLAVOR: Ubuntu Desktop, Ubuntu Server, Ubuntu Core
- HEADLINE: Build from source, minimize deltas from upstream, and quit poisoning the Debian ecosystem.
- DESCRIPTION: I have repeatedly hit issues with core packages and applications that are solved by simply doing:
apt-get build-dep; apt-get source package; cd package* ; fakeroot debian/rules
Sometimes the packages fail to build. This tells me that you do not have an automated build regression system, even though Debian has gone to great pains to make this easy to automate.
I have hit bugs in packages because there is a large stack of diffs that have been applied to the package (logrotate is one example), but never upstreamed. The logrotate diffs include a "security patch" that is not well thought out, does not actually close a real bug, and causes logrotate to silently fail, filling /var.
This would not happen if you actively upstreamed patches, and reverted changes that are not approved by upstream, or addressed in other ways by upstream developers.
These two systematic issues have caused me to move away from Ubuntu for server and desktop use.
Finally, I've heard stories about Ubuntu devs forcing through controversial votes in the Debian project, and noticed an uptick in user-hostile decisions by the Debian project (like the forced systemd migration).
As a major contributor to Debian, Ubuntu should do whatever it can to improve the health of the Debian community, and generally improve the code quality + stability of upstream debian projects (without just killing off stuff that Ubuntu has decided not to ship).
- ROLE/AFFILIATION: Engineer/Researcher At work, we ship a hardware appliance based on Ubuntu. I've been using Ubuntu / Debian as my primary development environment for almost two decades, and am saddened by the level of bitrot I've encountered over the last 2-3 years.