Bug#962214: (no subject)

2021-04-29 Thread Phillip Susi


julien forest writes:

> Package: policykit-1 
> Version: 0.105-30
> State: not installed
> Multi-Arch: foreign
> Priority: optional
> Section: admin
> Maintainer: Utopia Maintenance Team
>  Architecture: amd64
> Uncompressed Size: 335 k
> Depends: ... default-logind | logind ...
>
> which itself depends on libpam-systemd or libpam-elogind 
>
> There is no need IMHO to add such a dependency (maybe a recommend).

gparted depends on policykit-1 to get run as root.  Unless there's some
other way that still works these days to do that, removing this
depenency will break the desktop icon.

That depends on either systemd or elogind, which AFAIK, are already
requirements for any of the supported desktops.

Then again, if policykit-1 is already installed in all of the desktops,
the depenency may be redundant?  On the other hand, if it is redundant,
then how will removing it help you?  If it isn't redundant, then what
configurations will break because they don't have policykit-1 and so
launching gparted from the desktop icon will fail?



Bug#962214: (no subject)

2021-04-29 Thread julien forest
Package: policykit-1 
Version: 0.105-30
State: not installed
Multi-Arch: foreign
Priority: optional
Section: admin
Maintainer: Utopia Maintenance Team
 Architecture: amd64
Uncompressed Size: 335 k
Depends: ... default-logind | logind ...

which itself depends on libpam-systemd or libpam-elogind 

There is no need IMHO to add such a dependency (maybe a recommend).

Regards