From: Leandro Roggerone <leandro@tecnetmza.com.ar>
To: PVE User List <pve-user@pve.proxmox.com>
Subject: [PVE-User] (no subject)
Date: Tue, 17 Aug 2021 11:37:49 -0300 [thread overview]
Message-ID: <CALt2oz7a9byh5HX-YcPoQBZ=YJguxY3vGqA=iayQzoGdfcZGuQ@mail.gmail.com> (raw)
root@pve:~# apt-get update
Get:1 http://security.debian.org buster/updates InRelease [65.4 kB]
Get:2 http://ftp.debian.org/debian buster InRelease [122 kB]
Get:3 http://ftp.debian.org/debian buster-updates InRelease [51.9 kB]
Reading package lists... Done
E: Repository 'http://security.debian.org buster/updates InRelease' changed
its 'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can
be applied. See apt-secure(8) manpage for details.
E: Repository 'http://ftp.debian.org/debian buster InRelease' changed its
'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can
be applied. See apt-secure(8) manpage for details.
E: Repository 'http://ftp.debian.org/debian buster-updates InRelease'
changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
N: This must be accepted explicitly before updates for this repository can
be applied. See apt-secure(8) manpage for details.
This is my source.list
root@pve:~# cat /etc/apt/sources.list
deb http://ftp.debian.org/debian buster main contrib
deb http://ftp.debian.org/debian buster-updates main contrib
# security updates
deb http://security.debian.org buster/updates main contrib
This was working ok until sat 14.
Any idea ?
Thanks!
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Libre
de virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
next reply other threads:[~2021-08-17 14:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 14:37 Leandro Roggerone [this message]
[not found] ` <mailman.458.1629211453.329.pve-user@lists.proxmox.com>
2021-08-18 13:19 ` Leandro Roggerone
[not found] ` <e5a1f5ef-ab9b-9283-cd90-6aba6acc35ba@holub.co.at>
2021-08-24 15:13 ` Leandro Roggerone
2021-08-24 15:36 ` Alain Péan
[not found] ` <1aca635b-412d-c199-2382-629b16457939@holub.co.at>
2021-08-25 12:11 ` Leandro Roggerone
-- strict thread matches above, loose matches on Subject: below --
2023-08-29 23:11 Christian Karg
[not found] <CAGehcqHmTqfjBRwt61hWjjA1CQm8inajfS0=EOqCPrAdmGUheA@mail.gmail.com>
2023-07-24 8:58 ` Aaron Lauterer
2021-02-25 20:18 Aaron Wood
2021-02-26 11:17 ` Thomas Lamprecht
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='CALt2oz7a9byh5HX-YcPoQBZ=YJguxY3vGqA=iayQzoGdfcZGuQ@mail.gmail.com' \
--to=leandro@tecnetmza.com.ar \
--cc=pve-user@pve.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