On Mar 18, 2012, at 10:48, Puneet Kishor wrote:
> Thank goodness I didn't force reinstall openssl or git.
Not that forcing a reinstall of openssl or git-core would have had any negative
consequences, aside from some wasted time and effort.
___
macpo
On Mar 18, 2012, at 10:10 AM, Rainer Müller wrote:
> On 2012-03-18 04:47, Mr. Puneet Kishor wrote:
>> 2. Somewhere along the line, I guess my OpenSSL got updated, and now,
>> everytime I try to do a `git push` to another server, I get the following
>> error
>>
>> OpenSSL version mismatch.
On 2012-03-18 04:47, Mr. Puneet Kishor wrote:
> 2. Somewhere along the line, I guess my OpenSSL got updated, and now,
> everytime I try to do a `git push` to another server, I get the following
> error
>
> OpenSSL version mismatch. Built against 105f, you have 1000100f
> fatal: T
On Sun, Mar 18, 2012 at 08:50, Puneet Kishor wrote:
> So, I was all set to force reinstall OpenSSL, but now I am thinking of
> force reinstalling git. However, there *is* one issue to consider -- I get
> exactly the same error as above when I try to do a
>
> ssh-keygen -t rsa
>
> which indica
On Mar 18, 2012, at 4:04 AM, Brandon Allbery wrote:
> On Sun, Mar 18, 2012 at 00:07, Jeremy Lavergne
> wrote:
> > However, my original error, one that prompted all this dance, still
> > persists. On my computer "A" when I do `git push computer_b" I get
> >
> > OpenSSL version mismatch.
On Mar 18, 2012, at 04:04, Brandon Allbery wrote:
> It's not openssl that needs to be rebuilt, but the library/program that is
> using openssl that is now inconsistent and needs to be rebuilt against the
> latest openssl. In this case that probably means git-core.
I'm updating git-core to 1.7
On Sun, Mar 18, 2012 at 00:07, Jeremy Lavergne
wrote:
> > However, my original error, one that prompted all this dance, still
> persists. On my computer "A" when I do `git push computer_b" I get
> >
> > OpenSSL version mismatch. Built against 105f, you have 1000100f
> > fatal: The
On Mar 17, 2012, at 23:12, Mr. Puneet Kishor wrote:
> Yet, on computer A, I get the following error
>
> computer A$git push computer_B
> OpenSSL version mismatch. Built against 105f, you have 1000100f
> fatal: The remote end hung up unexpectedly
>
> what is it trying to te
> Sadly, I can't just uninstall openssl and reinstall it. A million other ports
> depend on it, and it won't let me uninstall it. Just doing a "port install"
> doesn't help. I am caught in some kind of a nasty loop here.
>
> Suggestions?
sudo port -f uninstall openssl
sudo port install openssl.
You can use the force switch to make it uninstall and then reinstall
it. Or, as Jeremy suggested earlier, perhaps "sudo port upgrade
--force openssl" will force it to rebuild.
Scott
On Sat, Mar 17, 2012 at 9:34 PM, Mr. Puneet Kishor wrote:
>
> On Mar 17, 2012, at 11:27 PM, Jeremy Lavergne wrote
On Mar 17, 2012, at 11:27 PM, Jeremy Lavergne wrote:
>> I get the same error about OpenSSL mismatch. Looking at the date,
>> /opt/local/bin/ssh-keygen is from Sep 11, 2011. Do I need to update that? If
>> yes, what port is that a part of, since I can't find it standalone on
>> macports.
>
> Y
> I get the same error about OpenSSL mismatch. Looking at the date,
> /opt/local/bin/ssh-keygen is from Sep 11, 2011. Do I need to update that? If
> yes, what port is that a part of, since I can't find it standalone on
> macports.
You can run `port provides FILE` to find out which package a giv
On Mar 17, 2012, at 11:14 PM, Jeremy Lavergne wrote:
>> Well, I am not sure if it is the issue. On both computers I have the
>> identical versions of openssl now. See below
>>
>> computer A$port installed openssl
>> The following ports are currently installed:
>>openssl @1.0.
> Well, I am not sure if it is the issue. On both computers I have the
> identical versions of openssl now. See below
>
> computer A$port installed openssl
> The following ports are currently installed:
> openssl @1.0.0e_0
> openssl @1.0.0e_1
> openssl @1.0.0g
On Mar 17, 2012, at 11:07 PM, Jeremy Lavergne wrote:
>> However, my original error, one that prompted all this dance, still
>> persists. On my computer "A" when I do `git push computer_b" I get
>>
>> OpenSSL version mismatch. Built against 105f, you have 1000100f
>> fatal: The rem
> However, my original error, one that prompted all this dance, still persists.
> On my computer "A" when I do `git push computer_b" I get
>
> OpenSSL version mismatch. Built against 105f, you have 1000100f
> fatal: The remote end hung up unexpectedly
>
> On computer "B" I have t
On Mar 17, 2012, at 10:58 PM, Jeremy Lavergne wrote:
>> In any case, I decided to update it all to the latest MacPorts version, and
>> have now hit a snag with the following message on doing `sudo port install
>> git-core`
>>
>> Error: Dependency 'p5.12-error' not found.
>> Error: St
> 1. On computer "A" I upgraded Postgres server from 9.0.x to 9.1.3, and
> Postgis 1.5.3. This caused Geos to be upgraded from 3.3.0 to 3.3.1, but
> caused gdal 1.8.0 to break. I fixed this by upgrading gdal 1.8.0 to gdal
> 1.9.0, but am wondering, why didn't gdal also upgrade when Geos was upda
I have landed in a bit of a funk. Two tales, one solved (but puzzling) and the
other unsolved --
1. On computer "A" I upgraded Postgres server from 9.0.x to 9.1.3, and Postgis
1.5.3. This caused Geos to be upgraded from 3.3.0 to 3.3.1, but caused gdal
1.8.0 to break. I fixed this by upgrading g
19 matches
Mail list logo
