jpilot@lists.jpilot.org

General support, questions, patches for J-Pilot.

View all threads

New Install Won't Sync with PDA

JM
Judd Montgomery
Thu, Jul 30, 2026 3:53 PM

On 7/30/26 09:12, J. Milgram via Jpilot wrote:

Other than fixing a declaration in jp-contact.c, no changes to the
codebase were required for Slack 15. That "patch" was:

sed -i -e 's/return Contact_add_blob(c, blob);/return
Contact_add_blob(c, (void*)blob);/' jp-contact.c

This should be fixed with the pilot-link and jpilot releases that are coming soon. You should make sure jpilot (HEAD) and pilot-link (HEAD) build and get any patches in ASAP.

Is the pilot-link build script abandoned also? It should be updated for the upcoming release.

BTW for some reason SBo categorizes it as "accessibility" but personally
I think it should be "office" ... before I recommend a change, any
history there I should know about?

It seems like office to me.

Judd

On 7/30/26 09:12, J. Milgram via Jpilot wrote: > Other than fixing a declaration in jp-contact.c, no changes to the > codebase were required for Slack 15. That "patch" was: > > sed -i -e 's/return Contact_add_blob(c, blob);/return > Contact_add_blob(c, (void*)blob);/' jp-contact.c This should be fixed with the pilot-link and jpilot releases that are coming soon. You should make sure jpilot (HEAD) and pilot-link (HEAD) build and get any patches in ASAP. Is the pilot-link build script abandoned also? It should be updated for the upcoming release. > BTW for some reason SBo categorizes it as "accessibility" but personally > I think it should be "office" ... before I recommend a change, any > history there I should know about? It seems like office to me. Judd
JM
J. Milgram
Fri, Jul 31, 2026 1:53 AM

On 7/30/26 11:53, Judd Montgomery wrote:

sed -i -e 's/return Contact_add_blob(c, blob);/return
Contact_add_blob(c, (void*)blob);/' jp-contact.c

This should be fixed with the pilot-link and jpilot releases that are coming soon. You should make sure jpilot (HEAD) and pilot-link (HEAD) build and get any patches in ASAP.

Is the pilot-link build script abandoned also? It should be updated for the upcoming release.

I  don't think there ever was a pilot-link SlackBuild. But I'll give it
a go.

I'll keep an eye out for the next jpilot release and submit updated
SlackBuilds then  (the pilot-link package will be new). There's an
"sbocheck" script that will notice that  jpilot needs an upgrade, so
just "sboupgrade jpilot" will take care of it once the new SlackBuild
is  up. So no harm  in  a 2.0.3 SlackBuild going out now.

SlackBuilds point towards source code release tarballs, so whatever has
been fixed or updated in the release is what the SlackBuild user will
get. I will remove the short patches I inserted  in the 2.0.3
Slackbuild. (SBO and indeed Slackware itself discourage patches over
what's in the official releases, but they're tolerated if they're needed
for  a successful build.)

Do jpilot and pilot-link depend on one another in any way? We can mark
the dependency  in the SlackBuild and the sbotool scripts will do the
right  thing.

regards
Judah

BTW for some reason SBo categorizes it as "accessibility" but personally
I think it should be "office" ... before I recommend a change, any
history there I should know about?

It seems like office to me.

Judd


Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org

--

milgram@cgpp.com
301-257-7069

On 7/30/26 11:53, Judd Montgomery wrote: > sed -i -e 's/return Contact_add_blob(c, blob);/return > Contact_add_blob(c, (void*)blob);/' jp-contact.c > > This should be fixed with the pilot-link and jpilot releases that are coming soon. You should make sure jpilot (HEAD) and pilot-link (HEAD) build and get any patches in ASAP. > > Is the pilot-link build script abandoned also? It should be updated for the upcoming release. I  don't think there ever was a pilot-link SlackBuild. But I'll give it a go. I'll keep an eye out for the next jpilot release and submit updated SlackBuilds then  (the pilot-link package will be new). There's an "sbocheck" script that will notice that  jpilot needs an upgrade, so just "sboupgrade jpilot" will take care of it once the new SlackBuild is  up. So no harm  in  a 2.0.3 SlackBuild going out now. SlackBuilds point towards source code release tarballs, so whatever has been fixed or updated in the release is what the SlackBuild user will get. I will remove the short patches I inserted  in the 2.0.3 Slackbuild. (SBO and indeed Slackware itself discourage patches over what's in the official releases, but they're tolerated if they're needed for  a successful build.) Do jpilot and pilot-link depend on one another in any way? We can mark the dependency  in the SlackBuild and the sbotool scripts will do the right  thing. regards Judah >> BTW for some reason SBo categorizes it as "accessibility" but personally >> I think it should be "office" ... before I recommend a change, any >> history there I should know about? > It seems like office to me. > > Judd > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org > -- ===== milgram@cgpp.com 301-257-7069
JM
J. Milgram
Mon, Aug 3, 2026 12:20 PM

OK the 2.0.3 Slackbuild is up:

https://slackbuilds.org/repository/15.0/office/jpilot/

Now binned as "office."

--

milgram@cgpp.com
301-257-7069

OK the 2.0.3 Slackbuild is up: https://slackbuilds.org/repository/15.0/office/jpilot/ Now binned as "office." -- ===== milgram@cgpp.com 301-257-7069