Reco wrote:
> Whatever pulled network-manager on this host pulled systemd-sysv.
I did
1. apt-get install libgimp2.0-dev
2. apt-get --fix-broken install
3. apt-get install libgimp2.0-dev
#1 failed
not sure if the dependency was already there.
The only previous installati
Hi.
On Mon, Sep 30, 2019 at 08:36:17PM +0200, deloptes wrote:
> Reco wrote:
>
> > On Mon, Sep 30, 2019 at 08:53:24AM +0200, deloptes wrote:
> >> few days ago tested upgrade in buster for a new build server and had to
> >> install libgimp2.0-dev which installed libgimp2.0 which pulled syst
Reco wrote:
> Hi.
>
> On Mon, Sep 30, 2019 at 08:53:24AM +0200, deloptes wrote:
>> few days ago tested upgrade in buster for a new build server and had to
>> install libgimp2.0-dev which installed libgimp2.0 which pulled systemd I
>> think over policykit.
>
> Does not reproduce:
Sorry Reco, mus
Hi.
On Mon, Sep 30, 2019 at 08:53:24AM +0200, deloptes wrote:
> few days ago tested upgrade in buster for a new build server and had to
> install libgimp2.0-dev which installed libgimp2.0 which pulled systemd I
> think over policykit.
Does not reproduce:
# dpkg -S /sbin/init
sysvinit-cor
Hi,
few days ago tested upgrade in buster for a new build server and had to
install libgimp2.0-dev which installed libgimp2.0 which pulled systemd I
think over policykit.
It was ask 1-2 weeks ago what is pulling systemd in buster. I wonder if
there is a way to avoid it and keep old init but having
5 matches
Mail list logo
