From: Petric Frank <pfrank@gmx.de>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: [PVE-User] Solved: Re: dist-upgrade throws error
Date: Sat, 08 Jan 2022 00:37:41 +0100 [thread overview]
Message-ID: <5684758.MhkbZ0Pkbq@main> (raw)
In-Reply-To: <8877761.CDJkKcVGEf@main>
Hello,
somehow there was a package on hold which blocked the upgrade.
regards
Am Freitag, 7. Januar 2022, 12:46:12 CET schrieb Petric Frank:
> Hallo,
>
> followup - found the pve repository wrongly configured. Now set to
> deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription
>
> according to https://pve.proxmox.com/wiki/Package_Repositories
>
> But no change in the error.
>
> regards
>
> Am Freitag, 7. Januar 2022, 12:03:15 CET schrieb Petric Frank:
> > Hello,
> >
> > during the upgrade this morning i get the following error message:
> > --------------------- cut ---------------------
> > root@proxmox:~# apt dist-upgrade
> > Reading package lists... Done
> > Building dependency tree... Done
> > Reading state information... Done
> > Calculating upgrade... Error!
> > Some packages could not be installed. This may mean that you have
> > requested an impossible situation or if you are using the unstable
> > distribution that some required packages have not yet been created
> > or been moved out of Incoming.
> > The following information may help to resolve the situation:
> >
> > The following packages have unmet dependencies:
> > libpve-common-perl : Breaks: qemu-server (< 7.0-19) but 7.0-13 is to be
> >
> > installed
> > E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused
> > by held packages.
> > --------------------- cut ---------------------
> >
> > apt update was executed before without issues. I am using the "no-
> >
> > subscription" repository:
> > deb http://download.proxmox.com/debian bullseye pve-no-subscription
> >
> > Could the repository have a problem ?
> >
> > Any hints ?
> >
> > kind regards
> >
> >
> >
> >
> > _______________________________________________
> > pve-user mailing list
> > pve-user@lists.proxmox.com
> > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2022-01-07 23:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 11:03 [PVE-User] " Petric Frank
2022-01-07 11:46 ` Petric Frank
2022-01-07 23:37 ` Petric Frank [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5684758.MhkbZ0Pkbq@main \
--to=pfrank@gmx.de \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox