- Pacman-dev - lists.archlinux.org

[pacman-dev] Pacman TODO from Xavier
by Dan McGee 06 Feb '08

06 Feb '08

Xavier pointed out a few pending items to me with pacman, and I thought I'd respond to his list here on the ML. Thoughts welcome from anyone else. > * -Qo and symlink : > http://www.archlinux.org/pipermail/pacman-dev/2008-February/011061.html > http://shining.toofishes.net/gitweb/gitweb.cgi?p=pacman.git;a=commit;h=cd43… Merged into maint tonight. > * pacman.conf clean up : > http://www.archlinux.org/pipermail/pacman-dev/2008-January/010996.html Replied to this message on the ML. > * ChangeLog.proto : > http://archlinux.org/pipermail/arch-dev-public/2008-January/004020.html > http://shining.toofishes.net/gitweb/gitweb.cgi?p=pacman.git;a=commitdiff;h=… Merged. > * install contrib files > http://www.archlinux.org/pipermail/pacman-dev/2008-January/010782.html How about an AUR package? pacman-contrib? Someone might even maintain it in community. > * ignore targets not found : > point 2) there : > http://www.archlinux.org/pipermail/pacman-dev/2007-September/009412.html 3.2 issue for sure. Interesting, but I like programs to fail hard with invalid input rather than gloss it over. When you script programs, it can be very misleading if things don't fail when you expect them to. > * broken database with two duplicated entries : > for example : > var/lib/pacman/local/xorg-xauth-1.0.1-1/ > var/lib/pacman/local/xorg-xauth-1.0.2-1/ > > If we want to do this check in testdb, don't we need db_splitname or something? > If we do it in libalpm, where exactly? I punted this one to Xavier because I didn't exactly know how to do it. :) Can't we just load the entire local pkgcache and then scan for duplicate names? I was originally thinking of doing this outside of libalpm, and at some point we can add some consistency checks into the library if necessary that ensure no pkgname is duplicated inside a single repo. > * segfault : FS#9235 > > * memleak caused by 8240da6cb3ff95ad480efe3e1876104024398fae > how to track whether a package has been added to the pkgcache or not. > The target list is currently never freed. only the pkgcache is. > If a package from the target list hasn't been added to the cache (because of a > failure, conflict or whatever), it won't be freed. Xavier- if you could bring this up in a separate email thread, that would probably be best. This is an issue where people are just going to have to sit down and try and work out a system for being sure of when/where a package needs to be freed. > * -Ru (unneeded) branch > http://shining.toofishes.net/gitweb/gitweb.cgi?p=pacman.git;a=shortlog;h=un… Mostly because I just haven't merged it yet. I'll try to get a good look at this soon and see if it is good to go for master. > * xdelta support > maybe we need a mail about the status on this, what needs to be done: > http://bbs.archlinux.org/viewtopic.php?id=43426 > (waiting on Nathan) xdelta support in repo-add would probably be our next step- we may need to refactor the common code out of repo-add and makepkg into some kind of makepkg lib, which I am not completely sure how to address. > * upgrade refactoring > status mail on this too? What does this refer to? The idea of our add/remove package lists? If so, it is still an idea brewing in a lot of our heads but no one has made any huge advances on it yet. Of course, it is not going to me an easy or clean change either. -Dan

4 4

[pacman-dev] pacman.conf little clean up
by Xavier 06 Feb '08

06 Feb '08

1) Why do we have this comment everywhere in the conf file : # Add your preferred servers here, they will be used first In my opinion, all these lines could disappear. It's recommended that you keep all your repositories in sync. That means using the same mirror for all official repo. And since all official repo already have this by default : Include = /etc/pacman.d/mirrorlist Only that file needs to be edited, and this will affect all official repo automatically. Advanced users who know what they are doing might not want to use the same mirror everywhere for specific reasons. But I don't think they need a comment everywhere explaining how to do it. But that comment might rather belong to the mirrorlist file. 2) For similar reasons, I don't think the following comment is needed : # REPOSITORIES # - can be defined here or included from another file I doubt many people use that. pacman.conf currently has only two parts : a few options, and the repositories. I don't think there is a need to split these. And again, people who do it probably know what they are doing. 3) I find pacman.conf more readable with more new lines (especially when read without syntax highlighting), so I added a few of these as well, to better separate the different parts, like the comments and the commented lines. Anyway, all these things are not important at all, and might be stupid ideas. It's just random thoughts that came to my mind after seeing an user messed up again configuring his pacman.conf. --- pacman.conf 2008-01-25 19:34:04.000000000 +0100 +++ pacman.conf.new 2008-01-25 18:03:29.000000000 +0100 @@ -6,19 +6,22 @@ # # GENERAL OPTIONS # + [options] + # The following paths are commented out with their default values listed. # If you wish to use different paths, uncomment and update the paths. + #RootDir = / #DBPath = /var/lib/pacman/ #CacheDir = /var/cache/pacman/pkg/ #LogFile = /var/log/pacman.log + HoldPkg = pacman glibc #XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u # # REPOSITORIES -# - can be defined here or included from another file # - pacman will search repositories in the order defined here # - local/custom mirrors can be added here or in separate files # - repositories listed first will take precedence when packages @@ -34,31 +37,28 @@ # # Testing is disabled by default. To enable, uncomment the following -# two lines. You can add preferred servers immediately after the header, -# and they will be used before the default mirrors. +# two lines. + #[testing] #Include = /etc/pacman.d/mirrorlist [core] -# Add your preferred servers here, they will be used first Include = /etc/pacman.d/mirrorlist [extra] -# Add your preferred servers here, they will be used first Include = /etc/pacman.d/mirrorlist [community] -# Add your preferred servers here, they will be used first Include = /etc/pacman.d/mirrorlist # Unstable is disabled by default. To enable, uncomment the following -# two lines. You can add preferred servers immediately after the header, -# and they will be used before the default mirrors. +# two lines. + #[unstable] #Include = /etc/pacman.d/mirrorlist # An example of a custom package repository. See the pacman manpage for # tips on creating your own repositories. + #[custom] #Server = file:///home/custompkgs -

3 3

[pacman-dev] [GIT] The official pacman repository branch, maint, updated. v3.1.1-18-gb29838c
by Dan McGee 06 Feb '08

06 Feb '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 b29838c8250125a22016c16180e941d059d55539 (commit) via 7d7a33791211b26d69bcf3c23174250dd14e9486 (commit) via a7a9f37561b45d2d2900b4c419ac3b9f0c7f2d75 (commit) via 7069b96173aa256d1c2eaed2d21811639e10e566 (commit) via 69bc5ea5e28086c8eea6808be2be3c84b555863b (commit) via 96ee1bca2473ea32d647db0464653424e34b1e91 (commit) via 37bb99abfa5672e101e34579882e22c7a1016a9b (commit) via 7786bf6024b6fbf13ba474aaa24613f2079d8cef (commit) from 7cfb343b0fed556e82b6fbc81047c5461effab84 (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: ChangeLog.proto | 16 ++++++++++++++++ Makefile.am | 2 +- doc/makepkg.8.txt | 14 +++++++++++++- scripts/gensync.sh.in | 7 +++++++ scripts/makepkg.sh.in | 3 +++ scripts/repo-add.sh.in | 4 ++-- scripts/repo-remove.sh.in | 4 +++- scripts/updatesync.sh.in | 7 +++++++ src/pacman/add.c | 5 +++-- src/pacman/query.c | 15 +++++++++++---- src/pacman/remove.c | 4 ++-- src/pacman/sync.c | 2 +- src/pacman/util.c | 28 ++++++++++++++++++++++++++++ src/pacman/util.h | 1 + 14 files changed, 98 insertions(+), 14 deletions(-) create mode 100644 ChangeLog.proto hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] [GIT] The official pacman repository branch, master, updated. v3.1.1-53-ge81dec9
by Dan McGee 06 Feb '08

06 Feb '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 e81dec9b8c65f7c882f5f447cdc117783259f4a4 (commit) via eca30ed66accd7c1555eb94cbdea60051efcf7f3 (commit) via b29838c8250125a22016c16180e941d059d55539 (commit) via 7d7a33791211b26d69bcf3c23174250dd14e9486 (commit) via 93a3050ed9e9735352013014da52adcdf896f95f (commit) via a7a9f37561b45d2d2900b4c419ac3b9f0c7f2d75 (commit) via 7069b96173aa256d1c2eaed2d21811639e10e566 (commit) via 69bc5ea5e28086c8eea6808be2be3c84b555863b (commit) via 96ee1bca2473ea32d647db0464653424e34b1e91 (commit) via 37bb99abfa5672e101e34579882e22c7a1016a9b (commit) via 5d03a6fd94c17442e05574b918970dfe12400cfa (commit) via 4fad7855fae4a01b265c7d28c12b995a19ebc72d (commit) via 7786bf6024b6fbf13ba474aaa24613f2079d8cef (commit) from c492ca840c54d8d45d5916a280f2119c363e0aba (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 e81dec9b8c65f7c882f5f447cdc117783259f4a4 Author: Chantry Xavier <shiningxc(a)gmail.com> Date: Sat Feb 2 23:24:49 2008 +0100 remove --force option from repo-add. The force option should only be specified in the PKGBUILD with options=(force). This information should be handled like any other meta info, and there is no need to have a special repo-add option for it. Signed-off-by: Chantry Xavier <shiningxc(a)gmail.com> [Dan: fix up a few more references in contrib/ scripts, etc] Signed-off-by: Dan McGee <dan(a)archlinux.org> commit eca30ed66accd7c1555eb94cbdea60051efcf7f3 Merge: 93a3050ed9e9735352013014da52adcdf896f95f b29838c8250125a22016c16180e941d059d55539 Author: Dan McGee <dan(a)archlinux.org> Date: Tue Feb 5 19:31:23 2008 -0600 Merge branch 'maint' Conflicts: contrib/gensync contrib/updatesync commit 93a3050ed9e9735352013014da52adcdf896f95f Author: Dan McGee <dan(a)archlinux.org> Date: Tue Feb 5 17:57:17 2008 -0600 Remove "Installed Size" hackeration Keeping this hack around where installed size is only shown if it is greater than total download size encourages broken repository databases. Signed-off-by: Dan McGee <dan(a)archlinux.org> commit 5d03a6fd94c17442e05574b918970dfe12400cfa Author: Dan McGee <dan(a)archlinux.org> Date: Sat Feb 2 14:16:47 2008 -0600 Remove gettext calls from gensync/updatesync Signed-off-by: Dan McGee <dan(a)archlinux.org> commit 4fad7855fae4a01b265c7d28c12b995a19ebc72d Author: Dan McGee <dan(a)archlinux.org> Date: Sat Feb 2 14:09:22 2008 -0600 Remove gensync and updatesync from normal distribution Move these two scripts into contrib/, and start the process of de-automaking them by removing the @sysconfdir@ references and the gettext initialization. The removal of all gettext will soon follow. Signed-off-by: Dan McGee <dan(a)archlinux.org> ----------------------------------------------------------------------- Summary of changes: ChangeLog.proto | 16 ++++++ Makefile.am | 2 +- contrib/Makefile.am | 2 + contrib/README | 4 ++ scripts/gensync.sh.in => contrib/gensync | 63 ++++++++---------------- scripts/updatesync.sh.in => contrib/updatesync | 61 ++++++++--------------- doc/makepkg.8.txt | 14 +++++- doc/repo-add.8.txt | 12 +---- po/POTFILES.in | 2 - scripts/.gitignore | 2 - scripts/Makefile.am | 10 +--- scripts/makepkg.sh.in | 3 + scripts/repo-add.sh.in | 14 ++--- scripts/repo-remove.sh.in | 4 +- src/pacman/add.c | 5 +- src/pacman/query.c | 15 ++++-- src/pacman/remove.c | 4 +- src/pacman/sync.c | 2 +- src/pacman/util.c | 34 +++++++++++-- src/pacman/util.h | 1 + 20 files changed, 138 insertions(+), 132 deletions(-) create mode 100644 ChangeLog.proto delete mode 100644 contrib/.gitignore rename scripts/gensync.sh.in => contrib/gensync (67%) mode change 100644 => 100755 rename scripts/updatesync.sh.in => contrib/updatesync (61%) mode change 100644 => 100755 hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] pmtransconv_t + cb_trans_conv
by Nagy Gabor 05 Feb '08

05 Feb '08

Hi! Some background: FS#7524 and http://bbs.archlinux.org/viewtopic.php?id=42959 So I decided to rephrase our questions and messages to give more information about what happening "inside". Then I soon ran into the question: "Is pmtransconv_t needed?". Why do we restrict ourselves to some pre-defined questions? The question string [char *] should also work, and then the front-end could put a " [Y/n]" after the question (or add yes/no buttons in a graphic dialog box). But after looking into cb_trans_conv I got the answer: the front-end must know the "meaning" of the question to apply its --no-confirm or (removed) --ask rules. I also saw in the comment, that function is tagged as ugly. My compromise: let the backend formulate the question (snprintf + pass char* question param or by using va_list) and keep this pmtransconv_t. An example: PM_TRANS_CONV_CONFLICT_PKG: "foo [pulled dependency] conflicts with bar. Do you remove bar?" Or we could use a more general PM_TRANS_CONV_REMOVE_LOCAL type... Opinions, ideas? Bye

2 3

[pacman-dev] [PATCH] Clarify remove error message.
by Chantry Xavier 05 Feb '08

05 Feb '08

Signed-off-by: Chantry Xavier <shiningxc(a)gmail.com> --- src/pacman/remove.c | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff --git a/src/pacman/remove.c b/src/pacman/remove.c index 56837fa..ee4e84a 100644 --- a/src/pacman/remove.c +++ b/src/pacman/remove.c @@ -108,8 +108,7 @@ int pacman_remove(alpm_list_t *targets) char *targ = alpm_list_getdata(i); if(alpm_trans_addtarget(targ) == -1) { printf("failed.\n"); - fprintf(stderr, _("error: failed to add target '%s' (%s)\n"), targ, - alpm_strerrorlast()); + fprintf(stderr, _("error: could not find '%s' to remove\n"), targ); remove_cleanup(); FREELIST(finaltargs); return(1); -- 1.5.4.rc4

4 7

[pacman-dev] gensync and updatesync status
by Xavier 04 Feb '08

04 Feb '08

I am confused by all the db scripts we have : gensync, updatesync, repo-add, repo-remove. So I had a look a bit at git history. It seems like originally, there were only gensync and updatesync. Then repo-add and repo-remove were created, doing mostly what gensync and updatesync did. But then, gensync and updatesync were rewritten using repo-add and repo-remove. What this done for a compatibility purpose maybe? Are these two tools still use anywhere? I heard (from Dan ;)) that core/extra used didn't even use the scripts in pacman git repo, but the ones in dbscripts git repo instead. But that community did use repo-add. Do they use repo-add directly, or do they use updatesync? What bothers me here is that there is apparently a functionality that is only found in updatesync/gensync, not repo-add : force flag support. Apparently, updatesync need both the PKGBUILD and the package. It reads the PKGBUILD, look if the force option is specified, and then calls repo-add (with --force option if force flag was found) on the package. That sounds rather ugly. Why don't we handle this the more usual way? makepkg could add a force line in .PKGINFO if it finds the force option in the PKGBUILD. And then repo-add add the force flag if it finds it in .PKGINFO. After that, gensync and updatesync could be totally removed, right?

6 14

[pacman-dev] file owners and symlinks
by Xavier 03 Feb '08

03 Feb '08

bash-3.2$ pacman -Ql jre jdk | grep "/java$" jre /opt/java/jre/bin/java jdk /opt/java/bin/java bash-3.2$ ls -l /opt/java/bin/java lrwxrwxrwx 1 root root 15 oct 4 22:59 /opt/java/bin/java -> ../jre/bin/java bash-3.2$ LANG=C pacman -Qo /opt/java/jre/bin/java /opt/java/jre/bin/java is owned by jdk 6u3-1 The -Qo operation calls realpath on both sides, and realpath(/opt/java/bin/java) = /opt/java/jre/bin/java, so it returns that /opt/java/jre/bin/java is owned by jdk, while in fact, jdk only owns a symlink that points to it. I think that realpath should only be called on the path (== dirname), not the whole thing (dirname + basename). That is, /opt/java/bin/ should be resolved, but not the java symlink itself. For implementing that, I would need a dirname function though. For basename, we have a mbasename function that was grabbed from uClibc source. Btw, what is the m for? And could we have mdirname also?

1 0

[pacman-dev] makepkg svn version discovery fails if the log message begins with r
by Jonathan 03 Feb '08

03 Feb '08

someone on irc discovered today that the ffmpeg-svn package failed to build with the odd error seen below... I am using the following version of pacman in archlinux (non-testing): Name : pacman Version : 3.1.1-1 Architecture : i686 Build Date : Sun 20 Jan 2008 07:51:41 PM PST $ makepkg ==> Determining latest svn revision... -> Version found: 11825 emove sed: -e expression #1, char 28: unterminated `s' command makepkg --holdver with old and new versions built ok. the suspect line in makepkg: newpkgver=$(svn log $_svntrunk --limit 1 | sed -n 's/^r$[^ ]* $ .*$/\1/p') here's the svn log at the time: ------------------------------------------------------------------------ r11825 | lorenm | 2008-02-02 19:21:47 -0800 (Sat, 02 Feb 2008) | 2 lines remove some movq in ff_h264_idct8_add_mmx. 288->280 cycles on core2. ------------------------------------------------------------------------ while a full reproduction requires a controlled svn server, a test can be done with this: $ svn log -r 11825 --limit 1 svn://svn.mplayerhq.hu/ffmpeg/trunk | sed -n 's/^r$[^ ]*$ .*$/\1/p' 11825 emove the following is a patch that forces sed to test only the second line of the log. while this works, it will break if the log header is reformatted in the future. But I couldn't find any documentation on how to change the format, or any variations in the logs of the handful of svn servers I've looked at. So it seems ok to do this. diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index 0997386..bd6a7fe 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -1007,7 +1007,7 @@ devel_check() { newpkgver=$(date +%Y%m%d) elif [ ! -z ${_svntrunk} ] && [ ! -z ${_svnmod} ] ; then msg "$(gettext "Determining latest svn revision...")" - newpkgver=$(svn log $_svntrunk --limit 1 -q | sed -n 's/^r$[0-9]* $ .*$/\1/p') + newpkgver=$(svn log $_svntrunk --limit 1 -q | sed -n '2s/^r$[0-9]* $ .*$/\1/p') elif [ ! -z ${_bzrtrunk} ] && [ ! -z ${_bzrmod} ] ; then msg "$(gettext "Determining latest bzr revision...")" newpkgver=$(bzr revno ${_bzrtrunk}) Jonathan Frazier

3 2

[pacman-dev] [PATCH] repo-remove: print an error in case of an empty db
by Chantry Xavier 03 Feb '08

03 Feb '08

When removing the last packages from a database, repo-remove silently failed. Now an error is printed. Signed-off-by: Chantry Xavier <shiningxc(a)gmail.com> --- scripts/repo-remove.sh.in | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/scripts/repo-remove.sh.in b/scripts/repo-remove.sh.in index 05bec39..a2c4095 100644 --- a/scripts/repo-remove.sh.in +++ b/scripts/repo-remove.sh.in @@ -25,7 +25,6 @@ export TEXTDOMAINDIR='@localedir@' myver='@PACKAGE_VERSION@' confdir='@sysconfdir@' -FORCE=0 REPO_DB_FILE="" msg() { @@ -169,6 +168,8 @@ if [ $success -eq 1 ]; then esac bsdtar -c${TAR_OPT}f "$REPO_DB_FILE" * + else + error "$(gettext "Cannot create an empty archive... Aborting")" fi popd 2>&1 >/dev/null -- 1.5.4.rc4

2 2

[pacman-dev] [GIT] The official pacman repository branch, maint, updated. v3.1.1-10-g7cfb343
by Dan McGee 02 Feb '08

02 Feb '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 7cfb343b0fed556e82b6fbc81047c5461effab84 (commit) from b1103a3eaf0c6bb2982ac90000628baa2d5c2079 (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: proto.install | 57 +++++++++++++++++++++++++++++---------------------------- 1 files changed, 29 insertions(+), 28 deletions(-) hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] [GIT] The official pacman repository branch, master, updated. v3.1.1-40-gc492ca8
by Dan McGee 02 Feb '08

02 Feb '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 c492ca840c54d8d45d5916a280f2119c363e0aba (commit) via 7cfb343b0fed556e82b6fbc81047c5461effab84 (commit) via b1103a3eaf0c6bb2982ac90000628baa2d5c2079 (commit) via 5647f7f512380200175675bc2fa5fa2e5892d997 (commit) via c028014f96911930bf3b7dce08c0fe997cedfc69 (commit) from 1fc83f4af6d827bf2e69c7a10e3d2010c9211974 (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 c492ca840c54d8d45d5916a280f2119c363e0aba Merge: 5647f7f512380200175675bc2fa5fa2e5892d997 7cfb343b0fed556e82b6fbc81047c5461effab84 Author: Dan McGee <dan(a)archlinux.org> Date: Sat Feb 2 13:39:50 2008 -0600 Merge branch 'maint' commit 5647f7f512380200175675bc2fa5fa2e5892d997 Author: Dan McGee <dan(a)archlinux.org> Date: Sat Feb 2 09:53:18 2008 -0600 Update libtool version (1.5.24 -> 1.5.26) Signed-off-by: Dan McGee <dan(a)archlinux.org> ----------------------------------------------------------------------- Summary of changes: config.guess | 36 ++++++++++++++++++---------- config.sub | 48 +++++++++++++++++++++++++++++++------ configure.ac | 1 - ltmain.sh | 58 +++++++++++++++++++++++++++++++++------------ proto.install | 57 +++++++++++++++++++++++---------------------- scripts/makepkg.sh.in | 2 +- scripts/updatesync.sh.in | 14 +++++++---- 7 files changed, 144 insertions(+), 72 deletions(-) hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] [GIT] The official pacman repository branch, maint, updated. v3.1.1-9-gb1103a3
by Dan McGee 02 Feb '08

02 Feb '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 b1103a3eaf0c6bb2982ac90000628baa2d5c2079 (commit) from c028014f96911930bf3b7dce08c0fe997cedfc69 (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 b1103a3eaf0c6bb2982ac90000628baa2d5c2079 Author: Alex Merry <huntedhacker(a)tiscali.co.uk> Date: Sat Feb 2 10:09:06 2008 -0600 updatesync: incorrect package deletion logic Fixes FS#9279. Signed-off-by: Dan McGee <dan(a)archlinux.org> ----------------------------------------------------------------------- Summary of changes: scripts/updatesync.sh.in | 14 +++++++++----- 1 files changed, 9 insertions(+), 5 deletions(-) hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] [GIT] The official pacman repository branch, maint, updated. v3.1.1-8-gc028014
by Dan McGee 02 Feb '08

02 Feb '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 c028014f96911930bf3b7dce08c0fe997cedfc69 (commit) from 0775c38e72c06b9ad428c4e6dbfd0b6f0cda2818 (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 c028014f96911930bf3b7dce08c0fe997cedfc69 Author: Dan McGee <dan(a)archlinux.org> Date: Sun Jan 27 21:06:28 2008 -0600 makepkg: ensure binaries in /opt/* are stripped The path selection for stripping binaries was slightly off, so any binaries in subdirectories of opt/ were missed. Fixes FS#9342. Signed-off-by: Dan McGee <dan(a)archlinux.org> ----------------------------------------------------------------------- Summary of changes: scripts/makepkg.sh.in | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] is newer than messages
by Karolina Lindqvist 02 Feb '08

02 Feb '08

What is the purpose of the messages "is newer then", from pacman -Su? Can't they please be removed in the normal case? Is there anyone who need them? They look like debug messages to me. $ sudo pacman -Su :: Starting full system upgrade... warning: attr: local (2.4.39-2.1) is newer than core (2.4.39-2) warning: kdebase: local (3.5.8.20080105-1) is newer than extra (3.5.8-3) warning: kdelibs: local (3.5.8.20080105-2) is newer than extra (3.5.8-4) warning: kernel26: ignoring package upgrade (2.6.23.14-1 => 2.6.24-2) warning: lirc: local (0.8.3-0.20080113) is newer than testing (0.8.2-10) warning: lirc-utils: local (0.8.3-0.20080113.1) is newer than extra (0.8.2-1) warning: tellico: local (1.3-1) is newer than community (1.2.14-1)

2 1

[pacman-dev] pamcan don't show the size of invididual package in remove list and 'Total remove size:' in operation -R
by Vojtěch Gondžala 31 Jan '08

31 Jan '08

Hi all, I think something like this: --------- # pacman -Rc amarok-engine-xine loading package data... done. checking dependencies... Targets: amarok-base [28.60 MB] amarok-engine-xine [0.21 MB] Total Removed Size: 28.81 MB Do you want to remove these packages? [Y/n] ---------- and ---------- # pacman -S qca2 resolving dependencies... looking for inter-conflicts... :: qca2 conflicts with qca. Remove qca? [Y/n] Remove: qca [2.94 MB] Total Removed Size: 2.94 MB Targets: qca2-2.0.0-1 [0.66 MB] Total Download Size: 0.00 MB Total Installed Size: 1.92 MB Proceed with installation? [Y/n] ---------- in attachment is patch for this --vogo

3 2

Re: [pacman-dev] pamcan don't show the size of invididual package in remove list and 'Total remove size:' in operation -R
by Vojtěch Gondžala 31 Jan '08

31 Jan '08

> This is already implemented for -S and -Q (see > http://bugs.archlinux.org/task/6667) > Add ShowSize option to pacman.conf. > So this should be just extended to support -R. > > -- > Roman Kyrylych (Роман Кирилич) no wholly in -S, see this line without patch: :: qca2 conflicts with qca. Remove qca? [Y/n] Remove: qca <<<<< Total Removed Size: 2.94 MB with patch: :: qca2 conflicts with qca. Remove qca? [Y/n] Remove: qca [2.94 MB] <<<<< Total Removed Size: 2.94 MB --vogo

2 1

[pacman-dev] [PATCH] Remove /bin/true from install.proto
by Roman Kyrylych 30 Jan '08

30 Jan '08

This patch removes /bin/true from install.proto to not endorse its bad usage. This was already done in Arch CVS when we discussed cyclic dependencies in Core. -- Roman Kyrylych (Роман Кирилич)

3 2

Re: [pacman-dev] [arch-dev-public] Filename search for Arch
by Dan McGee 28 Jan '08

28 Jan '08

On Jan 25, 2008 5:31 PM, eliott <eliott(a)cactuswax.net> wrote: > > On 1/25/08, Aaron Griffin <aaronmgriffin(a)gmail.com> wrote: > > On Jan 25, 2008 5:02 PM, Thomas Bächler <thomas(a)archlinux.org> wrote: > > > eliott schrieb: > > > > I guess I don't see where this script fits in, and how it is supposed > > > > to be used. > > > > thomas made mention of using zgrep for advanced users, but that seems > > > > just as difficult as opening a web browser and typing into a search > > > > box. > > > > > > The purpose is to provide filelists for download, so they can be > > > searched offline by pacman. > > > My first idea (implementing an online search in pacman) was rejected, > > > thus I thought about a "download the filelist and search it" offline > > > solution. > > > > Oh, I must have misunderstood too. If you're going to implement > > filelist search and all that stuff, we should: > > a) Move this to the pacman-dev mailing list > > b) Add external tools to do this as part of the "pacman source", i.e. > > as a patch to repo-add > > c) Not use this script until pacman actually has this feature. > > > > If the intent is to let users zgrep it, then I agree with cactus that > > that is significantly more complex then actually using the website to > > provide a search interface. > > Yeah. I wasn't apposed to having a file search mechanism on the site. > I was apposed to having pacman query the website. If a user opens up a > browser and searches, no problem. It was tying this to pacman that I > felt was a *really bad idea*. > > Alternatively, if there is a pacman only solution, that involves some > mirrored meta in the repository, that is something else entirely, and > should probably be talked about on the pacman dev list, so as to make > it as distribution neutral as possible. As I've said already, I really don't think this feature belongs in pacman. Obviously you can draw the connection with the -Ql operation, and the fact that we have -Ss, but this is something a bit different than that and I see it as feature creep. -Dan

10 15

[pacman-dev] dbscripts status
by Xavier 28 Jan '08

28 Jan '08

Why are there so many files there : http://projects.archlinux.org/git/?p=dbscripts.git;a=tree pkgdb, pkgdb1, pkgdb2-add.c, pkgdb2-del.c, pkgdb2.c, updatesync-many. These names don't really speak to me. Is updatesync-many the only one developers use directly? And what are all the pkgdb* stuff for? Well, at least the three c programs seem to interact with the mysql database. But that doesn't explain how all the scripts / programs interact together, and how hard it would be to make them use repo-add instead.

2 1

[pacman-dev] Pacman, sqlite and dialectic of competent people
by Manuel "ekerazha" C. 28 Jan '08

28 Jan '08

Maybe this is a better place where discuss this ( http://bbs.archlinux.org/viewtopic.php?id=42374 ) or at least I've have to clarify some things. 1)** toofishes says: ------------------------------------------------------------------------ Yes its faster. But does it matter all that much? $ time pacman -Qg gnome > /dev/null real 0m0.105s user 0m0.047s sys 0m0.037s $ time pacman -Sg gnome > /dev/null real 0m0.388s user 0m0.160s sys 0m0.203s ------------------------------------------------------------------------ Well... these are my results with Pacman 3.1.0 (Pentium III 933 Mhz, PC133 512 MB, 120 GB 7200rpm with XFS filesystem, "pacman-optimize" regularly done): [root@PC-ekerazha ekerazha]# time pacman -Qg gnome > /dev/null real 0m8.083s user 0m0.107s sys 0m0.233s [root@PC-ekerazha ekerazha]# time pacman -Sg gnome > /dev/null real 0m44.482s user 0m0.510s sys 0m0.963s So 8 and 44 seconds (44 seconds!). Apparently it really matters... toofishes says: ------------------------------------------------------------------------ Here are the things to "do" since you don't seem to understand we are "busy" developing "software" that works and doesn't "break" people's systems in the "name" of speed. ------------------------------------------------------------------------ Why should the sqlite approach "break people's systems in the name of speed"? You clearly don't know what are you talking about... I really hope there are also competent pacman devs there (as you say). 2) phrakture, people like "toofishes" is the living example of why "show you the code" (already partially done but incomplete) is useless. As I've already said, <People will "do" when the things to "do" will be *understood and accepted*, people won't waste their time vainly> and it seems obvious that people like "toofishes" isn't understanding anything about this. However... keep up the good work because Arch is a great Linux distro (the best out there) and well... pacman is a "decent" package manager (although poorly engineered and very slow). P.S. Excuse me for my bad English but it isn't my native language.

10 21

[pacman-dev] [GIT] The official pacman repository branch, maint, updated. v3.1.1-7-g0775c38
by Dan McGee 27 Jan '08

27 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 0775c38e72c06b9ad428c4e6dbfd0b6f0cda2818 (commit) via f950c2630798e03bbee314c4a3f2749d1293a2b3 (commit) via 11692e0eef79e016859bb182917e56a12a14f734 (commit) from bba62655fe06989e89576e66a97607da88aa9916 (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: doc/makepkg.8.txt | 2 +- scripts/makepkg.sh.in | 2 +- src/pacman/sync.c | 9 +++------ 3 files changed, 5 insertions(+), 8 deletions(-) hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] [GIT] The official pacman repository branch, master, updated. v3.1.1-35-g1fc83f4
by Dan McGee 27 Jan '08

27 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 1fc83f4af6d827bf2e69c7a10e3d2010c9211974 (commit) via 9fbb77c91ba411fa46b1f2955893e7a39291f46a (commit) via 9bfbd739176ebc41e4ec93dcd21264b87640aa5b (commit) via ea828b5693d389d24c744841385b16cb37a32fce (commit) via f432ce41e0892b17d062d8d64ac221e7bc4d718c (commit) via 0775c38e72c06b9ad428c4e6dbfd0b6f0cda2818 (commit) via f950c2630798e03bbee314c4a3f2749d1293a2b3 (commit) via 11692e0eef79e016859bb182917e56a12a14f734 (commit) from 88cbee3c24768470cc0d4abe050e98b989807a67 (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 1fc83f4af6d827bf2e69c7a10e3d2010c9211974 Author: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Date: Sun Jan 27 12:24:50 2008 +0100 pmsyncpkg_t cleanup Fix for sync044.py and reason001.py. Rename sync->data to sync->removes (alpm_list_t *) Replace pmsynctype_t sync->type by pmpkgreason_t sync->newreason The type field was set to UPGRADE or DEPEND or REPLACE. Instead of using type = UPGRADE or DEPEND, we now rather use a "pmpkgreason_t newreason" field directly (= explicit or depend) which allows a better handling of the install reason. And the REPLACE type is now deduced implicitly when the sync->removes list is not empty. Signed-off-by: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Signed-off-by: Chantry Xavier <shiningxc(a)gmail.com> Signed-off-by: Dan McGee <dan(a)archlinux.org> commit 9fbb77c91ba411fa46b1f2955893e7a39291f46a Merge: 9bfbd739176ebc41e4ec93dcd21264b87640aa5b 0775c38e72c06b9ad428c4e6dbfd0b6f0cda2818 Author: Dan McGee <dan(a)archlinux.org> Date: Sun Jan 27 11:54:52 2008 -0600 Merge branch 'maint' commit 9bfbd739176ebc41e4ec93dcd21264b87640aa5b Author: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Date: Fri Jan 25 21:52:35 2008 +0100 Fix PM_ERR_CONFLICTING_DEPS handling in sync.c * eliminate asymmetry (innerconflict vs. outerconflict) * fix a memleak (in case of PM_ERR_MEMORY deps wasn't freed) * fix wrong pmconflict_t duplication (*retconflict = *conflict) Note: the new code introduces some code duplication which shall disappear by fixing FS#7524. Signed-off-by: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Signed-off-by: Chantry Xavier <shiningxc(a)gmail.com> Signed-off-by: Dan McGee <dan(a)archlinux.org> commit ea828b5693d389d24c744841385b16cb37a32fce Author: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Date: Fri Jan 25 21:31:20 2008 +0100 New _alpm_conflict_dup function Added function to cleanly duplicate a conflict. Signed-off-by: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Signed-off-by: Chantry Xavier <shiningxc(a)gmail.com> commit f432ce41e0892b17d062d8d64ac221e7bc4d718c Author: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Date: Mon Jan 14 14:29:41 2008 +0100 small sync.c code clean-up Remove unnecessary synclist_free function, and use our standard way (alpm_list_free_inner + alpm_list_free) instead. This slightly reduces code duplication. Signed-off-by: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Signed-off-by: Chantry Xavier <shiningxc(a)gmail.com> Signed-off-by: Dan McGee <dan(a)archlinux.org> ----------------------------------------------------------------------- Summary of changes: doc/makepkg.8.txt | 2 +- lib/libalpm/alpm.h | 11 +--- lib/libalpm/conflict.c | 11 ++++ lib/libalpm/conflict.h | 1 + lib/libalpm/sync.c | 147 +++++++++++++++++++---------------------------- lib/libalpm/sync.h | 6 +- scripts/makepkg.sh.in | 2 +- src/pacman/sync.c | 9 +-- src/pacman/util.c | 25 ++++----- 9 files changed, 93 insertions(+), 121 deletions(-) hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] [PATCH] conflict error return fix in sync.c
by Nagy Gabor 24 Jan '08

24 Jan '08

From 1225b562d9ce5eb96cc3a391d7a6eb5553ff7450 Mon Sep 17 00:00:00 2001 From: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Date: Thu, 24 Jan 2008 22:52:58 +0100 Subject: [PATCH] conflict error return fix in sync.c *some memleak fixes *unify return lists (inner vs outer conflict) Note: this patch introduces some code duplication, which should be fixed, when fixing FS#7524 Signed-off-by: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> --- lib/libalpm/sync.c | 29 +++++++++++++---------------- 1 files changed, 13 insertions(+), 16 deletions(-) diff --git a/lib/libalpm/sync.c b/lib/libalpm/sync.c index 3e99795..603214d 100644 --- a/lib/libalpm/sync.c +++ b/lib/libalpm/sync.c @@ -485,9 +485,15 @@ int _alpm_sync_prepare(pmtrans_t *trans, pmdb_t *db_local, alpm_list_t *dbs_sync rsync = sync1; sync = sync2; } else { + _alpm_log(PM_LOG_ERROR, _("unresolvable package conflicts detected\n")); pm_errno = PM_ERR_CONFLICTING_DEPS; ret = -1; - *data = deps; + if(data) { + *data = deps; + } else { + alpm_list_free_inner(deps, (alpm_list_fn_free)_alpm_conflict_free); + alpm_list_free(deps); + } goto cleanup; } @@ -552,23 +558,14 @@ int _alpm_sync_prepare(pmtrans_t *trans, pmdb_t *db_local, alpm_list_t *dbs_sync sync->data = alpm_list_add(sync->data, local); } else { /* abort */ _alpm_log(PM_LOG_ERROR, _("unresolvable package conflicts detected\n")); - if(data) { - pmconflict_t *retconflict; - MALLOC(retconflict, sizeof(pmconflict_t), 0); - if(!retconflict) { - pm_errno = PM_ERR_MEMORY; - alpm_list_free_inner(*data, (alpm_list_fn_free)_alpm_conflict_free); - alpm_list_free(*data); - ret = -1; - goto cleanup; - } - *retconflict = *conflict; - *data = alpm_list_add(*data, retconflict); - } pm_errno = PM_ERR_CONFLICTING_DEPS; ret = -1; - alpm_list_free_inner(deps, (alpm_list_fn_free)_alpm_conflict_free); - alpm_list_free(deps); + if(data) { + *data = deps; + } else { + alpm_list_free_inner(deps, (alpm_list_fn_free)_alpm_conflict_free); + alpm_list_free(deps); + } goto cleanup; } } -- 1.5.3.7

1 0

[pacman-dev] Fwd: [arch-general] makepkg not stripping bin/libs
by Travis Willard 24 Jan '08

24 Jan '08

This feels more like pacman-dev material - forwarded there. ---------- Forwarded message ---------- From: Mark Constable <markc(a)renta.net> Date: Jan 24, 2008 6:58 AM Subject: [arch-general] makepkg not stripping bin/libs To: General Discusson about Arch Linux <arch-general(a)archlinux.org> makegpkg 3.1.1 line ~752 has this... find {,usr/{,local/},opt/}{bin,lib,sbin} -type f and I can't see how that will ever work, and it doesn't for me, however this does work (for me)... find -regex ".+/bin/.+" -o -regex ".+/lib/.+" -o -regex ".+/sbin/.+" -type f I recently rebuilt kdemod4 and it ended up being 1.9Gb whereas it should have been around >400Mb. --markc

3 3