- Pacman-dev - lists.archlinux.org

[pacman-dev] [PATCH] Add pactest for IgnoreGroup.
by Nathan Jones 12 Nov '07

12 Nov '07

Also tell pactest to reset IgnoreGroup like it does for IgnorePkg. Signed-off-by: Nathan Jones <nathanj(a)insightbb.com> --- pactest/pmtest.py | 1 + pactest/tests/sync138.py | 22 ++++++++++++++++++++++ 2 files changed, 23 insertions(+), 0 deletions(-) create mode 100644 pactest/tests/sync138.py diff --git a/pactest/pmtest.py b/pactest/pmtest.py index 00dd3cb..e0b3fd4 100755 --- a/pactest/pmtest.py +++ b/pactest/pmtest.py @@ -84,6 +84,7 @@ class pmtest: self.option = { "noupgrade": [], "ignorepkg": [], + "ignoregroup": [], "noextract": [] } diff --git a/pactest/tests/sync138.py b/pactest/tests/sync138.py new file mode 100644 index 0000000..410c7f0 --- /dev/null +++ b/pactest/tests/sync138.py @@ -0,0 +1,22 @@ +self.description = "Sysupgrade of packages in 'IgnoreGroup'" + +sp1 = pmpkg("pkg1", "1.0-2") +sp2 = pmpkg("pkg2", "1.0-2") +sp2.groups = ["grp"] + +for p in sp1, sp2: + self.addpkg2db("sync", p) + +lp1 = pmpkg("pkg1") +lp2 = pmpkg("pkg2") + +for p in lp1, lp2: + self.addpkg2db("local", p) + +self.option["ignoregroup"] = ["grp"] + +self.args = "-Su" + +self.addrule("PACMAN_RETCODE=0") +self.addrule("PKG_VERSION=pkg1|1.0-2") +self.addrule("!PKG_MODIFIED=pkg2") -- 1.5.3.5

1 0

[pacman-dev] [PATCH] makepkg: remove .pacsave files when uninstalling dependencies
by Roman Kyrylych 12 Nov '07

12 Nov '07

Hi! This is a small patch that fixes this: ==> Compressing package... ==> Removing installed dependencies... ERROR: ld.so: object 'libfakeroot.so' from LD_PRELOAD cannot be preloaded: ignored. checking dependencies... done. Targets: at Do you want to remove these packages? [Y/n] warning: /etc/at.deny saved as /etc/at.deny.pacsave (1/1) removing at [#####################] 100% ==> Finished making: gnome-schedule (Sun Nov 11 16:22:29 EET 2007) -- Roman Kyrylych (Роман Кирилич)

3 3

[pacman-dev] add043.py: alpm_depcmp and provisions
by Nagy Gabor 12 Nov '07

12 Nov '07

Hi! Give a look at the following pactest: ----add043.py---- self.description = "provision>=1.0-2 needed" p1 = pmpkg("pkg1", "1.0-2") p1.depends = ["provision>=1.0-2"] self.addpkg(p1) p2 = pmpkg("pkg2", "1.0-2") p2.provides = ["provision"] self.addpkg2db("local", p2) self.args = "-A %s" % p1.filename() self.addrule("PACMAN_RETCODE=1") self.addrule("!PKG_EXIST=pkg1") self.addrule("PKG_EXIST=pkg2") ----------------- This currently fails. IMHO this is a bug: alpm_depcmp uses the package version in the "provision case" too (so if you change p1.depends to "provision<=1.0-1", then the pactest will pass.) This is a good time to ask you about versioned provisions again (before fix): Personally, I like the idea; and the implementation needs ~0 effort and would cause ~0 slowdown; and would be 100% compatible with "no-version" provisions. I don't know if package maintainers need this feature or not (someone could ask them on arch-* ML <- I'm not a subscriber there), but this is just an extra feature, they needn't use it. Bye, ngaba

3 2

[pacman-dev] lstat issue / fileconflict001 pactest
by Xavier 12 Nov '07

12 Nov '07

Following the discussion started in the comments of bug 7484, because I think it's more appropriate : http://bugs.archlinux.org/task/7484#comment20837 I recently discovered that a trailing / is very important when using lstat, for directory symlinks. In the following situation : symdir -> realdir/ lstat(symdir) stats the link itself, but lstat(symdir/) stats realdir. So lstat(symdir/) seems equivalent to stat(symdir). The archive extraction code in add.c that Dan rewrote didn't take this into consideration, so he added a new _alpm_lstat that removes the trailing / when there is one : http://projects.archlinux.org/git/?p=pacman.git;a=commit;h=b55abdce7aebb142… A little typo in _alpm_lstat (path instead of newpath) made this change not active yet. As Dan noticed, fixing this makes fileconflict001 pass. The only purpose of this mail is explaining why. So in this pactest, we have the following situation : dir/realdir/ dir/symdir -> realdir Then pkg1 installs dir/realdir/file , and pkg2 installs dir/symdir/file . Since in this case, symdir points to realdir, pkg1 and pkg2 have a fileconflict on "file". But if fileconflict001 pass after the bugfix mentioned above, it's not because pacman detects there is a package<->package conflict between dir/realdir/file and dir/symdir/file. Instead, it detects a filesystem <-> package conflict between dir/symdir/ from pkg2 (which is a real directory there), and the dir/symdir symlink on the filesystem. So that's plain wrong. The fileconflict code currently does a lstat(dir/symdir/), which doesn't stat the symdir symlink, but the real directory realdir. So it treated dir/symdir/ as a directory, and ignored it : 336 /* stat the file - if it exists, do some checks / 337 if(_alpm_lstat(path, &buf) != 0) { 338 continue; 339 } 340 if(S_ISDIR(buf.st_mode)) { 341 _alpm_log(PM_LOG_DEBUG, "%s is a directory, not a conflict\n", path); Now, with the new behavior of _alpm_lstat, the code does a lstat(dir/symdir), which stats the symlink. And the following code will treat this as a conflict. The case of fileconflict001 is probably another situation easier to detect during the transaction (coupled with a rollback system), rather than beforehand. Otherwise, maybe the file conflict code should keep using the normal lstat, instead of _alpm_lstat which removes the trailing /.

4 9

[pacman-dev] Generate doxygen man pages on "make dist"
by Aaron Griffin 12 Nov '07

12 Nov '07

Would anyone have a problem with generating doxygen man pages on the "make dist" target? The reason I ask, is that having a doxygen makedepend is breaking our little core/extra repo separation, and this is the cleanest fix. It also cleans up building pacman. If you ask me, I don't see a problem with pre-generating them Opinions?

2 2

[pacman-dev] TotalDownload option.
by Nathan Jones 12 Nov '07

12 Nov '07

Sample output: $ sudo pacman -S gcc gcc-fortran gcc-libs resolving dependencies... done. looking for inter-conflicts... done. Targets: gcc-libs-4.2.2-2 [1.06 MB] gcc-4.2.2-3 [8.92 MB] gcc-fortran-4.2.2-1 [2.91 MB] Total Package Size: 12.89 MB Total Download Size: 12.89 MB Proceed with installation? [Y/n] :: Retrieving packages from core... gcc-libs-4.2.2-2-i686 1081.1K 503.8K/s 00:00:02 [#--------------------] 8% gcc-4.2.2-3-i686 10.0M 302.1K/s 00:00:34 [################-----] 77% :: Retrieving packages from extra... gcc-fortran-4.2.2-1-... 12.9M 338.0K/s 00:00:39 [#####################] 100% checking package integrity... done. (3/3) checking for file conflicts [#####################] 100% (1/3) upgrading gcc-libs [#####################] 100% (2/3) upgrading gcc [#####################] 100% (3/3) upgrading gcc-fortran [#####################] 100%

8 20

[pacman-dev] documenting the base-devel split
by Jonathan 12 Nov '07

12 Nov '07

I haven't been able to find any arch documentation (besides the mailing lists) on the splitting of base into base and base-devel groups. The main need is for people to understand the need to install the base-devel group before building packages. the makepkg man page seems like a good place for this. Jonathan 'wide-eye'

7 13

[pacman-dev] [GIT] The official pacman repository branch, master, updated. v3.0.0-531-gd0d5848
by Aaron Griffin 11 Nov '07

11 Nov '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 d0d58489ff8b4458719e4bceb6a5d7290c99588a (commit) via 2ee90ddae23dd86c68223c0d6c49f0b92d62429d (commit) from bdab234d977dd2e9417a39f5191e495d5c460ee7 (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 d0d58489ff8b4458719e4bceb6a5d7290c99588a Author: Aaron Griffin <aaronmgriffin(a)gmail.com> Date: Tue Nov 6 22:50:21 2007 -0600 Add STRDUP macro to mirror MALLOC/CALLOC Signed-off-by: Aaron Griffin <aaronmgriffin(a)gmail.com> commit 2ee90ddae23dd86c68223c0d6c49f0b92d62429d Author: Aaron Griffin <aaronmgriffin(a)gmail.com> Date: Tue Nov 6 00:55:45 2007 -0600 Maintain list tail pointers in the head node List head nodes contain null 'prev' pointer, which we can (ab)use to maintain a back reference to the tail pointer of the list. While list additions are not _significantly_ improved, they are still sped up. Original $ time pacman -Qo /usr/bin/wtpt /usr/bin/wtpt is owned by lcms 1.17-2 real 0m3.623s user 0m1.883s sys 0m1.473s New $ time pacman -Qo /usr/bin/wtpt /usr/bin/wtpt is owned by lcms 1.17-2 real 0m2.006s user 0m0.263s sys 0m1.627s Signed-off-by: Aaron Griffin <aaronmgriffin(a)gmail.com> ----------------------------------------------------------------------- Summary of changes: lib/libalpm/alpm_list.c | 59 +++++++++++++++++++++++++++++++++++------------ lib/libalpm/remove.c | 3 +- lib/libalpm/util.h | 2 + 3 files changed, 48 insertions(+), 16 deletions(-) hooks/post-receive -- The official pacman repository

5 12

[pacman-dev] [PATCH] Incorrect usage of alpm_db_whatprovides in sync.c
by Nagy Gabor 10 Nov '07

10 Nov '07

From 82e113f07a8d70e8cc0a1cbd2b1743981494d333 Mon Sep 17 00:00:00 2001 From: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Date: Sat, 10 Nov 2007 18:11:40 +0100 Subject: [PATCH] Incorrect usage of alpm_db_whatprovides in sync.c The old code thought that alpm_db_whatprovides returns with a list of strings (package names). Signed-off-by: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> --- lib/libalpm/sync.c | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/lib/libalpm/sync.c b/lib/libalpm/sync.c index 7791e74..e696b58 100644 --- a/lib/libalpm/sync.c +++ b/lib/libalpm/sync.c @@ -280,9 +280,9 @@ int _alpm_sync_addtarget(pmtrans_t *trans, pmdb_t *db_local, alpm_list_t *dbs_sy if(!p) { RET_ERR(PM_ERR_PKG_NOT_FOUND, -1); } + spkg = (pmpkg_t *) p->data; _alpm_log(PM_LOG_DEBUG, "found '%s' as a provision for '%s'\n", - (char *)p->data, targ); - spkg = _alpm_db_get_pkgfromcache(db, p->data); + alpm_pkg_get_name(spkg), targ); alpm_list_free(p); } } @@ -304,9 +304,9 @@ int _alpm_sync_addtarget(pmtrans_t *trans, pmdb_t *db_local, alpm_list_t *dbs_sy pmdb_t *db = j->data; alpm_list_t *p = _alpm_db_whatprovides(db, targ); if(p) { + spkg = (pmpkg_t *) p->data; _alpm_log(PM_LOG_DEBUG, "found '%s' as a provision for '%s' in db '%s'\n", - (char *)p->data, targ, db->treename); - spkg = _alpm_db_get_pkgfromcache(db, p->data); + alpm_pkg_get_name(spkg), targ, db->treename); alpm_list_free(p); } } -- 1.5.3.4

1 0

[pacman-dev] Hypotetic pacman's db structure (SQL)
by JJDaNiMoTh 09 Nov '07

09 Nov '07

Hello to all. I'm writing an example databe structure for pacman db ( may be useful when someone decide to use SQLite as backend, and not simple text file). [1] Tell me your impression, if something can be made, revisioned or deleted. Views isn't complete, because I need some data stored in the db to test it; and, of course, I'm writing a simple script that parse all packages information stored under /var/lib/pacman to this db schemas ( if anyone wants help, it's welcome :D ) Thanks [1] http://rafb.net/p/XxK62l68.html (Version 0.01) -- JJDaNiMoTh - ArchLinux Trusted User

5 7