[opensuse-factory] Issue with cups install?
Hi just done a "zypper dup" and i got this error (see below) during install - is it anything to worry about? regards Ian (24/28) Installing: cups-2.1.0-183.1 ............................................................................................................................................. [done] Additional rpm output: Failed to try-restart cups-lpd@.service: Unit name cups-lpd@.service is not valid. Job for cups.socket failed. See "systemctl status cups.socket" and "journalctl -xe" for details. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, On Sep 1 17:13 ianseeks wrote:
just done a "zypper dup" and i got this error (see below) during install - is it anything to worry about? ... (24/28) Installing: cups-2.1.0-183.1 ................ [done] Additional rpm output: Failed to try-restart cups-lpd@.service: Unit name cups-lpd@.service is not valid. Job for cups.socket failed. See "systemctl status cups.socket" and "journalctl -xe" for details.
CUPS 2.1.0 is not yet submited to openSUSE:Factory. Currently CUPS 2.1.0 is only in the "Printing" development project. Many thanks for testing our newest printing base software from its development project! On my Tumbleweed system where I installed CUPS 2.1.0 I have no messages regarding cups-lpd in systemd's journal so that currently I cannot reproduce your issue. I guess you can ignore cups-lpd stuff because usually one does not need support for the old LPD protocol. In general regarding cups-lpd see "man cups-lpd". Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 02 Sep 2015 11:35:44 Johannes Meixner wrote:
Hello,
On Sep 1 17:13 ianseeks wrote:
just done a "zypper dup" and i got this error (see below) during install - is it anything to worry about?
...
(24/28) Installing: cups-2.1.0-183.1 ................ [done] Additional rpm output: Failed to try-restart cups-lpd@.service: Unit name cups-lpd@.service is not valid. Job for cups.socket failed. See "systemctl status cups.socket" and "journalctl -xe" for details.
CUPS 2.1.0 is not yet submited to openSUSE:Factory.
Currently CUPS 2.1.0 is only in the "Printing" development project.
Many thanks for testing our newest printing base software from its development project! No problems. I check to make sure my original issue of no USB printer never reappears.
On my Tumbleweed system where I installed CUPS 2.1.0 I have no messages regarding cups-lpd in systemd's journal so that currently I cannot reproduce your issue.
I was only wondering if it was an install script issue, just thought i'd mention it in case it was.
I guess you can ignore cups-lpd stuff because usually one does not need support for the old LPD protocol. In general regarding cups-lpd see "man cups-lpd". i don;t think i've used lpd in years. well, not deliberately anyway. :o)
Kind Regards Johannes Meixner
Thanks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, On Sep 2 10:57 ianseeks wrote (excerpt):
(24/28) Installing: cups-2.1.0-183.1 ................ [done] Additional rpm output: Failed to try-restart cups-lpd@.service: Unit name cups-lpd@.service is not valid. Job for cups.socket failed. See "systemctl status cups.socket" and "journalctl -xe" for details. ...
I was only wondering if it was an install script issue, just thought i'd mention it in case it was.
It is an issue in the RPM scriptlets and I appreciate it that you reported it! The RPM scriptlets should work fail-safe. But currently I cannot see what is wrong. One reason why I cannot see what is wrong is that the systemd related parts in our RPM scriptlets are mostly RPM macros so that one cannot easily see what is actually done, cf. https://en.opensuse.org/openSUSE:Packaging_scriptlet_snippets#Debugging_scri... But of course using standardized RPM macros for standard tasks is better than individual implementations in each package. Another reason is that CUPS 2.1.0 builds for various architectures in the "Printing" project which shows that at least in "Printing" no RPM scriptlet fails (otherwise build would fail). In the end this means (unfortunately as often with systemd) what actually happens is obscured by various levels of indirection (cf. RFC 1925: item (6a)) so that in practice often nobody can sufficiently imagine why something goes wrong with systemd on someone else system. Because no RPM scriptlet fails in "Printing" I assume that your systemd overall state (i.e. what units exist in which particular state on your system) is different compared to the default in the RPM build system which results that in your case a RPM scriptlet fails. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 02 Sep 2015 12:32:05 Johannes Meixner wrote:
Hello,
On Sep 2 10:57 ianseeks wrote (excerpt):
(24/28) Installing: cups-2.1.0-183.1 ................ [done] Additional rpm output: Failed to try-restart cups-lpd@.service: Unit name cups-lpd@.service is not valid. Job for cups.socket failed. See "systemctl status cups.socket" and "journalctl -xe" for details.
...
I was only wondering if it was an install script issue, just thought i'd mention it in case it was.
It is an issue in the RPM scriptlets and I appreciate it that you reported it!
The RPM scriptlets should work fail-safe.
But currently I cannot see what is wrong.
One reason why I cannot see what is wrong is that the systemd related parts in our RPM scriptlets are mostly RPM macros so that one cannot easily see what is actually done, cf.
https://en.opensuse.org/openSUSE:Packaging_scriptlet_snippets#Debugging_scri ptlet_failure_during_RPM_package_build
But of course using standardized RPM macros for standard tasks is better than individual implementations in each package.
Another reason is that CUPS 2.1.0 builds for various architectures in the "Printing" project which shows that at least in "Printing" no RPM scriptlet fails (otherwise build would fail).
In the end this means (unfortunately as often with systemd) what actually happens is obscured by various levels of indirection (cf. RFC 1925: item (6a)) so that in practice often nobody can sufficiently imagine why something goes wrong with systemd on someone else system.
Because no RPM scriptlet fails in "Printing" I assume that your systemd overall state (i.e. what units exist in which particular state on your system) is different compared to the default in the RPM build system which results that in your case a RPM scriptlet fails.
Printing still works so i'm happy as a pig in shit. :O)
Kind Regards Johannes Meixner
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
ianseeks -
Johannes Meixner