https://bugzilla.redhat.com/show_bug.cgi?id=1302504 Bug ID: 1302504 Summary: Review Request: elog - Weblog server and client Product: Fedora Version: rawhide Component: Package Review Severity: medium Priority: medium Assignee: nobody@xxxxxxxxxxxxxxxxx Reporter: rosser.bjr@xxxxxxxxx QA Contact: extras-qa@xxxxxxxxxxxxxxxxx CC: package-review@xxxxxxxxxxxxxxxxxxxxxxx Spec URL: https://tc01.fedorapeople.org/elog/elog.spec SRPM URL: https://tc01.fedorapeople.org/elog/elog-3.1.1-3.fc22.src.rpm Description: ELOG is part of a family of applications known as weblogs. Their general purpose is: 1. To make it easy for people to put information online in a chronological fashion, in the form of short, time-stamped text messages ("entries") with optional HTML markup for presentation, and optional file attachments (images, archives, etc.) 2. To make it easy for other people to access this information through a Web interface, browse entries, search, download files, and optionally add, update, delete or comment on entries. ELOG is a remarkable implementation of a weblog in at least two respects: 1. Its simplicity of use: you don't need to be a seasoned server operator and/or an experimented database administrator to run ELOG ; one executable file (under Unix or Windows), a simple configuration text file, and it works. No Web server or relational database required. It is also easy to translate the interface to the appropriate language for your users. 2. Its versatility: through its single configuration file, ELOG can be made to display an infinity of variants of the weblog concept. There are options for what to display, how to display it, what commands are available and to whom, access control, etc. Moreover, a single server can host several weblogs, and each weblog can be totally different from the rest. Fedora Account System Username: tc01 elog contains both a client ("elog") and server ("elogd"). I've chosen for the moment to put elog and its manpage in the elog-client subpackage; just installing "elog" installs the server (with a dependency on elog-client). This may be the wrong way to do it; but since the server seems to be the "main" part of the software it seemed more reasonable to me that the "elog" package should install said server. This package is currently available from COPR here if you want to test it: https://copr.fedorainfracloud.org/coprs/tc01/elog/. $ rpmlint ../RPMS/x86_64/elog-3.1.1-3.fc22.x86_64.rpm elog.x86_64: W: spelling-error Summary(en_US) Weblog -> Web log, Web-log, We blog elog.x86_64: W: spelling-error %description -l en_US weblogs -> we blogs, we-blogs, web logs elog.x86_64: W: spelling-error %description -l en_US weblog -> we blog, we-blog, web log elog.x86_64: W: invalid-url URL: https://midas.psi.ch/elog/ <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)> elog.x86_64: E: incorrect-fsf-address /usr/share/licenses/elog/COPYING elog.x86_64: E: script-without-shebang /usr/share/elog/themes/default/elog.css elog.x86_64: E: script-without-shebang /usr/share/elog/themes/default/tiny.css elog.x86_64: W: file-not-utf8 /usr/share/doc/elog/doc/strftime.txt elog.x86_64: E: script-without-shebang /usr/share/elog/themes/default/compact.css elog.x86_64: W: dangerous-command-in-%post chown 1 packages and 0 specfiles checked; 4 errors, 6 warnings. I notified upstream about the invalid FSF address; it's been fixed in git. The "dangerous command in post" is because the elog package creates and wants to run under an "elog" user, and then needs to chown its files to said user. Is there a better way to do this that won't produce that rpmlint output? elog had a bundled copy of ckeditor that I have removed and replaced with a symlink (that gets created in %post as well). -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review