- Pacman-dev - lists.archlinux.org

[pacman-dev] [PATCH] Update pactest README
by Nagy Gabor 22 Jul '08

22 Jul '08

From ad3056757dcc675ee48324cf479b34a1c40dcd0c Mon Sep 17 00:00:00 2001 From: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Date: Tue, 22 Jul 2008 13:15:02 +0200 Subject: [PATCH] Update pactest README Signed-off-by: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> --- pactest/README | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/pactest/README b/pactest/README index b995edc..5d4e47f 100644 --- a/pactest/README +++ b/pactest/README @@ -288,7 +288,7 @@ Possible rules are: PKG_GROUPS=name|group PKG_PROVIDES=name|providename PKG_DEPENDS=name|depname - PKG_REQUIREDBY=name|reqbyname + PKG_OPTDEPENDS=name|depname PKG_REASON=name|intvalue PKG_FILES=name|filename PKG_BACKUP=name|backupname @@ -303,6 +303,8 @@ its DEPENDS field. FILE_EXIST=path/to/file FILE_MODIFIED=path/to/file + FILE_MODE=path/to/file|octal + FILE_TYPE=path/to/file|type (possible types: dir, file, link) FILE_PACNEW=path/to/file FILE_PACSAVE=path/to/file FILE_PACORIG=path/to/file -- 1.5.6.4

1 0

[pacman-dev] [PATCH] New fileconflict004.py pactest
by Nagy Gabor 22 Jul '08

22 Jul '08

From 92d5c1dbe3b1ecdb4a011a67a4c7719e240d861a Mon Sep 17 00:00:00 2001 From: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Date: Tue, 22 Jul 2008 12:48:59 +0200 Subject: [PATCH] New fileconflict004.py pactest Thread: http://www.archlinux.org/pipermail/pacman-dev/2008-July/012465.html Signed-off-by: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> --- pactest/tests/fileconflict004.py | 19 +++++++++++++++++++ 1 files changed, 19 insertions(+), 0 deletions(-) create mode 100644 pactest/tests/fileconflict004.py diff --git a/pactest/tests/fileconflict004.py b/pactest/tests/fileconflict004.py new file mode 100644 index 0000000..a5347cc --- /dev/null +++ b/pactest/tests/fileconflict004.py @@ -0,0 +1,19 @@ +self.description = "dir->symlink change during package upgrade (no conflict)" + +p1 = pmpkg("pkg1", "1.0-1") +p1.files = ["test/", + "test/file"] +self.addpkg2db("local", p1) + +p2 = pmpkg("pkg1", "2.0-1") +p2.files = ["test2/", + "test2/file2", + "test -> test2"] +self.addpkg2db("sync", p2) + +self.args = "-S pkg1" + +self.addrule("PACMAN_RETCODE=0") +self.addrule("PKG_EXIST=pkg1") +self.addrule("PKG_VERSION=pkg1|2.0-1") +self.addrule("FILE_TYPE=test|link") -- 1.5.6.4

1 0

[pacman-dev] [PATCH] Re-enable --debug with -Sw and -Sp
by Nagy Gabor 21 Jul '08

21 Jul '08

From c533684914d28407a0a7399e3026c747987d5de3 Mon Sep 17 00:00:00 2001 From: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Date: Mon, 21 Jul 2008 13:57:02 +0200 Subject: [PATCH] Re-enable --debug with -Sw and -Sp Commit 874190827676e3a974e8c5fef6c51b9e9d6b60fa disabled --debug in these cases. We just clear PM_LOG_WARNING flag now. Signed-off-by: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> --- src/pacman/sync.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/pacman/sync.c b/src/pacman/sync.c index b154b91..20daada 100644 --- a/src/pacman/sync.c +++ b/src/pacman/sync.c @@ -740,7 +740,7 @@ int pacman_sync(alpm_list_t *targets) /* Display only errors with -Sp and -Sw operations */ if(config->flags & (PM_TRANS_FLAG_DOWNLOADONLY | PM_TRANS_FLAG_PRINTURIS)) { - config->logmask = PM_LOG_ERROR; + config->logmask = config->logmask & ~PM_LOG_WARNING; } /* clean the cache */ -- 1.5.6.3

3 2

[pacman-dev] [translation] Updated Portuguese (Brazil) translation
by Hugo Doria 21 Jul '08

21 Jul '08

Updated Portuguese (Brazil) translation. -- Hugo

3 2

[pacman-dev] ldconfig runs twice in case of replaces
by Nagy Gabor 21 Jul '08

21 Jul '08

Hi! I've just discovered that ldconfig runs twice, if the sync transaction creates a remove transaction too (%REPLACES%, conflict resolving). IMHO we should move ldconfig call to trans.c to alpm_trans_commit. Opinions? Bye

2 3

[pacman-dev] String freeze for 3.2 release
by Dan McGee 21 Jul '08

21 Jul '08

Allan has finally bugged me enough that its time for our pacman codebase to see the light and a new 3.2 release. So here is the call for the string freeze. I've CC-ed this to the Arch General list to see if anyone there is interested in helping out. PLEASE reply to the pacman-dev mailing list if you have questions or want to help out but are not sure how. Our pacman translation policy is outlined here. The important sections for translators are the introduction and up to (and including) pre-release updates. http://www.archlinux.org/pacman/translation-help.html As stated in the above document, PO files have been made available to translate: http://code.toofishes.net/pacman/po_files/ I would like to get the release out in 7 days or so, so the sooner the better for the translations. Languages we currently have: cs:Vojtěch Gondžala <vojtech.gondzala(a)gmail.com> de: Matthias Gorissen <matthias(a)archlinux.de> en_GB: Jeff Bailes <thepizzaking(a)gmail.com> es: Juan Pablo Gonzalez <jotapesan(a)gmail.com>, Imanol Celaya <ilcra1989(a)gmail.com> fr: Xavier Chantry <shiningxc(a)gmail.com> hu: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> it: Giovanni Scafora <linuxmania(a)gmail.com> pl: Jaroslaw Swierczynski <swiergot(a)gmail.com> pt_BR: João Felipe Santos <jfsantos(a)archlinux-br.org> ru: Sergey Tereschenko <serg.partizan(a)gmail.com> tr: Samed Beyribey <beyribey(a)gmail.com> zh_CN: 甘露(Lu.Gan) <rhythm.gan(a)gmail.com> If you wish to help translate, but your language is already listed as handled by someone, please contact them at the above addresses. If the language is listed as "no current translator", then please reply to ALL on this message stating you are doing the translation so we do not have duplicated effort (although you are more than welcome to work in teams). Once you have updated or completed a translation, simply tar and gzip the files up and send them back to pacman-dev(a)archlinux.org with a [translation] prefix in the message. For those that are used to the old method of updating translations (GIT patches), those are still acceptable as well. Please prefix the patch with "translation:" so it can be picked out easily. Any questions should be answered if you reply to this email on the list. -Dan

5 28

[pacman-dev] [feature request] ignore lost+found in /var/lib/pacman when running -Sc
by solsTiCe d'Hiver 20 Jul '08

20 Jul '08

hi, i am running pacman db inside a loop (humm to speed up some pacman operation) and when i run pacman -Sc (or -Scc); i got ... Do you want to remove unused repositories? [Y/n] y Do you want to remove /var/lib/pacman/lost+found? [Y/n] n it's because i have a lost+found directory in /var/lib/pacman because it's the root of a filesystem. i find the question annyoing, as lost+found is NOT an unused repository. may be you could just ignore lost+found (on -Sc) so that the last question above is not asked ? that will be be really unfortunate if a real repo uses that name. so simply do not ask the user. on the other hand, as the user is asked about that where is the problem ? if ever there are some files in lost+found, he/she would have still plenty of time to fix it because he/she has to run manually a -Sc command. and if there is a problem the first to do is not to run -Sc ! a good or bad idea ? your call

4 4

[pacman-dev] [translation] Polish translation for pacman 3.2
by Mateusz Herych 19 Jul '08

19 Jul '08

Hi. Here is updated Polish translation for pacman 3.2. Regards, Mateusz.

2 2

[pacman-dev] [PATCH] Fix some memleaks in alpm/add.c
by Nagy Gabor 19 Jul '08

19 Jul '08

From b9673a106b1f985cb81f620f394620e6eca88516 Mon Sep 17 00:00:00 2001 From: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Date: Tue, 15 Jul 2008 13:30:34 +0200 Subject: [PATCH] Fix some memleaks in alpm/add.c In case of error some allocated memory wasn't freed in commit_single_pkg. Note: The return value of this function is not used. Signed-off-by: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> --- lib/libalpm/add.c | 20 +++++++++++++------- 1 files changed, 13 insertions(+), 7 deletions(-) diff --git a/lib/libalpm/add.c b/lib/libalpm/add.c index 5bf3fcd..3b60fb3 100644 --- a/lib/libalpm/add.c +++ b/lib/libalpm/add.c @@ -689,7 +689,7 @@ static int commit_single_pkg(pmpkg_t *newpkg, int pkg_current, int pkg_count, /* set up fake remove transaction */ int ret = upgrade_remove(oldpkg, newpkg, trans, db); if(ret != 0) { - return(ret); + goto cleanup; } } @@ -701,7 +701,9 @@ static int commit_single_pkg(pmpkg_t *newpkg, int pkg_current, int pkg_count, _alpm_log(PM_LOG_DEBUG, "extracting files\n"); if ((archive = archive_read_new()) == NULL) { - RET_ERR(PM_ERR_LIBARCHIVE, -1); + pm_errno = PM_ERR_LIBARCHIVE; + ret = -1; + goto cleanup; } archive_read_support_compression_all(archive); @@ -710,7 +712,9 @@ static int commit_single_pkg(pmpkg_t *newpkg, int pkg_current, int pkg_count, _alpm_log(PM_LOG_DEBUG, "archive: %s\n", newpkg->origin_data.file); if(archive_read_open_filename(archive, newpkg->origin_data.file, ARCHIVE_DEFAULT_BYTES_PER_BLOCK) != ARCHIVE_OK) { - RET_ERR(PM_ERR_PKG_OPEN, -1); + pm_errno = PM_ERR_PKG_OPEN; + ret = -1; + goto cleanup; } /* save the cwd so we can restore it later */ @@ -772,7 +776,7 @@ static int commit_single_pkg(pmpkg_t *newpkg, int pkg_current, int pkg_count, } if(errors) { - ret = 1; + ret = -1; if(is_upgrade) { _alpm_log(PM_LOG_ERROR, _("problem occurred while upgrading %s\n"), newpkg->name); @@ -798,7 +802,9 @@ static int commit_single_pkg(pmpkg_t *newpkg, int pkg_current, int pkg_count, alpm_pkg_get_name(newpkg), alpm_pkg_get_version(newpkg)); alpm_logaction("error: could not update database entry %s-%s\n", alpm_pkg_get_name(newpkg), alpm_pkg_get_version(newpkg)); - RET_ERR(PM_ERR_DB_WRITE, -1); + pm_errno = PM_ERR_DB_WRITE; + ret = -1; + goto cleanup; } if(_alpm_db_add_pkgincache(db, newpkg) == -1) { @@ -833,9 +839,9 @@ static int commit_single_pkg(pmpkg_t *newpkg, int pkg_current, int pkg_count, EVENT(trans, PM_TRANS_EVT_ADD_DONE, newpkg, oldpkg); } +cleanup: _alpm_pkg_free(oldpkg); - - return(0); + return(ret); } int _alpm_add_commit(pmtrans_t *trans, pmdb_t *db) -- 1.5.6.2

3 5

[pacman-dev] Linking to OpenSSL
by Teran McKinney 19 Jul '08

19 Jul '08

Hi, I have been working on an Arch fork for the past several months, and thus have been following Arch developments closely. I noticed this commit ( http://projects.archlinux.org/gitweb.cgi?p=pacman.git;a=commit;h=b8a66d6859… ), where OpenSSL replaces the usage of md5sum and sha1sum utilities for Pacman. While I like the idea of using libraries instead of external binaries, I feel that linking to OpenSSL complicates a few things. For one, it is big, and must be included with any non-static binaries of Pacman (in the installer, this would not be so ideal, unless OpenSSL is included anyways). Another, is that it is simply not legal under the GPL. OpenSSL includes an advertising clause that makes it incompatible with the GPL. Wget and climm had to modify their GPL licenses to link to it ( http://en.wikipedia.org/wiki/Openssl#Licensing ). I purpose using GNUTLS instead. It is released under the LGPLv2.1, should be fully capable, and is compatible with the GPL. Many projects that use OpenSSL can also optionally link to GNUTLS instead, so I would suggest doing so with all possible packages (lftp, elinks, wget). What are your thoughts about this? Pacman is an excellent package manager; thank you for all of the work that you put into it. Cheers, Teran (sega01)

3 3