On Mon, Dec 5, 2011 at 3:44 PM, Claudio Freire
On Mon, Dec 5, 2011 at 11:40 AM, todd rme
wrote: Usually not, because the python 2 and python 3 versions are generally different (for instance a script that calls python 2 versus a script that calls python 3). fdupes only finds, and is only useful for, files that are identical.
Ok, but the warning isn't triggered either if the files are different.
Or are they talking of changing that?
I think you are thinking of a different issue. What I am talking about is not the rpmlint fdupes warning. Rather, it is an error that occurs when two sub-packages of the same package both own a file with the same name but do not conflict with each other. To provide a relevant example, both the python2 and python3 versions of python-cx_freeze create the file /usr/bin/cxfreeze. If you try to create a package that builds python2 and python3 subpackages for python-cx_freeze, the build will fail because they both contain a file with that name. The only wat to avoid the error is to make the subpackages conflict (which I have done temporarily), but this defeats the purpose of having python2 and python3 both available. There is talk about expanding this so that there is an error even if they are not subpackages of the same package, which will break a lot of existing python3 packages as well. The only way to avoid this error is to rename one or both packages, move one or both packages, or rename and move them. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org