Hello everybody,
I would like to ask all of you that have access to different OS distributions to help with package generation. Please reply (personally if you prefer better this way) with OS name, version and architecture. We are looking mainly for common used distributions: Debian - testing (the other two are accounted already) Redhat Suse Open/NetBSD (FreeBSD accounted) SUN/Solaris Gentoo ...
We will help as much as possible with guidelines. We would require tomorrow an early compiling on all available systems to fix eventual warnings.
Cheers, Daniel
I will check on Gentoo-x86 2005.1.
On Oct 27, 2005, at 2:58 AM, Daniel-Constantin Mierla wrote:
Hello everybody,
I would like to ask all of you that have access to different OS distributions to help with package generation. Please reply (personally if you prefer better this way) with OS name, version and architecture. We are looking mainly for common used distributions: Debian - testing (the other two are accounted already) Redhat Suse Open/NetBSD (FreeBSD accounted) SUN/Solaris Gentoo ...
We will help as much as possible with guidelines. We would require tomorrow an early compiling on all available systems to fix eventual warnings.
Cheers, Daniel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
I had a good compilation on Gentoo-x86 2005.1 with attached ebuild file, which is modified according to Gentoo ebuild guildeline and ebuild maintainer's comments. Please include this ebuild for final release if possible.
There are some warning messages (example below) during compilation, but I checked previously that these can be safely ignored and seems there is no clear instruction on how to deal with it. Warning message example: " usr/lib/openser/modules/maxfwd.so usr/lib/openser/modules/maxfwd.so will contain runtime text relocations Text relocations require a lot of extra work to be preformed by the dynamic linker which will cause serious performance impact on IA-32 and might not function properly on other architectures hppa for example. If you are a programmer please take a closer look at this package and consider writing a patch which addresses this problem."
-- Cheng
On Oct 27, 2005, at 2:58 AM, Daniel-Constantin Mierla wrote:
Hello everybody,
I would like to ask all of you that have access to different OS distributions to help with package generation. Please reply (personally if you prefer better this way) with OS name, version and architecture. We are looking mainly for common used distributions: Debian - testing (the other two are accounted already) Redhat Suse Open/NetBSD (FreeBSD accounted) SUN/Solaris Gentoo ...
We will help as much as possible with guidelines. We would require tomorrow an early compiling on all available systems to fix eventual warnings.
Cheers, Daniel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hello Cheng Zhang,
thank you. We will look at the warning, which is bit strange for me at the first sight. Have you compiled the radius modules too?
We will update the ebuild package on cvs and we would ask you to take care of gentoo package generation. I do not think you need further assistance, just the time when you can take the sources.
Cheers, Daniel
On 10/27/05 07:30, Cheng Zhang wrote:
I had a good compilation on Gentoo-x86 2005.1 with attached ebuild file, which is modified according to Gentoo ebuild guildeline and ebuild maintainer's comments. Please include this ebuild for final release if possible.
There are some warning messages (example below) during compilation, but I checked previously that these can be safely ignored and seems there is no clear instruction on how to deal with it. Warning message example: " usr/lib/openser/modules/maxfwd.so usr/lib/openser/modules/maxfwd.so will contain runtime text relocations Text relocations require a lot of extra work to be preformed by the dynamic linker which will cause serious performance impact on IA-32 and might not function properly on other architectures hppa for example. If you are a programmer please take a closer look at this package and consider writing a patch which addresses this problem."
-- Cheng
On Oct 27, 2005, at 2:58 AM, Daniel-Constantin Mierla wrote:
Hello everybody,
I would like to ask all of you that have access to different OS distributions to help with package generation. Please reply (personally if you prefer better this way) with OS name, version and architecture. We are looking mainly for common used distributions: Debian - testing (the other two are accounted already) Redhat Suse Open/NetBSD (FreeBSD accounted) SUN/Solaris Gentoo ...
We will help as much as possible with guidelines. We would require tomorrow an early compiling on all available systems to fix eventual warnings.
Cheers, Daniel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
See below.
On 10/27/05, Daniel-Constantin Mierla daniel@voice-system.ro wrote:
Hello Cheng Zhang,
thank you. We will look at the warning, which is bit strange for me at the first sight. Have you compiled the radius modules too?
The warning message comes from Gentoo's Portage. Among the steps of building and installing the package source, there is a step of examing ELF binaries. In fact, it has such warning message for each .so file. I already saw such warnings months ago when I deal with OpenSER's ebuild for the first time. I did some google back then, and seems it's ok to ignore them. I don't know about others, but two Gentoo machines running OpenSER installed by this ebuild work fine in our internal testing environment (casual testing by a few people though).
We will update the ebuild package on cvs and we would ask you to take care of gentoo package generation. I do not think you need further assistance, just the time when you can take the sources.
Sure, I can do that. My goal on this one is actually getting the ebuild accepted into official ebuild tree. That way, folks running Gentoo can easily install OpenSER without looking around. :-)
- Cheng
Hello,
On 10/27/05 19:08, Cheng Zhang wrote:
See below.
On 10/27/05, Daniel-Constantin Mierla daniel@voice-system.ro wrote:
Hello Cheng Zhang,
thank you. We will look at the warning, which is bit strange for me at the first sight. Have you compiled the radius modules too?
The warning message comes from Gentoo's Portage. Among the steps of building and installing the package source, there is a step of examing ELF binaries. In fact, it has such warning message for each .so file. I already saw such warnings months ago when I deal with OpenSER's ebuild for the first time. I did some google back then, and seems it's ok to ignore them. I don't know about others, but two Gentoo machines running OpenSER installed by this ebuild work fine in our internal testing environment (casual testing by a few people though).
thanks for the clarifications.
We will update the ebuild package on cvs and we would ask you to take care of gentoo package generation. I do not think you need further assistance, just the time when you can take the sources.
Sure, I can do that. My goal on this one is actually getting the ebuild accepted into official ebuild tree. That way, folks running Gentoo can easily install OpenSER without looking around. :-)
That will be great. Thanks. Some docs to be updated, and tomorrow the packages building should start (it will be announced on the mailing list) - no time line or so, the packages will be added to the download site as soon as they are submitted. We will add contributed packages the days afterwards, too. This to be clear that no stress should be pushed by package generation.
Cheers, Daniel
- Cheng
Hi!
some question: for radius support - is radiusclient-ng 5.1 fine?
what about TLS: IMO it should be compiled by default, or we should have both: packages with TLS and without TLS support.
I think it is not a good idea to announce "first TLS-enabled" SIP proxy and then the compiled packages are not TLS capable. Thus, then we also has to add the openssl packages to the requriments for the openser package.
regards klaus
Daniel-Constantin Mierla wrote:
Hello everybody,
I would like to ask all of you that have access to different OS distributions to help with package generation. Please reply (personally if you prefer better this way) with OS name, version and architecture. We are looking mainly for common used distributions: Debian - testing (the other two are accounted already) Redhat Suse Open/NetBSD (FreeBSD accounted) SUN/Solaris Gentoo ...
We will help as much as possible with guidelines. We would require tomorrow an early compiling on all available systems to fix eventual warnings.
Cheers, Daniel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi Klaus,
as I see on http://developer.berlios.de/projects/radiusclient-ng/, 0.5.0 is not longer posted?!? So, 5.1 will be fine.
regarding the TLS. I was thinking to have two packages - one without TLS (as so far) and another one with TLS. The reason? I don't want to force dependencies to openssl for people not interested in TLS. As the packages will overlap, they must conflict at installation.
regards, Bogdan
Klaus Darilion wrote:
Hi!
some question: for radius support - is radiusclient-ng 5.1 fine?
what about TLS: IMO it should be compiled by default, or we should have both: packages with TLS and without TLS support.
I think it is not a good idea to announce "first TLS-enabled" SIP proxy and then the compiled packages are not TLS capable. Thus, then we also has to add the openssl packages to the requriments for the openser package.
regards klaus
Daniel-Constantin Mierla wrote:
Hello everybody,
I would like to ask all of you that have access to different OS distributions to help with package generation. Please reply (personally if you prefer better this way) with OS name, version and architecture. We are looking mainly for common used distributions: Debian - testing (the other two are accounted already) Redhat Suse Open/NetBSD (FreeBSD accounted) SUN/Solaris Gentoo ...
We will help as much as possible with guidelines. We would require tomorrow an early compiling on all available systems to fix eventual warnings.
Cheers, Daniel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Bogdan-Andrei Iancu wrote:
Hi Klaus,
as I see on http://developer.berlios.de/projects/radiusclient-ng/, 0.5.0 is not longer posted?!? So, 5.1 will be fine.
regarding the TLS. I was thinking to have two packages - one without TLS (as so far) and another one with TLS. The reason? I don't want to force dependencies to openssl for people not interested in TLS. As the packages will overlap, they must conflict at installation.
Sure. But is it possible to add the openssl package to the requriments for debian, e.g. dynamically when TLS==1 ?
regards klaus
regards, Bogdan
Klaus Darilion wrote:
Hi!
some question: for radius support - is radiusclient-ng 5.1 fine?
what about TLS: IMO it should be compiled by default, or we should have both: packages with TLS and without TLS support.
I think it is not a good idea to announce "first TLS-enabled" SIP proxy and then the compiled packages are not TLS capable. Thus, then we also has to add the openssl packages to the requriments for the openser package.
regards klaus
Daniel-Constantin Mierla wrote:
Hello everybody,
I would like to ask all of you that have access to different OS distributions to help with package generation. Please reply (personally if you prefer better this way) with OS name, version and architecture. We are looking mainly for common used distributions: Debian - testing (the other two are accounted already) Redhat Suse Open/NetBSD (FreeBSD accounted) SUN/Solaris Gentoo ...
We will help as much as possible with guidelines. We would require tomorrow an early compiling on all available systems to fix eventual warnings.
Cheers, Daniel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Klaus Darilion wrote:
Bogdan-Andrei Iancu wrote:
Hi Klaus,
as I see on http://developer.berlios.de/projects/radiusclient-ng/, 0.5.0 is not longer posted?!? So, 5.1 will be fine.
regarding the TLS. I was thinking to have two packages - one without TLS (as so far) and another one with TLS. The reason? I don't want to force dependencies to openssl for people not interested in TLS. As the packages will overlap, they must conflict at installation.
Sure. But is it possible to add the openssl package to the requriments for debian, e.g. dynamically when TLS==1 ?
not sure....have to check...in the worst case we have to have two specs :D.
regards, bogdan
regards klaus
regards, Bogdan
Klaus Darilion wrote:
Hi!
some question: for radius support - is radiusclient-ng 5.1 fine?
what about TLS: IMO it should be compiled by default, or we should have both: packages with TLS and without TLS support.
I think it is not a good idea to announce "first TLS-enabled" SIP proxy and then the compiled packages are not TLS capable. Thus, then we also has to add the openssl packages to the requriments for the openser package.
regards klaus
Daniel-Constantin Mierla wrote:
Hello everybody,
I would like to ask all of you that have access to different OS distributions to help with package generation. Please reply (personally if you prefer better this way) with OS name, version and architecture. We are looking mainly for common used distributions: Debian - testing (the other two are accounted already) Redhat Suse Open/NetBSD (FreeBSD accounted) SUN/Solaris Gentoo ...
We will help as much as possible with guidelines. We would require tomorrow an early compiling on all available systems to fix eventual warnings.
Cheers, Daniel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Bogdan-Andrei Iancu wrote:
Klaus Darilion wrote:
Bogdan-Andrei Iancu wrote:
Hi Klaus,
as I see on http://developer.berlios.de/projects/radiusclient-ng/, 0.5.0 is not longer posted?!? So, 5.1 will be fine.
regarding the TLS. I was thinking to have two packages - one without TLS (as so far) and another one with TLS. The reason? I don't want to force dependencies to openssl for people not interested in TLS. As the packages will overlap, they must conflict at installation.
Sure. But is it possible to add the openssl package to the requriments for debian, e.g. dynamically when TLS==1 ?
not sure....have to check...in the worst case we have to have two specs :D.
and "make deb_tls" ?
-
Bogdan-Andrei Iancu -
Cheng Zhang -
Daniel-Constantin Mierla -
Klaus Darilion