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 upgrade mercurial and it looks to
me like a newer version is overdue to hit the stable tree - not a sage
problem.
Francois
On Thu, 27 Feb 2014 14:40:57 Volker Braun wrote:
> 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 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
> > > 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.5.p2
> >
> > > still failed.
> > >
> > > On Thursday, February 27, 2014 3:51:42 PM UTC-6, François wrote:
> > > > 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 versions: 2.4.2 ~2.5.4 ~2.6.3 ~2.7.2 ~2.8.2 ~2.9
> >
> > **9999
> >
> > > > > {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-completion)
> > > > >
> > > > > I didn't remove the tinfo patch and rebuild Sage, but I did patch my
> > > >
> > > > Gentoo
> > > >
> > > > > python with it and python built just fine. I suspect it is somewhere
> > > >
> > > > else,
> > > >
> > > > > unless Gentoo is doing something very, very tricky?
> > > > >
> > > > > On Thursday, February 27, 2014 3:13:28 PM UTC-6, François wrote:
> > > > > > 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 remove it from my PATH?
> > > > > > >
> > > > > > > Experiment for the brave: Delete
> > > > > > > build/pkgs/python/patches/tinfo.patch
> > > > > > > and try rebuilding python.
> > > > > >
> > > > > > And because I built 6.2.beta2 from scratch without an hitch:
> > > > > > Output of
> > > > > > eix dev-vcs/mercurial
> > > > > >
> > > > > > Francois
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/groups/opt_out.
