Hello,
after the discussion on devel mailing list was decided to migrate OpenSER CVS repository to SVN. Most of developers considered the SVN more convenient to work with, especially when hunting reported bugs (svn revision number is printed by openser -V).
Unfortunately this bring a bit of work for those installing and maintaining OpenSER from CVS. The have to grab the subversion (svn) tree righ now. There are no changes in directory structure, so any patch you had privately should apply easy. To get the same directory tree as for CVS:
# svn co https://openser.svn.sourceforge.net/svnroot/openser sip-server
For details about how to get a certain branch, please see the download page on http://www.openser.org: http://www.openser.org/index.php?option=com_content&task=view&id=29&...
We are still working on making snapshot system using SVN, and maybe some other tools are not yet updated, but they will be in the next days. However, what is most important should be ready to go -- source tree should be fully functional with SVN. Please let us know if you encounter any issue.
The translation to SVN was made over this weeken. New commits were already done to SVN. There was no critical update you should run after, but is recommended to get SVN version as soon as possible. Old branches were migrated (releases 0.9.x, 1.0.x, 1.1.x).
For the reference, initial revision for subversion is 1689. Once you get your patch against latest CVS version availabe, then should be no issue to apply it to this subversion revision. Full commit history from CVS is available on SVN.
Hope SVN will make openser maintenance easier for all of you. Here are some links to get you familiar with SVN commands and capabilities: http://svnbook.red-bean.com/nightly/en/index.html http://subversion.tigris.org/
OpenSER SVN page at sourceforge: http://sourceforge.net/svn/?group_id=139143
Cheers, Daniel
Hi,
just a completion: CVS repository is still available but in read-only mode (both for anonymous and developers). The idea is to allow people having local changes into their CVS checkouts to generate patches against CVS repo (cvs diff) and to apply the patches on a SVN checkout.
After some time, the CVS repo will be killed.
Regards, Bogdan
Daniel-Constantin Mierla wrote:
Hello,
after the discussion on devel mailing list was decided to migrate OpenSER CVS repository to SVN. Most of developers considered the SVN more convenient to work with, especially when hunting reported bugs (svn revision number is printed by openser -V).
Unfortunately this bring a bit of work for those installing and maintaining OpenSER from CVS. The have to grab the subversion (svn) tree righ now. There are no changes in directory structure, so any patch you had privately should apply easy. To get the same directory tree as for CVS:
# svn co https://openser.svn.sourceforge.net/svnroot/openser sip-server
For details about how to get a certain branch, please see the download page on http://www.openser.org: http://www.openser.org/index.php?option=com_content&task=view&id=29&...
We are still working on making snapshot system using SVN, and maybe some other tools are not yet updated, but they will be in the next days. However, what is most important should be ready to go -- source tree should be fully functional with SVN. Please let us know if you encounter any issue.
The translation to SVN was made over this weeken. New commits were already done to SVN. There was no critical update you should run after, but is recommended to get SVN version as soon as possible. Old branches were migrated (releases 0.9.x, 1.0.x, 1.1.x).
For the reference, initial revision for subversion is 1689. Once you get your patch against latest CVS version availabe, then should be no issue to apply it to this subversion revision. Full commit history from CVS is available on SVN.
Hope SVN will make openser maintenance easier for all of you. Here are some links to get you familiar with SVN commands and capabilities: http://svnbook.red-bean.com/nightly/en/index.html http://subversion.tigris.org/
OpenSER SVN page at sourceforge: http://sourceforge.net/svn/?group_id=139143
Cheers, Daniel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
openser -V doesn't print the revision number:
# ./openser -V version: openser 1.2.0-pre6-tls (arm/linux) flags: STATS: Off, EXTRA_DEBUG, USE_IPV6, USE_TCP, USE_TLS, DISABLE_NAGLE, USE_MCAST, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. @(#) $Id: main.c 1693 2007-02-26 11:43:16Z bogdan_iancu $ main.c compiled on 20:45:52 Feb 26 2007 with /home/admin/slug-3.10/releases/slugos-3.10-beta/openslug-nslu2.tmp/cross/bin/armeb-linux-gcc 3.4.4
Regards, Ovidiu Sas
On 2/26/07, Daniel-Constantin Mierla daniel@voice-system.ro wrote:
Hello,
after the discussion on devel mailing list was decided to migrate OpenSER CVS repository to SVN. Most of developers considered the SVN more convenient to work with, especially when hunting reported bugs (svn revision number is printed by openser -V).
Unfortunately this bring a bit of work for those installing and maintaining OpenSER from CVS. The have to grab the subversion (svn) tree righ now. There are no changes in directory structure, so any patch you had privately should apply easy. To get the same directory tree as for CVS:
# svn co https://openser.svn.sourceforge.net/svnroot/openser sip-server
For details about how to get a certain branch, please see the download page on http://www.openser.org: http://www.openser.org/index.php?option=com_content&task=view&id=29&...
We are still working on making snapshot system using SVN, and maybe some other tools are not yet updated, but they will be in the next days. However, what is most important should be ready to go -- source tree should be fully functional with SVN. Please let us know if you encounter any issue.
The translation to SVN was made over this weeken. New commits were already done to SVN. There was no critical update you should run after, but is recommended to get SVN version as soon as possible. Old branches were migrated (releases 0.9.x, 1.0.x, 1.1.x).
For the reference, initial revision for subversion is 1689. Once you get your patch against latest CVS version availabe, then should be no issue to apply it to this subversion revision. Full commit history from CVS is available on SVN.
Hope SVN will make openser maintenance easier for all of you. Here are some links to get you familiar with SVN commands and capabilities: http://svnbook.red-bean.com/nightly/en/index.html http://subversion.tigris.org/
OpenSER SVN page at sourceforge: http://sourceforge.net/svn/?group_id=139143
Cheers, Daniel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
On Dienstag 27 Februar 2007, Ovidiu Sas wrote:
openser -V doesn't print the revision number:
# ./openser -V
[...]
@(#) $Id: main.c 1693 2007-02-26 11:43:16Z bogdan_iancu $
^^^^ It's right there... :)
Bastian
yeah ... right .... :-) Let's put it this way. I would expect it to see it here and, like it was pointed in all other subsequent e-mails, pointed to the latest revision :-)
# ./openserctl fifo version Server:: OpenSer (1.2.0-pre6-tls (arm/linux)) #
Ovidiu
On 2/27/07, Bastian Friedrich bastian.friedrich@collax.com wrote:
On Dienstag 27 Februar 2007, Ovidiu Sas wrote:
openser -V doesn't print the revision number:
# ./openser -V
[...]
@(#) $Id: main.c 1693 2007-02-26 11:43:16Z bogdan_iancu $
^^^^It's right there... :)
Bastian
-- Collax GmbH . Burkheimer Straße 3 . 79111 Freiburg . Germany p: +49 (0) 761-45684-24 f: +49 (0) 761-45684-10 www.collax.com
\ Paranoia is nothing to be afraid of!!
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
On 02/27/07 05:22, Ovidiu Sas wrote:
openser -V doesn't print the revision number:
yes, by now. I am thinking in using the svnversion tool to get that included in these details, when using sources.
Cheers, Daniel
# ./openser -V version: openser 1.2.0-pre6-tls (arm/linux) flags: STATS: Off, EXTRA_DEBUG, USE_IPV6, USE_TCP, USE_TLS, DISABLE_NAGLE, USE_MCAST, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. @(#) $Id: main.c 1693 2007-02-26 11:43:16Z bogdan_iancu $ main.c compiled on 20:45:52 Feb 26 2007 with /home/admin/slug-3.10/releases/slugos-3.10-beta/openslug-nslu2.tmp/cross/bin/armeb-linux-gcc
3.4.4
Regards, Ovidiu Sas
On 2/26/07, Daniel-Constantin Mierla daniel@voice-system.ro wrote:
Hello,
after the discussion on devel mailing list was decided to migrate OpenSER CVS repository to SVN. Most of developers considered the SVN more convenient to work with, especially when hunting reported bugs (svn revision number is printed by openser -V).
Unfortunately this bring a bit of work for those installing and maintaining OpenSER from CVS. The have to grab the subversion (svn) tree righ now. There are no changes in directory structure, so any patch you had privately should apply easy. To get the same directory tree as for CVS:
# svn co https://openser.svn.sourceforge.net/svnroot/openser sip-server
For details about how to get a certain branch, please see the download page on http://www.openser.org: http://www.openser.org/index.php?option=com_content&task=view&id=29&...
We are still working on making snapshot system using SVN, and maybe some other tools are not yet updated, but they will be in the next days. However, what is most important should be ready to go -- source tree should be fully functional with SVN. Please let us know if you encounter any issue.
The translation to SVN was made over this weeken. New commits were already done to SVN. There was no critical update you should run after, but is recommended to get SVN version as soon as possible. Old branches were migrated (releases 0.9.x, 1.0.x, 1.1.x).
For the reference, initial revision for subversion is 1689. Once you get your patch against latest CVS version availabe, then should be no issue to apply it to this subversion revision. Full commit history from CVS is available on SVN.
Hope SVN will make openser maintenance easier for all of you. Here are some links to get you familiar with SVN commands and capabilities: http://svnbook.red-bean.com/nightly/en/index.html http://subversion.tigris.org/
OpenSER SVN page at sourceforge: http://sourceforge.net/svn/?group_id=139143
Cheers, Daniel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
On 02/27/07 11:37, Daniel-Constantin Mierla wrote:
On 02/27/07 05:22, Ovidiu Sas wrote:
openser -V doesn't print the revision number:
yes, by now. I am thinking in using the svnversion tool to get that included in these details, when using sources.
to be more clear. it is a svn revision, but not the latest one overall, just latest one for main.c (Bastian pointed in another email). By using svnversion in Makefile should be possible to get the latest one.
Cheers, Daniel
# ./openser -V version: openser 1.2.0-pre6-tls (arm/linux) flags: STATS: Off, EXTRA_DEBUG, USE_IPV6, USE_TCP, USE_TLS, DISABLE_NAGLE, USE_MCAST, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. @(#) $Id: main.c 1693 2007-02-26 11:43:16Z bogdan_iancu $ main.c compiled on 20:45:52 Feb 26 2007 with /home/admin/slug-3.10/releases/slugos-3.10-beta/openslug-nslu2.tmp/cross/bin/armeb-linux-gcc
3.4.4
Regards, Ovidiu Sas
On 2/26/07, Daniel-Constantin Mierla daniel@voice-system.ro wrote:
Hello,
after the discussion on devel mailing list was decided to migrate OpenSER CVS repository to SVN. Most of developers considered the SVN more convenient to work with, especially when hunting reported bugs (svn revision number is printed by openser -V).
Unfortunately this bring a bit of work for those installing and maintaining OpenSER from CVS. The have to grab the subversion (svn) tree righ now. There are no changes in directory structure, so any patch you had privately should apply easy. To get the same directory tree as for CVS:
# svn co https://openser.svn.sourceforge.net/svnroot/openser sip-server
For details about how to get a certain branch, please see the download page on http://www.openser.org: http://www.openser.org/index.php?option=com_content&task=view&id=29&...
We are still working on making snapshot system using SVN, and maybe some other tools are not yet updated, but they will be in the next days. However, what is most important should be ready to go -- source tree should be fully functional with SVN. Please let us know if you encounter any issue.
The translation to SVN was made over this weeken. New commits were already done to SVN. There was no critical update you should run after, but is recommended to get SVN version as soon as possible. Old branches were migrated (releases 0.9.x, 1.0.x, 1.1.x).
For the reference, initial revision for subversion is 1689. Once you get your patch against latest CVS version availabe, then should be no issue to apply it to this subversion revision. Full commit history from CVS is available on SVN.
Hope SVN will make openser maintenance easier for all of you. Here are some links to get you familiar with SVN commands and capabilities: http://svnbook.red-bean.com/nightly/en/index.html http://subversion.tigris.org/
OpenSER SVN page at sourceforge: http://sourceforge.net/svn/?group_id=139143
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
-
Bastian Friedrich -
Bogdan-Andrei Iancu -
Daniel-Constantin Mierla -
Ovidiu Sas