seems there is a bug in the script that make the rpmsrate from the rpmsrate_raw http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/media/media_info/rpmsrate at least the 4 commits are still here: http://svnweb.mageia.org/packages/cauldron/meta-task/current/SOURCES/rpmsrate-raw?r1=276485&r2=287501
Priority: Normal => release_blockerCC: (none) => ennael1, thierry.vignaud
CC: (none) => pterjan
I've not access to the build machines
CC: thierry.vignaud => (none)
Was a meta-task package updated with those commits? The file is extracted from the package when it gets uploaded
There is indeed a problem rpmsrate 31-Aug-2012 05:44 25K rpmsrate-raw 03-Sep-2012 04:58 22K
FATAL: too complicated flags for duplicate entry ibus-table-cangjie (CAT_X LOCALES"zh_HK" and CAT_X LOCALES"zh_TW" at /usr/lib/perl5/vendor_perl/5.12.3/MGATools/rpmsrate.pm line 164, <$A> line 829.
This should fix it: @@ -614,8 +614,9 @@ 5 LOCALES"am" || LOCALES"as" || LOCALES"bn" || LOCALES"hi" || LOCALES"gu" || LOCALES"km" || LOCALES"kn" || LOCALES"ml" || LOCALES"mr" || LOCALES"ne" || LOCALES"pa_IN" || LOCALES"ta" || LOCALES"th" || LOCALES"vi" || LOCALES"dz" ibus-m17n 5 LOCALES"th" ibus-table-thai 5 LOCALES"zh_CN" ibus-pinyin ibus-table-wubi - 5 LOCALES"zh_TW" ibus-chewing ibus-table-cangjie - 5 LOCALES"zh_HK" ibus-cantonese ibus-table-cangjie + 5 LOCALES"zh_TW" || LOCALES"zh_HK" ibus-table-cangjie + 5 LOCALES"zh_TW" ibus-chewing + 5 LOCALES"zh_HK" ibus-cantonese 5 CAT_KDE LOCALES"am" || LOCALES"as" || LOCALES"bn" || LOCALES"gu" || LOCALES"hi" || LOCALES"ja" || LOCALES"km" || LOCALES"kn" || LOCALES"ko" || LOCALES"ml" || LOCALES"mr" || LOCALES"ne" || LOCALES"pa_IN" || LOCALES"ta" || LOCALES"th" || LOCALES"vi" || LOCALES"zh" || LOCALES"zh_TW" ibus-qt4 plasma-applet-kimpanel-backend-ibus 5 LOCALES"et" esteid-browser-plugin qdigidoc qesteidutil But this should be caught at build time
Submitted a fix to rpmsrate-raw + an additional check at build time. It would be better to have clean-rpmsrate to use drakx code...
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
thanks