Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
manulOffline
Post subject:   PostPosted: 07.05.2014, 20:16



Joined: 2010-09-13
Posts: 96

Status: Offline
      yossarian wrote:
@manul:
What's wrong with you?

Have you read that link provided above?
https://bugs.debian.org/cgi-bin/bugrepo ... =747105#27


Yes I did read the link and no, I do not think anything is wrong with me.

All I ask now, is:
      Quote:
how do I find which exactly package still "pulls" systemd as a dependency.
No one answered this yet btw, and this is a generic question (I was wondering about it before as well, for other packages).

Is not my question clear enough? (It is NOT systemd related per sе; it just happens to be systemd this time when I ask about it).

Is this possible (find which exactly package still "pulls" package xxx as a dependency, so it gets installed as "new package" when d-u), or is this beyond capabilities of apt?
A script/one-liner is welcome too, if there is no single tool to do it.

thanks,
manul
 
 View user's profile Send private message  
Reply with quote Back to top
yossarianOffline
Post subject:   PostPosted: 07.05.2014, 20:43



Joined: 2010-09-11
Posts: 35

Status: Offline
logind is a part of systemd. That's why you need systemd.
http://www.freedesktop.org/wiki/Softwar ... md/logind/

      Code:
aptitude why systemd
apt-cache rdepends systemd
 
 View user's profile Send private message  
Reply with quote Back to top
manulOffline
Post subject:   PostPosted: 07.05.2014, 20:50



Joined: 2010-09-13
Posts: 96

Status: Offline
I was able to find the reason with the help of cupt (apt alternative) which I installed temporarily.

When a package yyy has alternatives (xxx|zzz) (xxx being 1st - and so the "preferred alternative") - no matter that package zzz may already be installed - apt-get dist-upgrade still installs xxx (b/c this way package yyy has its "preferred alternative" which is obviously ranked higher in the dependency resolver).

Unlike apt, cupt's dist-upgrade allows user to not agree and seek other acceptable & coherent installation variants; in this particular case not installing xxx is fine (and proposed by cupt, when the default is not accepted); with the remark that it is not the preferred alternative.
 
 View user's profile Send private message  
Reply with quote Back to top
yossarianOffline
Post subject:   PostPosted: 07.05.2014, 21:02



Joined: 2010-09-11
Posts: 35

Status: Offline
Try aptitude:
      Code:
aptitude install sysvinit-core -s
The following NEW packages will be installed:
  sysvinit-core
0 packages upgraded, 1 newly installed, 0 to remove and 31 not upgraded.
Need to get 129 kB of archives. After unpacking 252 kB will be used.
The following packages have unmet dependencies:
 systemd-sysv : Breaks: sysvinit-core but 2.88dsf-53 is to be installed.
The following actions will resolve these dependencies:

     Remove the following packages:
1)     libpam-systemd             
2)     policykit-1                 
3)     policykit-1-gnome           
4)     systemd-sysv               



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

     Remove the following packages:         
1)     systemd-sysv                         

     Install the following packages:         
2)     systemd-shim [6-3 (testing, unstable)]



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

      Remove the following packages:                             
1)      gnome-keyring                                           
2)      libcap2-bin                                             
3)      libpam-systemd                                           
4)      policykit-1                                             
5)      systemd                                                 
6)      systemd-gui                                             
7)      systemd-sysv                                             
8)      systemd-ui                                               

      Install the following packages:                           
9)      libacl1:i386 [2.2.52-1 (testing, unstable)]             
10)     libaudit1:i386 [1:2.3.6-1 (testing, unstable)]           
11)     libcap2-bin:i386 [1:2.22-1.2 (testing, unstable)]       
12)     libcryptsetup4:i386 [2:1.6.4-4 (testing, unstable)]     
13)     libdevmapper1.02.1:i386 [2:1.02.83-2 (testing, unstable)]
14)     libkmod2:i386 [17-2 (unstable)]                         
15)     libpam-systemd:i386 [204-10 (unstable)]                 
16)     libpam0g:i386 [1.1.8-3 (testing, unstable)]             
17)     libpolkit-agent-1-0:i386 [0.105-5 (unstable)]           
18)     libpolkit-backend-1-0:i386 [0.105-5 (unstable)]         
19)     libpolkit-gobject-1-0:i386 [0.105-5 (unstable)]         
20)     libsystemd-daemon0:i386 [204-10 (unstable)]             
21)     libsystemd-login0:i386 [204-10 (unstable)]               
22)     policykit-1:i386 [0.105-5 (unstable)]                   
23)     systemd:i386 [204-10 (unstable)]                         
24)     systemd-shim:i386 [6-3 (testing, unstable)]             



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

     Keep the following packages at their current version:
1)     sysvinit-core [Not Installed]                     



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

     Remove the following packages:                                       
1)     systemd-sysv                                                       

     Downgrade the following packages:                                     
2)     libpam-systemd [204-10 (now, unstable) -> 204-8 (testing)]         
3)     libsystemd-daemon0 [204-10 (now, unstable) -> 204-8 (testing)]     
4)     libsystemd-journal0 [204-10 (now, unstable) -> 204-8 (testing)]     
5)     libsystemd-journal0:i386 [204-10 (now, unstable) -> 204-8 (testing)]
6)     libsystemd-login0 [204-10 (now, unstable) -> 204-8 (testing)]       
7)     systemd [204-10 (now, unstable) -> 204-8 (testing)]                 



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

     Remove the following packages:                             
1)     libpam-systemd                                           
2)     systemd-sysv                                             

     Downgrade the following packages:                           
3)     policykit-1 [0.105-5 (now, unstable) -> 0.105-4 (testing)]



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

     Remove the following packages:                                   
1)     libasound2-plugins:i386                                       
2)     libpulse0:i386                                                 
3)     libsystemd-journal0:i386                                       
4)     systemd-sysv                                                   

     Downgrade the following packages:                               
5)     libpam-systemd [204-10 (now, unstable) -> 204-8 (testing)]     
6)     libsystemd-daemon0 [204-10 (now, unstable) -> 204-8 (testing)]
7)     libsystemd-journal0 [204-10 (now, unstable) -> 204-8 (testing)]
8)     libsystemd-login0 [204-10 (now, unstable) -> 204-8 (testing)] 
9)     systemd [204-10 (now, unstable) -> 204-8 (testing)]           



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

      Remove the following packages:                                       
1)      cb-exit                                                             
2)      consolekit                                                         
3)      libck-connector0                                                   
4)      libpam-ck-connector                                                 
5)      libpam-systemd                                                     
6)      libpolkit-backend-1-0                                               
7)      lightdm                                                             
8)      policykit-1                                                         
9)      systemd-sysv                                                       

      Install the following packages:                                       
10)     consolekit:i386 [0.4.6-4 (testing)]                                 
11)     libacl1:i386 [2.2.52-1 (testing, unstable)]                         
12)     libaudit1:i386 [1:2.3.6-1 (testing, unstable)]                     
13)     libck-connector0:i386 [0.4.6-4 (testing)]                           
14)     libdbus-glib-1-2:i386 [0.102-1 (testing, unstable)]                 
15)     libpam0g:i386 [1.1.8-3 (testing, unstable)]                         
16)     libpolkit-agent-1-0:i386 [0.105-4 (testing)]                       
17)     libpolkit-backend-1-0:i386 [0.105-4 (testing)]                     
18)     libpolkit-gobject-1-0:i386 [0.105-5 (unstable)]                     
19)     libsystemd-login0:i386 [204-8 (testing)]                           
20)     policykit-1:i386 [0.105-4 (testing)]                               

      Downgrade the following packages:                                     
21)     libpolkit-agent-1-0 [0.105-5 (now, unstable) -> 0.105-4 (testing)] 
22)     libsystemd-daemon0 [204-10 (now, unstable) -> 204-8 (testing)]     
23)     libsystemd-journal0 [204-10 (now, unstable) -> 204-8 (testing)]     
24)     libsystemd-journal0:i386 [204-10 (now, unstable) -> 204-8 (testing)]
25)     libsystemd-login0 [204-10 (now, unstable) -> 204-8 (testing)]       
26)     systemd [204-10 (now, unstable) -> 204-8 (testing)]                 



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

      Remove the following packages:                                       
1)      cb-exit                                                             
2)      consolekit                                                         
3)      libck-connector0                                                   
4)      libpam-ck-connector                                                 
5)      libpam-systemd                                                     
6)      libpolkit-backend-1-0                                               
7)      lightdm                                                             
8)      policykit-1                                                         
9)      systemd-sysv                                                       

      Install the following packages:                                       
10)     consolekit:i386 [0.4.6-4 (testing)]                                 
11)     libacl1:i386 [2.2.52-1 (testing, unstable)]                         
12)     libaudit1:i386 [1:2.3.6-1 (testing, unstable)]                     
13)     libck-connector0:i386 [0.4.6-4 (testing)]                           
14)     libdbus-glib-1-2:i386 [0.102-1 (testing, unstable)]                 
15)     libpam0g:i386 [1.1.8-3 (testing, unstable)]                         
16)     libpolkit-agent-1-0:i386 [0.105-5 (unstable)]                       
17)     libpolkit-backend-1-0:i386 [0.105-4 (testing)]                     
18)     libpolkit-gobject-1-0:i386 [0.105-4 (testing)]                     
19)     libsystemd-login0:i386 [204-8 (testing)]                           
20)     policykit-1:i386 [0.105-4 (testing)]                               

      Downgrade the following packages:                                     
21)     libpolkit-gobject-1-0 [0.105-5 (now, unstable) -> 0.105-4 (testing)]
22)     libsystemd-daemon0 [204-10 (now, unstable) -> 204-8 (testing)]     
23)     libsystemd-journal0 [204-10 (now, unstable) -> 204-8 (testing)]     
24)     libsystemd-journal0:i386 [204-10 (now, unstable) -> 204-8 (testing)]
25)     libsystemd-login0 [204-10 (now, unstable) -> 204-8 (testing)]       
26)     systemd [204-10 (now, unstable) -> 204-8 (testing)]                 



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

      Remove the following packages:                                       
1)      cb-exit                                                             
2)      consolekit                                                         
3)      libck-connector0                                                   
4)      libpam-ck-connector                                                 
5)      libpam-systemd                                                     
6)      libpolkit-backend-1-0                                               
7)      lightdm                                                             
8)      policykit-1                                                         
9)      systemd-sysv                                                       

      Install the following packages:                                       
10)     consolekit:i386 [0.4.6-4 (testing)]                                 
11)     libacl1:i386 [2.2.52-1 (testing, unstable)]                         
12)     libaudit1:i386 [1:2.3.6-1 (testing, unstable)]                     
13)     libck-connector0:i386 [0.4.6-4 (testing)]                           
14)     libdbus-glib-1-2:i386 [0.102-1 (testing, unstable)]                 
15)     libpam0g:i386 [1.1.8-3 (testing, unstable)]                         
16)     libpolkit-agent-1-0:i386 [0.105-5 (unstable)]                       
17)     libpolkit-backend-1-0:i386 [0.105-4 (testing)]                     
18)     libpolkit-gobject-1-0:i386 [0.105-5 (unstable)]                     
19)     libsystemd-login0:i386 [204-8 (testing)]                           
20)     policykit-1:i386 [0.105-4 (testing)]                               

      Downgrade the following packages:                                     
21)     libsystemd-daemon0 [204-10 (now, unstable) -> 204-8 (testing)]     
22)     libsystemd-journal0 [204-10 (now, unstable) -> 204-8 (testing)]     
23)     libsystemd-journal0:i386 [204-10 (now, unstable) -> 204-8 (testing)]
24)     libsystemd-login0 [204-10 (now, unstable) -> 204-8 (testing)]       
25)     systemd [204-10 (now, unstable) -> 204-8 (testing)]                 



Accept this solution? [Y/n/q/?]
 
 View user's profile Send private message  
Reply with quote Back to top
manulOffline
Post subject:   PostPosted: 07.05.2014, 21:06



Joined: 2010-09-13
Posts: 96

Status: Offline
      yossarian wrote:
logind is a part of systemd. That's why you need systemd.
http://www.freedesktop.org/wiki/Softwar ... md/logind/

      Code:
aptitude why systemd
apt-cache rdepends systemd


There is nothing like package logind, but I have installed libsystemd-login0:

      Code:
root@siddie-new:/home/manul# dpkg -l | grep systemd
ii  libsystemd-daemon0:amd64                  204-10                             amd64        systemd utility library
ii  libsystemd-id128-0:amd64                  204-10                             amd64        systemd 128 bit ID utility library
ii  libsystemd-journal0:amd64                 204-10                             amd64        systemd journal utility library
ii  libsystemd-login0:amd64                   204-10                             amd64        systemd login utility library
ii  systemd-shim                              6-3                                amd64        shim for systemd
root@siddie-new:/home/manul#


apt-cache rdepends:

      Code:
root@siddie-new:/home/manul# apt-cache rdepends systemd
systemd
Reverse Depends:
 |upower
  tuxonice-userui
  systemd-ui
  systemd-cron
  systemd-sysv
  systemd-dbg
  libsystemd-login-dev
  libsystemd-login-dev
  libsystemd-journal-dev
  libsystemd-journal-dev
  libsystemd-id128-dev
  libsystemd-id128-dev
  libsystemd-daemon-dev
  libsystemd-daemon-dev
  libpam-systemd
  sogo
  pcscd
  live-config-systemd
  lighttpd
  libvirt-bin
  init-system-helpers
  init-select
  gummiboot
  gnome-settings-daemon
root@siddie-new:/home/manul#


There is nothing like logind here.
For all of these packages checked one by one with "apt-cache showpkg" it shows that either they dont depend on systemd (directly or indirectly); or if they they do they have alternative (for example libpam-systemd and systemd-shim).
Thats it, as far as I understand the apt-output...

I have no aptitude installed.
 
 View user's profile Send private message  
Reply with quote Back to top
yossarianOffline
Post subject:   PostPosted: 07.05.2014, 21:21



Joined: 2010-09-11
Posts: 35

Status: Offline
      Quote:
logind

systemd 30 and newer include systemd-logind. This is a tiny daemon that manages user logins and seats in various ways.

Include!
      Quote:
apt-cache depends policykit-1
policykit-1
Depends: libc6
Depends: libexpat1
Depends: libglib2.0-0
Depends: libpam0g
Depends: libpolkit-agent-1-0
Depends: libpolkit-backend-1-0
Depends: libpolkit-gobject-1-0
Depends: libsystemd-login0
Depends: libpam-systemd
Depends: dbus
dbus:i386
Conflicts: policykit-1:i386

      Quote:
apt-cache depends libpam-systemd
libpam-systemd
Depends: libc6
Depends: libcap2
Depends: libdbus-1-3
Depends: libpam0g
Depends: systemd
Depends: libpam-runtime
|Depends: systemd-sysv
Depends: systemd-shim

PreDepends: multiarch-support
multiarch-support:i386
Replaces: libpam-systemd:i386
Breaks: libpam-systemd:i386
 
 View user's profile Send private message  
Reply with quote Back to top
manulOffline
Post subject:   PostPosted: 07.05.2014, 21:35



Joined: 2010-09-13
Posts: 96

Status: Offline
yosarrian:

My apologies!!!
You are correct (I obviously overlooked this, don't think it changed in the repos for last hour or two since I checked last time).

systemd installed. (purge does not work as someone here suggested, as then policykit-1 is lost which makes sense).

Now my dmesg is full of messages like
      Code:
[   16.394916] udevd[1629]: failed to execute '/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory
[   16.395759] udevd[1628]: failed to execute '/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory
[   16.400083] udevd[1640]: failed to execute '/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory
[   16.405479] udevd[1648]: failed to execute '/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory
[   16.407249] udevd[1649]: failed to execute '/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory
[   16.408216] udevd[1651]: failed to execute '/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory

but it is separate thing and off topic here.

Sorry again for confusion.
Maybe something is wrong with me after all : )))

Take care,
manul
 
 View user's profile Send private message  
Reply with quote Back to top
yossarianOffline
Post subject:   PostPosted: 07.05.2014, 21:40



Joined: 2010-09-11
Posts: 35

Status: Offline
Smile
      Code:
dpkg -L systemd |grep logind
/etc/systemd/logind.conf
/usr/share/man/man5/logind.conf.5.gz
/usr/share/man/man8/systemd-logind.service.8.gz
/lib/systemd/system/systemd-logind.service
/lib/systemd/systemd-logind
/lib/systemd/systemd-logind-launch
/usr/share/man/man8/systemd-logind.8.gz
/lib/systemd/system/multi-user.target.wants/systemd-logind.service


      manul wrote:

Now my dmesg is full of messages like
      Code:
[   16.394916] udevd[1629]: failed to execute '/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory
[   16.395759] udevd[1628]: failed to execute '/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory
[   16.400083] udevd[1640]: failed to execute '/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory
[   16.405479] udevd[1648]: failed to execute '/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory
[   16.407249] udevd[1649]: failed to execute '/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory
[   16.408216] udevd[1651]: failed to execute '/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory

but it is separate thing and off topic here.

      Code:
apt-get purge hal

https://bugs.debian.org/cgi-bin/bugrepo ... bug=717613
 
 View user's profile Send private message  
Reply with quote Back to top
vinurOffline
Post subject:   PostPosted: 08.05.2014, 04:45



Joined: 2010-09-11
Posts: 60
Location: Lake Oswego
Status: Offline
Greetings, I was creating a new system this evening and ran into this thing.
On the initial dist-upgrade on a working initial install, the system blew up
segmentation fault
sysvinit and its collision as it were with systemd-sysv
is in conflict.
Its not tragic for me, but concerning, it will be an important system.
its not tragic because I have a full backup as a separate Hard Drive i pulled before a new drive was put in the system.
its expensive to do this way but safer...
if you have a single computer and depend on it, I would not recommend upgrading just yet, this one will sneak up and bite result: warning new installs are not at the moment safe if you are doing a new upgrade of a new instal.
It will bork your system.
I am working it out now but it is not going to be trivial. reading all of the posts to look for a good cure.
This problem seems to be a bad one.
good luck. Sad
 
 View user's profile Send private message Visit poster's website  
Reply with quote Back to top
vinurOffline
Post subject:   PostPosted: 08.05.2014, 05:21



Joined: 2010-09-11
Posts: 60
Location: Lake Oswego
Status: Offline
Greetings again,
Well this seems to fix it, don't fully understand why but it is a way to make everything work again.

apt-get install systemd-shim

Once it does this with a fair number of libs and the actual install, a system message to restart a lot of services comes up.
I said yes to all starting automatically, at which point a lot of them did.
then I did:

apt-get clean
init 5 && exit

At the log on screen I just rebooted the computer. trial by fire
sorry, I don't have the record of what went into this, I am at my main computer and this message is just a recount of my actions, sorry for the lack of proper information.

I sound rather cavalier but like I said this was a new system and so I had nothing to loose with it.

Don't fully know what the war is but I will do a lot of reading to find out.

All seems to be good for me at this time
I rebooted to what appears to be a normal system.
I will come back in a day or so if anything really seems to be malfunctioning. Cool
 
 View user's profile Send private message Visit poster's website  
Reply with quote Back to top
titanOffline
Post subject:   PostPosted: 08.05.2014, 07:55



Joined: 2010-09-11
Posts: 78

Status: Offline
Installing systemd-shim fixed my policykit-1 problem

description of systemd-shim

This package emulates the systemd function that are required to run the systemd helpers without using the init service.

seems obvious now.
 
 View user's profile Send private message  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 12 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by Zafenio