Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to 6.30 failed (from 29.2) #3576

Closed
Paulisper opened this issue May 30, 2020 · 2 comments
Closed

Update to 6.30 failed (from 29.2) #3576

Paulisper opened this issue May 30, 2020 · 2 comments
Labels
Duplicate For issues that are/were already handled within another issue

Comments

@Paulisper
Copy link

Sorry for posting this.
My Pi 3 could be updated to 6.30 without any flaw.
But my Pi 2 failed.
I am posting this because there was the request at the end of the failed update.
Thank you so much for coding and developing dietpi.
Kind regards,
Urban

Details:

  • Date | Sat May 30 17:52:14 CEST 2020
  • DietPi version | v6.29.2 (MichaIng/master)
  • Image creator | DietPi Core Team
  • Pre-image | Raspbian Lite
  • Hardware | RPi 2 Model B (armv7l) (ID=2)
  • Kernel version | Linux DietPi7 4.19.66-v7+ DietPi-Config | CPU performance benchmark #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
  • Distro | stretch (ID=4)
  • Command | apt-get -q update
  • Exit code | 100
  • Software title | DietPi-Update

Steps to reproduce:

  1. dietpi-update
  2. ...

Expected behaviour:

  • ...

Actual behaviour:

  • c below

Extra details:

  • self explaining, I guess. Sorry for not searching for a solution.
    I went back to 6.29.2,

Additional logs:

Hit:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Ign:2 https://archive.raspberrypi.org/debian stretch InRelease
Err:3 https://archive.raspberrypi.org/debian stretch Release
  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Reading package lists...
E: The repository 'https://archive.raspberrypi.org/debian stretch Release' does no longer have a Release file.
@Joulinar
Copy link
Collaborator

Hi,

Many thanks for you message. Yes this is known but nothing we can do against it.

See #3575

@Joulinar Joulinar added the Duplicate For issues that are/were already handled within another issue label May 30, 2020
@Joulinar
Copy link
Collaborator

issue fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Duplicate For issues that are/were already handled within another issue
Projects
None yet
Development

No branches or pull requests

2 participants