[Bug 226466] Merge Review: system-config-printer

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Merge Review: system-config-printer


https://bugzilla.redhat.com/show_bug.cgi?id=226466





------- Additional Comments From panemade at gmail.com  2007-10-01 03:18 EST -------
With new updated SRPM,
rpmlint on RPM gave me
--------------------------------------------------
system-config-printer.i386: W: non-conffile-in-etc
/etc/xdg/autostart/redhat-print-applet.desktop
==> This can be ignored.

system-config-printer.i386: E: no-binary
==> ok as we need system-config-printer-libs as i386 package and we can't use
noarch type then in SPEC file.

system-config-printer.i386: W: conffile-without-noreplace-flag
/etc/security/console.apps/system-config-printer
===> Is this(noreplace) not needed?

system-config-printer.i386: W: dangerous-command-in-%post rm
==> Do you have any other workaround to avoid using rm?

rpmlint on --libs RPM gave me
---------------------------------------------------------
system-config-printer-libs.i386: W: spurious-executable-perm
/usr/share/doc/system-config-printer-libs-0.7.74.3/pycups-1.9.27/examples/cupstree.py
===> any reason to have this as valid. I saw most of packages installing example
 files with 0644 mode.

system-config-printer-libs.i386: E: non-executable-script
/usr/share/system-config-printer/cupshelpers.py 0644
===> This MUST be solved. As you said its upstream. Can you provide a new SRPM
with upstream fix?

system-config-printer-libs.i386: W: conffile-without-noreplace-flag
/etc/dbus-1/system.d/newprinternotification.conf
===> Is this(noreplace) not needed?

system-config-printer-libs.i386: W: doc-file-dependency
/usr/share/doc/system-config-printer-libs-0.7.74.3/pycups-1.9.27/examples/cupstree.py
/usr/bin/python
===> ==> But user can use this with python command also right?


-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.