Re: Q: what's the blocker for firefox-esr update migrates to testing
Am 01.11.19 um 14:55 schrieb Aron Xu: I'm not implying to remove it altogether, but it could be moved it to debian-ports, even RPi4 is alreay aarch64 capable. This is not the question (of course arm64 != armel) and I don't see why a still well maintained and working architecture should move to ports. I'm really happy that even my 10+ years old armv5 based hardware is still supported by Debian, otherwise I had a lot of electronic waste. The main problem with armel was the support by buildd infrastructure but this is thanks to the effort made by Steve this is no actual problem anymore. -- Regards Carsten Schoenert
Re: Q: what's the blocker for firefox-esr update migrates to testing
On Fri, Nov 1, 2019 at 1:59 AM Carsten Schoenert wrote: > > Am 31.10.19 um 16:28 schrieb Aron Xu: > > This could be a reminder that we should start thinking about whether > > we want to keep armel as a release architecture for bullseye. > > No, but some X-based applications might simply get excluded from the > that architecture. There are still a lot armv5 based hardware outside > which is simply working fine with recent Debian releases. I see no real > reason to make all this hardware obsolete simply because some software > which requires some X features isn't build-able on armel. > I'm not implying to remove it altogether, but it could be moved it to debian-ports, even RPi4 is alreay aarch64 capable. Cheers, Aron -- Regards, Aron Xu
Re: Q: what's the blocker for firefox-esr update migrates to testing
Am 31.10.19 um 16:28 schrieb Aron Xu: This could be a reminder that we should start thinking about whether we want to keep armel as a release architecture for bullseye. No, but some X-based applications might simply get excluded from the that architecture. There are still a lot armv5 based hardware outside which is simply working fine with recent Debian releases. I see no real reason to make all this hardware obsolete simply because some software which requires some X features isn't build-able on armel. -- Regards Carsten Schoenert
Re: Q: what's the blocker for firefox-esr update migrates to testing
On Thu, Oct 31, 2019 at 11:09 PM Boyuan Yang wrote: > > According to https://qa.debian.org/excuses.php?package=firefox-esr , firefox- > esr build-depends on nodejs, which is not available on armel anymore > (explicitly not built on armel). Since armel is an release architecture, > firefox-esr won't migrate to Testing when its armel build is missing. > This could be a reminder that we should start thinking about whether we want to keep armel as a release architecture for bullseye. Cheers, Aron
Re: Q: what's the blocker for firefox-esr update migrates to testing
FYI: https://bugs.debian.org/818552#15 P. On 31/10/19 16:08, Boyuan Yang wrote: > According to https://qa.debian.org/excuses.php?package=firefox-esr , firefox- > esr build-depends on nodejs, which is not available on armel anymore > (explicitly not built on armel). Since armel is an release architecture, > firefox-esr won't migrate to Testing when its armel build is missing. > > The excuses page also shows some missing new versions of rust packages not > migrated yet but I assume it a temporary issue. > > These are not good signs, especially when both firefox-esr and chromium in > Testing are notably outdated.
Re: Q: what's the blocker for firefox-esr update migrates to testing
According to https://qa.debian.org/excuses.php?package=firefox-esr , firefox- esr build-depends on nodejs, which is not available on armel anymore (explicitly not built on armel). Since armel is an release architecture, firefox-esr won't migrate to Testing when its armel build is missing. The excuses page also shows some missing new versions of rust packages not migrated yet but I assume it a temporary issue. These are not good signs, especially when both firefox-esr and chromium in Testing are notably outdated. -- Regards, Boyuan Yang 在 2019-10-31四的 23:25 +0900，Hideki Yamane写道： > Hi, > > firefox-esr package doesn't migrate to testing but I cannot > find the reason at https://qa.debian.org/excuses.php?package=firefox-esr > > Could someone tell me why, please? signature.asc Description: This is a digitally signed message part
Re: Q: what's the blocker for firefox-esr update migrates to testing
On 2019-10-31 at 10:25, Hideki Yamane wrote: > Hi, > > firefox-esr package doesn't migrate to testing but I cannot > find the reason at https://qa.debian.org/excuses.php?package=firefox-esr > > Could someone tell me why, please? Quoted from that page: >> Issues preventing migration: >> firefox-esr unsatisfiable Build-Depends(-Arch) on armel: nodejs (>= 8.11) >> missing build on armel That seems clear enough to me, although I haven't looked into the reasons why that dependency can't currently be satisfied on that architecture. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
