Update monit to 5.27.x on Ubuntu 20.04 LTS

Asked by Steve Piercy

Would it be possible to update monit to 5.27.x on Ubuntu 20.04 LTS?

monit 5.27.0 adds support for pemchain and pemkey, which are the default files that Let's Encrypt creates.


Thank you for your consideration.

Question information

English Edit question
Ubuntu monit Edit question
No assignee Edit question
Solved by:
Manfred Hampl
Last query:
Last reply:
Revision history for this message
Manfred Hampl (m-hampl) said :

For the rules with respect to updating a package in an already-published Ubuntu release please see:
FAQ #3037: “no rolling release”.

Revision history for this message
Steve Piercy (bx0-ozb-zwn) said :

Is there a planned 20.04.3 release, beyond 20.04.2?

Also after reading the FAQ and linked articles, it is not clear to me whether 20.04.3 would be a new release or not. Can you clarify?

In either case, I think that monit 5.27.0 would qualify within the SRU under "2.2. Other safe cases", in the third bullet point:


I would be happy to champion this, if accepted, and make the contribution.

Thank you for your help.

Revision history for this message
Best Manfred Hampl (m-hampl) said :

Further point-releases are planned for Ubuntu 20.04, see https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule for the planned dates of 20.04.3 and 20.04.4, but they do not qualify as "new release" for updates to existing packages.

I doubt that "2.2. Other safe cases" of the SRU procedure is really applicable here.

I see another potential problem:
monit version 1:5.27.2-1 from Ubuntu hirsute depends on libc6 (>= 2.32), but Ubuntu focal has only libc6 2.31-*

You can try creating a bug report following the SRU procedure, but I am not optimistic that this will lead to an implementation of 5.27.x in focal.

Revision history for this message
Steve Piercy (bx0-ozb-zwn) said :

Thank you for taking the time to explain this for me, and especially the lack of optimism. I appreciate your candor.

I found a workaround for Let's Encrypt certificate and certbot users in the following Server Fault post, where the renewed/created certificates are concatenated in a post-hook script, just in case someone else finds this question.