starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 08:40:11 +03:00
Code Issues 23 Packages Projects Releases 10 Wiki Activity

Semaphore update failing due to wrong binary #2179

New Issue
Closed
opened 2026-02-05 04:07:14 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-05 04:07:14 +03:00
Owner
Copy Link

Originally created by @jershbytes on GitHub (Dec 17, 2025).

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 What is the name of the script you are using?

Semaphore

📂 What was the exact command used to execute the script?

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

9.1.2

📝 Provide a clear and concise description of the issue.

Running an update within the Semaphore lxc fails to the wrong binary trying to be installed.

🔄 Steps to reproduce the issue.

pct enter 106
update

❌ Paste the full error output (if available).

✔️   Update available: semaphore 2.16.45 → 2.16.46
  ✔️   Stopped Service
Reading package lists... Donee: semaphore (2.16.46)
Building dependency tree... Done
Reading state information... Done
Note, selecting 'semaphorepro' instead of '/tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb'
The following NEW packages will be installed:
  semaphorepro
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/17.1 MB of archives.
After this operation, 47.0 MB of additional disk space will be used.
Get:1 /tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb semaphorepro amd64 2.16.46 [17.1 MB]
(Reading database ... 50302 files and directories currently installed.)
Preparing to unpack .../semaphorepro_2.16.46_linux_amd64.deb ...
Unpacking semaphorepro (2.16.46) ...
dpkg: error processing archive /tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb (--unpack):
 trying to overwrite '/usr/bin/semaphore', which is also in package semaphore 2.16.45
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb
N: Download is performed unsandboxed as root as file '/tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
E: Sub-process /usr/bin/dpkg returned an error code (1)
(Reading database ... 50302 files and directories currently installed.)
Preparing to unpack .../semaphorepro_2.16.46_linux_amd64.deb ...
Unpacking semaphorepro (2.16.46) ...
dpkg: error processing archive /tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb (--install):
 trying to overwrite '/usr/bin/semaphore', which is also in package semaphore 2.16.45
dpkg-deb (subprocess): decompressing archive '/tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb' (size=17139546) member 'data.tar': internal gzip write error: Broken pipe
dpkg-deb: error: <decompress> subprocess returned error exit status 2
dpkg-deb (subprocess): cannot copy archive member from '/tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb' to decompressor pipe: failed to write (Broken pipe)
Errors were encountered while processing:
 /tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb
  ✖️   Both apt and dpkg installation failed
  ✖️   in line 36: exit code 1 (General error / Operation not permitted): while executing command return 1

🖼️ Additional context (optional).

https://github.com/semaphoreui/semaphore/releases

Looking at the new release of semaphore it looks like they have started shipping all of the binaries under the same repo. from my finding it looks like it may just need to be narrowed down to the regular and not the pro .deb package.

Originally created by @jershbytes on GitHub (Dec 17, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? Semaphore ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 9.1.2 ### 📝 Provide a clear and concise description of the issue. Running an update within the Semaphore lxc fails to the wrong binary trying to be installed. ### 🔄 Steps to reproduce the issue. ```bash pct enter 106 update ``` ### ❌ Paste the full error output (if available). ```bash ✔️ Update available: semaphore 2.16.45 → 2.16.46 ✔️ Stopped Service Reading package lists... Donee: semaphore (2.16.46) Building dependency tree... Done Reading state information... Done Note, selecting 'semaphorepro' instead of '/tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb' The following NEW packages will be installed: semaphorepro 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/17.1 MB of archives. After this operation, 47.0 MB of additional disk space will be used. Get:1 /tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb semaphorepro amd64 2.16.46 [17.1 MB] (Reading database ... 50302 files and directories currently installed.) Preparing to unpack .../semaphorepro_2.16.46_linux_amd64.deb ... Unpacking semaphorepro (2.16.46) ... dpkg: error processing archive /tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb (--unpack): trying to overwrite '/usr/bin/semaphore', which is also in package semaphore 2.16.45 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb N: Download is performed unsandboxed as root as file '/tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) E: Sub-process /usr/bin/dpkg returned an error code (1) (Reading database ... 50302 files and directories currently installed.) Preparing to unpack .../semaphorepro_2.16.46_linux_amd64.deb ... Unpacking semaphorepro (2.16.46) ... dpkg: error processing archive /tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb (--install): trying to overwrite '/usr/bin/semaphore', which is also in package semaphore 2.16.45 dpkg-deb (subprocess): decompressing archive '/tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb' (size=17139546) member 'data.tar': internal gzip write error: Broken pipe dpkg-deb: error: <decompress> subprocess returned error exit status 2 dpkg-deb (subprocess): cannot copy archive member from '/tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb' to decompressor pipe: failed to write (Broken pipe) Errors were encountered while processing: /tmp/tmp.xCGEwVGzyF/semaphorepro_2.16.46_linux_amd64.deb ✖️ Both apt and dpkg installation failed ✖️ in line 36: exit code 1 (General error / Operation not permitted): while executing command return 1 ``` ### 🖼️ Additional context (optional). https://github.com/semaphoreui/semaphore/releases Looking at the new release of semaphore it looks like they have started shipping all of the binaries under the same repo. from my finding it looks like it may just need to be narrowed down to the regular and not the pro .deb package.
OVERLORD added the bug label 2026-02-05 04:07:14 +03:00
OVERLORD commented 2026-02-05 04:07:20 +03:00
Author
Owner
Copy Link

@jershbytes commented on GitHub (Dec 17, 2025):

I think all we might need to do here is add the _ after the semaphore to grab the correct .deb binary.


function update_script() {
  header_info
  check_container_storage
  check_container_resources

  if [[ ! -f /etc/systemd/system/semaphore.service ]]; then
    msg_error "No ${APP} Installation Found!"
    exit
  fi
  if check_for_gh_release "semaphore" "semaphoreui/semaphore"; then
    msg_info "Stopping Service"
    systemctl stop semaphore
    msg_ok "Stopped Service"

    fetch_and_deploy_gh_release "semaphore_" "semaphoreui/semaphore" "binary"

    msg_info "Starting Service"
    systemctl start semaphore
    msg_ok "Started Service"
    msg_ok "Updated successfully!"
  fi
  exit
}
@jershbytes commented on GitHub (Dec 17, 2025): I think all we might need to do here is add the `_` after the semaphore to grab the correct .deb binary. ```bash function update_script() { header_info check_container_storage check_container_resources if [[ ! -f /etc/systemd/system/semaphore.service ]]; then msg_error "No ${APP} Installation Found!" exit fi if check_for_gh_release "semaphore" "semaphoreui/semaphore"; then msg_info "Stopping Service" systemctl stop semaphore msg_ok "Stopped Service" fetch_and_deploy_gh_release "semaphore_" "semaphoreui/semaphore" "binary" msg_info "Starting Service" systemctl start semaphore msg_ok "Started Service" msg_ok "Updated successfully!" fi exit } ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2179
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?