# Suricata-update far behind in debian

**URL:** <https://forum.suricata.io/t/suricata-update-far-behind-in-debian/4636>\
**Category:** Uncategorized\
**Created:** [May 3, 2024, 7:04am UTC](https://forum.suricata.io/t/suricata-update-far-behind-in-debian/4636 "2024-05-03T07:04:41Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![gordnho](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/gordnho/32/2837_2.png) [@gordnho](https://forum.suricata.io/u/gordnho)\
**Post date:** [May 3, 2024, 7:04am UTC](https://forum.suricata.io/t/suricata-update-far-behind-in-debian/4636/1 "2024-05-03T07:04:41Z")

</div>

Hello everyone I’m using suricata and have now update to suricata version 7.0.5 today on debian 12 unfortunately noticed suricata-update didn’t update along side it and is still in version 1.2.7 and is very far behind in updates compared to suricata it self , i really needed version 1.3.0 because there was a fix for MISP rules where they didn’t work because the file didn’t end with .rules

---

<div class="post-metadata">

**Author:** ![vjulien](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/vjulien/32/4_2.png) [@vjulien](https://forum.suricata.io/u/vjulien)\
**Post date:** [May 3, 2024, 7:28am UTC](https://forum.suricata.io/t/suricata-update-far-behind-in-debian/4636/2 "2024-05-03T07:28:50Z")

</div>

Looks like 1.3.3 is in testing: [suricata-update - Debian Package Tracker](https://tracker.debian.org/pkg/suricata-update)

Generally, I don’t think Debian updates major versions in stable, right @satta ?

---

<div class="post-metadata">

**Author:** ![gordnho](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/gordnho/32/2837_2.png) [@gordnho](https://forum.suricata.io/u/gordnho)\
**Post date:** [May 3, 2024, 7:32am UTC](https://forum.suricata.io/t/suricata-update-far-behind-in-debian/4636/3 "2024-05-03T07:32:14Z")

</div>

Yes the problem is for example we have the stable bpo version 7.0.5 and when i updated it today i was expecting suricata-update to do the same since they “should” come together maybe this is something you guys could take a look because it seems to be inconsistent

[https://tracker.debian.org/pkg/suricata](https://tracker.debian.org/pkg/suricata)

---

<div class="post-metadata">

**Author:** ![satta](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/satta/32/18_2.png) [@satta](https://forum.suricata.io/u/satta)\
**Post date:** [May 3, 2024, 7:38am UTC](https://forum.suricata.io/t/suricata-update-far-behind-in-debian/4636/4 "2024-05-03T07:38:38Z")

</div>

> Generally, I don’t think Debian updates major versions in stable, right @satta ?

Right. But AFAICS @gordnho mentioned stable-backports and not stable.

Unfortunately there has not been a backport for suricata-update so far, so even if I upload one now, it will need to be manually reviewed to clear backports-NEW. This might take a while. If you want I can provide you with a stable .deb here.

---

<div class="post-metadata">

**Author:** ![gordnho](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/gordnho/32/2837_2.png) [@gordnho](https://forum.suricata.io/u/gordnho)\
**Post date:** [May 3, 2024, 7:43am UTC](https://forum.suricata.io/t/suricata-update-far-behind-in-debian/4636/5 "2024-05-03T07:43:13Z")

</div>

Thanks a lot Sascha .

It’s not an urgent request since we are just still running test servers to deploy suricata permanently soon, but is this something that you will be doing in the future or will you just stick with updating the stable version.

Also thank a lot for your team for the quick answers.

---

<div class="post-metadata">

**Author:** ![satta](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/satta/32/18_2.png) [@satta](https://forum.suricata.io/u/satta)\
**Post date:** [May 3, 2024, 7:55am UTC](https://forum.suricata.io/t/suricata-update-far-behind-in-debian/4636/6 "2024-05-03T07:55:07Z")

</div>

Uploaded the backport, hopefully it’ll be through the NEW queue quickly. (You can track the progress via [Debian NEW and BYHAND Packages](https://ftp-master.debian.org/backports-new.html) where it should be listed soon)

Here’s the bookworm deb for you, if you want it directly:  
[bookworm-backports-suricata-update-1.3.3.zip](https://forum.suricata.io/uploads/short-url/dzrmCHz8qeeHfy93KMRnMqEQFHy.zip) (61.5 KB)

(You’d need to unzip it before since `.deb` uploads are not supported here)

---

<div class="post-metadata">

**Author:** ![satta](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/satta/32/18_2.png) [@satta](https://forum.suricata.io/u/satta)\
**Post date:** [May 3, 2024, 7:57am UTC](https://forum.suricata.io/t/suricata-update-far-behind-in-debian/4636/7 "2024-05-03T07:57:12Z")

</div>

> [@gordnho](#):
>
> is this something that you will be doing in the future or will you just stick with updating the stable version

I usually try to provide stable backports for new versions as soon as the new packages hit testing, but it must have slipped off my radar this time.

---

<div class="post-metadata">

**Author:** ![gordnho](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/gordnho/32/2837_2.png) [@gordnho](https://forum.suricata.io/u/gordnho)\
**Post date:** [May 3, 2024, 7:58am UTC](https://forum.suricata.io/t/suricata-update-far-behind-in-debian/4636/8 "2024-05-03T07:58:26Z")

</div>

Thanks a lot,no problems 👍

---

<div class="post-metadata">

**Author:** ![eleanelbert](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/eleanelbert/32/2915_2.png) [@eleanelbert](https://forum.suricata.io/u/eleanelbert)\
**Post date:** [May 29, 2024, 12:50pm UTC](https://forum.suricata.io/t/suricata-update-far-behind-in-debian/4636/9 "2024-05-29T12:50:43Z")

</div>

You might want to check the Suricata-update documentation or the Debian package repository for any available updates or patches.

---

<div class="post-metadata">

**Author:** ![gordnho](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/gordnho/32/2837_2.png) [@gordnho](https://forum.suricata.io/u/gordnho)\
**Post date:** [May 29, 2024, 12:57pm UTC](https://forum.suricata.io/t/suricata-update-far-behind-in-debian/4636/11 "2024-05-29T12:57:16Z")

</div>

The “issue” has been fixed by Sascha since the suricata-update was behind in debian

---

<div class="post-metadata">

**Author:** ![satta](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/satta/32/18_2.png) [@satta](https://forum.suricata.io/u/satta)\
**Post date:** [June 3, 2024, 1:46pm UTC](https://forum.suricata.io/t/suricata-update-far-behind-in-debian/4636/12 "2024-06-03T13:46:45Z")

</div>

FYI, it’s now version 1.3.3 in testing and bookworm-backports.
