You are not logged in.
Pages: 1
Hi,
I had to do a full system upgrade today and when I came to the point where I wanted to install my favourite browser, yaourt failed.
I typed:
$yaourt -S chromium-browser-bin
A list of the usual stuff pops up, eg. the comments and what not.. Then I get the typical warning about whether or not I would like to modify the pkgbuild which, of course, I would select yes (problem still happens if I hit no).. Immediately after that, I'm back with
chromium-browser-bin LATEST-12 : The open-source project behind Google Chrome
( Unsupported package: Potentally dangerous ! )
==> Edit the PKGBUILD (highly recommended for security reasons) ? [Y/n]("A" to abort)
==> ----------------------------------------------
==>n
[molecular-bio@archbox ~]$
Does this potentially mean that this package is deleted?
yaourt works for other packages, so I'm not sure here... I really, really liked the chromium-browser-bin package.
Thank you
Last edited by 10wattmindtrip (2009-12-28 14:18:01)
which would you choose: A god that never answers you or a society that embraces you?
Offline
Chromium is now in extra
Keep it Simple, Sexy
Offline
Chromium is now in extra
Thank you for answering.
Yes, I know chromium is in extra now. However, it's, I think, the beta 4.249. I'm a bleeding edge freak when it comes to Chrome/Chromium (bookmark sync and extensions). The one I had prior to re-installation was 4.283, or something like that anyway.
Oh well, I suppose I'll use the one in extra for now.
Thank you.
which would you choose: A god that never answers you or a society that embraces you?
Offline
You might want to check the page for chromium-browser-bin in AUR. There is a discussion about problems yaourt is having handling the PKGBUILD (or vice versa), plus possible workarounds.
Offline
You might want to check the page for chromium-browser-bin in AUR. There is a discussion about problems yaourt is having handling the PKGBUILD (or vice versa), plus possible workarounds.
Thank you very much.
which would you choose: A god that never answers you or a society that embraces you?
Offline
It's best to use ABS and compile chromium from source. Those PKGBUILDs found in the AUR are broken by design.
Offline
It's best to use ABS and compile chromium from source. Those PKGBUILDs found in the AUR are broken by design.
Uh? Care to elaborate or provide the interesting read link? Now you got me curious As far as I can tell PKGBUILDs from AUR don't look too much different from the ones in ABS (apart from the difference that the ones in ABS are checked to be sane because they are used to build the packages in the repos afaik).
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
I've had the same trouble with yaourt and chromium-browser-bin from the AUR. But downloading the PKGBUILD and other files and building via makepkg works fine still.
I use Xyne's pbget to grab the PKGBUILD.
http://xyne.archlinux.ca/info/pbget
Last edited by reed9 (2009-12-28 16:19:58)
Offline
The problem is with yaourt's parser. Using a different AUR helper, this problem disappears.
However, I can understand the attraction of using Yaourt. You can make chromium-browser-bin and chromium-codecs-ffmpeg-nonfree-bin work with yaourt by editing the PKGBUILDs. Where it says:
case "$CARCH" in
i686|i[3-5]86) _bldarch='chromium-rel-linux';;
x86_64|amd64) _bldarch='chromium-rel-linux-64';;
# The following should not happen; provided you're using 'makepkg' ;)
*) error "Unknown or invalid CARCH=$CARCH"; exit 1
esac
Replace that with the one for the version that you have:
64-bit Arch
_bldarch=chromium-rel-linux-64
32-bit Arch
_bldarch=chromium-rel-linux
(Edit: stupidly had the two swapped)
Last edited by airbreather (2010-03-17 12:25:03)
Offline
Pages: 1