There have been a few packages I've wanted to install that have run into conflicts. In some cases, I've simply forced the install and haven't had any problems. In others, like my Google Earth debacle last week, I ended up with some pretty major problems that, thankfully, this list helped me fix.
Now, I want to work on building a few RPM's and I need to install the tools. But, when I try, I get an error saying there's a conflict with the filesystem package.
What is the appropriate way to resolve this?
Thanks! Anthony
On Sat, 8 Jun 2013 05:08:52 -0500, Anthony wrote:
There have been a few packages I've wanted to install that have run into conflicts. In some cases, I've simply forced the install and haven't had any problems. In others, like my Google Earth debacle last week, I ended up with some pretty major problems that, thankfully, this list helped me fix.
Now, I want to work on building a few RPM's and I need to install the tools. But, when I try, I get an error saying there's a conflict with the filesystem package.
What is the appropriate way to resolve this?
Avoid including any files which are included in other packages already: https://fedoraproject.org/wiki/Packaging:Guidelines#Conflicts
On 06/08/2013 05:13 AM, Michael Schwendt wrote:
On Sat, 8 Jun 2013 05:08:52 -0500, Anthony wrote:
There have been a few packages I've wanted to install that have run into conflicts. In some cases, I've simply forced the install and haven't had any problems. In others, like my Google Earth debacle last week, I ended up with some pretty major problems that, thankfully, this list helped me fix.
Now, I want to work on building a few RPM's and I need to install the tools. But, when I try, I get an error saying there's a conflict with the filesystem package.
What is the appropriate way to resolve this?
Avoid including any files which are included in other packages already: https://fedoraproject.org/wiki/Packaging:Guidelines#Conflicts
Excellent resource, thank you! So how should a conflict in an existing package be handled. For example, the filesystem conflict that Google Earth has? Should I simply not install the package and report the bug to Google?
Anthony
On Sat, 8 Jun 2013 05:37:28 -0500, Anthony wrote:
Avoid including any files which are included in other packages already: https://fedoraproject.org/wiki/Packaging:Guidelines#Conflicts
Excellent resource, thank you! So how should a conflict in an existing package be handled. For example, the filesystem conflict that Google Earth has?
It's a packaging mistake in the Google Earth package. That package must not include any file/directory (with different permission flags or different contents), which belongs into Fedora's "filesystem" package (or any other package).
https://fedoraproject.org/wiki/Packaging:Guidelines#File_and_Directory_Owner... and https://fedoraproject.org/wiki/Packaging:Conflicts#Implicit_Conflicts
Should I simply not install the package and report the bug to Google?
Yes.
As a work-around, you can examine the conflict and restore the directory permissions _after_ installing the package. Option --force also adds option --replacefiles, however, so be careful.
On 06/08/2013 06:26 AM, Michael Schwendt wrote:
On Sat, 8 Jun 2013 05:37:28 -0500, Anthony wrote:
Avoid including any files which are included in other packages already: https://fedoraproject.org/wiki/Packaging:Guidelines#Conflicts
Excellent resource, thank you! So how should a conflict in an existing package be handled. For example, the filesystem conflict that Google Earth has?
It's a packaging mistake in the Google Earth package. That package must not include any file/directory (with different permission flags or different contents), which belongs into Fedora's "filesystem" package (or any other package).
https://fedoraproject.org/wiki/Packaging:Guidelines#File_and_Directory_Owner...
and
https://fedoraproject.org/wiki/Packaging:Conflicts#Implicit_Conflicts
Should I simply not install the package and report the bug to Google?
Yes.
As a work-around, you can examine the conflict and restore the directory permissions _after_ installing the package. Option --force also adds option --replacefiles, however, so be careful.
Thank you, Michael. Answered all of my questions and I'm much more comfortable working with packages now :-)
Anthony
On Sat, 8 Jun 2013, Michael Schwendt wrote:
On Sat, 8 Jun 2013 05:37:28 -0500, Anthony wrote:
Avoid including any files which are included in other packages already: https://fedoraproject.org/wiki/Packaging:Guidelines#Conflicts
Excellent resource, thank you! So how should a conflict in an existing package be handled. For example, the filesystem conflict that Google Earth has?
It's a packaging mistake in the Google Earth package. That package must not include any file/directory (with different permission flags or different contents), which belongs into Fedora's "filesystem" package (or any other package).
https://fedoraproject.org/wiki/Packaging:Guidelines#File_and_Directory_Owner... and https://fedoraproject.org/wiki/Packaging:Conflicts#Implicit_Conflicts
Should I simply not install the package and report the bug to Google?
Yes.
As a work-around, you can examine the conflict and restore the directory permissions _after_ installing the package. Option --force also adds option --replacefiles, however, so be careful.
Here's an explanation of how to fix the Google Earth problem (use rpmrebuild): http://0-productforums.google.com.library.ccbcmd.edu/forum/#!topic/earth/XNN...
fyi,
Max Pyziur pyz@brama.com
-
Anthony -
Max Pyziur -
Michael Schwendt