On Sun, Dec 10, 2023 at 02:38:34PM +0100, Mario Marietto wrote: > Hello to everyone. > > I'm using Devuan 5 for arm32 on my ARM chromebook and I've just tried to > update the system,but I failed. >
Hi Mario, You're on your own for two reasons: one is that relatively few of us will be running on an ARM chromebook, the second is that you're asking a Devuan question. With the best will in the world, the best that we can give you on this list is "best endeavours" answers: other Debian-based distributions may do things very differently and the good people here may not have the answers to give. > This is the sources.list file that I'm using : > > deb http://pkg.bunsenlabs.org/debian beryllium main > Bunsenlabs is at best Debian-based (as a continuation of Crunchbang). I've no idea how good their ARM port is here. > deb http://deb.devuan.org/merged daedalus main > deb http://deb.devuan.org/merged daedalus-updates main > deb http://deb.devuan.org/merged daedalus-security main > deb http://deb.devuan.org/merged daedalus-backports main > > deb-src http://deb.devuan.org/merged daedalus main > deb-src http://deb.devuan.org/merged daedalus-updates main > deb-src http://deb.devuan.org/merged daedalus-security main > deb-src http://deb.devuan.org/merged daedalus-backports main > Ask Devuan: is there any particular reason you're using Devuan here rather than Debian? > # apt update > > Hit:1 http://pkg.bunsenlabs.org/debian beryllium InRelease > Get:2 http://deb.devuan.org/merged daedalus InRelease [42.4 kB] > Get:3 http://deb.devuan.org/merged daedalus-updates InRelease [32.5 kB] > Get:4 http://deb.devuan.org/merged daedalus-security InRelease [32.5 kB] > Get:5 http://deb.devuan.org/merged daedalus-backports InRelease [32.6 kB] > > Reading package lists... Done > > E: Release file for > http://pkg.bunsenlabs.org/debian/dists/beryllium/InRelease is not valid yet > (invalid for another 8674d 3h 45min 8s). Updates for this repository will > not be applied. > E: Release file for http://deb.devuan.org/merged/dists/daedalus/InRelease > is not valid yet (invalid for another 8744d 2h 14min 0s). Updates for this > repository will not be applied. > E: Release file for > http://deb.devuan.org/merged/dists/daedalus-updates/InRelease is not valid > yet (invalid for another 8744d 7h 58min 21s). Updates for this repository > will not be applied. > E: Release file for > http://deb.devuan.org/merged/dists/daedalus-security/InRelease is not valid > yet (invalid for another 8744d 4h 58min 7s). Updates for this repository > will not be applied. > E: Release file for > http://deb.devuan.org/merged/dists/daedalus-backports/InRelease is not > valid yet (invalid for another 8744d 7h 58min 11s). Updates for this > repository will not be applied. > Your real time clock isn't :( Set the date correctly using GNU date command or similar and work forward from there. > After a little experimenting it looks like to me that it is a Fastly error: > > Fastly error: unknown domain: 199.232.150.132. Please check that this > domain has been added to a service. > > Fastly is cdn for Debian. > -- This is irrelevant given your sources lists - you're not referencing Debian sources, potentially. > Mario. With every good wish, as ever, Andy (amaca...@debian.org)
