Jpiloteers, I have a new Linux (Ubuntu 23.04) system.  While installing Jpilot, I encountered the following problem: **BEGIN** [Starting in the proper directory] bujin{jwt}% sudo dpkg -i ./python-pisock_0.12.5-dfsg-2build2_amd64.deb (Reading database ... 195124 files and directories currently installed.) Preparing to unpack .../python-pisock_0.12.5-dfsg-2build2_amd64.deb ... Unpacking python-pisock (0.12.5-dfsg-2build2) over (0.12.5-dfsg-2build2) ... dpkg: dependency problems prevent configuration of python-pisock: python-pisock depends on python2 (<< 2.8); however:  Package python2 is not installed. python-pisock depends on python2 (>= 2.7~); however:  Package python2 is not installed. python-pisock depends on python2:any (<< 2.8). python-pisock depends on python2:any (>= 2.7~). dpkg: error processing package python-pisock (--install): dependency problems - leaving unconfigured Errors were encountered while processing: python-pisock bujin{jwt}% python2 -V Python 2.7.13 **END** The "python2" package has been depreciated and is not available in Ubuntu 23.04. I manually installed Python 2.7.13.  I symbolically linked "python2.7" to "python2".  (The last couple of lines show that "python2" is, in fact, "Python 2.7.13".) My guess is that "python-pisock_0.12.5-dfsg-2build2_amd64.deb" is expecting to see _Package_ "python2" installed and not that "python2" merely available. My question is, "How do I correct this to complete getting Jpilot up on my new system?" Thanks for your help. -- John

Hi John, Pilot-link was removed from Debian a while back because of the python2 discrimination. Jpilot was removed because pilot-link is a dependency. There are a couple of things to try. 1. curl -o script.sh https://packagecloud.io/install/repositories/judd/jpilot/script.deb.sh Use the DISTRIB_CODENAME below for the dist. sudo os=ubuntu dist=lunar ./script.sh sudo apt install jpilot jpilot-plugins 2. Download the deb packages from jpilot.org and install them. Judd On 6/7/23 11:56, John Tiede wrote: > Jpiloteers, > > I have a new Linux (Ubuntu 23.04) system. While installing Jpilot, I > encountered the following problem: > > **BEGIN** > [Starting in the proper directory] > > bujin{jwt}% sudo dpkg -i ./python-pisock_0.12.5-dfsg-2build2_amd64.deb > (Reading database ... 195124 files and directories currently installed.) > Preparing to unpack .../python-pisock_0.12.5-dfsg-2build2_amd64.deb ... > Unpacking python-pisock (0.12.5-dfsg-2build2) over (0.12.5-dfsg-2build2) > ... > dpkg: dependency problems prevent configuration of python-pisock: > python-pisock depends on python2 (<< 2.8); however: > Package python2 is not installed. > python-pisock depends on python2 (>= 2.7~); however: > Package python2 is not installed. > python-pisock depends on python2:any (<< 2.8). > python-pisock depends on python2:any (>= 2.7~). > > dpkg: error processing package python-pisock (--install): > dependency problems - leaving unconfigured > Errors were encountered while processing: > python-pisock > bujin{jwt}% python2 -V > Python 2.7.13 > **END** > > The "python2" package has been depreciated and is not available in > Ubuntu 23.04. I manually installed Python 2.7.13. I symbolically linked > "python2.7" to "python2". (The last couple of lines show that "python2" > is, in fact, "Python 2.7.13".) > > My guess is that "python-pisock_0.12.5-dfsg-2build2_amd64.deb" is > expecting to see _Package_ "python2" installed and not that "python2" > merely available. > > My question is, "How do I correct this to complete getting Jpilot up on > my new system?" > > Thanks for your help. > > -- > John > > _______________________________________________ > Jpilot mailing list -- > jpilot@lists.jpilot.org > To unsubscribe send an email to > jpilot-leave@lists.jpilot.org

> sudo os=ubuntu dist=lunar ./script.sh I did this for noble (24.04) and encountered https://github.com/juddmon/jpilot/issues/57 :( “**E:** The repository 'https://packagecloud.io/judd/jpilot/ubuntu noble Release' does not have a Release file.”

After running the `curl` command, you can manually edit the file `/etc/apt/sources.list.d/judd_jpilot.list` and replace `noble` by `jammy` and again do `sudo apt update`. This is a workaround. Hopefully, there would be an official update some day. Am 14.10.24 um 20:11 schrieb tom+jpilot@falkensweb.com: >> sudo os=ubuntu dist=lunar ./script.sh > I did this for noble (24.04) and encountered https://github.com/juddmon/jpilot/issues/57 :( > > “**E:** The repository 'https://packagecloud.io/judd/jpilot/ubuntu noble Release' does not have a Release file.” > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org

Awesome !\ \ I can confirm this works on Ubuntu 24.04 LTS, a Palm TX, over WiFi (jpilot uses net:any, hard coded IP on the Palm side)\ \ This should just be updated on the website in the meantime ?