3 ms·
The bug was reported in February 2010 to the Debian bug tracker, where it was forever ignored, although the fix was trivial (replace the vol_id comment with blk
by Ologn 13y ago
The bug was reported in February 2010 to the Debian bug tracker, where it was forever ignored, although the fix was trivial (replace the vol_id comment with blkid). In May 2010 Ubuntu downstream is syncing with Debian ( https://launchpad.net/ubuntu/+source/partman-target/67ubuntu1 https://launchpad.net/ubuntu/+source/partman-target/67ubuntu... ), sees the bug report and fixes it in Ubuntu. Then in February 2011, a duplicate of the original bug is reported and gets fixed in Debian.
I was impressed by the fact that Ubuntu fixed this within three months even though the bug report was in the upstream ticket system, where it had not been fixed. Debian fixed it nine months after Ubuntu.
I appreciate the fact that Canonical has done things which help Ubuntu which sometimes, inadvertently or not, hurt Debian. For example, Canonical hiring so many Debian developers helped make the sarge release late. As I said in my post, Ubuntu is not that good about sending patches upstream. For a while, I was of the mind that Ubuntu was a mixed bag that in some ways helped and in some ways hurt the FLOSS community. Although over the past year or two, it seems the trend has been more toward the latter way.