1. Forum
  2. DOVE-Net
  3. Synchronet Sysops Only

  • gcc warnings after upgrading mosquitto to 2.1.2

    From Nick Boel@VERT to GitLab note in main/sbbs on Sun Aug 23 07:33:19 2026
    https://gitlab.synchro.net/main/sbbs/-/issues/1119#note_10202

    Not sure why it took me 4 months to actually dig into this a tiny bit to actually see and try to understand this - and I imagine it's probably already known by the devs, but I noticed /usr/include/mqtt_protocol.h contains:

    ```
    #include <mosquitto/mqtt_protocol.h>
    #warning "Please replace '#include <mqtt_protocol.h> with #include <mosquitto.h>"
    ```

    /usr/include/mosquitto/mqtt_protocol.h contains everything needed, and then /usr/include/mosquitto.h includes /usr/include/mosquitto/mqtt_protocol.h.

    So, is this just a warning that has come up in the latest version of mqtt (ie, not much to do with Synchronet except that Synchronet is still probably using /usr/include/mqtt_protocol.h at this point) all because mqtt_protocol.h is being moved to a new location?

    I suppose this would lead me to believe this issue has been left open as a reminder that once mqtt is updated in more "stable" distros that this change should be made?

    If so, kudos to upstream for giving plenty of fair warning (pun intended)!

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell@VERT to GitLab issue in main/sbbs on Fri Sep 11 17:30:33 2026
    close https://gitlab.synchro.net/main/sbbs/-/issues/1119

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Nigel Reed@VERT to GitLab note in main/sbbs on Tue Sep 15 18:07:47 2026
    https://gitlab.synchro.net/main/sbbs/-/issues/1119#note_10363


    ```
    <nelgin> 2 | #warning "Please replace '#include <mqtt_protocol.h> with #include <mosquitto.h>"
    <nelgin> | ^~~~~~~
    <nelgin> /usr/include/mqtt_protocol.h:2:2: warning: #warning "Please replace '#include <mqtt_protocol.h> with #include <mosquitto.h>" [-Wcpp]
    <DigitalMan> best to deal with that when I have a system that reproduces it
    ```

    I reported this issue on May 4th on IRC and was dismissed. Must be nice to have status.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell@VERT to GitLab note in main/sbbs on Tue Sep 15 20:50:35 2026
    https://gitlab.synchro.net/main/sbbs/-/issues/1119#note_10370

    One person reported the issue here (how it's supposed to be done) and another fixed it. You did neither. Nothing to do with status.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Nigel Reed@VERT to GitLab note in main/sbbs on Tue Sep 15 21:47:18 2026
    https://gitlab.synchro.net/main/sbbs/-/issues/1119#note_10371

    I read your comment as "if I cannot produce the warning then I'm not going to fix it" so I didn't bother. If you told me to open an issue then I would have.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell@VERT to GitLab note in main/sbbs on Tue Sep 15 21:57:19 2026
    https://gitlab.synchro.net/main/sbbs/-/issues/1119#note_10372

    I didn't fix it, someone else id (that presumably *could* reproduce it).

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell@VERT to GitLab note in main/sbbs on Tue Sep 15 21:57:28 2026
    https://gitlab.synchro.net/main/sbbs/-/issues/1119#note_10372

    I didn't fix it, someone else did (that presumably *could* reproduce it).

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net