Following packages have been kept back

When running the usual…

apt-get update && sudo apt-get upgrade

…I’m greeted with the following:

The following packages have been kept back:
  freepbx17 node-es-module-lexer node-globby node-tap

Everything seems to up-to-date though. Is this something to worry about? Or something that’ll be resolved automagically?

Not feeling like waiting around, I executed the following command:

apt-get install freepbx17 node-es-module-lexer node-globby node-tap

Lots of things happened and at one moment it seemed to break my install completely. After running apt-get update && sudo apt-get upgrade I was greeted by 27 vulnerabilities which I was able to revolve by running the following commands:

fwconsole ma refreshsignatures
fwconsole chown
fwconsole reload

In the end I wasn’t able to dial *97 while *98 did work. And incoming calls were dropped. Meanwhile I rolled back a snapshot.

Anyone?

I am also wondering the same thing. I am assuming the hold is intentional, but I have been seeing these for awhile, now. I am showing these packages held back:

node-tap node-globby node-es-module-lexer

Still having the same thing. I did run…

apt-get install node-es-module-lexer node-globby node-tap

To get rid of part of it, but when I add freepbx17 to the mix, my install is f-d.

Thanks.
I don’t show freepbx17 as being held back. I am assuming the holds are to make sure of no problems, but I think I have seen these packages on hold going back in November (or longer).

Strange thing is that I only have this issue on one of my servers. The one my client’s are on doesn’t show does.

So what it comes down to is that this is a feature no bug? And how is FreePBX updated when this is in place?

FreePBX17 won’t need to be updated until there is a FeePBX18. I’m sure the subcomponents of FreePBX will get more granular attention. To get rid of the warnings

apt remove FreePBX17

https://sangomakb.atlassian.net/wiki/spaces/PG/pages/20351208/Module+Admin+Module

Then wouldn’t it be a good idea to add that line to the install script?

Oh: “apt remove freepbx17” completely removed FreePBX from my server… recovering now. Beginning to think I did something wrong installing in the first place.

Hi All

Happy New Year 2025 !!

Please find following packages which are purposefully kept on-hold to ensure the stability and functionality of FreePBX. Below are the details:

1. FreePBX17 Package

  • This Debian package is used for the initial setup of FreePBX.
  • While the package itself is not required post-setup, removing it (apt remove freepbx17) would delete associated files and disrupt default FreePBX settings.
  • To prevent unintended updates to newer versions that could alter behavior, we have placed this package on hold.

2. Node.js Packages

  • Node.js is critical for FreePBX UCP and several commercial modules like Talk and Desktop Phone.
  • With FreePBX 17, we upgraded Node.js (and its dependencies), requiring significant compatibility work.
  • Uncontrolled updates via apt upgrade could lead to compatibility issues, so these packages are on hold.
  • Updates to Node.js and its dependencies will occur only after internal QA approval.

3. Linux Kernel (for DAHDI Users)

  • DAHDI/Wanpipe is heavily dependent on the underlying Linux kernel.
  • For FreePBX installations using DAHDI, we hold the kernel version to avoid incompatibilities with the latest Debian kernel updates.

If you have any questions or need clarification, please feel free to reach out.

Best Regards,
Kapil

@kgupta - Thank you for the information and confirmation. I appreciate it.

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