SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Unable to install change detection (issue installing msedge) #642

New Issue
Open
opened 2025-11-20 04:51:31 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 04:51:31 -05:00
Owner
Copy Link

Originally created by @kipusoep on GitHub (Mar 4, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Change Detection

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/changedetection.sh)"

📝 Provide a clear and concise description of the issue.

I am getting an error while it tries to install msedge, tried it 3 times:

+ install -o root -g root -m 644 /tmp/microsoft.gpg /etc/apt/trusted.gpg.d/
+ sh -c 'echo "deb [arch=amd64] https://packages.microsoft.com/repos/edge stable main" > /etc/apt/sources.list.d/microsoft-edge-stable.list'
+ rm /tmp/microsoft.gpg
+ apt-get update
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://security.debian.org bookworm-security InRelease                                                                                                                                        
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease                                                                                                                                       
Hit:4 https://dl.google.com/linux/chrome/deb stable InRelease                                                                                                                                       
Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease                                                                                                                 
Hit:6 https://packages.microsoft.com/repos/edge stable InRelease
Reading package lists... Done
+ apt-get install -y microsoft-edge-stable
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  microsoft-edge-stable
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/170 MB of archives.
After this operation, 602 MB of additional disk space will be used.
(Reading database ... 50135 files and directories currently installed.)
Preparing to unpack .../microsoft-edge-stable_133.0.3065.92-1_amd64.deb ...
Unpacking microsoft-edge-stable (133.0.3065.92-1) ...
dpkg-deb: error: <decompress> subprocess was killed by signal (Killed)
dpkg: error processing archive /var/cache/apt/archives/microsoft-edge-stable_133.0.3065.92-1_amd64.deb (--unpack):
 cannot copy extracted data for './opt/microsoft/msedge/msedge' to '/opt/microsoft/msedge/msedge.dpkg-new': unexpected end of file or stream

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Install the script

❌ Paste the full error output (if available).

+ install -o root -g root -m 644 /tmp/microsoft.gpg /etc/apt/trusted.gpg.d/
+ sh -c 'echo "deb [arch=amd64] https://packages.microsoft.com/repos/edge stable main" > /etc/apt/sources.list.d/microsoft-edge-stable.list'
+ rm /tmp/microsoft.gpg
+ apt-get update
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://security.debian.org bookworm-security InRelease                                                                                                                                        
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease                                                                                                                                       
Hit:4 https://dl.google.com/linux/chrome/deb stable InRelease                                                                                                                                       
Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease                                                                                                                 
Hit:6 https://packages.microsoft.com/repos/edge stable InRelease
Reading package lists... Done
+ apt-get install -y microsoft-edge-stable
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  microsoft-edge-stable
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/170 MB of archives.
After this operation, 602 MB of additional disk space will be used.
(Reading database ... 50135 files and directories currently installed.)
Preparing to unpack .../microsoft-edge-stable_133.0.3065.92-1_amd64.deb ...
Unpacking microsoft-edge-stable (133.0.3065.92-1) ...
dpkg-deb: error: <decompress> subprocess was killed by signal (Killed)
dpkg: error processing archive /var/cache/apt/archives/microsoft-edge-stable_133.0.3065.92-1_amd64.deb (--unpack):
 cannot copy extracted data for './opt/microsoft/msedge/msedge' to '/opt/microsoft/msedge/msedge.dpkg-new': unexpected end of file or stream

🖼️ Additional context (optional).

No response

Originally created by @kipusoep on GitHub (Mar 4, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Change Detection ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/changedetection.sh)" ### 📝 Provide a clear and concise description of the issue. I am getting an error while it tries to install msedge, tried it 3 times: ``` + install -o root -g root -m 644 /tmp/microsoft.gpg /etc/apt/trusted.gpg.d/ + sh -c 'echo "deb [arch=amd64] https://packages.microsoft.com/repos/edge stable main" > /etc/apt/sources.list.d/microsoft-edge-stable.list' + rm /tmp/microsoft.gpg + apt-get update Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://security.debian.org bookworm-security InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 https://dl.google.com/linux/chrome/deb stable InRelease Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease Hit:6 https://packages.microsoft.com/repos/edge stable InRelease Reading package lists... Done + apt-get install -y microsoft-edge-stable Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: microsoft-edge-stable 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/170 MB of archives. After this operation, 602 MB of additional disk space will be used. (Reading database ... 50135 files and directories currently installed.) Preparing to unpack .../microsoft-edge-stable_133.0.3065.92-1_amd64.deb ... Unpacking microsoft-edge-stable (133.0.3065.92-1) ... dpkg-deb: error: <decompress> subprocess was killed by signal (Killed) dpkg: error processing archive /var/cache/apt/archives/microsoft-edge-stable_133.0.3065.92-1_amd64.deb (--unpack): cannot copy extracted data for './opt/microsoft/msedge/msedge' to '/opt/microsoft/msedge/msedge.dpkg-new': unexpected end of file or stream ``` ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Install the script ### ❌ Paste the full error output (if available). ``` + install -o root -g root -m 644 /tmp/microsoft.gpg /etc/apt/trusted.gpg.d/ + sh -c 'echo "deb [arch=amd64] https://packages.microsoft.com/repos/edge stable main" > /etc/apt/sources.list.d/microsoft-edge-stable.list' + rm /tmp/microsoft.gpg + apt-get update Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://security.debian.org bookworm-security InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 https://dl.google.com/linux/chrome/deb stable InRelease Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease Hit:6 https://packages.microsoft.com/repos/edge stable InRelease Reading package lists... Done + apt-get install -y microsoft-edge-stable Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: microsoft-edge-stable 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/170 MB of archives. After this operation, 602 MB of additional disk space will be used. (Reading database ... 50135 files and directories currently installed.) Preparing to unpack .../microsoft-edge-stable_133.0.3065.92-1_amd64.deb ... Unpacking microsoft-edge-stable (133.0.3065.92-1) ... dpkg-deb: error: <decompress> subprocess was killed by signal (Killed) dpkg: error processing archive /var/cache/apt/archives/microsoft-edge-stable_133.0.3065.92-1_amd64.deb (--unpack): cannot copy extracted data for './opt/microsoft/msedge/msedge' to '/opt/microsoft/msedge/msedge.dpkg-new': unexpected end of file or stream ``` ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 04:51:31 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#642
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?