On 5/31/12 5:12 PM, Alexander Hansen wrote:
> On 5/31/12 4:30 PM, Lanny Ripple wrote:
>> What I mean is I was going to open a bug in sourceforge on the bug tracker
>> for fink and the content of the explanation is prefilled with a note that
>> says, "You can add a bug here but mostly we discuss these things on
>> [email protected]". If that's incorrect I'm more than happy
>> to re-open a bug report in the sourceforge system but in that case I would
>> ask that the note be taken out of the bug system so folks know where to
>> report things.
>>
>
> This is the place to do it.
>
>> Fink uses gnu's sed and as I understand it follows debian's packaging.
>
> Not necessarily. We just use their tools, and we don't necessarily care
> how they do their builds.
>
> The same version of sed (4.2.1) works on my ubuntu install so, in
> general, it's not an issue with the gnu code. That leaves the
> compilation of sed as specific to the 10.7 install. Since I notice fink
> doesn't just install pre-made packages but does a compile for each, fink
> seemed the natural place to report a bug that seems related to the
> compilation options.
>
> Sure, which is why I included our sed maintainer in the discussion.
>
>>
>> I did in fact start with the git team since I believe that a system's sed
>> should be the preferred one for a widely used software system and if there
>> are errors the application should address them, work around them, or choose
>> a new method to achieve it's goals. What I got from the git team was a lot
>> of, "You seem to be asking for a nail but there's no way we would give you
>> the kingdom." It was quite frustrating but from the conversation I was able
>> to resolve the issue and my development team can continue to make progress.
>>
>
>
>> In the end my stuff works and that's good enough for my purposes. I've
>> tried to be a good open-source citizen and report problems to the teams that
>> might have some stake in knowing about or resolving an unexpected bit of
>> behavior. Please let me know if I should go back to the sourceforge
>> bugtracker.
>>
>> Regards,
>> -ljr
>>
>> ---
>> Lanny Ripple
>> [email protected]
>>
>>
>
> What version of our git package is this, anyway? I don't have a git-am
> at all.
>
Ah, figured it out. (not a git expert).
Anyway, here's explicitly what is happening.
$ grep sed /sw/lib/git-core/git-am
rerere-autoupdate update the index with reused conflict resolution if
possible
sed -n -e '/^$/q' -e '/^[ ]/d' -e p |
# commands we invoke, based on the result of parsing command line
SIGNOFF=`git var GIT_COMMITTER_IDENT | sed -e '
commit=$(sed -e 's/^From \([0-9a-f]*\) .*/\1/' \
sed -e '1,/^$/d' >"$dotest/msg-clean"
sed -n '/^Subject/ s/Subject: //p'
"$dotest/info"
GIT_AUTHOR_NAME="$(sed -n '/^Author/ s/Author: //p'
"$dotest/info")"
GIT_AUTHOR_EMAIL="$(sed -n '/^Email/ s/Email: //p'
"$dotest/info")"
GIT_AUTHOR_DATE="$(sed -n '/^Date/ s/Date: //p' "$dotest/info")"
sed -ne '/^Signed-off-by: /p' \
sed -ne '$p'
# This is used only for interactive view option.
FIRSTLINE=$(sed 1q "$dotest/final-commit")
So there are a couple of options:
1) If we find out there's something in sed (or dependencies) that we
can fix, that will solve the problem.
2) If that's not the case, git can be set up always to use /usr/bin/sed.
--
Alexander Hansen, Ph.D.
Fink User Liaison
http://finkakh.wordpress.com/2012/02/21/got-job/
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Fink-users mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users
