- Pacman-dev - lists.archlinux.org

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

08 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 bfc024eab3a1d26ba37620175be815cb2eb59606 (commit) via 77c3cf9790472592902183354ea5481cffc01f58 (commit) via 7dc37109b096b484fc569060cc896b5127419775 (commit) via 14ee1be1ef21e09a84f01dc9623e8513218709d4 (commit) via 11fe18479eeb7bb97062a2922da13ba816597007 (commit) via 0c2206f542ce6df2606586d43f190cd5a423fb13 (commit) via 05d56349588665da7ed01eaa3337be7ece35fd2f (commit) via e63366ae5e701d8e9ae33144f68e8786b092a468 (commit) from e81dec9b8c65f7c882f5f447cdc117783259f4a4 (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 bfc024eab3a1d26ba37620175be815cb2eb59606 Merge: 77c3cf9790472592902183354ea5481cffc01f58 14ee1be1ef21e09a84f01dc9623e8513218709d4 Author: Dan McGee <dan(a)archlinux.org> Date: Thu Feb 7 20:16:16 2008 -0600 Merge branch 'maint' commit 77c3cf9790472592902183354ea5481cffc01f58 Author: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Date: Wed Jan 30 13:55:49 2008 +0100 Remove alpm_sync_get_newversion function sync->newversion shouldn't be public at all, and internally we access it directly. (Before pmsyncpkg_t clean-up the analogue of this field [type] was needed in replaces computation.) Signed-off-by: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Signed-off-by: Chantry Xavier <shiningxc(a)gmail.com> commit 7dc37109b096b484fc569060cc896b5127419775 Author: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Date: Mon Jan 28 01:44:23 2008 +0100 alpm_sync_sysupgrade split This patch indroduces a new public alpm_sync_newversion, which scans for new version of a package in sync repos. Hopefully this will reduce code duplication in the future: * check-for-pacman-new-version from front-end can be easier * -Qu refactoring Signed-off-by: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Signed-off-by: Chantry Xavier <shiningxc(a)gmail.com> commit 05d56349588665da7ed01eaa3337be7ece35fd2f Author: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Date: Sun Nov 18 19:05:47 2007 +0100 libalpm/package.c : add _alpm_pkgname_pkg_cmp function. _alpm_pkgname_pkg_cmp(pkgname, pkg) returns true iff pkg's name is pkgname. This is useful if you want to remove a package from pmpkg_t* list, and you want to search for package name. This allows cleaning the -Ru code a bit, by removing the need of a dummy pkg. Signed-off-by: Chantry Xavier <shiningxc(a)gmail.com> commit e63366ae5e701d8e9ae33144f68e8786b092a468 Author: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Date: Sun Nov 18 18:45:46 2007 +0100 New remove option : -u / --unneeded (FS#6505). With --unneeded option 'pacman -R' doesn't stop in case of dependency error; it removes the needed-dependency targets from the target-list instead. See also: http://archlinux.org/pipermail/pacman-dev/2007-October/009653.html . The patch also adds a new causingpkg field to pmdepmissing_t which indicates the to-be-removed package which would cause a dependency break. This is needed, because miss->depend.name may be a provision. miss->causingpkg will be useful in -R dependency error messages too. [Xavier: renamed inducer to causingpkg, removed the _alpm_pkgname_pkg_cmp helper function as requested by Aaron. This might be added by a further commit. Other small cleanups, updated manpage and bash completion.] Signed-off-by: Chantry Xavier <shiningxc(a)gmail.com> ----------------------------------------------------------------------- Summary of changes: contrib/bash_completion | 2 + doc/pacman.8.txt | 5 ++ lib/libalpm/add.c | 10 ++-- lib/libalpm/alpm.h | 6 ++- lib/libalpm/deps.c | 22 +++++++-- lib/libalpm/deps.h | 4 +- lib/libalpm/package.c | 6 ++ lib/libalpm/package.h | 1 + lib/libalpm/remove.c | 24 ++++++++- lib/libalpm/sync.c | 117 ++++++++++++++++++++++++------------------- pactest/pmdb.py | 13 ++++- pactest/tests/remove049.py | 19 +++++++ pactest/tests/upgrade045.py | 16 ++++++ pactest/util.py | 6 ++ scripts/makepkg.sh.in | 7 +++ src/pacman/pacman.c | 3 + 16 files changed, 193 insertions(+), 68 deletions(-) create mode 100644 pactest/tests/remove049.py create mode 100644 pactest/tests/upgrade045.py hooks/post-receive -- The official pacman repository

1 0

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

08 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 14ee1be1ef21e09a84f01dc9623e8513218709d4 (commit) via 11fe18479eeb7bb97062a2922da13ba816597007 (commit) via 0c2206f542ce6df2606586d43f190cd5a423fb13 (commit) from b29838c8250125a22016c16180e941d059d55539 (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: lib/libalpm/add.c | 10 ++++------ pactest/pmdb.py | 13 +++++++++++-- pactest/tests/upgrade045.py | 16 ++++++++++++++++ pactest/util.py | 6 ++++++ scripts/makepkg.sh.in | 7 +++++++ 5 files changed, 44 insertions(+), 8 deletions(-) create mode 100644 pactest/tests/upgrade045.py hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] xdelta status
by Nathan Jones 07 Feb '08

07 Feb '08

Today I read a post[1] by Xavier about how deltas cannot currently be used. As I say in the thread, I will work on adding delta creation support to repo-add in the next week. Is there anything else that needs to be changed before this can actually be used? [1] http://bbs.archlinux.org/viewtopic.php?id=43426

3 6

[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