That may be actually the beginning of an explanation of why the problem
is solved by upgrading system mercurial - the new one uses a newer python
infrastructure in Gentoo and may be protected from such injection.
So we may have a couple of question down.
So Gentoo users affected by this should upg
Mercurial is a Python program. While building Sage's Python the interpreter
might be in a bad shape, or we inject libraries via LD_LIBRARY_PATH into
the system interpreter that break it.
On Thursday, February 27, 2014 11:37:37 PM UTC+1, François wrote:
>
> It is all a bit of a mystery. Why is th
It is all a bit of a mystery. Why is the system python building? Why is sage's
one not? Why did it stop working when upgrading? Why moving to hg-2.5 solve
the problem?
Francois
On Thu, 27 Feb 2014 14:31:12 strogdon wrote:
> So with mercurial-2.5.4 installed python-2.7.5.p2 will build. So perhaps
So with mercurial-2.5.4 installed python-2.7.5.p2 will build. So perhaps
the version I had installed (2.4.2) is buggy? But it was this 2.4.2 version
that was present when python-2.7.5.p1 built without a problem? Hmm. Just to
make sure, before I did this, I rebuilt mercurial-2.4.2 and python-2.7.
Can you update to 2.5.4 at least? If that works I wonder what is done on
Gentoo to avoid the problem. Could there be something in ~/.hgrc or ~/.sage
that triggers this?
Francois
On Thu, 27 Feb 2014 13:19:24 strogdon wrote:
> # eix dev-vcs/mercurial
> [I] dev-vcs/mercurial
> Available versio
# eix dev-vcs/mercurial
[I] dev-vcs/mercurial
Available versions: 2.4.2 ~2.5.4 ~2.6.3 ~2.7.2 ~2.8.2 ~2.9 **
{bugzilla emacs gpg test tk zsh-completion PYTHON_TARGETS="python2_6
python2_7"}
Installed versions: 2.4.2(10:03:49 AM 02/12/2013)(bugzilla tk -emacs
-gpg -test -zsh-comple
On Fri, 28 Feb 2014 10:10:45 François Bissey wrote:
> On Thu, 27 Feb 2014 11:44:30 strogdon wrote:
> > After looking at ticket 15317 I see that could be a possibility. From the
> > sage shell
> >
> > (sage-sh) strogdon@ledaig:sage$ which hg
> > /usr/bin/hg
> >
> > So, why now? And must I now rem
On Thu, 27 Feb 2014 11:44:30 strogdon wrote:
> After looking at ticket 15317 I see that could be a possibility. From the
> sage shell
>
> (sage-sh) strogdon@ledaig:sage$ which hg
> /usr/bin/hg
>
> So, why now? And must I now remove it from my PATH?
Experiment for the brave: Delete
build/pkgs/p
On Thu, 27 Feb 2014 12:44:22 strogdon wrote:
> Which python logs, Gentoo or vanilla Sage?
>
Gentoo.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release
Which python logs, Gentoo or vanilla Sage?
On Thursday, February 27, 2014 2:35:21 PM UTC-6, François wrote:
>
> On Thu, 27 Feb 2014 12:33:10 strogdon wrote:
> > Yes this seems to do the trick. I'm sure my system hg is not broken. My
> > system python builds yet fine with it present. When it can'
On Thu, 27 Feb 2014 12:33:10 strogdon wrote:
> Yes this seems to do the trick. I'm sure my system hg is not broken. My
> system python builds yet fine with it present. When it can't find a HG
> repository it aborts the search and continues building.
>
> On Thursday, February 27, 2014 2:22:33 PM UT
Yes this seems to do the trick. I'm sure my system hg is not broken. My
system python builds yet fine with it present. When it can't find a HG
repository it aborts the search and continues building.
On Thursday, February 27, 2014 2:22:33 PM UTC-6, François wrote:
>
> On Thu, 27 Feb 2014 11:44:30
On 2014-02-27 19:19, strogdon wrote:
gcc -pthread -c -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3
-Wall -I. -IInclude -I./Include -fPIC -DPy_BUILD_CORE \
-DSVNVERSION="\"`LC_ALL=C svnversion .`\"" \
-DHGVERSION="\"`LC_ALL=C hg id -i .`\"" \
-DHGTAG="\"`LC_ALL=C hg i
On Thu, 27 Feb 2014 11:44:30 strogdon wrote:
> After looking at ticket 15317 I see that could be a possibility. From the
> sage shell
>
> (sage-sh) strogdon@ledaig:sage$ which hg
> /usr/bin/hg
>
> So, why now? And must I now remove it from my PATH?
I seriously doubt hg on Steve's system is bro
After looking at ticket 15317 I see that could be a possibility. From the
sage shell
(sage-sh) strogdon@ledaig:sage$ which hg
/usr/bin/hg
So, why now? And must I now remove it from my PATH?
On Thursday, February 27, 2014 1:36:05 PM UTC-6, Volker Braun wrote:
>
> You have a "hg" program in your
You have a "hg" program in your path that is trying to interactively ask
questions.
On Thursday, February 27, 2014 7:19:50 PM UTC+1, strogdon wrote:
>
> I've seen no post on the issue I'm having so here goes. I have
> sage-6.2.beta1 installed. After pulling from the git repo to get 6.2.beta2
I've seen no post on the issue I'm having so here goes. I have
sage-6.2.beta1 installed. After pulling from the git repo to get 6.2.beta2
and issuing make as I've always done, the new python (python-2.7.5.p2) will
not build. It just hangs doing something? Before I do a make distclean to
see if
17 matches
Mail list logo
