1. 01 Apr, 2021 4 commits
    • Karel Koci's avatar
      lists: move some of the IPv6 protocols to base-min and drop the rest · ed9ce518
      Karel Koci authored
      There is no reason to have IPv6 separate from other network protocols.
      They should be in same place and installed together.
      Preserved protocols:
      * ds-lite: it is widely deployed over the world so it is probably a must
      * 6in4: common tunneling protocol used to get IPv6 to networks without
        it. As a way to push IPv6 we should include it.
      * 6rd: a replacement for 6to4 in some way. It is a way to provide IPv6
        in IPv4 only network on ISP's network. There seems to be minority of
        ISPs actually using it.
      Removed protocols:
      * 6to4: marked as deprecated.
    • Karel Koci's avatar
      lists: move zone info to base-min · 2ae0692c
      Karel Koci authored
      Zone info is required to make local time work. It is not essential but
      not working local time is very weird and in reality this is about two
      megabytes of storage (which is nothing for us). Having it in minimal
      base installation thus is not a burden.
    • Karel Koci's avatar
      lists: move opkg from base-min to base · 5db588e9
      Karel Koci authored
      With removed updater from base-min the opkg should be removed as well as
      it serves the same purpose and is not essential for hardware
      Again to recapitulate the idea: The only self-updating and thus self
      package installing base is the base. Any other base either have to
      include base.lua or root based on it has to be managed externally (out
      of root in updater or --dest in opkg).
    • Karel Koci's avatar
      lists: remove updater from minimal installation · 8c55c7fe
      Karel Koci authored
      The minimal installation should be just minimal hardware support. That
      does not include updater. It also makes sense to have updater included
      in base.lua as that is the base script updater-ng uses.
      The full idea of this is that updater can be used to build image and
      externally manage root with any base script but only full base should
      contain self-updating.
  2. 29 Mar, 2021 5 commits
  3. 27 Mar, 2021 1 commit
  4. 26 Mar, 2021 1 commit
  5. 25 Mar, 2021 2 commits
  6. 22 Mar, 2021 2 commits
  7. 20 Mar, 2021 2 commits
  8. 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
  9. 13 Mar, 2021 2 commits
  10. 05 Mar, 2021 5 commits
  11. 04 Mar, 2021 5 commits
  12. 02 Mar, 2021 1 commit
  13. 23 Feb, 2021 3 commits
  14. 19 Feb, 2021 6 commits
    • Karel Koci's avatar
      gitlab-ci: refactor and cover all boards · 8c88e9d0
      Karel Koci authored and Josef Schlehofer's avatar Josef Schlehofer committed
    • 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.
    • 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.
    • 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
    • Karel Koci's avatar