OK. I don't see any difference but I'll trust you on this :).
Thanks for your contribution.
revno: 1217
author: Thomas Klausner
committer: Siegfried-Angel Gevatter Pujals
branch nick: zeitgeist-trunk
timestamp: Tue 2009-12-08 14:50:42
I looked at the dependencies in the Makefile and came up with something
that looked more useful to me. The attached patch works for me -- please
commit :)
** Attachment added: "Patch fixing the problem."
http://launchpadlibrarian.net/36574848/patch-ab
--
zeitgeist-0.2.0: using "env python" in
(Correction: in my previous post "configure time" should be "build
time", ie. it's generated when "make" is run).
2009/12/2 Thomas Klausner :
> Well, then my detailed diagnosis was incorrect; however, the main part was:
> it doesn't work. zeitgeist-daemon and zeitgeist-datahub start with "#!
> /
Well, then my detailed diagnosis was incorrect; however, the main part was: it
doesn't work. zeitgeist-daemon and zeitgeist-datahub start with "#!
/usr/bin/python", while config.log contains:
PYTHON='/usr/pkg/bin/python2.6'
which gets forwarded to Makefile as
PYTHON = /usr/pkg/bin/python2.6
--
2009/12/2 Thomas Klausner :
> The zeitgeist-daemon and zeitgeist-datahub files in the distribution have "#!
> /usr/bin/python" in the first line, so the sed pattern doesn't match.
zeitgeist-daemon and zeitgeist-datahub are generated from
zeitgeist-daemon.py and zeitgeist-datahub.py at configure t
I tried the 0.3.0, and the release has a bug:
The zeitgeist-daemon and zeitgeist-datahub files in the distribution have "#!
/usr/bin/python" in the first line, so the sed pattern doesn't match.
While looking for the reason, I also stumbled over:
"all-local: zeitgeist-daemon zeitgeist-datahub.py"
1184 Siegfried-Angel Gevatter Pujals 2009-11-27
Substitute "/usr/bin/env python" with the hardcoded path at compile time
Thomas, can you please verify that the fix works for you? :)
** Changed in: zeitgeist
Status: Incomplete => Fix Released
--
zeitgeist-0.2.0: using "env python
** Branch linked: lp:zeitgeist
--
zeitgeist-0.2.0: using "env python" instead of python executable name
https://bugs.launchpad.net/bugs/401199
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.
Status in Zeitgeist Fra
I'm on it.
--
zeitgeist-0.2.0: using "env python" instead of python executable name
https://bugs.launchpad.net/bugs/401199
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.
Status in Zeitgeist Framework: Incomplete
@Thomas can u send a patch please :)
--
zeitgeist-0.2.0: using "env python" instead of python executable name
https://bugs.launchpad.net/bugs/401199
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.
Status in Zeitgei
@Siegfried:
sed magic in the Makefile sounds fine.
@Markus:
In NetBSD pkgsrc, multiple versions of python can be installed at the same
time. They are called python2.4, python2.5, ...; also multiple versions of
python modules can be installed, once per python version.
Also, pkgsrc doesn't instal
I don't get why we need magic like ${PYTHON} at all. Isn't
/usr/bin/python always linked to the python version preferred by the
user? - so wn't fix for me too, unless there is a good reason I'm
missing.
** Changed in: zeitgeist
Status: Triaged => Incomplete
--
zeitgeist-0.2.0: using "env
This is a WONTFIX from my side (feature, not a bug), but I can be
convinced otherwise.
(In any case, we can't just change the files directly because then
Zeitgeist wouldn't run in-place anymore, but some little sed magic in
the Makefiles would do I guess.)
--
zeitgeist-0.2.0: using "env python"
Small task for Siegfried
** Changed in: zeitgeist
Status: New => Triaged
** Changed in: zeitgeist
Importance: Undecided => Low
** Changed in: zeitgeist
Assignee: (unassigned) => Siegfried Gevatter (rainct)
** Changed in: zeitgeist
Milestone: None => 0.3.0
--
zeitgeist-0.2.0
14 matches
Mail list logo
