1. 26 Mar, 2021 1 commit
  2. 25 Mar, 2021 2 commits
  3. 22 Mar, 2021 2 commits
  4. 20 Mar, 2021 2 commits
  5. 18 Mar, 2021 1 commit
    • Karel Koci's avatar
      lists/base-min: add urandom-seed · 8012f63b
      Karel Koci authored
      This package seeds /dev/urandom on boot with value generated on
      shutdown. This prevents predictable values to be generated after boot
      up.
      8012f63b
  6. 13 Mar, 2021 2 commits
  7. 05 Mar, 2021 5 commits
  8. 04 Mar, 2021 5 commits
  9. 02 Mar, 2021 1 commit
  10. 23 Feb, 2021 3 commits
  11. 19 Feb, 2021 7 commits
    • Karel Koci's avatar
      gitlab-ci: refactor and cover all boards · 8c88e9d0
      Karel Koci authored
      8c88e9d0
    • Josef Schlehofer's avatar
      GitLab CI: add generate and check medkit · 012d9a3b
      Josef Schlehofer authored
      We are testing in Gitlab CI if patches apply and also that package
      list can be generated and then we checked them. We should try to
      generate and check for medkit as well.
      
      Because someone on IRC (#turris on Freenode) complained that he could not
      generate medkit.
      
      It helped me to reproduce his issue with Gitlab CI and he didn't have installed pkg-config (dependency for Updater-ng, which is used to generate medkits), because it was working for me locally and also it works on our CI, but it does not provide any logs to public.
      This can help users to know if medkits can be generated.
      012d9a3b
    • Josef Schlehofer's avatar
    • Josef Schlehofer's avatar
      .gitlab-ci: Apply patches for Turris MOX · ea4df0f2
      Josef Schlehofer authored
      In some cases patches does not apply for some devices, let's try to
      test Turris MOX as well.
      ea4df0f2
    • Josef Schlehofer's avatar
      .gitlab.ci: refactor package lists and add verify stage · 8e9113ab
      Josef Schlehofer authored
      There was an added test for package lists, but it runs twice.
      If you check in the previous changes then there are two jobs, which
      do practically the same. In generate pkglists there are generated
      lists with debug parameter, but we don't work with that anymore, which
      is wrong. And because of that, we had another job check generated
      pkglists, where we are generating lists once again and then we are
      checking if those have been generated.
      
      Solution: Don't waste hardware resources and run it just once. When package lists
      are generated then the artifact is uploaded and uses in the next job in
      the next stage
      8e9113ab
    • Karel Koci's avatar
      acc2a570
    • Karel Koci's avatar
      Revert "compile_pkgs: suppress warning on new git versions about initial branch" · fd114075
      Karel Koci authored
      This reverts commit 0c0b95f3.
      
      The feature, which was introduced, was added to Git in version 2.28.
      Thus unfortunately, it is not present in Git version like 2.20.1, which
      is used in distributions like Debian Strech. It throws the following
      error message: error: unknown option `initial-branch=master'.
      fd114075
  12. 18 Feb, 2021 3 commits
    • Karel Koci's avatar
      Merge branch 'hotfix/compile_pkgs' into hbl · 69c1f007
      Karel Koci authored
      69c1f007
    • Karel Koci's avatar
      compile_pkgs: suppress warning on new git versions about initial branch · 0c0b95f3
      Karel Koci authored
      New versions of git complain that the initial branch name is not
      specified. It suggests specification in config but in our case the
      better option is to not rely on user and just suppress this warning by
      explicitly specifying master.
      0c0b95f3
    • Karel Koci's avatar
      Add project specific gitconfig and mmore · b8f9963d
      Karel Koci authored
      This is a pull and modification of changes introduced to
      turris-os-packages 848af2d4e4cd4c8591fbe8b525d303570e079a46.
      
      It introduces primarily project specific config that includes new
      scripts and hooks. To enable it in local repository it is just:
        git config --local include.path ../.gitconfig
      
      The hook checks if commit being pushed to Gitlab server is correct.
      There are multiple checks:
      * Check naming convention
      * Check base (hbk vs hbl vs hbd)
      * Protects against forgotten hbl and hbd pushes when pushing hbk or hbl
      
      In terms of aliases this adds:
      git new-mr:
        This opens web browser with new merge request on https://gitlab.nic.cz
        for current branch.
      git new-branch:
        This creates new branch interactively and should help users with
        naming convention.
      b8f9963d
  13. 17 Feb, 2021 6 commits