You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
|
Sep
(5) |
Oct
(110) |
Nov
(67) |
Dec
(17) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(32) |
Feb
(33) |
Mar
(17) |
Apr
(22) |
May
(13) |
Jun
(29) |
Jul
(19) |
Aug
(3) |
Sep
(18) |
Oct
(37) |
Nov
(187) |
Dec
(107) |
2003 |
Jan
(97) |
Feb
(59) |
Mar
(109) |
Apr
(83) |
May
(77) |
Jun
(55) |
Jul
(33) |
Aug
(36) |
Sep
(62) |
Oct
(43) |
Nov
(21) |
Dec
(25) |
2004 |
Jan
(28) |
Feb
(23) |
Mar
(29) |
Apr
(12) |
May
(25) |
Jun
(11) |
Jul
(2) |
Aug
(29) |
Sep
(15) |
Oct
(21) |
Nov
(17) |
Dec
(8) |
2005 |
Jan
(17) |
Feb
(16) |
Mar
(43) |
Apr
(23) |
May
(23) |
Jun
(32) |
Jul
(40) |
Aug
(26) |
Sep
(26) |
Oct
(53) |
Nov
(37) |
Dec
(27) |
2006 |
Jan
(29) |
Feb
(56) |
Mar
(60) |
Apr
(47) |
May
(25) |
Jun
(6) |
Jul
(13) |
Aug
(11) |
Sep
(20) |
Oct
(12) |
Nov
(12) |
Dec
(13) |
2007 |
Jan
(16) |
Feb
(11) |
Mar
(7) |
Apr
(10) |
May
(47) |
Jun
(31) |
Jul
(31) |
Aug
(13) |
Sep
(54) |
Oct
(52) |
Nov
(79) |
Dec
(208) |
2008 |
Jan
(203) |
Feb
(63) |
Mar
(85) |
Apr
(28) |
May
(77) |
Jun
(36) |
Jul
(84) |
Aug
(26) |
Sep
(38) |
Oct
(21) |
Nov
(7) |
Dec
(27) |
2009 |
Jan
(34) |
Feb
(22) |
Mar
(31) |
Apr
(12) |
May
(15) |
Jun
(20) |
Jul
(40) |
Aug
(18) |
Sep
(10) |
Oct
(9) |
Nov
(6) |
Dec
(29) |
2010 |
Jan
(3) |
Feb
(12) |
Mar
(13) |
Apr
(10) |
May
(8) |
Jun
|
Jul
(2) |
Aug
|
Sep
(10) |
Oct
(35) |
Nov
(1) |
Dec
(8) |
2011 |
Jan
(13) |
Feb
(16) |
Mar
(15) |
Apr
(9) |
May
(4) |
Jun
(11) |
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
(4) |
Dec
(7) |
2012 |
Jan
(5) |
Feb
(1) |
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(7) |
Dec
|
From: Gustavo <ghr...@gm...> - 2022-11-24 23:52:22
|
Hi guys My name is Gustavo, I am working with the SynCE sources of trunk (rev 4335) to make binaries for the current Debian stable. In the task of creating libera binaries, I ran into a dependency problem. Script: ##### TMP_DIR="$(mktemp -d "/tmp/$(basename "$0")_XXXXXX")" || exit 1 LIB_RRA_PATH="${TMP_DIR}/synce-librra" # Download sources from SourceForge svn export "https://svn.code.sf.net/p/synce/code/trunk/librra" "${LIB_RRA_PATH}" || exit 1 cd "${LIB_RRA_PATH}" || exit 1 # Build sourcecode with non-root user export PATH="$PATH:/sbin" export CFLAGS="-O2" ./autogen.sh --prefix=/usr --localstatedir=/var || exit 1 make clean || exit 1 make || exit 1 echo "build successful" ##### Output: checking for libsynce >= 0.17... yes checking for mdir_parse in -lmimedir... no configure: error: Can't find libmimedir ( http://sourceforge.net/projects/libmimedir/) However, to meet the librra requirement, I had previously installed libmimedir from SynCE PPA on my Debian Bullseye. $ dpkg -l | grep mimedir ii libmimedir0 0.5.1-4ubuntu3~ppa1~xenial2 i386 Library to parse RFC 2425 Directory Information block Can someone explain to me why it doesn't recognize the installed library? Thanks in advance !!! [image: Gustavo Perez Reyes] |
From: Gustavo <ghr...@gm...> - 2022-11-24 22:43:56
|
Really, I don't understand... $ ls -l /tmp/synce-core-sh_m2cCFq/synce-core/python/.libs/ -rw-r--r-- 1 admin admin 268204 nov 24 12:31 pyrapi2.a lrwxrwxrwx 1 admin admin 13 nov 24 12:31 pyrapi2.la -> ../pyrapi2.la -rw-r--r-- 1 admin admin 1010 nov 24 12:31 pyrapi2.lai -rw-r--r-- 1 admin admin 267912 nov 24 12:31 pyrapi2_la-pyrapi2.o -rwxr-xr-x 1 admin admin 233412 nov 24 12:31 pyrapi2.so -rwxr-xr-x 1 root root 233412 nov 24 18:55 *pyrapi2.soT* File exists !!! El jue, 24 nov 2022 a la(s) 19:17, Gustavo (ghr...@gm...) escribió: > > Hi Arnd > > When running synce-core "make install" I get the following error > > make[2]: se entra en el directorio '/tmp/synce-core/python' > make[3]: se entra en el directorio '/tmp/synce-core/python' > make[3]: No se hace nada para 'install-exec-am'. > /usr/bin/mkdir -p '/usr/lib/python2.7/dist-packages' > /bin/bash ../libtool --mode=install /usr/bin/install -c pyrapi2.la > '/usr/lib/python2.7/dist-packages' > libtool: *warning*: *relinking 'pyrapi2.la <http://pyrapi2.la>*' > libtool: install: (cd /tmp/synce-core-sh_m2cCFq/synce-core/python; > /bin/bash "/tmp/synce-core-sh_m2cCFq/synce-core/libtool" --tag CC > --mode=relink gcc -I/usr/include/python2.7 -I../lib/utils -I../lib/utils > -I../lib/rapi -pthread -Wall -Wsign-compare -Wno-long-long -O2 -module > -avoid-version -fPIC -o pyrapi2.la -rpath > /usr/lib/python2.7/dist-packages pyrapi2_la-pyrapi2.lo ../lib/libsynce.la > -lm ) > > libtool: relink: gcc -shared -fPIC -DPIC .libs/pyrapi2_la-pyrapi2.o > -L/usr/lib -lsynce -lm -pthread -O2 -pthread -Wl,-soname -Wl,pyrapi2.so > -o .libs/pyrapi2.so > libtool: install: /usr/bin/install -c .libs/pyrapi2.soT > /usr/lib/python2.7/dist-packages/pyrapi2.so > */usr/bin/install: cannot stat '.libs/pyrapi2.soT': No such file or > directory* > make[3]: *** [Makefile:465: install-rapibindingsLTLIBRARIES] Error 1 > make[3]: se sale del directorio '/tmp/synce-core/python' > make[2]: *** [Makefile:720: install-am] Error 2 > make[2]: se sale del directorio '/tmp/synce-core/python' > make[1]: *** [Makefile:556: install-recursive] Error 1 > make[1]: se sale del directorio '/tmp/synce-core/python' > make: *** [Makefile:510: install-recursive] Error 1 > > > El jue, 3 nov 2022 a la(s) 20:05, Arndt Kaiser (ar...@gm...) escribió: > >> Hello Gustavo, >> >> it sounds like you are using very old sources or source packages. Many >> things have changed since then. As far as i remember the package with >> the name "python" was removed and replaced by "python2" and "python3" >> during the python3 transition. >> >> When you really are interested in compiling the old sources then the >> dependency "python" of the package should be changed to "python2" >> because the old sources contain scripts for python version 2. >> >> But i strongly recommend to use the newest available version of the core >> package available at www.sourceforge.net. During 2021 I modyfied all >> python scripts to use python3 and a lot of Bugfixing was done to the c >> sourcecode as well. >> >> The drawback is, that currently no build system for debian packages >> exists in the repository. This is up to you... >> >> To build the binary files, you can use something like this in a bash >> script: >> >> ##### >> TMP_DIR="$(mktemp -d "/tmp/$(basename "$0")_XXXXXX")" || exit 1 >> SYNCE_CORE_PATH="${TMP_DIR}/synce-core" >> >> # Download sources from SourceForge >> svn export "https://svn.code.sf.net/p/synce/code/trunk/core" >> "${SYNCE_CORE_PATH}" || exit 1 >> cd "${SYNCE_CORE_PATH}" || exit 1 >> >> # Build sourcecode with non-root user >> export PATH="$PATH:/sbin" >> export CFLAGS="-O2" >> ./autogen.sh --prefix=/usr --localstatedir=/var || exit 1 >> make clean || exit 1 >> make || exit 1 >> echo "build successful" >> ##### >> >> The following debian packages (bullseye) should be installed to compile >> the sources: >> libglib2.0-dev libdbus-1-dev libgudev-1.0-dev autoconf automake libtool >> make g++ >> >> >> Hope this helps. >> >> >> Cheers, Arndt >> >> >> >> Am 03.11.22 um 22:16 schrieb Gustavo: >> > >> > Good afternoon guys >> > >> > My name is Gustavo, I am working with the Synce PPA sources to make a >> > DEB version for the current Debian stable */"Bullseye"/*. I am not a >> > developer, my specialty is system administration. In the past I've been >> > encouraged to make minor changes to Synce's Python source to adapt it to >> > my needs (in Ubuntu 8.04 Hardy). Today, making an updated version for >> > Debian is a major challenge for me. I am focused on five packages: >> > /*libmimedir*/, */librra/*, */librtfcomp /*libraries along with >> > */synce-core/* and */synce-sync-engine/*. >> > >> > For this purpose, I am using this post as a guide: >> > >> https://www.linuxquestions.org/questions/linux-software-2/connection-linux-pda-windowsce-4175560071/#post5465293 >> < >> https://www.linuxquestions.org/questions/linux-software-2/connection-linux-pda-windowsce-4175560071/#post5465293 >> > >> > I prepared the build system with pbuilder, and the result was something >> > strange, unexpected. >> > At the end of the operation, the output indicates that there are >> > unsatisfied dependencies, but these packages are installed in the same >> > or higher version >> > >> > $ sudo /usr/sbin/pbuilder build >> > synce-sync-engine_0.16-0.1~0debian0~bullseye1.dsc >> > (...) >> > dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper (>= 5) >> > python-setuptools python (>= 2.6.6-3) >> > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; >> > aborting >> > >> > But, APT says otherwise... >> > >> > # apt show debhelper >> > Package: debhelper >> > Version: 13.3.4 >> > >> > # apt show python-setuptools >> > Package: python-setuptools >> > Version: 44.1.1-1 >> > >> > # apt show python >> > Package: python >> > State: not a real (virtual) package >> > N: Cannot select the candidate version of the python package since it >> > has no candidates >> > N: Different versions of the "python" package cannot be selected because >> > it is purely virtual >> > N: No package found >> > >> > $ sudo /usr/sbin/pbuilder build >> synce-core_0.17-0.1~0debian0~bullseye1.dsc >> > (...) >> > dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper (>= 5) >> > libglib2.0-dev (>= 2.26.0) python (>> 2.6.6) python-all-dev (>> 2.6.6) >> > python-pyrex (>= 0.9.6) quilt ppp libgudev-1.0-dev udev >> > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; >> > aborting >> > >> > But... >> > >> > # apt show debhelper >> > Package: debhelper >> > Version: 13.3.4 >> > >> > # apt show libglib2.0-dev >> > Package: libglib2.0-dev >> > Version: 2.66.8-1 >> > >> > # apt show python >> > Package: python >> > State: not a real (virtual) package >> > N: Cannot select the candidate version of the python package since it >> > has no candidates >> > N: Different versions of the "python" package cannot be selected because >> > it is purely virtual >> > N: No package found >> > >> > # apt show python-all-dev >> > Package: python-all-dev >> > Version: 2.7.18-3 >> > >> > # apt show python-pyrex (NOT in Bullseye, download from Debian Buster >> > repository) >> > Package: python-pyrex >> > Version: 0.9.9-1 >> > >> > # apt show quilt >> > Package: quilt >> > Version: 0.66-2.1 >> > >> > # apt show ppp >> > Package: ppp >> > Version: 2.4.9-1+1 >> > >> > # apt show libgudev-1.0-dev >> > Package: libgudev-1.0-dev >> > Version: 234-1 >> > >> > # apt show udev >> > Package: udev >> > Version: 247.3-7+deb11u1 >> > >> > Taking a look at the version of Python installed... >> > >> > # apt list --installed | grep ^python | grep stable | cut -d "/" -f 1 >> > python-all-dev >> > python-all >> > python-apt-common >> > python-dev-is-python2 >> > python-is-python2 >> > python-pkg-resources >> > python-setuptools >> > python2-dev >> > python2-minimal >> > python2.7-dev >> > python2.7-minimal >> > python2.7 >> > python2 >> > python3-apt >> > python3-brlapi >> > python3-cairo >> > python3-certifi >> > python3-chardet >> > python3-cups >> > python3-cupshelpers >> > python3-dbus >> > python3-debian >> > python3-distro-info >> > python3-distro >> > python3-distutils >> > python3-gi-cairo >> > python3-gi >> > python3-gpg >> > python3-ibus-1.0 >> > python3-idna >> > python3-ldb >> > python3-lib2to3 >> > python3-libvoikko >> > python3-louis >> > python3-magic >> > python3-mako >> > python3-markupsafe >> > python3-minimal >> > python3-numpy >> > python3-pkg-resources >> > python3-pyatspi >> > python3-pycurl >> > python3-pyside2.qtcore >> > python3-pyside2.qtgui >> > python3-pyside2.qtwidgets >> > python3-requests >> > python3-six >> > python3-smbc >> > python3-software-properties >> > python3-speechd >> > python3-talloc >> > python3-unidiff >> > python3-uno >> > python3-urllib3 >> > python3-xdg >> > python3.9-minimal >> > python3.9 >> > python3 >> > >> > /*Any help will be very welcome!!!*/ >> > /* >> > */ >> > Best regards to all >> > >> > >> > _______________________________________________ >> > SynCE-Devel mailing list >> > Syn...@li... >> > https://lists.sourceforge.net/lists/listinfo/synce-devel >> > |
From: Gustavo <ghr...@gm...> - 2022-11-24 22:17:50
|
Hi Arnd When running synce-core "make install" I get the following error make[2]: se entra en el directorio '/tmp/synce-core/python' make[3]: se entra en el directorio '/tmp/synce-core/python' make[3]: No se hace nada para 'install-exec-am'. /usr/bin/mkdir -p '/usr/lib/python2.7/dist-packages' /bin/bash ../libtool --mode=install /usr/bin/install -c pyrapi2.la '/usr/lib/python2.7/dist-packages' libtool: *warning*: *relinking 'pyrapi2.la <http://pyrapi2.la>*' libtool: install: (cd /tmp/synce-core-sh_m2cCFq/synce-core/python; /bin/bash "/tmp/synce-core-sh_m2cCFq/synce-core/libtool" --tag CC --mode=relink gcc -I/usr/include/python2.7 -I../lib/utils -I../lib/utils -I../lib/rapi -pthread -Wall -Wsign-compare -Wno-long-long -O2 -module -avoid-version -fPIC -o pyrapi2.la -rpath /usr/lib/python2.7/dist-packages pyrapi2_la-pyrapi2.lo ../lib/libsynce.la -lm ) libtool: relink: gcc -shared -fPIC -DPIC .libs/pyrapi2_la-pyrapi2.o -L/usr/lib -lsynce -lm -pthread -O2 -pthread -Wl,-soname -Wl,pyrapi2.so -o .libs/pyrapi2.so libtool: install: /usr/bin/install -c .libs/pyrapi2.soT /usr/lib/python2.7/dist-packages/pyrapi2.so */usr/bin/install: cannot stat '.libs/pyrapi2.soT': No such file or directory* make[3]: *** [Makefile:465: install-rapibindingsLTLIBRARIES] Error 1 make[3]: se sale del directorio '/tmp/synce-core/python' make[2]: *** [Makefile:720: install-am] Error 2 make[2]: se sale del directorio '/tmp/synce-core/python' make[1]: *** [Makefile:556: install-recursive] Error 1 make[1]: se sale del directorio '/tmp/synce-core/python' make: *** [Makefile:510: install-recursive] Error 1 El jue, 3 nov 2022 a la(s) 20:05, Arndt Kaiser (ar...@gm...) escribió: > Hello Gustavo, > > it sounds like you are using very old sources or source packages. Many > things have changed since then. As far as i remember the package with > the name "python" was removed and replaced by "python2" and "python3" > during the python3 transition. > > When you really are interested in compiling the old sources then the > dependency "python" of the package should be changed to "python2" > because the old sources contain scripts for python version 2. > > But i strongly recommend to use the newest available version of the core > package available at www.sourceforge.net. During 2021 I modyfied all > python scripts to use python3 and a lot of Bugfixing was done to the c > sourcecode as well. > > The drawback is, that currently no build system for debian packages > exists in the repository. This is up to you... > > To build the binary files, you can use something like this in a bash > script: > > ##### > TMP_DIR="$(mktemp -d "/tmp/$(basename "$0")_XXXXXX")" || exit 1 > SYNCE_CORE_PATH="${TMP_DIR}/synce-core" > > # Download sources from SourceForge > svn export "https://svn.code.sf.net/p/synce/code/trunk/core" > "${SYNCE_CORE_PATH}" || exit 1 > cd "${SYNCE_CORE_PATH}" || exit 1 > > # Build sourcecode with non-root user > export PATH="$PATH:/sbin" > export CFLAGS="-O2" > ./autogen.sh --prefix=/usr --localstatedir=/var || exit 1 > make clean || exit 1 > make || exit 1 > echo "build successful" > ##### > > The following debian packages (bullseye) should be installed to compile > the sources: > libglib2.0-dev libdbus-1-dev libgudev-1.0-dev autoconf automake libtool > make g++ > > > Hope this helps. > > > Cheers, Arndt > > > > Am 03.11.22 um 22:16 schrieb Gustavo: > > > > Good afternoon guys > > > > My name is Gustavo, I am working with the Synce PPA sources to make a > > DEB version for the current Debian stable */"Bullseye"/*. I am not a > > developer, my specialty is system administration. In the past I've been > > encouraged to make minor changes to Synce's Python source to adapt it to > > my needs (in Ubuntu 8.04 Hardy). Today, making an updated version for > > Debian is a major challenge for me. I am focused on five packages: > > /*libmimedir*/, */librra/*, */librtfcomp /*libraries along with > > */synce-core/* and */synce-sync-engine/*. > > > > For this purpose, I am using this post as a guide: > > > https://www.linuxquestions.org/questions/linux-software-2/connection-linux-pda-windowsce-4175560071/#post5465293 > < > https://www.linuxquestions.org/questions/linux-software-2/connection-linux-pda-windowsce-4175560071/#post5465293 > > > > I prepared the build system with pbuilder, and the result was something > > strange, unexpected. > > At the end of the operation, the output indicates that there are > > unsatisfied dependencies, but these packages are installed in the same > > or higher version > > > > $ sudo /usr/sbin/pbuilder build > > synce-sync-engine_0.16-0.1~0debian0~bullseye1.dsc > > (...) > > dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper (>= 5) > > python-setuptools python (>= 2.6.6-3) > > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; > > aborting > > > > But, APT says otherwise... > > > > # apt show debhelper > > Package: debhelper > > Version: 13.3.4 > > > > # apt show python-setuptools > > Package: python-setuptools > > Version: 44.1.1-1 > > > > # apt show python > > Package: python > > State: not a real (virtual) package > > N: Cannot select the candidate version of the python package since it > > has no candidates > > N: Different versions of the "python" package cannot be selected because > > it is purely virtual > > N: No package found > > > > $ sudo /usr/sbin/pbuilder build > synce-core_0.17-0.1~0debian0~bullseye1.dsc > > (...) > > dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper (>= 5) > > libglib2.0-dev (>= 2.26.0) python (>> 2.6.6) python-all-dev (>> 2.6.6) > > python-pyrex (>= 0.9.6) quilt ppp libgudev-1.0-dev udev > > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; > > aborting > > > > But... > > > > # apt show debhelper > > Package: debhelper > > Version: 13.3.4 > > > > # apt show libglib2.0-dev > > Package: libglib2.0-dev > > Version: 2.66.8-1 > > > > # apt show python > > Package: python > > State: not a real (virtual) package > > N: Cannot select the candidate version of the python package since it > > has no candidates > > N: Different versions of the "python" package cannot be selected because > > it is purely virtual > > N: No package found > > > > # apt show python-all-dev > > Package: python-all-dev > > Version: 2.7.18-3 > > > > # apt show python-pyrex (NOT in Bullseye, download from Debian Buster > > repository) > > Package: python-pyrex > > Version: 0.9.9-1 > > > > # apt show quilt > > Package: quilt > > Version: 0.66-2.1 > > > > # apt show ppp > > Package: ppp > > Version: 2.4.9-1+1 > > > > # apt show libgudev-1.0-dev > > Package: libgudev-1.0-dev > > Version: 234-1 > > > > # apt show udev > > Package: udev > > Version: 247.3-7+deb11u1 > > > > Taking a look at the version of Python installed... > > > > # apt list --installed | grep ^python | grep stable | cut -d "/" -f 1 > > python-all-dev > > python-all > > python-apt-common > > python-dev-is-python2 > > python-is-python2 > > python-pkg-resources > > python-setuptools > > python2-dev > > python2-minimal > > python2.7-dev > > python2.7-minimal > > python2.7 > > python2 > > python3-apt > > python3-brlapi > > python3-cairo > > python3-certifi > > python3-chardet > > python3-cups > > python3-cupshelpers > > python3-dbus > > python3-debian > > python3-distro-info > > python3-distro > > python3-distutils > > python3-gi-cairo > > python3-gi > > python3-gpg > > python3-ibus-1.0 > > python3-idna > > python3-ldb > > python3-lib2to3 > > python3-libvoikko > > python3-louis > > python3-magic > > python3-mako > > python3-markupsafe > > python3-minimal > > python3-numpy > > python3-pkg-resources > > python3-pyatspi > > python3-pycurl > > python3-pyside2.qtcore > > python3-pyside2.qtgui > > python3-pyside2.qtwidgets > > python3-requests > > python3-six > > python3-smbc > > python3-software-properties > > python3-speechd > > python3-talloc > > python3-unidiff > > python3-uno > > python3-urllib3 > > python3-xdg > > python3.9-minimal > > python3.9 > > python3 > > > > /*Any help will be very welcome!!!*/ > > /* > > */ > > Best regards to all > > > > > > _______________________________________________ > > SynCE-Devel mailing list > > Syn...@li... > > https://lists.sourceforge.net/lists/listinfo/synce-devel > |
From: Gustavo <ghr...@gm...> - 2022-11-24 17:26:30
|
Hi Arndt !!! Hi all guys from the SynCE Community !!! I build the binary files with your bash script. What would be the next step ? As I said, my area is not package development, I am sysadmin. Should I perform the same steps with librra, librtfcomp and pywbxml? In /trunk, the library libmimedir is not found, no longer needed? I want to test the binaries with MC3000 series with WM https://www.zebra.com/us/en/products/mobile-computers/handheld/mc3200.html Any help will be greatly appreciated El vie, 4 nov 2022 a la(s) 10:40, Gustavo (ghr...@gm...) escribió: > > Hi Arndt > > Thanks for the tip regarding the newest sources available. > > I want to build the following packages: libmimedir, librra, librtfcomp, > synce-core and synce-sync-engine. > I understand that they are the minimum packages necessary for a connection > with the devices. > In /trunk, the library libmimedir is not found, no longer needed? > I also don't see the sources to build the synce-core-engine binary, there > is a sync-engine folder but it doesn't seem complete, no Makefile, > autogen.sh, etc. > > Another question, after executing the script (with autogen and make), I'm > already in a position to add Debian specific modifications under the debian > directory, and create the set of input files used for Debian package > building in quilt format? > > As I said, my area is not package development but I am interested in > learning. I have many questions, sorry if they may seem trivial. > > Thanks in advance > > El jue, 3 nov 2022 a la(s) 20:05, Arndt Kaiser (ar...@gm...) escribió: > >> Hello Gustavo, >> >> I strongly recommend to use the newest available version of the core >> package available at www.sourceforge.net. During 2021 I modyfied all >> python scripts to use python3 and a lot of Bugfixing was done to the c >> sourcecode as well. >> >> The drawback is, that currently no build system for debian packages >> exists in the repository. This is up to you... >> >> To build the binary files, you can use something like this in a bash >> script: >> >> ##### >> TMP_DIR="$(mktemp -d "/tmp/$(basename "$0")_XXXXXX")" || exit 1 >> SYNCE_CORE_PATH="${TMP_DIR}/synce-core" >> >> # Download sources from SourceForge >> svn export "https://svn.code.sf.net/p/synce/code/trunk/core" >> "${SYNCE_CORE_PATH}" || exit 1 >> cd "${SYNCE_CORE_PATH}" || exit 1 >> >> # Build sourcecode with non-root user >> export PATH="$PATH:/sbin" >> export CFLAGS="-O2" >> ./autogen.sh --prefix=/usr --localstatedir=/var || exit 1 >> make clean || exit 1 >> make || exit 1 >> echo "build successful" >> ##### >> >> The following debian packages (bullseye) should be installed to compile >> the sources: >> libglib2.0-dev libdbus-1-dev libgudev-1.0-dev autoconf automake libtool >> make g++ >> >> >> Hope this helps. >> >> >> Cheers, Arndt >> >> >> |
From: Gustavo <ghr...@gm...> - 2022-11-04 13:41:03
|
Hi Arndt First things first, thank you very much for your prompt response. I had seen sources at https://sourceforge.net/projects/synce/files/ dated from May 2012, very old. And the most recent ones at https://launchpad.net/~synce/+archive/ubuntu/ppa/ with packages for Ubuntu Xenial dated between August and October 2016. I saw that they even take into account the change in the DHCP client, among others. That's why I took it. Thanks for the tip regarding the newest sources available. I'm having a hard time understanding the organization of the many folders and sources in /trunk I want to build the following packages: libmimedir, librra, librtfcomp, synce-core and synce-sync-engine. I understand that they are the minimum packages necessary for a connection with the devices. In /trunk, the library libmimedir is not found, no longer needed? I also don't see the sources to build the synce-core-engine binary, there is a sync-engine folder but it doesn't seem complete, no Makefile, autogen.sh, etc. Another question, after executing the script (with autogen and make), I'm already in a position to add Debian specific modifications under the debian directory, and create the set of input files used for Debian package building in quilt format? As I said, my area is not package development but I am interested in learning. I have many questions, sorry if they may seem trivial. Thanks in advance El jue, 3 nov 2022 a la(s) 20:05, Arndt Kaiser (ar...@gm...) escribió: > Hello Gustavo, > > it sounds like you are using very old sources or source packages. Many > things have changed since then. As far as i remember the package with > the name "python" was removed and replaced by "python2" and "python3" > during the python3 transition. > > When you really are interested in compiling the old sources then the > dependency "python" of the package should be changed to "python2" > because the old sources contain scripts for python version 2. > > But i strongly recommend to use the newest available version of the core > package available at www.sourceforge.net. During 2021 I modyfied all > python scripts to use python3 and a lot of Bugfixing was done to the c > sourcecode as well. > > The drawback is, that currently no build system for debian packages > exists in the repository. This is up to you... > > To build the binary files, you can use something like this in a bash > script: > > ##### > TMP_DIR="$(mktemp -d "/tmp/$(basename "$0")_XXXXXX")" || exit 1 > SYNCE_CORE_PATH="${TMP_DIR}/synce-core" > > # Download sources from SourceForge > svn export "https://svn.code.sf.net/p/synce/code/trunk/core" > "${SYNCE_CORE_PATH}" || exit 1 > cd "${SYNCE_CORE_PATH}" || exit 1 > > # Build sourcecode with non-root user > export PATH="$PATH:/sbin" > export CFLAGS="-O2" > ./autogen.sh --prefix=/usr --localstatedir=/var || exit 1 > make clean || exit 1 > make || exit 1 > echo "build successful" > ##### > > The following debian packages (bullseye) should be installed to compile > the sources: > libglib2.0-dev libdbus-1-dev libgudev-1.0-dev autoconf automake libtool > make g++ > > > Hope this helps. > > > Cheers, Arndt > > > |
From: Arndt K. <ar...@gm...> - 2022-11-03 23:05:11
|
Hello Gustavo, it sounds like you are using very old sources or source packages. Many things have changed since then. As far as i remember the package with the name "python" was removed and replaced by "python2" and "python3" during the python3 transition. When you really are interested in compiling the old sources then the dependency "python" of the package should be changed to "python2" because the old sources contain scripts for python version 2. But i strongly recommend to use the newest available version of the core package available at www.sourceforge.net. During 2021 I modyfied all python scripts to use python3 and a lot of Bugfixing was done to the c sourcecode as well. The drawback is, that currently no build system for debian packages exists in the repository. This is up to you... To build the binary files, you can use something like this in a bash script: ##### TMP_DIR="$(mktemp -d "/tmp/$(basename "$0")_XXXXXX")" || exit 1 SYNCE_CORE_PATH="${TMP_DIR}/synce-core" # Download sources from SourceForge svn export "https://svn.code.sf.net/p/synce/code/trunk/core" "${SYNCE_CORE_PATH}" || exit 1 cd "${SYNCE_CORE_PATH}" || exit 1 # Build sourcecode with non-root user export PATH="$PATH:/sbin" export CFLAGS="-O2" ./autogen.sh --prefix=/usr --localstatedir=/var || exit 1 make clean || exit 1 make || exit 1 echo "build successful" ##### The following debian packages (bullseye) should be installed to compile the sources: libglib2.0-dev libdbus-1-dev libgudev-1.0-dev autoconf automake libtool make g++ Hope this helps. Cheers, Arndt Am 03.11.22 um 22:16 schrieb Gustavo: > > Good afternoon guys > > My name is Gustavo, I am working with the Synce PPA sources to make a > DEB version for the current Debian stable */"Bullseye"/*. I am not a > developer, my specialty is system administration. In the past I've been > encouraged to make minor changes to Synce's Python source to adapt it to > my needs (in Ubuntu 8.04 Hardy). Today, making an updated version for > Debian is a major challenge for me. I am focused on five packages: > /*libmimedir*/, */librra/*, */librtfcomp /*libraries along with > */synce-core/* and */synce-sync-engine/*. > > For this purpose, I am using this post as a guide: > https://www.linuxquestions.org/questions/linux-software-2/connection-linux-pda-windowsce-4175560071/#post5465293 <https://www.linuxquestions.org/questions/linux-software-2/connection-linux-pda-windowsce-4175560071/#post5465293> > I prepared the build system with pbuilder, and the result was something > strange, unexpected. > At the end of the operation, the output indicates that there are > unsatisfied dependencies, but these packages are installed in the same > or higher version > > $ sudo /usr/sbin/pbuilder build > synce-sync-engine_0.16-0.1~0debian0~bullseye1.dsc > (...) > dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper (>= 5) > python-setuptools python (>= 2.6.6-3) > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; > aborting > > But, APT says otherwise... > > # apt show debhelper > Package: debhelper > Version: 13.3.4 > > # apt show python-setuptools > Package: python-setuptools > Version: 44.1.1-1 > > # apt show python > Package: python > State: not a real (virtual) package > N: Cannot select the candidate version of the python package since it > has no candidates > N: Different versions of the "python" package cannot be selected because > it is purely virtual > N: No package found > > $ sudo /usr/sbin/pbuilder build synce-core_0.17-0.1~0debian0~bullseye1.dsc > (...) > dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper (>= 5) > libglib2.0-dev (>= 2.26.0) python (>> 2.6.6) python-all-dev (>> 2.6.6) > python-pyrex (>= 0.9.6) quilt ppp libgudev-1.0-dev udev > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; > aborting > > But... > > # apt show debhelper > Package: debhelper > Version: 13.3.4 > > # apt show libglib2.0-dev > Package: libglib2.0-dev > Version: 2.66.8-1 > > # apt show python > Package: python > State: not a real (virtual) package > N: Cannot select the candidate version of the python package since it > has no candidates > N: Different versions of the "python" package cannot be selected because > it is purely virtual > N: No package found > > # apt show python-all-dev > Package: python-all-dev > Version: 2.7.18-3 > > # apt show python-pyrex (NOT in Bullseye, download from Debian Buster > repository) > Package: python-pyrex > Version: 0.9.9-1 > > # apt show quilt > Package: quilt > Version: 0.66-2.1 > > # apt show ppp > Package: ppp > Version: 2.4.9-1+1 > > # apt show libgudev-1.0-dev > Package: libgudev-1.0-dev > Version: 234-1 > > # apt show udev > Package: udev > Version: 247.3-7+deb11u1 > > Taking a look at the version of Python installed... > > # apt list --installed | grep ^python | grep stable | cut -d "/" -f 1 > python-all-dev > python-all > python-apt-common > python-dev-is-python2 > python-is-python2 > python-pkg-resources > python-setuptools > python2-dev > python2-minimal > python2.7-dev > python2.7-minimal > python2.7 > python2 > python3-apt > python3-brlapi > python3-cairo > python3-certifi > python3-chardet > python3-cups > python3-cupshelpers > python3-dbus > python3-debian > python3-distro-info > python3-distro > python3-distutils > python3-gi-cairo > python3-gi > python3-gpg > python3-ibus-1.0 > python3-idna > python3-ldb > python3-lib2to3 > python3-libvoikko > python3-louis > python3-magic > python3-mako > python3-markupsafe > python3-minimal > python3-numpy > python3-pkg-resources > python3-pyatspi > python3-pycurl > python3-pyside2.qtcore > python3-pyside2.qtgui > python3-pyside2.qtwidgets > python3-requests > python3-six > python3-smbc > python3-software-properties > python3-speechd > python3-talloc > python3-unidiff > python3-uno > python3-urllib3 > python3-xdg > python3.9-minimal > python3.9 > python3 > > /*Any help will be very welcome!!!*/ > /* > */ > Best regards to all > > > _______________________________________________ > SynCE-Devel mailing list > Syn...@li... > https://lists.sourceforge.net/lists/listinfo/synce-devel |
From: Gustavo <ghr...@gm...> - 2022-11-03 21:17:22
|
Good afternoon guys My name is Gustavo, I am working with the Synce PPA sources to make a DEB version for the current Debian stable *"Bullseye"*. I am not a developer, my specialty is system administration. In the past I've been encouraged to make minor changes to Synce's Python source to adapt it to my needs (in Ubuntu 8.04 Hardy). Today, making an updated version for Debian is a major challenge for me. I am focused on five packages: *libmimedir*, *librra*, *librtfcomp *libraries along with *synce-core* and *synce-sync-engine*. For this purpose, I am using this post as a guide: https://www.linuxquestions.org/questions/linux-software-2/connection-linux-pda-windowsce-4175560071/#post5465293 I prepared the build system with pbuilder, and the result was something strange, unexpected. At the end of the operation, the output indicates that there are unsatisfied dependencies, but these packages are installed in the same or higher version $ sudo /usr/sbin/pbuilder build synce-sync-engine_0.16-0.1~0debian0~bullseye1.dsc (...) dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper (>= 5) python-setuptools python (>= 2.6.6-3) dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting But, APT says otherwise... # apt show debhelper Package: debhelper Version: 13.3.4 # apt show python-setuptools Package: python-setuptools Version: 44.1.1-1 # apt show python Package: python State: not a real (virtual) package N: Cannot select the candidate version of the python package since it has no candidates N: Different versions of the "python" package cannot be selected because it is purely virtual N: No package found $ sudo /usr/sbin/pbuilder build synce-core_0.17-0.1~0debian0~bullseye1.dsc (...) dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper (>= 5) libglib2.0-dev (>= 2.26.0) python (>> 2.6.6) python-all-dev (>> 2.6.6) python-pyrex (>= 0.9.6) quilt ppp libgudev-1.0-dev udev dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting But... # apt show debhelper Package: debhelper Version: 13.3.4 # apt show libglib2.0-dev Package: libglib2.0-dev Version: 2.66.8-1 # apt show python Package: python State: not a real (virtual) package N: Cannot select the candidate version of the python package since it has no candidates N: Different versions of the "python" package cannot be selected because it is purely virtual N: No package found # apt show python-all-dev Package: python-all-dev Version: 2.7.18-3 # apt show python-pyrex (NOT in Bullseye, download from Debian Buster repository) Package: python-pyrex Version: 0.9.9-1 # apt show quilt Package: quilt Version: 0.66-2.1 # apt show ppp Package: ppp Version: 2.4.9-1+1 # apt show libgudev-1.0-dev Package: libgudev-1.0-dev Version: 234-1 # apt show udev Package: udev Version: 247.3-7+deb11u1 Taking a look at the version of Python installed... # apt list --installed | grep ^python | grep stable | cut -d "/" -f 1 python-all-dev python-all python-apt-common python-dev-is-python2 python-is-python2 python-pkg-resources python-setuptools python2-dev python2-minimal python2.7-dev python2.7-minimal python2.7 python2 python3-apt python3-brlapi python3-cairo python3-certifi python3-chardet python3-cups python3-cupshelpers python3-dbus python3-debian python3-distro-info python3-distro python3-distutils python3-gi-cairo python3-gi python3-gpg python3-ibus-1.0 python3-idna python3-ldb python3-lib2to3 python3-libvoikko python3-louis python3-magic python3-mako python3-markupsafe python3-minimal python3-numpy python3-pkg-resources python3-pyatspi python3-pycurl python3-pyside2.qtcore python3-pyside2.qtgui python3-pyside2.qtwidgets python3-requests python3-six python3-smbc python3-software-properties python3-speechd python3-talloc python3-unidiff python3-uno python3-urllib3 python3-xdg python3.9-minimal python3.9 python3 *Any help will be very welcome!!!* Best regards to all |
From: Launchpad B. S. <no...@la...> - 2016-10-02 19:01:21
|
* Source Package: libmimedir * Version: 0.5.1-4ubuntu3~ppa1~xenial1 * Architecture: amd64 * Archive: ~synce/ubuntu/ppa * Component: main * State: Failed to build * Duration: 2 minutes * Build Log: https://launchpad.net/~synce/+archive/ubuntu/ppa/+build/10981495/+files/buildlog_ubuntu-xenial-amd64.libmimedir_0.5.1-4ubuntu3~ppa1~xenial1_BUILDING.txt.gz * Builder: https://launchpad.net/builders/lgw01-03 * Source: not available If you want further information about this situation, feel free to contact a member of the Launchpad Buildd Administrators team. -- amd64 build of libmimedir 0.5.1-4ubuntu3~ppa1~xenial1 in ubuntu xenial RELEASE https://launchpad.net/~synce/+archive/ubuntu/ppa/+build/10981495 You are receiving this email because your team SynCE is the owner of this archive. |
From: Launchpad B. S. <no...@la...> - 2016-10-02 19:01:21
|
* Source Package: libmimedir * Version: 0.5.1-4ubuntu3~ppa1~xenial1 * Architecture: i386 * Archive: ~synce/ubuntu/ppa * Component: main * State: Failed to build * Duration: 2 minutes * Build Log: https://launchpad.net/~synce/+archive/ubuntu/ppa/+build/10981496/+files/buildlog_ubuntu-xenial-i386.libmimedir_0.5.1-4ubuntu3~ppa1~xenial1_BUILDING.txt.gz * Builder: https://launchpad.net/builders/lgw01-43 * Source: not available If you want further information about this situation, feel free to contact a member of the Launchpad Buildd Administrators team. -- i386 build of libmimedir 0.5.1-4ubuntu3~ppa1~xenial1 in ubuntu xenial RELEASE https://launchpad.net/~synce/+archive/ubuntu/ppa/+build/10981496 You are receiving this email because your team SynCE is the owner of this archive. |
From: Launchpad B. S. <no...@la...> - 2014-04-19 16:12:28
|
* Source Package: synce-core * Version: 0.17-0ubuntu0~ppa1~trusty2 * Architecture: i386 * Archive: synce PPA * Component: main * State: Failed to build * Duration: 2 minutes * Build Log: https://launchpad.net/~synce/+archive/ppa/+build/5920916/+files/buildlog_ubuntu-trusty-i386.synce-core_0.17-0ubuntu0%7Eppa1%7Etrusty2_FAILEDTOBUILD.txt.gz * Builder: https://launchpad.net/builders/wani08 * Source: not available If you want further information about this situation, feel free to contact a member of the Launchpad Buildd Administrators team. -- i386 build of synce-core 0.17-0ubuntu0~ppa1~trusty2 in ubuntu trusty RELEASE https://launchpad.net/~synce/+archive/ppa/+build/5920916 |
From: Launchpad B. S. <no...@la...> - 2013-07-28 10:10:51
|
* Source Package: synce-gvfs * Version: 0.7-0ubuntu0~ppa1~precise1 * Architecture: amd64 * Archive: synce PPA * Component: main * State: Failed to build * Duration: 9 minutes * Build Log: https://launchpad.net/~synce/+archive/ppa/+build/4832431/+files/buildlog_ubuntu-precise-amd64.synce-gvfs_0.7-0ubuntu0%7Eppa1%7Eprecise1_FAILEDTOBUILD.txt.gz * Builder: https://launchpad.net/builders/alphard * Source: not available If you want further information about this situation, feel free to contact a member of the Launchpad Buildd Administrators team. -- amd64 build of synce-gvfs 0.7-0ubuntu0~ppa1~precise1 in ubuntu precise RELEASE https://launchpad.net/~synce/+archive/ppa/+build/4832431 |
From: Launchpad B. S. <no...@la...> - 2013-07-28 08:57:19
|
* Source Package: synce-gvfs * Version: 0.7-0ubuntu0~ppa1~precise1 * Architecture: i386 * Archive: synce PPA * Component: main * State: Failed to build * Duration: 3 minutes * Build Log: https://launchpad.net/~synce/+archive/ppa/+build/4832432/+files/buildlog_ubuntu-precise-i386.synce-gvfs_0.7-0ubuntu0%7Eppa1%7Eprecise1_FAILEDTOBUILD.txt.gz * Builder: https://launchpad.net/builders/chindi08 * Source: not available If you want further information about this situation, feel free to contact a member of the Launchpad Buildd Administrators team. -- i386 build of synce-gvfs 0.7-0ubuntu0~ppa1~precise1 in ubuntu precise RELEASE https://launchpad.net/~synce/+archive/ppa/+build/4832432 |
From: Launchpad B. S. <no...@la...> - 2012-05-29 08:37:01
|
* Source Package: synce-gvfs * Version: 0.5~20120518-0ubuntu0~ppa1~precise1 * Architecture: i386 * Archive: synce-synce-head PPA * Component: main * State: Failed to build * Duration: 5 minutes * Build Log: https://launchpad.net/~synce/+archive/synce-head/+build/3532407/+files/buildlog_ubuntu-precise-i386.synce-gvfs_0.5%7E20120518-0ubuntu0%7Eppa1%7Eprecise1_FAILEDTOBUILD.txt.gz * Builder: https://launchpad.net/builders/muntries * Source: not available If you want further information about this situation, feel free to contact a member of the Launchpad Buildd Administrators team. -- i386 build of synce-gvfs 0.5~20120518-0ubuntu0~ppa1~precise1 in ubuntu precise RELEASE https://launchpad.net/~synce/+archive/synce-head/+build/3532407 |
From: Kal S. <swo...@gm...> - 2012-04-17 11:17:43
|
Hello again, So it turns out that SuSE 9 does in fact remove /dev/ttyUSB0 when I unplug my Windows CE device, and re-create /dev/ttyUSB0 when I replug the Windows CE device. I just had to be a little patient and wait a few seconds (usually no more than 5 seconds). I have been able to use this fact to reliably detect whether the /dev/ttyUSB0 has been used in a PPP session (by comparing `stat -c %z /dev/ttyUSB0` with `stat -c %y /dev/ttyUSB0`). This way, at least my shell script can instruct the user to unplug and replug the device after having dialed PPP once (because PPP works only once everytime the device is plugged, due to the limitation in Windows CE). Unfortunately I am having trouble with this approach on SuSE 8. /dev/ttyUSB0 does not get automatically removed and re-created when I unplug and replug the Windows CE device. In fact, if I start by manually removing /dev/ttyUSB0, and then plug the Windows CE device, dmesg would tell me that the device has been created and assigned to ttyUSB0, when in fact, /dev/ttyUSB0 has not been automatically created at all. So I cannot use stat -c %z and stat -c %y to check whether ttyUSB0 has been used in a PPP session. Does this appear fixable at all (without changing the kernel or kernel module)? Best Regards, Kal On 5 December 2011 11:57, David Eriksson <tw...@us...>wrote: > I'm quite sure that you only can connect a PPP session once on the ttyUSB > device. This is probably a limitation in Windows CE. > > Best regards, > > David Eriksson > > Skickat från min mobiltelefon. > Den 5 dec 2011 04:35 skrev "Kal Sze" <swo...@gm...>: > > Hi David, >> >> I just tried unloading the ipaq kernel module (by executing `rmmod -v >> ipaq`). It immediately caused the SUSE 9 machine to crash. So I guess >> that's not an option I can use. >> >> Also, I have discovered that with my current approach, even when ttyUSB0 >> remains after I terminate the ppp connection by killing the pppd process, I >> cannot reuse ttyUSB0 until I physically unplug and replug the Windows CE >> device (such that ttyUSB0 device node is removed and remade by the ipaq >> kernel module). Without physically replugging the Windows CE device, the >> next `pppd call script` cannot successfully establish a connection (it will >> output "Connect script failed" after the TIMEOUT specified in the >> /usr/sbin/chat script), even though the previous pppd process has really >> terminated. Maybe I need to use /usr/sbin/chat to properly "hang up" the >> device after the connection is terminated? >> >> Best Regards, >> Kal >> >> On 29 November 2011 15:19, David Eriksson <tw...@us...>wrote: >> >>> Hi, >>> >>> Maybe you can try to unload the USB module and load it again? >>> >>> Cheers, >>> >>> David >>> >>> >>> On Tue, Nov 29, 2011 at 06:10, Kal Sze <swo...@gm...> wrote: >>> >>>> Thanks, Mark, for the reminder about connection stability. So far, I >>>> don't seem to have any issue with that. >>>> >>>> I have another problem, however: >>>> >>>> As I said before, I'm only using pppd to dial a ppp connection to the >>>> Windows CE device. Once I'm done using the ppp connection, my script >>>> terminates the connection by using linux's `kill` command and giving it the >>>> PID of the pppd process. The problem is that *sometimes*, after I kill the >>>> pppd process, ttyUSB0 disappears, even though the Windows CE device is >>>> still physically connected. If I physically disconnect and reconnect the >>>> Windows CE device, linux's ipaq kernel module will re-create ttyUSB0. Would >>>> somebody have an idea why ttyUSB0 disappears and whether I can prevent that >>>> from happening? I would be happy if I could at least put something in my >>>> script to cause the ipaq kernel module to re-create the ttyUSB0 without >>>> requiring me to physically disconnect and reconnect the device. >>>> >>>> Best Regards, >>>> Kal >>>> >>>> On 20 June 2011 04:05, Mark Ellis <ma...@mp...> wrote: >>>> >>>>> On Fri, 2011-06-17 at 14:57 +0200, Kal Sze wrote: >>>>> > On 17 June 2011 19:18, David Eriksson <tw...@us...> >>>>> wrote: >>>>> > > Yes but when you dismiss the error, the connection closes, I think. >>>>> > > >>>>> > > \David >>>>> > >>>>> > Yes, that's my experience as well. But my end users will never see >>>>> > that error box because there will be a full screen application that >>>>> > always stays on top. All is still well. >>>>> > >>>>> > :D >>>>> > >>>>> >>>>> Yes, that error probably occurs because there is no dccm on the other >>>>> end responding to the keep-alive ping. Don't know how stable the link >>>>> will be without a dccm. >>>>> >>>>> Mark >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> EditLive Enterprise is the world's most technically advanced content >>>>> authoring tool. Experience the power of Track Changes, Inline Image >>>>> Editing and ensure content is compliant with Accessibility Checking. >>>>> http://p.sf.net/sfu/ephox-dev2dev >>>>> _______________________________________________ >>>>> SynCE-Devel mailing list >>>>> Syn...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/synce-devel >>>>> >>>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> All the data continuously generated in your IT infrastructure >>>> contains a definitive record of customers, application performance, >>>> security threats, fraudulent activity, and more. Splunk takes this >>>> data and makes sense of it. IT sense. And common sense. >>>> http://p.sf.net/sfu/splunk-novd2d >>>> >>>> _______________________________________________ >>>> SynCE-Devel mailing list >>>> Syn...@li... >>>> https://lists.sourceforge.net/lists/listinfo/synce-devel >>>> >>>> >>> >> |
From: Robert D. <ro...@gm...> - 2012-02-08 04:34:29
|
I fixed bug 3485372 global name 'our_udi' is not defined [1] Then I ran into the dbus rejected send message as did Christian S. [2] so I patched that. Finally, I fixed an infinite loop in get_connected_devices where the device is connected but never gets a client connection. Now I can successfully connect a Trimble Nomad device running Windows Mobile 6 and copy files. (I was a little confused by dccm source code in both connector/ and core/ but I patched in both places) Mark, or someone, could you consider making a release 0.15.3? Or delegate to me and I'll do it. Thanks! 1. https://sourceforge.net/tracker/?func=detail&aid=3485372&group_id=30550&atid=399601 2. https://sourceforge.net/mailarchive/forum.php?thread_name=201112082013.02786.sch%40schlabs.com.ar&forum_name=synce-users -- Robert Dale |
From: David E. <tw...@us...> - 2012-01-26 21:57:09
|
Hi, I have moved Unshield and Dynamite to github: https://github.com/twogood/unshield https://github.com/twogood/dynamite Pull requests are most welcome! PS. Yes, I plan to make a new Unshield release. Best regards, David Eriksson http://www.divideandconquer.se/ |
From: Mark E. <ma...@mp...> - 2012-01-15 11:30:37
|
Reply to the lists, someone else might know the answer. On Tue, 2011-12-20 at 14:20 +0100, Marcin Lach wrote: > On WM without enabled rndis I've made some tests. > Sybce-hal - file /usr/lib/has/scripts/hal-synce-serial I've added ip > adress of dns in pppd opitons instead of local_ip. > on linux: > iptables --table nat --append POSTROUTING --out-interface eth0 -j > MASQUERADE > > and i've got: > > using vxutils i can ping and wget from internet, but IE on WM don't > see this connection and asks for configuring one, also app witch we > are using for transfer files to our server can't use this connection. > Are you using a WM5 or later device in serial (non-rndis) mode, or is it an earlier device ? If its a WM5 in serial, then sync-engine will still do what you want. If its an earlier one .... the iptables masqerading rules should do everything you need from the host side. The real problem is getting the device to understand what it's supposed to do, MS have managed to create one of the most complex and non-intuitive configs for this i have ever seen. I haven't done it for ages, i did once so it is possible. All i can suggest is to keep playing around with the connection settings on the device. > > > > > > 2011/12/19 Mark Ellis <ma...@mp...> > On Mon, 2011-12-19 at 12:40 +0100, Marcin Lach wrote: > > Hello > > > > First, thanks for developing synce. > > > > We use synce with rugged windows mobile/windows CE devices. > > For some reasons we have to do it on Debian. I've managed to > install > > your new packages for ubuntu on debian, seems to work :-), > but it > > would be nice to have native debian packages. > > > I'd like to get proper packages onto debian, it's just a bit > harder than > having some ubuntu packages in the PPA, but when i've finished > the next > big bit of work i do want to try and get it in. > > > > > I've one question/request. > > Is there any option to have internet pass trough (get > internet on > > device through usb and linux computer) when connecting not > rndis > > device. > > > > On non rndis device all work ok exept interent conection. > > > On rndis devices the pass through code is in sync-engine. > Firstly > sync-engine only recognises rndis devices, though i'd like it > to > recognise older ones in the future. I'm not sure if pass > through works > in the same way on older devices though. The old synce-kde > raki used > iptables masquerading. From the source, to start masquerading > you'd do > > iptables -t nat -A POSTROUTING -s {deviceip} -d 0.0.0.0/0 -j > MASQUERADE > > and to stop it use > > iptables -t nat -D POSTROUTING -s {deviceip} -d 0.0.0.0/0 -j > MASQUERADE > > replacing {deviceip} as appropriate. Haven't tried it for some > time, but > it's probably worth a go. > > > > > > > Best regard > > Martin > > |
From: Mark E. <ma...@mp...> - 2012-01-15 09:54:32
|
On Fri, 2012-01-06 at 11:05 +0100, Ilya Bakulin wrote: > The best approach IMHO is to use mpd (miltilink PPP daemon by mav@, > not music player) to connect to WM device. > IIRC I have posted some configs and scripts here in the past. > If there are none floating around, I will try to search them on the > local disc. > Unfortunately I've moved from FreeBSD desktop to Mac OS X and to > Android-based phone, so I have no possibility to test these scripts. > > P.S. Happy New Year to all of you! > Hi Ilya, happy new year to you ! I use android myself as well, but i am trying to keep synce at least working. If you've got some scripts to use mpd i'd like a look at them. For now i'll try what i've cooked up for user ppp, just because i don't have a huge amount of time to look at something new from scratch, but changing ppp at a later date shouldn't be too tricky. I'm more stuck on devd :( > 06.01.12 2:01, Mark Ellis пишет: > > On Tue, 2012-01-03 at 14:16 +0100, Alexander Logvinov wrote: > > > Hello, Mark! > > Hi Alexander > > > > Posting back to the list in case there is anyone else about. > > > > > 2011/12/31 Mark Ellis <ma...@mp...>: > > > > Any FreeBSD users out there ? I want to try and make the new release as > > > > FreeBSD freindly as I can, but I have very little knowledge of it and > > > > could use a hand, so please speak up. > > > I'm maintainer of some of synce-* FreeBSD ports ( > > > http://www.freshports.org/search.php?stype=name&method=match&query=synce-&num=20&orderby=category&orderbyupdown=asc&search=Search > > > ). Unfortunately we don't have pppd binary in the FreeBSD base from > > > 8.0 version (we have userland /usr/sbin/ppp only). All of the synce-* > > > ports are useless right now. > > > > > I noticed that, that's not something I was expecting to have to fix :( I > > do have some ideas on it though. I don't much like it, because it > > appears to be impossible to use userland ppp without modifying the > > system config file, very messy IMHO, and completely awful for a dynamic > > config like synce has. I'm going to have to add an entry to the ppp > > config file to enable a control socket, and run pppctl to configure the > > link, hopefully have something working soon, and it will at least be > > usable at that point. > > > > The other fun part is working out devd to replace all the hal stuff, > > there appears to be very little documentation. What i'd like to do is > > listen for connection events involving the uipaq driver to set off the > > connection, but I can't see any way of getting the correct device file > > when this happens, are you familiar with devd ? > > > > Ta > > Mark > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > > infrastructure or vast IT resources to deliver seamless, secure access to > > virtual desktops. With this all-in-one solution, easily deploy virtual > > desktops for less than the cost of PCs and save 60% on VDI infrastructure > > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > > > > !DSPAM:4f061df112411576013865! > > > > > > _______________________________________________ > > SynCE-Devel mailing list > > Syn...@li... > > https://lists.sourceforge.net/lists/listinfo/synce-devel > > > > > > !DSPAM:4f061df112411576013865! > > -- > Regards, > Ilya Bakulin > http://kibab.com > xmpp://kib...@ja... |
From: Ilya B. <web...@ki...> - 2012-01-06 10:21:11
|
The best approach IMHO is to use mpd (miltilink PPP daemon by mav@, not music player) to connect to WM device. IIRC I have posted some configs and scripts here in the past. If there are none floating around, I will try to search them on the local disc. Unfortunately I've moved from FreeBSD desktop to Mac OS X and to Android-based phone, so I have no possibility to test these scripts. P.S. Happy New Year to all of you! 06.01.12 2:01, Mark Ellis ?????: > On Tue, 2012-01-03 at 14:16 +0100, Alexander Logvinov wrote: >> Hello, Mark! > Hi Alexander > > Posting back to the list in case there is anyone else about. > >> 2011/12/31 Mark Ellis <ma...@mp...>: >>> Any FreeBSD users out there ? I want to try and make the new release as >>> FreeBSD freindly as I can, but I have very little knowledge of it and >>> could use a hand, so please speak up. >> I'm maintainer of some of synce-* FreeBSD ports ( >> http://www.freshports.org/search.php?stype=name&method=match&query=synce-&num=20&orderby=category&orderbyupdown=asc&search=Search >> ). Unfortunately we don't have pppd binary in the FreeBSD base from >> 8.0 version (we have userland /usr/sbin/ppp only). All of the synce-* >> ports are useless right now. >> > I noticed that, that's not something I was expecting to have to fix :( I > do have some ideas on it though. I don't much like it, because it > appears to be impossible to use userland ppp without modifying the > system config file, very messy IMHO, and completely awful for a dynamic > config like synce has. I'm going to have to add an entry to the ppp > config file to enable a control socket, and run pppctl to configure the > link, hopefully have something working soon, and it will at least be > usable at that point. > > The other fun part is working out devd to replace all the hal stuff, > there appears to be very little documentation. What i'd like to do is > listen for connection events involving the uipaq driver to set off the > connection, but I can't see any way of getting the correct device file > when this happens, are you familiar with devd ? > > Ta > Mark > > > > > > > ------------------------------------------------------------------------------ > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > > !DSPAM:4f061df112411576013865! > > > _______________________________________________ > SynCE-Devel mailing list > Syn...@li... > https://lists.sourceforge.net/lists/listinfo/synce-devel > > > !DSPAM:4f061df112411576013865! -- Regards, Ilya Bakulin http://kibab.com xmpp://kib...@ja... |
From: Mark E. <ma...@mp...> - 2012-01-05 22:01:46
|
On Tue, 2012-01-03 at 14:16 +0100, Alexander Logvinov wrote: > Hello, Mark! Hi Alexander Posting back to the list in case there is anyone else about. > > 2011/12/31 Mark Ellis <ma...@mp...>: > > Any FreeBSD users out there ? I want to try and make the new release as > > FreeBSD freindly as I can, but I have very little knowledge of it and > > could use a hand, so please speak up. > I'm maintainer of some of synce-* FreeBSD ports ( > http://www.freshports.org/search.php?stype=name&method=match&query=synce-&num=20&orderby=category&orderbyupdown=asc&search=Search > ). Unfortunately we don't have pppd binary in the FreeBSD base from > 8.0 version (we have userland /usr/sbin/ppp only). All of the synce-* > ports are useless right now. > I noticed that, that's not something I was expecting to have to fix :( I do have some ideas on it though. I don't much like it, because it appears to be impossible to use userland ppp without modifying the system config file, very messy IMHO, and completely awful for a dynamic config like synce has. I'm going to have to add an entry to the ppp config file to enable a control socket, and run pppctl to configure the link, hopefully have something working soon, and it will at least be usable at that point. The other fun part is working out devd to replace all the hal stuff, there appears to be very little documentation. What i'd like to do is listen for connection events involving the uipaq driver to set off the connection, but I can't see any way of getting the correct device file when this happens, are you familiar with devd ? Ta Mark |
From: Mark E. <ma...@mp...> - 2011-12-30 20:53:16
|
Any FreeBSD users out there ? I want to try and make the new release as FreeBSD freindly as I can, but I have very little knowledge of it and could use a hand, so please speak up. Ta Mark |
From: Mark E. <ma...@mp...> - 2011-12-19 21:48:31
|
On Mon, 2011-12-19 at 12:40 +0100, Marcin Lach wrote: > Hello > > First, thanks for developing synce. > > We use synce with rugged windows mobile/windows CE devices. > For some reasons we have to do it on Debian. I've managed to install > your new packages for ubuntu on debian, seems to work :-), but it > would be nice to have native debian packages. I'd like to get proper packages onto debian, it's just a bit harder than having some ubuntu packages in the PPA, but when i've finished the next big bit of work i do want to try and get it in. > > I've one question/request. > Is there any option to have internet pass trough (get internet on > device through usb and linux computer) when connecting not rndis > device. > > On non rndis device all work ok exept interent conection. On rndis devices the pass through code is in sync-engine. Firstly sync-engine only recognises rndis devices, though i'd like it to recognise older ones in the future. I'm not sure if pass through works in the same way on older devices though. The old synce-kde raki used iptables masquerading. From the source, to start masquerading you'd do iptables -t nat -A POSTROUTING -s {deviceip} -d 0.0.0.0/0 -j MASQUERADE and to stop it use iptables -t nat -D POSTROUTING -s {deviceip} -d 0.0.0.0/0 -j MASQUERADE replacing {deviceip} as appropriate. Haven't tried it for some time, but it's probably worth a go. > > > Best regard > Martin |
From: Pavel R. <pr...@gn...> - 2011-12-07 14:16:54
|
Quoting David Eriksson <tw...@us...>: > Hi Pavel, > > I plan to move Unshield (and libdynamite) from the SynCE project on > SourceForge to github, and make a new release as soon as possible. That would be great! Thank you! -- Regards, Pavel Roskin |
From: David E. <tw...@us...> - 2011-12-07 13:51:09
|
Hi Pavel, I plan to move Unshield (and libdynamite) from the SynCE project on SourceForge to github, and make a new release as soon as possible. \David On Mon, Dec 5, 2011 at 20:54, Pavel Roskin <pr...@gn...> wrote: > Hello! > > The current release of unshield is 0.6, according to > http://sourceforge.net/projects/synce/files/Unshield/ > > Version 0.6 crashed with the archives created by the latest versions of > InstallShield. The fixes were applied in Subversion (revisions 3805 and > 3953). The last commit was made in January 2011, almost a year ago. > > It would be nice to make another release soon. Nobody likes software > that crashes. > > While at that, the link called "Unshield package" on > http://www.synce.org/oldwiki/index.php/Unshield > leads to a page that has nothing interesting: > http://sourceforge.net/projects/synce/files/OldFiles/ > > Instead, the link should be to this page: > http://sourceforge.net/projects/synce/files/Unshield/ > > I tried to register in the Wiki to make the change, but it don't appear > to be working in the latest Mozilla Firefox or Google Chromium. I try > to log in and I get a message: > > There is no user by the name "Pavel Roskin". Check your spelling, or > use the form below to create a new user account. > > However, there is no form below. I'm talking about "oldwiki", the new > wiki doesn't have a page for unshield. > > -- > Regards, > Pavel Roskin > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > SynCE-Devel mailing list > Syn...@li... > https://lists.sourceforge.net/lists/listinfo/synce-devel > |
From: Pavel R. <pr...@gn...> - 2011-12-05 20:29:16
|
Hello! The current release of unshield is 0.6, according to http://sourceforge.net/projects/synce/files/Unshield/ Version 0.6 crashed with the archives created by the latest versions of InstallShield. The fixes were applied in Subversion (revisions 3805 and 3953). The last commit was made in January 2011, almost a year ago. It would be nice to make another release soon. Nobody likes software that crashes. While at that, the link called "Unshield package" on http://www.synce.org/oldwiki/index.php/Unshield leads to a page that has nothing interesting: http://sourceforge.net/projects/synce/files/OldFiles/ Instead, the link should be to this page: http://sourceforge.net/projects/synce/files/Unshield/ I tried to register in the Wiki to make the change, but it don't appear to be working in the latest Mozilla Firefox or Google Chromium. I try to log in and I get a message: There is no user by the name "Pavel Roskin". Check your spelling, or use the form below to create a new user account. However, there is no form below. I'm talking about "oldwiki", the new wiki doesn't have a page for unshield. -- Regards, Pavel Roskin |