Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=953101 --- Comment #57 from Kevin Kofler <kevin@xxxxxxxxxxxxxxxx> --- > http://kojipkgs.fedoraproject.org//work/tasks/2314/5332314/build.log > /usr/share/razor/razor-config/razor-config-appearance_sr@xxxxxxxx > /usr/share/razor/razor-panel/razor-panel_sr@xxxxxxxx Well, it's a bug in %find_lang that it doesn't find those files. Just list them manually, they're just 2 files: %lang(sr) %{_datadir}/razor/razor-config/razor-config-appearance_sr@xxxxxxxx %lang(sr) %{_datadir}/razor/razor-panel/razor-panel_sr@xxxxxxxx (Use %lang(sr) to tag them.) > I'd like to choose something one - "section > subpackage" or "package > > section" order. In 2nd case I'm to put package > %description > %files > (together). I prefere _strict_ "section > subpackage" order, sorry. Almost all packages in Fedora use the ordering as in: http://pkgs.fedoraproject.org/cgit/qt.git/tree/qt.spec In other words: Definition of the main package %description %package foo1 %description foo1 %package foo2 %description foo2 … %package fooN %description fooN %prep %build %install %check (if used) %clean (if used) %pre/%post/%preun/%postun/%posttrans (for the main package) as needed %pre/%post/%preun/%postun/%posttrans foo1 as needed %pre/%post/%preun/%postun/%posttrans foo2 as needed … %pre/%post/%preun/%postun/%posttrans fooN as needed %files %files foo1 %files foo2 … %files fooN %changelog I see no valid reason to do this differently. It's much easier to read other people's specfiles if they all use the agreed ordering. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=yTvMCA8DIL&a=cc_unsubscribe _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review