0 Members and 1 Guest are viewing this topic.
Setting up cups-daemon (1.7.4-1) ...A dependency job for cups.service failed. See 'journalctl -xn' for details.invoke-rc.d: initscript cups, action "start" failed.dpkg: error processing package cups-daemon (--configure): subprocess installed post-installation script returned error exit status 1dpkg: dependency problems prevent configuration of cups-core-drivers: cups-core-drivers depends on cups-daemon (>= 1.7.4-1); however: Package cups-daemon is not configured yet.dpkg: error processing package cups-core-drivers (--configure): dependency problems - leaving unconfigureddpkg: dependency problems prevent configuration of cups: cups depends on cups-core-drivers (>= 1.7.4-1); however: Package cups-core-drivers is not configured yet. cups depends on cups-daemon (>= 1.7.4-1); however: Package cups-daemon is not configured yet.dpkg: error processing package cups (--configure): dependency problems - leaving unconfiguredErrors were encountered while processing: cups-daemon cups-core-drivers cupsE: Sub-process /usr/bin/dpkg returned an error code (1)
-- Logs begin at Wed 2014-07-23 11:11:32 MYT, end at Wed 2014-07-23 12:37:40 MYT. --Jul 23 12:37:25 siduction systemd[1]: ^[[1;39m[/lib/systemd/system/pywwetha.service:10] Unknown section 'Socket'. Ignoring.Jul 23 12:37:25 siduction systemd[1]: ^[[1;39m[/lib/systemd/system/pywwetha.service:11] Assignment outside of section. Ignoring.Jul 23 12:37:25 siduction systemd[1]: Starting CUPS Printing Service Sockets.-- Subject: Unit cups.socket has begun with start-up-- Defined-By: systemd-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel---- Unit cups.socket has begun starting up.Jul 23 12:37:25 siduction systemd[1]: ^[[1;39mcups.socket failed to listen on sockets: Cannot assign requested addressJul 23 12:37:25 siduction systemd[1]: Failed to listen on CUPS Printing Service Sockets.-- Subject: Unit cups.socket has failed-- Defined-By: systemd-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel---- Unit cups.socket has failed.---- The result is failed.Jul 23 12:37:25 siduction systemd[1]: Dependency failed for CUPS Printing Service.-- Subject: Unit cups.service has failed-- Defined-By: systemd-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel---- Unit cups.service has failed.---- The result is dependency.Jul 23 12:37:25 siduction sudo[17375]: pam_unix(sudo:session): session closed for user rootJul 23 12:37:40 siduction sudo[17652]: ^[[1;39mbalken : TTY=pts/1 ; PWD=/home/balken ; USER=root ; COMMAND=/bin/journalctl -xnJul 23 12:37:40 siduction sudo[17652]: pam_unix(sudo:session): session opened for user root by balken(uid=0)
Hi all,seems my siduction install is getting worse:After a fresh apt-get update and apt-get upgrade it came up with that:
apt-get update && apt-get dist-upgrade
Siduction is based on debian sid (unstable), we use dist-upgrade not upgrade, which, can/will break your system
Quote from: piper on Yesterday at 07:33:46 AMSiduction is based on debian sid (unstable), we use dist-upgrade not upgrade, which, can/will break your systemAs long as the dependencies are correctly set (*) there is no danger in doing just "upgrade". I regularly do first upgrade and then dist-upgrade after I check which packages will be installed/removed. Doing the "upgrade" first clears the easy-to-upgrade packages out of the way.(*) and this should be the case even for unstable. experimental is a different beast.
You must be new here
PLEASE READ OUR MANUALIf you continue with the "upgrade" stuff, you are on your own, no support from us.
Please, don't recommend or encourage our users to do so.
I just checked your manual. However I didn't find any substantiated reason why upgrade may be harmful in sid(uction).
It is also used when changes are made to the relationships between installed packages. With apt-get upgrade, these packages would be kept untouched (kept back).
It is linux, it's your machine, you decide what you do
...The rest is a matter of preference.
Quote from: piper on Yesterday at 10:42:31 PMIt is linux, it's your machine, you decide what you do Right. Which means there's no point discussing.The important issue here is that, as you asked, I should not recommend other users to do things that are unsupported by you.So I won't.The rest is a matter of preference.
As long as the dependencies are correctly set (*) there is no danger in doing just "upgrade". I regularly do first upgrade and then dist-upgrade after I check which packages will be installed/removed. Doing the "upgrade" first clears the easy-to-upgrade packages out of the way.(*) and this should be the case even for unstable. experimental is a different beast.
There is no "preference" for the computational result of the calculation "1+1=?"
What you call *preference* is like going to a store, buying whatever pieces lie around (upgrade), ignoring the warnings written down on many places where it says "Please, only buy parts which fit to each other and to your existing machinery" (dist-upgrade), then go home, mount the pieces together and then blame the manger of the store for the fact that not al parts fit and your machinery is broken now, telling him you live in a free country and therefore you like to buy whatever parts are available.
I mean you may call it preference although it obviously is ignorance.
...Ignorance of what? you seem to believe apt-get does something magical that no human can understand?
..but is also getting a bit offensive ...