List, Version: 10.3 Sys: dual core, 4 GIG I downloaded a few RPM's for a project I'm working on. Installed the RPMs, all went okay, but when I went to preview the directories I noticed some of the directories had no files in them, when they should have. These directories were suppose to be built by the RPM's and files installed. Then I panicked, instead of using 'rpm -e', I deleted the new directories. Now when I use 'rpm -U' to re-install the software, I get the message that this rpm is already installed. How do I get back to the beginning before the rpm's were installed and start over, a clean slate. Thanks, -- MikeF Houston, TX -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 * Mike.Friedrichs <mfriedrichs@consolidated.net> [11-12-07 13:33]:
I downloaded a few RPM's for a project I'm working on. Installed the RPMs, all went okay, but when I went to preview the directories I noticed some of the directories had no files in them, when they should have. These directories were suppose to be built by the RPM's and files installed.
Then I panicked, instead of using 'rpm -e', I deleted the new directories. Now when I use 'rpm -U' to re-install the software, I get the message that this rpm is already installed.
How do I get back to the beginning before the rpm's were installed and start over, a clean slate.
When in doubt, the first step is the command-line, rpm --help and read the output looking for your solution. The second setp would be the man pages. the option you are looking for is "--force" and rpm --help will provide you the necessary command-line parameters. - -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn4472 (GNU/Linux) iD8DBQFHOKW8ClSjbQz1U5oRAoX0AJ47YmQgWt5R5kJhKmbNQuxLU6QPeACfS3eS IidSyBhSNzRWLg3vdNU+0N8= =u0gX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2007-11-12 at 12:04 -0600, Mike.Friedrichs wrote:
List,
Version: 10.3 Sys: dual core, 4 GIG
I downloaded a few RPM's for a project I'm working on. Installed the RPMs, all went okay, but when I went to preview the directories I noticed some of the directories had no files in them, when they should have. These directories were suppose to be built by the RPM's and files installed.
Then I panicked, instead of using 'rpm -e', I deleted the new directories. Now when I use 'rpm -U' to re-install the software, I get the message that this rpm is already installed.
How do I get back to the beginning before the rpm's were installed and start over, a clean slate.
Thanks,
-- MikeF Houston, TX
Not sure what packages you are referring to, so I'll just give a general response here. rpm -U does one of two things:... 1) It upgrades an existing package. 2) If the package did not exist, it installs as new. rpm -F is "freshen". In this case, 1) It upgrades an existing package, or 2) if the package does not exist, it stops. So with respect to the blank directories, is it possible you installed an upgrade package rather than a full blown package? Also, what happens if you rpm -e the entire package and then re-install the package from scratch using rpm -i? -- ---Bryen--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 12 November 2007 19:04:11 Mike.Friedrichs wrote:
List,
Version: 10.3 Sys: dual core, 4 GIG
I downloaded a few RPM's for a project I'm working on. Installed the RPMs, all went okay, but when I went to preview the directories I noticed some of the directories had no files in them, when they should have. These directories were suppose to be built by the RPM's and files installed.
Then I panicked, instead of using 'rpm -e', I deleted the new directories. Now when I use 'rpm -U' to re-install the software, I get the message that this rpm is already installed.
How do I get back to the beginning before the rpm's were installed and start over, a clean slate.
Could you give a few more details? Like which rpms exactly, and which exact commands you ran? Anders -- Madness takes its toll -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anders Johansson wrote:
On Monday 12 November 2007 19:04:11 Mike.Friedrichs wrote:
List,
Version: 10.3 Sys: dual core, 4 GIG
I downloaded a few RPM's for a project I'm working on. Installed the RPMs, all went okay, but when I went to preview the directories I noticed some of the directories had no files in them, when they should have. These directories were suppose to be built by the RPM's and files installed.
Then I panicked, instead of using 'rpm -e', I deleted the new directories. Now when I use 'rpm -U' to re-install the software, I get the message that this rpm is already installed.
How do I get back to the beginning before the rpm's were installed and start over, a clean slate.
Could you give a few more details? Like which rpms exactly, and which exact commands you ran?
Anders
I am working on a RTEMS RTOS system. The rpms came from: http://www.rtems.com/ftp/pub/rtems/linux/4.8/suse/10.3/i586/. The rpms include the cross compiler, debugger, build tools for their RTOS.... They have an example in there documents which used 'rpm -U' for installation. Which I used, but the documents didn't describe the RPM dependencies, I finally found the correct order of installation, at least I didn't get any error messages. I then went to the include directory to look at some of the .h files, there wasn't any, so I knew the installation failed. When installing the location ends up to be /opt/rtem-4.8/with many sub-directories. RPMs, I used: rtems-4.8-binutils-common-2.18-2.suse10.3.i586.rpm rtems-4.8-gcc-common-4.2.1-24.suse10.3.i586.rpm rtems-4.8-gdb-common-6.7.1-1.suse10.3.i586.rpm rtems-4.8-i386-rtems4.8-binutils-2.18-2.suse10.3.i586.rpm rtems-4.8-i386-rtems4.8-gcc-4.2.1-23.suse10.3.i586.rpm rtems-4.8-i386-rtems4.8-gcc-c++-4.2.1-23.suse10.3.i586.rpm rtems-4.8-i386-rtems4.8-gdb-6.6-9.suse10.3.i586.rpm rtems-4.8-i386-rtems4.8-newlib-1.15.0-23.suse10.3.i586.rpm rtems-4.8-newlib-common-1.15.0-24.suse10.3.i586.rpm -- MikeF Houston, TX -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 12 November 2007 21:35:59 Mike.Friedrichs wrote:
I am working on a RTEMS RTOS system. The rpms came from: http://www.rtems.com/ftp/pub/rtems/linux/4.8/suse/10.3/i586/. The rpms include the cross compiler, debugger, build tools for their RTOS....
They have an example in there documents which used 'rpm -U' for installation. Which I used, but the documents didn't describe the RPM dependencies, I finally found the correct order of installation,
That is a repository, so you could just have added it to YaST and let it do the work for you
at least I didn't get any error messages.
If you didn't get any error messages then there were no errors. What makes you think there should have been .h files there? There are about a million rpms in that directory, are you sure you didn't just miss one? But I was also curious about the exact rpm -e command you used, and the subsequent rpm -U command that you said produced the message "already installed" Anders -- Madness takes its toll -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anders Johansson wrote:
On Monday 12 November 2007 21:35:59 Mike.Friedrichs wrote:
I am working on a RTEMS RTOS system. The rpms came from: http://www.rtems.com/ftp/pub/rtems/linux/4.8/suse/10.3/i586/. The rpms include the cross compiler, debugger, build tools for their RTOS....
They have an example in there documents which used 'rpm -U' for installation. Which I used, but the documents didn't describe the RPM dependencies, I finally found the correct order of installation,
That is a repository, so you could just have added it to YaST and let it do the work for you
at least I didn't get any error messages.
If you didn't get any error messages then there were no errors. What makes you think there should have been .h files there?
There are about a million rpms in that directory, are you sure you didn't just miss one?
But I was also curious about the exact rpm -e command you used, and the subsequent rpm -U command that you said produced the message "already installed"
Anders
I looked down the list and grabbed each one that had 'common' or 'suse' in the filename. The .h files are required to do any cross-compiling, none of them were there...... Instead of rpm -e I executed 'rm -rf /opt/rtems-4.8/*'. That wiped all of the sub directories. I then realized I screwed up and should of used 'rpm -e'. I went ahead and tried to use rpm -U to re-install the rpms, which didn't get anywhere because the message told me the rpm was already installed. Then I tried rpm -e, and the message I believe, was, rpm not installed. So now I'm thinking, I need to clean the slate and start over, then I sent an inquiry to this list. Could you give some explanation about using YaST... -- MikeF -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 12 November 2007 22:12:58 Mike.Friedrichs wrote:
Anders Johansson wrote:
On Monday 12 November 2007 21:35:59 Mike.Friedrichs wrote:
I am working on a RTEMS RTOS system. The rpms came from: http://www.rtems.com/ftp/pub/rtems/linux/4.8/suse/10.3/i586/. The rpms include the cross compiler, debugger, build tools for their RTOS....
They have an example in there documents which used 'rpm -U' for installation. Which I used, but the documents didn't describe the RPM dependencies, I finally found the correct order of installation,
That is a repository, so you could just have added it to YaST and let it do the work for you
at least I didn't get any error messages.
If you didn't get any error messages then there were no errors. What makes you think there should have been .h files there?
There are about a million rpms in that directory, are you sure you didn't just miss one?
But I was also curious about the exact rpm -e command you used, and the subsequent rpm -U command that you said produced the message "already installed"
Anders
I looked down the list and grabbed each one that had 'common' or 'suse' in the filename.
The .h files are required to do any cross-compiling, none of them were there......
Instead of rpm -e I executed 'rm -rf /opt/rtems-4.8/*'. That wiped all of the sub directories. I then realized I screwed up and should of used 'rpm -e'. I went ahead and tried to use rpm -U to re-install the rpms, which didn't get anywhere because the message told me the rpm was already installed. Then I tried rpm -e, and the message I believe, was, rpm not installed.
You probably used the full name of the rpm and not the "rpm name". Each rpm has a file name (the one you see when you do ls) and an "rpm name", which is internal to rpm, and doesn't necessarily have anything at all to do with the file name. But usually it is the first part of it. So for example rtems-4.8-i386-rtems4.8-binutils-2.18-1.suse10.3.i586.rpm is a file name, and the rpm name is rtems-4.8-i386-rtems4.8-binutils You can see this if you do rpm -qpi rtems-4.8-i386-rtems4.8-binutils-2.18-1.suse10.3.i586.rpm You need to use the file name for "rpm -U" but you need to use the rpm name for "rpm -e" I still don't think there should have been any .h files. If rpm failed to install anything, it would have told you. If you need the headers to compile things, ask them which package they're in
So now I'm thinking, I need to clean the slate and start over, then I sent an inquiry to this list.
Could you give some explanation about using YaST...
Sure. In YaST, go to "Software repositories", and click on "Add". Then select http and click on "Next". Give the repository a name (doesn't matter what, something you will know what it is when you see it) Server name: www.rtems.com Directory on server: /ftp/pub/rtems/linux/4.8/suse/10.3/i586/ Click "Next" and then on "Finish", and after that you can use YaST's Software Management module to install the packages, and it will handle all dependencies for you Anders -- Madness takes its toll -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon November 12 2007 03:35:59 pm Mike.Friedrichs wrote:
I am working on a RTEMS RTOS system. The rpms came from: http://www.rtems.com/ftp/pub/rtems/linux/4.8/suse/10.3/i586/. The rpms include the cross compiler, debugger, build tools for their RTOS....
They have an example in there documents which used 'rpm -U' for installation. Which I used, but the documents didn't describe the RPM dependencies, I finally found the correct order of installation, at least I didn't get any error messages. I then went to the include directory to look at some of the .h files, there wasn't any, so I knew the installation failed. When installing the location ends up to be /opt/rtem-4.8/with many sub-directories.
Hi Mike, As Patrick suggested, 'rpm --help' will give you a quick snaphot/refresher of the most frequently used options. You might consider the procedure I use: - copy the new rpms into an empty working directory and cd into it - su + password to gain the appropriate permissions - rpm -Uhv *.rpm --test "U" will upgrade earlier versions (if they exist) or just install "h" gives you hash mark progress bars with percentage completion "v" is, of course, verbose mode (feedback) "--test" does a 'dry run'. Nothing is actually written to disk and it advises you of any conflicts or missing dependencies. When you finally get the 'mix' right, drop the "--test" and install. And don't forget to run 'ldconfig' and 'SuSEconfig' afterwards. hth & regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 12 November 2007 12:35, Mike.Friedrichs wrote:
... Which I used, but the documents didn't describe the RPM dependencies, I finally found the correct order of installation, at least I didn't get any error messages.
In addition to Carl's general suggestions on using "rpm," you should be aware that you don't have to install in (reverse) dependency (partial) order. You can simply supply all the RPM files to a single install or upgrade invocation of the rpm command. As far as what you know when rpm completes without diagnostics, it's really down to how carefully the packager determined the dependencies. If any were omitted, rpm will succeed but the software may not run, either at all or under certain circumstances. Naturally, the larger and more complex the package, the easier it is to make a mistake and the more room there is for sporadic or partial failures.
...
-- MikeF Houston, TX
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Anders Johansson -
Bryen -
Carl Hartung -
Mike.Friedrichs -
Patrick Shanahan -
Randall R Schulz