[opensuse-factory] Re: Seems some macros are broken in Factory
On Wednesday 18 January 2012 02:05:01 Ilya Chernykh wrote:
For example, this line leads to fail of packages in Factory:
%{?suse_update_config:%{suse_update_config -f}}
This makes ALL pachages break. All that use this macro.
also the %configure macro is broken: it tries to patch the configure file for 64-bit library paths but incorrectly. For example it changes the Qt3 directory on 64-architecture from /usr/lib to /usr/lib64 which is incorrect (Qt3 directory is always /usr/lib with libraries go to either /usr/lib/qt3/lib or /usr/lib/qt3/lib64).
Please correct the macros.
This problem is actually with macro %suse_update_libdir -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 17/01/12 19:24, Ilya Chernykh wrote:
On Wednesday 18 January 2012 02:05:01 Ilya Chernykh wrote:
For example, this line leads to fail of packages in Factory:
%{?suse_update_config:%{suse_update_config -f}}
This makes ALL pachages break. All that use this macro.
Expected, this macro is going away, you have to fix your packages not to call that very old kludge (actually from SUSE 7.x (!!!) )
This problem is actually with macro %suse_update_libdir
There is nothing broken there.. your spec files are ..though. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 18 January 2012 02:29:25 Cristian Rodríguez wrote:
Expected, this macro is going away, you have to fix your packages not to call that very old kludge (actually from SUSE 7.x (!!!) )
This problem is actually with macro %suse_update_libdir
There is nothing broken there.. your spec files are ..though.
Look here what it doees (according the build log): @@ -1474,11 +1474,11 @@ --with-qmake=BIN Use specific qmake binary with the absolute path. (only for platforms where qmake is not installed under QTDIR/bin, /usr/bin, /usr/local/bin, - /usr/lib/qt3/bin or in PATH). + /usr/lib64/qt3/bin or in PATH). --with-lrelease=BIN Use specific lrelease binary with the absolute path. (Only for platforms where lrelease is not installed under QTDIR/bin, /usr/bin, /usr/local/bin, - /usr/lib/qt3/bin or in PATH). + /usr/lib64/qt3/bin or in PATH). --with-root-dir=DIR Install files under different root directory (path to prepend before the prefix, empty by default - use if you are packager and want to create package, or This is COMPLETELY incorrect, because qt3 IS NOT in /usr/lib64/qt3 but in /usr/lib/qt3 even on a 64-bit architecture. The script just changes any occurrence of /lib to /lib64. Without using this macro all works well.
On 17/01/12 19:38, Ilya Chernykh wrote:
Without using this macro all works well.
..And that's exactly why you should not call %suse_update_libdir or %suse_update_config in the first place.. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 18 January 2012 02:42:41 Cristian Rodríguez wrote:
Without using this macro all works well.
..And that's exactly why you should not call %suse_update_libdir or %suse_update_config in the first place..
On 12.1 all works well... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 17/01/12 19:44, Ilya Chernykh wrote:
On Wednesday 18 January 2012 02:42:41 Cristian Rodríguez wrote:
Without using this macro all works well.
..And that's exactly why you should not call %suse_update_libdir or %suse_update_config in the first place..
On 12.1 all works well...
Yeah, that's because this macros have been altered for future versions (factory, 12.2...) it is not a bug, just a big hammer against obsolete workarounds. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 18 January 2012 03:22:44 Cristian Rodríguez wrote:
Yeah, that's because this macros have been altered for future versions (factory, 12.2...) it is not a bug, just a big hammer against obsolete workarounds.
What's the purpose of %suse_update_libdir if it does nt update the dirs correctly? What's the purpose of %suse_update_config if it breaks ALL packages? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 17/01/12 20:28, Ilya Chernykh wrote:
What's the purpose of %suse_update_libdir if it does nt update the dirs correctly?
What's the purpose of %suse_update_config if it breaks ALL packages?
Break packages so they are updated by their respective maintainers ? :-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 18 January 2012, Cristian Rodríguez wrote:
On 17/01/12 19:44, Ilya Chernykh wrote:
On Wednesday 18 January 2012 02:42:41 Cristian Rodríguez wrote:
Without using this macro all works well.
..And that's exactly why you should not call %suse_update_libdir or %suse_update_config in the first place..
On 12.1 all works well...
Yeah, that's because this macros have been altered for future versions (factory, 12.2...) it is not a bug, just a big hammer against obsolete workarounds.
But actually it's not done by "big hammer". It prints only a warning now and does someting random instead. Better take the big hammer please and remove it completely. cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Cristian Rodríguez -
Ilya Chernykh -
Ruediger Meier