Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: jabbim - Jabber client for mere mortals https://bugzilla.redhat.com/show_bug.cgi?id=426460 mmahut(a)redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|nobody(a)fedoraproject.org |mmahut(a)redhat.com Status|NEW |ASSIGNED Flag| |fedora-review? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: jabbim - Jabber client for mere mortals https://bugzilla.redhat.com/show_bug.cgi?id=426460 mcepl(a)redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmahut(a)redhat.com AssignedTo|mmahut(a)redhat.com |mcepl(a)redhat.com ------- Additional Comments From mcepl(a)redhat.com 2007-12-21 19:16 EST ------- MUST Items: 1. rpmlint must be run on every package. OK 2. The package must be named according to the Package Naming Guidelines OK 3. The spec file name must match the base package %{name}, in the format %{name}.spec OK 4. The spec file must be written in American English. OK 5. The spec file for the package MUST be legible. OK 6. Each package must consistently use macros, as described in the macros section of Packaging Guidelines OK 7. Each package must have a %clean section, which contains rm -rf %{buildroot} OK 8. The package must meet the Packaging Guidelines OK 9. The package must be licensed with an open-source compatible license and meet other legal requirements as defined in the Packaging Guidelines OK 10. The License field in the package spec file must match the actual license. OK 11. 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. OK 12. The package must contain code, or permissable content. This is described in detail in the code vs. content section of Packaging Guidelines. OK 13. 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. No, but diff -uNr doesn't find anything. Probably given by generating tarball out of SVN. OK 14. The package must successfully compile and build into binary rpms on at least one supported architecture. OK 15. All build dependencies must be listed in BuildRequires, except for any that are listed in the exceptions section of Packaging Guidelines; inclusion of those as BuildRequires is optional. Apply common sense. OK 16. If the package does not successfully compile, build or work on an architecture, then those architectures should be listed in the spec in ExcludeArch. OK 17. The spec file MUST handle locales properly. This is done by using the %find_lang macro. Using %{_datadir}/locale/* is strictly forbidden. OK 18. Every binary RPM package which stores shared library files (not just symlinks) in any of the dynamic linker's default paths, must call ldconfig in %post and %postun. OK 19. Non-relocatable? OK 20. A package must own all directories that it creates. NO!!! If I am not mistaken it acutally doesn't own %{jabbimdata} itself. Moreover, it might be more fruitful just to put into %files %{jabbimdata}/ and leave it at that. 21. A package must not contain any duplicate files in the %files listing. OK 22. Permissions on files must be set properly. OK 23. Large documentation files should go in a -doc subpackage. OK 24. 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. OK 25. Header files must be in a -devel package. #N/A 26. Static libraries must be in a -static package. #N/A 27. Packages containing pkgconfig(.pc) files must 'Requires: pkgconfig' (for directory ownership and usability). #N/A 28. 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. #N/A 29. In the vast majority of cases, devel packages must require the base package using a fully versioned dependency: Requires: %{name} = %{version}-%{release} #N/A 30. Packages must NOT contain any .la libtool archives, these should be removed in the spec. OK 31. 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. OK (no-GUI application, but library) 32. Packages must not own files or directories already owned by other packages. OK SHOULD Items: 1. If the source package does not include license text(s) as a separate file from upstream, the packager SHOULD query upstream to include it. OK (we have license) 2. The description and summary sections in the package spec file should contain translations for supported Non-English languages, if available. OK (we have none) 3. The reviewer should test that the package builds in mock. OK (built in koji) 4. The package should compile and build into binary rpms on all supported architectures. OK (built in koji and it is noarch) 5. The reviewer should test that the package functions as described. A package should not segfault instead of running, for example. OK 6. If scriptlets are used, those scriptlets must be sane. This is vague, and left up to the reviewers judgement to determine sanity. OK (no scriptlets) 7. Usually, subpackages other than devel should require the base package using a fully versioned dependency. OK (there are no other subpackages) 8. 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. OK (no pkgconfig) 9. 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. Please see File Dependencies in the Guidelines for further information. OK (no other dependencies) NOT APPROVED. Please, fix item 20. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: jabbim - Jabber client for mere mortals https://bugzilla.redhat.com/show_bug.cgi?id=426460 mcepl(a)redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Flag|fedora-review? |fedora-review+ ------- Additional Comments From mcepl(a)redhat.com 2007-12-22 17:53 EST ------- Looks good. APPROVED -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: jabbim - Jabber client for mere mortals https://bugzilla.redhat.com/show_bug.cgi?id=426460 kevin(a)tummy.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kevin(a)tummy.com Flag|fedora-cvs? |fedora-cvs+ ------- Additional Comments From kevin(a)tummy.com 2007-12-23 13:21 EST ------- Since you are installing an icon, perhaps you need to follow: http://fedoraproject.org/wiki/Packaging/ScriptletSnippets#head-7103f6c38d... Also, why the call to 'hardlink' ? You might want to address those before importing... cvs done. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: jabbim - Jabber client for mere mortals https://bugzilla.redhat.com/show_bug.cgi?id=426460 mschmidt(a)redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |NEXTRELEASE -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: jabbim - Jabber client for mere mortals https://bugzilla.redhat.com/show_bug.cgi?id=426460 kevin(a)tummy.com changed: What |Removed |Added ---------------------------------------------------------------------------- Flag|fedora-cvs? |fedora-cvs+ ------- Additional Comments From kevin(a)tummy.com 2008-01-03 23:20 EST ------- cvs done. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: jabbim - Jabber client for mere mortals https://bugzilla.redhat.com/show_bug.cgi?id=426460 kevin(a)tummy.com changed: What |Removed |Added ---------------------------------------------------------------------------- Flag|fedora-cvs? |fedora-cvs+ ------- Additional Comments From kevin(a)tummy.com 2008-01-05 13:12 EST ------- Oops. ;( Not sure how I got that confused there... Sorry about that. Would you like me to leave the EL-5 branch? Or would you prefer it be removed? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: jabbim - Jabber client for mere mortals https://bugzilla.redhat.com/show_bug.cgi?id=426460 ------- Additional Comments From a.badger(a)gmail.com 2008-01-09 01:46 EST ------- Done. The branch has been removed from cvs and marked removed in the pkgdb. It will still shows up on the jabbim page (with status Removed) until I fix the pkgdb to not display removed branches. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.