Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: Update support for Ubuntu #2407

Closed
wants to merge 1 commit into from
Closed

Conversation

sebix
Copy link
Member

@sebix sebix commented Sep 6, 2023

Ubuntu 20.04 is no longer supported because it only has dnspython 1.16.0, but intelmq requires >= 2.0.0
On Ubuntu 22.04, intelmq is available, but not intelmq-api

@sebix sebix added bug Indicates an unexpected problem or unintended behavior documentation Indicates a need for improvements or additions to documentation labels Sep 6, 2023
@sebix sebix added this to the 3.2.2 milestone Sep 6, 2023
@aaronkaplan
Copy link
Member

Hm... what to do? Still plenty of 20.04 installations around.... and officially still supported.

"For each Ubuntu LTS release, Canonical maintains the Base Packages and provides security updates, including kernel livepatching, for a period of ten years. The lifecycle consists of an initial five-year standard security maintenance period, during which maintenance updates are publicly available without a subscription"
(source: https://ubuntu.com/about/release-cycle).

So for 20.04 this would mean that it's supported without ESM until April 2025 (!)

@sebix
Copy link
Member Author

sebix commented Sep 6, 2023

Actually with the backport of dnspython in the repos, it should still work, changed the text accordingly. intelmq-api is an issue with ubuntu and Debian 10.

Ubuntu 20.04 is no longer supported because it only has dnspython 1.16.0,
but intelmq requires >= 2.0.0
On Ubuntu 22.04, intelmq is available, but not intelmq-api
* openSUSE Tumbleweed, Leap 15.5
* Ubuntu: 20.04 Focal, 22.04 Jammy
* Ubuntu: 22.04 Jammy
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If deb still supports Ubuntu 20, shouldn't it be listed here as well? Or you wanted to make a difference between recommended and minimally supported?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or you wanted to make a difference between recommended and minimally supported?

Not sure how to describe the situation in the docs ideally. Buster and Focal work, but only with upgrading packages (either custom repo or pip3). Maybe making a separated list "Supported, but not recommended for new installations"?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay, I'll create an issue for this topic and we can revisit the documentation on that topic later. See #2451

@aaronkaplan
Copy link
Member

aaronkaplan commented Sep 6, 2023 via email

@sebix
Copy link
Member Author

sebix commented Sep 6, 2023

and larger orgs don't change soo often if the bugfix support is given.

These larger orgs also have the resources. They just lack the will to contribute to IntelMQ.

@kamil-certat
Copy link
Contributor

kamil-certat commented Sep 7, 2023

I'd suggest two sections:

  • Recommended setup – only the newest LTS/active, described as where we put the main effort
  • Supported setup – here all current LTS/active, described as where we want IntelMQ to work on and are open for any bug reports

EDIT: And a note that we are open for every contribution, also for not officially supported setups

@aaronkaplan
Copy link
Member

and larger orgs don't change soo often if the bugfix support is given.

These larger orgs also have the resources. They just lack the will to contribute to IntelMQ.

Well, working at one, I know that they have all kinds of other topics which often stop them from even being able to do so.
But that's another discussion and won't bring us forward here.

@aaronkaplan
Copy link
Member

I am fine with the proposed changes in this PR as is.

@aaronkaplan
Copy link
Member

Merging in, since we moved the documentation change to later . See #2451

@aaronkaplan
Copy link
Member

Closing as discussed in the chat.... We may re-open it if needed and wade through the mud of merging this one :)

@aaronkaplan aaronkaplan closed this Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or unintended behavior documentation Indicates a need for improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants