You are not logged in.
Trying to install the Iron build of Chromium:
==> Making package: iron 4.0.227-2 x86_64 (Wed Dec 9 14:26:24 EST 2009)
==> Checking Runtime Dependencies...
==> Installing missing dependencies...
lib32-dbus-glib package not found, searching for group...
[b]error: 'lib32-dbus-glib': not found in sync db[/b]
==> ERROR: Pacman failed to install missing dependencies.
Error: Makepkg was unable to build iron package.Note lib32-dbus-glib really is on AUR. Also,
$ yaourt -S lib32-dbus-glib --asdepsworks fine (but then I need to install lib32-gconf by hand also). On the other hand,
$ yaourt -S lib32-gconf #another dependency for Iron
==> lib32-gconf dependencies:
- lib32-orbit2 (building from AUR)
- lib32-gtk2 (package found)
- lib32-libxml2 (package found)This seems pretty inconsistent. Why is yaourt pulling in dependencies from AUR to install lib32-gconf but not to install Iron?
Edit: notice the build order seems to be different, because one somehow (?) gets identified as a _runtime_ dependency.
Last edited by Fixnum (2009-12-09 19:59:05)
Offline
I changed the PKGBUILD from
if [[ $CARCH = x86_64 ]]; then
depends=('lib32-alsa-lib' 'lib32-dbus-glib' 'lib32-gconf' 'lib32-nss' 'lib32-libxdamage' 'ttf-dejavu')
optdepends=('nspluginwrapper-flash: flash support')
else
depends=('alsa-lib' 'gconf' 'nss' 'ttf-dejavu')
fito
depends=('lib32-alsa-lib' 'lib32-dbus-glib' 'lib32-gconf' 'lib32-nss' 'lib32-libxdamage' 'ttf-dejavu')
optdepends=('nspluginwrapper-flash: flash support')and suddenly it works. So, I noticed this (installing from original PKGBUILD):
==> iron dependencies:
- alsa-lib (already installed)
- gconf (already installed)
- nss (already installed)
- ttf-dejavu (already installed)So, it seems like pacman/yaourt is initially getting dependencies for the wrong architecture and only later coming back and only later getting the correct dependencies from testing against $CARCH, but at this point it screws up for some reason, and the added dependencies like lib32-<stuff> are "not found in sync db" ...
Edit: this issue persists in yaourt-git.
Last edited by Fixnum (2009-12-10 20:46:58)
Offline
paktahn > yaourt =]
[home page] -- [code / configs]
"Once you go Arch, you must remain there for life or else Allan will track you down and break you."
-- Bregol
Offline
Yeah yaourt doesn't handle [ $CARCH = x86_64 ] for some reason, not sure just why.
Setting Up a Scripting Environment | Proud donor to wikipedia - link
Offline
This is why we need to drop bash PKGBUILDs in favor of a universally parsable format.
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline