[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#933344: marked as done (Update debian/testing64 vagrant box (too old to update to unstable))

Your message dated Sun, 6 Oct 2019 13:33:11 +0200
with message-id <20191006113311.GA12676@xanadu.blop.info>
and subject line Re: Bug#933344: Update debian/testing64 vagrant box (too old to update to unstable)
has caused the Debian Bug report #933344,
regarding Update debian/testing64 vagrant box (too old to update to unstable)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
933344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933344
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cloud.debian.org
Severity: grave
I was trying to use the default debian/testing64 vagrant box, but it is too old to even update to sid. Please provide an updated version of this image. 

$ sudo apt update
Get:1 http://deb.debian.org/debian unstable InRelease [149 kB]
Err:1 http://deb.debian.org/debian unstable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 04EE7237B7D453EC NO_PUBKEY 648ACFD622F3D138 
Reading package lists... Done
W: GPG error: http://deb.debian.org/debian unstable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 04EE7237B7D453EC NO_PUBKEY 648ACFD622F3D138 E: The repository 'http://deb.debian.org/debian unstable InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. 
vagrant@stretch:~$ sudo apt install debian-archive-keyring
Reading package lists... Done
Building dependency tree
Reading state information... Done
debian-archive-keyring is already the newest version (2014.3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

--- End Message ---
--- Begin Message --- 
Hi,

On 29/07/19 at 13:41 +0000, Pirate Praveen wrote:
> I was trying to use the default debian/testing64 vagrant box, but it is too
> old to even update to sid. Please provide an updated version of this image.
> 
> $ sudo apt update
> Get:1 http://deb.debian.org/debian unstable InRelease [149 kB]
> Err:1 http://deb.debian.org/debian unstable InRelease
>   The following signatures couldn't be verified because the public key is
> not available: NO_PUBKEY 04EE7237B7D453EC NO_PUBKEY 648ACFD622F3D138
> Reading package lists... Done
> W: GPG error: http://deb.debian.org/debian unstable InRelease: The following
> signatures couldn't be verified because the public key is not available:
> NO_PUBKEY 04EE7237B7D453EC NO_PUBKEY 648ACFD622F3D138
> E: The repository 'http://deb.debian.org/debian unstable InRelease' is not
> signed.
> N: Updating from such a repository can't be done securely, and is therefore
> disabled by default.
> N: See apt-secure(8) manpage for repository creation and user configuration
> details.
> vagrant@stretch:~$ sudo apt install debian-archive-keyring
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> debian-archive-keyring is already the newest version (2014.3).
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Thanks for the report.

I updated both debian/testing64 and debian/contrib-testing64 today. Feel
free to ping me when you feel that those boxes need an update: I don't
have much time for Debian nowadays, but do most of my Debian work inside
those boxes, so I have a net interest in keeping them updated.

Lucas

--- End Message ---
Reply to: