On Wed, 19 Aug 2020, Thorsten Glaser wrote:
> On Wed, 19 Aug 2020, Cristian Ionescu-Idbohrn wrote:
>
> > > libelogind0 actually *does* implement much of libsystemd0's ABI.
> > > Just wait for the new version.
> >
> > Nothing pesonal. This has been gone for too long. I'm tired, but
> > just let
On Wed, 19 Aug 2020, Cristian Ionescu-Idbohrn wrote:
> > libelogind0 actually *does* implement much of libsystemd0's ABI.
> > Just wait for the new version.
>
> Nothing pesonal. This has been gone for too long. I'm tired, but
> just let me put it this way:
[…]
I’m in the same boat. But if you
On Mon, 17 Aug 2020, Thorsten Glaser wrote:
> On Mon, 17 Aug 2020, Cristian Ionescu-Idbohrn wrote:
>
> > > As a workaround you can use equivs to install a dummy package that
> > > Provides: libsystemd0 (99:99) to satisfy wireshark-common's
>
> > I would have expected such a dummy package to be pr
On Mon, 17 Aug 2020, Cristian Ionescu-Idbohrn wrote:
> > As a workaround you can use equivs to install a dummy package that
> > Provides: libsystemd0 (99:99) to satisfy wireshark-common's
> I would have expected such a dummy package to be provided in the
No, this does not belong into the distri
On Mon, 17 Aug 2020, Balint Reczey wrote:
>
> Hi Cristian,
Balint,
> As a workaround you can use equivs to install a dummy package that
> Provides: libsystemd0 (99:99) to satisfy wireshark-common's
> dependencies and lose only the ability to dissect journals which most
> likely you are not inter
Hi Cristian,
On Sun, Aug 16, 2020 at 6:42 PM Cristian Ionescu-Idbohrn
wrote:
>
> On Fri, 14 Aug 2020, Balint Reczey wrote:
> >
> > Wireshark parses systemd journals and for doing so it depends on
> > libsystemd0.
> > The version it depends on is controlled only by the used symbols and
> > wiresha
On Fri, 14 Aug 2020, Balint Reczey wrote:
>
> Wireshark parses systemd journals and for doing so it depends on
> libsystemd0.
> The version it depends on is controlled only by the used symbols and
> wireshark only build-depends on libsystemd-dev.
But Balint, reassigning that bug to elogind won'
Control: forwarded -1 https://github.com/elogind/elogind/issues/170
Balint and Thorsten,
On Fri, Aug 14, 2020 at 08:43:31AM +0200, Balint Reczey wrote:
[…]
> libelogind0 provides only libsystemd0 (= 243.7) which I understand
> since keeping up with systemd upstream is hard, but other packages
>
Control: reassign -1 libelogind0 243.7-1+debian1
Hi Thorsten,
On Fri, Aug 14, 2020 at 3:03 AM Thorsten Glaser wrote:
>
> Package: wireshark-common
> Version: 3.2.6-1
> Severity: important
> X-Debbugs-Cc: t...@mirbsd.de
>
> I cannot upgrade wireshark-common (and thus wireshark-qt) from 3.2.5-1
>
Package: wireshark-common
Version: 3.2.6-1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de
I cannot upgrade wireshark-common (and thus wireshark-qt) from 3.2.5-1
to 3.2.6-1 because the latter introduced a version into the libsystemd0
dependency. This seems to have been done with no reason, consid
10 matches
Mail list logo
