I'm running FC3 with its bundled samba 3.0.11-fc3, and I'm trying to
update to 3.0.14a. I've downloaded the rpms from samba.org, and (I
think) I've backed up the original samba installation--/etc/samba--and
I've stopped smb (I had to kill the smbd and nmbd processes;
"/etc/rc.d/init.d/smb stop" didn't work). I've also withdrawn
(make
uninstall) an earlier abortive attempt to install 3.0.14a from source.
However, when I run rpm -U samba-common-3.0.14a-1.i386.rpm (for
instance), I just get:
error: Failed dependencies:
samba-common = 0:3.0.8 is needed by (installed)
samba-3.0.8-0.pre1.3.i386
samba-common = 0:3.0.8 is needed by (installed)
samba-client-3.0.8-0.pre1.3.i38
I also get a Warning V3 DSA signature: NOKEY, but I think this is
relatively minor.
When I tried the -i switch, I got a long-ish list of conflicts with the
3.0.8 installation (no surprise there, I suppose).
What am I doing wrong?
Thanks for your help.
Eric Hines
FC3 uses rpm packages to mantain the system up to date. Im sorry to tell you that Fedora dosen't work this way, you just can't upgrade every single package coz every package needs a dependency. FC doesn't resolve this automatically. You should download every samba-*-3.0.14a-1.i386.rpm and install them to make this work. When you download every package, just rpm -Uvh samba*3.0.14a*rpm And everything maybe... maybe... works. But again, is Fedora... This is not a samba problem. Is a Fedora problem. E Hines wrote:> I'm running FC3 with its bundled samba 3.0.11-fc3, and I'm trying to > update to 3.0.14a. I've downloaded the rpms from samba.org, and (I > think) I've backed up the original samba installation--/etc/samba--and > I've stopped smb (I had to kill the smbd and nmbd processes; > "/etc/rc.d/init.d/smb stop" didn't work). I've also withdrawn (make > uninstall) an earlier abortive attempt to install 3.0.14a from source. > > However, when I run rpm -U samba-common-3.0.14a-1.i386.rpm (for > instance), I just get: > > error: Failed dependencies: > samba-common = 0:3.0.8 is needed by (installed) > samba-3.0.8-0.pre1.3.i386 > samba-common = 0:3.0.8 is needed by (installed) > samba-client-3.0.8-0.pre1.3.i38 > > > I also get a Warning V3 DSA signature: NOKEY, but I think this is > relatively minor. > > When I tried the -i switch, I got a long-ish list of conflicts with the > 3.0.8 installation (no surprise there, I suppose). > > What am I doing wrong? > > Thanks for your help. > > Eric Hines > >
> However, when I run rpm -U samba-common-3.0.14a-1.i386.rpm (for > instance), I just get: > > error: Failed dependencies: > samba-common = 0:3.0.8 is needed by (installed) > samba-3.0.8-0.pre1.3.i386 > samba-common = 0:3.0.8 is needed by (installed) > samba-client-3.0.8-0.pre1.3.i38The Samba packages on Fedora 3 should be installed like this: rpm -Uhv --nodeps /usr/src/redhat/RPMS/i386/samba-common-3.0.14a-1.i386.rpm rpm -Uhv /usr/src/redhat/RPMS/i386/samba-3.0.14a-1.i386.rpm rpm -Uhv /usr/src/redhat/RPMS/i386/samba-client-3.0.14a-1.i386.rpm Don't forget to backup /var/lib/samba/* and /etc/samba/* before the update and after the shutdown of all samba deamons. Alex.
Guys .... the easiest method I have used it rpm -Fvh *.rpm This will only upgrade the packages you already have.... rather than either forcing the trash of the rpm database or doing a lot of typing... Good luck, MJ Barber -----Original Message----- From: samba-bounces+mjbarber=hearst.com@lists.samba.org [mailto:samba-bounces+mjbarber=hearst.com@lists.samba.org] On Behalf Of pgienger@ae-solutions.com Sent: Tuesday, April 19, 2005 9:42 AM To: a.vaal@nh-hotels.com Cc: samba@lists.samba.org Subject: Re: [Samba] Can't Install Samba 3.0.14a>The Samba packages on Fedora 3 should be installed like this: > >rpm -Uhv --nodeps/usr/src/redhat/RPMS/i386/samba-common-3.0.14a-1.i386.rpm>rpm -Uhv /usr/src/redhat/RPMS/i386/samba-3.0.14a-1.i386.rpm >rpm -Uhv /usr/src/redhat/RPMS/i386/samba-client-3.0.14a-1.i386.rpm > > >GAAAAHH!!!! NO!!! nodeps is bad. Why don't you just try installing everything with the --force flag, since that's what you're doing basically, throwing the integrity of the rpm database right out the window. Put all the packages on one rpm line and you'll be fine. That allows rpm to figure out for itself that you've got your ducks in a row and trust that if it does just what you said everything will be all right. Turning rant off for a second, there is one place where a --nodeps or even a --force is useful. When you do a yum upgrade you need to push a couple packages (like rpm itself) in really hard to get it to kick off right, but that's a pretty specific situation where you're upgrading pretty much everything on the system anyway. On a regular package and a functioning system, --nodeps is a no-no, especially if you don't know why you want to use it in the first place.>Don't forget to backup /var/lib/samba/* and /etc/samba/* before theupdate>and after the >shutdown of all samba deamons. > >Alex. > > > >-- Paul Gienger Office: 701-281-1884 Applied Engineering Inc. Systems Architect Fax: 701-281-1322 URL: www.ae-solutions.com mailto: pgienger@ae-solutions.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba