1. 19 Oct, 2019 3 commits
  2. 09 Oct, 2019 1 commit
  3. 07 Oct, 2019 2 commits
  4. 06 Oct, 2019 2 commits
  5. 05 Oct, 2019 2 commits
  6. 19 Aug, 2019 1 commit
  7. 18 Aug, 2019 1 commit
    • Eli Schwartz's avatar
      Move permission for LIST_COMMENTS to dev/tu block · 3ac958ac
      Eli Schwartz authored
      In commit 3578e77a we implemented
      listing of comments from the account details page , but this was
      intended to only be available to TUs and Devs. As the comment says:
      "display the comment list if they're a TU/dev"
      
      The credential checking code, however, set this credential for all
      users, contrary to the intention of the commit.
      
      In order to preserve the ability to list a person's own comments, also
      declare the allowed uids based on the profile being viewed.
      3ac958ac
  8. 30 Jul, 2019 1 commit
  9. 30 Jun, 2019 1 commit
  10. 25 May, 2019 2 commits
  11. 24 May, 2019 2 commits
  12. 28 Apr, 2019 2 commits
  13. 08 Feb, 2019 1 commit
  14. 21 Jan, 2019 1 commit
  15. 14 Jan, 2019 1 commit
  16. 26 Oct, 2018 1 commit
  17. 17 Oct, 2018 1 commit
    • Vladimir Panteleev's avatar
      pkg_comments.php: Make comment timestamps link to the comment · f046dd58
      Vladimir Panteleev authored and Eli Schwartz's avatar Eli Schwartz committed
      As of today, there is no easy way to obtain a link to a specific
      comment on a package page.
      
      Many implementations of forums and comment systems today seem to
      follow a convention where a comment's timestamp is an unobtrusive link
      to the comment itself. Some examples are:
      
      - phpBB (e.g. bbs.archlinux.org)
      - GitHub
      - Disqus
      - Discourse
      
      This patch adopts this convention as well, by making the timestamp a
      link to the comment.
      f046dd58
  18. 12 Aug, 2018 4 commits
  19. 06 Aug, 2018 3 commits
  20. 09 Jul, 2018 1 commit
    • Eli Schwartz's avatar
      Fix regression in translating anything at all · c8d99bac
      Eli Schwartz authored and Lukas Fleischer's avatar Lukas Fleischer committed
      In commit 840ee20f
      
       (Rename translation resources from aur to aurweb,
      2018-07-07) the translations file was renamed but we never actually
      switched to using the renamed translations.
      
      As a result, every single push to the AUR contains the following
      traceback:
      
          remote: Traceback (most recent call last):
          remote:   File "/usr/bin/aurweb-notify", line 11, in <module>
          remote:     load_entry_point('aurweb==4.7.0', 'console_scripts', 'aurweb-notify')()
          remote:   File "/usr/lib/python3.6/site-packages/aurweb-4.7.0-py3.6.egg/aurweb/scripts/notify.py", line 541, in main
          remote:   File "/usr/lib/python3.6/site-packages/aurweb-4.7.0-py3.6.egg/aurweb/scripts/notify.py", line 69, in send
          remote:   File "/usr/lib/python3.6/site-packages/aurweb-4.7.0-py3.6.egg/aurweb/scripts/notify.py", line 56, in get_body_fmt
          remote:   File "/usr/lib/python3.6/site-packages/aurweb-4.7.0-py3.6.egg/aurweb/scripts/notify.py", line 192, in get_body
          remote:   File "/usr/lib/python3.6/site-packages/aurweb-4.7.0-py3.6.egg/aurweb/l10n.py", line 14, in translate
          remote:   File "/usr/lib/python3.6/gettext.py", line 514, in translation
          remote:     raise OSError(ENOENT, 'No translation file found for domain', domain)
          remote: FileNotFoundError: [Errno 2] No translation file found for domain: 'aur'
      Signed-off-by: Eli Schwartz's avatarEli Schwartz <eschwartz@archlinux.org>
      Signed-off-by: Lukas Fleischer's avatarLukas Fleischer <lfleischer@archlinux.org>
      c8d99bac
  21. 07 Jul, 2018 4 commits
  22. 20 May, 2018 1 commit
  23. 18 May, 2018 1 commit
    • Eli Schwartz's avatar
      git-update: accept any arch in arch-dependent metadata · 16795eaf
      Eli Schwartz authored and Lukas Fleischer's avatar Lukas Fleischer committed
      
      
      Currently we hardcode the architectures the official repos historically
      supported, which seems both inefficient because of hardcoding, and
      simply wrong, because many packages support various ARM platforms too.
      
      If we were to say "only officially supported arches will be supported in
      the AUR" we'd have to disable i686, which seems silly and arbitrarily
      restrictive. Also there's better places to implement such a blacklist
      (via die_commit in the main loop, via a config option to list supported
      arches, would make much more sense in terms of logic).
      
      As for the metadata extraction itself, there's no reason to hardcode the
      arches to check for at all. We can get this information too, from the
      .SRCINFO itself. Detecting this dynamically is not incompatible with a
      blacklist, should we ever decide to implement such a thing.
      Signed-off-by: Eli Schwartz's avatarEli Schwartz <eschwartz@archlinux.org>
      Signed-off-by: Lukas Fleischer's avatarLukas Fleischer <lfleischer@archlinux.org>
      16795eaf
  24. 17 May, 2018 1 commit