How do I install co-dependent AUR packages?

I downloaded the Bumblebee tarball using lynx.
lynx https://aur.archlinux.org/packages/bumblebee/
Then I extracted it.
# tar -xvzf bumblebee.tar.gz
Then I went to the appropriate directory.
# cd bumblebee
Then I ran makepkg.
# makepkg -s
It returned the following error.
error: target not found: virtualgl
==> ERROR: 'pacman' failed to install missing dependencies.
I want to use primus instead of virtualgl. So, I try to install it.
lynx https://aur.archlinux.org/packages/primus-git/
Extracted it...
# tar -xvzf primus-git.tar.gz
cd to directory
# cd primus-git
makepkg
# makepkg -s
Another error.
error: target not found: bumblebee
==> ERROR: 'pacman' failed to install missing dependencies.
What do?
** EDIT - I changed the title and content to reflect the actual problem. **
Moderator note: Please never do this! If you change the proper of your first post the whole thread becomes useless. Even if you made some really silly mistakes (all of us do sometimes) leave the thread intact and put a note in a final post why you think so and what you have done. It will help others to not stumble in this same trap again.
Forum Etiquette
Last edited by bernarcher (2012-12-16 05:04:40)

WonderWoofy wrote:
doug piston wrote:
You can't use pacman for packages in the AUR.
https://wiki.archlinux.org/index.php/Ar … Repository
Seenig that the OP doesn't seem to understand the difference between the AUR and official repos, I would just like to clarify this comment for Doug Piston. In reality, you still end up using pacman for packages in the AUR. Though these packages are not yet built, so you have to use the PKGBUILD/tarball from the AUR along with makepkg to produce the package. Then you ultimately install it with pacman.
I will have to do further research on this topic. Thank you for the pointers. I appreciate your help.

Similar Messages

[Solved] Cant install\compile certain AUR packages

This is a brand new 32-bit build on my laptop. Everything is working great, but for some reason I cant get some AUR packages. I have Yaourt, pacman-color, and slock installed from AUR and working fine, but I cant get mpd-git or mplayer-svn installed? I have gcc, python installed and tried both root and user accounts. Not sure what is missing. This is a new dual core laptop so not sure why I am getting the CPU errors below?
This is for mplayer-svn:
==> SVN checkout done or server timeout, updating build dir
==> Applying disabled-features patch...
/var/abs/local/yaourtbuild/mplayer-svn/./PKGBUILD: line 56: patch: command not found
Detected operating system: Linux
Detected host architecture: i386
Checking for host cc ... gcc
Checking for cross compilation ... yes
./configure: line 1605: gcc: command not found
./configure: line 1610: gcc: command not found
Checking for CPU vendor ... GenuineIntel (6:15:11)
Checking for CPU type ... Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz
Checking for kernel support of mmx ... failed
It seems that your kernel does not correctly support mmx.
To use mmx extensions in MPlayer, you have to upgrade/recompile your kernel!
Checking for kernel support of mmxext ... failed
It seems that your kernel does not correctly support mmxext.
To use mmxext extensions in MPlayer, you have to upgrade/recompile your kernel!
Checking for kernel support of sse ... failed
It seems that your kernel does not correctly support sse.
To use sse extensions in MPlayer, you have to upgrade/recompile your kernel!
Checking for kernel support of sse2 ... failed
It seems that your kernel does not correctly support sse2.
To use sse2 extensions in MPlayer, you have to upgrade/recompile your kernel!
Checking for kernel support of ssse3 ... failed
It seems that your kernel does not correctly support ssse3.
To use ssse3 extensions in MPlayer, you have to upgrade/recompile your kernel!
Checking for kernel support of cmov ... failed
It seems that your kernel does not correctly support cmov.
To use cmov extensions in MPlayer, you have to upgrade/recompile your kernel!
Checking for mtrr support ... yes
Checking for GCC & CPU optimization abilities ... CPU optimization disabled. CPU not recognized or your compiler is too old.
error
Checking for byte order ... failed to autodetect byte order, defaulting to little-endian
Checking for extern symbol prefix ...
Error: Symbol mangling check failed.
Check "configure.log" if you do not understand why it failed.
==> ERROR: Build Failed.
Aborting...
Error: Makepkg was unable to build mplayer-svn package.
This is for mpd-git:
Looks like I need to set the path for gcc in here, but not sure how?
configure: error: in `/tmp/yaourt-tmp-banshee/aur-mpd-git/mpd-git/src/mpd-build':
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details.
make: *** No targets specified and no makefile found. Stop.
==> ERROR: Build Failed.
Aborting...
Error: Makepkg was unable to build mpd-git package.
Last edited by banshee28 (2009-09-03 04:15:43)

Allan wrote:
You need to install the base-devel group (pacman -S base-devel).
This is a bit weird though....
Checking for cross compilation ... yes
hopefully it goes away!
Ah, I see all the apps in this group now! Not sure how I missed this? Was this in the wiki somwhere??
Anyways,its getting further along now ....

(SOLVED) How do I remove dependencies of AUR packages?

I rather not use sudo and thereof I issue a 'makepkg' instead of a 'makepkg -s' and install dependencies manually. I wonder though what happens when I issue a 'pacman -Rns' to remove an AUR package. Pacman doesn't seem to remove the dependencies. Do I need to issue a 'makepkg -s' in order to automagically remove dependencies with 'pacman -Rns'? What about AUR packages that have other AUR packages as dependency and therefor cannot be installed with 'makepkg -s'?
Last edited by Kasumi_Ninja (2010-01-03 13:39:51)

I haven't fully thought this through but I would like --asdeps to take an argument that specifies 'to what'.
For example: wicd has an optional dependency for notifcation-daemon, which I want. I would like to be able to
pacman -S --asdeps='wicd' notification-daemon
This would then modify wicd to depend on notification-daemon. This isn't perfect since it is an optional and not a real dependency. The only real problem I can think of is if I want to remove notification-daemon. However pacman should see 'notification-daemon' listed under dependencies AND optional-dependencies, so it could give a warning and an option to go ahead anyway. If it goes ahead, pacman reverts wicd to nolonger depend notification-daemon. I feel like it should be pretty easy to add this to pacman.
I feel like something like yaourt would be responsible for asking if I want to install optional dependencies. So when I install something with yaourt it asks me about each optional dependency and if I want it.
Just my two cents.

How do I install upgrades of CS4 package and bypass the installation of older version(s) first?

Hi,
I would like to install the CS4 designing premium upgrade to my new iMac. It's using the new 10.6 OS. My previous Mac 'past away' over three years ago. How do I install upgrades and bypass the installation of older version(s) first? I do owned the full version of each individual software from CS4 designing premium in the past, including the ones Adobe acquired from Macromedia. I also bought and used all the sequential upgrades of each individual software as they came out. However, my purchase of CS3 package came right after my Mac died, so I never register that package's softwares.
Thank you,
George

This forum is for discussing the functionality of these forums, not for discussing other Adobe products and services. I think the place where you should post your question is either in the Create Suites forum:
http://forums.adobe.com/community/creativesuites/version_cue_macintosh

[Solved] List AUR packages installed and only AUR packages.

Here's a good one. Thought this would be easy but thought it over and then looked around a bit and haven't found anything. There's might just be an easy way to do this that will make me *bonk* my head in the morning but I haven't found it yet. I'm looking to be able to just list the packages I have installed from AUR and not any that I have gotten from the official repos. I've checked out some utilities in AUR (like AURcheck) but as far as I can tell they just look for AUR updates. Anyone know of a way to do this?
Last edited by Gen2ly (2009-10-30 14:32:22)

I just got to reinstalling and this was a lifesaver - it worked great. Thank for the help, brisbin, ghost, Allan...
@Ghost, I would have used packup but I had a couple downgraded packages and I wanted to be able to troubleshoot it.
The tip about the grep -v doing 'shortnameplus' was a good tip, Profjim. I hadn't read this last post before and during the reinstall I was a bit surprised nvidia wasn't installed so... all is good now.
I created a script to be able to create the backup list and restores from it simliar to ghosts and am able to run it in cron job. Probably not a big deal, but... phhht. Here it is for anyone that can use it:
#!/bin/bash
# pacbac - Create and restore from list all installed packages
# Package list locations (official and local)
pkglsoff=/opt/backup/pc-emach/arch-pkglist-official
pkglsloc=/opt/backup/pc-emach/arch-pkglist-local
# Exclude packages
excldoff=()
excldloc=()
# Use filename as program name
prog=${0##*/}
# Text color variables
bldblu='\e[1;34m' # blue
bldred='\e[1;31m' # red
bldwht='\e[1;37m' # white
txtcyn='\e[0;36m' # cyan
txtund=$(tput sgr 0 1) # underline
txtrst='\e[0m' # text reset
info=${bldwht}*${txtrst}
pass=${bldblu}*${txtrst}
warn=${bldred}!${txtrst}
# If restoring, be sure yaourt is installed
if [[ "$1" == 'r' ]] && [[ -z $(pacman -Qs yaourt) ]]; then
echo ""
echo -e "$warn $prog requires ${txtund}}Yaourt${txtrst} to be installed."
echo -e " ${txtcyn}http://wiki.archlinux.org/index.php/Yaourt${txtrst}"
echo ""
exit
fi
case $1 in
b ) # Create list of official repository packages (core, extra, community)
echo -e "$info Creating list of official (core/extra/community packages) packages installed."
# Create list, remove local, base
pacman -Qqe | grep -vx "$(pacman -Qqg base)" | grep -vx "$(pacman -Qqm)" > "$pkglsoff"
# Create list of local packages (includes the AUR)
echo -e "$info Creating list of local (includes AUR) packages installed."
pacman -Qqm > "$pkglsloc"
echo -e "$pass Official package list saved to ${txtund}"$pkglsoff"${txtrst}"
echo -e "$pass Local package list saved to ${txtund}"$pkglsloc"${txtrst}" ;;
r ) # Update repository database, then restore packages from list
echo -e "$info Installing packages from lists"
sudo pacman -Sy
# use -f to overwrite conflicting files
sudo pacman -S --needed $(cat "$pkglsoff")
# Yaourt doesn't have --needed check
yaourt -S $(cat "$pkglsloc" | grep -vx "$(pacman -Qqm)") ;;
* ) echo -e " pacbac b - build installed packages list. (dir:${txtund}"${pkglsoff%/*}"${txtrst})"
echo -e " pacbac r - restore installed packages from package list." ;;
esac
Last edited by Gen2ly (2009-10-31 14:16:55)

[Solved] How to include examples for an AUR package

Hi,
I read the wiki pages how to create packages for the AUR,
but I am not sure how to include examples which should be placed
in /usr/share/doc/<package>/examples/ after the package was installed.
Should all files be mentioned in the "sources" variable of the PKGBUILD
or is it better to copy them via the .install file?
Last edited by fana (2012-01-22 17:38:41)

fana wrote:Ah, I see. So a good way would be just providing a tarball with all the examples and add that tarball to the source array
Yup, I don't see how are these are examples different [1] from the other files.
[1] Well, apart from stuff like https://bugs.archlinux.org/task/25998 ;P

Cannot retrieve aur packages installed with yaourt

I accidently deleted /var/lib/pacman folder while attempting to solve my update issues (updating system after a long time) . I restored my local pacman database with the excellent guide in the wiki using /var/log/pacman.log http://wiki.archlinux.org/index.php/Pac … l_database. I was able to update and restore my system. However, yaourt is not listing my installed aur packages. I re-installed yaourt and tried packer as well but it is not able to find the aur packages I installed using yaourt earlier to my update ( It is able to install and list new aur packages) . I can run the old aur packages but I am not able to remove or list them. How can I list these lost aur packages or remove them completely? Is there a way to retrieve the database for aur packages installed with yaourt?
Thanks.

Hi karol,
Thanks for your response.
Executing pacman -Qm only lists aur packages which were installed after I accidently deleted /var/lib/pacman. I am not able to list those aur packages that I installed with yaourt prior to my /var/lib/pacman deletion. I am not sure how the accidental deletion and this issue is related, but I would like to delete these old aur packages. One example of such an aur package installed through yaourt (prior to blunder of /var/lib/pacman deletion ) was chromium-browser. I am able to run chromium-browser, but since this package is very old I would like to remove it. However, neither pacman nor yaourt is able to remove it.
# pacman -R chromium-browser
chromium-browser not found, searching for group...
error: 'chromium-browser': not found in local db
$ yaourt -R chromium-browser
You are not allowed to launch /usr/bin/pacman with sudo
Please enter root password
Password:
chromium-browser not found, searching for group...
error: 'chromium-browser': not found in local db
However chromium-browser is present on my system and runs very well.
$ locate chromium-browser
/etc/chromium-browser
/etc/chromium-browser/default
/opt/chromium-browser
/opt/chromium-browser/chrome
/opt/chromium-browser/chrome-wrapper
/opt/chromium-browser/chrome.pak
/opt/chromium-browser/chrome_sandbox
/opt/chromium-browser/libffmpegsumo.so
/opt/chromium-browser/locales
/opt/chromium-browser/product_logo_48.png
/opt/chromium-browser/resources
/opt/chromium-browser/xdg-settings
/opt/chromium-browser/locales/am.pak
/opt/chromium-browser/locales/ar.pak
/opt/chromium-browser/locales/bg.pak
/opt/chromium-browser/locales/bn.pak
/opt/chromium-browser/locales/ca.pak
/opt/chromium-browser/locales/cs.pak
/opt/chromium-browser/locales/da.pak
/opt/chromium-browser/locales/de.pak
/opt/chromium-browser/locales/el.pak
/opt/chromium-browser/locales/en-GB.pak
/opt/chromium-browser/locales/en-US.pak
/opt/chromium-browser/locales/es-419.pak
/opt/chromium-browser/locales/es.pak
/opt/chromium-browser/locales/et.pak
/opt/chromium-browser/locales/fi.pak
/opt/chromium-browser/locales/fil.pak
/opt/chromium-browser/locales/fr.pak
/opt/chromium-browser/locales/gu.pak
/opt/chromium-browser/locales/he.pak
/opt/chromium-browser/locales/hi.pak
/opt/chromium-browser/locales/hr.pak
/opt/chromium-browser/locales/hu.pak
/opt/chromium-browser/locales/id.pak
/opt/chromium-browser/locales/it.pak
/opt/chromium-browser/locales/ja.pak
/opt/chromium-browser/locales/kn.pak
/opt/chromium-browser/locales/ko.pak
/opt/chromium-browser/locales/lt.pak
/opt/chromium-browser/locales/lv.pak
/opt/chromium-browser/locales/ml.pak
/opt/chromium-browser/locales/mr.pak
/opt/chromium-browser/locales/nb.pak
/opt/chromium-browser/locales/nl.pak
/opt/chromium-browser/locales/or.pak
/opt/chromium-browser/locales/pl.pak
/opt/chromium-browser/locales/pt-BR.pak
/opt/chromium-browser/locales/pt-PT.pak
/opt/chromium-browser/locales/ro.pak
/opt/chromium-browser/locales/ru.pak
/opt/chromium-browser/locales/sk.pak
/opt/chromium-browser/locales/sl.pak
/opt/chromium-browser/locales/sr.pak
/opt/chromium-browser/locales/sv.pak
/opt/chromium-browser/locales/sw.pak
/opt/chromium-browser/locales/ta.pak
/opt/chromium-browser/locales/te.pak
/opt/chromium-browser/locales/th.pak
/opt/chromium-browser/locales/tr.pak
/opt/chromium-browser/locales/uk.pak
/opt/chromium-browser/locales/vi.pak
/opt/chromium-browser/locales/zh-CN.pak
/opt/chromium-browser/locales/zh-TW.pak
/opt/chromium-browser/resources/inspector
/opt/chromium-browser/resources/inspector/Images
/opt/chromium-browser/resources/inspector/devtools.css
/opt/chromium-browser/resources/inspector/devtools.html
/opt/chromium-browser/resources/inspector/devtools.js
/opt/chromium-browser/resources/inspector/inspector.css
/opt/chromium-browser/resources/inspector/inspector.html
/opt/chromium-browser/resources/inspector/inspectorSyntaxHighlight.css
/opt/chromium-browser/resources/inspector/Images/back.png
/opt/chromium-browser/resources/inspector/Images/checker.png
/opt/chromium-browser/resources/inspector/Images/clearConsoleButtonGlyph.png
/opt/chromium-browser/resources/inspector/Images/closeButtons.png
/opt/chromium-browser/resources/inspector/Images/consoleButtonGlyph.png
/opt/chromium-browser/resources/inspector/Images/consoleIcon.png
/opt/chromium-browser/resources/inspector/Images/cookie.png
/opt/chromium-browser/resources/inspector/Images/database.png
/opt/chromium-browser/resources/inspector/Images/databaseTable.png
/opt/chromium-browser/resources/inspector/Images/debuggerContinue.png
/opt/chromium-browser/resources/inspector/Images/debuggerPause.png
/opt/chromium-browser/resources/inspector/Images/debuggerStepInto.png
/opt/chromium-browser/resources/inspector/Images/debuggerStepOut.png
/opt/chromium-browser/resources/inspector/Images/debuggerStepOver.png
/opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallDown.png
/opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallDownBlack.png
/opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallDownWhite.png
/opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallRight.png
/opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallRightBlack.png
/opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallRightDown.png
/opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallRightDownBlack.png
/opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallRightDownWhite.png
/opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallRightWhite.png
/opt/chromium-browser/resources/inspector/Images/dockButtonGlyph.png
/opt/chromium-browser/resources/inspector/Images/elementsIcon.png
/opt/chromium-browser/resources/inspector/Images/enableOutlineButtonGlyph.png
/opt/chromium-browser/resources/inspector/Images/enableSolidButtonGlyph.png
/opt/chromium-browser/resources/inspector/Images/errorIcon.png
/opt/chromium-browser/resources/inspector/Images/errorMediumIcon.png
/opt/chromium-browser/resources/inspector/Images/errorRedDot.png
/opt/chromium-browser/resources/inspector/Images/excludeButtonGlyph.png
/opt/chromium-browser/resources/inspector/Images/focusButtonGlyph.png
/opt/chromium-browser/resources/inspector/Images/forward.png
/opt/chromium-browser/resources/inspector/Images/glossyHeader.png
/opt/chromium-browser/resources/inspector/Images/glossyHeaderPressed.png
/opt/chromium-browser/resources/inspector/Images/glossyHeaderSelected.png
/opt/chromium-browser/resources/inspector/Images/glossyHeaderSelectedPressed.png
/opt/chromium-browser/resources/inspector/Images/goArrow.png
/opt/chromium-browser/resources/inspector/Images/graphLabelCalloutLeft.png
/opt/chromium-browser/resources/inspector/Images/graphLabelCalloutRight.png
/opt/chromium-browser/resources/inspector/Images/grayConnectorPoint.png
/opt/chromium-browser/resources/inspector/Images/largerResourcesButtonGlyph.png
/opt/chromium-browser/resources/inspector/Images/localStorage.png
/opt/chromium-browser/resources/inspector/Images/nodeSearchButtonGlyph.png
/opt/chromium-browser/resources/inspector/Images/paneBottomGrow.png
/opt/chromium-browser/resources/inspector/Images/paneBottomGrowActive.png
/opt/chromium-browser/resources/inspector/Images/paneGrowHandleLine.png
/opt/chromium-browser/resources/inspector/Images/paneSettingsButtons.png
/opt/chromium-browser/resources/inspector/Images/pauseOnExceptionButtonGlyph.png
/opt/chromium-browser/resources/inspector/Images/percentButtonGlyph.png
/opt/chromium-browser/resources/inspector/Images/profileGroupIcon.png
/opt/chromium-browser/resources/inspector/Images/profileIcon.png
/opt/chromium-browser/resources/inspector/Images/profileSmallIcon.png
/opt/chromium-browser/resources/inspector/Images/profilesIcon.png
/opt/chromium-browser/resources/inspector/Images/profilesSilhouette.png
/opt/chromium-browser/resources/inspector/Images/radioDot.png
/opt/chromium-browser/resources/inspector/Images/recordButtonGlyph.png
/opt/chromium-browser/resources/inspector/Images/recordToggledButtonGlyph.png
/opt/chromium-browser/resources/inspector/Images/reloadButtonGlyph.png
/opt/chromium-browser/resources/inspector/Images/resourceCSSIcon.png
/opt/chromium-browser/resources/inspector/Images/resourceDocumentIcon.png
/opt/chromium-browser/resources/inspector/Images/resourceDocumentIconSmall.png
/opt/chromium-browser/resources/inspector/Images/resourceJSIcon.png
/opt/chromium-browser/resources/inspector/Images/resourcePlainIcon.png
/opt/chromium-browser/resources/inspector/Images/resourcePlainIconSmall.png
/opt/chromium-browser/resources/inspector/Images/resourcesIcon.png
/opt/chromium-browser/resources/inspector/Images/resourcesSilhouette.png
/opt/chromium-browser/resources/inspector/Images/resourcesSizeGraphIcon.png
/opt/chromium-browser/resources/inspector/Images/resourcesTimeGraphIcon.png
/opt/chromium-browser/resources/inspector/Images/scriptsIcon.png
/opt/chromium-browser/resources/inspector/Images/scriptsSilhouette.png
/opt/chromium-browser/resources/inspector/Images/searchSmallBlue.png
/opt/chromium-browser/resources/inspector/Images/searchSmallBrightBlue.png
/opt/chromium-browser/resources/inspector/Images/searchSmallGray.png
/opt/chromium-browser/resources/inspector/Images/searchSmallWhite.png
/opt/chromium-browser/resources/inspector/Images/segment.png
/opt/chromium-browser/resources/inspector/Images/segmentChromium.png
/opt/chromium-browser/resources/inspector/Images/segmentEnd.png
/opt/chromium-browser/resources/inspector/Images/segmentHover.png
/opt/chromium-browser/resources/inspector/Images/segmentHoverChromium.png
/opt/chromium-browser/resources/inspector/Images/segmentHoverEnd.png
/opt/chromium-browser/resources/inspector/Images/segmentHoverEndChromium.png
/opt/chromium-browser/resources/inspector/Images/segmentSelected.png
/opt/chromium-browser/resources/inspector/Images/segmentSelectedChromium.png
/opt/chromium-browser/resources/inspector/Images/segmentSelectedEnd.png
/opt/chromium-browser/resources/inspector/Images/segmentSelectedEndChromium.png
/opt/chromium-browser/resources/inspector/Images/sessionStorage.png
/opt/chromium-browser/resources/inspector/Images/splitviewDimple.png
/opt/chromium-browser/resources/inspector/Images/splitviewDividerBackground.png
/opt/chromium-browser/resources/inspector/Images/statusbarBackground.png
/opt/chromium-browser/resources/inspector/Images/statusbarBackgroundChromium.png
/opt/chromium-browser/resources/inspector/Images/statusbarBottomBackground.png
/opt/chromium-browser/resources/inspector/Images/statusbarBottomBackgroundChromium.png
/opt/chromium-browser/resources/inspector/Images/statusbarButtons.png
/opt/chromium-browser/resources/inspector/Images/statusbarButtonsChromium.png
/opt/chromium-browser/resources/inspector/Images/statusbarMenuButton.png
/opt/chromium-browser/resources/inspector/Images/statusbarMenuButtonChromium.png
/opt/chromium-browser/resources/inspector/Images/statusbarMenuButtonSelected.png
/opt/chromium-browser/resources/inspector/Images/statusbarMenuButtonSelectedChromium.png
/opt/chromium-browser/resources/inspector/Images/statusbarResizerHorizontal.png
/opt/chromium-browser/resources/inspector/Images/statusbarResizerVertical.png
/opt/chromium-browser/resources/inspector/Images/storageIcon.png
/opt/chromium-browser/resources/inspector/Images/successGreenDot.png
/opt/chromium-browser/resources/inspector/Images/timelineBarBlue.png
/opt/chromium-browser/resources/inspector/Images/timelineBarGray.png
/opt/chromium-browser/resources/inspector/Images/timelineBarGreen.png
/opt/chromium-browser/resources/inspector/Images/timelineBarOrange.png
/opt/chromium-browser/resources/inspector/Images/timelineBarPurple.png
/opt/chromium-browser/resources/inspector/Images/timelineBarRed.png
/opt/chromium-browser/resources/inspector/Images/timelineBarYellow.png
/opt/chromium-browser/resources/inspector/Images/timelineCheckmarks.png
/opt/chromium-browser/resources/inspector/Images/timelineDots.png
/opt/chromium-browser/resources/inspector/Images/timelineHollowPillBlue.png
/opt/chromium-browser/resources/inspector/Images/timelineHollowPillGray.png
/opt/chromium-browser/resources/inspector/Images/timelineHollowPillGreen.png
/opt/chromium-browser/resources/inspector/Images/timelineHollowPillOrange.png
/opt/chromium-browser/resources/inspector/Images/timelineHollowPillPurple.png
/opt/chromium-browser/resources/inspector/Images/timelineHollowPillRed.png
/opt/chromium-browser/resources/inspector/Images/timelineHollowPillYellow.png
/opt/chromium-browser/resources/inspector/Images/timelineIcon.png
/opt/chromium-browser/resources/inspector/Images/timelinePillBlue.png
/opt/chromium-browser/resources/inspector/Images/timelinePillGray.png
/opt/chromium-browser/resources/inspector/Images/timelinePillGreen.png
/opt/chromium-browser/resources/inspector/Images/timelinePillOrange.png
/opt/chromium-browser/resources/inspector/Images/timelinePillPurple.png
/opt/chromium-browser/resources/inspector/Images/timelinePillRed.png
/opt/chromium-browser/resources/inspector/Images/timelinePillYellow.png
/opt/chromium-browser/resources/inspector/Images/tipBalloon.png
/opt/chromium-browser/resources/inspector/Images/tipBalloonBottom.png
/opt/chromium-browser/resources/inspector/Images/tipIcon.png
/opt/chromium-browser/resources/inspector/Images/tipIconPressed.png
/opt/chromium-browser/resources/inspector/Images/toolbarItemSelected.png
/opt/chromium-browser/resources/inspector/Images/treeDownTriangleBlack.png
/opt/chromium-browser/resources/inspector/Images/treeDownTriangleWhite.png
/opt/chromium-browser/resources/inspector/Images/treeRightTriangleBlack.png
/opt/chromium-browser/resources/inspector/Images/treeRightTriangleWhite.png
/opt/chromium-browser/resources/inspector/Images/treeUpTriangleBlack.png
/opt/chromium-browser/resources/inspector/Images/treeUpTriangleWhite.png
/opt/chromium-browser/resources/inspector/Images/undockButtonGlyph.png
/opt/chromium-browser/resources/inspector/Images/userInputIcon.png
/opt/chromium-browser/resources/inspector/Images/userInputPreviousIcon.png
/opt/chromium-browser/resources/inspector/Images/userInputResultIcon.png
/opt/chromium-browser/resources/inspector/Images/warningIcon.png
/opt/chromium-browser/resources/inspector/Images/warningMediumIcon.png
/opt/chromium-browser/resources/inspector/Images/warningOrangeDot.png
/opt/chromium-browser/resources/inspector/Images/warningsErrors.png
/opt/chromium-browser/resources/inspector/Images/whiteConnectorPoint.png
/usr/bin/chromium-browser
/usr/share/applications/chromium-browser.desktop
/usr/share/licenses/chromium-browser-bin
/usr/share/licenses/chromium-browser-bin/LICENSE.txt
/usr/share/man/man1/chromium-browser.1.gz
/usr/share/pixmaps/chromium-browser.png
Chromium-browser is just one of the packages I remember having installed using yaourt prior to the /var/lib/pacman deletion. I would like to know if there is a way to find all such aur packages installed through yaourt prior to /var/lib/pacman deletion and if possible, delete them.
Thanks.
Last edited by billy123 (2010-04-05 16:35:35)

How to inspect AUR package PKBUILD and .install files

Hi,
Linux and arch newbie here. I was reading the wiki article about the AUR and noticed this bit:
Warning: Carefully check all files. cd to the newly created directory and carefully check the PKGBUILD and any .install file for malicious commands. PKGBUILDs are bash scripts containing functions to be executed by makepkg: these functions can contain any valid commands or Bash syntax, so it is totally possible for a PKGBUILD to contain dangerous commands through malice or ignorance on the part of the author. Since makepkg uses fakeroot (and should never be run as root), there is some level of protection but you should never count on it. If in doubt, do not build the package and seek advice on the forums or mailing list.
This is something that have not been doing at all in the past, but I am trying to improve my practices managing my system.
The problem is, I do not know what exactly I am looking at or for in these files. If I give these files a look over before installing the package, can I honestly expect to spot something malicious? What would I need to learn to notice if something was fishy?
Anyway, I am not to worried about this practically, because I only use a handful of AUR packages and I usually install ones based on recommendations, not just at random. But it still seemed interesting for the wiki to stress this so strongly. How important is this guidline anyway?
Thanks!
[EDIT: spelling]
Last edited by supernerd (2014-06-25 10:41:13)

I scan the whole PKGBUILD. I start by ensuring that the source link to the original source looks accurate. For example, take the source line for gmusicbrowser-git:
source=("${pkgname}::git+http://github.com/squentin/gmusicbrowser.git")
I know this is the correct link to the source, and so it passes my check. But suppose it had said:
source=("${pkgname}::git+http://youvebeenhackedhub.com/1337haxorz/gmusicbrowser.git")
I would become suspicious. Of course this is an exaggeration, but common sense goes a long ways here. At least check the first time..
With the source verified, I ensure that the md5sum or sha256sum block has a sum. This way, if a download is compromised at the source, the sha256 or md5sum can catch it before you installed (this assumes that the PKGBUILD is not "bad" and has the sum number of a package that wasnt compromised). Note that with git this isnt necessary (the git process protects against such problems). Anytime a tarball is downloaded and extracted however, the sums should be present in the PKGBUILD. If I go to install an AUR package that has 'SKIP' for the md5sum/sha256sum block, I will double or triple check the source of the tarball (or of the patch files enclosed in the build directory, etc..)
I also look for any "dangerous" commands in the build and install sections. For example, if I see "rm -rf" I had better see something like $pkgdir to start the directory path or be VERY sure the path is "safe". Since makepkg is not run as root this should theoretically not be a problem, but imagine if someone put "rm -rf /home/*" (warning: do not run that command on your system!) in there! This is mostly common sense; in time as you get more comfortable with bash and various linux commands it will make more and more sense and you will be able to spot mistakes.
Also, consider the user posting the pkgbuild. "Trusted Users" are selected as trustworthy members of the community, so obviously you can feel much more comfortable with PKGBUILDS they have made (Xyne comes to mind..). For people you may not know, check what other PKGBUILDs they have available. After awhile, you develop a trust for certain people whos PKGBUILDs or software you have used. For example, I wouldnt hesitate to build/install using a PKGBUILD put up by BurntSushi since I use some of his software, have personally corresponded with him, and find him to be responsible. You might "develop" such rapport with other AUR users I dont even know about.
Consider the vote count of a package as an approximate metric. Dont discount a package because it has 0 votes- it may just be that not many people have use for that particular software. Ive considered hosting a PKGBUILD for "xfce4-terminal-nowindowhints"; consider that tilers generally ignore them anyway, and that my package would only be useful for someone literally using xfce4-terminal with pytyle. How high do you think the vote count would be (even if the PKGBUILD had 0 errors)? On the other hand, you at least have a good chance the PKGBUILD is solid if the package has 354 people voting for it.. That said, the package could have been well-maintained before (when it received a ton of votes), and the quality has dropped since- just be mindful of these trends.
Finally, adding all of these things together will leave the odds of a malicious PKGBUILD affecting your system pretty slim, though its certainly not impossible. I have never (to my knowledge to be fair) encountered a malicious PKGBUILD, though I have found a few that had errors or outdated sources, etc.
Last edited by GSF1200S (2014-06-29 10:13:50)

[Solved] How to list installed AUR packages ?

Hi,
I use "packer" to install AUR packages.
How can I get a list of installed AUR packages ?
Thanks for your help
- PierreR
Last edited by PierreR (2011-12-06 11:37:40)

You should focus your Google searches to the forum
site:bbs.archlinux.org how to list installed AUR packages
https://www.google.com/search?q=site%3A … 78&bih=977 (I used your title for the search)
You can set the settings to pick only the hits from e..g the last year.

[SOLVED] How to install aur packages using pacaur

I'm trying to install dwb-git. It installs with no problem with aura, but pacaur gives me problems. If I run pacaur as regular user it will build but will not install and will say permission denied.
If I run pacaur with sudo it will say building packages as root is a bad idea and will quit. The only other possibility I see is running it with --asroot flag which is a really bad idea.
Last edited by bstaletic (2014-06-22 15:02:41)

No, I get the errors I described above.
Here are the outputs:
bstaletic@arch ~ $ pacaur -y dwb-git
:: resolving dependencies...
:: no AUR metadata for dwb-git package
:: looking for inter-conflicts...
AUR Packages (1):
Name Old Version New Version
aur/dwb-git latest
:: Proceed with installation? [Y/n]
:: Retrieving package(s)...
:: View dwb-git PKGBUILD? [Y/n] n
:: View dwb.install script? [Y/n] n
==> Making package: dwb-git 2014.03.04.g5088db1-1 (Sun Jun 22 15:46:30 CEST 2014)
==> Retrieving sources...
-> Cloning dwb git repo...
Cloning into bare repository '/tmp/pacaurtmp-bstaletic/dwb-git/dwb'...
remote: Counting objects: 15056, done.
remote: Compressing objects: 100% (3796/3796), done.
remote: Total 15056 (delta 11190), reused 14783 (delta 10952)
Receiving objects: 100% (15056/15056), 2.63 MiB | 88.00 KiB/s, done.
Resolving deltas: 100% (11190/11190), done.
Checking connectivity... done.
==> Validating source files with md5sums...
dwb ... Skipped
==> Extracting sources...
-> Creating working copy of dwb git repo...
Cloning into 'dwb'...
done.
==> Starting pkgver()...
==> Updated version: dwb-git 2014.06.14.g9f4bdb9-1
==> Sources are ready.
:: Building dwb-git package(s)...
==> Making package: dwb-git 2014.06.14.g9f4bdb9-1 (Sun Jun 22 15:47:05 CEST 2014)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing src/ tree
==> Starting build()...
Build options:
CC = cc
CFLAGS = -march=native -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wall -Werror=format-security -pipe --ansi -std=c99 -D_POSIX_C_SOURCE=200112L -O2 -g -D_BSD_SOURCE -D_NETBSD_SOURCE -D__BSD_VISIBLE -pthread -I/usr/include/webkitgtk-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/webkitgtk-1.0 -I/usr/include/p11-kit-1 -I/usr/include/json-c -I/usr/include/libsecret-1 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DWITH_LIBSOUP_2_38=1
LDFLAGS = -Wl,-O1,--sort-common,--as-needed,-z,relro -lwebkitgtk-1.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lpangoft2-1.0 -lpango-1.0 -lfontconfig -lfreetype -lsoup-2.4 -ljavascriptcoregtk-1.0 -lgnutls -ljson-c -lsecret-1 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lpthread -lm -lX11
CPPFLAGS = -march=native -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -DWITH_LIBSECRET
make[1]: Entering directory '/tmp/pacaurtmp-bstaletic/dwb-git/src/dwb/src/util'
cc convert_transport_security.c
convert_transport_security.c: In function ‘handle_pinsets’:
convert_transport_security.c:256:9: warning: ‘json_object_object_get’ is deprecated (declared at /usr/include/json-c/json_object.h:290) [-Wdeprecated-declarations]
if((name_obj = json_object_object_get(pin_list, "name")) == NULL || !json_object_is_type(name_obj, json_type_string))
^
convert_transport_security.c:263:9: warning: ‘json_object_object_get’ is deprecated (declared at /usr/include/json-c/json_object.h:290) [-Wdeprecated-declarations]
good_hashes = json_object_object_get(pin_list, "static_spki_hashes");
^
convert_transport_security.c:264:9: warning: ‘json_object_object_get’ is deprecated (declared at /usr/include/json-c/json_object.h:290) [-Wdeprecated-declarations]
bad_hashes = json_object_object_get(pin_list, "bad_static_spki_hashes");
^
convert_transport_security.c: In function ‘handle_entries’:
convert_transport_security.c:297:9: warning: ‘json_object_object_get’ is deprecated (declared at /usr/include/json-c/json_object.h:290) [-Wdeprecated-declarations]
if((name_obj = json_object_object_get(entry, "name")) == NULL ||
^
convert_transport_security.c:307:9: warning: ‘json_object_object_get’ is deprecated (declared at /usr/include/json-c/json_object.h:290) [-Wdeprecated-declarations]
json_object *mode = json_object_object_get(entry, "mode");
^
convert_transport_security.c:315:9: warning: ‘json_object_object_get’ is deprecated (declared at /usr/include/json-c/json_object.h:290) [-Wdeprecated-declarations]
json_object *include_subdomains = json_object_object_get(entry, "include_subdomains");
^
convert_transport_security.c:327:9: warning: ‘json_object_object_get’ is deprecated (declared at /usr/include/json-c/json_object.h:290) [-Wdeprecated-declarations]
if((entry_pins = json_object_object_get(entry, "pins")) != NULL)
^
convert_transport_security.c: In function ‘parse_json’:
convert_transport_security.c:371:5: warning: ‘json_object_object_get’ is deprecated (declared at /usr/include/json-c/json_object.h:290) [-Wdeprecated-declarations]
if((pinsets = json_object_object_get(json, "pinsets")) == NULL || !json_object_is_type(pinsets, json_type_array) ||
^
convert_transport_security.c:380:5: warning: ‘json_object_object_get’ is deprecated (declared at /usr/include/json-c/json_object.h:290) [-Wdeprecated-declarations]
if((entries = json_object_object_get(json, "entries")) == NULL || !json_object_is_type(entries, json_type_array) ||
^
gen hsts_preload.h
/bin/sh: ./convert_transport_security: Permission denied
Makefile:41: recipe for target '../../src/hsts_preload.h' failed
make[1]: *** [../../src/hsts_preload.h] Error 126
make[1]: Leaving directory '/tmp/pacaurtmp-bstaletic/dwb-git/src/dwb/src/util'
Makefile:22: recipe for target 'src/util.subdir-buildfirst' failed
make: *** [src/util.subdir-buildfirst] Error 2
==> ERROR: A failure occurred in build().
Aborting...
:: dwb-git cleaned
bstaletic@arch ~ $ sudo pacaur -y dwb-git
:: resolving dependencies...
:: no AUR metadata for dwb-git package
:: looking for inter-conflicts...
AUR Packages (1):
Name Old Version New Version
aur/dwb-git latest
:: Proceed with installation? [Y/n]
:: Retrieving package(s)...
:: View dwb-git PKGBUILD? [Y/n] n
:: View dwb.install script? [Y/n] n
==> ERROR: Running makepkg as root is a BAD idea and can cause permanent,
catastrophic damage to your system. If you wish to run as root, please
use the --asroot option.
:: Building dwb-git package(s)...
==> ERROR: Running makepkg as root is a BAD idea and can cause permanent,
catastrophic damage to your system. If you wish to run as root, please
use the --asroot option.
:: dwb-git cleaned
I get the same errors with -Sya and -Sa flags.

[SOLVED] Archiso : installing AUR packages on a live image

Hi all,
I'm quite an arch newbie, I'm trying to setup a live USB stick, with the help of archiso. My goal is to finally get an "audio oriented" system (with jack, ardour, qsampler, and so more...).
During the setup everything was working very well, until I tried to add some AUR packages to the install.
On the arch website, I found this tip, which gave me a great hope about this.
I'm not so familiar with Arch package management, but ok, I try to make a test : adding the "qsampler" AUR package. It needs "linuxsampler", "qt4", and "liblscp" as dependencies. "linuxsampler" and "qt4" are official packages, so I just have to add them to packages.both in the archiso working directory. "liblscp" is an AUR package (with no dependency); so there is 2 AUR packages to install : "liblscp", and "qsampler".
So I create a directory tree like described in the tip, download the two build packages from AUR, and for each of them I do (something) like described there :
# tar -xvf tarball_filename.tar.gz
# cd tarball_filename
# makepkg --asroot
# mv *.xz ..
# cd ..
# rm -r tarball_filename{,.tar.gz}
And then:
# repo-add customrepo.db.tar.gz *.xz
(I'm staying as root because it's red written to stay as root for the image creation. I think it's stupid, but people make stupid things when they are desesperate. Sorry I didn't take the time to test the code above again, it's only memory, but it was very similar)
I did the same for both architectures (i686 and x86_64), so that my custom repo looks like this:
~/liveusb/customrepo # ls -R
i686 x86_64
./i686:
customrepo.db customrepo.db.tar.gz liblscp-0.5.6-1-x86_64.pkg.tar.xz qsampler-0.2.3-1-x86_64.pkg.tar.xz
./x86_64:
customrepo.db customrepo.db.tar.gz liblscp-0.5.6-1-x86_64.pkg.tar.xz qsampler-0.2.3-1-x86_64.pkg.tar.xz
Oops... I just noticed I did wrong for i686 machines, but it doesn't matter for the moment, since I'm working on an x86_64 machine.
As explained in the tip, I add the following lines to pacman.conf (in the archiso working directory):
[customrepo]
SigLevel = Optional TrustAll
Server = file:///my/path/to/customrepo/$arch
From my point of view, at this point, the USB stick is ready to be updated:
~/liveusb # ./build.sh -v
and then (with /dev/sdf as my usb stick device):
~/liveusb # dd if=out/archlinux-2014.10.01-dual.iso of=/dev/sdf
But when I boot on the USB stick, there's no trace of qsampler (linuxsampler, however, is present).
Since it happened, I'm feeling like a lost, lonely man, on a desert island... Thinking about the "why", the "how"..., the meaning of life..., of package management... all this stuff
I'm sure I did something wrong about the "custom repository", and the main reason is I don't deeply understand all the steps about this; that's why I'm looking for help
Any idea?
Many thanks
Last edited by yolenoyer (2014-10-02 09:16:57)

Thank you for the reply,
I think I did a more trivial mistake :
With archiso, the packages are automatically installed, from a package list file called "packages.both", and "packages.x86_64", "packages.i686" for architecture dependent packages. But they only use common repos by default. The "'qsampler" is not in official repos (that's why I choosed this one for my question).
So, ok, I setup a common repo (with some mistakes but it was working), BUT...
I just forgot to put the package name in the packages.both file...
So, now that I did it, I just have an error about the package architecture, which I think possible to fix, just by rebuilding the common repo in a correct manner:
~/liveusb # ./build -v
warning: vlc-2.1.5-3 is up to date -- reinstalling
warning: mplayer-37224-2 is up to date -- reinstalling
error: failed to prepare transaction (package architecture is not valid)
:: package qsampler-0.2.3-1-x86_64 does not have a valid architecture
==> ERROR: Failed to install packages to new root
Trilby wrote:Also, does this need to be a static iso image - is there a reason not to just do a persistent usb install?
About the static iso image : the idea of building an iso image with all my personnal tools and config already installed on it is very pleasant to me, including the fact that you can burn it on a CD as well. The persistent acpect would be pleasant too, but in a secondary way.
While I'm writing this message I really understand a bit more about all of this, since yesterday... Sometimes, simply posting a message in forums helps you to understand your own problem, because you have to be clear and concise!
Thanks

Yaourt fails to install *any* AUR package

Hello, I'm new to Arch, but since my problem is pretty much specific to yaourt/AUR I thought this would be the better place to ask around.
I tried to install a whole bunch of packages from the AUR repository, but almost all that I tried failed to install, mainly dependency errors far into or after the compiling process, one example - the game Go-Ollie wouldn't install because the Image Magick library wasn't found. However, Image Magick is installed, but there's no trace of it's library not in the AUR, nor the community repository. Same with A7XPG - failed to install because something was missing that I can't find anywhere. I am starting to get VERY frustrated. It looks like there are a ton of broken packages floating around in the AUR and there are a ton of programs missing that I'm used to having on the other distors (Ubuntu, Fedora, etc..) What am I missing here? Am I doing something wrong or is AUR/Yaourt really as messed up as it seems? A little help?
PS: Please be easy on me, I'm still a grass green noob after all

bloodyhell wrote:Got an off-topic question though - It came to my attention that the Arch install distro had a relatively easy albeit non-graphical installer. Why did the developers ditch this? I think I'll never understand the appeal of things being more complicated and/or inconvenient than they have to be.
The AIF was not ditched for any but the most simple reason: It was buggy as hell and the maintainer did not have the time to keep it going. It tried to do everything, to cover every scenario, but was ultimately a victim to its own complexity. The new installer is not more complicated, it is actually more simple. All you have to do is follow the readme step by step and make your own decisions in the process. I find pacstrap and arch-chroot to be more universal than the old AIF. Before the switch, creating an install script was a painful process of understanding the AIF and learning its syntax. Now we have these straight forward tools, so building your own install script is very easy. It also gives you a more in-depth knowledge of what's going on on your system.
The new installer also seems to be more friendly towards wifi users. Then you will never ever again have to deal with the situation, that the AIF somehow kicks you out of the process and then complains about an ongoing installation, without telling you where the lockfile is or how to fix this manually. In a menu, I always press down and enter to get to the next item. The AIF did half of this, it moved the cursor down to the next item automatically. In more than one occasion, I killed the installer with this and sometimes even had to redo the entire process (incl. downloading the packages), because bringing the installer back to a specific state was a painful act. I find the current solution more user friendly.
If you feel like Arch could need a menu driven installer, you are invited to create one, but all attempts to do this so far either drowned as quick as they had emerged or were rejected by the other users, because they were either too specific, too buggy or generally failed to add anything to the process, that the current install scripts have to offer.

How to list AUR packages in terminal with yaourt or other helper?

I can list packages I have installed from AUR, for example to find all the developer components of Xfce that I have installed, I can run the following command:
pacman -Qim | grep -E "Name : xf".+devel
Which outputs:
Name : xfce4-appfinder-devel
Name : xfce4-dev-tools-devel
Name : xfce4-panel-devel
Name : xfce4-session-devel
Name : xfce4-settings-devel
Name : xfdesktop-devel
Name : xfwm4-devel
But, how do I find out if there are other packages that match the same regex pattern available in the AUR, maybe using yaourt? When I try:
yaourt -Si | grep -E "Name : xf".+devel
I get no output. When I don't include .+devel, I find out that none of the AUR packages are included. If I try to force it to search the AUR by including -a, it says that's not a valid option.
So, how do I search the AUR from the terminal?

falconindy wrote:
cower transparently supports regex -- but not thanks to the AUR. In reality, the query "xf.*-devel" is actually asking the AUR to search for "xf". The returned results are filtered against the regex "xf.*-devel" and out pops magic.
Yaourt doesn't do this.
I saw that, but Yaourt should be able to simply query the AUR without it trying to install stuff, but how? Does anyone know? I knew yaourt didn't support regex, that's why I was piping the output to grep. It worked for pacman, and works for yaourt when it uses pacman, but I can't figure out how to get it to return the contents of the AUR so I can pipe those contents through grep.

[SOLVED] can't build an AUR package while installing Arch

So I am nearly there installing Arch for the first time. And I will start with saying that I am really sorry if I missed the answer to my problem but I have had a look around the documentation and the general webz for something regarding this problem and haven't found anything.
I am trying to set my wireless connection up but I apparently need the AUR b43-firmware package installed for my Broadcom BCM4322 [14e4:432b] to be functional.
So I follow the documentation to install an AUR package, but I am stuck at the building stage as makepkg does not allow me to build if I am root, and I am root by default while installing/configuring Arch...
What should I do to build and install that package so I have a wireless connection later on?
Cheers
Last edited by chtfn (2015-03-21 14:11:12)

I am connected to the wired network, and I followed the steps to make it persistent for later, but I just wanted to go through the wireless stuff too to be extra sure I will be able to connect to the Internet later on. As it is the first time I install Arch, I am trying to be extra cautious, and having that security would make me feel more comfortable! Plus, I am keen to learn how to do those things from the command line.
Isn't there a way to switch to a normal user just for a command, and automatically reverting back to root when that action is finished? Just like sudo but the other way round

Did I install the AUR packages correctly and safely ?

Hello
I'm interested in several packages in AUR, but to be honest, it's the first time that I install an AUR pkg without using the yaourt frontend.
I just installed archey, I tried to follow the wiki but I would like to know if I followed all the steps correctly or not...
I've done:
sudo pacman -S fakeroot
wget http://aur.archlinux.org/packages/archey/archey.tar.gz
wget http://aur.archlinux.org/packages/archey/archey/PKGBUILD
makepkg -s
[makepkg -s installed git, and perl-error through pacman I supposed]
sudo pacman -U archey-20100704-1-x86_64.pkg.tar.xz
My questions are:
1] I've done "sudo pacman -U archey-20100704-1-x86_64.pkg.tar.xz" but the wiki said "$ pacman -U /path/to/pkg.tar.gz" => because the prompt said something like "only root can perform this action" when I was not using sudo
2] After the installation, I've done "pacman -Qdt" and it appeared that git, and perl-error were not longer used, so I removed them => Is it a mistake ?
3] How can I update the AUR packages when a newer version will be released ?
Sorry for my english, and thank you for helping me understanding
Last edited by Lowra (2010-07-04 11:34:03)

Lowra wrote:
Thank you Allan:
"3) there are many helpers to keep AUR packages up to date. See the wiki." => Sorry that was not that I wanted to say, I hope I will do this things in the future, but I have not enough experience for that now ^^
In fact, I wanted to say: How can I update the packages installed in my computer from AUR (example: archey) when the maintainer will update his program ?
Thanks again, it's nice to learn news things about Arch, AUR, and Linux ^^
Read what Allan said again.
You want an AUR helper, like packer, clyde or bauerbill, for example. ;)

How do I install co-dependent AUR packages?

Similar Messages

Maybe you are looking for