- Pacman-dev - lists.archlinux.org

[pacman-dev] Segfault at end of transaction?
by Allan McRae 25 Apr '13

25 Apr '13

I'm guess no-one here has seen this (or why have you not reported it yet!!!), but a couple of people on the Chakra forums are reporting a segfault at the end of the transaction - after releasing the databases. See http://chakra-project.org/bbs/viewtopic.php?id=10224 Waiting for more backtrace information. Allan

4 5

[pacman-dev] [PATCH] Add prepare function to PKGBUILD proto files
by Eric Bélanger 24 Apr '13

24 Apr '13

Signed-off-by: Eric Bélanger <snowmaniscool(a)gmail.com> --- proto/PKGBUILD-split.proto | 7 ++++++- proto/PKGBUILD.proto | 7 ++++++- 2 files changed, 12 insertions(+), 2 deletions(-) diff --git a/proto/PKGBUILD-split.proto b/proto/PKGBUILD-split.proto index 42c469c..f2a2d11 100644 --- a/proto/PKGBUILD-split.proto +++ b/proto/PKGBUILD-split.proto @@ -24,10 +24,15 @@ backup=() options=() install= changelog= -source=($pkgbase-$pkgver.tar.gz) +source=($pkgbase-$pkgver.tar.gz $pkgname-$pkgver.patch) noextract=() md5sums=() #generate with 'makepkg -g' +prepare() { + cd "$srcdir/$pkgname-$pkgver" + patch -p1 -i "$srcdir/$pkgname-$pkgver.patch" +} + build() { cd "$srcdir/$pkgbase-$pkgver" ./configure --prefix=/usr diff --git a/proto/PKGBUILD.proto b/proto/PKGBUILD.proto index 8e9ae04..e78b110 100644 --- a/proto/PKGBUILD.proto +++ b/proto/PKGBUILD.proto @@ -24,10 +24,15 @@ backup=() options=() install= changelog= -source=($pkgname-$pkgver.tar.gz) +source=($pkgname-$pkgver.tar.gz $pkgname-$pkgver.patch) noextract=() md5sums=() #generate with 'makepkg -g' +prepare() { + cd "$srcdir/$pkgname-$pkgver" + patch -p1 -i "$srcdir/$pkgname-$pkgver.patch" +} + build() { cd "$srcdir/$pkgname-$pkgver" ./configure --prefix=/usr -- 1.8.2.1

3 2

[pacman-dev] Mark outdated packages automatically (aka Livecheck)
by Anatol Pomozov 18 Apr '13

18 Apr '13

Hi, I believe in automatization. Any routine work that can be done automatically should be done this way. One such thing that can be improved in Arch project is discovering out-of-date packages. Currently it is done by users who go to https://www.archlinux.org/packages/ find the package and then click "Flag Package Out-of-Date" link. Why to bother users? Why not to let some bot to visit websites and check for new versions? There are examples of package managers that have such functionality - macports http://guide.macports.org/chunked/reference.livecheck.html Their Portfiles can have information about how to find released files (using regexp). Then periodically (e.g. daily) a bot visits webpages, parses html and checks if new files are present. Is it possible to have such functionality in pacman? It would save users time and make package update time lower.

4 8

[pacman-dev] [PATCH v2] Remove ALPM_QUESTION_LOCAL_NEWER
by Connor Behan 18 Apr '13

18 Apr '13

Remove a question that hasn't been used since the 3.0 days. To prevent us from having an ugly enum of questions that is missing a bitmask, this changes the API of the hidden --ask option. Signed-off-by: Connor Behan <connor.behan(a)gmail.com> --- lib/libalpm/alpm.h | 7 +++---- src/pacman/callback.c | 9 --------- test/pacman/tests/ignore005.py | 2 +- test/pacman/tests/sync140.py | 2 +- test/pacman/tests/sync141.py | 2 +- test/pacman/tests/unresolvable001.py | 2 +- test/pacman/tests/upgrade090.py | 2 +- 7 files changed, 8 insertions(+), 18 deletions(-) diff --git a/lib/libalpm/alpm.h b/lib/libalpm/alpm.h index ccbdd1c..2277a69 100644 --- a/lib/libalpm/alpm.h +++ b/lib/libalpm/alpm.h @@ -405,10 +405,9 @@ typedef enum _alpm_question_t { ALPM_QUESTION_REPLACE_PKG = (1 << 1), ALPM_QUESTION_CONFLICT_PKG = (1 << 2), ALPM_QUESTION_CORRUPTED_PKG = (1 << 3), - ALPM_QUESTION_LOCAL_NEWER = (1 << 4), - ALPM_QUESTION_REMOVE_PKGS = (1 << 5), - ALPM_QUESTION_SELECT_PROVIDER = (1 << 6), - ALPM_QUESTION_IMPORT_KEY = (1 << 7) + ALPM_QUESTION_REMOVE_PKGS = (1 << 4), + ALPM_QUESTION_SELECT_PROVIDER = (1 << 5), + ALPM_QUESTION_IMPORT_KEY = (1 << 6) } alpm_question_t; /** Question callback */ diff --git a/src/pacman/callback.c b/src/pacman/callback.c index 71d9d04..01cb2e4 100644 --- a/src/pacman/callback.c +++ b/src/pacman/callback.c @@ -377,15 +377,6 @@ void cb_question(alpm_question_t event, void *data1, void *data2, *response = select_question(count); } break; - case ALPM_QUESTION_LOCAL_NEWER: - if(!config->op_s_downloadonly) { - *response = yesno(_("%s-%s: local version is newer. Upgrade anyway?"), - alpm_pkg_get_name(data1), - alpm_pkg_get_version(data1)); - } else { - *response = 1; - } - break; case ALPM_QUESTION_CORRUPTED_PKG: *response = yesno(_("File %s is corrupted (%s).\n" "Do you want to delete it?"), diff --git a/test/pacman/tests/ignore005.py b/test/pacman/tests/ignore005.py index 274e44c..51bcba3 100644 --- a/test/pacman/tests/ignore005.py +++ b/test/pacman/tests/ignore005.py @@ -36,7 +36,7 @@ self.option["IgnorePkg"] = ["packageA3"] -self.args = "-S packageA1 packageA2 --ask=32" +self.args = "-S packageA1 packageA2 --ask=16" self.addrule("PACMAN_RETCODE=0") self.addrule("PKG_VERSION=packageA1|1.0-1") diff --git a/test/pacman/tests/sync140.py b/test/pacman/tests/sync140.py index ce21cc3..fbe750f 100644 --- a/test/pacman/tests/sync140.py +++ b/test/pacman/tests/sync140.py @@ -18,7 +18,7 @@ for p in sp1, sp2, sp3: self.addpkg2db("sync", p) -self.args = "-Su --ignore %s --ask=32" % sp1.name +self.args = "-Su --ignore %s --ask=16" % sp1.name self.addrule("PACMAN_RETCODE=0") self.addrule("PKG_VERSION=glibc|1.0-1") diff --git a/test/pacman/tests/sync141.py b/test/pacman/tests/sync141.py index f2f0136..02f7be8 100644 --- a/test/pacman/tests/sync141.py +++ b/test/pacman/tests/sync141.py @@ -18,7 +18,7 @@ for p in sp1, sp2, sp3: self.addpkg2db("sync", p) -self.args = "-Su --ignore %s --ask=32" % sp1.name +self.args = "-Su --ignore %s --ask=16" % sp1.name self.addrule("PACMAN_RETCODE=0") self.addrule("PKG_VERSION=c_glibc|1.0-1") diff --git a/test/pacman/tests/unresolvable001.py b/test/pacman/tests/unresolvable001.py index 9d54c3e..4e5da6f 100644 --- a/test/pacman/tests/unresolvable001.py +++ b/test/pacman/tests/unresolvable001.py @@ -11,7 +11,7 @@ packageA2up.depends = ["dep"]; self.addpkg2db("sync", packageA2up) -self.args = "-S package dep --ask=32" +self.args = "-S package dep --ask=16" self.addrule("PACMAN_RETCODE=0") self.addrule("PKG_EXIST=package") diff --git a/test/pacman/tests/upgrade090.py b/test/pacman/tests/upgrade090.py index 26e531c..cdd4cac 100644 --- a/test/pacman/tests/upgrade090.py +++ b/test/pacman/tests/upgrade090.py @@ -16,7 +16,7 @@ sp.files = ["bin/dep"] self.addpkg2db("sync", sp) -self.args = "-U %s --ask=32" % " ".join([p.filename() for p in p1, p2, p3]) +self.args = "-U %s --ask=16" % " ".join([p.filename() for p in p1, p2, p3]) self.addrule("PACMAN_RETCODE=0") for p in p1, p2, sp: -- 1.8.2.1

1 0

[pacman-dev] pacman-4.2 plans?
by Allan McRae 18 Apr '13

18 Apr '13

The 4.2 roadmap is empty! https://wiki.archlinux.org/index.php?title=DeveloperWiki:Pacman_Roadmap I thought it would be good to discuss what people are planning. So far things I know are being or will be worked on: - Remove of support for PKGBUILDs with only a build() function - Removal of directory symlink support Other things that have starts of patchsets available: - Parallel operations (I think I will take this...) - Optdepends handling Things the world would love to see but need substantial planning: - Hooks Any other ideas that people are working on or plan to? Allan

9 20

[pacman-dev] [PATCH] Remove ALPM_QUESTION_LOCAL_NEWER
by Connor Behan 18 Apr '13

18 Apr '13

It seems this question has not been used since the 3.0 days. Signed-off-by: Connor Behan <connor.behan(a)gmail.com> --- lib/libalpm/alpm.h | 7 +++---- src/pacman/callback.c | 9 --------- 2 files changed, 3 insertions(+), 13 deletions(-) diff --git a/lib/libalpm/alpm.h b/lib/libalpm/alpm.h index ccbdd1c..2277a69 100644 --- a/lib/libalpm/alpm.h +++ b/lib/libalpm/alpm.h @@ -405,10 +405,9 @@ typedef enum _alpm_question_t { ALPM_QUESTION_REPLACE_PKG = (1 << 1), ALPM_QUESTION_CONFLICT_PKG = (1 << 2), ALPM_QUESTION_CORRUPTED_PKG = (1 << 3), - ALPM_QUESTION_LOCAL_NEWER = (1 << 4), - ALPM_QUESTION_REMOVE_PKGS = (1 << 5), - ALPM_QUESTION_SELECT_PROVIDER = (1 << 6), - ALPM_QUESTION_IMPORT_KEY = (1 << 7) + ALPM_QUESTION_REMOVE_PKGS = (1 << 4), + ALPM_QUESTION_SELECT_PROVIDER = (1 << 5), + ALPM_QUESTION_IMPORT_KEY = (1 << 6) } alpm_question_t; /** Question callback */ diff --git a/src/pacman/callback.c b/src/pacman/callback.c index 16d66df..a743adc 100644 --- a/src/pacman/callback.c +++ b/src/pacman/callback.c @@ -382,15 +382,6 @@ void cb_question(alpm_question_t event, void *data1, void *data2, *response = select_question(count); } break; - case ALPM_QUESTION_LOCAL_NEWER: - if(!config->op_s_downloadonly) { - *response = yesno(_("%s-%s: local version is newer. Upgrade anyway?"), - alpm_pkg_get_name(data1), - alpm_pkg_get_version(data1)); - } else { - *response = 1; - } - break; case ALPM_QUESTION_CORRUPTED_PKG: *response = yesno(_("File %s is corrupted (%s).\n" "Do you want to delete it?"), -- 1.8.2.1

2 1

[pacman-dev] [PATCH] Give the frontend control over responses for print
by Connor Behan 17 Apr '13

17 Apr '13

There are currently 8 questions that libalpm may ask the user. Each of them has a "pacman default" and a "libalpm default". The pacman default is the response that gets used if the user presses enter without typing anything. Equivalently it is the response when --noconfirm is passed. The libalpm default is what happens when --print is passed and the question callback never even executes. This commit forces pacman to specify responses for --print and therefore never rely on the libalpm default. The following states how each question is handled: ALPM_QUESTION_INSTALL_IGNOREPKG: The pacman default is 1 and the libalpm default is 0. The latter was agreed to be a bug so we return 1 on print. ALPM_QUESTION_REPLACE_PKG: The pacman default is 1 and the libalpm default is 0. We return 0 on print. ALPM_QUESTION_CONFLICT_PKG: The pacman default is 0 and the libalpm default is 0. We return 0 on print even though print should not encounter this. ALPM_QUESTION_REMOVE_PKGS: The pacman default is 0 and the libalpm default is 0. We return 0 on print. ALPM_QUESTION_SELECT_PROVIDER: The pacman default is 0 and the libalpm default is 0. We return 0 on print. ALPM_QUESTION_LOCAL_NEWER: The pacman default is 1 and this is dead code so there is no libalpm default. We return 1 on print. ALPM_QUESTION_CORRUPTED_PKG: The pacman default is 1 and the libalpm default is 0. We return 0 on print even though print should not encounter this. ALPM_QUESTION_IMPORT_KEY: The pacman default is 1 and the libalpm default is 0. We return 0 on print even though print should not encounter this. Signed-off-by: Connor Behan <connor.behan(a)gmail.com> --- src/pacman/callback.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/pacman/callback.c b/src/pacman/callback.c index 71d9d04..711d116 100644 --- a/src/pacman/callback.c +++ b/src/pacman/callback.c @@ -309,6 +309,14 @@ void cb_question(alpm_question_t event, void *data1, void *data2, void *data3, int *response) { if(config->print) { + switch(event) { + case ALPM_QUESTION_INSTALL_IGNOREPKG: + case ALPM_QUESTION_LOCAL_NEWER: + *response = 1; + break; + default: + *response = 0; + } return; } switch(event) { -- 1.8.1.5

2 3

[pacman-dev] [PATCH] Unify front and backend responses for --print
by Connor Behan 17 Apr '13

17 Apr '13

When libalpm asks the user a question, there are two possible defaults. One default for pacman (used when the user presses enter without typing and for --noconfirm) and the libalpm default. Currently the libalpm default gets used for the pacman "--print" option. This affects the printing of ignored packages since the defaults differ for "ALPM_QUESTION_INSTALL_IGNOREPKG". Adjust the response of this case when using --print so pacman acts consistently. Signed-off-by: Connor Behan <connor.behan(a)gmail.com> --- src/pacman/callback.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/pacman/callback.c b/src/pacman/callback.c index 71d9d04..16d66df 100644 --- a/src/pacman/callback.c +++ b/src/pacman/callback.c @@ -309,6 +309,11 @@ void cb_question(alpm_question_t event, void *data1, void *data2, void *data3, int *response) { if(config->print) { + if(event == ALPM_QUESTION_INSTALL_IGNOREPKG) { + *response = 1; + } else { + *response = 0; + } return; } switch(event) { -- 1.8.2.1

1 0

[pacman-dev] 回复: [PATCH] Give the frontend control over responses for print
by Ssfdust 16 Apr '13

16 Apr '13

已从三星手机发送 -------- 原始消息 -------- 主题：[pacman-dev] [PATCH] Give the frontend control over responses for print 发件人：Connor Behan <connor.behan(a)gmail.com> 收件人：pacman-dev(a)archlinux.org 抄送： null

1 0

[pacman-dev] 回复: [PATCH] Give the frontend control over responses for print
by Ssfdust 16 Apr '13

16 Apr '13

已从三星手机发送 -------- 原始消息 -------- 主题：[pacman-dev] [PATCH] Give the frontend control over responses for print 发件人：Connor Behan <connor.behan(a)gmail.com> 收件人：pacman-dev(a)archlinux.org 抄送： There are currently 8 questions that libalpm may ask the user. Each of them has a "pacman default" and a "libalpm default". The pacman default is the response that gets used if the user presses enter without typing anything. Equivalently it is the response when --noconfirm is passed. The libalpm default is what happens when --print is passed and the question callback never even executes. This commit forces pacman to specify responses for --print and therefore never rely on the libalpm default. The following states how each question is handled: ALPM_QUESTION_INSTALL_IGNOREPKG: The pacman default is 1 and the libalpm default is 0. The latter was agreed to be a bug so we return 1 on print. ALPM_QUESTION_REPLACE_PKG: The pacman default is 1 and the libalpm default is 0. We return 0 on print. ALPM_QUESTION_CONFLICT_PKG: The pacman default is 0 and the libalpm default is 0. We return 0 on print even though print should not encounter this. ALPM_QUESTION_REMOVE_PKGS: The pacman default is 0 and the libalpm default is 0. We return 0 on print. ALPM_QUESTION_SELECT_PROVIDER: The pacman default is 0 and the libalpm default is 0. We return 0 on print. ALPM_QUESTION_LOCAL_NEWER: The pacman default is 1 and this is dead code so there is no libalpm default. We return 1 on print. ALPM_QUESTION_CORRUPTED_PKG: The pacman default is 1 and the libalpm default is 0. We return 0 on print even though print should not encounter this. ALPM_QUESTION_IMPORT_KEY: The pacman default is 1 and the libalpm default is 0. We return 0 on print even though print should not encounter this. Signed-off-by: Connor Behan <connor.behan(a)gmail.com> --- src/pacman/callback.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/pacman/callback.c b/src/pacman/callback.c index 71d9d04..711d116 100644 --- a/src/pacman/callback.c +++ b/src/pacman/callback.c @@ -309,6 +309,14 @@ void cb_question(alpm_question_t event, void *data1, void *data2, void *data3, int *response) { if(config->print) { + switch(event) { + case ALPM_QUESTION_INSTALL_IGNOREPKG: + case ALPM_QUESTION_LOCAL_NEWER: + *response = 1; + break; + default: + *response = 0; + } return; } switch(event) { -- 1.8.1.5

1 0