You are not logged in.
there's one thing missing..
if I'm installing something with yaourt, it should respond to the unix SIGNALS correctly, this is:
- if I press Ctrl+C it should stop and sigterm the pacman/libalpm and then stop the yaourt thing.
it happens not. I must press up to 3 times to stop yaourt from installing that app.
Last edited by quarkup (2009-10-09 23:02:47)
If people do not believe that mathematics is simple, it is only because they do not realize how complicated life is.
Simplicity is the ultimate sophistication.
Offline
I find it a little bit strange that yaourt asks twice if one wishes to edit PKGBUILD and .install files.
Shouldn't one query be enough?
<rickh> f(Arch) = ((Gentoo - Compiletime) + (Slackware + Depency resolution and Downloading))
Offline
Guy, what do you think about about such optoin to add to yaourt or pacman.
So for example we list available updates, but add the time when the package is appeared.
==> Software upgrade (new version) :
extra/aria2 1.6.3-1 -> 1.7.1-2 (10 days ago)
Is it possible?
It would help for those who wants to stick to tested releases by community and avoid upgrading to newest packages those have a risk of non-discovered bugs and just update to these packages later after a few weeks of the release date.
Sometimes I update right away after packages are released, but when I don't have time to fix something I would prefer to stay away from newest upgrades. But the problem it is hard to know which is new package and which one is old
Offline
I find it a little bit strange that yaourt asks twice if one wishes to edit PKGBUILD and .install files.
Shouldn't one query be enough?
I agree - or the post-edit query should be a different one, with [Y/n] rather than [y/N].
Offline
When I try to install packages from AUR, when I press 'y' or 'n' when it asks about editing the PKGBUILD, yaourt just kills itself with no output. If I press y, it opens nano like normal but when I close it yaourt is still dead. Any ideas?
Offline
When I try to issue a
yaourt -Syub
It tries to compile the correct software, but not the right version. It tries to compile the version I already have installed instead of the newest version.
Yet
yaourt -Syu
works just fine.
Is this a bug, or am I missing something?
Offline
Maybe it was mentioned somehere, but since one or two month, my yaourt output looks like this.
It is a bug or my fault?
23:52:37::$ y -S rtorrent-svn --noconfirm
==> Resuming previous build
==> Downloading $PKG PKGBUILD from AUR...
[...]
:: rtorrent-color: steht im Konflikt mit rtorrent
==> WARNING: Your package is saved in $YAOURTTMPDIR/$pkgname-$pkgver-$pkgrel-$PARCH${PKGEXT}
Last edited by posativ (2009-12-26 22:57:43)
Offline
So, I'm using yaourt-git and I have my sudo timeout set to ask for a password every time.
So, if I run yaourt, it asks for my password three times. Is there any way to consolidate that into one?
Offline
So, I'm using yaourt-git and I have my sudo timeout set to ask for a password every time.
So, if I run yaourt, it asks for my password three times. Is there any way to consolidate that into one?
Yaourt can be modified to support this, all it really requires is this
stty -echo
read -p "sudo password: " spass
stty echo
sudo -S [command] <<<${spass}
Last edited by some-guy94 (2010-02-18 00:30:26)
Offline
pogeymanz wrote:So, I'm using yaourt-git and I have my sudo timeout set to ask for a password every time.
So, if I run yaourt, it asks for my password three times. Is there any way to consolidate that into one?
Yaourt can be modified to support this, all it really requires is this
stty -echo read -p "sudo password: " spass stty echo sudo -S [command] <<<${spass}
sorry, but I don't understand, how do you stop it asking 3 times?
Offline
He propose that yaourt stores password and then use it for each sudo call, but the password will be available for every PKGBUILD and visible in process list.
If you want to disable sudo verification, just modify "is_sudo_allowed()" in /usr/bin/yaourt:
is_sudo_allowed()
{
return 0
}
Offline
He propose that yaourt stores password and then use it for each sudo call, but the password will be available for every PKGBUILD and visible in process list.
If you want to disable sudo verification, just modify "is_sudo_allowed()" in /usr/bin/yaourt:
is_sudo_allowed() { return 0 }
Thank you very much, that worked a treat
Offline
When I try to issue a
yaourt -Syub
It tries to compile the correct software, but not the right version. It tries to compile the version I already have installed instead of the newest version.
Yet
yaourt -Syu
works just fine.
Is this a bug, or am I missing something?
The rsync server is not updated as often as your mirror, so you will have to wait a bit before the current version reaches it.
I'm french, don't mind my mistakes in english.
Offline
is yaourt is being maintained? I heard the development has stopped
Acer Aspire V5-573P Antergos KDE
Offline
Slowly maintained, but has not completely stopped.
Offline
why use it, anyways
[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
how did this become a "dont use yaourt" thread? you dont like it/use it/care, please skip the thread...
it is maintained, slow or fast.. it is used by many of us..
back on topic, can someone explain to me the difference between the yaourt package and yaourt-git? on my desktop I upgraded yaourt, and get warned about new config file (yaourtrc). on laptop, using -git, i get no such message. both yaourtrc's look the same to me..
"I know what you're thinking, 'cause right now I'm thinking the same thing. Actually, I've been thinking it ever since I got here:
Why oh why didn't I take the BLUE pill?"
Offline
how did this become a "dont use yaourt" thread? you dont like it/use it/care, please skip the thread...
it is maintained, slow or fast.. it is used by many of us..
I agree. Yaourt is a great program and has worked perfectly for me since I started using Arch Linux back in 2005. There are regular upgrades to adjust to changes to pacman. Please stop the FUD about it not being maintained.
Offline
back on topic, can someone explain to me the difference between the yaourt package and yaourt-git?
now, it's the same cause the last commit corresponds to the last release, otherwise, -git is the development version.
on my desktop I upgraded yaourt, and get warned about new config file (yaourtrc). on laptop, using -git, i get no such message. both yaourtrc's look the same to me..
yaourtrc has bash syntax in -git since a while now, I simply forget to update the PKGBUILD to show the warning in the -git package.
Offline
how did this become a "dont use yaourt" thread? you dont like it/use it/care, please skip the thread...
it is maintained, slow or fast.. it is used by many of us..
No kidding. There was a bug in the last release, I created a bug report, the maintainer quickly wrote the patch and the fix was out a day later or so. Hey, if it ain't broke, why fix it?
Offline
after last pacman upgrade, i keep getting this message
/usr/bin/pacman: unrecognized option '--print-uris'
after running yaourt --noconfirm -Syu
how can i fix this?
Offline
after last pacman upgrade, i keep getting this message
/usr/bin/pacman: unrecognized option '--print-uris'
after running yaourt --noconfirm -Syu
how can i fix this?
I assume there will be a yaourt upgrade to handle the new pacman. I you can't wait, it is written in bash. You could just get rid of the option in question and see what happens.
Offline
You have a very old version, update yaourt.
Offline
smau [~] $ yaourt -V
yaourt 0.9.4.3 is a pacman frontend with AUR support and more
homepage: http://archlinux.fr/yaourt
isn't this the last version?
Offline
It is, but 0.9.4.3 doesn't use --print-uris, it runs "pacman -Spu"
Did you installed it from AUR ?
Offline