guidol Posted March 26, 2019 Posted March 26, 2019 https://lists.debian.org/debian-devel-announce/2019/03/msg00006.html Removal of Wheezy and Jessie (except LTS) from mirrors Quote To: d-d-a <debian-devel-announce@lists.debian.org> Subject: Removal of Wheezy and Jessie (except LTS) from mirrors From: Joerg Jaspert <joerg@debian.org> Date: Wed, 20 Mar 2019 21:50:35 +0100 Message-id: <[🔎] 87zhppi82s.fsf@debian.org> Mail-followup-to: d-d-a <debian-devel-announce@lists.debian.org> Hello, as Wheezy and Jessie have been integrated into the archive.debian.org structure recently, we are now removing all of Wheezy and all non-LTS architectures of Jessie from the mirror network starting today. That is, only Jessie i386, amd64, armel and armhf will continue to be hosted on the normal mirrors. The data is, of course, not lost - the whole of it is synced to archive.debian.org, so if you still need it you will be able to get it from there.[1] [1] Keep in mind that they have no security support at all! -- bye, Joerg The sun? That’s the hottest place on Earth.
lanefu Posted March 26, 2019 Posted March 26, 2019 Ya it was interesting the debian security team bailed on jessie for arm64 like last summer or something because of resources.
olivluca Posted March 29, 2019 Posted March 29, 2019 On 3/26/2019 at 4:54 PM, guidol said: [1] Keep in mind that they have no security support at all! -- I understand that, but at least they could have archived the latest security updates (or I'm just stupid and cannot find them.....for wheezy).
guidol Posted March 29, 2019 Author Posted March 29, 2019 26 minutes ago, olivluca said: I understand that, but at least they could have archived the latest security updates (or I'm just stupid and cannot find them.....for wheezy). let's try this url for wheezy security updates?: http://security.debian.org/debian-security/dists/wheezy/updates/http://security-cdn.debian.org/debian-security/dists/wheezy/updates/ and here main contrib and non-free? 1
olivluca Posted March 29, 2019 Posted March 29, 2019 Thank you, I knew it was me being stupid Edit doubly stupid: I commented that source myself from /etc/apt/sources.list when I saw the rest of the sources giving me 404
guidol Posted April 14, 2019 Author Posted April 14, 2019 I did play with OSMC / debian jessie on my old trusty Apple TV1 and there (when "new" installed) is also a old sources.list whcih didnt work. I did a short search and ended up with the follwing sources.list for the osmc / ATV1 from https://superuser.com/questions/1417617/apt-get-update-is-failing-in-debian orhttps://www.jesusamieiro.com/failed-to-fetch-http-ftp-debian-org-debian-dists-jessie-updates-main-404-not-found/ (where you could delete the osmc line for other jessie-systems): deb http://archive.debian.org/debian/ jessie main contrib non-free deb-src http://archive.debian.org/debian/ jessie main contrib non-free deb http://security.debian.org jessie/updates main contrib non-free deb-src http://security.debian.org jessie/updates main contrib non-free deb http://apt.osmc.tv jessie main
Christos Posted January 22, 2020 Posted January 22, 2020 Hi @guidol @Igor It has been a while since I did a build and did not notice this change. My environment relies on jessie thus I compile with this. sudo ./compile.sh SET_EXPERT=yes RELEASE=jessie When tried a build got these errors during compile Err http://httpredir.debian.org jessie-backports/main armhf Packages 404 Not Found [IP: ::1 3142] Err http://httpredir.debian.org jessie-backports/contrib armhf Packages 404 Not Found [IP: ::1 3142] Err http://apt.armbian.com jessie/main armhf Packages 404 Not Found [IP: ::1 3142] Err http://httpredir.debian.org jessie-backports/non-free armhf Packages 404 Not Found [IP: ::1 3142] Err http://apt.armbian.com jessie/jessie-utils armhf Packages 404 Not Found [IP: ::1 3142] Err http://apt.armbian.com jessie/jessie-desktop armhf Packages 404 Not Found [IP: ::1 3142] Fetched 10.1 MB in 8s (1187 kB/s) W: Failed to fetch http://apt.armbian.com/dists/jessie/main/binary-armhf/Packages 404 Not Found [IP: ::1 3142] W: Failed to fetch http://apt.armbian.com/dists/jessie/jessie-utils/binary-armhf/Packages 404 Not Found [IP: ::1 3142] W: Failed to fetch http://apt.armbian.com/dists/jessie/jessie-desktop/binary-armhf/Packages 404 Not Found [IP: ::1 3142] W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-backports/main/binary-armhf/Packages 404 Not Found [IP: ::1 3142] W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-backports/contrib/binary-armhf/Packages 404 Not Found [IP: ::1 3142] W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-backports/non-free/binary-armhf/Packages 404 Not Found [IP: ::1 3142] E: Some index files failed to download. They have been ignored, or old ones used instead. [ o.k. ] Upgrading base packages [ Armbian ] And after a while the compilation stopped with this Processing triggers for libc-bin (2.19-18+deb8u10) ... Processing triggers for ca-certificates (20141019+deb8u4) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d....done. [ o.k. ] Installing packages for [ Armbian ] Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package armbian-firmware E: Unable to locate package mmc-utils [ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:229 ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:62 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated Then I searched through the forum and seen this thread. Is there a way to reference the archived jessie when performing a build ? It seems that the build scripts use the previous place of jessie. Can someone change the build scripts and when they refer to jessie to automatically point/refer to the new place you puted them ? regards, Christos PS My build is OrangePiPC default/legacy 3.4.113, jessie, console/server.
Igor Posted January 22, 2020 Posted January 22, 2020 Jessie is gone. There is nothing I can do about this. If you need something based on 3.4.y, use Xenial builds and use BUILD_TAG="v19.08" ... but if things doesn't work, nobody will fix it.
Christos Posted January 22, 2020 Posted January 22, 2020 Hi @Igor Thanks for answering. The platform I use is OPiPC and I do indeed need the 3.4.113. Tried every possible combination, (with BUILD_TAG or without, server or desktop etc) of either debian or ubuntu with the default/legacy 3.4.113. It looks that all of them during build do stop with the exact same message Reading state information... E: Unable to locate package armbian-firmware E: Unable to locate package mmc-utils [ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:229 ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:62 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated Obviously that is something different than phasing out jessie. If I understand it correctly, Armbian can no longer be build with the default/legacy sunxi kernel for OrangePi H3 in any way ? so Armbian has abandoned the 3.4.113 ? Is that correct ?
Igor Posted January 22, 2020 Posted January 22, 2020 1 minute ago, Christos said: If I understand it correctly, Armbian can no longer be build with the default/legacy sunxi kernel for OrangePi H3 in any way ? We left last build sources which should be able to build that here: https://github.com/armbian/build/tree/v19.08 6 minutes ago, Christos said: so Armbian has abandoned the 3.4.113 We provide binaries and sources, while support costs are yours now.
Heisath Posted January 22, 2020 Posted January 22, 2020 Hey I just tested this myself, I did: git clone https://github.com/armbian/build cd build git checkout v19.08 sudo ./compile.sh EXPERT=yes LIB_TAG="v19.08" RELEASE=jessie Selected "Orange Pi PC", "Full image" and installation failed as you indicated: [ .... ] Fingerprinting [ o.k. ] Building package [ linux-jessie-root-orangepipc ] [ o.k. ] Building desktop package [ armbian-jessie-desktop_5.99_all ] [ o.k. ] Starting rootfs and image building process for [ orangepipc jessie ] [ o.k. ] Checking for local cache [ jessie-cli-armhf.fd2...6e9.tar.lz4 ] [ .... ] searching on servers [ o.k. ] ... remote not found [ Creating new rootfs cache for jessie ] [ o.k. ] Installing base system [ Stage 1/2 ] E: unrecognized or invalid option --components= [ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:147 ] [ error ] Debootstrap base system first stage failed [ o.k. ] Process terminated [ o.k. ] Unmounting [ /home/user/build/.tmp/rootfs-default-orangepipc-jessie-no-no/ ] [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:66 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated So yes there seems to be a problem creating the root fs for jessie. We will not fix this because it is out of support. If you look inside the output folder though, you can see that the 3.4.y kernel was successfully created & packaged. So maybe you can use some more current (working) build and go back from there. You can downgrade your kernel with the debs created. And you could also change your apt.lists (in a running more recent install) and downgrade your stretch or whatever to jessie. Alternatively have a look at the buildscript and try to fix the sources yourself or get the rootfs from somewhere else. Maybe Orange Pi vendor? Kind regards, count-doku
Christos Posted January 22, 2020 Posted January 22, 2020 Thank you @count-doku , @Igor It seems though that the problem here might be more than just jessie or 3.4.113. Please have a look at the logs posted above and on those following My Armbian build host is Ubuntu Bionic 18.04 (x64) Tried a few builds with the mainline kernel, Strech and Ubuntu, all of them gave error Armbian build for (AllWinner H3) OPiPC, Mainline kernel, Debian 9 Strech, Server/console, full os image Setting up libsasl2-modules-db:armhf (2.1.27~101-g0780600+dfsg-3+deb9u1) ... Setting up libsasl2-2:armhf (2.1.27~101-g0780600+dfsg-3+deb9u1) ... Setting up libssl1.0.2:armhf (1.0.2u-1~deb9u1) ... Processing triggers for libc-bin (2.24-11+deb9u4) ... Setting up libssl1.1:armhf (1.1.0l-1~deb9u1) ... Setting up openssl (1.1.0l-1~deb9u1) ... Processing triggers for libc-bin (2.24-11+deb9u4) ... [ o.k. ] Installing packages for [ Armbian ] Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package armbian-firmware [ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:229 ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:62 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated Armbian build for (AllWinner H3) OPiPC, Mainline kernel, Ubuntu Xenial 16.04 LTS, Server/console, full os image Setting up console-setup (1.108ubuntu15.5) ... update-initramfs: deferring update (trigger activated) Processing triggers for libc-bin (2.23-0ubuntu11) ... Processing triggers for systemd (229-4ubuntu21.23) ... Processing triggers for initramfs-tools (0.122ubuntu8.16) ... Processing triggers for resolvconf (1.78ubuntu7) ... Processing triggers for ca-certificates (20170717~16.04.2) ... Updating certificates in /etc/ssl/certs... 17 added, 42 removed; done. Running hooks in /etc/ca-certificates/update.d... done. [ o.k. ] Installing packages for [ Armbian ] Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package armbian-firmware [ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:229 ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:62 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated Armbian build for (AllWinner H3) OPiPC, Mainline kernel, Ubuntu Bionic 18.04 LTS, Desktop, full os image Setting up python3-gi (3.26.1-2ubuntu1) ... Setting up libgssapi-krb5-2:armhf (1.16-2ubuntu0.1) ... Setting up libavahi-client3:armhf (0.7-3.1ubuntu1.2) ... Setting up ubuntu-minimal (1.417.3) ... Setting up networkd-dispatcher (1.7-0ubuntu3.3) ... Installing new version of config file /etc/default/networkd-dispatcher ... Setting up libcups2:armhf (2.2.7-1ubuntu2.7) ... Processing triggers for initramfs-tools (0.130ubuntu3) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for systemd (237-3ubuntu10.33) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for mime-support (3.60ubuntu1) ... [ o.k. ] Installing packages for [ Armbian ] Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package armbian-firmware [ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:229 ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:62 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated It looks to me that the problem is generic to all builds, could it be related to this ? What happenned to those apps and their repo? E: Unable to locate package armbian-firmware E: Unable to locate package mmc-utils Anyway, as it is right now, it seems that I cannot build anything related to H3, legacy kernel or mainline, no H3 build succeeds. Did not test though any other CPU.. I do not know if I am missing something, I hope you can find a solution.
lanefu Posted January 23, 2020 Posted January 23, 2020 1 hour ago, Christos said: Armbian build for (AllWinner H3) OPiPC, Mainline kernel, Debian 9 Strech, Server/console, full os image That test was from latest checkout? Have you tried cleaning your cache folder?
Christos Posted January 23, 2020 Posted January 23, 2020 6 minutes ago, lanefu said: That test was from latest checkout? Have you tried cleaning your cache folder? It was from a checkout a few months back, in June, though from what I know and see, the build script perform any update required. Will do tomorrow a full clean new checkout and report back.
Christos Posted January 23, 2020 Posted January 23, 2020 Indeed after a fresh checkout things got better and now I can build ok the supported items in build system. The problem is that jessie build bails out with error, though as @Igor said, the 3.4.113 can still be compiled with xenial and the 19.08 branch (for as long as it does..) A minor but time consuming task is that whenever we have to make a new fresh checkout, it takes so many hours to re-download all the cached components specifically the toolchains and thats a real bummer. Thanks for your hints. 1
guidol Posted April 25, 2020 Author Posted April 25, 2020 as reminder here my latest /etc/apt/sources.list for wheezy (should work on old systems - I did try to update "the last time?" my Intel galileo Gen1 debian): # OLD: # deb http://ftp.us.debian.org/debian wheezy main contrib non-free # deb http://ftp.us.debian.org/debian wheezy-updates main contrib non-free # deb http://security.debian.org/ wheezy/updates main contrib non-free # NEW: deb http://archive.debian.org/debian wheezy main contrib non-free deb http://archive.debian.org/debian-archive/debian-security/ wheezy updates/main updates/contrib updates/non-free #even NEWER: deb http://archive.debian.org/debian wheezy-backports main contrib non-free deb http://archive.debian.org/debian wheezy-backports-sloppy main contrib non-free
Recommended Posts