1. 26 Oct, 2018 1 commit
  2. 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
  3. 12 Aug, 2018 4 commits
  4. 06 Aug, 2018 3 commits
  5. 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
  6. 07 Jul, 2018 4 commits
  7. 20 May, 2018 1 commit
  8. 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
  9. 17 May, 2018 5 commits
  10. 16 May, 2018 1 commit
  11. 12 May, 2018 4 commits
  12. 11 May, 2018 1 commit
    • Eli Schwartz's avatar
      Use a link to accept orphan requests · 0ffa0679
      Eli Schwartz authored and Lukas Fleischer's avatar Lukas Fleischer committed
      
      
      Currently, a form is used instead of a link. This forwards to a
      confirmation page, and currently drops the "via" parameter in the
      process.
      
      As a result, accepted orphan requests usually show:
      
          Request #XXXXXX has been accepted automatically by the Arch User
          Repository package request system:
      
          The user YYYYYYY disowned the package.
      
      This is wrong, and should show (will show, if you manually add it or use
      the close button instead of the accept button):
      
          Request #XXXXXX has been rejected by YYYYYYY [1]:
      
      Fixes FS#56606.
      Signed-off-by: Eli Schwartz's avatarEli Schwartz <eschwartz@archlinux.org>
      Signed-off-by: Lukas Fleischer's avatarLukas Fleischer <lfleischer@archlinux.org>
      0ffa0679
  13. 10 May, 2018 2 commits
  14. 22 Apr, 2018 1 commit
    • Eli Schwartz's avatar
      config: allow reading both the defaults file and the modified config · 97c5bcec
      Eli Schwartz authored and Lukas Fleischer's avatar Lukas Fleischer committed
      
      
      In the process, rename config.proto to config.defaults (because that is
      what it is now).
      
      Also use dict.get('key', default_value) when querying os.environ, rather
      than an if block, as it is more pythonic/readable/concise, and reduces
      the number of dict lookups.
      
      This change allows aurweb configuration to be done via either:
      - copying config.defaults to config and modifying values
      - creating a new config only containing modified values, next to a
        config.defaults containing unmodified values
      
      The motivation for this change is to enable ansible configuration in our
      flagship deployment by storing only changed values, and deferring to
      config.defaults otherwise.
      
      A side benefit is, it is easier to see what has changed by inspecting
      only the site configuration file.
      
      If a config.defaults file does not exist next to $AUR_CONFIG or in
      $AUR_CONFIG_DEFAULTS, it is ignored and *all* values are expected to
      live in the modified config file.
      Signed-off-by: Eli Schwartz's avatarEli Schwartz <eschwartz@archlinux.org>
      Signed-off-by: Lukas Fleischer's avatarLukas Fleischer <lfleischer@archlinux.org>
      97c5bcec
  15. 08 Apr, 2018 1 commit
  16. 21 Mar, 2018 1 commit
  17. 20 Mar, 2018 1 commit
  18. 14 Mar, 2018 2 commits
  19. 13 Mar, 2018 1 commit
  20. 10 Mar, 2018 2 commits
  21. 24 Feb, 2018 2 commits