Package Details: package-query 1.12-1

Git Clone URL: https://aur.archlinux.org/package-query.git (read-only, click to copy)
Package Base: package-query
Description: Query ALPM and AUR
Upstream URL: https://github.com/archlinuxfr/package-query/
Licenses: GPL
Submitter: tuxce
Maintainer: matthewq337 (Skunnyk, f2404)
Last Packager: Skunnyk
Votes: 1143
Popularity: 0.009438
First Submitted: 2010-03-24 23:18 (UTC)
Last Updated: 2021-06-02 15:03 (UTC)

Latest Comments

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 51 Next › Last »

ahioros commented on 2016-02-07 02:50 (UTC) (edited on 2016-02-07 03:57 (UTC) by ahioros)

@josephgbr i follow you trying upgrade and i have this message: /usr/lib/yaourt/util.sh: line 166: package-query: not found /usr/lib/yaourt/util.sh: line 166: package-query: not found % pacman -Qs package-query local/package-query 1.7-2 Query ALPM and AUR update #archlinux irc channel topic: Welcome to Arch Linux World Domination, Inc. <+> Be kind to the people who are helping you. Be kind to the people you are trying to help. <+> pacman 5.0 in [core]! http://allanmcrae.com/2016/01/pacman-5-0-released/ <+> old package-query versions are incompatible with pacman 5.0, update it or remove it along with yaourt

rafaelff commented on 2016-02-06 01:35 (UTC)

Basically, it is required to: 1- remove package-query - if you have a package that requires it, remove too (to reinstall later). 2- run system update, which will update pacman to 5.0.0 (sudo pacman -Syu) 3- with pacman 5.0.0 installed, rebuild package-query and install, along with other helpers you want, e.g. pacupg, yaourt, etc. done

kerberizer commented on 2016-02-05 22:25 (UTC)

@valentin.brasov, obviously you need to also update (or, rather, uninstall and rebuild after pacman is updated) pacdep as well... https://aur.archlinux.org/cgit/aur.git/commit/?h=pacdep&id=e5d5b043eda1583daa1bf3d261cee3e97dab5cb5

valentin.brasov commented on 2016-02-05 22:12 (UTC)

Hi again, Trying on another system, I run into a problem: So firstly I run successfully: # pacman -Rdd package-query yaourt Then when I do: # pacman -Syu I get: error: failed to prepare transaction (could not satisfy dependencies) :: pacdep: requires pacman<4.3 Then I checked what pacman version I have: # pacman --version Ad it prints: Pacman v4.2.1 - libalpm v9.0.1 Please help.

ondoho commented on 2016-02-05 13:15 (UTC) (edited on 2016-02-05 13:16 (UTC) by ondoho)

__"You can symlink, rebuild (package-query), and remove the symlink. Still, I'd probably rebuild a second time -- just to be sure."__ this is what i just did, and now all works. from what i can see (i hope i'm not missing anything) there can't be any harm in it.

kerberizer commented on 2016-02-04 22:13 (UTC) (edited on 2016-02-04 22:15 (UTC) by kerberizer)

@el_Salmon: Pretty sure you get the same message as @accessgranted, namely "WARNING: A package has already been built, installing existing package..." Do not use "makepkg -si". Use "makepkg -sif" instead. "-f" stands for "force", i.e. build a new package even if there is already an existing one in the output directory. It also may be a good practice as extra precaution to clean the "src" directory in advance with "-C", so finally the command would become "makepkg -Cifs". Also, as other people have noted elsewhere, you don't really need to rebuild yaourt (but probably should uninstall and reinstall it anyway, unless you want to break your package dependencies).

<deleted-account> commented on 2016-02-04 20:57 (UTC)

Removing and installing package-query and yaourt like in [1] doesn't work for me. I get the same error always: $yaourt -Syu package-query: error while loading shared libraries: libalpm.so.9: cannot open shared object file: No such file or directory [1] https://archlinux.fr/yaourt-en

kerberizer commented on 2016-02-04 00:00 (UTC)

@asafk: That's what I had in mind with "in a pinch". Still, I'd probably rebuild a second time -- just to be sure. ;) And to be honest, I also think anyone should be able to rebuild at least package-query without any helper tool. Don't get lazy, people! @all: Also, be careful what you do and pay attention to any warnings or suspicious messages. Take for example @accessgranted's problem: he/she hadn't noticed the message "WARNING: A package has already been built, installing existing package..." So, instead of rebuilding the package, accessgranted just reinstalled their old one. No surprise that the missing library problem persisted. Linux is not really that tough, but it does require some effort. Obviously, you're not afraid of that effort, so do the things the right way. This is what really makes you stand out of the Windows crowd. ;)

asafk commented on 2016-02-03 23:47 (UTC)

You can symlink, rebuild, and remove the symlink. That's what I did and it works just peachy.

kerberizer commented on 2016-02-03 22:48 (UTC)

I'm sorry to have to say this, but symlinking to libraries with a different soname, even just with respect to the version (the number after the .so extension), is a _bad_ idea. While it can probably be used in a pinch to just run a thing or two needed for a proper rebuild, one should _never_ use it as a substitution to that rebuild. There _is_ a reason why the soname gets bumped: it doesn't get bumped that often actually. Bumping means incompatibility and the problem is that it may look like everything's working OK, but then, just when you've already forgotten what you did with that symlink, strange errors begin to occur. And then everybody wastes precious time debugging those errors until you remember at last about that symlink. TL;DR: Don't symlink different version shared libraries. Rebuild!

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 51 Next › Last »