Packages following Debian stable

[lgalex]

This is a more general question I have concerning packages like firefox-esr (that was, I think, coming from Debian stable and not from the Raspberry Pi foundation) that stopped being updated in Raspbian (even though it is still in Debian stable).

Are they going to be removed from the repo at some point? Maybe only on the next major release?
Is it something that's so rare that it's not really a problem (after all, Debian stable mostly gets stability/security updates)?

I (maybe incorrectly) assumed that if I apt-get install something that is available in the Raspbian repo, it would be updated and safe (the same version as Debian stable).

Thanks

[plugwash]

Generally we do follow debian stable, but sometimes things get snarled up. In this particular case local modifications were blocking the import of a new version of cargo from debian which was blocking the firefox build. I have just unblocked cargo so hopefully it and the new firefox will be built soon.

[lgalex]

Generally we do follow debian stable, but sometimes things get snarled up. In this particular case local modifications were blocking the import of a new version of cargo from debian which was blocking the firefox build. I have just unblocked cargo so hopefully it and the new firefox will be built soon.

ohh! I was simply curious to know how it works... but know it's even better, my firefox "problem" will be fixed

I also wonder if in cases like this it is simply a matter of time before someone looks at the logs and fix the problems or if it's useful to post it in the forum?

Thanks

[plugwash]

It's useful to post, i'm the main developer of raspbian but i'm often guilty of putting all my focus on testing and just expecting stable to sort itself out.

[lgalex]

It's useful to post, i'm the main developer of raspbian but i'm often guilty of putting all my focus on testing and just expecting stable to sort itself out.

Ok! that's understandable
Thanks

[plugwash]

Unfortunately I am seeing reports that the updated firefox from Debian stable doesn't actually work on arm, so for now I am having to put any updates to it on hold.

[fruitoftheloom]

Unfortunately I am seeing reports that the updated firefox from Debian stable doesn't actually work on arm, so for now I am having to put any updates to it on hold.

https://www.debian.org/security/2018/dsa-4287

In addition, the new Firefox packages require Rust to build. A compatible Rust toolchain has been backported to Debian stretch, but is not available for all architectures which previously supported the purely C++-based Firefox packages. Thus, the new Firefox packages don't support the armel, armhf, mips, mips64el and mipsel architectures at this point.

[lgalex]

Unfortunately I am seeing reports that the updated firefox from Debian stable doesn't actually work on arm, so for now I am having to put any updates to it on hold.

https://www.debian.org/security/2018/dsa-4287

In addition, the new Firefox packages require Rust to build. A compatible Rust toolchain has been backported to Debian stretch, but is not available for all architectures which previously supported the purely C++-based Firefox packages. Thus, the new Firefox packages don't support the armel, armhf, mips, mips64el and mipsel architectures at this point.

Oh... that's sad

Well, I guess I will have to wait a little longer to have a modern up-to-date browser on Raspbian (yes yes, Vivaldi, I know...)
Thanks anyway

[fruitoftheloom]

Unfortunately I am seeing reports that the updated firefox from Debian stable doesn't actually work on arm, so for now I am having to put any updates to it on hold.

https://www.debian.org/security/2018/dsa-4287

In addition, the new Firefox packages require Rust to build. A compatible Rust toolchain has been backported to Debian stretch, but is not available for all architectures which previously supported the purely C++-based Firefox packages. Thus, the new Firefox packages don't support the armel, armhf, mips, mips64el and mipsel architectures at this point.

Oh... that's sad

Well, I guess I will have to wait a little longer to have a modern up-to-date browser on Raspbian (yes yes, Vivaldi, I know...)
Thanks anyway

I disagree with "sad", chromium-browser v65 fulfills the purpose of running Flash based Scratch2 on the RPi2 & 3, anything else is a bonus.


kweb can fulfill the roll of watching YT and many other sites etc...


When want to undertake multiple-tab browsing either use my Asus ChromeBit or SmartPhone, the RPi SBC is good but not a "desktop pc" replacement !!

[lgalex]

I disagree with "sad", chromium-browser v65 fulfills the purpose of running Flash based Scratch2 on the RPi2 & 3, anything else is a bonus.

kweb can fulfill the roll of watching YT and many other sites etc...

When want to undertake multiple-tab browsing either use my Asus ChromeBit or SmartPhone, the RPi SBC is good but not a "desktop pc" replacement !!

Yeah, I know that the main purpose of chrome is to run flash for Scratch, but a part of me still doesn't like the idea of a 6 month old browser by default. But I don't really care about flash or scratch either and I understand why things are like this for now.

[lgalex]

It seems that the firefox-esr package (and the backported rust) are now available in Debian stable for arm. Is there any chances of it being available in Raspbian soon?

Thanks

[plugwash]

Does the package from Debian stable armhf actually work?

[lgalex]

Does the package from Debian stable armhf actually work?

Well That's actually a good question that I can't really test unfortunately. I just saw it was available and thought that it was working. I know that the rust package wasn't available on arm according to the Debian website before, and now it is (so... I assume it's working now... why changing the status if nothing changed).

I assumed (maybe incorrectly) that it was the same for firefox, and that if it's available, it should be working. But maybe it's not.

[plugwash]

https://bugs.debian.org/cgi-bin/bugrepo ... bug=906570

[lgalex]

https://bugs.debian.org/cgi-bin/bugrepo ... bug=906570

Ok well, I guess it probably won't be available for a while then

Sorry if I used your time for nothing, I should have done a better search

Thanks

[lgalex]

Now that the new version on Raspbian based on Buster is available, I have another question about the packages versions.

I see that the version of Firefox available in the Raspbian buster repo is 60.7.0esr-1+rpi1 and the version from Debian is 60.7.2esr-1.

I don't really understand why the version is still a few months behind (60.7.0 was released in May, 6.7.2 in June), but I assume that there is something going on that's specific to Raspbian (rpi1 in the version number).

I guess I simply want to know if my assumptions are right.. and if so, why
I can't really find any informations on subject like I would with a Debian package with changelogs and status pages.

Thanks

[plugwash]

There is an issue with the firefox build scripts where they make incorrect assumptions about rust architectures and hence fail to build on raspbian. I have a patch that works around the issue but that means that updates to the package have to go through the autoforwardporter which is only semi-automated.

http://debdiffs.raspbian.org/main/f/fir ... i1.debdiff

I've just kicked off the autoforwardporter, hopefully it should spit out some new firefox packages soon.

[lgalex]

There is an issue with the firefox build scripts where they make incorrect assumptions about rust architectures and hence fail to build on raspbian. I have a patch that works around the issue but that means that updates to the package have to go through the autoforwardporter which is only semi-automated.

http://debdiffs.raspbian.org/main/f/fir ... i1.debdiff

I've just kicked off the autoforwardporter, hopefully it should spit out some new firefox packages soon.

I think I understand
Thanks