You are not logged in.
Thanks Spyhawk for your care.
I don't have sudo installed
.bashrc
/etc/bash.bashrc
/etc/bash.bashrc.local does not exist
bash -x pacaur -S arch-bubble-icons
zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)
Offline
I don't have sudo installed
So it seems that "yes | makepkg <option>" doesn't work with "su", although it does when sudo is installed. Beh.
I'm currently working on a fix, and the good news is that I've been able to make it working without sudo. I still have some other side effects to solve, but I might be able to release pacaur 2.3.9 very soon :]
Stay tuned!
Last edited by Spyhawk (2011-10-23 19:11:16)
Offline
Wow, thanks. TBH about the only thing I dont feel comfortable in pacaur is this very feature, that it automatically answers yes to all questions. I know pacaur is intended for "fast" workflow, but I personally feel like I have more control if I answer to pacman's questions personally. Matter of taste.
zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)
Offline
Wow, thanks. TBH about the only thing I dont feel comfortable in pacaur is this very feature, that it automatically answers yes to all questions. I know pacaur is intended for "fast" workflow, but I personally feel like I have more control if I answer to pacman's questions personally. Matter of taste.
You're probably not in the userbase target then. Pacaur intentionally doesn't take your hand all along the process: you confirm the main prompt and conflict questions, then pacaur execute your decision. No need to confirm something twice :]
Offline
You're probably not in the userbase target then.
Wrong, I am definitely a target.
PS. Too bad, my next original post was removed due to the forum error, I'll try to repost it as well.
Last edited by SanskritFritz (2011-10-25 11:23:50)
zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)
Offline
SanskritFritz> About your "next-but-deleted" post (unable to install from AUR when an extra third party repository provide a compiled package): you might want to have a look at the IgnoreRepo option of cower config file. I thought initially about including a "--ignorerepo" flag in pacaur, but that is a very special usercase and I don't think it makes lot of sense to add it in a practical point of view. Add your extra repo to cower config file, and use pacaur's --repo flag to install from binary repo.
And now the not so good news: I've been looking into the "standard in must be a tty" issue for the past 2 days or so, and I haven't been able to find a proper workaround. Unlike sudo, it seems "su" simply does't support pipe (for security reason), and that leaves me with the following possibilities:
- not using the pipe at all (as 2.3.3), and removing pacaur conflict handling support;
- adding very ugly hack directly in the code (if su, then do that, elif sudo do it like this .... else .. fi) and sometimes adding additional code to handle su special cases, not to mention that the runasroot() function won't make sense anymore;
- changing entirely the internal design and dropping the "fast workflow" feature;
- dropping su support entirely.
As you might have guessed, the solution I'm thinking of actually is the very last one. Unless someone can figure out a proper solution, it doesn't make sense to impede the fast workflow feature that is the basis of the design. Fast workflow doesn't even is that fast when you're not using sudo afterall, and in that case packer might also be a really good choice.
Offline
Hi all, first thing, GREAT program thanks a lot!!
but one weirdness... this is hopefully just me but wanted to let you know anyways:
- If I do "pac -Sy mc" mc installs normally
- If I do "pac -Sy packer" I get an "error target not found: packer" like:
[maroco@MBlack ~]$ pac -Sy packer
:: Synchronisiere Paketdatenbanken...
core ist aktuell
extra ist aktuell
community ist aktuell
multilib ist aktuell
Fehler: Ziel nicht gefunden: packer
- And if I do "pac -m packer" packer installs completely normal like
:: packer-20111031-1 is up to date -- reinstalling
:: AUR package(s) to build: packer
Proceed with installation? [Y/n] y
Huh..?!? Is that just me? Anyway, no big deal as I can install it but.. funny
Cheers
Maroco
Btw, +1 for pogeymanz comment "Also, I LOVE that all the editing happens BEFORE the packages get installed. " Thanks
Offline
Hi all, first thing, GREAT program thanks a lot!!
but one weirdness... this is hopefully just me but wanted to let you know anyways:
- If I do "pac -Sy mc" mc installs normally- If I do "pac -Sy packer" I get an "error target not found: packer" like:
[maroco@MBlack ~]$ pac -Sy packer
:: Synchronisiere Paketdatenbanken...
core ist aktuell
extra ist aktuell
community ist aktuell
multilib ist aktuell
Fehler: Ziel nicht gefunden: packer
Ah ja.. -Sy redirect to pacman directly, not cower. I actually never use "pacaur -Sy <package>" to install, just -S. I'll see if I can change that behavior.
- And if I do "pac -m packer" packer installs completely normal like
:: packer-20111031-1 is up to date -- reinstalling
:: AUR package(s) to build: packer
Proceed with installation? [Y/n] yHuh..?!? Is that just me? Anyway, no big deal as I can install it but.. funny
Cheers
Maroco
-m actually does not install the package (it only builds it, or if necessary installs dependencies, builds the package then removes the dependencies), but I should have worded the prompt differently :]
Edit: also, please check the first post if you're using German locale.
Btw, +1 for pogeymanz comment "Also, I LOVE that all the editing happens BEFORE the packages get installed. " Thanks
If I'm not mistaken, bauerbill was doing it way before pacaur existed. I did not invent anything at all
Edit: Both issues should now be fixed in 2.3.10. Thanks for your feedback.
Last edited by Spyhawk (2011-10-31 22:49:13)
Offline
Hi Spyhawk,
thanks for the quick reaction. Not sure about bauerbill right now... Hello brain, remember... No offline apparently I used bauerbill quite some time but it tended to eat lot's of memory on my main machine (but JUST there, never found out why) and meanwhile is an "old project" on Xynes page anyway so I started looking for alternatives some time ago. Actually that brought me to pacaur finally after I found neither yaourt nor packer, clyde etc. do everything aroung packages *exactly* the way humble me thinks is perfect.
Regarding your language hint: THANKS
Actually I put > alias pac='LANG="en_US.UTF-8" pacaur' < in my .bashrc right after I discovered and installed pacaur but -after quite some headscratching on my part- I finally found out that years ago I must have set LANG, LC_ALL and company in /etc/environment to de_DE too. So the .basrc entry didn't have any effect. Cool, again one 'error' less on my pc.
So I happily installed pacaur 2.3.11 and tried again - and now am even more confused...
I used yaourt as a test subject, and in short "pac -S yaourt" and "pac -Sy yaourt" still produce the very same "target not found error" here, whilst "pac -y yaourt" after I had put LANG, LC_ALL etc in .bashrc and deleted it from /etc/environment now makes AND installs yaourt nicely.
(And the -m option... oh well. silly me found out about its meaning on my own in the meantime but thanks for pointing out again it 'M'akes packages but doesn't 'Y'nstall them. I should have verified... )
After all I guess the -S / -Sy thing is actually a no-problem as pacaur seems to work perfectly with -y but for curiosities sake I'd like to know WHY they don't work here but apparently on your machine. I guess the sister of Miss Configured is still lingering around here somewhere...
So just for the record in case you want to investigate further:
the options in my /etc/pacaur are:
buildDir="/tmp/pacaurtmp-$USER"
editor="$EDITOR"
color=true
clean=true
fallback=false
carchmagic=true
And here's the terminal history. If you need anything else, just tell me what.
(I used yaourt -h just to confirm presence or absence of yaourt btw)
[maroco@MBlack ~]$ yaourt -h
Usage: yaourt <operation> [...]
operations:
yaourt (search pattern|package file)
yaourt {-h --help}
yaourt {-V --version}
yaourt {-Q --query} [options] [package(s)]
yaourt {-R --remove} [options] <package(s)>
yaourt {-S --sync} [options] [package(s)]
yaourt {-U --upgrade} [options] <package(s)>
yaourt {-C --clean} [options]
yaourt {-B --backup} [save directory|restore file]
yaourt {-G --getpkgbuild} [options] <package(s)>
yaourt {--stats}
[maroco@MBlack ~]$ pac -R yaourt
checking dependencies...
Remove (1): yaourt-0.10.2-1 [0.22 MB]
Total Removed Size: 0.22 MB
Do you want to remove these packages? [Y/n]
(1/1) removing yaourt [----------------------] 100%
[maroco@MBlack ~]$ yaourt -h
bash: /usr/bin/yaourt: Datei oder Verzeichnis nicht gefunden
[maroco@MBlack ~]$ pac -Sy yaourt
:: Synchronizing package databases...
core is up to date
extra is up to date
xyne-any is up to date
community is up to date
multilib is up to date
error: target not found: yaourt
[maroco@MBlack ~]$ pac -S yaourt
error: target not found: yaourt
[maroco@MBlack ~]$ pac -y yaourt
:: AUR package(s) to build: yaourt
Proceed with installation? [Y/n]
:: Building yaourt package...
==> Making package: yaourt 0.10.2-1 (Wed Nov 2 22:20:08 CET 2011)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
-> Downloading yaourt-0.10.2.tar.gz...
--2011-11-02 22:20:08-- [url]http://mir.archlinux.fr/~tuxce/releases/yaourt/yaourt-0.10.2.tar.gz[/url]
Resolving mir.archlinux.fr... 91.121.141.57
Connecting to mir.archlinux.fr|91.121.141.57|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 51489 (50K) [application/x-gzip]
Saving to: `yaourt-0.10.2.tar.gz.part'
100%[======================================>] 51,489 --.-K/s in 0.1s
2011-11-02 22:20:08 (438 KB/s) - `yaourt-0.10.2.tar.gz.part' saved [51489/51489]
==> Validating source files with md5sums...
yaourt-0.10.2.tar.gz ... Passed
==> Extracting Sources...
-> Extracting yaourt-0.10.2.tar.gz with bsdtar
==> Starting build()...
GEN yaourt.sh
GEN lib/util.sh
GEN lib/pkgbuild.sh
GEN pacdiffviewer.sh
GEN lib/pacman.sh
==> Entering fakeroot environment...
==> Starting package()...
/bin/install -d /tmp/pacaurtmp-maroco/yaourt/pkg/usr/bin
/bin/install -d /tmp/pacaurtmp-maroco/yaourt/pkg/usr/lib/yaourt
/bin/install -d /tmp/pacaurtmp-maroco/yaourt/pkg/etc
/bin/install -d /tmp/pacaurtmp-maroco/yaourt/pkg/etc/bash_completion.d
/bin/install -d /tmp/pacaurtmp-maroco/yaourt/pkg/usr/share/man/man{5,8}
# Scripts
/bin/install -m755 yaourt.sh /tmp/pacaurtmp-maroco/yaourt/pkg/usr/bin/yaourt
/bin/install -m755 pacdiffviewer.sh /tmp/pacaurtmp-maroco/yaourt/pkg/usr/bin/pacdiffviewer
# Configuration
/bin/install -m644 yaourtrc /tmp/pacaurtmp-maroco/yaourt/pkg/etc/yaourtrc
/bin/install -m644 bashcompletion /tmp/pacaurtmp-maroco/yaourt/pkg/etc/bash_completion.d/yaourt
# Libs
/bin/install -m644 lib/alpm_backup.sh /tmp/pacaurtmp-maroco/yaourt/pkg/usr/lib/yaourt
/bin/install -m644 lib/alpm_query.sh /tmp/pacaurtmp-maroco/yaourt/pkg/usr/lib/yaourt
/bin/install -m644 lib/alpm_stats.sh /tmp/pacaurtmp-maroco/yaourt/pkg/usr/lib/yaourt
/bin/install -m644 lib/abs.sh /tmp/pacaurtmp-maroco/yaourt/pkg/usr/lib/yaourt
/bin/install -m644 lib/aur.sh /tmp/pacaurtmp-maroco/yaourt/pkg/usr/lib/yaourt
/bin/install -m644 lib/util.sh /tmp/pacaurtmp-maroco/yaourt/pkg/usr/lib/yaourt
/bin/install -m644 lib/io.sh /tmp/pacaurtmp-maroco/yaourt/pkg/usr/lib/yaourt
/bin/install -m644 lib/pacman.sh /tmp/pacaurtmp-maroco/yaourt/pkg/usr/lib/yaourt
/bin/install -m644 lib/pkgbuild.sh /tmp/pacaurtmp-maroco/yaourt/pkg/usr/lib/yaourt
# Man
/bin/install -m644 man/*.5 /tmp/pacaurtmp-maroco/yaourt/pkg/usr/share/man/man5
/bin/install -m644 man/*.8 /tmp/pacaurtmp-maroco/yaourt/pkg/usr/share/man/man8
# Locales
test -x /usr/bin/msgfmt && for file in po/*/*.po; \
do \
package=$(echo $file | /bin/sed -e 's#po/\([^/]\+\).*#\1#'); \
lang=$(echo $file | /bin/sed -e 's#.*/\([^/]\+\).po#\1#'); \
/bin/install -d /tmp/pacaurtmp-maroco/yaourt/pkg/usr/share/locale/$lang/LC_MESSAGES; \
/usr/bin/msgfmt -o /tmp/pacaurtmp-maroco/yaourt/pkg/usr/share/locale/$lang/LC_MESSAGES/$package.mo $file; \
done
==> Tidying install...
-> Purging other files...
-> Compressing man and info pages...
-> Stripping unneeded symbols from binaries and libraries...
==> Creating package...
-> Generating .PKGINFO file...
-> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: yaourt 0.10.2-1 (Wed Nov 2 22:20:08 CET 2011)
==> Installing package yaourt with pacman-color -U...
resolving dependencies...
looking for inter-conflicts...
Targets (1): yaourt-0.10.2-1 [0.04 MB]
Total Download Size: 0.00 MB
Total Installed Size: 0.22 MB
Proceed with installation? [Y/n] (1/1) checking package integrity [----------------------] 100%
(1/1) checking for file conflicts [----------------------] 100%
(1/1) checking available disk space [----------------------] 100%
(1/1) installing yaourt [----------------------] 100%
Optional dependencies for yaourt
aurvote: vote for favorite packages from AUR for inclusion in [community]
customizepkg: automatically modify PKGBUILD during install/upgrade
rsync: retrieve PKGBUILD from official repositories
pacman-color: fully colorized output
:: Build directory cleaned
[maroco@MBlack ~]$ yaourt -h
Usage: yaourt <operation> [...]
operations:
yaourt (search pattern|package file)
yaourt {-h --help}
yaourt {-V --version}
yaourt {-Q --query} [options] [package(s)]
yaourt {-R --remove} [options] <package(s)>
yaourt {-S --sync} [options] [package(s)]
yaourt {-U --upgrade} [options] <package(s)>
yaourt {-C --clean} [options]
yaourt {-B --backup} [save directory|restore file]
yaourt {-G --getpkgbuild} [options] <package(s)>
yaourt {--stats}
[maroco@MBlack ~]$ Cheers :)
Thanks again for this great program - even if you didn't invent anything new you put together the best bits and pieces and arranged them the right was
Cheers
Maroco
Offline
MAroco > Pff, that is a weird one. Probably related to your German locale :]
Might I ask you to pastebin output of "bash -x pacaur -S yaourt" and "bash -x pacaur -Sy yaourt" so I can have additional debug information?
Edit: I might have found the reason it doesn't work on your machine: your fallback setting is set to false. When fallback is turned on "false", you have to pass the --aur option explicitly in order to make it working. Try "pacaur -Sya yaourt", and let me know if that works.
Last edited by Spyhawk (2011-11-03 15:10:46)
Offline
Hi Spyhawk,
yippiehjajeah seems that was is.
Tried with -Sya and it worked so I changed the setting in the config to true and now -Sy also works as expected. Thanks a lot and very sorry for keeping you busy just cause I'm apparently to dumb to understand config options. I'm quite embarassed...
In the first post you wrote "Additionally, pacaur wraps pacman and extend its function to the AUR (ie, pacaur -Ss will search the repo, then the AUR if necessary). This behavior can be disabled with the fallback variable."
I understood this as "normal behaviour is to extend commands to AUR" and to disable this behaviour one has to enable the config option i.e. set it to true. But since I wanted the normal behaviour I set the option to false... Perhaps I should stop thinking around 3 corners and just assume the easy explanation "fallback to AUR = true" means what it says...:)
Just for completeness: independant of this config option "bash -x pacaur -S yaourt" in any case seems to produce the same output ending in "target not found" (only in German as the LANG is missing.) Same goes for -Sy.
Was that what you expected? I assumed with fallback=true the "target not found" should vanish but it doesn't. But with fallback=true the installation works, with fallback=no not, so obviously the option is respected.
with fallback=true:
[maroco@MBlack ~]$ bash -x pacaur -S yaourt
+ name=pacaur
+ version=2.3.11
+ tmpDir=/tmp/pacaurtmp-maroco
+ [[ -d /tmp/pacaurtmp-maroco ]]
+ rm -rf /tmp/pacaurtmp-maroco
+ mkdir -p /tmp/pacaurtmp-maroco
+ buildDir=/tmp/pacaurtmp-maroco
+ editor=leafpad
+ color=false
+ clean=true
+ fallback=true
+ carchmagic=false
+ source /etc/pacaur.conf
++ buildDir=/tmp/pacaurtmp-maroco
++ editor=leafpad
++ color=true
++ clean=true
++ fallback=true
++ carchmagic=true
+ [[ -r /home/maroco/.config/pacaur/config ]]
+ true
+ pacmanBin=pacman-color
+ cower='cower --color=always'
++ tput sgr0
+ reset=''
+ colorR='\e[1;31m'
+ colorG='\e[1;32m'
+ colorY='\e[1;33m'
+ colorB='\e[1;34m'
+ colorM='\e[1;35m'
+ colorC='\e[1;36m'
+ colorW='\e[1;39m'
+ [[ -n -S ]]
+ pkgs=()
+ count=0
+ [[ -n -S ]]
+ case "$1" in
+ option=sync
+ installpkg=true
+ force=true
+ edit=true
+ shift
+ [[ -n yaourt ]]
+ case "$1" in
+ pkgs+=("$1")
+ shift
+ [[ -n '' ]]
+ [[ ! -n leafpad ]]
+ [[ ! -d /tmp/pacaurtmp-maroco ]]
+ [[ ! -f /usr/bin/pacman-color ]]
+ [[ ! -n '' ]]
+ [[ ! -n sync ]]
+ [[ -n '' ]]
+ [[ '' = search ]]
+ [[ '' = info ]]
+ [[ '' = download ]]
+ [[ '' = makepkg ]]
+ [[ '' = check ]]
+ [[ sync = search ]]
+ [[ sync = sync ]]
+ [[ ! -n yaourt ]]
+ ClassifyPkgs yaourt
+ [[ true = true ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ [[ ! -n '' ]]
+ [[ ! -n '' ]]
+ GetIgnoredGrps
+ ignoredgrps+=($(grep '^ *IgnoreGroup' '/etc/pacman.conf' | cut -d '=' -f 2-))
++ grep '^ *IgnoreGroup' /etc/pacman.conf
++ cut -d = -f 2-
+ for i in '${pkgs[@]}'
+ [[ =~ yaourt ]]
++ pacman-color -S --print yaourt
++ grep -v error:
+ [[ -z Fehler: Ziel nicht gefunden: yaourt ]]
+ repopkgs+=("$i")
+ [[ -n yaourt ]]
+ [[ -n '' ]]
+ [[ -n true ]]
+ runasroot pacman-color -S yaourt
+ [[ 1000 -eq 0 ]]
+ sudo -l pacman-color -S yaourt
+ sudo pacman-color -S yaourt
Passwort:
Fehler: Ziel nicht gefunden: yaourt
+ [[ ! -n true ]]
+ [[ -n '' ]]
+ exit
[maroco@MBlack ~]$
AND with fallback=false:
[maroco@MBlack ~]$ bash -x pacaur -S yaourt
+ name=pacaur
+ version=2.3.11
+ tmpDir=/tmp/pacaurtmp-maroco
+ [[ -d /tmp/pacaurtmp-maroco ]]
+ rm -rf /tmp/pacaurtmp-maroco
+ mkdir -p /tmp/pacaurtmp-maroco
+ buildDir=/tmp/pacaurtmp-maroco
+ editor=leafpad
+ color=false
+ clean=true
+ fallback=true
+ carchmagic=false
+ source /etc/pacaur.conf
++ buildDir=/tmp/pacaurtmp-maroco
++ editor=leafpad
++ color=true
++ clean=true
++ fallback=false
++ carchmagic=true
+ [[ -r /home/maroco/.config/pacaur/config ]]
+ true
+ pacmanBin=pacman-color
+ cower='cower --color=always'
++ tput sgr0
+ reset=''
+ colorR='\e[1;31m'
+ colorG='\e[1;32m'
+ colorY='\e[1;33m'
+ colorB='\e[1;34m'
+ colorM='\e[1;35m'
+ colorC='\e[1;36m'
+ colorW='\e[1;39m'
+ [[ -n -S ]]
+ pkgs=()
+ count=0
+ [[ -n -S ]]
+ case "$1" in
+ option=sync
+ installpkg=true
+ force=true
+ edit=true
+ shift
+ [[ -n yaourt ]]
+ case "$1" in
+ pkgs+=("$1")
+ shift
+ [[ -n '' ]]
+ [[ ! -n leafpad ]]
+ [[ ! -d /tmp/pacaurtmp-maroco ]]
+ [[ ! -f /usr/bin/pacman-color ]]
+ [[ ! -n '' ]]
+ [[ ! -n sync ]]
+ [[ -n '' ]]
+ [[ '' = search ]]
+ [[ '' = info ]]
+ [[ '' = download ]]
+ [[ '' = makepkg ]]
+ [[ '' = check ]]
+ [[ sync = search ]]
+ [[ sync = sync ]]
+ [[ ! -n yaourt ]]
+ ClassifyPkgs yaourt
+ [[ false = true ]]
+ [[ ! -n '' ]]
+ repopkgs=(${pkgs[@]})
+ [[ -n yaourt ]]
+ [[ -n '' ]]
+ [[ -n true ]]
+ runasroot pacman-color -S yaourt
+ [[ 1000 -eq 0 ]]
+ sudo -l pacman-color -S yaourt
+ sudo pacman-color -S yaourt
Fehler: Ziel nicht gefunden: yaourt
+ [[ ! -n true ]]
+ [[ -n '' ]]
+ exit
[maroco@MBlack ~]$
So thanks again, your help and dedication is very much appreciated!
Cheers
Maroco
Offline
MAroco > Glad it works for you :]
Let me know if I could improve the man page in any way - after all, English isn't my native language either.
Also, I guess the debug output fails because of the German locale:
++ grep -v error:
+ [[ -z Fehler: Ziel nicht gefunden: yaourt ]]
Although error = Fehler, pacaur is too dumb to understand it - and the conditional test fails here.
Unfortunately, I don't see an easy way to make pacaur working with any user locale (maybe gettext?). I don't plan to implement this feature myself, nor do I want to teach pacaur German... :] Instead, I'll look for a way to force English output for all, regardless of the chosen locale. In the meantime, use a bash alias. You also might want to alias pacman/pacman-color the same way:
alias pacaur='LANG="en_US.UTF-8" pacaur'
alias pacman-color='LANG="en_US.UTF-8" pacman-color'
alias pacman='LANG="en_US.UTF-8" pacman'
LC_ALL=C might work too.
Last edited by Spyhawk (2011-11-03 20:58:36)
Offline
Well actually I don't see any need to change the main page as it was me overcomplicating things. Don't grow grey hairs just cause I'm silly sometimes... And I agree absolutely about the localiztion. The alias in .bashrc is the perfect solution, pacaur should manage packages not become a multilingualistic
And thanks for mentioning pacman-color in the example, I thought of pacman but missed that. Aahh me an the details again... oh boy. But at least now I know where the german output came from after all, as I have the colors activated. Keep up this great project!!
Best wishes
Maroco
Offline
sudo as dependency is new, right? What is the reason behind this move?
zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)
Offline
SanskriFritz: Can be that sudo is used for pacaur to install packages (or another pacman operation that requires root permission) and wasn't listed before as a dependency. Just saying
Last edited by ethail (2011-11-07 10:29:57)
Best Testing Repo Warning: [testing] means it can eat you hamster, catch fire and you should keep it away from children. And I'm serious here, it's not an April 1st joke.
Offline
SanskritFritz > You might have missed #156.
Offline
I did miss that, thanks.
zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)
Offline
hi I know it might have been answered at sometime but I have no idea why after 3 months of not updating I get the following errors:
M|$├1─> sudo pacaur -Syu
Password:
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
there is nothing to do
:: Starting AUR upgrade...
:: [backintime-kde4]: Couldn't resolve host name
:: [avast]: Couldn't resolve host name
:: [burg-themes]: Couldn't resolve host name
:: [burg-bzr]: Couldn't resolve host name
:: [boxee]: Couldn't resolve host name
:: [chromium-browser-bin]: Couldn't resolve host name
:: [burg-themes-extras]: Couldn't resolve host name
:: [cloog-ppl]: Couldn't resolve host name
:: [bitdefender]: Couldn't resolve host name
:: [clamtk]: Couldn't resolve host name
:: [clyde-git]: Couldn't resolve host name
:: [conky-lua]: Couldn't resolve host name
:: [couchpotato-git]: Couldn't resolve host name
:: [cower]: Couldn't resolve host name
:: [customizable-weather-plasmoid]: Couldn't resolve host name
:: [db4.5]: Couldn't resolve host name
:: [dropbox]: Couldn't resolve host name
:: [esound]: Couldn't resolve host name
:: [fahmon]: Couldn't resolve host name
:: [foldingathome]: Couldn't resolve host name
:: [foremost]: Couldn't resolve host name
:: [fpm2]: Couldn't resolve host name
:: [gen-init-cpio]: Couldn't resolve host name
:: [google-talkplugin]: Couldn't resolve host name
:: [hal]: Couldn't resolve host name
:: [hal-info]: Couldn't resolve host name
:: [huludesktop]: Couldn't resolve host name
:: [jdownloader]: Couldn't resolve host name
:: [json-glib-git]: Couldn't resolve host name
:: [kdeplasma-addons-applets-socketsentry]: Couldn't resolve host name
:: [kdeplasma-addons-applets-veromix]: Couldn't resolve host name
:: [kwooty]: Couldn't resolve host name
:: [lastpass]: Couldn't resolve host name
:: [libjpeg6]: Couldn't resolve host name
:: [libkeybinder]: Couldn't resolve host name
:: [libpng12]: Couldn't resolve host name
:: [lua-lzlib]: Couldn't resolve host name
:: [lua-yajl-git]: Couldn't resolve host name
:: [mediatomb]: Couldn't resolve host name
:: [midori-git]: Couldn't resolve host name
:: [nevernote]: Couldn't resolve host name
:: [openssl-compatibility]: Couldn't resolve host name
:: [os-prober]: Couldn't resolve host name
:: [pacaur]: Couldn't resolve host name
:: [package-query]: Couldn't resolve host name
:: [packer]: Couldn't resolve host name
:: [pacman-color]: Couldn't resolve host name
:: [paktahn]: Couldn't resolve host name
:: [par2cmdline]: Couldn't resolve host name
:: [perl-file-find-rule]: Couldn't resolve host name
:: [perl-number-compare]: Couldn't resolve host name
:: [perl-text-glob]: Couldn't resolve host name
:: [pms]: Couldn't resolve host name
:: [python24]: Couldn't resolve host name
:: [python-cheetah]: Couldn't resolve host name
:: [python-yenc]: Couldn't resolve host name
:: [sabnzbd]: Couldn't resolve host name
:: [sickbeard-git]: Couldn't resolve host name
:: [silc-toolkit]: Couldn't resolve host name
:: [tcp_wrappers]: Couldn't resolve host name
:: [teamviewer]: Couldn't resolve host name
:: [tixati]: Couldn't resolve host name
:: [toluapp]: Couldn't resolve host name
:: [ttf-ms-fonts]: Couldn't resolve host name
:: [ttf-openlogos]: Couldn't resolve host name
:: [ttf-pizzadude-bullets]: Couldn't resolve host name
:: [ttf-stylebats]: Couldn't resolve host name
:: [wicd-kde-git]: Couldn't resolve host name
:: [wakka]: Couldn't resolve host name
:: [xdg-su]: Couldn't resolve host name
:: [yaourt]: Couldn't resolve host name
:: [yapan]: Couldn't resolve host name
:: [yawp-weather-plasmoid]: Couldn't resolve host name
there is nothing to do
anyone have any ideas?? thanks.
did something happen to aurs address??? like did it change? I dont see any info anywhere on it. Also if it did how would I modify where it looks for packages?? thanks.
Last edited by splippity (2011-11-27 19:09:53)
Offline
Hi I am pretty new to Arch Linux. I am planning to install an AUR helper. After a lot of reading I have come to a conclusion that pacaur is the best option for my needs of an efficient, fast, powerful and easy to use AUR helper. Before this I have only used clyde but have now removed it as its development has stopped and bugs are not getting fixed.
Before Installing pacaur I had few questions:
1) I have already got on my system many manually installed (makepkg method) AUR pacakges. When I install pacaur will I be able to use it to upgrade them. If yes what command is the most suitable one for the upgrade of already installed AUR packages.
2) I intend to use pacaur only for AUR packages and pacman for other packages. Is this approach ok with pacaur. Do pacman and pacaur share package cache and repository configuration.
3) Do we have any mini how to for users like me who have primarily only used pacman and not very familiar with arch package management.
I am asking these questions because I want to take all possible precautions as pacaur is a package manager as opposed to a normal package and it takes lot of time to install and configure an arch system to ones liking.
I am sorry for being dumb.
Offline
1. pacaur -u
2. Yes that is ok.
3. pacaur -h, You can also look on the first post for all the available flags.
Offline
[...] Do pacman and pacaur share package cache and repository configuration.
[...]
I am sorry for being dumb.
Firstly, don't be sorry, or believe you're being dumb; it just takes some initial research to get to understanding new things propperly in the beginning...
Anyway, I would just like to expand on one of your points that was unanswered...
I'm pretty sure(I use my own "aur-helper" zsh functions) that pacaur honors /etc/makepkg.conf for defining where you want your packages cached(well, it's not actually that pacaur "honers", but rather that pacaur wraps makepkg), and by default that's just in pwd(current dir), whereas pacman by default stores it's cache in var/cache/pacman/pkg...
You can configure both in /etc/{makepkg,pacman}.conf...
On the question about if pacaur shares repos with pacman, then the answer is that pacaur wraps pacman, meaning every pacman operation is sent to pacman directly by pacaur, and so it's /etc/pacman.d/mirrorlist which controls which mirrors pacman uses(also through pacaur!)...
The aur dosen't use mirrros in the same way as the pacman repos, but rather uses a single static rpc.php interface, and you don't have to configure anything for that to work in pacaur...
Lastly, as allready been stated, read up on the man of pacaur, and also if you haven't allready, the arch wiki articles about pacman, makepkg and the aur...
Btw, remember --devel, if you want to update devel packages, as else they won't be updated before the pkgbuild gets updated
Offline
- If I do "pac -Sy mc" mc installs normally
I know I'm a little late to the party but in case MAroco still reads this thread I'd like to point this out -
https://bbs.archlinux.org/viewtopic.php … 61#p802661 - you REALLY shouldn't be doing -Sy, and I'm somewhat surprised Spyhawk went along with changing the behaviour of pacaur.
In a perfect world -Sy would simply fail without an additional option like rm's --no-preserve-root, but clearly The Arch Way precludes dealing with problematic extreme-edge-case system destroyers in ways other than a phrik command.
Offline
Thank you very much mhertz for your very informative reply. It really cleared some concepts. Earlier I was always afraid of using AUR helpers thinking they may mess up my system. Now I understand that I can have my chosen package and source dirs for AUR. I only need to to change $PKGDEST and $PKGSRC variable in /etc/makepkg.conf and pacaur will install the AUR packages as if they were first built by makepkg and then installed by pacman (except for automation). Earlier I used to download an AUR tarball in to a dedicated dir name aurbuilds and cd into the specific package's extracted directory and run makepkg. The makepkg used to then build package and store the resultant .xz file and sources in the same directory (as you said makepkg default is PWD). I then used to run pacman -U command on the resulting binary. Now, as I understand, pacaur will download from aur, give the command to makepkg to build the binary and then transfer the command to packman to install it. Am I right?
Also for installation and upgrade packages in core, extra and community pacaur will straight away transfer the command to pacman to do the stuff and and store the package in var/cache/pacman/pkg. Isn't it? In this case I won't need to use pacman at all. One tool to handle both repositories and AUR with respective pacages getting stored at its intended places.
Regarding the upgrade of existing aur pakages I was told by anonymous_user (thanks to him too) that I need to run pacaur -u. Is it it a global command like -Syu for AUR packages or do in need to upgrade existing packages one by one using pacaur -u aur-package-name.
Offline
Thank you very much mhertz for your very informative reply.
You're most welcome, mate.
Now, as I understand, pacaur will download from aur, give the command to makepkg to build the binary and then transfer the command to packman to install it. Am I right?
Exactly! (Allthough, to be totally precise, then I think that pacaur dosen't bother running pacman seperatelly after makepkg has built the package, since makepkg supports an -i flag(for 'install'), which does the same, and which I guess pacaur uses(I haven't looked at the code)i.e. makepkg calls pacman automatically to install the package, after it's been built, if using e.g. makepkg -si)
Also for installation and upgrade packages in core, extra and community pacaur will straight away transfer the command to pacman to do the stuff and and store the package in var/cache/pacman/pkg. Isn't it?
Exactly!
Regarding the upgrade of existing aur pakages I was told by anonymous_user (thanks to him too) that I need to run pacaur -u. Is it it a global command like -Syu for AUR packages or do in need to upgrade existing packages one by one using pacaur -u aur-package-name.
You can run -u, which updates _all_ aur packages, and if you specify additional package-names, then _only_ those packages gets updated.
However, If you want to upgrade all repo packages + aur packages, then it's just -Syu.
Note, I don't and have never used pacaur, and so I have gotten this from simply reading the pacaur man page...
Edit: .. And remember --devel if you have dev-snapshots installed...
Last edited by mhertz (2011-11-29 16:27:27)
Offline
Thanks mhertz. I am now ready to install pacaur.
Offline