1. 30 Sep, 2021 9 commits
  2. 23 Sep, 2021 1 commit
  3. 21 Sep, 2021 1 commit
  4. 04 Sep, 2021 1 commit
  5. 02 Sep, 2021 3 commits
  6. 11 Aug, 2021 1 commit
  7. 20 Jul, 2021 1 commit
  8. 14 Jul, 2021 1 commit
    • Valters Jansons's avatar
      debian: Clean up 0.9.7 changelog · 10d357f8
      Valters Jansons authored
      - Update for maintainer name and email address, as to reflect who
        actually prepared this release of the package. It was not me,
        but I was selected due to having the first commit on the package.
      
        To mitigate against this, when running the `debchange --release`
        (`dch -r`) command, environment variables DEBFULLNAME and DEBEMAIL
        should be configured properly for the current user.
      
      - Removal of NMU comment on my name, as I am not really doing a
        non-maintainer upload. I would say the 'NMU' message is fairly
        useless on this repository, as it is self-maintained here.
      Signed-off-by: default avatarValters Jansons <valter.jansons@gmail.com>
      Signed-off-by: default avatarMichael Tremer <michael.tremer@ipfire.org>
      10d357f8
  9. 11 Jul, 2021 6 commits
  10. 09 Jul, 2021 2 commits
  11. 20 Jun, 2021 2 commits
  12. 11 Jun, 2021 1 commit
    • Valters Jansons's avatar
      debian: Add dpkg's symbols file · 87779e52
      Valters Jansons authored
      There are muiltiple standards of listing symbols throughout the Linux
      ecosystem. For `dpkg`, a d/package.symbols file tracks symbols, and in
      which version they were added in. This is then used to allow dependency
      checks/resolution.
      
      See man:dpkg-gensymbols(1) for details about the generation,
      and man:dpkg-shlibdeps(1) for how the symbols file ends up being used.
      
      This commit adds a d/libloc1.symbols file, containing the current state
      of the symbols. There is now also a d/gensymbols.sh script, which
      generates this symbols file. The script tries to determine what Git
      tags need to be checked for changes in symbols, by looking at current
      maximum version referenced in symbols file.
      
      After checking tags, the current revision is also processed, to allow
      building symbols file for a yet unreleased version (prior to tagging it).
      This is to allow symbols changes to be included in a tag.
      
      Do keep in mind, that for the workflow above, when running the script,
      the d/changelog file should contain information about what version the
      current revision will be released at (potentially tagged as UNRELEASED
      in the d/changelog file). Otherwise, if there is no version tagged,
      the `dpkg-gensymbols` tool will use the old version information,
      in turn incorrectly attributing new symbols to an old version.
      Signed-off-by: default avatarMichael Tremer <michael.tremer@ipfire.org>
      87779e52
  13. 10 Jun, 2021 4 commits
  14. 07 Jun, 2021 3 commits
  15. 25 May, 2021 2 commits
  16. 18 May, 2021 1 commit
  17. 14 May, 2021 1 commit