- Pacman-dev - lists.archlinux.org

[pacman-dev] [PATCH] Updated Italian Translation
by Giovanni Scafora 18 Dec '07

18 Dec '07

Hi guys, I apologize to you, but we have another patch to fix 1 fuzzy message into libalpm and some general improvements to the italian translation. Thanks a lot. -- Giovanni Scafora Arch Linux Trusted User (voidnull) http://www.archlinux.org linuxmania(a)gmail.com

1 0

[pacman-dev] [PATCH] Add PM_DEP_MOD_GT and PM_DEP_MOD_LT to documentation
by Nagy Gabor 18 Dec '07

18 Dec '07

From ef8f4ca925cee8472aebffc9afc0f0837566cc81 Mon Sep 17 00:00:00 2001 From: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Date: Tue, 18 Dec 2007 14:48:32 +0100 Subject: [PATCH] Add PM_DEP_MOD_GT and PM_DEP_MOD_LT to documentation Signed-off-by: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> --- doc/PKGBUILD.5.txt | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/PKGBUILD.5.txt b/doc/PKGBUILD.5.txt index b3ea4c9..1ebf4a6 100644 --- a/doc/PKGBUILD.5.txt +++ b/doc/PKGBUILD.5.txt @@ -117,8 +117,9 @@ Options and Directives An array of packages that this package depends on to run. Packages in this list should be surrounded with single quotes and contain at least the package name. Entries can also include a version requirement of the - form 'name<>version', where <> is one of three comparisons: >= (greater - than or equal to), <= (less than or equal to), or = (equal to). + form 'name<>version', where <> is one of five comparisons: >= (greater + than or equal to), <= (less than or equal to), = (equal to), > (greater + than), or < (less than). *makedepends (array)*:: An array of packages that this package depends on to build, but are not -- 1.5.3.7

1 0

[pacman-dev] Problem compiling pacman 3.0.6-2
by Karolina 18 Dec '07

18 Dec '07

It appears that pacman needs /usr/lib/libattr.la but the package "attr" has options=('!libtool') and does not provide that file. Setting options=('libtool') for the package "attr" solves the problem, but I don't know if that is the correct solution. Karolina

3 4

[pacman-dev] foo<2.0 dependency
by Nagy Gabor 17 Dec '07

17 Dec '07

Hi! First I refer to this old mail: http://www.archlinux.org/pipermail/pacman-dev/2007-July/008701.html (s/depend/requiredby in that subject <- this 'audacious-plugins depends on audacious logic' is so confusing to me;-) So how can we "predict" the future? A possible solution (from crazy@FW) we use foo<2.0 dependency of bar, which indicates that only foo 1.x dependency is expected to work with bar. For example, then the packager can add both foo>=1.3 and foo<1.4 dependencies to his bar 1.3 package (foo 1.4 may work, but probably won't). And this will prevent users from upgrading foo 1.3 to foo 1.4 without dependency break (see the confusing audacious example above: audacious-plugins 1.3.5 is not expected to work with audacious-player 1.4.x). So my definition of foo<2.0: foo<=2.0 holds, but foo=2.0 doesn't. Bye, ngaba PS: I don't know whether foo>1.0 would be useful or not, maybe with conflicts only (<- predicted conflict ;-), but if we implemented '<', then probably we would implement '>' to enjoy the symmetry.

2 1

[pacman-dev] Package name and version check
by Nagy Gabor 17 Dec '07

17 Dec '07

Hi! I refer to this thread: http://www.archlinux.org/pipermail/pacman-dev/2007-November/010252.html Well, I agree with Dan and Aaron, quote: "Maybe I want my packages just named pkgname.lol". However, I don't see the clear rules, where (pkgname,pkgver) comes from in case of repos. I would like make a little comment here: Packages in sync (and local) dbs are identified by their directory names, not by %NAME% and %VERSION% in desc (reason: speed-up): see line 220 in be_files.c: if(_alpm_db_splitname(ent->d_name, pkg->name, pkg->version) != 0)... So we should make sure, that directory name contains the valid %NAME% and %VERSION% (or %NAME% and %VERSION% is not needed in desc) And of course %FILENAME% should point to a package with the correct %NAME% and %VERSION% <- we may want to check the .PKGINFO content of the (downloaded) pointed file, not the filename itself. However, I'm not sure if this is needed: then we should also check %DEPENDS%, %PROVIDES% and other fields... (checkdeps might have been fooled for example) Bye

3 2

[pacman-dev] [PATCH] Updated Italian Translation for pacman 3.1
by Giovanni Scafora 16 Dec '07

16 Dec '07

Hi, here's an updated translation to fix 1 fuzzy translation and some improvements. Thanks. -- Giovanni Scafora Arch Linux Trusted User (voidnull) http://www.archlinux.org linuxmania(a)gmail.com

1 0

Re: [pacman-dev] [arch-general] Package group xorg-video-drivers: intel conflict
by Xavier 15 Dec '07

15 Dec '07

On Sat, Dec 08, 2007 at 10:16:19PM +0100, Michael Towers wrote: > Aaron Griffin wrote: >> On Dec 8, 2007 11:04 AM, Michael Towers <gradgrind(a)online.de> wrote: >>> Since the addition of xf86-video-intel it has become impossible to >>> install the xorg-video-drivers group via the group name (because of the >>> conflict with xf86-video-i810). >>> >>> I guess there is no guideline outlawing this - I suppose something like >>> this could, theoretically, happen more often. But it is a bit annoying >>> when doing installations which are supposed to run on various machines. >>> >>> I don't want to make a request or anything here - I don't know what I >>> could ask for. I just thought I'd point it out. >> >> Hmmm, I'd say in cases like this we pick one that we prefer, and keep >> that in the group. /me shrugs >> >> Maybe FR that regarding these two drivers and we can see how Alex >> feels about it? >> >> > > http://bugs.archlinux.org/task/8874 > > Why can't we do pacman -S xorg-video-drivers --ignore xf86-video-i810 ? Though, it's probably a bad idea to put conflicting packages in the same group in the first place, but still.. Suppose "target" is part of "group", and target is in IgnorePkg, it might make sense that : * pacman -S group doesn't install target * pacman -S target installs target (because explictly asked) Anyway, here is a sample session, how I like them (it may have been mentioned already, but I don't remember where) : > sudo pacman -S xorg-video-drivers :: group xorg-video-drivers: xf86-video-intel :: Install whole content? [Y/n] :: group xorg-video-drivers: xf86-video-amd xf86-video-apm xf86-video-ark xf86-video-ati xf86-video-chips xf86-video-cirrus xf86-video-dummy xf86-video-fbdev xf86-video-glint xf86-video-i128 xf86-video-i740 xf86-video-i810 xf86-video-imstt xf86-video-intel xf86-video-mga xf86-video-neomagic xf86-video-nv xf86-video-radeonhd xf86-video-rendition xf86-video-s3 xf86-video-s3virge xf86-video-savage xf86-video-siliconmotion xf86-video-sis xf86-video-sisusb xf86-video-tdfx xf86-video-trident xf86-video-tseng xf86-video-unichrome xf86-video-v4l xf86-video-vesa xf86-video-vga xf86-video-via xf86-video-vmware xf86-video-voodoo :: Install whole content? [Y/n] warning: xf86-video-intel-2.1.1-3 is up to date -- reinstalling warning: xf86-video-vesa-1.3.0-5 is up to date -- reinstalling resolving dependencies... looking for inter-conflicts... error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: xf86-video-intel: conflicts with xf86-video-i810 Ok, xf86-video-i810 is not a conflict, so we won't ask the whole content next time. > sudo pacman -S xorg-video-drivers :: group xorg-video-drivers: xf86-video-intel :: Install whole content? [Y/n] :: group xorg-video-drivers: xf86-video-amd xf86-video-apm xf86-video-ark xf86-video-ati xf86-video-chips xf86-video-cirrus xf86-video-dummy xf86-video-fbdev xf86-video-glint xf86-video-i128 xf86-video-i740 xf86-video-i810 xf86-video-imstt xf86-video-intel xf86-video-mga xf86-video-neomagic xf86-video-nv xf86-video-radeonhd xf86-video-rendition xf86-video-s3 xf86-video-s3virge xf86-video-savage xf86-video-siliconmotion xf86-video-sis xf86-video-sisusb xf86-video-tdfx xf86-video-trident xf86-video-tseng xf86-video-unichrome xf86-video-v4l xf86-video-vesa xf86-video-vga xf86-video-via xf86-video-vmware xf86-video-voodoo :: Install whole content? [Y/n] n :: Install xf86-video-amd from group xorg-video-drivers? [Y/n] :: Install xf86-video-apm from group xorg-video-drivers? [Y/n] :: Install xf86-video-ark from group xorg-video-drivers? [Y/n] :: Install xf86-video-ati from group xorg-video-drivers? [Y/n] :: Install xf86-video-chips from group xorg-video-drivers? [Y/n] :: Install xf86-video-cirrus from group xorg-video-drivers? [Y/n] :: Install xf86-video-dummy from group xorg-video-drivers? [Y/n] :: Install xf86-video-fbdev from group xorg-video-drivers? [Y/n] :: Install xf86-video-glint from group xorg-video-drivers? [Y/n] :: Install xf86-video-i128 from group xorg-video-drivers? [Y/n] :: Install xf86-video-i740 from group xorg-video-drivers? [Y/n] :: Install xf86-video-i810 from group xorg-video-drivers? [Y/n] n :: Install xf86-video-imstt from group xorg-video-drivers? [Y/n] :: Install xf86-video-intel from group xorg-video-drivers? [Y/n] :: Install xf86-video-mga from group xorg-video-drivers? [Y/n] :: Install xf86-video-neomagic from group xorg-video-drivers? [Y/n] :: Install xf86-video-nv from group xorg-video-drivers? [Y/n] :: Install xf86-video-radeonhd from group xorg-video-drivers? [Y/n] :: Install xf86-video-rendition from group xorg-video-drivers? [Y/n] :: Install xf86-video-s3 from group xorg-video-drivers? [Y/n] :: Install xf86-video-s3virge from group xorg-video-drivers? [Y/n] :: Install xf86-video-savage from group xorg-video-drivers? [Y/n] :: Install xf86-video-siliconmotion from group xorg-video-drivers? [Y/n] :: Install xf86-video-sis from group xorg-video-drivers? [Y/n] :: Install xf86-video-sisusb from group xorg-video-drivers? [Y/n] :: Install xf86-video-tdfx from group xorg-video-drivers? [Y/n] :: Install xf86-video-trident from group xorg-video-drivers? [Y/n] :: Install xf86-video-tseng from group xorg-video-drivers? [Y/n] :: Install xf86-video-unichrome from group xorg-video-drivers? [Y/n] :: Install xf86-video-v4l from group xorg-video-drivers? [Y/n] :: Install xf86-video-vesa from group xorg-video-drivers? [Y/n] :: Install xf86-video-vga from group xorg-video-drivers? [Y/n] :: Install xf86-video-via from group xorg-video-drivers? [Y/n] :: Install xf86-video-vmware from group xorg-video-drivers? [Y/n] :: Install xf86-video-voodoo from group xorg-video-drivers? [Y/n] warning: xf86-video-intel-2.1.1-3 is up to date -- reinstalling warning: xf86-video-vesa-1.3.0-5 is up to date -- reinstalling resolving dependencies... looking for inter-conflicts... error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: xf86-video-unichrome: conflicts with xf86-video-via Oh no, I have to start everything again. Seriously, how practical is that? Personally, I never used it, and I don't see the point of this interactivity. I just do pacman -S group, I have a look at all the targets it wants to pull. And then, either I accept, or I refuse, and I run pacman -S again by picking the few targets I want manually. But if instead of only picking a few targets, you just want to exclude a few ones, then IgnorePkg should probably apply here. What do you think? There might be some important and common use cases I'm forgetting, which is why I bring this up here for discussion.

4 6

[pacman-dev] [PATCH] Updated Hungarian translation
by Nagy Gabor 12 Dec '07

12 Dec '07

Hi! Patch attached. Note: As Giovanni noted, the call-for-translators .po files weren't fully up-to-date. ---------------------------------------------------- SZTE Egyetemi Könyvtár - http://www.bibl.u-szeged.hu This mail sent through IMP: http://horde.org/imp/

1 0

[pacman-dev] [GIT] The official pacman repository branch, master, updated. v3.0.6-675-gf5478d6
by Dan McGee 11 Dec '07

11 Dec '07

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 f5478d68a67741236a2e9f42f2e524ee1bb26517 (commit) via 685a659656d670acb0d606f8e91c8984d47c98b5 (commit) via 9558639d8009483fbf422b138d020745986f82f1 (commit) via f8b113ed97652da62c217cef139c58ca1d75d647 (commit) via 565d2eeed5fdd85b516cbc76bc48be439e42c41f (commit) via 9781d0d637fb2a077b0c4b262af1e2fb4decc2a0 (commit) via 572bdb5c997846c426aba53392800e5866f725bd (commit) via bd83a1fd85c0e1e41be998b3633f613bce75f08c (commit) via 90d72bd24f67e1ec32525ca0c36fece4d6364eab (commit) via 7249c08bdf6beacc087607db558ef16d3527b9b6 (commit) via 815a2ead3ef2b8daedb9e93e5e141356d5003e6e (commit) from b6acb30aae5504736fd23f97402389baabbddb1b (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 f5478d68a67741236a2e9f42f2e524ee1bb26517 Author: Aaron Griffin <aaronmgriffin(a)gmail.com> Date: Thu Nov 29 23:39:51 2007 -0600 Add real scriptlet checking for pactest Due to commit da1222de2e30aabcae9d17bbfa10bbf0672338af, we can now use fakechroot to completely run scriptlet pactests Use "which" functionality so as not to REQUIRE it for all users Signed-off-by: Aaron Griffin <aaronmgriffin(a)gmail.com> Signed-off-by: Dan McGee <dan(a)archlinux.org> commit 685a659656d670acb0d606f8e91c8984d47c98b5 Author: Aaron Griffin <aaronmgriffin(a)gmail.com> Date: Thu Nov 29 23:37:53 2007 -0600 Add "which" path searching functionality to pactest Signed-off-by: Aaron Griffin <aaronmgriffin(a)gmail.com> commit 9558639d8009483fbf422b138d020745986f82f1 Author: Aaron Griffin <aaronmgriffin(a)gmail.com> Date: Thu Nov 29 23:30:57 2007 -0600 popen does NOT require /bin/sh in a subchroot I appears that when chrooted, the /bin/sh used by popen is that of the parent process. This is true until the process forks once chrooted, which we do not want to do. As such, this actually makes things nicer. We don't need a /bin/sh in a chroot to run install scriptlets, and don't need to check for it in the root directory Signed-off-by: Aaron Griffin <aaronmgriffin(a)gmail.com> Signed-off-by: Dan McGee <dan(a)archlinux.org> commit f8b113ed97652da62c217cef139c58ca1d75d647 Author: Aaron Griffin <aaronmgriffin(a)gmail.com> Date: Thu Nov 29 22:33:45 2007 -0600 Fail sanely on OUTPUT rules when --nolog is passed Check for existence of the logfile first, and output an error if not found Signed-off-by: Aaron Griffin <aaronmgriffin(a)gmail.com> Signed-off-by: Dan McGee <dan(a)archlinux.org> commit 565d2eeed5fdd85b516cbc76bc48be439e42c41f Author: Aaron Griffin <aaronmgriffin(a)gmail.com> Date: Thu Nov 29 13:58:00 2007 -0600 Correct scriptlet usage pattern The new pattern is as follows: . /path/to/scriptlet post_upgrade X Y This requires less frameworking in the install scripts (the three lines that shift and eval a function are nasty) Signed-off-by: Aaron Griffin <aaronmgriffin(a)gmail.com> Signed-off-by: Dan McGee <dan(a)archlinux.org> commit 9781d0d637fb2a077b0c4b262af1e2fb4decc2a0 Author: Dan McGee <dan(a)archlinux.org> Date: Mon Dec 10 22:55:22 2007 -0600 Update GNU GPL boilerplate and copyright dates Update the GPL boilerplate to direct people to the GNU website for a copy of the license, as well as bump all of Judd's copyrights to 2007. Signed-off-by: Dan McGee <dan(a)archlinux.org> commit 572bdb5c997846c426aba53392800e5866f725bd Author: Dan McGee <dan(a)archlinux.org> Date: Sun Nov 4 14:30:11 2007 -0600 pactest: if we are root, don't use fakeroot Signed-off-by: Dan McGee <dan(a)archlinux.org> commit bd83a1fd85c0e1e41be998b3633f613bce75f08c Author: Dan McGee <dan(a)archlinux.org> Date: Mon Dec 10 12:06:12 2007 -0600 Updates to PKGBUILD manpage Make the manpage a little more distro agnostic by referring to ABS in the context of Arch Linux, and saying that prototype files are also available with the pacman source. Signed-off-by: Dan McGee <dan(a)archlinux.org> commit 90d72bd24f67e1ec32525ca0c36fece4d6364eab Author: Dan McGee <dan(a)archlinux.org> Date: Sun Dec 9 13:49:38 2007 -0600 Rename prototype install file Most (sane) people name their install file pkgname.install, and this move of the prototype reflects that. Signed-off-by: Dan McGee <dan(a)archlinux.org> commit 7249c08bdf6beacc087607db558ef16d3527b9b6 Author: Dan McGee <dan(a)archlinux.org> Date: Sat Dec 8 23:42:04 2007 -0600 Improve changelog handling through addition of open/read/close functions Thanks to Allan for inspiring all this work on what was one little TODO item in the codebase. :) Change changelog handling so we can now dump a changelog from both installed packages and package files (fixes FS#7371). We do this by moving all of the machinery to the backend where it should have been in the first place. The changelog reading is now done through a open/read/close interface similar to the fopen/fread/fclose functions (can you guess how it is done?). It is buffered by the frontend, so programs using the library can read as much or as little as they want at a time. Unfortunately, I could not implement a changelog_feof function due to some shortcomings of libarchive. However, I left the stub code in there, commented out, in case it becomes possible later or anyone wants to take a stab at it. Original-work-by: Allan McRae <mcrae_allan(a)hotmail.com> Improved-by: Chantry Xavier <shiningxc(a)gmail.com> Signed-off-by: Dan McGee <dan(a)archlinux.org> commit 815a2ead3ef2b8daedb9e93e5e141356d5003e6e Author: Giovanni Scafora <linuxmania(a)gmail.com> Date: Sun Dec 9 11:38:08 2007 +0100 Updated Italian Translation Signed-off-by: Giovanni Scafora <linuxmania(a)gmail.com> Signed-off-by: Dan McGee <dan(a)archlinux.org> ----------------------------------------------------------------------- Summary of changes: COPYING | 31 +- contrib/pacdiff | 4 +- contrib/pacsearch | 3 +- contrib/{install.proto => proto.install} | 4 - contrib/re-pacman | 4 +- doc/PKGBUILD.5.txt | 17 +- lib/libalpm/add.c | 4 +- lib/libalpm/add.h | 6 +- lib/libalpm/alpm.c | 4 +- lib/libalpm/alpm.h | 11 +- lib/libalpm/alpm_list.c | 6 +- lib/libalpm/alpm_list.h | 6 +- lib/libalpm/backup.c | 4 +- lib/libalpm/backup.h | 6 +- lib/libalpm/be_files.c | 4 +- lib/libalpm/cache.c | 6 +- lib/libalpm/cache.h | 6 +- lib/libalpm/conflict.c | 6 +- lib/libalpm/conflict.h | 6 +- lib/libalpm/db.c | 6 +- lib/libalpm/db.h | 6 +- lib/libalpm/delta.c | 4 +- lib/libalpm/delta.h | 4 +- lib/libalpm/deps.c | 6 +- lib/libalpm/deps.h | 6 +- lib/libalpm/error.c | 6 +- lib/libalpm/error.h | 6 +- lib/libalpm/group.c | 6 +- lib/libalpm/group.h | 6 +- lib/libalpm/handle.c | 6 +- lib/libalpm/handle.h | 6 +- lib/libalpm/log.c | 6 +- lib/libalpm/log.h | 6 +- lib/libalpm/md5.c | 5 +- lib/libalpm/md5.h | 5 +- lib/libalpm/package.c | 115 +++++++- lib/libalpm/package.h | 6 +- lib/libalpm/remove.c | 6 +- lib/libalpm/remove.h | 6 +- lib/libalpm/server.c | 4 +- lib/libalpm/server.h | 4 +- lib/libalpm/sync.c | 6 +- lib/libalpm/sync.h | 6 +- lib/libalpm/trans.c | 19 +- lib/libalpm/trans.h | 6 +- lib/libalpm/util.c | 6 +- lib/libalpm/util.h | 6 +- pactest/pactest.py | 4 +- pactest/pmdb.py | 4 +- pactest/pmenv.py | 4 +- pactest/pmfile.py | 4 +- pactest/pmpkg.py | 4 +- pactest/pmrule.py | 12 +- pactest/pmtest.py | 15 +- pactest/tests/scriptlet001.py | 17 +- pactest/tests/scriptlet002.py | 17 +- pactest/util.py | 12 +- po/it.po | 478 ++++++++++++++++-------------- scripts/abs.sh.in | 4 +- scripts/gensync.sh.in | 4 +- scripts/makepkg.sh.in | 4 +- scripts/makeworld.sh.in | 4 +- scripts/pacman-optimize.sh.in | 4 +- scripts/rankmirrors.py.in | 4 +- scripts/repo-add.sh.in | 4 +- scripts/repo-remove.sh.in | 4 +- scripts/updatesync.sh.in | 4 +- src/pacman/add.c | 4 +- src/pacman/callback.c | 4 +- src/pacman/callback.h | 4 +- src/pacman/conf.c | 6 +- src/pacman/conf.h | 6 +- src/pacman/deptest.c | 6 +- src/pacman/package.c | 44 ++-- src/pacman/package.h | 8 +- src/pacman/pacman.c | 4 +- src/pacman/pacman.h | 4 +- src/pacman/query.c | 13 +- src/pacman/remove.c | 6 +- src/pacman/sync.c | 4 +- src/pacman/util.c | 6 +- src/pacman/util.h | 4 +- src/util/testdb.c | 4 +- src/util/testpkg.c | 4 +- src/util/vercmp.c | 4 +- 85 files changed, 574 insertions(+), 586 deletions(-) rename contrib/{install.proto => proto.install} (91%) hooks/post-receive -- The official pacman repository

2 1

[pacman-dev] [PATCH] Database with index??
by JJDaNiMoTh 10 Dec '07

10 Dec '07

Hello to all. After 2 weeks of intensive work (:P) I'm glad to post the first proof-of-concept code about using index in our life. Do you remember the discussion Backend DB, where we talked about in November? If not, see http://archlinux.org/pipermail/pacman-dev/2007-November/009938.html : Mikos proposed to see how pacman works with a big database file, like pacman1, but with a smaller index, that contains some information ( like pkgname - pkgver ) and where an entries start and finish in the big database. So, I've thinked about the making of index every time that users do pacman -Sy; but we haven't time to re-make index all times; so, I've coded all on the "B-side" of pacman: repo-add. The result are two file: txtdb.idx ===> big, big database file; index.idx ===> smaller file, that has this format: pkgname - pkgver - line_start - line_end Example: chpax - 0.12 - 22 - 53 Reading the line that contains "chpax", I see that the entries in txtdb.idx starts on line 22 and ends on line 53. Note that this patch doesn't modify the old way to make database. It simply add a new one :D Now the only part that I need to code is the pacman-side. Why I haven't coded this yet? Because pacman-side is ( in my point of view ) the more difficult part, and ( last but no last ) I want to hear your opinion about this. Excuse my elementary english ( I have rewrited 3 times the introduction to the patch :D ) and excuse If I can't explain how patch works ( I don't write any comments.. ). I will do all ( comments and explain ) tomorrow.. now it's very late :) Thanks -- JJDaNiMoTh - ArchLinux Trusted User

2 2