This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The official pacman repository".

The branch, master has been updated
       via  5b51dbb11e2087e1055be24b486502be806b5e13 (commit)
       via  e760c4f4784c7e7b59717cd10c56dac04f175b73 (commit)
       via  081f64aea3aa7df13f1ccd1da601075abab6b1ba (commit)
       via  0969c2e700c6bd7f855ddfa4e73b6ccd71911ff5 (commit)
       via  56f0cf9d157bc2b902e4590364e2926c2f169b05 (commit)
       via  96e023c7bd0b1069878667278a45a34476c42472 (commit)
       via  e27a8c9ae323c275b0c3503d6a6ea18b639f4dc6 (commit)
       via  9451b2e4f23a3c566fcfe3420c379b3cb3eb1f90 (commit)
       via  901e4aa5c203f605e9d527e474821426a40e5cea (commit)
       via  282eeadc68fec1da8651d0c65ad0dfebd11a9c7f (commit)
      from  9609c0f1351a73e06edcfda1494a41d66c51dcb5 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 5b51dbb11e2087e1055be24b486502be806b5e13
Author: Xavier Chantry <[EMAIL PROTECTED]>
Date:   Sat May 31 15:06:30 2008 +0200

    Cleanup of _alpm_pkg_compare_versions.
    
    * Change the return values to be more informative.
    
    It was previously boolean, only indicating if a sync package was newer than
    a local package.
    
    Now it is a simple wrapper to vercmp, handling the force flag.
    
    * Remove the verbose output from _alpm_pkg_compare_versions.
    
    The "force" message is not so useful.
    The "package : local (v1) is newer than repo (v2)" message can be moved to
    -Su operation.
    For the -S operation, it is better to have something like :
    "downgrading package from v1 to v2"
    
    * Don't display the "up to date -- skipping" and "up to date -- 
reinstalling"
    messages, when the local version is newer than the sync one.
    
    * Fix the behavior of --needed option to not skip a target when the local
    version is newer, and clarify its description.
    
    * Add a new alpm_pkg_has_force function
    
    This allows us to access the pkg->force field like any other package fields.
    
    Signed-off-by: Xavier Chantry <[EMAIL PROTECTED]>
    Signed-off-by: Dan McGee <[EMAIL PROTECTED]>

commit e760c4f4784c7e7b59717cd10c56dac04f175b73
Author: Xavier Chantry <[EMAIL PROTECTED]>
Date:   Wed Aug 20 23:17:02 2008 +0200

    download : disable progressbar when total is unknown.
    
    This is a work around for FS#8725.
    
    There are some bad combination of proxies and mirrors where the Content
    Length is not returned, and thus the progress bar can't be displayed
    correctly.
    
    Dan: Note that this patch also adds a "downloading" message when the
    progress bar is disabled, which was formerly not indicated at all in the
    output.
    
    Signed-off-by: Xavier Chantry <[EMAIL PROTECTED]>
    Signed-off-by: Dan McGee <[EMAIL PROTECTED]>

commit 081f64aea3aa7df13f1ccd1da601075abab6b1ba
Author: Xavier Chantry <[EMAIL PROTECTED]>
Date:   Thu Aug 21 09:09:16 2008 +0200

    fix HACKING asciidoc file.
    
    The HACKING file seemed to be broken :
    http://archlinux.org/pacman/HACKING.html
    
    And indeed, running asciidoc HACKING issued a number of warnings :
    
    WARNING: HACKING: line 27: missing [paradef-default] C-style entry
    type:  numbered : expected  1  got  3
    WARNING: HACKING: line 44: list item 3 out of sequence
    WARNING: HACKING: line 49: missing [paradef-default] C-style entry
    type:  numbered : expected  2  got  4
    WARNING: HACKING: line 62: list item 4 out of sequence
    type:  numbered : expected  3  got  5
    WARNING: HACKING: line 69: list item 5 out of sequence
    type:  numbered : expected  4  got  6
    WARNING: HACKING: line 75: list item 6 out of sequence
    type:  numbered : expected  5  got  7
    WARNING: HACKING: line 83: list item 7 out of sequence
    WARNING: HACKING: line 104: missing [paradef-default] C-style entry
    WARNING: HACKING: line 116: missing [paradef-default] C-style entry
    WARNING: HACKING: line 126: missing [paradef-default] C-style entry
    
    I just followed the syntax example there :
    http://www.methods.co.nz/asciidoc/userguide.html#X56
    And all is fine now :)
    
    Signed-off-by: Xavier Chantry <[EMAIL PROTECTED]>
    Signed-off-by: Dan McGee <[EMAIL PROTECTED]>

commit 0969c2e700c6bd7f855ddfa4e73b6ccd71911ff5
Author: Xavier Chantry <[EMAIL PROTECTED]>
Date:   Thu Aug 7 19:50:07 2008 +0200

    pacman : clarify help message.
    
    Signed-off-by: Xavier Chantry <[EMAIL PROTECTED]>
    Signed-off-by: Dan McGee <[EMAIL PROTECTED]>

commit 56f0cf9d157bc2b902e4590364e2926c2f169b05
Author: Xavier Chantry <[EMAIL PROTECTED]>
Date:   Thu Jul 17 22:35:35 2008 +0200

    makepkg : localize the Y/n part of the question.
    
    pacman already localizes the yesno stuff, so doing the same in makepkg is
    more consistent.
    
    Signed-off-by: Xavier Chantry <[EMAIL PROTECTED]>
    Signed-off-by: Dan McGee <[EMAIL PROTECTED]>

commit 96e023c7bd0b1069878667278a45a34476c42472
Author: Xavier Chantry <[EMAIL PROTECTED]>
Date:   Thu Jul 31 16:35:21 2008 +0200

    pacman: print optdepends on install and upgrade.
    
    This implements FS#10630.
    
    Signed-off-by: Xavier Chantry <[EMAIL PROTECTED]>
    Signed-off-by: Dan McGee <[EMAIL PROTECTED]>

commit e27a8c9ae323c275b0c3503d6a6ea18b639f4dc6
Author: Nagy Gabor <[EMAIL PROTECTED]>
Date:   Thu Jul 31 15:58:25 2008 +0200

    Add new list_display_linebreak function
    
    list_display puts several members on the same line, which is not appropriate
    for optdepends:
    
    Optdepends: foo: feature1  bar: feature2  baz: feature3
    
    The new list_display_linebreak function puts every member on its own line,
    which is much better with optdepends:
    
    Optdepends: foo: feature1
                bar: feature2
                baz: feature3
    
    Signed-off-by: Nagy Gabor <[EMAIL PROTECTED]>
    [Xav: implement this new behavior as a new function rather than as a
    parameter of list_display]
    Signed-off-by: Xavier Chantry <[EMAIL PROTECTED]>
    Signed-off-by: Dan McGee <[EMAIL PROTECTED]>

commit 9451b2e4f23a3c566fcfe3420c379b3cb3eb1f90
Author: Nagy Gabor <[EMAIL PROTECTED]>
Date:   Thu Jul 31 13:38:30 2008 +0200

    Move the the description parsing logic to string_display()
    
    So dump_pkg_full will indent all strings correctly.
    
    Signed-off-by: Nagy Gabor <[EMAIL PROTECTED]>
    [Xav: add string_length function]
    Signed-off-by: Xavier Chantry <[EMAIL PROTECTED]>
    Signed-off-by: Dan McGee <[EMAIL PROTECTED]>

commit 901e4aa5c203f605e9d527e474821426a40e5cea
Author: Xavier Chantry <[EMAIL PROTECTED]>
Date:   Fri Aug 22 13:54:15 2008 +0200

    makepkg: do insensitive comparisons of checksums.
    
    This fixes FS#11283 , which was originally reported on the forums :
    http://bbs.archlinux.org/viewtopic.php?id=53794
    
    Insensitive comparisons were implicitly made before since md5sum --status 
was
    used for checking. Now that we use openssl and compare checksums manually in
    bash, we lost that feature.
    This can be easily reintroduced using tr '[A-F]' '[a-f]'
    
    What convinced me to fix it is that the md5 command line tool generates 
md5sums
    in upper case by default :
    http://www.fourmilab.ch/md5/
    
    And finally, A-F and a-f are the same in hex and both are used.
    
    Signed-off-by: Xavier Chantry <[EMAIL PROTECTED]>
    Signed-off-by: Dan McGee <[EMAIL PROTECTED]>

commit 282eeadc68fec1da8651d0c65ad0dfebd11a9c7f
Author: Dan McGee <[EMAIL PROTECTED]>
Date:   Tue Aug 19 23:29:56 2008 -0500

    Factor shell script size command into configure script
    
    Commit 149839c5391e9a93 introduced a small behavior regression as a drawback
    for a better portability. repo-add now includes the approximate size (to the
    nearest KB) rather than an exact size due to the switching of the du command
    to a more portable form. Instead of sacrificing the exact size, use
    configure to help us determine a valid command to acquire our filesize and
    place it in the sync database.
    
    Signed-off-by: Dan McGee <[EMAIL PROTECTED]>

-----------------------------------------------------------------------

Summary of changes:
 HACKING                |   36 +++++++++---------
 configure.ac           |    7 +++
 doc/pacman.8.txt       |    2 +-
 lib/libalpm/alpm.h     |    1 +
 lib/libalpm/package.c  |   38 +++++++++---------
 lib/libalpm/sync.c     |   30 ++++++++++----
 scripts/Makefile.am    |    1 +
 scripts/makepkg.sh.in  |   11 +++--
 scripts/repo-add.sh.in |    4 +-
 src/pacman/callback.c  |    7 +++-
 src/pacman/package.c   |   20 +--------
 src/pacman/pacman.c    |    7 ++-
 src/pacman/util.c      |   98 +++++++++++++++++++++++++++++++++++------------
 src/pacman/util.h      |    2 +
 14 files changed, 165 insertions(+), 99 deletions(-)


hooks/post-receive
--
The official pacman repository
_______________________________________________
pacman-dev mailing list
[email protected]
http://archlinux.org/mailman/listinfo/pacman-dev

Reply via email to