Bug#941937: apt: Unexpected linkage dependency on libsystemd

2020-06-05 Thread Julian Andres Klode
(I guess the last email was the disagree email, and this one is the positive one, idk, I just missed those two points) On Fri, Jun 05, 2020 at 04:15:07PM +0200, Adam Borowski wrote: > On Fri, Jun 05, 2020 at 10:34:47AM +0200, Julian Andres Klode wrote: > > On Fri, Jun 05, 2020 at 04:34:23AM

Bug#941937: apt: Unexpected linkage dependency on libsystemd

2020-06-05 Thread Julian Andres Klode
On Fri, Jun 05, 2020 at 04:15:07PM +0200, Adam Borowski wrote: > On Fri, Jun 05, 2020 at 10:34:47AM +0200, Julian Andres Klode wrote: > > On Fri, Jun 05, 2020 at 04:34:23AM +0300, Aleksey Tulinov wrote: > > > systemd-inhibit --what="shutdown" --mode="block" /internal/path/to/dpkg $@ > > > > Let's

Bug#941937: apt: Unexpected linkage dependency on libsystemd

2020-06-05 Thread Adam Borowski
On Fri, Jun 05, 2020 at 10:34:47AM +0200, Julian Andres Klode wrote: > On Fri, Jun 05, 2020 at 04:34:23AM +0300, Aleksey Tulinov wrote: > > systemd-inhibit --what="shutdown" --mode="block" /internal/path/to/dpkg $@ > > Let's try this again: We run dpkg multiple times. We need to run dpkg > up to

Bug#941937: apt: Unexpected linkage dependency on libsystemd

2020-06-05 Thread Aleksey Tulinov
пт, 5 июн. 2020 г. в 11:34, Julian Andres Klode : > This is a best effort thing, there's nothing sensible we can do if it > fails, except for logging a warning, and that does not help a lot. We > don't want to issue an error obviously because you still want to be able > to upgrade the system if

Bug#941937: apt: Unexpected linkage dependency on libsystemd

2020-06-05 Thread Julian Andres Klode
On Fri, Jun 05, 2020 at 04:34:23AM +0300, Aleksey Tulinov wrote: > пт, 5 июн. 2020 г. в 00:30, David Kalnischkies : > > > I mentioned already that this is implemented in libapt to apply to ALL > > apt-based clients equally. A cron-job is not effected by aliases nor is > > a python script (using

Bug#941937: apt: Unexpected linkage dependency on libsystemd

2020-06-04 Thread Aleksey Tulinov
пт, 5 июн. 2020 г. в 00:30, David Kalnischkies : > I mentioned already that this is implemented in libapt to apply to ALL > apt-based clients equally. A cron-job is not effected by aliases nor is > a python script (using python-apt). It isn't even realistic that you > alias all "normal" libapt

Bug#941937: apt: Unexpected linkage dependency on libsystemd

2020-06-04 Thread Julian Andres Klode
On Thu, Jun 04, 2020 at 09:24:22PM +0300, Aleksey Tulinov wrote: > On Wed, 9 Oct 2019 17:36:07 +0200 David Kalnischkies > wrote: > > > As Julian already said, it is "just" used for its dbus communication > > implementation. We don't require systemd to be your init or to be even > > functional.

Bug#941937: apt: Unexpected linkage dependency on libsystemd

2020-06-04 Thread David Kalnischkies
On Thu, Jun 04, 2020 at 09:24:22PM +0300, Aleksey Tulinov wrote: > On Wed, 9 Oct 2019 17:36:07 +0200 David Kalnischkies > wrote: > > As Julian already said, it is "just" used for its dbus communication > > implementation. We don't require systemd to be your init or to be even > > functional. So I

Bug#941937: apt: Unexpected linkage dependency on libsystemd

2020-06-04 Thread Aleksey Tulinov
On Wed, 9 Oct 2019 17:36:07 +0200 David Kalnischkies wrote: > As Julian already said, it is "just" used for its dbus communication > implementation. We don't require systemd to be your init or to be even > functional. So I guess proposing an alternative which a) works equally > well and b)

Bug#941937: apt: Unexpected linkage dependency on libsystemd

2019-10-09 Thread Balint Reczey
Hi David, On Wed, Oct 9, 2019 at 6:03 PM David Kalnischkies wrote: > > On Wed, Oct 09, 2019 at 12:53:45AM +0200, Adam Borowski wrote: > > It's not about not being available in normal use, it's because switching the > > library's implementation is fragile -- especially if systemd's prerm fails >

Bug#941937: apt: Unexpected linkage dependency on libsystemd

2019-10-09 Thread David Kalnischkies
On Wed, Oct 09, 2019 at 12:53:45AM +0200, Adam Borowski wrote: > It's not about not being available in normal use, it's because switching the > library's implementation is fragile -- especially if systemd's prerm fails > which it's notorious to. This will make apt fail, and apt happens to be the

Bug#941937: apt: Unexpected linkage dependency on libsystemd

2019-10-08 Thread Adam Borowski
On Mon, Oct 07, 2019 at 09:23:01PM +0200, Julian Andres Klode wrote: > On Mon, Oct 07, 2019 at 08:22:33PM +0200, Andreas Messer wrote: > > Would it make sense to use dlopen() to dynamically load libsystemd when > > needed > > and avoid the hard dependency on libsystemd? If systemd is installed,

Bug#941937: apt: Unexpected linkage dependency on libsystemd

2019-10-07 Thread Julian Andres Klode
Control: tag -1 wontfix Control: severity -1 wishlist On Mon, Oct 07, 2019 at 08:22:33PM +0200, Andreas Messer wrote: > Package: apt > Version: 1.8.2 > Severity: normal > > I observed a linkage dependency on libsystemd. This was unexpected for me > since I wouldn't expect a package manager

Bug#941937: apt: Unexpected linkage dependency on libsystemd

2019-10-07 Thread Andreas Messer
Package: apt Version: 1.8.2 Severity: normal I observed a linkage dependency on libsystemd. This was unexpected for me since I wouldn't expect a package manager depend on it. A package manager should be as lean as possible. Having reviewed the code, the only function using libsystemd is used to