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: 1142
Popularity: 0.000039
First Submitted: 2010-03-24 23:18 (UTC)
Last Updated: 2021-06-02 15:03 (UTC)

Latest Comments

« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 51 Next › Last »

joko commented on 2015-01-07 07:39 (UTC)

Hello, everyone, I'd like to share my experience upgrading package-query while moving from pacman 4.1 to 4.2. My installed version of package-query requiring pacman<=4.2, thus I couldn't upgrade my system straightforwardly. So, I built package-query 1.5-2 manually with makepkg -si. yaourt -Syua updated properly pacman then, but it stopped working in the middle, because the libalpm.so.8 dependency issue that other users have already reported. At this point, I did pacman-db-upgrade and then rebuilt package-query 1.5-2 manually and finally my system was working as intended.

rafaelff commented on 2015-01-05 19:14 (UTC)

Guys, please do not extend this discussion in this Comment list. Only issues related to package build/installation/bugs should take place in here. For other types of discussion, do it in aur-general mail list.

Scimmia commented on 2015-01-05 18:58 (UTC)

@kerberizer, there's a number of reasons. The first reason is philosophical, but the others are practical problems. 1. It encourages people to stay willfully ignorant of how the AUR work. AUR helpers are nice, but you should know what they're doing. Arch's only supported method of using the AUR is running makepkg directly, so it's vitally important that you know how to use it. 2. Since the repo is unofficial, the packages aren't rebuilt/moved at exactly the same time as the official package. This is really only a problem because of #1, as people who know how to use the AUR don't have a problem with it. 3. The repo is a mess. Have you ever looked at what is all there? If it gets put in at the top of pacman.conf, it can cause problems. If a user tries to install an AUR package that has an old version already build in the repo, it causes problems. Packages in the repo aren't always built in a clean chroot, so they cause problems. These packages aren't included in to-do lists, so they often miss changes in Arch, causing problems. Should I continue?

kerberizer commented on 2015-01-05 16:25 (UTC)

@crossroads1112, you would've saved us both from needlessly spamming the comments if you had first read carefully my comment. I had said exactly the same you did. @Scimmia, could you please elaborate on why the archlinux.fr repo is "really pretty bad"? Why not notify the maintainers of the problems? And if it's that hopeless, well, let's make a new, better repo -- specifically for package-query and yaourt. @agent0, you could simplify the things a little bit and avoid some possible mistakes by using "makepkg -is". "-i" stands for install and will simply invoke "pacman -U" automatically (thus no way you could accidentally re-install a package from the cache). I typically use "-cifs" myself, which also cleans the directory afterwards and forces the build even if there is a previously build package. P.S. My personal opinion is that understanding how to solve such problems on your own will benefit most users (this is one of the reasons to use Arch, after all), but I also understand why some users feel frustration instead and would have preferred a more automagic-type approach.

agent0 commented on 2015-01-05 03:24 (UTC)

@Scimmia, @josephgbr, I completely did all things again: remove package-query, yaourt, yaourt-gui. Then I downloaded package-query's PKGBUILD and did makepkg -s. Then installed via pacman -U. For now ldd /usr/bin/package-query | grep alpm shows libalpm.so.9 => /usr/lib/libalpm.so.9 (0x00007fba43511000). Maybe when I reinstalled packege-query it was installed from cache? Do not know. It was written if I want to reinstall package and I answered yes. And by the way, I did not removed yaourt that time. Maybe that was a problem. Anyway, for now problem is solved for me. Thank you!

Scimmia commented on 2015-01-05 03:08 (UTC)

@agent0, how about using objdump -p instead of ldd, does it still point to libalpm.so.8? There's no way the system can link something at build time to a library that doesn't exist.

rafaelff commented on 2015-01-05 03:05 (UTC)

agent0: looks good. Please make sure you installed the pkg.tar.xz you just built, and not an old build.

agent0 commented on 2015-01-05 02:30 (UTC)

@josephgbr, I checked that my pacman version is 4.2.0-5, but to be clear, I reinstalled pacman itself via pacman. Then I makepkg -s for package-query. It's version is 1.5-2. Then I reinstall it. $ ldd /usr/bin/package-query | grep alpm libalpm.so.8 => not found What the hell? @Scimmia, already removed that symlink. I understand that it is bad thing, but how I then solve problem?

« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 51 Next › Last »