Picasa install error fed21

[Paul Cartwright]

trying to install picasa-3.0.5744-3.i386.rpm
on fedora 21 x86_64.

I get this error:
Transaction check error:
  file / from install of picasa-3.0.5744-3.i386 conflicts with file from
package filesystem-3.2-28.fc21.x86_64
  file /usr/bin from install of picasa-3.0.5744-3.i386 conflicts with
file from package filesystem-3.2-28.fc21.x86_64
  file /usr/lib from install of picasa-3.0.5744-3.i386 conflicts with
file from package filesystem-3.2-28.fc21.x86_64

I googled & found a similar error and it said to use rpm -U --force..
not sure if that is a good idea when the package is filesystem

[Tim]

Allegedly, on or about 06 February 2015, Paul Cartwright sent:
> trying to install picasa-3.0.5744-3.i386.rpm
> on fedora 21 x86_64.
>
> I get this error:
> Transaction check error:
>   file / from install of picasa-3.0.5744-3.i386 conflicts with file from
> package filesystem-3.2-28.fc21.x86_64
>   file /usr/bin from install of picasa-3.0.5744-3.i386 conflicts with
> file from package filesystem-3.2-28.fc21.x86_64
>   file /usr/lib from install of picasa-3.0.5744-3.i386 conflicts with
> file from package filesystem-3.2-28.fc21.x86_64
>
> I googled & found a similar error and it said to use rpm -U --force..
> not sure if that is a good idea when the package is filesystem

Sounds like the same tomfoolery involved with installing google-earth,
it wants to own a system directory (/usr/bin) that it has no business
doing.

There was a thread about that, about one or two weeks ago, that I
followed to force google-earth into installing without stomping on
system directories, using rpmrebuild on google-earth to change its
demands.  Here's that message:

https://lists.fedoraproject.org/pipermail/users/2015-January/457944.html

You could try using it as a template, and look for the three system
filepaths your error threw up, and do the same trick with them.

NB:  Look through the report you get on the work it does, it'll say
where the newly built RPM is located.

The issue has been around for a long time, and I don't know why google
doesn't fix their broken packages, instead of expecting users to kludge
things, other than sheer arrogance.

[Paul Cartwright]

On 02/06/2015 11:06 PM, Tim wrote:
> There was a thread about that, about one or two weeks ago, that I
> followed to force google-earth into installing without stomping on
> system directories, using rpmrebuild on google-earth to change its
> demands.  Here's that message:

I saw that, but I just used --replacefiles and it worked..

[Tim]

Tim:
> > There was a thread about that, about one or two weeks ago, that I
> > followed to force google-earth into installing without stomping on
> > system directories, using rpmrebuild on google-earth to change its
> > demands.  Here's that message:

Paul Cartwright:
> I saw that, but I just used --replacefiles and it worked..

Oooh, but I wouldn't feel confident sweeping something like that under
the carpet.  Those are system directories that it has no business
interfering with.  I'd be far more inclined to do the opposite, have it
install what it can, and omit what fails.

[Paul Cartwright]

On 02/07/2015 07:48 AM, Tim wrote:
> > > I saw that, but I just used --replacefiles and it worked..
>
> Oooh, but I wouldn't feel confident sweeping something like that under
> the carpet.  Those are system directories that it has no business
> interfering with.  I'd be far more inclined to do the opposite, have it
> install what it can, and omit what fails.

too late, already done, and picasa is working.. hopefully so is
everything else:)

[Michael Schwendt]

On Sat, 07 Feb 2015 08:02:33 -0500, Paul Cartwright wrote:
> On 02/07/2015 07:48 AM, Tim wrote:
> > > > I saw that, but I just used --replacefiles and it worked..
> >
> > Oooh, but I wouldn't feel confident sweeping something like that under
> > the carpet.  Those are system directories that it has no business
> > interfering with.  I'd be far more inclined to do the opposite, have it
> > install what it can, and omit what fails.
>
> too late, already done, and picasa is working.. hopefully so is
> everything else:)

Still you might want to check the permissions/ownership of those
directories and compare them with the "filesystem" package. A directory
conflict at install-time is because of permissions/ownership being
different. => It could be anything like making a directory world-writable!

rpm -V filesystem
  rpm --setperms filesystem
  rpm -V filesystem

[Paul Cartwright]

On 02/08/2015 06:59 AM, Michael Schwendt wrote:
> Still you might want to check the permissions/ownership of those
> directories and compare them with the "filesystem" package. A directory
> conflict at install-time is because of permissions/ownership being
> different. => It could be anything like making a directory world-writable!
>
> rpm -V filesystem

# rpm -V filesystem
.........    / (replaced)
.........    /usr/bin (replaced)
.........    /usr/lib (replaced)
> rpm --setperms filesystem

scrolled a huge list of files...
chmod: cannot access ‘/usr/share/man/zza/man9’: No such file or directory
chmod: cannot access ‘/usr/share/man/zza/man9x’: No such file or directory
chmod: cannot access ‘/usr/share/man/zza/mann’: No such file or directory
> rpm -V filesystem

# rpm -V filesystem
.........    / (replaced)
.........    /usr/bin (replaced)
.........    /usr/lib (replaced)