1. 26 Jun, 2018 1 commit
  2. 21 Jun, 2018 1 commit
  3. 20 Jun, 2018 1 commit
  4. 18 Jun, 2018 1 commit
  5. 12 Jun, 2018 1 commit
  6. 08 Jun, 2018 1 commit
  7. 05 Jun, 2018 1 commit
  8. 01 Jun, 2018 1 commit
  9. 30 May, 2018 1 commit
  10. 26 May, 2018 1 commit
  11. 25 May, 2018 1 commit
  12. 23 May, 2018 3 commits
  13. 21 May, 2018 2 commits
  14. 20 May, 2018 1 commit
  15. 18 May, 2018 1 commit
  16. 17 May, 2018 1 commit
  17. 16 May, 2018 1 commit
  18. 15 May, 2018 1 commit
  19. 14 May, 2018 1 commit
  20. 12 May, 2018 1 commit
  21. 09 May, 2018 4 commits
  22. 05 May, 2018 1 commit
  23. 04 May, 2018 1 commit
  24. 01 May, 2018 1 commit
    • Richard Hughes's avatar
      flatpak: Fix multiple flatpak refreshes with new libflatpak · 29d1b0eb
      Richard Hughes authored
      In the latest flatpak release flatpak_installation_update() started returning
      (the arguably correct) ALREADY_INSTALLED error code when we call the method
      flatpak_installation_update(NO_DEPLOY) on an already-downloaded ref.
      
      Since there's no way to know if a commit has been downloaded race-free, just
      handle the error and continue downloading the other refs if required.
      29d1b0eb
  25. 28 Apr, 2018 1 commit
  26. 27 Apr, 2018 1 commit
  27. 25 Apr, 2018 1 commit
  28. 24 Apr, 2018 1 commit
  29. 23 Apr, 2018 2 commits
  30. 22 Apr, 2018 1 commit
  31. 19 Apr, 2018 1 commit
  32. 18 Apr, 2018 1 commit
  33. 17 Apr, 2018 1 commit