May 2007 - Pacman-dev - lists.archlinux.org

[pacman-dev] slower ftp access with pacman 3 ?
by Xavier 08 May '07

08 May '07

2007/5/8, Aaron Griffin <aaronmgriffin(a)gmail.com>: > > That one is problematic and is due to the symlinking on the servers. > There's no way to know what it should do because 'PWD' returns the > wrong directory. > yes, I was just wondering if it was possible to detect symlinks, but I don't think ftp allows this. > Ideally we need to fix the ftp setup on the main servers and the > mirrors though (0.8 should be a symlink to current, not the other way > around). But you could try using the 0.8 path in your mirror config > and see if that helps. > I don't know, I find it more logical to have current pointing to the current version. Having it the other way around would indeed solve the problem, but I find it a bit odd. Using 0.8 in the config directly indeed works, since it's a real directory. Anyway, this problem only occurs when downloading several packages from current. For syncing, it has to change path for each repo (current, then extra, then ...), so there is another problem. Did the ftp code change a lot between pacman 2 and pacman 3? Also, why is ftp used by default for all mirrors, even though many are available through both protocols. What's wrong with http? It has much faster access, but maybe also some obvious downsides I don't know about?

4 4

[pacman-dev] slower ftp access with pacman 3 ?
by Xavier 08 May '07

08 May '07

I'm using the same mirror (mir1.archlinuxfr.org) for the 5 repos (testing current extra community unstable), and I found that syncing was much slower after upgrading to pacman 3. I made some measures using time pacman -Sy : pacman 3 ftp : 4,3s http : 0,5s pacman 2 ftp : 2,5s http : 4,5s It looks like pacman 2 with http doesn't work correctly. It seems it's the only case where pacman can't detect the databases didn't change, and download them again. So using http with pacman 3 is by far the fastest solution. What are the downsides using http over ftp? But this slowdown in pacman 3 with ftp is still strange. Any ideas what could have caused it? Also, it's funny what happens when, for example, downloading 2 packages from current : >>> PWD <<< 257 "/archlinux/0.8/os/i686" >>> CDUP <<< 250 Directory successfully changed. >>> PWD <<< 257 "/archlinux/0.8/os" >>> CDUP <<< 250 Directory successfully changed. >>> PWD <<< 257 "/archlinux/0.8" >>> CDUP <<< 250 Directory successfully changed. >>> PWD <<< 257 "/archlinux" >>> CWD current <<< 250 Directory successfully changed. >>> CWD os <<< 250 Directory successfully changed. >>> CWD i686 <<< 250 Directory successfully changed. ie, libdownload is already in the correct directory, /archlinux/0.8/os/i686 , but it doesn't know current is a link to 0.8 , so it believes it's in the wrong directory, and goes back to /archlinux and returns in current/os/i686 I'm not sure if it's possible to avoid that though, is it?

3 2

[pacman-dev] File unavailable (e.g., file not found, no access)
by Scott Horowitz 08 May '07

08 May '07

I get this error with pacman3 (almost?) every single time that I have to download multiple packages. Usually it will download the first package fine and then give the error "File unavailable (e.g., file not found, no access)" on the subsequent package. Normal: Beginning upgrade process... :: Retrieving packages from extra... libbonoboui 381.9K 572.6K/s 00:00:01 [#########################################################] 100% error: failed retrieving file 'gnome-keyring-0.8.1-2.pkg.tar.gz' from locke.suu.edu : File unavailable (e.g., file not found, no access) error: failed retrieving file 'libgnomeui-2.18.1-2.pkg.tar.gz' from locke.suu.edu : File unavailable (e.g., file not found, no access) error: failed retrieving file 'gnome-desktop-2.18.1-1.pkg.tar.gz' from locke.suu.edu : File unavailable (e.g., file not found, no access) and so on... Using --debug=3: http://pastebin.archlinux.org/2861 The whole CWD <random letter> seems awfully strange. Any ideas? Scott

5 6

[pacman-dev] CVS update of pacman-lib (20 files)
by Dan McGee 08 May '07

08 May '07

Date: Monday, May 7, 2007 @ 23:41:31 Author: dan Path: /home/cvs-pacman/pacman-lib Modified: lib/libalpm/po/de.po (1.19 -> 1.20) lib/libalpm/po/en_GB.po (1.5 -> 1.6) lib/libalpm/po/es.po (1.1 -> 1.2) lib/libalpm/po/fr.po (1.12 -> 1.13) lib/libalpm/po/hu.po (1.12 -> 1.13) lib/libalpm/po/it.po (1.22 -> 1.23) lib/libalpm/po/libalpm.pot (1.10 -> 1.11) lib/libalpm/po/pl_PL.po (1.1 -> 1.2) lib/libalpm/po/pt_BR.po (1.11 -> 1.12) lib/libalpm/po/ru_RU.po (1.3 -> 1.4) src/pacman/po/de.po (1.22 -> 1.23) src/pacman/po/en_GB.po (1.7 -> 1.8) src/pacman/po/es.po (1.1 -> 1.2) src/pacman/po/fr.po (1.16 -> 1.17) src/pacman/po/hu.po (1.17 -> 1.18) src/pacman/po/it.po (1.23 -> 1.24) src/pacman/po/pacman.pot (1.12 -> 1.13) src/pacman/po/pl_PL.po (1.1 -> 1.2) src/pacman/po/pt_BR.po (1.15 -> 1.16) src/pacman/po/ru_RU.po (1.8 -> 1.9) A ton of updates of all of the translation files. Thanks to the authors of those. ----------------------------+ lib/libalpm/po/de.po | 56 ++--- lib/libalpm/po/en_GB.po | 202 ++++++++++--------- lib/libalpm/po/es.po | 395 ++++++++++++++++++-------------------- lib/libalpm/po/fr.po | 6 lib/libalpm/po/hu.po | 202 ++++++++++--------- lib/libalpm/po/it.po | 40 +-- lib/libalpm/po/libalpm.pot | 198 ++++++++++--------- lib/libalpm/po/pl_PL.po | 85 ++++---- lib/libalpm/po/pt_BR.po | 198 ++++++++++--------- lib/libalpm/po/ru_RU.po | 202 ++++++++++--------- src/pacman/po/de.po | 2 src/pacman/po/en_GB.po | 18 - src/pacman/po/es.po | 442 +++++++++++++++++++++++-------------------- src/pacman/po/fr.po | 2 src/pacman/po/hu.po | 18 - src/pacman/po/it.po | 10 src/pacman/po/pacman.pot | 12 - src/pacman/po/pl_PL.po | 210 ++++++++++---------- src/pacman/po/pt_BR.po | 18 - src/pacman/po/ru_RU.po | 18 - 20 files changed, 1211 insertions(+), 1123 deletions(-) The diff is longer than the limit of 39KB.

3 2

[pacman-dev] CVS update of pacman-lib (configure.ac)
by Aaron Griffin 08 May '07

08 May '07

Date: Tuesday, May 8, 2007 @ 04:13:13 Author: aaron Path: /home/cvs-pacman/pacman-lib Modified: configure.ac (1.40 -> 1.41) Version bumped to 3.0.4 --------------+ configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index: pacman-lib/configure.ac diff -u pacman-lib/configure.ac:1.40 pacman-lib/configure.ac:1.41 --- pacman-lib/configure.ac:1.40 Sat Apr 28 04:26:37 2007 +++ pacman-lib/configure.ac Tue May 8 04:13:13 2007 @@ -3,7 +3,7 @@ AC_PREREQ(2.59) dnl Update it right before the release since $pkgver_foo are all _post_ release snapshots -AC_INIT([Pacman package manager], 3.0.3, [pacman-dev(a)archlinux.org] [pacman]) +AC_INIT([Pacman package manager], 3.0.4, [pacman-dev(a)archlinux.org] [pacman]) AC_LANG([C]) AC_CONFIG_HEADERS(config.h) AC_CANONICAL_HOST

1 0

[pacman-dev] CVS update of pacman-lib/lib/libalpm (server.c)
by Aaron Griffin 08 May '07

08 May '07

Date: Tuesday, May 8, 2007 @ 04:11:59 Author: aaron Path: /home/cvs-pacman/pacman-lib/lib/libalpm Modified: server.c (1.28 -> 1.29) minor: Remove trailing slashes from Server urls to prevent double slashes in paths ----------+ server.c | 5 +++++ 1 file changed, 5 insertions(+) Index: pacman-lib/lib/libalpm/server.c diff -u pacman-lib/lib/libalpm/server.c:1.28 pacman-lib/lib/libalpm/server.c:1.29 --- pacman-lib/lib/libalpm/server.c:1.28 Wed Mar 21 17:08:08 2007 +++ pacman-lib/lib/libalpm/server.c Tue May 8 04:11:59 2007 @@ -72,6 +72,10 @@ strcpy(u->pwd, "libalpm@guest"); } + /* remove trailing slashes, just to clean up the rest of the code */ + for(int i = strlen(u->doc) - 1; u->doc[i] == '/'; --i) + u->doc[i] = '\0'; + server->s_url = u; return server; @@ -126,6 +130,7 @@ } snprintf(doc, doclen, "%s/%s", server->s_url->doc, filename); + _alpm_log(PM_LOG_DEBUG, "file path: '%s'", doc); ret = downloadMakeURL(server->s_url->scheme, server->s_url->host, server->s_url->port,

1 0

[pacman-dev] CVS update of pacman-lib/scripts (repo-add)
by Dan McGee 06 May '07

06 May '07

Date: Sunday, May 6, 2007 @ 18:56:08 Author: dan Path: /home/cvs-pacman/pacman-lib/scripts Modified: repo-add (1.9 -> 1.10) repo-add: fix typo, conflicts instead of conflict ----------+ repo-add | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index: pacman-lib/scripts/repo-add diff -u pacman-lib/scripts/repo-add:1.9 pacman-lib/scripts/repo-add:1.10 --- pacman-lib/scripts/repo-add:1.9 Sat Apr 28 04:26:37 2007 +++ pacman-lib/scripts/repo-add Sun May 6 18:56:08 2007 @@ -117,7 +117,7 @@ license=*) _licenses="$_licenses $license" ;; replaces=*) _replaces="$_replaces $replaces" ;; provides=*) _provides="$_provides $provides" ;; - conflicts=*) _conflicts="$_conflicts $conflicts" ;; + conflict=*) _conflicts="$_conflicts $conflicts" ;; esac done

1 0

[pacman-dev] ALPM Questions
by Georg Grabler 04 May '07

04 May '07

Hey guys, I know, none if you is quite happy with the current public interface of ALPM. Anyway, we're on to build up python bindings for this library. We'll be with you when the API of ALPM changes, so i'll watch the lists and cvs carefully. We have a feature plan for the first milestone of the project, but for the sake of task definition i'm missing information (basically documentation, but we all know it always could be better :) .. i hate documenting things too, it's annoying but needed). You have exported quite a lot of data structures. Basically, the first milestone will include a configuration "interface", spoken from the binding, the possibility to add and remove packages (undecided for packagegroups). I've some question regarding alpm features, as well as data structure questions. I'll start with the alpm features. As it seems, alpm currently has no possibility to fetch a list of packages provided by a specified package database. It seems, as if i need to use the pmdb_t structure and manually step trough the pkgcache of it to have a list what the repo provides. Am i right? Or is there any other interface? The data structures: Since adding and removing packages are quite simple tasks (at least from the point of view of someone using the API), by taking a look at the pacman code (3.0.0, don't have the current 3.0.3 here), it seems as i need a type implementation in the binding for the following structures: pmdb_t alpm_list pmgrp_t (if we provide the grouping already in ms1) pmdepmissing_t pmdepend_t (if i want a list what a package depends on anyway, the implementation might be needed for the purpose of building a pkg object containing a set of information). pmconflict_t pmsyncpkg_t There i'm unsure what it is used for, and if i need it at all. I could not find any function which i definitely need to call where this structure is used for. --- Feature related bindings Register / unregister DBs Register / unregister cache directories (handled by the binding, not the client) Add packages (resolving deps, conflichts, handling of ignorepkg, checksums, sha1, architecture handling and adding packages using alpm_trans_addtarget, alpm_prepare and alpm_commit). Removing packages Resolving of all removable dependencies to keep the system "clean". Remove packages including removable dependencies (using alpm_trans_addtarget, alpm_prepare and alpm_commit). QUESTION: how to find out which dependencies of a package are stil in use by other installed packages, and which not? The features of the first test client are still undecided, even though there is no decision if there will be a GUIfied test for the first milestone release. A closer look: https://213.129.245.26/svn/ggtest/docs/milestone_0_1.pdf This document is missing the pmdb_t implementation - was late yesterday in the evening i started the document, and i've still some more tasks (getting the domain right down the same server as the svn is located, providing a task-tracking and bug-tracking for the dev etc or a groupware etc). A basic question is: pyalpm will break within a new version with API changes of alpm. Will it be possible to have two libraries installed? Otherwhise, we would either have to react fast, or keep on track with your development, for being able to release with a new alpm api as well. There we'd definitely need proper information befor it's pushed live. For now, not important, but all this are things somehow turning my brain around. Kind regards, Georg

2 3