Skip to content
  1. Jan 15, 2022
  2. Jan 14, 2022
    • Josef Schlehofer's avatar
      Merge pull request #17432 from r4sas/i2pd-2.40.0 · 0f0c7b8e
      Josef Schlehofer authored
      i2pd: Update to 2.40.0, update init.rc script, UCI config and Makefile
      0f0c7b8e
    • Josef Schlehofer's avatar
      Merge pull request #17608 from miska/mariadb-owner-fix · c280d64f
      Josef Schlehofer authored
      Mariadb owner fix & sudo dependency
      c280d64f
    • Michal Hrusecky's avatar
      mariadb: Add sudo dependency · 0ffec9bd
      Michal Hrusecky authored
      
      
      During update we use sudo to start an instance. It probably could be
      workarounded, but given the MariaDB size, dependency on sudo shouldn't
      be an issue.
      
      Signed-off-by: default avatarMichal Hrusecky <michal.hrusecky@turris.com>
      0ffec9bd
    • Michal Hrusecky's avatar
      mariadb: Check and fix datadir owner issues during upgrade · b41525ce
      Michal Hrusecky authored
      
      
      If you are migrating to MariaDB package, you might have old datadir
      stored somewhere using different setup with different users. If you
      trust us enough to enable autoupgrade, you probably trust us enough to
      chown your datadir as well. This can prevent some potential issues.
      
      Signed-off-by: default avatarMichal Hrusecky <michal.hrusecky@turris.com>
      b41525ce
    • Paul Spooren's avatar
      CI: fix runtime testing for non master branch · f535d770
      Paul Spooren authored
      
      
      The runtime testing always ran on master branch aka snapshots since the
      branch wasn't passed over to the container execution!
      
      Signed-off-by: default avatarPaul Spooren <mail@aparcar.org>
      f535d770
    • R4SAS I2P's avatar
      i2pd: Update to 2.40.0 and update package sources · ac27ffff
      R4SAS I2P authored
      
      
      * Updating i2pd package to 2.40.0
      * Rewrite Makefile
      * Remove usage of PKG_INSTALL (package's make install)
      * Rewrite init.rc configuration and script
      * Remove '--service' option from init, which only sets datadir to /var/lib/i2pd
      * Use '--datadir' option in init, otherwise datadir changing via uci is not works
      * Update patch for i2pd.conf
      
      Signed-off-by: default avatarR4SAS I2P <r4sas@i2pmail.org>
      ac27ffff
    • Jeffery To's avatar
      Merge pull request #16389 from paper42/apparmor-3.0.3 · eeeb4a41
      Jeffery To authored
      apparmor: cleanup
      eeeb4a41
    • Aleksander Morgado's avatar
      modemmanager: remove 2s timeout before reporting cached events · ab061c8d
      Aleksander Morgado authored
      
      
      When ModemManager is started on boot we may end up with hotplug events
      reported directly to the daemon, plus some others already cached in
      the cache file before the daemon was started.
      
      If the cached events correspond to the same device that is still
      notifying ports directly, we may end up with a modem object created
      before the cached events have been emitted, so the modem may not
      handle all control/data ports it should.
      
      E.g.:
      
        - modem detected
        - hotplug event for wwan0 port, cached as MM not running
        - hotplug event for cdc-wdm0 port, cached as MM not running
        - hotplug event for ttyUSB0, cached as MM not running
        - MM starts
        - hotplug event for ttyUSB1, directly processed as MM is running
        - hotplug event for ttyUSB2, directly processed as MM is running
        - modem object created with ttyUSB1 and ttyUSB2
        - 2s after MM starts, cached events for wwan0, cdc-wdm0 and ttyUSB0
          happen, but are ignored because the modem object has already been
          created
      
      MM expects that ports of the same device are reported with less than
      1500ms in between ports. In other words, if ports are reported more
      than 1500ms after the last reported port, they may get ignored.
      
      If we remove the 2s timeout, the report of the cached events will
      happen as soon as MM starts, which makes it much more likely to happen
      in the timeslot that MM expects for ports of the same device reported.
      The logic is still not perfect, and we may also need to increase that
      1500ms timeout inside MM, but removing the 2s timeout right away here
      makes sense.
      
      This 2s timeout was introduced along with the new wrapper launcher for
      the daemon, it didn't exist before.
      
      Signed-off-by: default avatarAleksander Morgado <aleksander@aleksander.es>
      ab061c8d
  3. Jan 13, 2022