Ubuntu: not contributing to Debian, and even doing bad work
Par jd le mardi, octobre 2 2007, 20:34 - Debian - Lien permanent
Googling around using the rebuildd keyword to find if people were talking about it, I found that patch from Ubuntu.
This patch is used to ship rebuildd Debian package in Ubuntu.
Wahou. First surprise! So, Ubuntu is fixing bugs and not telling me. I though that people saying "Ubuntu does not contribute back to Debian!" were exaggerating. Seems I was wrong.
Nevermind: I take the patch. I read the patch. I apply the pat… oh wait: the fix is wrong.
lol.
Commentaires
If you still want to fix the bug, I recommend /usr/bin/printf for this sort of thing.
Already commited with printf, yes.
All things considered, considering that I haven't the patience of saints, I probably wouldn't make much of an effort to submit my patches to sociopathic dicks (that's debian-fr, by the way) if I could, either. Unsurprisingly, this is self-perpetuating, which is why it's 500% more likely that a random debian-fr user is going to troll Planet Debian about uncooperative upstreams/downstreams comparing to normal DDs.
Apologies to the few French DDs tarred with this brush who don't spend most of their free time making other free software developers less inclined to cooperate with debian. But then, I imagine they stopped reading this blog a while ago.
- Chris
I filed & fixed the Ubuntu bug (the fix is correct in Ubuntu, but /usr/bin/printf is indeed more correct, thanks).
I can't remember exactly why I didn't file a Debian bug as well, but it was probably because: (1) I didn't have a Debian system at the time to test it on, and (2) It shouldn't have adversely affected the Debian package at all, since you use bash for /bin/sh.
We assume that /bin/sh can be dash as well.
If the fix is correct in Ubuntu, you assume that /bin/sh will never be bash?
It can be frustrating to send patches upstream and be shot down, but I don't think that Ubuntu developers should allow the letdowns to discourage them, even if they comprise the majority of interactions with Debian.
In this particular case, the developer seems to have decided Debian upstream wasn't interested in fixing bash-isms. I'm glad to hear you are. Indeed, I wish there was a better way to handle. Partly I think the direct antagonism directed at Ubuntu makes people care less about working with Debian, resulting in less than optimal systems like patches.ubuntu.com with little or no documentation. I realize that the amateur efforts that sometimes represent Ubuntu Universe are less than perfect. Still, I like Ubuntu and Debian, and I hope the future finds some better policies, algorithms and communications to make this work with less friction on both sides. A posting on a blog indexed by Planet Debian should not be the best avenue to pursue such things, but it seems for the moment it is =(
FWIW the proper fix is not to use printf at all but use:
python -c "statement1; statement2; statement3"
@Chris: I thought Ubuntu had a CoC ? or does it apply only in teletubyland (_that_ would be a quite convenient CoC then) ?
All our buildds have /bin/sh -> dash, this is our default sh, and I (mistakenly) thought that \n -> newline in echo was POSIX (it's implementation defined, apparently). Stupid man sh, stupid me!
Your fix is really a fix, being actually portable. The Ubuntu bug has been re-opened.
Ubuntu no contribuye a Debian y encima hace el trabajo mal
Trackback:
http://bytecoders.homelinux.com/con...