You are attempting to remove the meta-package 'proxmox-ve'!

ardev

New Member
Jun 18, 2023
3
0
1
I am attempting to install the gnome-keyring package on my server and it keeps resulting in the following error:

Code:
Do you want to continue? [Y/n] y
W: (pve-apt-hook) !! WARNING !!
W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'!
W: (pve-apt-hook)
W: (pve-apt-hook) If you really want to permanently remove 'proxmox-ve' from your system, run the following command
W: (pve-apt-hook)       touch '/please-remove-proxmox-ve'
W: (pve-apt-hook) run apt purge proxmox-ve to remove the meta-package
W: (pve-apt-hook) and repeat your apt invocation.
W: (pve-apt-hook)
W: (pve-apt-hook) If you are unsure why 'proxmox-ve' would be removed, please verify
W: (pve-apt-hook)       - your APT repository settings
W: (pve-apt-hook)       - that you are using 'apt full-upgrade' to upgrade your system
E: Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code (1)
E: Failure running script /usr/share/proxmox-ve/pve-apt-hook
 
What command did you use? What is in /etc/apt/sources.list and the files in /etc/apt/sources.list.d?
Took me a minute to respond but here you go

Command Used: apt-get install gnome-keyring

etc/apt/sources.list:
Code:
root@server:~# cat /etc/apt/sources.list
# deb http://asi-fs-y.contabo.net/debian buster main

deb http://asi-fs-y.contabo.net/debian buster main non-free contrib
deb-src http://asi-fs-y.contabo.net/debian buster main non-free contrib

deb http://security.debian.org/debian-security buster/updates main contrib non-free
deb-src http://security.debian.org/debian-security buster/updates main contrib non-free

# buster-updates, previously known as 'volatile'
deb http://asi-fs-y.contabo.net/debian buster-updates main contrib non-free
deb-src http://asi-fs-y.contabo.net/debian buster-updates main contrib non-free
## These are official Contabo mirrors providing faster updates for your server ##
## (the files from the official servers are synced to it) ##

# Experimental/unstable (sid) repositories
deb http://ftp.debian.org/debian experimental main
deb http://ftp.debian.org/debian sid main

/etc/apt/sources.list.d:

Code:
root@server:~# ls /etc/apt/sources.list.d
ceph.list    java.list             nodesource.list      pve-enterprise.list.save
docker.list  mongodb-org-5.0.list  pve-enterprise.list  pve-install-repo.list
 
Oh, man, where to begin...

First off you have experimental and sid activated while running buster. That is a very, very, bad idea. Sid is 3 versions ahead of buster. Unless you have done some pinning when you install anything it is going to pull from sid/experimental and will try to upgrade vast swathes of your system. Since PVE is probably on an older version (based on Buster) it may well try to uninstall PVE to get a consistent configuration. I think you are getting a much larger message than you posted.

I would say to remove those two lines but that may not be enough if you have installed anything or attempted an upgrade in this configuration. There is also a pretty large list of third-party repositories that are at who knows what version. That can potentially cause similar problems.

You basically need to clean up your repositories and get everything on the same version. That is the fundamental issue here,
 
  • Like
Reactions: spirit
Oh, man, where to begin...

First off you have experimental and sid activated while running buster. That is a very, very, bad idea. Sid is 3 versions ahead of buster. Unless you have done some pinning when you install anything it is going to pull from sid/experimental and will try to upgrade vast swathes of your system. Since PVE is probably on an older version (based on Buster) it may well try to uninstall PVE to get a consistent configuration. I think you are getting a much larger message than you posted.

I would say to remove those two lines but that may not be enough if you have installed anything or attempted an upgrade in this configuration. There is also a pretty large list of third-party repositories that are at who knows what version. That can potentially cause similar problems.

You basically need to clean up your repositories and get everything on the same version. That is the fundamental issue here,
I went ahead and removed the experimental and sid ones, I had added them by accident a while ago and forgot to remove them. But once removing them it allowed me to install gnome-keyring! Thank you very much
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!