Re: [cross-project-issues-dev] Mac signing service issues -- plan for M4
*sigh* The breakage coincided with system updates and a reboot.
How did you figure it out? I couldn't get codesign to return an
actual error (other than, "1").
I don't send the full process output to the client (to avoid disclosing sensitive information) but everything is added to a local log file (~/webservice/eclipse.org/signing/log/
Oh, and thank you for fixing this.
there is currently "no solution
in sight" for this week, I think the best course of
action is to push
ahead, and produce M4 as planned, with affected projects
Once we have
that build "in hand",
a) if the user experience is "really bad", we can
(but as far as know, if they are doing fresh install,
then they have to
do that "open" or "ctrl-open" trick we have used in
the past -- that is, in the past there has been
milestones without a Mac
signature. b) if enough people are around next week, to
with Mac signed, we can do an M4a deliverable.
But, in either
case, since we are between
a rock and a hard place, I think best to try and produce
one as planned.
Otherwise, we might be well into January before we could
produce one, depending
on everyone's holiday schedules.
signing service issues
The Mac signing service is currently broken. We're
tracking the issue in
cross-project-issues-dev mailing listcross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Description: Message signed with OpenPGP using GPGMail