Mark J. Nelson wrote:
> Elaine Ashton wrote:
>>
>> On Apr 16, 2009, at 3:32 PM, Rafael Vanoni wrote:
>>>
>>> I believe it would be okay with us (the powertop team) to simply
>>> re-create the repository, if the problem is root caused and you feel
>>> there's no need to chase this issue down. We'r
On Apr 16, 2009, at 3:32 PM, Rafael Vanoni wrote:
>
> I believe it would be okay with us (the powertop team) to simply re-
> create the repository, if the problem is root caused and you feel
> there's no need to chase this issue down. We're currently in sync
> with ON.
I don't have a problem
On Apr 16, 2009, at 3:08 PM, Mark J. Nelson wrote:
>
> Different Eric. Eric Saxe. Sorry, I was assuming he was involved,
> as the merge changeset that tripped over this problem was his. I
> meant "whoever tried to clone this project repository."
Ah, right.
> If the zfs snapshot is just th
On Apr 16, 2009, at 2:49 PM, Mark J. Nelson wrote:
> Rich and I have been discussing this.
>
> Looks like Mercurial issue 612: http://www.selenic.com/mercurial/bts/issue612
>
> ...which was fixed in Hg 0.9.5.
>
> We're not sure why it's only now showing up. When was the last
> Mercurial upgrad
Elaine Ashton wrote:
>
> On Apr 16, 2009, at 3:32 PM, Rafael Vanoni wrote:
>>
>> I believe it would be okay with us (the powertop team) to simply
>> re-create the repository, if the problem is root caused and you feel
>> there's no need to chase this issue down. We're currently in sync with
>>
>> If the zfs snapshot is just the repo in question, that's fine,
>> otherwise a tarball would be great. The 30-day rollback would be
>> insufficient, as the problem was actually introduced when merging the
>> project gate to onnv_82.
> If it's is only the powertop repo in question, then we'l
Elaine Ashton wrote:
>
> On Apr 16, 2009, at 2:49 PM, Mark J. Nelson wrote:
>
>> Rich and I have been discussing this.
>>
>> Looks like Mercurial issue 612:
>> http://www.selenic.com/mercurial/bts/issue612
>>
>> ...which was fixed in Hg 0.9.5.
>>
>> We're not sure why it's only now showing up.
Rich and I have been discussing this.
Looks like Mercurial issue 612:
http://www.selenic.com/mercurial/bts/issue612
...which was fixed in Hg 0.9.5.
We're not sure why it's only now showing up. When was the last
Mercurial upgrade on the app servers, and from what version to what version?
When
Mark J. Nelson wrote:
>
>>> If the zfs snapshot is just the repo in question, that's fine,
>>> otherwise a tarball would be great. The 30-day rollback would be
>>> insufficient, as the problem was actually introduced when merging the
>>> project gate to onnv_82.
>
>> If it's is only the power
Mike Kupfer wrote:
>> usr/src/lib/fm/topo/maps/SUNW,Sun-Fire-X4550/.make.state
>
> Since he can't clone from a repo on hg.opensolaris.org, this suggests
> that the repo got corrupted. First step: ssh to hg.opensolaris.org, cd
> to the repo, and do "hg verify". If that doesn't fix things, go to
10 matches
Mail list logo
