# Zeek 6.0.3 Binary Package Install on Ubuntu 22.04 Breaks apt Dependencies

**URL:** <https://community.zeek.org/t/zeek-6-0-3-binary-package-install-on-ubuntu-22-04-breaks-apt-dependencies/7348>\
**Category:** Zeek\
**Tags:** installation\
**Created:** [April 29, 2024, 1:34pm UTC](https://community.zeek.org/t/zeek-6-0-3-binary-package-install-on-ubuntu-22-04-breaks-apt-dependencies/7348 "2024-04-29T13:34:25Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mayara](https://avatars.discourse-cdn.com/v4/letter/m/ecb155/32.png) [@Mayara](https://community.zeek.org/u/Mayara)\
**Post date:** [April 29, 2024, 1:34pm UTC](https://community.zeek.org/t/zeek-6-0-3-binary-package-install-on-ubuntu-22-04-breaks-apt-dependencies/7348/1 "2024-04-29T13:34:25Z")

</div>

Hello, I was trying to install Zeek 6.0.3 in Ubuntu 22.04 using binary packages and following the instructions of the official documentation. However, I was unable to conclude the process of installation. After that, I successfully installed Zeek 6.0.3 following the instructions of [this blog post](https://cybertoolguardian.blogspot.com/2023/09/zeek-installation-in-ubuntu.html), which has instructions for installing from the source. I deleted all files related to Zeek before installing from source.

However, when I try to install other softwares, for instance, I ran _sudo apt install autoconf_, and i got this response:

_Reading package lists… Done_  
_Building dependency tree… Done_  
_Reading state information… Done_  
_You might want to run ‘apt --fix-broken install’ to correct these._  
_The following packages have unmet dependencies:_

- zeek-6.0-core-dev : Depends: libbroker-6.0-dev (= 6.0.3-0) but it is not going to be installed\*  
_E: Unmet dependencies. Try ‘apt --fix-broken install’ with no packages (or specify a solution)._

When I try to run _sudo apt --fix-broken install_, I get this response:

_Preparing to unpack …/libbroker-6.0-dev\_6.0.3-0\_amd64.deb …_  
_Unpacking libbroker-6.0-dev (6.0.3-0) …_  
_dpkg: error processing archive /var/cache/apt/archives/libbroker-6_  
_.0-dev\_6.0.3-0\_amd64.deb (–unpack):_

- trying to overwrite ‘/opt/zeek/include/broker/address.hh’, which \*  
_is also in package libbroker-lts-dev 6.0.3-0_  
_dpkg-deb: error: paste subprocess was killed by signal (Broken pip_  
_e)_  
_Errors were encountered while processing:_
- /var/cache/apt/archives/libbroker-6.0-dev\_6.0.3-0\_amd64.deb\*  
_E: Sub-process /usr/bin/dpkg returned an error code (1)_

So, I may be wrong, but it seems that there is a directory error, since the system tries to access _/opt/zeek_ , but the Zeek files are located in _/usr/local/zeek_.

How could I solve this issue? I would like to try to solve the issue over installing Zeek again from source, since this process can take a really long while. Any help would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![johanna](https://avatars.discourse-cdn.com/v4/letter/j/50afbb/32.png) [@johanna](https://community.zeek.org/u/johanna)\
**Post date:** [April 29, 2024, 1:47pm UTC](https://community.zeek.org/t/zeek-6-0-3-binary-package-install-on-ubuntu-22-04-breaks-apt-dependencies/7348/2 "2024-04-29T13:47:08Z")

</div>

Hi,

it seems like you have been trying to install conflicting Zeek packages. You can either install the zeek, zeek-6.0, or the zeek-lts package - but they cannot be installed simultaneously.

Try removing the “libbroker-lts-dev” package, which conflicts with “libbroker-6.0-dev” and then try the apt fixing operation again.

This partially is my fault - this shows that there is insufficient flagging between some conflicting Zeek packages. I will try to add these conflicts to the package - which might make these kind of errors auto-fixable by apt.

---

<div class="post-metadata">

**Author:** ![Mayara](https://avatars.discourse-cdn.com/v4/letter/m/ecb155/32.png) [@Mayara](https://community.zeek.org/u/Mayara)\
**Post date:** [April 29, 2024, 3:09pm UTC](https://community.zeek.org/t/zeek-6-0-3-binary-package-install-on-ubuntu-22-04-breaks-apt-dependencies/7348/3 "2024-04-29T15:09:35Z")

</div>

> [@johanna](#):
>
> libbroker-lts-dev

I just tried to run _sudo apt remove libbroker-lts-dev_, still I got the error response:

_You might want to run ‘apt --fix-broken install’ to correct these._  
_The following packages have unmet dependencies:_

- zeek-6.0-core-dev : Depends: libbroker-6.0-dev (= 6.0.3-0) but it is not going to be installed\*  
_E: Unmet dependencies. Try ‘apt --fix-broken install’ with no packages (or specify a solution)._

I also tried to delete manually the files related to libbroker-lts-dev, however the error message persisted.

---

<div class="post-metadata">

**Author:** ![johanna](https://avatars.discourse-cdn.com/v4/letter/j/50afbb/32.png) [@johanna](https://community.zeek.org/u/johanna)\
**Post date:** [April 29, 2024, 3:33pm UTC](https://community.zeek.org/t/zeek-6-0-3-binary-package-install-on-ubuntu-22-04-breaks-apt-dependencies/7348/4 "2024-04-29T15:33:20Z")

</div>

Did you try `apt --fix-broken install` again after removing libbroker-lts-dev? 🙂

---

<div class="post-metadata">

**Author:** ![Mayara](https://avatars.discourse-cdn.com/v4/letter/m/ecb155/32.png) [@Mayara](https://community.zeek.org/u/Mayara)\
**Post date:** [April 29, 2024, 4:07pm UTC](https://community.zeek.org/t/zeek-6-0-3-binary-package-install-on-ubuntu-22-04-breaks-apt-dependencies/7348/5 "2024-04-29T16:07:08Z")

</div>

I did, however the error persisted 😭

I think that installing Zeek again may not be the sollution, since i was unable to install from binary packages and if I install from source again the error will persist, because is related to the directory which contains Zeek files.

_Preparing to unpack …/libbroker-6.0-dev\_6.0.3-0\_amd64.deb …_  
_Unpacking libbroker-6.0-dev (6.0.3-0) …_  
_dpkg: error processing archive /var/cache/apt/archives/libbroker-6.0-dev\_6.0.3-0_  
_\_amd64.deb (–unpack):_

- trying to overwrite ‘/opt/zeek/include/broker/address.hh’, which is also in pac\*  
_kage libbroker-lts-dev 6.0.3-0_  
_dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)_  
_Errors were encountered while processing:_
- /var/cache/apt/archives/libbroker-6.0-dev\_6.0.3-0\_amd64.deb\*  
_E: Sub-process /usr/bin/dpkg returned an error code (1)_

---

<div class="post-metadata">

**Author:** ![johanna](https://avatars.discourse-cdn.com/v4/letter/j/50afbb/32.png) [@johanna](https://community.zeek.org/u/johanna)\
**Post date:** [April 30, 2024, 9:37am UTC](https://community.zeek.org/t/zeek-6-0-3-binary-package-install-on-ubuntu-22-04-breaks-apt-dependencies/7348/6 "2024-04-30T09:37:30Z")

</div>

This looks very much like `libbroker-lts-dev` is still installed :).

Could you try removing it again, and perhaps also doing an `apt autoremove`.

I can also try to update the -lts packages to make this kind of error less likely, but it will take me a couple of days.

---

<div class="post-metadata">

**Author:** ![Mayara](https://avatars.discourse-cdn.com/v4/letter/m/ecb155/32.png) [@Mayara](https://community.zeek.org/u/Mayara)\
**Post date:** [April 30, 2024, 12:16pm UTC](https://community.zeek.org/t/zeek-6-0-3-binary-package-install-on-ubuntu-22-04-breaks-apt-dependencies/7348/7 "2024-04-30T12:16:12Z")

</div>

The problem is solved! 🎉

I was trying to remove libbroker-lts-dev using the command _sudo apt remove libbroker-lts-dev_, but the depency-related error persisted, however, I successfully removed the package executing _sudo dpkg --remove --force-depends libbroker-lts-dev_. Now I am able to install other programs. Thank you for your help!

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\
**Post date:** [April 20, 2026, 8:30pm UTC](https://community.zeek.org/t/zeek-6-0-3-binary-package-install-on-ubuntu-22-04-breaks-apt-dependencies/7348/8 "2026-04-20T20:30:39Z")

</div>

Closed on April 20, 2026, 8:30pm UTC

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
