On 2 Jun 2009, at 15:12, Jeff Pyle wrote:
> Hi Dan,
>
> One version of Python, and I think I'm okay on "extra" _conntrack.so
> files.
>
> I run media-relay from the path after a system-wide installation.
> It looks
> like that's where it's picking it up from:
>
> # python -c "import sys, med
Dan,
I copied the file directly from the build directory into the directory you
showed me how to find. It gets as far as complaining about the dispatcher,
which is fine since I haven't gotten that far yet.
- Jeff
On 6/2/09 8:12 AM, "Jeff Pyle" wrote:
> Hi Dan,
>
> One version of Python,
Hi Dan,
One version of Python, and I think I'm okay on "extra" _conntrack.so files.
I run media-relay from the path after a system-wide installation. It looks
like that's where it's picking it up from:
# python -c "import sys, mediaproxy; print sys.modules['mediaproxy']"
It appears I am missi
On 2 Jun 2009, at 10:33, Dan Pascu wrote:
> On 2 Jun 2009, at 00:41, Dan Pascu wrote:
>
>>
>> On 1 Jun 2009, at 16:11, Jeff Pyle wrote:
>>
>>> Dan,
>>>
>>> It did not exit cleanly:
>>>
>>> # python -c "from mediaproxy.interfaces.system import _conntrack"
>>> Traceback (most recent call last):
>>>
On 2 Jun 2009, at 00:41, Dan Pascu wrote:
>
> On 1 Jun 2009, at 16:11, Jeff Pyle wrote:
>
>> Dan,
>>
>> It did not exit cleanly:
>>
>> # python -c "from mediaproxy.interfaces.system import _conntrack"
>> Traceback (most recent call last):
>> File "", line 1, in
>> ImportError: cannot import name
On 1 Jun 2009, at 16:11, Jeff Pyle wrote:
Dan,
It did not exit cleanly:
# python -c "from mediaproxy.interfaces.system import _conntrack"
Traceback (most recent call last):
File "", line 1, in
ImportError: cannot import name _conntrack
I do not know what the matter is. The file is there
Dan,
It did not exit cleanly:
# python -c "from mediaproxy.interfaces.system import _conntrack"
Traceback (most recent call last):
File "", line 1, in
ImportError: cannot import name _conntrack
- Jeff
On 5/31/09 6:34 AM, "Dan Pascu" wrote:
> Everything seems to be all right there, so I
On Saturday 30 May 2009, Jeff Pyle wrote:
> Dan,
>
> # python -c "import sys; print sys.path"
> ['', '/usr/lib/python2.5', '/usr/lib/python2.5/plat-linux2-sparc',
> '/usr/lib/python2.5/lib-tk', '/usr/lib/python2.5/lib-dynload',
> '/usr/local/lib/python2.5/site-packages',
> '/usr/lib/python2.5/site
Dan,
# python -c "import sys; print sys.path"
['', '/usr/lib/python2.5', '/usr/lib/python2.5/plat-linux2-sparc',
'/usr/lib/python2.5/lib-tk', '/usr/lib/python2.5/lib-dynload',
'/usr/local/lib/python2.5/site-packages',
'/usr/lib/python2.5/site-packages', '/var/lib/python-support/python2.5']
# ldd
On Saturday 30 May 2009, Jeff Pyle wrote:
> It appears I wrote too soon.
>
> While everything did install correctly, media-relay gives the following
> error:
>
> fatal error: failed to create MediaProxy Relay: cannot import name
> _conntrack
> Traceback (most recent call last):
> --- ---
> Fil
It appears I wrote too soon.
While everything did install correctly, media-relay gives the following
error:
fatal error: failed to create MediaProxy Relay: cannot import name
_conntrack
Traceback (most recent call last):
--- ---
File "/usr/bin/media-relay", line 55, in
from mediaproxy.rel
Dan,
I believe I'm beginning to wrap my mind around the coolness that is Debian
packaging. Per your example I updated python-application from the source
repository, applied both patches to mediaproxy-2.3.4, built the packages and
installed them without any issues. Almost like I knew what I was d
On Thursday 28 May 2009, Jeff Pyle wrote:
> Dan,
>
> With your patch Mediaproxy 2.3.2 built packages without any problems. On an
> x86 CentOS install I run 2.3.2 with the older version of python-application.
> But, installing the package, I get:
>
> Starting MediaProxy relay: media-relayCannot s
On Thursday 28 May 2009, Jeff Pyle wrote:
> Hmm, it appears I spoke too soon. It wants python-application version
> 1.1.1, but only 1.0.9-4 is available for this architecture.
My guess is that you mean distribution. python-application is architecture
independent so it is available with the same
On Thursday 28 May 2009, Jeff Pyle wrote:
> Hmm, it appears I spoke too soon. It wants python-application version
> 1.1.1, but only 1.0.9-4 is available for this architecture. Is this
> crucial?
Yes. mediaproxy-2.3.4 uses some of the new stuff in 1.1.1
--
Dan
_
Dan,
With your patch Mediaproxy 2.3.2 built packages without any problems. On an
x86 CentOS install I run 2.3.2 with the older version of python-application.
But, installing the package, I get:
Starting MediaProxy relay: media-relayCannot start MediaProxy Relay. A Linux
host is required for oper
Hmm, it appears I spoke too soon. It wants python-application version
1.1.1, but only 1.0.9-4 is available for this architecture. Is this
crucial?
- Jeff
On 5/28/09 3:51 PM, "Jeff Pyle" wrote:
> That worked.
>
>
> On 5/28/09 9:19 AM, "Dan Pascu" wrote:
>
>> On Thursday 28 May 2009, Jef
That worked.
On 5/28/09 9:19 AM, "Dan Pascu" wrote:
> On Thursday 28 May 2009, Jeff Pyle wrote:
>> Hi Dan,
>>
>> Output was:
>> linux2-sparc Linux
>>
>> Iptables and conntrack are supported; the libnetfilter-conntrack-dev package
>> installed properly as part of the dependency packages list
On Thursday 28 May 2009, Jeff Pyle wrote:
> Hi Dan,
>
> Output was:
> linux2-sparc Linux
>
> Iptables and conntrack are supported; the libnetfilter-conntrack-dev package
> installed properly as part of the dependency packages listed in the install
> file.
>
> The build file is attached. Looki
Hi Dan,
Output was:
linux2-sparc Linux
Iptables and conntrack are supported; the libnetfilter-conntrack-dev package
installed properly as part of the dependency packages listed in the install
file.
The build file is attached. Looking through it I notice a few things that
cause me to raise an
On Wednesday 27 May 2009, Jeff Pyle wrote:
> Hi Dan,
>
> It's Debian 5.0.1 on sparc architecture, a fresh installation. Debhelper is
> the at the newest version, according to apt-get.
>
> apt-get build-dep mediaproxy-relay seems okay. It reported "0 upgraded, 0
> newly installed, 0 to remove an
On Wednesday 27 May 2009, Jeff Pyle wrote:
> Hi Dan,
>
> It's Debian 5.0.1 on sparc architecture, a fresh installation. Debhelper is
> the at the newest version, according to apt-get.
>
> apt-get build-dep mediaproxy-relay seems okay. It reported "0 upgraded, 0
> newly installed, 0 to remove an
Hi Dan,
It's Debian 5.0.1 on sparc architecture, a fresh installation. Debhelper is
the at the newest version, according to apt-get.
apt-get build-dep mediaproxy-relay seems okay. It reported "0 upgraded, 0
newly installed, 0 to remove and 0 not upgraded." I ran the large apt-get
install comma
On Tuesday 26 May 2009, Jeff Pyle wrote:
> Hello,
>
> I got the following error when trying to debuild on Debian Lenny:
>
> /chop/
> dh_installudev -pmediaproxy-relay
> dh_lintian -pmediaproxy-relay
> dh_install -pmediaproxy-relay
> cp: cannot stat `debian/tmp/usr/bin/media-relay': No such file o
Hello,
I got the following error when trying to debuild on Debian Lenny:
/chop/
dh_installudev -pmediaproxy-relay
dh_lintian -pmediaproxy-relay
dh_install -pmediaproxy-relay
cp: cannot stat `debian/tmp/usr/bin/media-relay': No such file or directory
dh_install: command returned error code 256
mak
25 matches
Mail list logo
