Connection Linux --> PDA WindowsCE

barnarasta · 12-21-2015, 06:58 AM

Good morning,
I just have a PDA to check the work done on packages and
IT DOES NOT WORK

No response, sound or warning occurs.
I write some data if they can be useful.
# syslog ===> I find it strange that long line that I remarked.

Quote:

Dec 21 13:34:36 debian-jessie-test synce-udev-serial: INFO : serial event, ACTION = remove, INTERFACE = , DEVPATH = /devices/pci0000:00/0000:00:13.2/usb2/2-3/2-3:1.0/ttyUSB0/tty/ttyUSB0, SUBSYSTEM = tty, DEVNAME = /dev/ttyUSB0
Dec 21 13:34:40 debian-jessie-test kernel: [ 104.678126] usb 2-3: new high-speed USB device number 3 using ehci-pci
Dec 21 13:34:40 debian-jessie-test kernel: [ 104.825851] usb 2-3: New USB device found, idVendor=045e, idProduct=00ce
Dec 21 13:34:40 debian-jessie-test kernel: [ 104.825864] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 21 13:34:40 debian-jessie-test kernel: [ 104.825871] usb 2-3: Product: Datalogic USB Sync
Dec 21 13:34:40 debian-jessie-test kernel: [ 104.825877] usb 2-3: Manufacturer: Datalogic S.p.A.
Dec 21 13:34:40 debian-jessie-test kernel: [ 104.825882] usb 2-3: SerialNumber: e6461300-4604-0801-500e-00479c090000
Dec 21 13:34:40 debian-jessie-test kernel: [ 104.827983] ipaq 2-3:1.0: PocketPC PDA converter detected
Dec 21 13:34:40 debian-jessie-test kernel: [ 104.829550] usb 2-3: PocketPC PDA converter now attached to ttyUSB0
Dec 21 13:34:40 debian-jessie-test synce-udev-serial: INFO : serial event, ACTION = add, INTERFACE = , DEVPATH = /devices/pci0000:00/0000:00:13.2/usb2/2-3/2-3:1.0/ttyUSB0/tty/ttyUSB0, SUBSYSTEM = tty, DEVNAME = /dev/ttyUSB0

# lsusb

Quote:

Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

# /dev

Quote:

crw--w---- 1 root tty 4, 63 dic 21 13:33 tty63
crw--w---- 1 root tty 4, 7 dic 21 13:33 tty7
crw--w---- 1 root tty 4, 8 dic 21 13:33 tty8
crw--w---- 1 root tty 4, 9 dic 21 13:33 tty9
crw-rw---- 1 root dialout 4, 64 dic 21 13:33 ttyS0
crw-rw---- 1 root dialout 4, 65 dic 21 13:33 ttyS1
crw-rw---- 1 root dialout 4, 66 dic 21 13:33 ttyS2
crw-rw---- 1 root dialout 4, 67 dic 21 13:33 ttyS3
crw-rw---- 1 root dialout 188, 0 dic 21 13:45 ttyUSB0
crw------- 1 root root 10, 239 dic 21 13:33 uhid
crw------- 1 root root 10, 223 dic 21 13:33 uinput
crw-rw-rw- 1 root root 1, 9 dic 21 13:33 urandom
crw-rw---- 1 root tty 7, 0 dic 21 13:33 vcs
crw-rw---- 1 root tty 7, 1 dic 21 13:33 vcs1
crw-rw---- 1 root tty 7, 2 dic 21 13:33 vcs2
crw-rw---- 1 root tty 7, 3 dic 21 13:33 vcs3

# ifconfig ( does not appear ppp0 )

Quote:

eth0 Link encap:Ethernet HWaddr f4:6d:04:52:27:a4
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::f66d:4ff:fe52:27a4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3340 errors:0 dropped:27 overruns:0 frame:0
TX packets:956 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:900606 (879.4 KiB) TX bytes:254993 (249.0 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:208 errors:0 dropped:0 overruns:0 frame:0
TX packets:208 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:89332 (87.2 KiB) TX bytes:89332 (87.2 KiB)

# synce-pls =====> Specific command to list PDA inside.

Quote:

synce-pls: Could not find device '(Default)': 800704e0: No more local devices.

next post, values working perfectly ( fine, fine, super-fine) with wheezy.

barnarasta · 12-21-2015, 07:06 AM

working with wheezy.

differences (Jessie vs wheezy) marked

Quote:

kernel: [ 1430.884028] usb 1-7: new high-speed USB device number 4 using ehci_hcd
kernel: [ 1431.032061] usb 1-7: New USB device found, idVendor=045e, idProduct=00ce
kernel: [ 1431.032068] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: [ 1431.032072] usb 1-7: Product: Datalogic USB Sync
kernel: [ 1431.032076] usb 1-7: Manufacturer: Datalogic S.p.A.
kernel: [ 1431.032079] usb 1-7: SerialNumber: e6461300-4604-0801-500e-004769090000 checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7"
mtp-probe: bus: 1, device: 4 was not an MTP device
kernel: [ 1431.104067] usbcore: registered new interface driver usbserial
kernel: [ 1431.104095] USB Serial support registered for generic
kernel: [ 1431.104147] usbcore: registered new interface driver usbserial_generic
kernel: [ 1431.104150] usbserial: USB Serial Driver core
kernel: [ 1431.118172] USB Serial support registered for PocketPC PDA
kernel: [ 1431.118216] ipaq 1-7:1.0: PocketPC PDA converter detected
kernel: [ 1431.118509] usb 1-7: PocketPC PDA converter now attached to ttyUSB0
kernel: [ 1431.118523] usbcore: registered new interface driver ipaq
kernel: [ 1431.118524] ipaq: v1.0:USB PocketPC PDA driver
modem-manager[2673]: <info> (ttyUSB0) opening serial port...
modem-manager[2673]: <info> (ttyUSB0) closing serial port...
acpid: client connected from 2749[0:0]
kernel: [ 1748.112048] usb 1-7: new high-speed USB device number 5 using ehci_hcd
kernel: [ 1748.260281] usb 1-7: New USB device found, idVendor=045e, idProduct=00ce
kernel: [ 1748.260287] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: [ 1748.260292] usb 1-7: Product: Datalogic USB Sync
kernel: [ 1748.260295] usb 1-7: Manufacturer: Datalogic S.p.A.
kernel: [ 1748.260299] usb 1-7: SerialNumber: e6461300-4604-0801-500e-004769090000
kernel: [ 1748.262490] ipaq 1-7:1.0: PocketPC PDA converter detected
kernel: [ 1748.263832] usb 1-7: PocketPC PDA converter now attached to ttyUSB0
mtp-probe: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7"
mtp-probe: bus: 1, device: 5 was not an MTP device
dbus[2335]: [system] Activating service name='org.freedesktop.Hal' (using servicehelper)
dbus[2335]: [system] Successfully activated service 'org.freedesktop.Hal'
acpid: client connected from 5638[116:124]
acpid: 1 client rule loaded
pppd[5646]: pppd 2.4.5 started by root, uid 0
kernel: [ 1794.900708] PPP generic driver version 2.4.2
pppd[5646]: Serial connection established.
pppd[5646]: Using interface ppp0
pppd[5646]: Connect: ppp0 <--> /dev/ttyUSB0
NetworkManager[2613]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
NetworkManager[2613]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
kernel: [ 1796.404499] PPP BSD Compression module registered
kernel: [ 1796.417983] PPP Deflate Compression module registered
pppd[5646]: local IP address 192.168.131.1
pppd[5646]: remote IP address 192.168.131.129

# lsusb

Quote:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 1307:0330 Transcend Information, Inc. 63-in-1 Multi-Card Reader/Writer
Bus 002 Device 002: ID 1bcf:0005 Sunplus Innovation Technology Inc.
Bus 001 Device 005: ID 045e:00ce Microsoft Corp. Generic PPC Flash device

# ifconfig

Quote:

eth0 Link encap:Ethernet HWaddr 10:78:d2:74:b9:34
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::1278:d2ff:fe74:b934/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6446 errors:0 dropped:0 overruns:0 frame:0
TX packets:4631 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2269456 (2.1 MiB) TX bytes:663274 (647.7 KiB)
Interrupt:42 Base address:0xe000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:480 (480.0 B) TX bytes:480 (480.0 B)

ppp0 Link encap:Point-to-Point Protocol
inet addr:192.168.131.1 P-t-P:192.168.131.129 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:113 errors:0 dropped:0 overruns:0 frame:0
TX packets:140 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:6352 (6.2 KiB) TX bytes:5839 (5.7 KiB)

With all my ignorance, but apparently not aligned correctly to execute the connection device pppd.
I'm giving this unpleasant news.
If you need some more information, notice me and I'll gladly offers.

bobbib · 12-22-2015, 06:52 PM

Quote:

Originally Posted by barnarasta

IT DOES NOT WORK

That's sad.
Well, let's try to analyze your Jessie testing system configuration...

---

Quote:

# syslog ===> I find it strange that long line that I remarked.

Code:

Dec 21 13:34:36 debian-jessie-test synce-udev-serial: INFO : serial event, ACTION = remove, INTERFACE = , DEVPATH = /devices/pci0000:00/0000:00:13.2/usb2/2-3/2-3:1.0/ttyUSB0/tty/ttyUSB0, SUBSYSTEM = tty, DEVNAME = /dev/ttyUSB0
...
Dec 21 13:34:40 debian-jessie-test synce-udev-serial: INFO : serial event, ACTION = add, INTERFACE = , DEVPATH = /devices/pci0000:00/0000:00:13.2/usb2/2-3/2-3:1.0/ttyUSB0/tty/ttyUSB0, SUBSYSTEM = tty, DEVNAME = /dev/ttyUSB0

Those long lines are not really strange, they're are device file addresses in device tree (look into the "/sys/devices/" directory).
IMHO, "ACTION = remove" followed by "ACTION = add" suggests the device being removed and connected again.
BTW, where do you get that log? From "/var/log/syslog"?

---

Notice lsusb output shows no "045e:00ce" devices. Device disconnected? Unstable connection?

---

Regarding the PPP, can you please try to execute:
$ apt-cache policy ppp

barnarasta · 12-23-2015, 08:09 AM

Regarding the PPP, can you please try to execute:
$ apt-cache policy ppp

WHEEZY

Quote:

ppp:
Instalados: 2.4.5-5.1+deb7u2
Candidato: 2.4.5-5.1+deb7u2
Tabla de versin:
*** 2.4.5-5.1+deb7u2 0
500 http://ftp.es.debian.org/debian/ wheezy/main i386 Packages
500 http://security.debian.org/ wheezy/updates/main i386 Packages
500 http://ftp.us.debian.org/debian/ wheezy/main i386 Packages
100 /var/lib/dpkg/status

JESSIE

Quote:

ppp:
Instalados: 2.4.6-3.1
Candidato: 2.4.6-3.1
Tabla de versin:
*** 2.4.6-3.1 0
500 http://ftp.us.debian.org/debian/ jessie/main amd64 Packages
100 /var/lib/dpkg/status

lsusb

Quote:

Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 004: ID 045e:00ce Microsoft Corp. Generic PPC Flash device
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

/var/log/syslog

Quote:

Dec 23 15:01:01 debian-jessie-test systemd[1]: Failed to start LSB: DHCP server.
Dec 23 15:06:30 debian-jessie-test kernel: [ 470.620374] usb 2-3: new high-speed USB device number 4 using ehci-pci
Dec 23 15:06:30 debian-jessie-test kernel: [ 470.767907] usb 2-3: New USB device found, idVendor=045e, idProduct=00ce
Dec 23 15:06:30 debian-jessie-test kernel: [ 470.767919] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 23 15:06:30 debian-jessie-test kernel: [ 470.767927] usb 2-3: Product: Datalogic USB Sync
Dec 23 15:06:30 debian-jessie-test kernel: [ 470.767933] usb 2-3: Manufacturer: Datalogic S.p.A.
Dec 23 15:06:30 debian-jessie-test kernel: [ 470.767938] usb 2-3: SerialNumber: e6461300-4604-0801-500e-00479c090000
Dec 23 15:06:30 debian-jessie-test kernel: [ 470.770111] ipaq 2-3:1.0: PocketPC PDA converter detected
Dec 23 15:06:30 debian-jessie-test kernel: [ 470.771595] usb 2-3: PocketPC PDA converter now attached to ttyUSB0
Dec 23 15:06:30 debian-jessie-test synce-udev-serial: INFO : serial event, ACTION = add, INTERFACE = , DEVPATH = /devices/pci0000:00/0000:00:13.2/usb2/2-3/2-3:1.0/ttyUSB0/tty/ttyUSB0, SUBSYSTEM = tty, DEVNAME = /dev/ttyUSB0

=============================================================

I have to idea - after Christmas - put a Wheezy-test on a small HD I have to test the packages created.

We know that:
synce-hal + librapi2-tools ==> works perfectly in Wheezy. amd64 & i386
synce-hal ==> does not exist in Jessie
synce-core_0.17 ===> not work for Jessie

I want to verify that:
synce-core_0.17 ===>? It works well in Wheezy ??

Happy new year!!

bobbib · 12-25-2015, 06:16 PM

Quote:

JESSIE
ppp:
Instalados: 2.4.6-3.1

barnarasta, that means PPP is installed at least...

I'll try to read the docs, maybe I'll find something useful.

---

IMHO, given that we're trying to make our fresh package work with Debian Jessie, testing it on old Wheezy is not very useful.

---

Happy holidays!

barnarasta · 01-08-2016, 02:22 AM

Happy New Year !!!

Quote:

barnarasta, that means PPP is installed at least...

$ apt-cache policy ppp
JESSIE
ppp:
Installed: 2.4.6-3.1
======================================================
My idea of trying the original package in Wheezy was only to verify that the operation is perfect,
remember that I have installed and running synce-hal & librapi2-tools NOT the synce-core.

If you do not see it useful, I hope to know if you found something new in the documentation.

1salu2

bobbib · 01-15-2016, 05:36 PM

Quote:

Originally Posted by barnarasta

remember that I have installed and running synce-hal & librapi2-tools NOT the synce-core.

As far as I understand it, the programs that were previously in "synce-hal" & "librapi2-tools", now (in new SynCE versions) have been moved to a single "synce-core" package;
and some of the obsolete internal components, relying on outdated Linux frameworks, were just removed (and that should not harm the ordinary usage).

Quote:

I hope to know if you found something new in the documentation.

Unfortuanately, not yet; needs more reading. And probably I need to find my old WinCE device to experiment with...

barnarasta · 01-20-2016, 04:06 PM

Quote:

Originally Posted by bobbib

Unfortuanately, not yet; needs more reading. And probably I need to find my old WinCE device to experiment with...

Unfortunately we are far to encounter and experience with my PDA.

Wheezy-LTS ends in April 2018, we hope that during this time to develop something similar to "synce-hal" to the more modern kernels.

I was looking and found a Comment
https://sourceforge.net/p/synce/mail...sage/34352394/
that seems to work the same problem from a different vision.
"synce-sync-engine".
Unfortunately I just do not understand how it develops 'Gustavo', I sent an email requesting more information and I'm waiting for a possible response.

bobbib, Thanks for everything !!!

GREYES71 · 06-22-2016, 07:26 PM

Quote:

Originally Posted by barnarasta

[...]
I was looking and found a Comment
https://sourceforge.net/p/synce/mail...sage/34352394/
that seems to work the same problem from a different vision.
"synce-sync-engine".
Unfortunately I just do not understand how it develops 'Gustavo', I sent an email requesting more information and I'm waiting for a possible response.

bobbib, Thanks for everything !!!

Hola Angel / Hi barnarasta ;-)

Because misfortune occurred with the hard disk of my PC (with Ubuntu), I decided to do a clean install and choose change for Debian Jessie. The change was already in mind but the ultimate motivation is to help get the project Synce running (based on binary packages) in other OS besides Ubuntu.

I have compiled synce-core without making changes DHCLIENTPATH; simply "/sbin" should be in the user's PATH or run "./configure" as "root".

Regarding the error "GLIB_LIBS"; you must install the "libglib2.0-dev" package.

I have not tried yet, maybe tomorrow, but I think the error with "D-Bus" is solved by installing "libdbus-1-dev" && "libgudev-1.0-dev" && "udev" (maybe "libdbus-glib-1-dev" else).

Regards!

GREYES71 · 06-23-2016, 08:15 AM

Yesterday...

checking for DBUS... no
checking for DBUS... no
checking whether to use GDBus... yes
[...]
configure: error: udev support requested but D-Bus could not be found

Today, after installing libdbus-1-dev...

checking for DBUS... yes
checking for DBUS... yes
checking whether to use GDBus... yes
[...]
configure: Building with udev support
checking for GUDEV... no
checking for UDEV... yes
checking for udevadm... /sbin/udevadm
checking udev dir... /lib/udev

Final successfully!!

GREYES71 · 06-23-2016, 08:43 AM

Today, after apt-get install libgudev-1.0-dev

Building dependency tree
The following extra packages will be installed:
gir1.2-gudev-1.0
Need to get 27.3 kB of archives.
After this operation, 309 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y

checking for DBUS... yes
checking for DBUS... yes
checking whether to use GDBus... yes
[...]
configure: Building with udev support
checking for GUDEV... yes
checking for UDEV... yes
checking for udevadm... /sbin/udevadm
checking udev dir... /lib/udev

Difference between the two outputs of "./configure":

< checking for GUDEV... no
---
> checking for GUDEV... yes

Both successfully.

GREYES71 · 06-23-2016, 10:17 AM

GOTO synce-sync-engine-0.16

I do not know about Python, do not know if there is something like "./configure".
Reading a bit on the web about it, supposedly in the file "setup.py" should have a section named "install_requires", this should be used to specify what dependencies a project minimally needs to run.

And... there is no dependence.

Next step: do DEB files for Debian “Jessie”

I'm reading...
- http://packaging.ubuntu.com/html/pac...-software.html
- https://wiki.debian.org/HowToPackageForDebian
- https://wiki.debian.org/Packaging/Intro
- [Es] https://wiki.debian.org/es/IntroDebianPackaging
- https://debian-handbook.info/browse/...t-package.html

GREYES71 · 10-27-2022, 04:02 PM

Hi all

Quote:

Originally Posted by bobbib

barnarasta, now you see how complex the manual compilation process can be

Uff!!! Really, I Know.
I am currently working on building a DEB package for Debian Bullseye from SynCE version 0.17 sources from SynCE PPA
with pbuilder following your steps bobbib.

Quote:

Originally Posted by bobbib

$ dpkg-source -b synce-core-0.17

Install pbuilder:
# apt-get install pbuilder

Create a configuration file ("/root/.pbuilderrc"; needs superuser privileges) with the following contents:

Code:

# Target distribution
DISTRIBUTION=jessie
# By default, pbuilder uses "/var/cache/pbuilder/aptcache" for package cache;
# why not try reusing the packages from the system's APT cache?
APTCACHE=/var/cache/apt/archives

Create the base build image:
# pbuilder create

In case you've created the base image long time ago, update it:
# pbuilder update

---

Actual binary packages building process from the source package.

Go to the directory where your source package's files ("synce-core_0.17.orig.tar.gz", "synce-core_0.17-0.1.debian.tar.xz", "synce-core_0.17-0.1.dsc") are stored:
$ cd /home/user/synce-core

Start the builder:
# pbuilder build synce-core_0.17-0.1.dsc

Wait...

If everything finishes well, you'll see a bunch of new files:
$ ls /var/cache/pbuilder/result

Code:

libsynce0_0.17-0.1_amd64.deb
libsynce0-dev_0.17-0.1_amd64.deb
libsynce-dbg_0.17-0.1_amd64.deb
python-rapi2_0.17-0.1_amd64.deb
synce-bluetooth_0.17-0.1_amd64.deb
synce-core_0.17-0.1_amd64.changes
synce-core_0.17-0.1.debian.tar.xz
synce-core_0.17-0.1.dsc
synce-core_0.17.orig.tar.gz
synce-dccm_0.17-0.1_amd64.deb
synce-doc_0.17-0.1_all.deb
synce-tools_0.17-0.1_amd64.deb

I should have made a change in the dependencies: python -> python2 [OK]
In Bullseye the python-pyrex package is missing, but...
I got python-pyrex (0.9.9-1) from the Buster repository and and installed successfully.
Lets go!!

Code:

$ sudo pbuilder update --override-config
I: Upgrading for distribution bullseye
...
[OK]

----

$ sudo pbuilder build synce-core_0.17-0.1~0debian0~bullseye1.dsc
...
dpkg-source: info: extracting synce-core in synce-core-0.17
dpkg-source: info: unpacking synce-core_0.17.orig.tar.gz
dpkg-source: info: unpacking synce-core_0.17-0.1~0debian0~bullseye1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying rename-p-binaries.diff
dpkg-source: info: applying py-findallfiles-segfault.diff
I: using fakeroot in build.
I: Installing the build-deps
No se puede instalar este paquete ("Cannot install this package")
Dependency is not satisfiable: python-pyrex (>= 0.9.6)
E: pbuilder-satisfydepends failed.

I've followed several tutorials to get pbuilder to include local packages (in this case python-pyrex), but some did not work and others aren't clear enough.
Now, i want to try "Building With Local Packages" with dput & mini-dinstall.

File ~/.mini-dinstall.conf

Code:

[DEFAULT]

architectures = i386
archivedir = /var/cache/archive/
use_dnotify = 0
verify_sigs = 0
extra_keyrings = ~/.gnupg/pubring.gpg
mail_on_success = 0
archive_style = flat
poll_time = 10
mail_log_level = NONE

[bullseye]

File ~/.dput.cf

Code:

[local]
method = local
incoming = /var/cache/archive/mini-dinstall/incoming
allow_non-us_software = 1
run_dinstall = 0
post_upload_command = mini-dinstall --batch

And now? I should upload the python-pyrex deb to my local filesystem with command like:

Code:

# dput local python-pyrex_0.9.9-1_all.changes
Can't open python-pyrex_0.9.9-1_all.changes

How the .changes file is generated?
I dont understand at all. At this point I'm lost and very tired.
All help is welcome.

Gustavo

Soadyheid · 10-28-2022, 08:23 AM

This thread died and went to thread heaven about six years ago, perhaps it should be left to rest in peace.

@GREYES71, Maybe you should start a new thread to highlight your problem.

Play Bonny!

GREYES71 · 10-28-2022, 10:34 AM

Quote:

Originally Posted by Soadyheid

This thread died and went to thread heaven about six years ago, perhaps it should be left to rest in peace.

@GREYES71, Maybe you should start a new thread to highlight your problem.

Hi Soadyheid
I've posted in the same thread for two reasons: (1) the problem is the same (connecting PDA to Linux) using Synce on Debian (except instead of Jessie it's now Bullseye); (2) here is a knowledge base on the subject that I think is good to have on hand.

Best regards