1. 02 Jan, 2022 1 commit
  2. 20 Nov, 2021 1 commit
    • Morgan Adamiec's avatar
      Update mailing list url · b0a2fd75
      Morgan Adamiec authored
      change pacman-dev@archlinux.org to pacmandev@lists.archlinux.org
      
      Most of this is copyright notices but this also fixes FS#72129 by
      updating the address in docs/index.asciidoc.
      b0a2fd75
  3. 01 Mar, 2021 1 commit
  4. 10 Feb, 2020 1 commit
  5. 23 Oct, 2019 1 commit
  6. 13 May, 2018 1 commit
    • Eli Schwartz's avatar
      Remove all modelines from the project · 860e4c49
      Eli Schwartz authored and Allan McRae's avatar Allan McRae committed
      
      
      Many of these are pointless (e.g. there is no need to explicitly turn on
      spellchecking and language dictionaries for the manpages by default).
      
      The only useful modelines are the ones enforcing the project coding
      standards for indentation style (and "maybe" filetype/syntax, but
      everything except the asciidoc manpages and makepkg.conf is already
      autodetected), and indent style can be applied more easily with
      .editorconfig
      
      Signed-off-by: Eli Schwartz's avatarEli Schwartz <eschwartz@archlinux.org>
      Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
      860e4c49
  7. 14 Mar, 2018 1 commit
  8. 04 Jan, 2017 1 commit
  9. 04 Jan, 2016 1 commit
  10. 01 Feb, 2015 1 commit
  11. 28 Dec, 2014 2 commits
  12. 24 Dec, 2014 1 commit
  13. 06 Jan, 2014 1 commit
  14. 15 Nov, 2013 1 commit
  15. 21 Aug, 2013 2 commits
  16. 07 Oct, 2011 1 commit
  17. 23 Aug, 2011 1 commit
    • Dan McGee's avatar
      vercmp: ensure 2.0a and 2.0.a do not compare equal · 30d978a9
      Dan McGee authored
      
      
      We had this interesting set of facts conundrum, according to vercmp
      return values:
          2.0a <  2.0
          2.0  <  2.0.a
          2.0a == 2.0.a
      
      This introduces a code change that ensures '2.0a < 2.0.a' as would be
      expected by the first two comparisons. Unfortunately this stays us a bit
      further from upstream RPM code, but those are the breaks (in RPM, the
      versions involving 'a' do in fact compare the same, but they are both
      greater than the bare '2.0').
      
      Signed-off-by: default avatarDan McGee <dan@archlinux.org>
      30d978a9
  18. 08 Aug, 2011 1 commit
  19. 05 Apr, 2011 1 commit
  20. 28 Mar, 2011 1 commit
  21. 22 Jan, 2011 1 commit
    • Dan McGee's avatar
      Allow version comparison to contain epoch specifier · 5c46ba14
      Dan McGee authored
      
      
      Adapting from RPM, follow the [epoch:]version[-release] syntax. We can also
      borrow some of their parsing code for our purposes (thanks!).  Add some new
      tests to our vercmp shell script tester for epoch comparisons, and then make
      the code work with these newfangled epoch specifiers.
      
      Signed-off-by: default avatarDan McGee <dan@archlinux.org>
      5c46ba14
  22. 02 Jun, 2010 2 commits
  23. 25 Jul, 2008 2 commits
    • Dan McGee's avatar
      vercmptest: fix binary existence check · 3bf94489
      Dan McGee authored
      
      
      Signed-off-by: default avatarDan McGee <dan@archlinux.org>
      3bf94489
    • Dan McGee's avatar
      Fix vercmp and add additional tests · 5e4882df
      Dan McGee authored
      
      
      This vercmp issue has been a sticking point but this should resolve many of
      the issues that have come up. Only a few minor code changes were necessary
      to get the behavior we desired, and this version appears to beat any other
      vercmp rendition on a few more cases added in this commit.
      
      This commit passes all 58 vercmp tests currently out there. Other 'fixes'
      still fail on a few tests, namely these ones:
      
      test: ver1: 1.5.a ver2: 1.5 ret: -1 expected: 1
        ==> FAILURE
      test: ver1: 1.5 ver2: 1.5.a ret: 1 expected: -1
        ==> FAILURE
      test: ver1: 1.5-1 ver2: 1.5.b ret: 1 expected: -1
        ==> FAILURE
      test: ver1: 1.5.b ver2: 1.5-1 ret: -1 expected: 1
        ==> FAILURE
      4 of 58 tests failed
      
      Signed-off-by: default avatarDan McGee <dan@archlinux.org>
      5e4882df
  24. 30 May, 2008 1 commit
    • Dan McGee's avatar
      Fix versioncmp regression after update · 54e1e3e6
      Dan McGee authored
      Commit 84283672
      
       introduced the regression,
      and a previous commit introduced the vercmptest.sh test script to track down
      these issues. This commit solves the problem by removing the previous
      attempt at locating the pkgrel portions and replacing it with something that
      performs the correct logic.
      
      While tracking down everything I needed to, I also found a mistake in one of
      the pactests which is fixed here as well as increased the functionality and
      verbosity of the vercmptest script to both print out each test it is running
      as well as automatically run the mirror of each test case.
      
      Signed-off-by: default avatarDan McGee <dan@archlinux.org>
      54e1e3e6
  25. 29 May, 2008 1 commit
    • Dan McGee's avatar
      Add simple vercmp test script · 2cd0a87b
      Dan McGee authored
      Commit 84283672
      
       updated the versioncmp code
      in libalpm. Unfortunately for us, it also introduced the regression that
      becomes apparant with the following upgrade:
      
      warning: sonata: local (1.5-2) is newer than extra (1.5.1-2)
      
      Add a vercmptest.sh test script that is run during the make check phase
      which now points out three regressions in the version comparison function
      that will need fixing. All current tests in this script pass with the old
      versioncmp code.
      
      Signed-off-by: default avatarDan McGee <dan@archlinux.org>
      2cd0a87b