Spec URL: http://people.gnome.org/~icq/gtranslator.spec SRPM URL: http://people.gnome.org/~icq/gtranslator-2.90.6-1.fc16.src.rpm Description: gtranslator is an enhanced gettext po file editor for the GNOME desktop environment. It handles all forms of gettext po files and features many comfortable everyday usage features like find and replace functions, auto translation, and translation learning,
For what I can read in the dead.package it was retired because it was building, not sure why, as here it builds correctly. See: http://koji.fedoraproject.org/koji/taskinfo?taskID=3425037
gtranslator.x86_64: W: spelling-error Summary(en_US) Gettext -> Get text, Get-text, Georgette gtranslator.x86_64: W: spelling-error Summary(en_US) po -> PO, pew, op gtranslator.x86_64: W: spelling-error %description -l en_US gettext -> get text, get-text, Georgette gtranslator.x86_64: W: spelling-error %description -l en_US po -> PO, pew, op gtranslator.x86_64: E: postin-without-ldconfig /usr/lib64/libgtranslator-private.so.0.0.0 gtranslator.x86_64: E: postun-without-ldconfig /usr/lib64/libgtranslator-private.so.0.0.0 gtranslator.x86_64: W: devel-file-in-non-devel-package /usr/lib64/libgtranslator-private.so I guess that this 3 previous warnings are the important ones. gtranslator.x86_64: E: incorrect-fsf-address /usr/lib64/gtranslator/plugins/charmap/__init__.py gtranslator.x86_64: E: incorrect-fsf-address /usr/lib64/gtranslator/plugins/charmap/panel.py gtranslator-devel.x86_64: E: incorrect-fsf-address /usr/include/gtranslator-3.0/gtranslator/gtr-tab-activatable.h gtranslator-devel.x86_64: E: incorrect-fsf-address /usr/include/gtranslator-3.0/gtranslator/gtr-header.h gtranslator-devel.x86_64: E: incorrect-fsf-address /usr/include/gtranslator-3.0/gtranslator/gtr-profile.h gtranslator-devel.x86_64: E: incorrect-fsf-address /usr/include/gtranslator-3.0/gtranslator/gtr-statusbar.h gtranslator-devel.x86_64: E: incorrect-fsf-address /usr/include/gtranslator-3.0/gtranslator/gtr-window-activatable.h Is this important?
Just for the sake I just updated the fsf addresses.
Just updated the spec file (same links) and this is the result: gtranslator.x86_64: W: spelling-error Summary(en_US) Gettext -> Get text, Get-text, Georgette gtranslator.x86_64: W: spelling-error Summary(en_US) po -> PO, pew, op gtranslator.x86_64: W: spelling-error %description -l en_US gettext -> get text, get-text, Georgette gtranslator.x86_64: W: spelling-error %description -l en_US po -> PO, pew, op These warnings are fine. gtranslator.x86_64: E: incorrect-fsf-address /usr/lib64/gtranslator/plugins/charmap/__init__.py gtranslator.x86_64: E: incorrect-fsf-address /usr/lib64/gtranslator/plugins/charmap/panel.py gtranslator-devel.x86_64: E: incorrect-fsf-address /usr/include/gtranslator-3.0/gtranslator/gtr-tab-activatable.h gtranslator-devel.x86_64: E: incorrect-fsf-address /usr/include/gtranslator-3.0/gtranslator/gtr-header.h gtranslator-devel.x86_64: E: incorrect-fsf-address /usr/include/gtranslator-3.0/gtranslator/gtr-profile.h gtranslator-devel.x86_64: E: incorrect-fsf-address /usr/include/gtranslator-3.0/gtranslator/gtr-statusbar.h gtranslator-devel.x86_64: E: incorrect-fsf-address /usr/include/gtranslator-3.0/gtranslator/gtr-window-activatable.h 2 packages and 1 specfiles checked; 7 errors, 4 warnings. This is already fixed upstream.
+ MUST: rpmlint must be run on the source rpm and all binary rpms the build produces. The output should be posted in the review. gtranslator.src: W: strange-permission gtranslator-2.90.6.tar.xz 0444L A file that you listed to include in your package has strange permissions. Usually, a file should have 0644 permissions. Probably nothing we should be bothered with. + MUST: The package must be named according to the Package Naming Guidelines. There is a conflict with already existing package node, so rename is allowed. + MUST: The spec file name must match the base package %{name}, in the format %{name}.spec unless your package has an exemption. + MUST: The package must meet the Packaging Guidelines. ? MUST: The package must be licensed with a Fedora approved license and meet the Licensing Guidelines. + MUST: The License field in the package spec file must match the actual license. + MUST: If (and only if) the source package includes the text of the license(s) in its own file, then that file, containing the text of the license(s) for the package must be included in %doc. + MUST: The spec file must be written in American English. + MUST: The spec file for the package MUST be legible. + MUST: The sources used to build the package must match the upstream source, as provided in the spec URL. Reviewers should use md5sum for this task. If no upstream URL can be specified for this package, please see the Source URL Guidelines for how to deal with this. MD5SUM: 932deb32204bbce2ac4d45f3aa18d8b3 + MUST: The package MUST successfully compile and build into binary rpms on at least one primary architecture. Builds in koji http://koji.fedoraproject.org/koji/taskinfo?taskID=3428437 + MUST: If the package does not successfully compile, build or work on an architecture, then those architectures should be listed in the spec in ExcludeArch. Each architecture listed in ExcludeArch MUST have a bug filed in bugzilla, describing the reason that the package does not compile/build/work on that architecture. The bug number MUST be placed in a comment, next to the corresponding ExcludeArch line. + MUST: All build dependencies must be listed in BuildRequires, except for any that are listed in the exceptions section of the Packaging Guidelines ; inclusion of those as BuildRequires is optional. Apply common sense. Builds in koji. + MUST: The spec file MUST handle locales properly. This is done by using the %find_lang macro. Using %{_datadir}/locale/* is strictly forbidden. + MUST: Every binary RPM package (or subpackage) which stores shared library files (not just symlinks) in any of the dynamic linker's default paths, must call ldconfig in %post and %postun. + MUST: Packages must NOT bundle copies of system libraries. + MUST: If the package is designed to be relocatable, the packager must state this fact in the request for review, along with the rationalization for relocation of that specific package. Without this, use of Prefix: /usr is considered a blocker. + MUST: A package must own all directories that it creates. If it does not create a directory that it uses, then it should require a package which does create that directory. + MUST: A Fedora package must not list a file more than once in the spec file's %files listings. (Notable exception: license texts in specific situations) + MUST: Permissions on files must be set properly. Executables should be set with executable permissions, for example. + MUST: Each package must consistently use macros. + MUST: The package must contain code, or permissable content. + MUST: Large documentation files must go in a -doc subpackage. (The definition of large is left up to the packager's best judgement, but is not restricted to size. Large can refer to either size or quantity). + MUST: If a package includes something as %doc, it must not affect the runtime of the application. To summarize: If it is in %doc, the program must run properly if it is not present. + MUST: Header files must be in a -devel package. + MUST: Static libraries must be in a -static package. + MUST: If a package contains library files with a suffix (e.g. libfoo.so.1.1), then library files that end in .so (without suffix) must go in a -devel package. - MUST: In the vast majority of cases, devel packages must require the base package using a fully versioned dependency: Requires: %{name}%{?_isa} = %{version}-%{release} + MUST: Packages must NOT contain any .la libtool archives, these must be removed in the spec if they are built. + MUST: Packages containing GUI applications must include a %{name}.desktop file, and that file must be properly installed with desktop-file-install in the %install section. If you feel that your packaged GUI application does not need a .desktop file, you must put a comment in the spec file with your explanation. + MUST: Packages must not own files or directories already owned by other packages. The rule of thumb here is that the first package to be installed should own the files or directories that other packages may rely upon. This means, for example, that no package in Fedora should ever share ownership with any of the files or directories owned by the filesystem or man package. If you feel that you have a good reason to own a file or directory that another package owns, then please present that at package review time. + MUST: All filenames in rpm packages must be valid UTF-8. + SHOULD: If the source package does not include license text(s) as a separate file from upstream, the packager SHOULD query upstream to include it. + SHOULD: The description and summary sections in the package spec file should contain translations for supported Non-English languages, if available. + SHOULD: The reviewer should test that the package builds in mock. builds in koji + SHOULD: The package should compile and build into binary rpms on all supported architectures. + SHOULD: The reviewer should test that the package functions as described. A package should not segfault instead of running, for example. + SHOULD: If scriptlets are used, those scriptlets must be sane. This is vague, and left up to the reviewers judgement to determine sanity. + SHOULD: Usually, subpackages other than devel should require the base package using a fully versioned dependency. + SHOULD: The placement of pkgconfig(.pc) files depends on their usecase, and this is usually for development purposes, so should be placed in a -devel pkg. A reasonable exception is that the main pkg itself is a devel tool not installed in a user runtime, e.g. gcc or gdb. + SHOULD: If the package has file dependencies outside of /etc, /bin, /sbin, /usr/bin, or /usr/sbin consider requiring the package which provides the file instead of the file itself. + SHOULD: your package should contain man pages for binaries/scripts. If it doesn't, work with upstream to add them where they make sense. ------------ Please fix the issue with the Requires and %{?_isa} indicated above. Otherwise, I think, we are almost there.
Yes, all issues solved in the current package. APPROVED
New Package SCM Request ======================= Package Name: gtranslator Short Description: Gettext po file editor for GNOME Owners: nacho Branches: f16 InitialCC:
Unretired. Please take ownership in pkgdb, then submit a Package Change SCM request to add the f16 branch. Thanks!
Package Change Request ====================== Package Name: gtranslator New Branches: f16 Owners: nacho InitialCC:
am I suppose to take ownership in all branches? or just like I did with f15 and master is ok?
Git done (by process-git-requests). At least devel. Beyond that, whatever you feel like supporting.
3433093 build (dist-rawhide, /gtranslator:d1fd003d77823b7fa205194be5ebb0beff6b9b5a): open (x86-13.phx2.fedoraproject.org) -> FAILED: BuildError: package gtranslator is blocked for tag f17 I am getting this problem when building in f16 and rawhide. Is it maybe that you missed to setup something else?
What about closing this bug when the package is built? http://koji.fedoraproject.org/koji/packageinfo?packageID=12607
So after all, the comment was right, just bad URL http://koji.fedoraproject.org/koji/packageinfo?packageID=2012