> Date: Sat, 22 Apr 2006 23:35:01 -0800
> From: "Kam Leo" <kam.leo@xxxxxxxxx>
> Subject: Re: gnome-vfs2-2.14.1-1.fc5.1.src.rpm spec file contains an
> error.
> To: "For users of Fedora Core releases" <fedora-list@xxxxxxxxxx>
> Message-ID:
> <f84880b00604230035r31e84762j874bf65f53260bd2@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 4/22/06, Ken Solomon <kensol@xxxxxxxxxxxxxx> wrote:
> > Hi everyone, I've just tried upgrading gnome-vfs2, gnome-vfs2-smb
> > and gnome-vfs2-devel RPM's through yum and got the following error,
> >
> > [ken@localhost SPECS]$ sudo yum update --disablerepo="*"
> > --enablerepo="fedora-updates-testing" gnome-vfs2 gnome-vfs2-smb
> > gnome-vfs2-devel Setting up Update Process Setting up repositories
> > fedora-updates-testing
> > [1/1] Reading repository metadata in from local files
> > Resolving Dependencies
> > --> Populating transaction set with selected packages. Please wait.
> > ---> Package gnome-vfs2-smb.i386 0:2.14.1-1.fc5.1 set to be updated
> > ---> Package gnome-vfs2-devel.i386 0:2.14.1-1.fc5.1 set to be
> > updated ---> Package gnome-vfs2.i386 0:2.14.1-1.fc5.1 set to be
> > updated --> Running transaction check
> > --> Processing Dependency: gnome-vfs2 = 2.14.1-1.fc5.1} for package:
> > gnome-vfs2-smb --> Finished Dependency Resolution
> > Error: Missing Dependency: gnome-vfs2 = 2.14.1-1.fc5.1} is needed by
> > package gnome-vfs2-smb
> >
> > I then downloaded the source RPM package and found a missing "{" in
> > the spec file,
> >
> > %package smb
> > Summary: Windows fileshare support for gnome-vfs
> > Group: System Environment/Libraries
> > Requires: %{name} = %{version}-%release} <-- missing "{"
> > Requires: samba-common >= %{samba_version}
> > Obsoletes: gnome-vfs2-extras
> > Provides: gnome-vfs2-extras
> >
> >
> > Apologies if this information has already been posted.
> >
> >
> > --
> > Ken <Registered Linux User #342812>
> >
>
> Is the package from updates-testing? If so you are reporting the error
> to the wrong list.
>
Yes it is from updates-testing. The latest update appears to have
fixed the problem. Sorry for reporting to this list, in future I'll be
sure to send a report to the relevant list. Thanks for your help.
--
Ken <Registered Linux User #342812>
