- Pacman-dev - lists.archlinux.org

[pacman-dev] [GIT] The official pacman repository branch, maint, updated. v3.0.6-749-gb1a2314
by Dan McGee 10 Jan '08

10 Jan '08

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, maint has been updated via b1a231427b1335af2ef7c23796525f5e17441f14 (commit) via 47761d5aec3f27fcbb4acc7d0f4f1881cd0c0e6a (commit) via 33f6fda8b669443d6f6ca81fc433afffd53ecfda (commit) via 079f5a8346d71b36f703c68e5c1f27fac58815ba (commit) from 3ddbdc4c1d3130896240452d99dc20f68aeb1ee0 (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 b1a231427b1335af2ef7c23796525f5e17441f14 Author: Dan McGee <dan(a)archlinux.org> Date: Wed Jan 9 18:32:27 2008 -0600 makepkg: Ensure we include all manpage directories in compression line Signed-off-by: Dan McGee <dan(a)archlinux.org> commit 47761d5aec3f27fcbb4acc7d0f4f1881cd0c0e6a Author: Chantry Xavier <shiningxc(a)gmail.com> Date: Sat Jan 5 19:45:07 2008 +0100 Move the fallback on providers from backend to frontend. This reverts commit e28973169d2e5eda8b64ebdda11ece0dc761d978. This code might fit better in the frontend than in the backend finally. Ref: http://www.archlinux.org/pipermail/pacman-dev/2007-November/010150.html I also changed it for fixing FS#8763 : if there is exactly one provider, pacman will pull it and print a warning. if there are several providers, pacman will list them and fail. It's up to the user to pick one. Add sync501 pactest to reflect that. commit 33f6fda8b669443d6f6ca81fc433afffd53ecfda Author: Karolina Lindqvist <karolina.lindqvist(a)kramnet.se> Date: Wed Jan 9 18:08:43 2008 -0600 makepkg: add package name to output when installing package Signed-off-by: Dan McGee <dan(a)archlinux.org> ----------------------------------------------------------------------- Summary of changes: configure.ac | 2 +- lib/libalpm/sync.c | 28 ++-------------------------- pactest/tests/sync501.py | 15 +++++++++++++++ scripts/makepkg.sh.in | 5 ++--- src/pacman/sync.c | 34 +++++++++++++++++++++++++++++++--- 5 files changed, 51 insertions(+), 33 deletions(-) create mode 100644 pactest/tests/sync501.py hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] [GIT] The official pacman repository branch, master, updated. v3.0.6-746-g079f5a8
by Dan McGee 10 Jan '08

10 Jan '08

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 079f5a8346d71b36f703c68e5c1f27fac58815ba (commit) from 3ddbdc4c1d3130896240452d99dc20f68aeb1ee0 (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 ----------------------------------------------------------------- ----------------------------------------------------------------------- Summary of changes: configure.ac | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] %REPLACES% doesn't appear in localdb
by Nagy Gabor 10 Jan '08

10 Jan '08

Hi! See _alpm_db_write in libalpm/be_files.c: ------------------------- 702 if(!local) { 703 if(info->replaces) { 704 fputs("%REPLACES%\n", fp); 705 for(lp = info->replaces; lp; lp = lp->next) { 706 fprintf(fp, "%s\n", (char *)lp->data); 707 } 708 fprintf(fp, "\n"); 709 } -------------------------- So %REPLACES% field is not recorded to local db. I know, that we don't need that field, but then we should remove 'replaces' listing from -Qi. Since we have some other not needed but interesting infos in local db (packager, optdepend etc.) I vote for remove that if(!local) line instead. Anyway, is there any case where local != 0? Bye ---------------------------------------------------- SZTE Egyetemi Könyvtár - http://www.bibl.u-szeged.hu This mail sent through IMP: http://horde.org/imp/

5 10

[pacman-dev] Maybe some problems with pacman-git
by Karolina Lindqvist 09 Jan '08

09 Jan '08

I have a patch-file that I apply to makepkg in pacman-git, with some problems and enhancement. I made a new diff with the current version, and this is possible problem areas. Since I have more "feature" patches, I have tried to extract just the problems, in case someone think that the fix might be valuable. All proper UNIFIED diff patch snippets are for makepkg.sh.in BUG: When pacman recurses, and the --asroot option is given it fails to propagate --asroot to the inner pacman. The second part of the patch is that the correct options are not propagated to a recursing makepkg. I think this is primarily --noconfirm and --noprogressbar @@ -363,13 +373,15 @@ local makepkg_opts='-i -c -b' [ "$RMDEPS" = "1" ] && makepkg_opts="$makepkg_opts -r" + [ "$ASROOT" = "1" ] && makepkg_opts="$makepkg_opts -r --asroot" local ret packagedir for packagedir in $candidates; do if [ -f "$packagedir/$BUILDSCRIPT" ]; then cd "$packagedir" ret=0 - PKGDEST="$PKGDEST" makepkg $makepkg_opts || ret=$? [ $ret -eq 0 ] && continue 2 + PKGDEST="$PKGDEST" makepkg $PACMAN_OPTS $makepkg_opts || ret=$? fi done bsdtar failed to unzip one of the zip files in one of the packages, so therefore I have this patch. @@ -616,10 +628,12 @@ local file_type=$(file -bizL "$file") local cmd='' case "$file_type" in - *application/x-tar*|*application/zip*|*application/x-zip*| *application/x-cpio*) + *application/x-tar*|*application/x-cpio*) cmd="bsdtar -x -f $file" ;; *application/x-gzip*) cmd="gunzip -d -f $file" ;; + *application/zip*|*application/x-zip*) + cmd="unzip -q $file" ;; *application/x-bzip*) cmd="bunzip2 -f $file" ;; *) This one I have, since bsdtar outputs tons, and tons of error/warning messages, about something that it cannot handle attributes. Highly annoying. @@ -858,7 +876,7 @@ local pkg_file="$PKGDEST/${pkgname}-${pkgver}-${pkgrel}-${CARCH}${PKGEXT}" - if ! bsdtar -czf "$pkg_file" $comp_files $(ls); then + if ! bsdtar -czf "$pkg_file" $comp_files $(ls) 2>/dev/null ; then error "$(gettext "Failed to create package file.")" exit 1 # TODO: error code fi BUG: Pacman fails to work properly with --asroot, and when it recalls itself, on some particular packages. @@ -1425,6 +1454,7 @@ rm -rf "$pkgdir" fi mkdir -p "$pkgdir" + cd "$startdir" if [ $EUID -eq 0 ]; then # if we are root, then we don't need to recall makepkg with fakeroot @@ -1439,7 +1469,6 @@ create_package else msg "$(gettext "Entering fakeroot environment...")" - cd "$startdir" if [ "$newpkgver" != "" ]; then fakeroot -- $0 --forcever $newpkgver -F $ARGLIST || exit $? This is just a nice "feature" patch, so that you know what is going on when you use -b. @@ -969,7 +987,7 @@ install_package() { [ "$INSTALL" = "0" ] && return - msg "$(gettext "Installing package with pacman -U...")" + msg "$(gettext "Installing package ${pkgname} with pacman -U...")" if [ "$ASROOT" = "0" ]; then sudo pacman $PACMAN_OPTS -U $PKGDEST/${pkgname}-${pkgver}-${pkgrel}-${CARCH}${PKGEXT} || exit $? else

5 15

[pacman-dev] [GIT] The official pacman repository branch, master, updated. v3.0.6-745-g3ddbdc4
by Dan McGee 09 Jan '08

09 Jan '08

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 3ddbdc4c1d3130896240452d99dc20f68aeb1ee0 (commit) via 504e6ebb878379512128323d8df6a0361f10edcf (commit) via 9dd016001eafb69991661d4d8bda91906d51ed78 (commit) via a24c323abadd7802a38d162a0015bbc4dc82f75d (commit) via 9a6361d31f17e86028ec801525978ce7c802c860 (commit) via dd5bc808ea513ff0a6131ec3e75b02fb138302c5 (commit) from aa48be72235edc7245f1099ae0f7fc2ff4c71f7f (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 3ddbdc4c1d3130896240452d99dc20f68aeb1ee0 Author: Nathan Jones <nathanj(a)insightbb.com> Date: Tue Jan 8 15:34:34 2008 -0500 Documentation updates Document the following: * -R can take a group * -S can take a group and provision I also split up the -S description into multiple paragraphs because it was getting too large. Signed-off-by: Nathan Jones <nathanj(a)insightbb.com> [Dan: added some feedback from the ML, rewrapped lines] Signed-off-by: Dan McGee <dan(a)archlinux.org> commit 504e6ebb878379512128323d8df6a0361f10edcf Author: Dan McGee <dan(a)archlinux.org> Date: Tue Jan 8 15:52:49 2008 -0600 NEWS: fix note about ABS Signed-off-by: Dan McGee <dan(a)archlinux.org> commit 9dd016001eafb69991661d4d8bda91906d51ed78 Author: Dan McGee <dan(a)archlinux.org> Date: Tue Jan 8 15:49:52 2008 -0600 Remove upgradedelay and all code associated with it It wasn't even implemented correctly, and it really doesn't have a use if packagers just do their job correctly anyway for a distro. Let's not try to solve a problem with the wrong solution now. Signed-off-by: Dan McGee <dan(a)archlinux.org> commit a24c323abadd7802a38d162a0015bbc4dc82f75d Author: Dan McGee <dan(a)archlinux.org> Date: Tue Jan 8 13:29:41 2008 -0600 Remove unused date element from pmpkg_t struct We had an unused date element in the pmpkg_t struct (not builddate or installdate). Kill it off and fix the one function that was using it. Signed-off-by: Dan McGee <dan(a)archlinux.org> commit 9a6361d31f17e86028ec801525978ce7c802c860 Author: Chantry Xavier <shiningxc(a)gmail.com> Date: Tue Jan 8 19:58:52 2008 +0100 Update NEWS with versioned conflicts and new DEP_MOD operators. Signed-off-by: Chantry Xavier <shiningxc(a)gmail.com> commit dd5bc808ea513ff0a6131ec3e75b02fb138302c5 Author: Dan McGee <dan(a)archlinux.org> Date: Tue Jan 8 09:10:45 2008 -0600 makepkg: Fix issues with --asroot and building dependencies The --asroot option was not passed to recursive calls of makepkg. In addition, a 'cd' call was done only on the fakeroot branch instead of both fakeroot and root branches. Move it outside the conditional. Noticed-by: Karolina Lindqvist <karolina.lindqvist(a)kramnet.se> Signed-off-by: Dan McGee <dan(a)archlinux.org> ----------------------------------------------------------------------- Summary of changes: NEWS | 4 +++- README | 1 - doc/pacman.8.txt | 25 +++++++++++++++++++------ lib/libalpm/alpm.h | 3 --- lib/libalpm/handle.c | 14 -------------- lib/libalpm/handle.h | 1 - lib/libalpm/package.c | 22 ---------------------- lib/libalpm/package.h | 2 -- scripts/makepkg.sh.in | 7 ++++--- src/pacman/pacman.c | 5 ----- 10 files changed, 26 insertions(+), 58 deletions(-) hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] zsh completion for pacman
by Dan McGee 08 Jan '08

08 Jan '08

Can anyone tell me if this package should be merged with our zsh_completion file in the current pacman repository? http://aur.archlinux.org/packages.php?do_Details=1&ID=6843 If so, can someone provide a patch ASAP? I plan on installing both the bash completion and zsh completion files in the next pacman release. -Dan

2 2

[pacman-dev] [GIT] The official pacman repository branch, master, updated. v3.0.6-739-gaa48be7
by Dan McGee 08 Jan '08

08 Jan '08

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 aa48be72235edc7245f1099ae0f7fc2ff4c71f7f (commit) via f438f7a8ff8e96691d8f27e77755d1822d5f02f6 (commit) via 6025df659432cd2dd98d1f1840fb4a0d9d4f5cd4 (commit) from 6f86f46c965d2268c533d9cedf873b922a598bb1 (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 aa48be72235edc7245f1099ae0f7fc2ff4c71f7f Author: Dan McGee <dan(a)archlinux.org> Date: Mon Jan 7 21:42:19 2008 -0600 Update translation-help with new translation policies Signed-off-by: Dan McGee <dan(a)archlinux.org> commit f438f7a8ff8e96691d8f27e77755d1822d5f02f6 Author: Dan McGee <dan(a)archlinux.org> Date: Sun Jan 6 22:18:08 2008 -0600 Documentation updates Update description of path specifiers for both pacman and pacman.conf in their respective manpages. Ensure it is obvious that they are absolute and not relative paths. Signed-off-by: Dan McGee <dan(a)archlinux.org> commit 6025df659432cd2dd98d1f1840fb4a0d9d4f5cd4 Author: Dan McGee <dan(a)archlinux.org> Date: Sun Jan 6 16:14:18 2008 -0600 Asciidoc a few more of our informative files Signed-off-by: Dan McGee <dan(a)archlinux.org> ----------------------------------------------------------------------- Summary of changes: HACKING | 10 ++- doc/pacman.8.txt | 18 ++++-- doc/pacman.conf.5.txt | 27 ++++++--- submitting-patches | 90 +++++++++++++++++------------ translation-help | 152 +++++++++++++++++++++++++++++++++++------------- 5 files changed, 200 insertions(+), 97 deletions(-) hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] translation procedure
by Xavier 07 Jan '08

07 Jan '08

There was a discussion yesterday on irc about simplifying the translation process. Stonecrest was basically saying that having to go through git might turn off some potential translators, and confuse others. And I agree with that. Translators actually don't even need the pacman source tree, here is how the process can go : 19:53 stonecrest >> 1. release coming 2. string freeze 3. dan updates po files 4. people download po files from gitweb and update them 5. people submit them 19:54 stonecrest >> and you can continue making any changes to pacman during that process that don't change strings. So first, I would like to know the opinion of others (especially the existing translators) about this procedure. And then, I tried to update the translation-help accordingly, but I am not sure how bad my changes are, so if others could also comment on that and suggest improvements, it would be great :) Note : the patch is based on Dan's working branch since he converted translation-help to asciidoc there.

2 1

[pacman-dev] [abs] Proto files and Makeworld
by Travis Willard 07 Jan '08

07 Jan '08

Hey guys, With ABS splitting off from pacman, I was wondering where makeworld and the .proto files belonged. To me, makeworld seems to be an abs tool (and even mentions ABS in its usage) so it would seem to belong in the abs project, not with pacman itself. The proto files (PKGBUILD.proto, install.proto, and possibly a ChangeLog.proto?) seem to belong with makepkg in my mind. Any changes in these proto files would be directly caused by changes to makepkg, and the coupling of putting them in with the pacman package seems to make sense. I've never understood why we sync them with abs in the first place - if someone wants a prototype PKGBUILD to start from, why should they have to download the entirety of our repos' build scripts? In short, I think we should move makeworld to the abs project/package, and move the prototype files into the pacman project/package, perhaps in /usr/share/pacman/*proto? Thoughts? -- Travis

6 25

[pacman-dev] typo ?
by fancris3 07 Jan '08

07 Jan '08

[~]:: sudo pacman -Rd perl-html-parser loading package data... done. checking dependencies... (1/1) removing perl-html-parser [#############################################] 100% [~]:: sudo pacman -Sd perl-html-parser looking for inter-conflicts... Targets: perl-html-parser-3.56-3 Total Download Size: 0.00 MB Total Installed Size: 0.09 MB Proceed with installation? [Y/n] y checking package integrity... (1/1) checking for file conflicts [#############################################] 100% (1/1) installing perl-html-parser [#############################################] 100% [~]:: maybe : skip dependencies... ?

2 1