Skip to content
Snippets Groups Projects
  1. Apr 02, 2019
    • Emanuele Aina's avatar
      Drop the LXC OSTree containers · eb3c133f
      Emanuele Aina authored
      
      In the past we started a proof-of-concept implementation of self-updating
      OSTree-based LXC containers, but in the end the project which prompted this
      development ended up updating containers from the host.
      
      Since we have no planned use for them, they are not part of any formal release,
      no test is performed on them and since they fell quite behind after the rebase
      to Buster with several parts still commented out, let's drop them altogether.
      
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
      eb3c133f
    • Martyn Welch's avatar
      Rhosydd: Re-enable in SDK (in one place) and add headers to devroot · 9be2d02b
      Martyn Welch authored
      
      Rhosydd had been re-enabled in the target, but not in the SDK or devroot
      where it had also previously been installed. Re-enable it on the SDK, but
      just in 1 place, deleting the second. On the devroot, we should really
      have the relevant library headers rather than rhosydd its self, so add
      libcroesor-0-dev and librhosydd-0-dev to that image instead.
      
      Signed-off-by: default avatarMartyn Welch <martyn.welch@collabora.com>
      9be2d02b
  2. Apr 01, 2019
  3. Mar 29, 2019
    • Martyn Welch's avatar
      Add iptables-persistent and Apertis iptables rules · e122eb00
      Martyn Welch authored
      
      In previous versions of Apertis we were using a modified iptables package
      containing custom scripting/systemd unit to load iptables rules at boot.
      Debian contains the iptables-persistent package which performs this task.
      
      Use this instead of adding the custom scripts to the new version. Add the
      custom rules to an overlay so we don't need to modify the package.
      
      Signed-off-by: default avatarMartyn Welch <martyn.welch@collabora.com>
      e122eb00
  4. Mar 27, 2019
  5. Mar 21, 2019
  6. Mar 15, 2019
  7. Mar 14, 2019
  8. Mar 13, 2019
    • Emanuele Aina's avatar
      Drop the "00000000.0" timestamp defaults · 70ad2ee3
      Emanuele Aina authored
      
      Jenkins is actually defining the full names for every artifact anyway and the
      default is not particularly useful when building stuff locally without passing
      any parameter so let's ensure the default names are sane and drop the
      00000000.0 default.
      
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
      70ad2ee3
    • Emanuele Aina's avatar
      ospack: Disable fqdn resolution for sudo · 17ecfc74
      Emanuele Aina authored
      When opening a new session sudo tries to resolve the fqdn of the host, but that
      introduces a sensible delay if the host does not have a fqdn set up
      appropriately, as it is often the case with development board or when booting
      images in QEMU.
      
      We currently also ship libnss-myhostname which in theory could solve the issue
      at the system level and not just for sudo, but upstream configures it to come
      *after* dns resolution to avoid breaking `hostname --fqdn`, see
      https://github.com/systemd/systemd/issues/1280
      
      
      
      Our use-case is sligthly different and we may configure libnss-myhostname to
      precede dns resolution, but in the meantime keep disabling this in sudo as the
      apertis-customization package used to do.
      
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
      17ecfc74
  9. Mar 12, 2019
  10. Mar 08, 2019
    • Emanuele Aina's avatar
      Fix bootctl install by truncating /etc/machine-id much later · 5383ab91
      Emanuele Aina authored
      
      UEFI images currently fail on `bootctl install`:
      
        bootctl --path=/boot/efi install | Failed to get machine id: No medium found
        Action `Install UEFI bootloader` failed at stage Run, error: exit status 1
      
      This is due to bootctl using the machine-id to set the default entry in
      /boot/loader/loader.conf and the kernel postinst script using the same value to
      create the matching /boot/loader/entries entry.
      
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
      5383ab91
  11. Mar 06, 2019
  12. Mar 05, 2019
    • Emanuele Aina's avatar
      Drop resolv.conf so the right one is created at runtime · b2756878
      Emanuele Aina authored
      When virtualization is available, Debos uses systemd-nspawn to run commands in
      the "chroot".
      
      systemd-nspawn automatically takes care of setting up a working
      /etc/resolv.conf, usually by bind mounting the "host" one:
      
       https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--resolv-conf=
      
      In our case, the host is the VM managed by fakemachine, which is configured to
      use systemd-resolved.
      
      The end result is that the stub /etc/resolv.conf pointing to 127.0.0.53 is
      copied to our rootfs and included in the generated ospack.
      
      This is arguably a weird corner of Debos, the resolv.conf file should really
      not persist out of the chroot:
      
       https://phabricator.apertis.org/T4308
      
      
      
      However, in the past ConnMan used to ship a tmpfiles.d snippet to overwrite
      it with a link to /var/run/connman/resolv.conf but since commit 45ccde23a90c
      shipped in ConnMan 1.36 the snippet has been changed to no longer overwrite
      existing files, causing DNS resolution to fail on our images.
      
      By dropping /etc/resolv.conf at the end of each recipe, after all the
      chroot:true actions, we should be able to ensure that the final artifacts
      don't ship it and at runtime the ConnMan tmpfiles.d snippet should work
       again as intended.
      
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
      b2756878
  13. Mar 04, 2019
  14. Dec 12, 2018
  15. Nov 10, 2018
  16. Nov 09, 2018
  17. Nov 07, 2018
  18. Oct 04, 2018
  19. Sep 05, 2018
  20. Aug 03, 2018
    • Sjoerd Simons's avatar
      Add a more usable user shell · 76ff1269
      Sjoerd Simons authored
      
      Dash is great as a system shell, but it's pretty horrible as a user
      shell as there is no tab completion or history. There are things that
      the busybox ash applet does provide making it a lot more pleasant to
      use, while only less then 500 kilobytes to the ospack.
      
      As an added benefit this gives easy acces to the wget/nc/ip busybox
      applets.
      
      Signed-off-by: default avatarSjoerd Simons <sjoerd.simons@collabora.co.uk>
      76ff1269
  21. Jul 12, 2018
  22. Jun 19, 2018
  23. Jun 13, 2018
  24. Jun 12, 2018
Loading