On 2020-12-14 23:33:19 +0100, Thorsten Glaser wrote:
> On Mon, 14 Dec 2020, Cristian Ionescu-Idbohrn wrote:
>
> > > It doesn't depend on the init, but it links against the library to
> > > parse the journal files,
> >
> > I have no journal files on my system (yet). So, that dependency is
> >
On Mon, 14 Dec 2020, Cristian Ionescu-Idbohrn wrote:
> > It doesn't depend on the init, but it links against the library to
> > parse the journal files,
>
> I have no journal files on my system (yet). So, that dependency is
> total nonsense to me.
Not on your system but in the packet stream it
On Wed, 11 Nov 2020, Thorsten Glaser wrote:
> On Wed, 11 Nov 2020, Juliusz Chroboczek wrote:
>
> > Why on earth would a network traffic analyzer depend on system init?
>
> Please read https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968379#10
> in which all questions regarding this were
Due to this issue, I've just spent 40 minutes of my life determining
Wireshark's dependencies and compiling it from source. In case it helps:
- use Wireshark 3.2.8, not the latest stable;
- you don't need to install, Wireshark works fine from the build directory.
I do feel some nostalgia
On Sun, 16 Aug 2020, Harald Dunkel wrote:
>
> ??? There is no libsystemd0 installed, so it must have been
> referenced by wireshark. Do you think this could be replaced by
> "libelogind0 | libsystemd0"? in the dependencies?
Me too, but different.
The cause seems to be the hard dependency of
Package: wireshark
Version: 3.2.6-1
Trying to install wireshark I stumbled over
# apt install wireshark
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you
6 matches
Mail list logo
