I just upgraded from RH9 to Fedora Core 1. I grabbed the Fedora apt RPM and did the appropriate rpm -U, and moved the new sources.list into place, since rpm told me it hadn't overwritten the old sources.list file. I then did "apt-get update" and, after it had grabbed the pertinent lists, it warned me that I had two (!) ntp RPMs installed: ntp-4.1.2-0.rc1.2 and ntp-4.1.2-5. I presume that 4.1.2-5 is the one I want to keep, but just out of idle curiosity, how did I end up with two?
James Jones
On Sat, 2003-11-15 at 04:35, James Jones wrote:
I just upgraded from RH9 to Fedora Core 1. I grabbed the Fedora apt RPM and did the appropriate rpm -U, and moved the new sources.list into place, since rpm told me it hadn't overwritten the old sources.list file. I then did "apt-get update" and, after it had grabbed the pertinent lists, it warned me that I had two (!) ntp RPMs installed: ntp-4.1.2-0.rc1.2 and ntp-4.1.2-5. I presume that 4.1.2-5 is the one I want to keep, but just out of idle curiosity, how did I end up with two?
James Jones
Maybe you did an 'rpm -i' instead of 'rpm -U' and the package did not properly replace the older package. Such thing can happen with testing releases, which is where you might have got you other rpm.
Nope. I had the same thing happen to me. I upgraded a RH9 installation and then fired up synaptic and it complained the same way. There were all sorts of little things having issues, however, so I ended up reinstalling FC1 clean on the root partition. This is definitely an upgrade issue, though I can't tell if it has something to do with apt/synaptic or just a RH9->FC1 upgrade.
-- Dave
On Fri, 2003-11-14 at 18:47, Maynard Kuona wrote:
On Sat, 2003-11-15 at 04:35, James Jones wrote:
I just upgraded from RH9 to Fedora Core 1. I grabbed the Fedora apt RPM and did the appropriate rpm -U, and moved the new sources.list into place, since rpm told me it hadn't overwritten the old sources.list file. I then did "apt-get update" and, after it had grabbed the pertinent lists, it warned me that I had two (!) ntp RPMs installed: ntp-4.1.2-0.rc1.2 and ntp-4.1.2-5. I presume that 4.1.2-5 is the one I want to keep, but just out of idle curiosity, how did I end up with two?
James JonesMaybe you did an 'rpm -i' instead of 'rpm -U' and the package did not properly replace the older package. Such thing can happen with testing releases, which is where you might have got you other rpm.
-- fedora-list mailing list fedora-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-list
On Fri, 2003-11-14 at 23:45, Dave Roberts wrote:
Nope. I had the same thing happen to me. I upgraded a RH9 installation and then fired up synaptic and it complained the same way. There were all sorts of little things having issues, however, so I ended up reinstalling FC1 clean on the root partition. This is definitely an upgrade issue, though I can't tell if it has something to do with apt/synaptic or just a RH9->FC1 upgrade.
Hit me on a 7.1->FC1 upgrade
Bret
Hmmm... interesting. Was your 7.1 a clean install, or had you mucked around with it a bit. On mine, I had things like Ximian's version of Evolution 1.4, etc. I know that Ximian's and FC1's packages were clashing a bit and was wondering if that could be it.
On Fri, 2003-11-14 at 22:01, Bret Hughes wrote:
On Fri, 2003-11-14 at 23:45, Dave Roberts wrote:
Nope. I had the same thing happen to me. I upgraded a RH9 installation and then fired up synaptic and it complained the same way. There were all sorts of little things having issues, however, so I ended up reinstalling FC1 clean on the root partition. This is definitely an upgrade issue, though I can't tell if it has something to do with apt/synaptic or just a RH9->FC1 upgrade.
Hit me on a 7.1->FC1 upgrade
Bret
-- fedora-list mailing list fedora-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-list
On Saturday 15 November 2003 05:45, Dave Roberts wrote:
Nope. I had the same thing happen to me. I upgraded a RH9 installation and then fired up synaptic and it complained the same way. There were all sorts of little things having issues, however, so I ended up reinstalling FC1 clean on the root partition. This is definitely an upgrade issue, though I can't tell if it has something to do with apt/synaptic or just a RH9->FC1 upgrade.
-- Dave
I didn't use apt/synaptic but rather the distributed ISO's to upgrade from RH9 to Fedora and ended up with both ntp rpms too. rpm -qa | grep ntp- ntp-4.1.2-5 ntp-4.1.2-0.rc1.2
Regards, Mike Klinke
On Sat, 2003-11-15 at 00:12, Dave Roberts wrote:
Hmmm... interesting. Was your 7.1 a clean install, or had you mucked around with it a bit. On mine, I had things like Ximian's version of Evolution 1.4, etc. I know that Ximian's and FC1's packages were clashing a bit and was wondering if that could be it.
On Fri, 2003-11-14 at 22:01, Bret Hughes wrote:
On Fri, 2003-11-14 at 23:45, Dave Roberts wrote:
Nope. I had the same thing happen to me. I upgraded a RH9 installation and then fired up synaptic and it complained the same way. There were all sorts of little things having issues, however, so I ended up reinstalling FC1 clean on the root partition. This is definitely an upgrade issue, though I can't tell if it has something to do with apt/synaptic or just a RH9->FC1 upgrade.
Hit me on a 7.1->FC1 upgrade
Bret
major mucking.
Bret
Mike Klinke wrote:
On Saturday 15 November 2003 05:45, Dave Roberts wrote:
Nope. I had the same thing happen to me. I upgraded a RH9 installation and then fired up synaptic and it complained the same way. There were all sorts of little things having issues,
check your upgrade.log search for *.rpmnew *.rpmsave on your system
however, so I ended up reinstalling FC1 clean on the root partition. This is definitely an upgrade issue, though I can't tell if it has something to do with apt/synaptic or just a RH9->FC1 upgrade.
I didn't use apt/synaptic but rather the distributed ISO's to upgrade from RH9 to Fedora and ended up with both ntp rpms too.
not here
rpm -qa | grep ntp- ntp-4.1.2-5 ntp-4.1.2-0.rc1.2
update via iso´s rhl 7.x -> 8 -> 9 -> fc1
# grep ^ntp upgrade.log ntp-4.1.2-5.i386 wird aktualisiert (upgrade is ok!)
# rpm -qa ntp* ntp-4.1.2-5 # rpm -qa | grep ntp- ntp-4.1.2-5
# grep ^ntp cd* cd1-fc1:ntp-4.1.2-5.i386.rpm cd1-fct3:ntp-4.1.2-4.1.i386.rpm cd1-rh73:ntp-4.1.1-1.i386.rpm cd1-rh80:ntp-4.1.1a-9.i386.rpm cd1-rh9:ntp-4.1.2-0.rc1.2.i386.rpm
On Saturday 15 November 2003 11:11, shrek-m@gmx.de wrote:
Mike Klinke wrote:
On Saturday 15 November 2003 05:45, Dave Roberts wrote:
Nope. I had the same thing happen to me. I upgraded a RH9 installation and then fired up synaptic and it complained the same way. There were all sorts of little things having issues,
check your upgrade.log search for *.rpmnew *.rpmsave on your system
Thanks for the suggestion. I didn't even consider that log! Here's an excerpt from mine:
========= upgrade.log ================ Upgrading ntp-4.1.2-5.i386. warning: /etc/ntp.conf created as /etc/ntp.conf.rpmnew error: %post(ntp-4.1.2-5) scriptlet failed, exit status 1
I installed FC1 on Nov 8th.
-rw-r--r-- 1 root root 2875 Nov 8 20:20 /etc/ntp.conf
-rw-r--r-- 1 root root 2798 Oct 29 11:07 /etc/ntp.conf.rpmnew
so the ntp update appears to have failed on my box. Is there a way to get the "scriptlet" mentioned above and run it in a way to see what's choking?
Regards, Mike Klinke
On Sat, 2003-11-15 at 03:11, shrek-m@gmx.de wrote:
Mike Klinke wrote:
check your upgrade.log search for *.rpmnew *.rpmsave on your system
Already wiped my entire root partition with the new install. Sorry.
however, so I ended up reinstalling FC1 clean on the root partition. This is definitely an upgrade issue, though I can't tell if it has something to do with apt/synaptic or just a RH9->FC1 upgrade.
I didn't use apt/synaptic but rather the distributed ISO's to upgrade from RH9 to Fedora and ended up with both ntp rpms too.
not here
rpm -qa | grep ntp- ntp-4.1.2-5 ntp-4.1.2-0.rc1.2
update via iso´s rhl 7.x -> 8 -> 9 -> fc1
Just so we're clear on trying to diagnose this issue, my upgrade was from iso's. I only fired up synaptic to check if Freshrpms.net had done anything with Fedora yet (I actually forget to change any of my apt config, so it looked at the RH9 repository on Freshrpms, but I never got as far as installing anything).
The point is, I think the iso upgrade messed things up a bit, with synaptic just being the thing that actually caught the problem and informed me about it.
The only thing that I had really done that was not stock on my system was to install the Ximian version of Evolution 1.4 (which did a bit of surgery under the covers on all sorts of stuff), and install apt/synaptic, with some rpms from Freshrpms.net (like Totem, etc.). I don't think that has anything to do with this issue, though. It sounds like a generic upgrade issue for FC1, coming from multiple distributions (Brett coming from RH7.x and me from RH9).
I didn't use apt/synaptic but rather the distributed ISO's to upgrade from RH9 to Fedora and ended up with both ntp rpms too. rpm -qa | grep ntp- ntp-4.1.2-5 ntp-4.1.2-0.rc1.2
Regards, Mike Klinke
$ rpm -e ntp-4.1.2-0.rc1.2 then just to make sure... $ rpm -V ntp-4.1.2-5 if there are problems - remove them bouth and install the new one
On Fri, 14 Nov 2003, Dave Roberts wrote:
Nope. I had the same thing happen to me. I upgraded a RH9 installation and then fired up synaptic and it complained the same way. There were all sorts of little things having issues, however, so I ended up reinstalling FC1 clean on the root partition. This is definitely an upgrade issue, though I can't tell if it has something to do with apt/synaptic or just a RH9->FC1 upgrade.
I've had this happening with apt using apt to upgrade from RH8 to RH9. I found that on doing an rpm -Fvh on a load of files, I'd got loads of duplicates. Performing an rpm -Uvh on all the packages again cleared the problem.
jh
On Monday 17 November 2003 14:21, Doncho N. Gunchev wrote:
I didn't use apt/synaptic but rather the distributed ISO's to upgrade from RH9 to Fedora and ended up with both ntp rpms too. rpm -qa | grep ntp- ntp-4.1.2-5 ntp-4.1.2-0.rc1.2
Regards, Mike Klinke
$ rpm -e ntp-4.1.2-0.rc1.2 then just to make sure... $ rpm -V ntp-4.1.2-5 if there are problems - remove them bouth and install the new one
You're correct, I could do that but it might cure the symptom without determining the disease. I was hoping that someone could shed some light on the question of the "scriptlet" to see if we can determine what caused the error and perhaps get it fixed so others don't run into this problem.
Regards, Mike Klinke
On Monday 17 November 2003 14:21, Doncho N. Gunchev wrote:
I didn't use apt/synaptic but rather the distributed ISO's to upgrade from RH9 to Fedora and ended up with both ntp rpms too. rpm -qa | grep ntp- ntp-4.1.2-5 ntp-4.1.2-0.rc1.2
Regards, Mike Klinke
$ rpm -e ntp-4.1.2-0.rc1.2 then just to make sure... $ rpm -V ntp-4.1.2-5 if there are problems - remove them bouth and install the new one
You're correct, I could do that but it might cure the symptom without determining the disease. I was hoping that someone could shed some light on the question of the "scriptlet" to see if we can determine what caused the error and perhaps get it fixed so others don't run into this problem.
Regards, Mike Klinke
On Monday 17 November 2003 19:13, Mike Klinke wrote:
On Monday 17 November 2003 14:21, Doncho N. Gunchev wrote:
I didn't use apt/synaptic but rather the distributed ISO's to upgrade from RH9 to Fedora and ended up with both ntp rpms too. rpm -qa | grep ntp- ntp-4.1.2-5 ntp-4.1.2-0.rc1.2
Regards, Mike Klinke
$ rpm -e ntp-4.1.2-0.rc1.2 then just to make sure... $ rpm -V ntp-4.1.2-5 if there are problems - remove them bouth and install the new one
You're correct, I could do that but it might cure the symptom without determining the disease. I was hoping that someone could shed some light on the question of the "scriptlet" to see if we can determine what caused the error and perhaps get it fixed so others don't run into this problem.
Regards, Mike Klinke
I think it has something to do with the rpm bug that makes it lock and crash sometimes. Unfortunately it locks/crashes very rarely and is probably still not fixed. When I installed fedora core 1 at home I could not get rpmbuild working 1/2 days - it crashed just before packing all the files in the final .rpm :( The next day (maybe after I installed some binary packages) it started working by itself... and fortunately I have no problems till now... I had some more problems I'm trying to reproduce again... but no luck till now (ex: one package installed fine with DESTDIR=/tmp/zzz by hand, but tryed to install in / from rpmbuild regardles of the DESTDIR in the .spec file...).
-
Bret Hughes -
Dave Roberts -
Doncho N. Gunchev -
James Jones -
John Hodrien -
Maynard Kuona -
Mike Klinke -
shrek-m＠gmx.de