media-gfx/splash-themes-livecd-2007.0 (I think the version before does also) uses /sbin/functions.sh, but baselayout-2 does not provide that any longer.
# epm -ql splash-themes-livecd|xargs grep functions.sh
I think it should use /etc/init.d/functions.sh instead, that seem to exist since a very long time, and still exists in baselayout-2.
Created attachment 118768 [details, diff]
Come on, just patching this can't be so hard.
*** Bug 188444 has been marked as a duplicate of this bug. ***
fixed it myself.
Please do not ever do that again without asking the maintainer.
(In reply to comment #5)
> Please do not ever do that again without asking the maintainer.
Nice to see the consistency in your opinions :P
Jakub: I have asked you repeatedly to leave your snarky comments to yourself. Now, I am done being cordial with you. Leave my bugs alone. This is no longer a request. Stay away from my bugs. Your "insight" isn't welcome and neither is your opinion.
wolf31o2: This is not in-place. You should have fixed this.
This bug was brought to my attention as a Developer Relations representative by an involved party, as such I advise that everyone discontinue this line of discussion. The bug is closed, there is no need for further comments technical or otherwise, further comments here may lead to disciplinary action.
musikc: As all CC and reporter are @gentoo.org, why don't we discuss why maintainer does not fix such minor issue? And why do you threat people who discuss valid issue? Jacub was right before and right now... But as it seems devrel always threat the people who work and protect the people who do nothing.
Alon: I'm sorry, but who asked you, anyway? I've been busy working on the Council and Trustees, as well as doing setup for LWE and such. Now, had zzam asked me to commit this, I would have said yes. He didn't. I simply stated for him not to do such a thing again. That was it. There was no issue between Matthias and I. Jakub had no place getting involved in any way, much as you have no place, especially when you're calling one of the distribution's top commiters someone who "does nothing"... seriously, get a clue.
alonbl, you misunderstand my intent and for that I apologize that I was not clearer. My intent was not to threaten people who wish to hold a valid and civil discussion. It was meant to caution people who may have considered "adding fuel to the fire."
Technical discussions and those asking for clarification would be appropriate. Taunting statements would not be appropriate. This is another case where the meaning is easily lost in the delivery of the message.
Anyone/everyone involved can be contacted via email and usually IRC for further discussion; lets take this off of this bug.
(In reply to comment #12)
> Technical discussions and those asking for clarification would be appropriate.
> Taunting statements would not be appropriate. This is another case where the
> meaning is easily lost in the delivery of the message.
Taunting? Oh, sure not. Sarcastic - definitely. If someone writes a huge discourse on reducing territoriality on gentoo-dev ML and then - couple of weeks later - goes and screams "do not ever do that again" about a trivial one-liner fix that could have been done months ago, that's what such person deserves. Anyone could have fixed this bug without Chris having any right to scream "do not do this again", his comment #5 is plain ridiculous.
How about "thanks for fixing this, zzam. I was busy" instead? What are your territorial pissings here about, Chris?
musikc: I am sorry for this one...
But you should also comment the following statement:
"Alon: I'm sorry, but who asked you, anyway?"
I am a user, and part of this community, these statements are these you should handle.
While Jacub statement at comment#6 was relevant and should have address in more polite way.
wolf31o2: I am a user just like any other, and users don't care how much work you do in the background. The public interface of Gentoo is bugzilla, timely response (or any) is very important, a lot more than most of Gentoo activities.
As comment#7-comment#0=0000-03-09, you had plenty of time to ACK this and suggest someone else may fix it. Nobody should beg for response.
Just like any community who wish to survive, we should think what are the expectation of our users/clients/customers/consumers, and prioritize our activity accordingly.
And the fact that you mentioned your high rank just make it even more important, as if people at the high floor are such, imagine how people in the lowers one are.
So everyone made clear what he thinks about the issue and we should all settle down. If you make a big issue out of a non-issue, that makes me feel sorry. Maybe even top-committers should control their temper a bit and wait until they submit a comment on a bug. If you two (Jakub and Chris) just need a reason to fight and pick every little thing, please meet in a boxing ring, but not on Bugzilla. Thanks.
Developer Relations has already asked all of you to take this off this bug. Please do so.