Spec URL: http://melmorabity.fedorapeople.org/packages/ktikz/ktikz.spec SRPM URL: http://melmorabity.fedorapeople.org/packages/ktikz/ktikz-0.10-1.fc14.src.rpm Description: KTikZ and Qtikz are small applications to assist in the creation of diagrams and drawings using the TikZ macros from the LaTeX package "pgf". They consist of a text editor pane in which the TikZ code for the drawing is edited and a preview pane showing the drawing as rendered by LaTeX. The preview pane can be updated in real-time. Common drawing tools, options and styles are available from the menus to assist the coding process. Note that this package provides two versions of the same program: - qtikz, a QT desktop-independant version, - ktikz, a KDE-integrated version, with a KPart. Build logs: http://koji.fedoraproject.org/koji/taskinfo?taskID=2598104 rpmlint runs silently on all RPMs (except false-positive spelling issues).
Any example file to test?
(In reply to comment #1) > Any example file to test? Sure. Any example avaible in the 320-page PGF manual, in /usr/share/texmf/doc/generic/pgf/version-for-pdftex/en/pgfmanual.pdf
Ah, 175M to download. This will take a while.
OK, here is. "+" - OK, "0" - not require. [+]: rpmlint is almost silent but wrong possitive spelling warning. [+]: The package must be named according to the Package Naming Guidelines . [+]: The spec file name must match the base package %{name}. [+]: The package must meet the Packaging Guidelines . [+]: The package must be licensed with a Fedora approved license and meet the Licensing Guidelines . [+]: The License field in the package spec file must match the actual license. [+]: File, containing the text of the license(s) for the package, included in %doc. [+]: The spec file must be written in American English. [+]: The spec file for the package MUST be legible. [+]: The sources used to build the package must match the upstream source, as provided in the spec URL. [+]: The package MUST successfully compile and build into binary rpms on at least one primary architecture. [0]: If the package does not successfully compile, build or work on an architecture, then those architectures should be listed in the spec in ExcludeArch. [+]: All build dependencies must be listed in BuildRequires. [+]: The spec file MUST handle locales properly. [0]: 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. [+]: Packages must NOT bundle copies of system libraries. [0]: If the package is designed to be relocatable, the packager must state this fact in the request for review. [+]: A package must own all directories that it creates. [+]: 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) [+]: Permissions on files must be set properly. [+]: Each package must consistently use macros. [+]: The package must contain code, or permissable content. [0]: Large documentation files must go in a -doc subpackage. [+]: If a package includes something as %doc, it must not affect the runtime of the application. [0]: Header files must be in a -devel package. [0]: Static libraries must be in a -static package. [0]: 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. [0]: In the vast majority of cases, devel packages must require the base package using a fully versioned dependency: Requires: %{name} = %{version}-%{release}. [+]: Packages must NOT contain any .la libtool archives, these must be removed in the spec if they are built. [+]: 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. [+]: Packages must not own files or directories already owned by other packages. [+]: All filenames in rpm packages must be valid UTF-8. SHOULD Items: [+] The reviewer should test that the package builds in mock. [+] The package should compile and build into binary rpms on all supported architectures. [+] The reviewer should test that the package functions as described. A package should not segfault instead of running, for example. [+] If scriptlets are used, those scriptlets must be sane. [+] your package should contain man pages for binaries/scripts. /===========/ / APPROVED. / /===========/
Thanks for your efficient review :)
New Package SCM Request ======================= Package Name: ktikz Short Description: Editor for the TikZ language Owners: melmorabity Branches: f13 f14 InitialCC:
Git done (by process-git-requests).
ktikz-0.10-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/ktikz-0.10-1.fc14
ktikz-0.10-1.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/ktikz-0.10-1.fc13
ktikz-0.10-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update ktikz'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/ktikz-0.10-1.fc13
ktikz-0.10-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
ktikz-0.10-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.