3 ms·

Given my bad experience during the past years of Ubuntu breaking things in Debian and inventing poor software by themselves, my estimation is that they're not s

Given my bad experience during the past years of Ubuntu breaking things in Debian and inventing poor software by themselves, my estimation is that they're not smart enough to pull this off.

hollerith 14y ago
am curious how Ubuntu broke things in Debian. were Debian maintainers too ready to accept changes from Ubuntu?
- AnthonBerg 14y ago
  Ah! Oops! I meant break things FROM debian, as in got code from Debian and broke it in Ubuntu, or didn't pull fixes from Debian into Ubuntu for years. My apologies! I'm not a native English speaker :( and sometimes I think I am smarter than I am :)
  - TheCowboy 14y ago
    What did they break?
    - AnthonBerg 14y ago
      mdadm and associated init scripts was the dealbreaker for me they broke the initscripts so array assembly didn't work correctly - not even the same as the installed man page stated they had mdadm version 2.x (has significant flaws) for YEARS after mdadm 3.x was accepted into debian - YEARS - even after multiple users making clear what the problem was in bug reports a user even made a patch and a ppa which fixed things but still they didn't pick up on that for a year + as i recall and they broke/removed debian's PERFECT support for installation onto md raid other stuff i've honestly forgotten but i swear there was more oh! oh! wait, also the STOPPING THE BOOT PROCESS TO WAIT FOR YOU TO PRESS A KEY if a drive needed an fsck!!!!! what the f.... (don't understand why you were downvoted, good question)
      - deleted 14y ago
        [deleted]
Ologn 14y ago
I agree they do not have the personnel to put out a major software component like this themselves. Just go to Launchpad and read the bug reports for their forks. Here is a typical nux bug report: https://bugs.launchpad.net/nux/+bug/846444 https://bugs.launchpad.net/nux/+bug/846444 So Canonical decides to go off the beaten path and create nux. Dozens of Ubuntu users indicate a problem. Indicating at least hundreds of people probably see this problem? Resolution? Nothing for 10 months. Then "Gee, our nux developers have been at work on a cool new version instead of fixing bugs, why not upgrade to that and try it out". With Ubuntu upstream libraries from Gnome, freedesktop.org, Debian etc., you have a confluence of people from different distros who can work on bugs that come up. With these Canonical forks, realistically only Canonical employees are going to fix 95% of their forks. But they're too busy working on the next cool thing to fix bugs. My Ubuntu 12.04 LTS desktop currently has hundreds of zombie lightdm processes running on it. I reboot but they come up again. This is not specifically a Canonical fork problem, but is an annoying bug and I and many Ubuntu users have come across many of these bugs. I can imagine what Ubuntu will look like as it forks more and more functionality, and less and less help for bugs can gain help from Gnome and fd.o.

Given my bad experience during the past years of Ubuntu breaking things in Debian and inventing poor software by themselves, my estimation is that they're not smart enough to pull this off.

hollerith 14y ago

am curious how Ubuntu broke things in Debian. were Debian maintainers too ready to accept changes from Ubuntu?

AnthonBerg 14y ago
Ah! Oops! I meant break things FROM debian, as in got code from Debian and broke it in Ubuntu, or didn't pull fixes from Debian into Ubuntu for years. My apologies! I'm not a native English speaker :( and sometimes I think I am smarter than I am :)
- TheCowboy 14y ago
  What did they break?
  - AnthonBerg 14y ago
    mdadm and associated init scripts was the dealbreaker for me they broke the initscripts so array assembly didn't work correctly - not even the same as the installed man page stated they had mdadm version 2.x (has significant flaws) for YEARS after mdadm 3.x was accepted into debian - YEARS - even after multiple users making clear what the problem was in bug reports a user even made a patch and a ppa which fixed things but still they didn't pick up on that for a year + as i recall and they broke/removed debian's PERFECT support for installation onto md raid other stuff i've honestly forgotten but i swear there was more oh! oh! wait, also the STOPPING THE BOOT PROCESS TO WAIT FOR YOU TO PRESS A KEY if a drive needed an fsck!!!!! what the f.... (don't understand why you were downvoted, good question)
    - deleted 14y ago
      [deleted]

Ologn 14y ago

I agree they do not have the personnel to put out a major software component like this themselves. Just go to Launchpad and read the bug reports for their forks. Here is a typical nux bug report: https://bugs.launchpad.net/nux/+bug/846444 https://bugs.launchpad.net/nux/+bug/846444 So Canonical decides to go off the beaten path and create nux. Dozens of Ubuntu users indicate a problem. Indicating at least hundreds of people probably see this problem? Resolution? Nothing for 10 months. Then "Gee, our nux developers have been at work on a cool new version instead of fixing bugs, why not upgrade to that and try it out". With Ubuntu upstream libraries from Gnome, freedesktop.org, Debian etc., you have a confluence of people from different distros who can work on bugs that come up. With these Canonical forks, realistically only Canonical employees are going to fix 95% of their forks. But they're too busy working on the next cool thing to fix bugs. My Ubuntu 12.04 LTS desktop currently has hundreds of zombie lightdm processes running on it. I reboot but they come up again. This is not specifically a Canonical fork problem, but is an annoying bug and I and many Ubuntu users have come across many of these bugs. I can imagine what Ubuntu will look like as it forks more and more functionality, and less and less help for bugs can gain help from Gnome and fd.o.