- Pacman-dev - lists.archlinux.org

[pacman-dev] [PATCH] makepkg: always update symlinks to compressed man pages
by Allan McRae 05 Mar '10

05 Mar '10

When a man page has both symbolic and hard links, any symlink pointing to other than the alphabetically first hardlink was not "compressed" and left dangling towards the uncompressed man page. Fixes FS#18569. Signed-off-by: Allan McRae <allan(a)archlinux.org> --- scripts/makepkg.sh.in | 23 ++++++++++++----------- 1 files changed, 12 insertions(+), 11 deletions(-) diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index 3d987ac..f8072f9 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -836,17 +836,18 @@ tidy_install() { local manpage ext file link hardlinks hl find ${MAN_DIRS[@]} -type f 2>/dev/null | while read manpage ; do - # check file still exists (potentially compressed with hard link) - if [[ -f ${manpage} ]]; then - ext="${manpage##*.}" - file="${manpage##*/}" - if [[ $ext != gz && $ext != bz2 ]]; then - # update symlinks to this manpage - find ${MAN_DIRS[@]} -lname "$file" 2>/dev/null | - while read link ; do - rm -f "$link" - ln -sf "${file}.gz" "${link}.gz" - done + ext="${manpage##*.}" + file="${manpage##*/}" + if [[ $ext != gz && $ext != bz2 ]]; then + # update symlinks to this manpage + find ${MAN_DIRS[@]} -lname "$file" 2>/dev/null | + while read link ; do + rm -f "$link" + ln -sf "${file}.gz" "${link}.gz" + done + + # check file still exists (potentially already compressed due to hardlink) + if [[ -f ${manpage} ]]; then # find hard links and remove them # the '|| true' part keeps the script from bailing if find returned an # error, such as when one of the man directories doesn't exist -- 1.7.0.1

1 1

Re: [pacman-dev] [arch-general] [arch-dev-public] Versioned dependency fun...
by Dan McGee 03 Mar '10

03 Mar '10

On Tue, Mar 2, 2010 at 4:40 PM, Xavier Chantry <chantry.xavier(a)gmail.com> wrote: > On Tue, Mar 2, 2010 at 7:32 PM, Pierre Schmitz <pierre(a)archlinux.de> wrote: >> Am Dienstag, 2. März 2010 14:06:57 schrieb Dan McGee: >>> > and here we have another reason to punish anybody using versioned >>> > dependencies. ;-) (of course upstream needs to be hit, too) >>> >>> Blaming this on versioned deps is punishing the messenger; this >>> package wouldn't upgrade without a force option either because the >>> same version comparison is used everywhere... >> >> You did notice the smiley? I know this wasn't fair in this case and not too >> serious. But anyway, I would prefer add the force flag and add the (stupid) >> upstream version instead of making your own up. >> > > The force flag is a big ugly crap. > I find sanitizing upstream version to be much.. saner. > Or figure out a way to have both a sane version for pacman and the > insane upstream version. I was actually thinking about this again and thinking epoch might not be a bad idea- I don't know if I had any legit objection to it before but I can't think of one anymore. If someone is interested in implementing, I'd be for it. -Dan

4 3

[pacman-dev] [GIT] The official pacman repository branch, master, updated. v3.3.3-125-g1a00ee5
by dan＠archlinux.org 01 Mar '10

01 Mar '10

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 1a00ee5c276785aef70225c2cc951dbb15888ea5 (commit) via d85421ec62cdcd0b4b1f162b9908dc3eb0b704b4 (commit) via afb61bb22a9478ec076f77ff0e102e81763191e7 (commit) via 27bc2f7eb81566370f9f19f89eb95c6e6c9ec49a (commit) from 0eadc992400aaad58da5866d23caee01a22e1341 (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 1a00ee5c276785aef70225c2cc951dbb15888ea5 Author: Cedric Staniewski <cedric(a)gmx.ca> Date: Thu Feb 25 23:23:06 2010 +0100 bash_completion: remove absolute utility paths again The location of the used utilities may and does differ between various distributions and therefore absolute paths do not work well. Since the main purpose of its introduction was to avoid side-effects caused by aliases, it is sufficient to disable possible aliases temporarily by preceding the commands with a backslash. Signed-off-by: Cedric Staniewski <cedric(a)gmx.ca> Signed-off-by: Dan McGee <dan(a)archlinux.org> commit d85421ec62cdcd0b4b1f162b9908dc3eb0b704b4 Author: Pierre Schmitz <pierre(a)archlinux.de> Date: Thu Feb 18 05:18:10 2010 +0100 contrib/*_completion: match *.pkg.tar.* Signed-off-by: Pierre Schmitz <pierre(a)archlinux.de> Signed-off-by: Dan McGee <dan(a)archlinux.org> commit afb61bb22a9478ec076f77ff0e102e81763191e7 Author: Allan McRae <allan(a)archlinux.org> Date: Thu Dec 24 08:09:38 2009 +1000 Do not print installed size when only downloading When using --downloadonly the "Total Installed Size" message is not needed and perhaps misleading. Signed-off-by: Allan McRae <allan(a)archlinux.org> Signed-off-by: Dan McGee <dan(a)archlinux.org> commit 27bc2f7eb81566370f9f19f89eb95c6e6c9ec49a Author: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Date: Tue Jan 19 21:35:13 2010 +0100 Print "there is nothing to do" with NOOP transactions The "local database is up to date" message has been replaced with "there is nothing to do" message. This used with "empty" -S, -R, -U operations too. (Examples: pacman -S ignored_pkg, pacman -Ru needed_pkg.) See FS#17859. Signed-off-by: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> Signed-off-by: Dan McGee <dan(a)archlinux.org> ----------------------------------------------------------------------- Summary of changes: contrib/bash_completion | 32 ++++++++++++++++---------------- contrib/zsh_completion | 8 ++++---- src/pacman/remove.c | 1 + src/pacman/sync.c | 2 +- src/pacman/upgrade.c | 1 + src/pacman/util.c | 4 +++- 6 files changed, 26 insertions(+), 22 deletions(-) hooks/post-receive -- The official pacman repository

1 0

[pacman-dev] [PATCH] contrib/*_completion: match *.pkg.tar.*
by Pierre Schmitz 01 Mar '10

01 Mar '10

Signed-off-by: Pierre Schmitz <pierre(a)archlinux.de> --- contrib/bash_completion | 4 ++-- contrib/zsh_completion | 8 ++++---- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/contrib/bash_completion b/contrib/bash_completion index 62e5bc9..a231eb6 100644 --- a/contrib/bash_completion +++ b/contrib/bash_completion @@ -321,7 +321,7 @@ _pacman () case "${op}" in U) COMPREPLY=( $( compgen -d -- "$cur" ) \ - $( compgen -f -X '!*.pkg.tar.gz' -- "$cur" ) ) + $( compgen -f -X '!*.pkg.tar.*' -- "$cur" ) ) return 0 ;; h|V) @@ -336,7 +336,7 @@ _pacman () $( compgen -f -- "$cur" ) ) elif _instring $mod p; then COMPREPLY=( $( compgen -d -- "$cur" ) \ - $( compgen -f -X '!*.pkg.tar.gz' -- "$cur" ) ) + $( compgen -f -X '!*.pkg.tar.*' -- "$cur" ) ) elif _instring $mod u; then COMPREPLY='' return 0 diff --git a/contrib/zsh_completion b/contrib/zsh_completion index 2f43d9b..01b3c44 100644 --- a/contrib/zsh_completion +++ b/contrib/zsh_completion @@ -32,7 +32,7 @@ _pacman_opts_common=( _pacman_opts_pkgfile=( '-d[Skip dependency checks]' '-f[Overwrite conflicting files]' - '*:package file:_files -g "*.pkg.tar.gz(.)"' + '*:package file:_files -g "*.pkg.tar.*(.)"' ) # options for passing to _arguments: subactions for --query command @@ -120,7 +120,7 @@ _pacman_action_query() { _arguments -s : \ "$_pacman_opts_common[@]" \ "$_pacman_opts_query_modifiers[@]" \ - '*:package file:_files -g "*.pkg.tar.gz"' + '*:package file:_files -g "*.pkg.tar.*"' ;; query_group) _arguments -s : \ @@ -295,11 +295,11 @@ _pacman() { "$_pacman_opts_query_modifiers[@]" \ '*:package file:_files' ;; - -Q*p*) # file *.pkg.tar.gz + -Q*p*) # file *.pkg.tar.* _arguments -s : \ "$_pacman_opts_common[@]" \ "$_pacman_opts_query_modifiers[@]" \ - '*:package file:_files -g "*.pkg.tar.gz"' + '*:package file:_files -g "*.pkg.tar.*"' ;; -Q*) _pacman_action_query ;; -R*) _pacman_action_remove ;; -- 1.7.0 -- Pierre Schmitz, https://users.archlinux.de/~pierre

2 1

[pacman-dev] -Qi output corrupted when using screen
by Roman Kyrylych 28 Feb '10

28 Feb '10

Hi! It has been a looong time since I last posted here (or even read the list), so please forgive me if this is a known issue. I have a VPS on Linode and they have a tool called LISH which is a minimal environment that is accessible via logging in via ssh on the _host_. There is a screen session that shows the output from /dev/hvc0 (which is hardware tty in Xen), so you can access your system even if you locked yourself from accessing it via ssh. When doing pacman -Qi in that screen session I get corrupted output like this: <some text from the top of the host's tty buffer goes here first> Feb 2010 12:14:18 AM UTC Install Date : Sun 14 Feb 2010 02:21:13 PM UTC Install Reason : Explicitly installed Install Script : Yes Description : Utility programs used for creating patch files This happens only when doing -Qi. Any ideas about this? And if it's a known issue - how to fix it? -- Roman Kyrylych (Роман Кирилич)

6 16

[pacman-dev] [PATCH] bash_completion: remove absolute utility paths again
by Cedric Staniewski 26 Feb '10

26 Feb '10

The location of the used utilities may and does differ between various distributions and therefore absolute paths do not work well. Since the main purpose of its introduction was to avoid side-effects caused by aliases, it is sufficient to disable possible aliases temporarily by preceding the commands with a backslash. Signed-off-by: Cedric Staniewski <cedric(a)gmx.ca> --- contrib/bash_completion | 28 ++++++++++++++-------------- 1 files changed, 14 insertions(+), 14 deletions(-) diff --git a/contrib/bash_completion b/contrib/bash_completion index 62e5bc9..40ef8c0 100644 --- a/contrib/bash_completion +++ b/contrib/bash_completion @@ -14,7 +14,7 @@ rem_selected () # (Adapted from bash_completion by Ian Macdonald <ian(a)caliban.org>) # This removes any options from the list of completions that have # already been specified on the command line. - COMPREPLY=($(/bin/echo "${COMP_WORDS[@]}" | \ + COMPREPLY=($(\echo "${COMP_WORDS[@]}" | \ (while read -d ' ' i; do [ "${i}" == "" ] && continue # flatten array with spaces on either side, @@ -24,20 +24,20 @@ rem_selected () # remove word from list of completions COMPREPLY=(${COMPREPLY/ ${i%% *} / }) done - /bin/echo ${COMPREPLY[@]}))) + \echo ${COMPREPLY[@]}))) return 0 } _available_repos () { - COMPREPLY=( $( compgen -W "$(/bin/grep '\[' /etc/pacman.conf | /bin/grep -v -e 'options' -e '^#' | tr -d '[]' )" -- $cur ) ) + COMPREPLY=( $( compgen -W "$(\grep '\[' /etc/pacman.conf | \grep -v -e 'options' -e '^#' | \tr -d '[]' )" -- $cur ) ) } _installed_pkgs () { local installed_pkgs - installed_pkgs=$( /bin/ls /var/lib/pacman/local/ ) - COMPREPLY=( $( compgen -W "$( for i in $installed_pkgs; do /bin/echo ${i%-*-*}; done )" -- $cur ) ) + installed_pkgs=$( \ls /var/lib/pacman/local/ ) + COMPREPLY=( $( compgen -W "$( for i in $installed_pkgs; do \echo ${i%-*-*}; done )" -- $cur ) ) } _available_pkgs () @@ -47,16 +47,16 @@ _available_pkgs () # This little change-up removes the find *and* only uses enabled repos local available_pkgs local enabled_repos - enabled_repos=$( /bin/grep '\[' /etc/pacman.conf | /bin/grep -v -e 'options' -e '^#' | tr -d '[]' ) - available_pkgs=$( for r in $enabled_repos; do /bin/echo /var/lib/pacman/sync/$r/*; done ) + enabled_repos=$( \grep '\[' /etc/pacman.conf | \grep -v -e 'options' -e '^#' | \tr -d '[]' ) + available_pkgs=$( for r in $enabled_repos; do \echo /var/lib/pacman/sync/$r/*; done ) COMPREPLY=( $( compgen -W "$( for i in $available_pkgs; do j=${i##*/}; echo ${j%-*-*}; done )" -- $cur ) ) } _installed_groups () { local installed_groups - installed_groups=$( /bin/find /var/lib/pacman/local -name desc -exec /bin/sed -ne '/%GROUPS%/,/^$/{//d; p}' {} \; | /bin/sort -u ) - COMPREPLY=( $( compgen -W "$( for i in $installed_groups; do /bin/echo ${i%-*-*}; done )" -- $cur ) ) + installed_groups=$( \find /var/lib/pacman/local -name desc -exec \sed -ne '/%GROUPS%/,/^$/{//d; p}' {} \; | \sort -u ) + COMPREPLY=( $( compgen -W "$( for i in $installed_groups; do \echo ${i%-*-*}; done )" -- $cur ) ) } _available_groups () @@ -66,9 +66,9 @@ _available_groups () # This little change-up removes the find *and* only uses enabled repos local available_groups local enabled_repos - enabled_repos=$( /bin/grep '\[' /etc/pacman.conf | /bin/grep -v -e 'options' -e '^#' | tr -d '[]' ) - available_groups=$( for r in $enabled_repos; do /bin/sed '/%GROUPS%/,/^$/{//d; p}' /var/lib/pacman/sync/$r/*/desc | /bin/sort -u; done ) - COMPREPLY=( $( compgen -W "$( for i in $available_groups; do /bin/echo ${i%-*-*}; done )" -- $cur ) ) + enabled_repos=$( \grep '\[' /etc/pacman.conf | \grep -v -e 'options' -e '^#' | tr -d '[]' ) + available_groups=$( for r in $enabled_repos; do \sed '/%GROUPS%/,/^$/{//d; p}' /var/lib/pacman/sync/$r/*/desc | \sort -u; done ) + COMPREPLY=( $( compgen -W "$( for i in $available_groups; do \echo ${i%-*-*}; done )" -- $cur ) ) } ## makepkg completion @@ -126,7 +126,7 @@ _instring () str="${1}" shift 1 for c in "${@}"; do - if [ $(/bin/expr index "${str}" "${c}") -gt 0 ]; then + if [ $(\expr index "${str}" "${c}") -gt 0 ]; then return 0 fi done @@ -193,7 +193,7 @@ _pacman () esac arglen=$(( ${#toparse}-1 )) - for c in $(/bin/seq 0 "${arglen}"); do + for c in $(\seq 0 "${arglen}"); do arg=${toparse:$c:1} [ "${arg}" != "-" ] && mod="${mod}${arg}" done -- 1.7.0

9 13

[pacman-dev] Bash completion
by Cedric Staniewski 25 Feb '10

25 Feb '10

Hi, I just replaced my bash completion file with the git version and noticed it tries to execute /bin/seq and fails because seq is located at /usr/bin/seq. Since I could not find anything in coreutils' changelog file I guess the path was wrong right from the start and should be corrected. The other thing I wonder about (still the same commit[1]) is why the (slower) external echo command is preferred to bash's internal implementation. Thanks, Cedric [1] http://projects.archlinux.org/pacman.git/commit/?id=8b3f5f0ce6dca98ca14cc48…

4 4

[pacman-dev] [PATCH] makepkg: update required programs
by Allan McRae 25 Feb '10

25 Feb '10

Remove getopt, add xz. Signed-off-by: Allan McRae <allan(a)archlinux.org> --- scripts/makepkg.sh.in | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index 5120feb..3d987ac 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -28,7 +28,7 @@ # makepkg uses quite a few external programs during its execution. You # need to have at least the following installed for makepkg to function: # bsdtar (libarchive), bzip2, coreutils, fakeroot, find (findutils), -# getopt (util-linux), gettext, grep, gzip, openssl, sed, tput (ncurses) +# gettext, grep, gzip, openssl, sed, tput (ncurses), xz # gettext initialization export TEXTDOMAIN='pacman' -- 1.7.0

1 0

[pacman-dev] bug: pacman giving up too fast downloading
by Paul Dufresne 17 Feb '10

17 Feb '10

Well, I have lots of errors while downloading packages with pacman, and almost never while downloading files from Shiretoko Firefox. I have tried many mirrors, that's the same for each. Oh... I use a 56k modem (Intel 536EP Data Fax modem). But even while downloading in Firefox, it sometimes give me the feeling it has stopped downloading for about 40 secs... while pacman seems to give up after about 20 secs. I did not tried yet to download with wget or curl (does pacman use one of them?). Is there a constant I could change in the code, and rebuild it?... I did not download the code of pacman yet.

7 8

[pacman-dev] [PATCH] don't use old packages to satisfy dependencies
by Henning Garus 12 Feb '10

12 Feb '10

Don't use packages which are updated during the current transaction as dependency providers, when computing needed dependencies in resolvedeps. This could lead to new dependencies not being pulled in, in situations like: foo-1 provides bar baz depends on bar foo-2 does not provide bar anymore baz still depends on bar bar is not pulled in because foo-1 is used to satisfy the dependency Signed-off-by: Henning Garus <henning.garus(a)gmail.com> --- This should fix the "phonon bug". I am not entirely happy with this, because I more or less copy the local db (once more) on every call to resolvedeps. Alternatively one could create a joined list from remove and trans->add and give it to checkdeps as remove parameter. This would do what we want (exclude packages which will be upgraded from the list used to compute already satisfied dependencies in checkdeps), but it feels wrong. lib/libalpm/deps.c | 12 +++++++++++- 1 files changed, 11 insertions(+), 1 deletions(-) diff --git a/lib/libalpm/deps.c b/lib/libalpm/deps.c index 46699ac..85d7e24 100644 --- a/lib/libalpm/deps.c +++ b/lib/libalpm/deps.c @@ -600,6 +600,7 @@ int _alpm_resolvedeps(pmdb_t *local, alpm_list_t *dbs_sync, pmpkg_t *pkg, { alpm_list_t *i, *j; alpm_list_t *targ; + alpm_list_t *untouched = NULL; alpm_list_t *deps = NULL; alpm_list_t *packages_copy; @@ -620,11 +621,19 @@ int _alpm_resolvedeps(pmdb_t *local, alpm_list_t *dbs_sync, pmpkg_t *pkg, on that list */ *packages = alpm_list_add(*packages, pkg); + /* Create a list of local packages which can be used to satisfy deps. + * Don't use packages which are updated in the current transaction */ + for(i = _alpm_db_get_pkgcache(local); i; i = i->next) { + if(!alpm_list_find(handle->trans->add, i->data, _alpm_pkg_cmp)) { + untouched = alpm_list_add(untouched, i->data); + } + } + _alpm_log(PM_LOG_DEBUG, "started resolving dependencies\n"); for(i = alpm_list_last(*packages); i; i = i->next) { pmpkg_t *tpkg = i->data; targ = alpm_list_add(NULL, tpkg); - deps = alpm_checkdeps(_alpm_db_get_pkgcache(local), 0, remove, targ); + deps = alpm_checkdeps(untouched, 0, remove, targ); alpm_list_free(targ); for(j = deps; j; j = j->next) { pmdepmissing_t *miss = j->data; @@ -666,6 +675,7 @@ int _alpm_resolvedeps(pmdb_t *local, alpm_list_t *dbs_sync, pmpkg_t *pkg, alpm_list_free_inner(deps, (alpm_list_fn_free)_alpm_depmiss_free); alpm_list_free(deps); } + alpm_list_free(untouched); alpm_list_free(packages_copy); _alpm_log(PM_LOG_DEBUG, "finished resolving dependencies\n"); return(0); -- 1.6.6.1

2 1

Re: [pacman-dev] [arch-general] Error message on mkinitcpio
by Xavier Chantry 12 Feb '10

12 Feb '10

On Thu, Feb 11, 2010 at 10:27 PM, Dan McGee <dpmcgee(a)gmail.com> wrote: > > I think we may have this fixed in pacman-git, but Nagy or Xavier would > know for sure... > That documentation from man PKGBUILD still applies, I don't think we ever considered it as a bug/problem : replaces (array) An array of packages that this package should replace, and can be used to handle renamed/combined packages. For example, if the j2re package is renamed to jre, this directive allows future upgrades to continue as expected even though the package has moved. Sysupgrade is currently the only pacman operation that utilizes this field, a normal sync will not use its value. But now I am wondering if replaces could imply conflicts/provides. Implicit fields means less control and power to the user/packager though.

2 1

Re: [pacman-dev] [arch-dev-public] Warning 2/2: removing kde-unstable; KDE 4.4 in testing
by Xavier Chantry 10 Feb '10

10 Feb '10

On Mon, Feb 1, 2010 at 1:04 PM, Pierre Schmitz <pierre(a)archlinux.de> wrote: > Hi DEVs and TUs, > > I am about to move the first wave of KDE 4.4 RC3 packages into testing. These > will be x86_64 at first; i686 packages might follow later this evening. There > won't be any l10n packages. (they are not needed for testing and rebuild and > we'll save disk space and bandwidth this way) > > The same Information about kde-unstable now apply to testing: > http://wiki.archlinux.org/index.php/DeveloperWiki:KDE#Users Note that the kde- > unstable repository will be removed soon. > > If you update you have to use the following commands as pacman is not able to > resolve the dependencies otherwise: > > % pacman -Sy --asdeps qt > % pacman -Su > Please report this kind of issues to pacman-dev ML or pacman bugtracker in the future :) This limitation was actually not even known to us (at least Nagy and I), and it doesn't seem that we have a pactest for it. This issue might be fixable (at least that specific case), and it might be a pactest that we want to add to the testsuite, to avoid future regressions.

4 6

Re: [pacman-dev] [arch-general] A suggestion for the devs regarding rebuilds
by Xavier Chantry 08 Feb '10

08 Feb '10

On Mon, Jan 11, 2010 at 12:53 AM, Aaron Griffin <aaronmgriffin(a)gmail.com> wrote: > On Sun, Jan 10, 2010 at 12:08 PM, Jeff Horelick <jdhore1(a)gmail.com> wrote: >> Hey all, >> >> I have a suggestion to possibly make rebuilds a bit less painful (or >> non-existant). I think this is a good idea because it seems like right now, >> even before there was a new rebuild (ffmpeg/x264) in testing, there's >> already another on the horizon (linjpeg/libpng, and it's a big one) and when >> this isn't the case, there's usually a rebuild, when it leaves testing, >> another rebuild comes in within days and so on. >> >> My suggestion would be to do what Debian does and when there's a library >> release with a new soname, bump the old package and "rename" it (or for new >> packages just do it from the start) and make the package name include the >> soname version (like libjpeg7, libpng12, libtorrent-rasterbar4 and so on) >> and when the soname is bumped upstream, just make libjpeg8 or libpng13 or >> libtorrent-rasterbar5. This does clutter the repos a bit, but it pretty much >> negates the need for rebuilds since (i believe) when the new GNOME for >> example is released, it'll automagically build against libjpeg8 and libpng13 >> instead of the old ones and eventually, almost no packages will be using the >> old ones. Once the package list for a large rebuild like the libpng/libjpeg >> one is down to 3 or 4 items after like 3 months, you can probably rebuild >> them and pull libjpeg7/libpng12 from the repos. > > This is one of the single biggest things I hate about apt based > distros. The libfoo2/libfoo3/libfoo4 cruft. It's needless. > > This doesn't do anything with regards to helping the devs do rebuilds, > because packages still need to be rebuilt. It just allows us to take > our time - something you DON'T want if you're expecting packages to be > up to date. > With every big rebuilds we get new breakage stories. It seems like it's the norm nowadays rather than the exception. I am wondering if it's really only the users that are to blame.. or if Arch is also to blame. Or if Arch was supposed to be an elitist distribution and is victim of its success. More importantly, I am wondering if the sodepends/soprovides proposal would not actually be a more complex solution than the libfoo2/libfoo3/libfoo4 way.

2 1

[pacman-dev] [PATCH] makepkg: only strip files that are writable
by Allan McRae 03 Feb '10

03 Feb '10

Signed-off-by: Allan McRae <allan(a)archlinux.org> --- scripts/makepkg.sh.in | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index 5120feb..0ca5e36 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -869,7 +869,7 @@ tidy_install() { if [[ $(check_option strip) = y && -n ${STRIP_DIRS[*]} ]]; then msg2 "$(gettext "Stripping unneeded symbols from binaries and libraries...")" local binary - find ${STRIP_DIRS[@]} -type f 2>/dev/null | while read binary ; do + find ${STRIP_DIRS[@]} -type f -writable 2>/dev/null | while read binary ; do case "$(file -biz "$binary")" in *compressed-encoding*) # Skip compressed binaries ;; -- 1.6.6.1

4 6

[pacman-dev] [PATCH] makepkg: Add documentation for the new SRCPKGDEST variable
by Nezmer 22 Jan '10

22 Jan '10

Add SRCPKGDEST documentation to the makepkg.conf man page Signed-off-by: Nezmer <git(a)nezmer.info> --- doc/makepkg.conf.5.txt | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/doc/makepkg.conf.5.txt b/doc/makepkg.conf.5.txt index 704dccc..d8ee86b 100644 --- a/doc/makepkg.conf.5.txt +++ b/doc/makepkg.conf.5.txt @@ -171,6 +171,11 @@ Options in the current directory. Many people like to keep all source files in a central location for easy cleanup, so this path can be set here. +**SRCPKGDEST=**"/path/to/folder":: + If this value is not set, source package files will be stored in + PKGDEST. Many people like to keep all source package files in + a central location for easy cleanup, so this path can be set here. + **PACKAGER=**"John Doe <john(a)example.com>":: This value is used when querying a package to see who was the builder. It is recommended you change this to your name and email address. -- 1.6.6

4 3

[pacman-dev] Matching split packages to PKGBUILDs
by Xyne 21 Jan '10

21 Jan '10

I was under the impression that the naming convention for split packages was $pkgbase-$pkgname. I've used this scheme in bauerbill to determine the corresponding PKGBUILD of split packages in $repo.abs.tar.gz. This works for all packages in the kernel26 PKGBUILD, for example, but someone has discovered that this does not work with dhclient. Is there simply no official rule for this or should dhclient actually be names "dhcp-client"? I'm hoping for that latter with the expectation that the name was not changed because the package was named "dhclient" before the advent of split packages. Should I file a bug report and request that the package be renamed "dhcp-client" and provide "dhclient"? If not, how can I sanely determine the corresponding PKGBUILD for packages such as dhclient which do not follow any naming convention that would identify the matching PKGBUILD? Would it be possible to include symlinks or duplicate PKGBUILDs in $repo.abs.tar.gz to enable applications to determine this? I know that some of you feel that the sole purpose of makepkg is to build packages and consequently have no regard for anything else one might want to do with PKGBUILDs, but this is very unfortunate as it severely limits the development of complementary tools. While I see the superficial simplicity of using bash for PKGBUILDs and the convenience of split PKGBUILDs, I really think this is going in the wrong direction. There is a difference between simplicity and laziness, and the trade-off of versatility and elegance is a considerable disadvantage of this direction, as previous discussions here have shown. Regards, Your friendly yet frustrated contributor.

4 6

[pacman-dev] BUG and PATCH: 'handle' not null after alpm_release()
by Markus Meissner 21 Jan '10

21 Jan '10

Hi pacman dev list, I am the guy behind pyalpmm and I found a not so small bug in libalpm. As I wrote some unit-tests for pyalpmm I needed to open and close a libalpm-"session" multiple times without restarting the calling application. Something like that: 1. alpm_initialize(); 2. /** do some operation here **/ 3. alpm_release(); 4. alpm_initialize(); 5. alpm_release(); But I couldn't do this, because the alpm_initialize() call in line 4 always threw an error (errno: PM_ERR_HANDLE_NOT_NULL), which translates to: "library already initialized". This is obviously not true, because the alpm_release() function was successfully called. I checked the code and found out that this line threw the error: ASSERT(handle != NULL, RET_ERR(PM_ERR_HANDLE_NULL, -1)); What means that the handle is not correctly reseted to NULL, but the _alpm_free_handle() function, which is called by alpm_release() has a FREE(handle) inside. So here is my explanation why this happens: The handle pointer is passed to _alpm_free_handle() as a value, so the pointer value itself is copied. This works perfect for freeing the contents of the handle struct, BUT setting this handle pointer to NULL just sets the locally copied pointer to NULL, what means the original handle variable remains un-touched. So every alpm_initialize() call after the first one will throw this error, no matter if you called alpm_release() or not. So to get finally end, I fixed it and the patch is (against latest git) attached to this email. Hopefully my explanation is enough to sketch the problem. Solving it, is really easy, just change the _alpm_free_handle() function to take a pointer of a pointer of pmhandle_t as an argument, change the references to handle inside the function and slightly change the _alpm_free_handle() call in alpm_release(). That's how it is done with the attached patch... Finally I also have a question: I saw many changes in the recent git compared to the latest release. Is there an estimated release date? Thanks and Greets Markus

4 6

[pacman-dev] outdated web stuff
by Jeff 21 Jan '10

21 Jan '10

Just a heads up: ftp://ftp.archlinux.org/other/pacman/md5sums doesn't include 3.3.3. http://www.archlinux.org/pacman/ shows 3.3.0 as the latest version HTH! -- Jeff My other computer is an abacus.

2 2

[pacman-dev] [PATCH] Print "there is nothing to do" with NOOP transactions
by Nagy Gabor 21 Jan '10

21 Jan '10

This patch was inspired by FS#17859. (That is not a bug atm due to "target loading"-interface change.) >From now on, with "empty" transactions (e.g. -Ru needed_pkg) pacman prints a " there is nothing to do" message. The " local database is up to date" message is kept for -Su. Signed-off-by: Nagy Gabor <ngaba(a)bibl.u-szeged.hu> --- Reason for resubmit: Xavier and I decided to keep the old -Su message to not confuse scripts (and users). src/pacman/remove.c | 1 + src/pacman/sync.c | 6 +++++- src/pacman/upgrade.c | 1 + 3 files changed, 7 insertions(+), 1 deletions(-) diff --git a/src/pacman/remove.c b/src/pacman/remove.c index 6d44350..61b57c7 100644 --- a/src/pacman/remove.c +++ b/src/pacman/remove.c @@ -118,6 +118,7 @@ int pacman_remove(alpm_list_t *targets) /* Step 3: actually perform the removal */ alpm_list_t *pkglist = alpm_trans_get_remove(); if(pkglist == NULL) { + printf(_(" there is nothing to do\n")); goto cleanup; /* we are done */ } /* print targets and ask user confirmation */ diff --git a/src/pacman/sync.c b/src/pacman/sync.c index a2ef616..3832f03 100644 --- a/src/pacman/sync.c +++ b/src/pacman/sync.c @@ -663,7 +663,11 @@ static int sync_trans(alpm_list_t *targets) packages = alpm_trans_get_add(); if(packages == NULL) { /* nothing to do: just exit without complaining */ - printf(_(" local database is up to date\n")); + if(config->op_s_upgrade) { + printf(_(" local database is up to date\n")); + } else { + printf(_(" there is nothing to do\n")); + } goto cleanup; } diff --git a/src/pacman/upgrade.c b/src/pacman/upgrade.c index 57c7b79..ddb4796 100644 --- a/src/pacman/upgrade.c +++ b/src/pacman/upgrade.c @@ -132,6 +132,7 @@ int pacman_upgrade(alpm_list_t *targets) /* print targets and ask user confirmation */ alpm_list_t *packages = alpm_trans_get_add(); if(packages == NULL) { /* we are done */ + printf(_(" there is nothing to do\n")); trans_release(); return(retval); } -- 1.6.6

1 0

[pacman-dev] [PATCH] makepkg: [Idea] Introduce $SRCPKGDEST
by Nezmer 20 Jan '10

20 Jan '10

Introduce $SRCPKGDEST to define a destination dir for source packages instead of saving them in $PKGDEST with binary packages. The simple patch doesn't break old behavior. Signed-off-by: Nezmer <git(a)nezmer.info> --- etc/makepkg.conf.in | 2 ++ scripts/makepkg.sh.in | 7 +++++-- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/etc/makepkg.conf.in b/etc/makepkg.conf.in index 3a3a415..b92a697 100644 --- a/etc/makepkg.conf.in +++ b/etc/makepkg.conf.in @@ -91,6 +91,8 @@ PURGE_TARGETS=(usr/{,share}/info/dir .packlist *.pod) #PKGDEST=/home/packages #-- Source cache: specify a fixed directory where source files will be cached #SRCDEST=/home/sources +#-- Source packages: specify a fixed directory where all src packages will be placed +#SRCPKGDEST=/home/srcpackages #-- Packager: name/email of the person or organization building packages #PACKAGER="John Doe <john(a)doe.com>" diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index 5bbd880..5bd294c 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -1108,7 +1108,7 @@ create_srcpackage() { "$SRCEXT" ;; esac - local pkg_file="$PKGDEST/${pkgbase}-${pkgver}-${pkgrel}${SRCEXT}" + local pkg_file="$SRCPKGDEST/${pkgbase}-${pkgver}-${pkgrel}${SRCEXT}" # tar it up msg2 "$(gettext "Compressing source package...")" @@ -1575,6 +1575,7 @@ done #preserve environment variables _PKGDEST=${PKGDEST} _SRCDEST=${SRCDEST} +_SRCPKGDEST=${SRCPKGDEST} # default config is makepkg.conf MAKEPKG_CONF=${MAKEPKG_CONF:-$confdir/makepkg.conf} @@ -1613,6 +1614,8 @@ PKGDEST=${_PKGDEST:-$PKGDEST} PKGDEST=${PKGDEST:-$startdir} #default to $startdir if undefined SRCDEST=${_SRCDEST:-$SRCDEST} SRCDEST=${SRCDEST:-$startdir} #default to $startdir if undefined +SRCPKGDEST=${_SRCPKGDEST:-$SRCPKGDEST} +SRCPKGDEST=${SRCPKGDEST:-$PKGDEST} #default to $PKGDEST if undefined if (( HOLDVER )) && [[ -n $FORCE_VER ]]; then @@ -1838,7 +1841,7 @@ msg "$(gettext "Making package: %s")" "$pkgbase $pkgver-$pkgrel ($(date))" # if we are creating a source-only package, go no further if (( SOURCEONLY )); then - if [[ -f $PKGDEST/${pkgbase}-${pkgver}-${pkgrel}${SRCEXT} ]] \ + if [[ -f $SRCPKGDEST/${pkgbase}-${pkgver}-${pkgrel}${SRCEXT} ]] \ && (( ! FORCE )); then error "$(gettext "A source package has already been built. (use -f to overwrite)")" exit 1 -- 1.6.6

6 5

[pacman-dev] [PATCH] zsh_completion: Add proper completion for --ignore and --ignoregroup (v2)
by Nezmer 20 Jan '10

20 Jan '10

This patch provides proper comma-separated completions for --ignore and --ignoregroup Signed-off-by: Nezmer <Nezmer(a)allurelinux.org> --- contrib/zsh_completion | 26 +++++++++++++++++++++++--- 1 files changed, 23 insertions(+), 3 deletions(-) diff --git a/contrib/zsh_completion b/contrib/zsh_completion index 2f43d9b..b751c82 100644 --- a/contrib/zsh_completion +++ b/contrib/zsh_completion @@ -86,9 +86,9 @@ _pacman_opts_sync_modifiers=( '-w[Download packages only]' '-y[Download fresh package databases]' '*--ignore[Ignore a package upgrade]:package: - _pacman_completions_all_packages' - '*--ignoregroup[Ignore a group upgrade]:package group: - _pacman_completions_all_groups' + _pacman_completions_ignore_packages' + '*--ignoregroup[Ignore a group upgrade]:group: + _pacman_completions_ignore_groups' '--asdeps[Install packages as non-explicitly installed]' '--asexplicit[Install packages as explicitly installed]' ) @@ -240,6 +240,26 @@ _pacman_completions_all_packages() { fi } +# provides comma-separated completions for packages available from repositories +# to be used with --ignore +_pacman_completions_ignore_packages() { + local -a cmd packages + _pacman_get_command + packages=($(pacman -Slq)) + typeset -U packages + _wanted packages expl "packages" _values -s "," compadd - "${(@)packages}" +} + +# provides comma-separated completions for package groups to be used +# with --ignoregroup +_pacman_completions_ignore_groups() { + local -a cmd groups + _pacman_get_command + groups=($(pacman -Sg)) + typeset -U groups + _wanted groups expl "groups" _values -s "," compadd - "${(@)groups}" +} + # provides completions for package groups _pacman_completions_installed_groups() { local -a cmd groups -- 1.6.5.6

3 2

[pacman-dev] [PATCH] Show used/freed space when syncing
by Hugo Chargois 20 Jan '10

20 Jan '10

Shows the "Total Used/Freed Size" after "Total Download Size" and "Total Installed Size" when syncing packages. It is the difference of installation size between packages to be updated and the installation size of the older version of these packages on disk. For exemple, if uploading to a new version of a package that has an installed size of 60 and the old version has an installed size of 50, this will show 10. Negative numbers represent space actually freed. Signed-off-by: Hugo Chargois <hugo.chargois(a)free.fr> --- src/pacman/util.c | 15 ++++++++++++--- 1 files changed, 12 insertions(+), 3 deletions(-) diff --git a/src/pacman/util.c b/src/pacman/util.c index 14a0f6c..3b4a695 100644 --- a/src/pacman/util.c +++ b/src/pacman/util.c @@ -44,6 +44,7 @@ #include "conf.h" #include "callback.h" +extern pmdb_t db_local; int trans_init(pmtransflag_t flags) { @@ -498,8 +499,8 @@ void display_targets(const alpm_list_t *pkgs, int install) { char *str; const alpm_list_t *i; - off_t isize = 0, dlsize = 0; - double mbisize = 0.0, mbdlsize = 0.0; + off_t isize = 0, dlsize = 0, localsize = 0; + double mbisize = 0.0, mbdlsize = 0.0, mdeltasize = 0.0; alpm_list_t *targets = NULL; if(!pkgs) { @@ -510,8 +511,14 @@ void display_targets(const alpm_list_t *pkgs, int install) for(i = pkgs; i; i = alpm_list_next(i)) { pmpkg_t *pkg = alpm_list_getdata(i); + char *name = alpm_pkg_get_name(pkg); + pmpkg_t *local_pkg = alpm_db_get_pkg(db_local, name); + dlsize += alpm_pkg_download_size(pkg); isize += alpm_pkg_get_isize(pkg); + if (local_pkg != NULL){ + localsize += alpm_pkg_get_isize(local_pkg); + } /* print the package size with the output if ShowSize option set */ if(config->showsize) { @@ -527,9 +534,10 @@ void display_targets(const alpm_list_t *pkgs, int install) targets = alpm_list_add(targets, str); } - /* Convert byte sizes to MB */ + /* Convert byte sizes to MB and calculate delta size*/ mbdlsize = dlsize / (1024.0 * 1024.0); mbisize = isize / (1024.0 * 1024.0); + mdeltasize = (isize - localsize) / (1024.0 * 1024.0); if(install) { asprintf(&str, _("Targets (%d):"), alpm_list_count(targets)); @@ -539,6 +547,7 @@ void display_targets(const alpm_list_t *pkgs, int install) printf(_("Total Download Size: %.2f MB\n"), mbdlsize); printf(_("Total Installed Size: %.2f MB\n"), mbisize); + printf(_("Total Size Used/Freed: % .2f MB\n"), mdeltasize); } else { asprintf(&str, _("Remove (%d):"), alpm_list_count(targets)); list_display(str, targets); -- 1.6.3.3

5 9

[pacman-dev] [PATCH] makepkg: add option holdver (like --holdver arg)
by Vesa Kaihlavirta 20 Jan '10

20 Jan '10

From: Vesa Kaihlavirta <vegai(a)iki.fi> Signed-off-by: Vesa Kaihlavirta <vegai(a)iki.fi> --- scripts/makepkg.sh.in | 15 ++++++++------- 1 files changed, 8 insertions(+), 7 deletions(-) diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index 5bbd880..78b1e22 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -44,7 +44,7 @@ startdir="$PWD" srcdir="$startdir/src" pkgdir="$startdir/pkg" -packaging_options=('strip' 'docs' 'libtool' 'emptydirs' 'zipman' 'purge') +packaging_options=('strip' 'docs' 'libtool' 'emptydirs' 'zipman' 'holdver' 'purge') other_options=('ccache' 'distcc' 'makeflags' 'force') splitpkg_overrides=('pkgver' 'pkgrel' 'pkgdesc' 'arch' 'license' 'groups' \ 'depends' 'optdepends' 'provides' 'conflicts' 'replaces' \ @@ -1269,12 +1269,13 @@ check_sanity() { devel_check() { newpkgver="" - # Do not update pkgver if --holdver is set, when building a source package, repackaging, - # reading PKGBUILD from pipe (-f), or if we cannot write to the file (-w) - if (( HOLDVER || SOURCEONLY || REPKG )) \ - || [[ ! -f $BUILDFILE || ! -w $BUILDFILE ]]; then - return - fi + # Do not update pkgver if --holdver is set, holdver option is set, when building a + # source package, when reading PKGBUILD from pipe (-f), or if we cannot write to the file (-w) + if [ "$HOLDVER" -eq 1 -o "$(check_option holdver)" = "y" \ + -o "$SOURCEONLY" -ne 0 -o ! -f "$BUILDFILE" \ + -o ! -w "$BUILDFILE" ]; then + return + fi if [[ -z $FORCE_VER ]]; then # Check if this is a svn/cvs/etc PKGBUILD; set $newpkgver if so. -- 1.6.6

3 5

[pacman-dev] [PATCH] Remove setgid bit on srcdir/pkgdir creation
by Dan McGee 20 Jan '10

20 Jan '10

It was noted in FS#17533 that setgid bits are carried down into any created subdirectories, and thus could end up being in a built package if the original package directory was marked g+s. When we create src/ and pkg/, explicitly chmod them to remove any sticky bits. Signed-off-by: Dan McGee <dan(a)archlinux.org> --- scripts/makepkg.sh.in | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index 5bd294c..c2045e5 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -1056,6 +1056,7 @@ create_srcpackage() { # Get back to our src directory so we can begin with sources. mkdir -p "$srcdir" + chmod a-s "$srcdir" cd "$srcdir" download_sources # We can only check checksums if we have all files. @@ -1725,6 +1726,7 @@ fi if (( GENINTEG )); then mkdir -p "$srcdir" + chmod a-s "$srcdir" cd "$srcdir" download_sources generate_checksums @@ -1824,6 +1826,7 @@ if (( INFAKEROOT )); then for pkg in ${pkgname[@]}; do pkgdir="$pkgdir/$pkg" mkdir -p "$pkgdir" + chmod a-s "$pkgdir" backup_package_variables run_package $pkg tidy_install @@ -1880,6 +1883,7 @@ umask 0022 # get back to our src directory so we can begin with sources mkdir -p "$srcdir" +chmod a-s "$srcdir" cd "$srcdir" if (( NOEXTRACT )); then @@ -1915,6 +1919,7 @@ else rm -rf "$pkgdir" fi mkdir -p "$pkgdir" + chmod a-s "$pkgdir" cd "$startdir" # if we are root or if fakeroot is not enabled, then we don't use it @@ -1935,6 +1940,7 @@ else for pkg in ${pkgname[@]}; do pkgdir="$pkgdir/$pkg" mkdir -p "$pkgdir" + chmod a-s "$pkgdir" backup_package_variables run_package $pkg tidy_install -- 1.6.6

3 4

[pacman-dev] [GIT] The official pacman repository branch, maint, updated. v3.3.3-5-g8b3f5f0
by dan＠archlinux.org 20 Jan '10

20 Jan '10

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, maint has been updated via 8b3f5f0ce6dca98ca14cc48f5a85188313769b40 (commit) via ce9bb994f86f9653dc293f2dda0f8f2160964090 (commit) via 0c3f5020645ab5ab28113322e33abdeeb2b34a63 (commit) via a12ed63545ee16d37da2b28bbf4c1820bd367315 (commit) from 335627d72dd5e51201b4cd53d84b70954946c013 (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 ----------------------------------------------------------------- ----------------------------------------------------------------------- Summary of changes: contrib/bacman | 4 ++-- contrib/bash_completion | 28 ++++++++++++++-------------- lib/libalpm/alpm.c | 1 + scripts/makepkg.sh.in | 7 ++++--- 4 files changed, 21 insertions(+), 19 deletions(-) hooks/post-receive -- The official pacman repository

1 0