I get the error message (ie given below) on installation of any rpm file in openSUSE.
[PK_TMP_DIR|dir:///var/tmp/TmpDir.NUXK6P] Repository already exists.
What should I do?
RPM run from command line? Some other way?
Did you look and see what is in ///var/tmp/TmpDir.NUXK6P
maybe try rebuilding database
as root
rpm --dbrebuild
vineetgupta wrote:
> I get the error message (ie given below) on installation of any rpm file
> in openSUSE.
>
> [PK_TMP_DIR|dir:///var/tmp/TmpDir.NUXK6P] Repository already exists.
>
> What should I do?
-=welcome=-
well, the first question is why are you installing from rpm? i mean,
of course you can if want to but why do it the openSUSE way? try
searching for an installing programs in YaST…that hooks you directly
to a vast storehouse of free software that is tuned for openSUSE and
known to be free from malware…
AND, if YaST installs it YaST will automatically add it to your menu
AND know how to uninstall if if that time comes…
second, that file in your /tmp directory is probably the remains of a
previous attempt you made at installing something but you didn’t let
it finish (you killed the process) and so it left that piece laying
around…
you can go into YaST and set the machine to clean out the /tmp on
every reboot…see here to learn how:
http://forums.opensuse.org/information-new-users/unreviewed-how-faq/412640-clear-temp-files-boot.html
after you have done that in YaST then reboot, and you next attempt at
installing from rpm should work—BUT, my best advice is to always
install with YaST from the four primary repos: oss, non-oss, update
and packman…
–
DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio
Thanks a lot.
Hi all,
I have the same problem.
i look for softwares i need with YAST. but if i don’t find it i go for rpm, if can’t find that also, i build from src.
anyway, i wanted to ask, should i have “PK_TMP_DIR” in my repositories?
Thanks
devox wrote:
> anyway, i wanted to ask, should i have “PK_TMP_DIR” in my
> repositories?
did you abort a YaST run?
–
DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio
yes i do, the refresh when i start application manager sometimes take forever.
does that affect the repositories?
devox wrote:
> yes i do, the refresh when i start application manager sometimes take
> forever.
> does that affect the repositories?
well, yes it affects the software updating system…it just shuts
it down in the middle of everything and messes up everything…
read here: http://tinyurl.com/3568vsn
–
DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio
You might want to see which repo is so slow. My bet is Packman. If so try a different mirror closer to you.
Thanks for the advice. But what do we do when we come to a site – Opera 11.1, for example, or Python 3.1 – that offers an rpm or even a tarball with an installation script? It’s so convenient to just download it and install it. Are you saying that we should avoid the temptation and search for a repository somewhere that contains the package? What if there is no repository?
Could we download the rpm into a subdirectory, add that subdirectory as a repository, and then invoke zypper or YaST?
On 02/20/2011 10:36 PM, NonZ wrote:
> Thanks for the advice. But what do we do when we come to a site –
> Opera 11.1, for example, or Python 3.1 – that offers an rpm or even a
> tarball with an installation script?
as a matter of habit do NOT go out to sites all over the net looking
for stuff to install…
always, your first stop should be the openSUSE repos!
opera and python are both available in the standard (oss) repo and
easily installed with either YaST or zypper
> It’s so convenient to just download it and install it.
it is impossible for it to be more convenient that to install it with
either YaST or zypper…both are a TWO STEP process
-use search to find
-click accept to download, unpack, install AND add to the menu
> Are you saying that we should avoid the
> temptation and search for a repository somewhere that contains the
> package?
yes. always install from an openSUSE repo if possible…
if YaST or zypper do not immediately find the package you seek, then
look to here: http://software.opensuse.org/search
> What if there is no repository?
well, if there is not one (and sometimes there are not) then it is
best to get it from a TRUSTED source…look for an rpm with “suse” in
its name…failing that you can TRY any rpm, maybe it will work,
maybe not…
of course, you are always safe to download source files from a trusted
source and compile on your machine…
do NOT go out and download executables from unknown sources and
execute them (that is the kind of foolishness that allows so many bot
nets among our smarts-challenged friends)…
> Could we download the rpm into a subdirectory, add that subdirectory as
> a repository, and then invoke zypper or YaST?
not necessary…if you find an rpm you know is safe, just click to
begin the download and Firefox will ask you what you wanna do with it,
pick “Open with Install/Remove Software” give your root password when
asked and you are done…no more of that old SO-last-century
download, fiddle around, unpack, double click, follow the “wizard”,
click on the wizard, play with yourself, yadda yadda…
–
DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11
I took your advice and used YaST to install python 3.1.
In the past, I have installed it manually, following the README. There is an option that must be specified to prevent 3.1 from overwriting 2.6. When I do the install through YaST, there’s no way to specify that option (or any other option), so I was afraid that YaST would replace 2.6 with 3.1. Much to my relief that didn’t happen. But I do wonder how installs are done when the install requires options that cannot be defaulted.
I did have a minor problem when I installed the python 3.1 documentation. In the past, I’ve used pydoc and subversion to generate html in a directory of my choosing. With YaST, I had no control over the directory. I guessed that the documentation might end up in /usr/share/doc/packages/python3.1, but there was nothing there. I went to the /var/log/YaST2/y2log and found the name of the documentation package (python3-doc), then used
rpm -ql python3-doc
It turns out that this DID get installed in /usr/share/doc/packages/python, where I expected to find only 2.6 files.
One advantage that the YaST installation offers is uniformity: the package ends up in the same directory on every system. But when one is used to a hands-on approach, allowing YaST or zypper take over completely requires a good deal of faith!
Anyway, thanks for the detailed and very helpful reply. You’ve cleared up a number of issues for me.