1. 19 Feb, 2019 1 commit
    • Frédéric Dalleau's avatar
      Disable u-boot-distro test · 8a723d4e
      Frédéric Dalleau authored
      The patch "" is a fix on a the Guardian board because that board does
      not have a separate boot partition, the deployment occurs in a "/boot"
      folder on the main partition. Thus the boot configuration needs to be
      modified to account for the new location.
      This is causing a problem in the uboot-distro test because the generic
      admin test is deployed on a single partition but not expecting this
      path change
      Signed-off-by: 's avatarFrédéric Dalleau <frederic.dalleau@collabora.com>
      8a723d4e
  2. 15 Feb, 2019 9 commits
    • Martyn Welch's avatar
      Determine whether /boot resides on the / partition · 7c02210a
      Martyn Welch authored
      We need to know whether /boot resides on the boot partition or not when
      writing the U-Boot configuration. If /boot is on a separate partition then
      we do not need to include this directory in the locations of the boot
      components. If /boot is on the root partition then this needs to be
      specified or the boot components will not be found and boot will fail.
      Signed-off-by: Martyn Welch's avatarMartyn Welch <martyn.welch@collabora.co.uk>
      
      Gbp-Pq: Name Determine-whether-boot-resides-on-the-partition.patch
      7c02210a
    • Martyn Welch's avatar
      Add in rollback generation · 0ba0e7d4
      Martyn Welch authored
      We wish to provide a second config that can be used in the event that the
      latest upgrade fails to boot successfully (to be determined by system
      specific metrics). Cause OSTree to generate an alternative config that
      defaults to the alternative OSTree image that the bootloader can swtich to
      when a failure state is detected.
      Signed-off-by: Martyn Welch's avatarMartyn Welch <martyn.welch@collabora.co.uk>
      
      Gbp-Pq: Name Add-in-rollback-generation.patch
      0ba0e7d4
    • Sjoerd Simons's avatar
      Add bootloader configuration for sd-boot · a13ca8c1
      Sjoerd Simons authored
      SD-boot bootloader support. Assumes the ESP is at /boot/efi and uses the
      existance of loader/entries on the ESP to detect of sd-boot is in use.
      Signed-off-by: 's avatarSjoerd Simons <sjoerd@luon.net>
      
      Gbp-Pq: Name 0001-Add-bootloader-configuration-for-sd-boot.patch
      a13ca8c1
    • Sjoerd Simons's avatar
      Add test for distro u-boot · d97c9abc
      Sjoerd Simons authored
      Gbp-Pq: Name Add-test-for-distro-u-boot.patch
      d97c9abc
    • Sjoerd Simons's avatar
      u-boot distro configuration loader · 039256b0
      Sjoerd Simons authored
      
      Gbp-Pq: Name u-boot-distro-configuration-loader.patch
      039256b0
    • Sjoerd Simons's avatar
      tests: sysroot: Test deployment of dtb files · c7701a0b
      Sjoerd Simons authored
      There are two conventions for the layout of the dtb directory, one is to
      just have all the dtbs at the top-level (e.g. done on 32 bit arm) the
      other is to have them in subdirectories per vendor (e.g. done on 64 bit
      arm). Extend the test for dtb using both strategies and while there also
      check the initramfs is all happy.
      
      Gbp-Pq: Name tests-sysroot-Test-deployment-of-dtb-files.patch
      c7701a0b
    • Sjoerd Simons's avatar
      sysroot: Also deploy device-tree files · a1faf321
      Sjoerd Simons authored
      Most embedded system need a device-tree file to go along with the kernel
      and the initramfs. This file is a description of the non-introspectable
      parts of the hardware.
      
      Currently with ostree the only way to use it is to use the legacy "appended
      dtb" method, which is basically just slapping a specific boards dtb at
      the end of the kernel binary. Which is fine when creating deployments for a
      single board, but not very useful when targetting a bigger selection of
      boards.
      
      Add support to ostree sysroot deploy to apart from the kernel and
      initramfs also deploy the directory with dtbs directory.
      
      Gbp-Pq: Name sysroot-Also-deploy-device-tree-files.patch
      a1faf321
    • Sjoerd Simons's avatar
      Add fdtdir bootconfig entry · 3fa38e4e
      Sjoerd Simons authored
      Gbp-Pq: Name Add-fdtdir-bootconfig-entry.patch
      3fa38e4e
    • Frédéric Dalleau's avatar
      u-boot: Add fdtdir option when generating uEnv.txt · 6a50ebc4
      Frédéric Dalleau authored
      u-boot config generator does not create fdtdir entry in uEnv.txt.
      Add fdtdir, as done in u-boot-distro.
      Signed-off-by: Frédéric Dalleau's avatarFrédéric Dalleau <frederic.dalleau@collabora.co.uk>
      
      Gbp-Pq: Name 0001-u-boot-Add-fdtdir-option-when-generating-uEnv.txt.patch
      6a50ebc4
  3. 14 Feb, 2019 3 commits
    • Simon McVittie's avatar
      Skip test-pull-repeated during CI · ee70d3c7
      Simon McVittie authored
      This test is expected to fail a small proportion of the time. During
      the build of ostree 2018.7-1 in Debian, it seems we were unlucky on
      s390x. Non-deterministic tests are also problematic for autopkgtest,
      where they can gate migration of our dependencies like GLib, so skip
      this test unless the caller has opted-in to non-deterministic tests.
      
      It would be appropriate to enable this test in environments where
      failures can easily be retried and are not disruptive to other
      packages.
      Signed-off-by: 's avatarSimon McVittie <smcv@debian.org>
      
      Gbp-Pq: Topic debian
      Gbp-Pq: Name Skip-test-pull-repeated-during-CI.patch
      ee70d3c7
    • Simon McVittie's avatar
      Imported Debian patch 2018.9.1-1 · 8cb69dec
      Simon McVittie authored
      8cb69dec
    • Frédéric Dalleau's avatar
      Imported Upstream version 2018.9.1 · 0844ccb5
      Frédéric Dalleau authored
      0844ccb5
  4. 28 Sep, 2018 3 commits
  5. 27 Sep, 2018 2 commits
  6. 19 Sep, 2018 2 commits
  7. 08 Mar, 2018 2 commits
  8. 24 Jan, 2018 1 commit
  9. 23 Jan, 2018 3 commits
  10. 20 Jul, 2017 5 commits
  11. 19 Jul, 2017 2 commits
  12. 18 Jul, 2017 6 commits
  13. 06 Jul, 2017 1 commit