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

[bug]: freepbx17 package update 17.1-1.sng12 vs 17.1-1.sng12 #476

Open
hknet opened this issue Oct 6, 2024 · 2 comments
Open

[bug]: freepbx17 package update 17.1-1.sng12 vs 17.1-1.sng12 #476

hknet opened this issue Oct 6, 2024 · 2 comments
Labels
bug Something isn't working triage Triage

Comments

@hknet
Copy link

hknet commented Oct 6, 2024

FreePBX Version

FreePBX 17

Issue Description

apt update reports this package as upgradable:

apt list --upgradable -a
Listing... Done
freepbx17/bookworm 17.1-1.sng12 amd64 [upgradable from: 17.1-1.sng12]
freepbx17/now 17.1-1.sng12 amd64 [installed,upgradable to: 17.1-1.sng12]

it seems versioning is missing a point, but then again this package is set on hold (also a long list of other packages):

apt-mark showhold
freepbx17

so the basic question would be how to not get annoyed by apt that there is an update if there should never be an update.

Operating Environment

FreePBX17 on Debian v12

Relevant log output

apt-cache policy freepbx17
freepbx17:
  Installed: 17.1-1.sng12
  Candidate: 17.1-1.sng12
  Version table:
     17.1-1.sng12 600
        600 http://deb.freepbx.org/freepbx17-prod bookworm/main amd64 Packages
 *** 17.1-1.sng12 100
        100 /var/lib/dpkg/status
@hknet hknet added bug Something isn't working triage Triage labels Oct 6, 2024
@JoseGoncalves
Copy link

Hi @hknet. Please check this thread for an insight over the freepbx17 package versioning:

AFAIK there is no way to hide in Debian the holded packages (unless you write some custom script to wrap the apt command).

@hknet
Copy link
Author

hknet commented Oct 7, 2024

Hey @JoseGoncalves thx for pointing this out.
While I understand the rationale behind putting this on hold I'd suggest to maybe split the package into a gui-admin-part and and asterisk-default-conf part as I suspect an admin-gui-update might be needed (especially if a security issue arises).

On the other hand if it's a one-off filedump to lots of directories, maybe putting this into a package is not the best way forward.

regards!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage Triage
Projects
None yet
Development

No branches or pull requests

2 participants