Installed packages with root

Hi!
I accidently installed a couple of applications when i was logged in as root.
Is there a way to make the root account as it is from the beginning without installing arch all over again?

RaisedFist wrote:Still, all packages are installed as root. If he means he was running some apps with root, then he has to switch back to his user and just start the application.
Exactly, unless root holds permissions to some files that need to be read by those apps - they won't run then.
Let's wait for the OP to respond what exactly the problem is and what are the symptoms :-)

Similar Messages

  • How to install package with documentation

    hi, i installed emacs but the manual is missing in this instalation.
    How can I force to install a package with manual and other documentation?
    Thanks

    i solved it. I used the correponding option in PKGBUILD and compiled again. R.M.

  • Install package with extra switches

    Is it possible to install a package with extra switches that you would normally give with the configure command?

    vinyl wrote:Is it possible to install a package with extra switches that you would normally give with the configure command?
    this is what srcpac was made for - run "pacman -S srcpac" and then check out the man page (there's alot to explain)
    however, as noted, you're going to have to recompile the app, but it's not all that hard with srcpac.... you add the additional line in srcpac.conf and run "srcpac -S some_app"... if there is no line in srcpac.conf, srcpac installs the app through pacman... it's very cool
    for the record, if the repos had one package for every switch, they would grow to huge proportions... imagine 20 vim packages, one for each flag... and that's just vim... KDE and gnome would make the repos hit huge proportions...

  • [SOLVED]How to install packages with the -U option? PGP error.

    I have to downgrade some packages (linux package due to ath5k problem), but pacman won't allow me because of the signatures.
    I downloaded the packages i need from here http://schlunix.org/archlinux/.
    These packages are safe to install? How can i bypass the signature check, if these packages are safe to install?
    Thanks.
    Last edited by Hyugga (2012-04-19 19:46:23)

    If you have a pgp key, you can sign the packages with your own key. You can do this by editing /etc/makepkg.conf, adding your key to the  GPGKEY="" section and enabling the sign option in the BUILDENV section. When building the package, it'll then be signed with your personal key. Afterwards import your key in pacman (pacman-key -r <yourkey>), assign the proper trust level and you're good to go.
    A workaround is to temporarily set "SigLevel = Never" in your /etc/pacman.conf (and hence disabling keysigning).
    EDIT: I just bothered to actually check your link and you'll be installing prebuilt binaries, so my first explanation doesn't apply there (you won't be building anything). So just setting SigLevel to Optional or Never (temporarily) should do.
    Last edited by Gcool (2012-04-19 19:23:05)

  • Install Packages with a schedule (repeating)

    When I make a (for example) package Office 2008 SP2 update and make a schedule for a computer group and click "Repeating every 1 Days" on so that Macs that are outside the company get the update when they login the network the next day or week. I notice that Mac's who received the update the next day they received the update the day after this again (settings of the install package) I there a way that Mac's who received a update don't get that update again? or must i manually removed the Mac's who received the update?

    Basically, the construct $(command) takes the output of command and inserts it into the outside command...
    for example,
    if pidof xyz outputs 1248,
    kill $(pidof xyz)
    is identical to
    kill 1248
    There is a similar older construct that uses backtics (that's the one under the tilde, not the apostrophe), so that
    kill `pidof xyz`
    is identical to the above.  The new construct $() is more useful because it's easier to nest multiple commands as in
    command 1 $(command2 $(command 3))
    if that ever needed to be done.
    So what the original command did was insert the output of the 'cat pkg.txt' command in the commandline.
    Dusty

  • HAI (Home Arch Install) - install packages without root account

    HAI, or Home Arch Install, can "install" and run Arch Linux programs from your normal user account. (Even if you don't run Arch Linux at all - see the config file.)
    HAI's design is heavily inspired by Zero Install, but it uses Arch Linux packages instead of a new package format. This means you can make use of Arch's extensive package database, right now.
    HAI follows the KISS and worse-is-better philosophies. HAI is implemented as a set of specialized bash scripts, with under 500 lines of code in total, so it's not that hard to read, understand and extend.
    HAI doesn't really install the packages it downloads - it uses fakechroot and unionfs-fuse to fool the program you run into thinking it's installed in /usr.
    Quick start guide:
    1. Download HAI from http://www.smnd.sk/tomi/hai/hai-1.1.tar.gz . (The address might eventually change, so please don't link to it directly.)
    2. HAI doesn't need system-wide installation. Just unpack it somewhere.
    3. Put this in your ~/.bashrc file: "alias hai=~/your/directory/with/hai". This allows you to run hai without typing the path.
    4. Run "./bootstrap" from HAI's directory. This downloads dependencies HAI itself needs. (You need FUSE already installed, though.)
    5. Try it:
    hai bwm-ng
    hai frozen-bubble
    hai pysolfc pysolfc-cardsets -- pysol
    hai inkscape -- inkscape somefile.svg
    # in general: hai (what packages to install) -- (what program to run)
    HAI comes with a README.txt file. You really should read it, it's short and if you've read this far, you already know most of it.
    I've been working on HAI for two months and it's finally reached a state bug-free and elegant enough that it satisfies my prefectionism. I developed HAI to scratch my own itch, but please tell me if you try HAI, or perhaps even find it useful! I'd also like to know about any bugs you experience or feature requests you might have. If you find something in the documentation that could use clarifying, tell me as well.
    (Update 2010-05-11: hai-1.1 fixes a bug when downloading from AUR and switches from tar to bsdtar, because tar acts up when downloading xz-compressed packages. For now, bsdtar has to be installed on the local system.)
    Last edited by Tomi (2010-05-11 10:35:44)

    Oops, didn't notice your reply, tavianator. Thanks for the bug reports!
    vercmp: That's what I get for assuming libalpm won't change its internal layout... it was working at the time of HAI's release. Thanks for the fix.
    rsync: I use it to get the fakechroot PKGBUILD. I could download the whole ABS tree through http, but most of the time it would be a waste... I'll try to think of a compromise.
    Using HAI on distros other than Arch isn't very streamlined, though this is something I hope to improve. The SYSTEM_CHECK in the config file needs changing. (It's a program that checks if a package is already installed on the machine.) This line should work (it was tested on Mandriva, which uses rpm too):
    SYSTEM_CHECK='local sysver; sysver=`rpm -qa | grep "^\(\|lib\)$requestname" | sort | grep -o "[^-]*-[^-]*$" | grep -o "^[^-]*"` || true; [ "$sysver" ] && version-ok "$sysver" && true'
    Update on rsync: The PKGBUILD is in http://repos.archlinux.org/wsvn/package … dl&isdir=1 too, but that link can easily change if Arch switched from websvn to someting else. I'd appreciate a second opinion whether to use rsync or this link.
    Last edited by Tomi (2010-05-19 18:21:10)

  • Installing package with -U and Ignoring Signatures

    If I want to install a package using -U but the package isn't signed, can I tell pacman to SigLevel = Never for this one transaction, rather than having to edit pacman.conf, install, then change pacman.conf back?
    # pacman -U http://www.example.com/foobar-20130417-1-any.pkg.tar.xz
    foobar-20130417-1-any 1180.0 B 1152K/s 00:00 [#############################################] 100%
    loading packages...
    error: /var/cache/pacman/pkg/foobar-20130417-1-any.pkg.tar.xz: signature format errorerror: GPGME error: No data
    error: '/var/cache/pacman/pkg/foobar-20130417-1-any.pkg.tar.xz': invalid or corrupted package (PGP signature)

    teateawhy wrote:
    Jristz wrote:
    LocalFileSigLevel = Never
    located on manpages
    why this is Trusted by default??
    Do you trust yourself?
    in this case is unnecesary have a LocalFileSigLevel because a common person Trust in their/yourself and if one going to install any from a local file, what is the point of have this if one troust in theirself

  • Replacing a package with a self-build package

    If I have a self-build package that provides something (another package) that I allready have installed and also conflicts with, how do I replace the installed package with the self-build?
    When I try to install it with
    pacman -A /path/to/package
    pacman first tells me that my self-build package conflicts with the installed and whether I want to remove it. If I tell him that he should remove the installed package I get a list of dependencies that would get broke and the installation aborts.
    Any hints on how to solve that problem?

    Use -U (upgrade) switch if updating the package with the same name.
    Use -Rd (remove without dependencies) to uninstall a package and then install the one that provides the same.
    Last edited by lucke (2007-02-11 23:15:27)

  • Are others finding AAMEE 3.0 install packages failing on Macs

    I'm able to create install packages with AAMEE 3.0 without issue.  However, when I go to install the packages on machines (so far, through no automated process), I get an "The installation failed" screen.

    To continue on w/ the original question/problem, I've been having issues, too.  After making my package, I see 2 types of failures.  One has the installer pausing at about 1/8 or so in the progress and the time remaining increases.  This never clears out and you have to force quit the installer.  I've let it sit there and have it climb it to over an hour w/o the progress bar moving.  The other problem involves the failed install which will happen within about 7-10 seconds.  It will go through the progress bar quickly and finish w/ a failed install message.  My packages do have the  "Ignore conflicting process" box checked. 
    One thing I noticed that helped me get around this 7-10 second failed install this morning did not make sense to me.  I did 3 machines w/ the Photoshop CS6 package I created by copying the package over ARD to the desktop of the machine and running it.  The 4th machine I copied the same package off of a local server and it would repeatedly fail during the installation (7-10 second failure).  Finally when I copied it via ARD and running it, it did work.  Anybody ever see this?  I'm not doing the ARD Install package feature.  Just a copy.
    Also, any clue on my first type of failure w/ stuck installer?
    Thanks!

  • Sharing my script to show version difference of installed packages

    Hi all.
    Sometimes I don't want to just pacman -Syu. There are many packages that are big but introduce only minor bugfixes (usually libreoffice packages* are the culprits), so I don't want to have to install those.
    This is something I cooked up a while ago to show version difference of currently installed packages with the latest packages in repository.
    It's in python3, and uses python-termcolor.
    It outputs something like this:
    acl : 2.2.52-1 --> 2.2.52-2
    archlinux-keyring : 20130926-1 --> 20131027-1
    bison : 3.0-1 --> 3.0.1-1
    cracklib : 2.9.0-1 --> 2.9.0-2
    Here is the script:
    #!/usr/bin/python3
    from subprocess import check_output
    from termcolor import colored
    pacman_out=check_output(["pacman","-Sl"], universal_newlines=True).split("\n")
    outlist = []
    len_pkgname = 0
    len_majver = 0
    len_newver = 0
    len_oldver = 0
    for pkgs in pacman_out:
    if not "[installed" in pkgs:
    continue
    if "[installed]" in pkgs:
    continue
    pkg_split = pkgs.split(" ")
    newver = pkg_split[2]
    oldver = pkg_split[4].rstrip("]")
    for i in range(min(len(newver),len(oldver))):
    if newver[i] != oldver[i]:
    break
    pkgname = pkg_split[1]
    majver = newver[:i]
    oldver = oldver[i:]
    newver = newver[i:]
    outlist.append((pkgname, majver, newver, oldver))
    len_pkgname = max(len_pkgname, len(pkgname))
    len_majver = max(len_majver, len(majver))
    len_newver = max(len_newver, len(newver))
    len_oldver = max(len_oldver, len(oldver))
    for (pkgname, majver, newver, oldver) in outlist:
    print("{}: {}{} --> {}{}".format(
    pkgname.ljust(len_pkgname),
    colored(majver.rjust(len_majver),"cyan"),
    colored(oldver.ljust(len_oldver),"cyan",attrs=["bold"]),
    colored(majver.rjust(len_majver),"magenta"),
    colored(newver.ljust(len_newver),"magenta",attrs=["bold"])))
    I hope pkgbrowser will include something like this in the future.
    P/S: * these packages will break anyway in the event the dependencies has had some ABI changes.
    EDIT: swapped new and old version columns. Thanks, karol!
    Last edited by syockit (2013-12-04 17:55:42)

    syockit wrote:I hope pkgbrowser will include something like this in the future.
    Why not suggest adding this feature?
    Currently it shows only the version that is going to be installed https://bbs.archlinux.org/viewtopic.php … 3#p1316573
    I've mated pacman's checkupdates with my old script https://bbs.archlinux.org/viewtopic.php … 80#p829780
    $ diff -Naur /usr/bin/checkupdates ch
    --- /usr/bin/checkupdates 2013-10-21 14:04:37.000000000 +0000
    +++ ch 2013-12-04 18:46:52.792101792 +0000
    @@ -37,7 +37,11 @@
    mkdir -p "$CHECKUPDATES_DB"
    ln -s "${DBPath}/local" "$CHECKUPDATES_DB" &> /dev/null
    fakeroot pacman -Sy --dbpath "$CHECKUPDATES_DB" --logfile /dev/null &> /dev/null
    -pacman -Qqu --dbpath "$CHECKUPDATES_DB" 2> /dev/null
    +
    +conf=${TMPDIR:-/tmp}/checkup-db-${USER}/pacman.conf
    +grep -v "^Ignore" /etc/pacman.conf > $conf
    +
    +/usr/bin/paste -d " " <(/usr/bin/printf "%-20.20s %-12s => \n" $(/usr/bin/pacman -Qu)) <(/usr/bin/pacman -Sdp --config $conf --print-format "%v" $(/usr/bin/pacman -Qqu --dbpath "$CHECKUPDATES_DB" 2> /dev/null))
    exit 0
    $ ./ch
    libpipeline 1.2.4-1 => 1.2.5-1
    No colors though.
    Last edited by karol (2013-12-04 18:55:03)

  • [SOLVED] script to backup installed packages

    Hi guys,
    I know it should be easy, but I keep failing...
    I can generate the list of installed packages with:
    comm -23 <(pacman -Qeq|sort) <(pacman -Qmq|sort) > pkglist.txt
    and I woudl like to integrate into my backup script.
    I was testing it with a script with only two lines:
    #! /bin/bash
    comm -23 <(pacman -Qeq|sort) <(pacman -Qmq|sort) > pkglist.txt
    but I get:
    mkpklist: line 3: syntax error near unexpected token `('
    mkpklist: line 3: `comm -23 <(pacman -Qeq|sort) <(pacman -Qmq|sort) > pkglist.txt '"
    I tried different options with brackets in different places, but me being useless with these things I have no idea of what I am doing...
    could anyone point me in the right direction?
    Thanks a lot
    M
    Last edited by mcarni (2013-01-09 22:26:34)

    @mcarni, you know that when you use "sh <script>" you are specifying sh as the shell the script will be run with.  In otherwords, you are overriding the shebang (#!/bin/bash) with /bin/sh.  On our systems, we actually don't have an actual /bin/sh, as it is a symlink to bash.  But when it is called via that symlink, it actually does its best to act like the old bourne shell.

  • Hmm - reason for installing package...

    All,
    I'm not sure if this issue has been brought up before, but I want to get some feedback about a pacman idea that I had.
    pacman -Qi lets you see dependencies for installed packages.  It helps you see why you installed a package.  Super helpful.  But it doesn't show everything.
    Sometimes you've installed a package because there was an install-time recommendation for another package.  Or perhaps I was writing a python program and tried out a library, but then later used a different library and so the library is still installed, but not being used.  In cases like these, there may be no clean way to hook up an installed package with the "reason" it was installed.
    My idea is to have some type of flag on pacman where I can record the reason I'm installing a package (or group of package).  Then that reason will be stored for when I run pacman -Qi later on.  It can just be a one-line piece of text.  No need for anything fancy.
    pacman -S python-sqlobject --reason "trying this for project blah"
    It might also be helpful to have a flag where you can set the "reason" on a package after it's already been installed.
    pacman -Q python-sqlobject --reason "trying this for project blah"
    Then, later:
    > pacman -Qi python-sqlobject
    Repository : extra
    Name : python-sqlobject
    Version : 0.10.1-1
    URL : http://sqlobject.org/
    Licenses : LGPL
    Groups : None
    Provides : None
    Depends On : python>=2.5 setuptools>=0.6c8 python-formencode>=0.7
    Optional Deps : None
    Conflicts With : None
    Replaces : None
    Download Size : 278.70 K
    Installed Size : 1108.91 K
    Packager : Eric Belanger <[email protected]>
    Architecture : i686
    Build Date : Tue 27 May 2008 06:21:26 PM PDT
    MD5 Sum : c3898c5caa7df3f63f04d7afa71fa6d8
    Description : A popular Object Relational Manager for providing an object
    interface to your database, with tables as classes, rows as
    instances, and columns as attributes
    Reason : trying this for project blah
    I envision this being extremely helpful when cleaning up and administering packages on my system (for me personally).
    Can anyone see the benefit of this?  Has this already been brought up?  Are there simpler solutions people are already using? ...

    I actually think this is a pretty good idea, but I'm not sure how many would use it.  I often run across packages on my system and don't remember installing them even though pacman says I did it explicitly

  • Checking installed packages and kernals on linux

    what are the commands to check
    checking installed packages and kernals on linux?

    According to http://download-uk.oracle.com/docs/html/A96167_01/pre.htm#sthref106,
    uname -a should give you your kernel version.
    rpm -q should list all installed packaged with RPM.
    (see http://www.die.net/doc/linux/man/man8/rpm.8.html)
    Message was edited by:
    Pierre Forstmann

  • Install RAC failed with root.sh error while loading shared libraries: libst

    Hi ,
    I install rac under vmware workstation using this atricle .
    http://www.oracle-base.com/articles/10g/OracleDB10gR2RACInstallationOnCentos4UsingVMware.php
    everything work smoothly but I faced error with root.sh
    Failed to upgrade Oracle Cluster Registry configuration
    I found metlalink talk about missing compat-libstdc++-33-3.2.3-47.3.ia64.rpm and must be installed according to
    that .
    The probelm rasied when run
    /u01/app/oracle/product/10.2.0/crs/bin/crsctl.bin: error while loading shared libraries: libstdc++.so.5: cannot
    open shared object file: No such file or directory
    Failure initializing entries in /etc/oracle/scls_scr/rac2.
    Linux version is RHE4
    [oracle@rac1 bin]$ uname -a
    Linux rac1.localdomain 2.6.9-55.ELsmp #1 SMP Fri Apr 20 17:03:35 EDT 2007 i686 i686 i386 GNU/Linux
    when install this package it does not work
    [root@rac1 RPMS]# rpm -Uvh compat-libstdc++-33-3.2.3-47.3.ia64.rpm
    warning: compat-libstdc++-33-3.2.3-47.3.ia64.rpm: V3 DSA signature: NOKEY, key ID b38a8516error: Failed
    dependencies:
    libc.so.6.1()(64bit) is needed by compat-libstdc++-33-3.2.3-47.3.ia64 libc.so.6.1(GLIBC_2.2)(64bit)
    is needed by compat-libstdc++-33-3.2.3-47.3.ia64 libc.so.6.1(GLIBC_2.3)(64bit) is needed by compat-
    libstdc++-33-3.2.3-47.3.ia64 libgcc_s.so.1()(64bit) is needed by compat-libstdc++-33-3.2.3-47.3.ia64
    libgcc_s.so.1(GCC_3.0)(64bit) is needed by compat-libstdc++-33-3.2.3-47.3.ia64 libgcc_s.so.1(GCC_3.3)(64bit)
    is needed by compat-libstdc++-33-3.2.3-47.3.ia64 libgcc_s.so.1(GLIBC_2.0)(64bit) is needed by compat-
    libstdc++-33-3.2.3-47.3.ia64 libm.so.6.1()(64bit) is needed by compat-libstdc++-33-3.2.3-47.3.ia64
    compat-libstdc++ = 7.3-2.96.128 is needed by (installed) compat-libstdc++-devel-7.3-2.96.128.i386 compat-
    libstdc++ = 7.3 is needed by (installed) compat-gcc-c++-7.3-2.96.128.i386[root@rac1 RPMS]#
    My probelm cannot install this packages ? What shoudl I do .

    user12010537 wrote:
    Hi ,
    I found metlalink talk about missing compat-libstdc++-33-3.2.3-47.3.ia64.rpm and must be installed according to
    Linux version is RHE4
    [root@rac1 RPMS]# rpm -Uvh compat-libstdc++-33-3.2.3-47.3.ia64.rpm
    warning: compat-libstdc++-33-3.2.3-47.3.ia64.rpm: V3 DSA signature: NOKEY, key ID b38a8516error: Failed
    dependencies:
    libc.so.6.1()(64bit) is needed by compat-libstdc++-33-3.2.3-47.3.ia64
    My probelm cannot install this packages ? What shoudl I do .
    Hi,
    You need to install the dependency package first like glibc, etc
    also see the output from runcluvfy, it should show which packages need to installed
    Cheers

  • Using pacman to install packages into a seperate root

    After working with an Arch Linux machine for 1-2 years I switched jobs and was given a Mac, which I've enjoyed so far.
    I would, however, like to switch back to Arch Linux but there's something that I've been able to do on Mac OS X using its unofficial package manager Homebrew (http://mxcl.github.com/homebrew/) which I was wondering if it were possible with pacman.
    Typically you have one installation of Homebrew, at /usr/local, and by running 'brew' (/usr/local/brew) it knows that its root is at /usr/local & looks there for all dependencies & installs packages there. If, however, you install homebrew elsewhere (could be the first or a second installation), for instance ~/sw, then running brew from there will install packages in that root.
    I've found this very useful to install package specific to a project I'm working on (specific vendor & version of DB, specific web server etc) without having to install them globally on my system and at the same time without having to resort to installing everything by hand (including dipendencies).
    Is this possible with Pacman?
    Thanks in advance,
    Dale

    this wiki isn't entirely related, but can be helpful.
    https://wiki.archlinux.org/index.php/Ar … bit_System
    4. Sync pacman:
    pacman --root /opt/arch32 --cachedir /opt/arch32/var/cache/pacman/pkg --config /opt/arch32/pacman.conf -Sy
    5. Install the base and optionally base-devel groups:
    pacman --root /opt/arch32 --cachedir /opt/arch32/var/cache/pacman/pkg --config /opt/arch32/pacman.conf -S base base-devel

Maybe you are looking for