PHP 7 on archive.raspbian.org but not in apt?

[DanTup]

I'm a linux noob so not familiar with how these things work, but I noticed there are PHP7 files here:

https://archive.raspbian.org/raspbian/p ... /p/php7.0/

Yet if I do

Code: Select all

sudo apt list | grep php7

there are 0 results.

What's the reason for this? If there are files on that server, why wouldn't they show in apt lists?

[plugwash]

The pool contains deb files for all releases of raspbian. php7.0 is in stretch but not in jessie.

[DanTup]

Aha, that makes sense!

Is there a way to browse these to see what packages are where (eg. like packages.debian.org)?

[fruitoftheloom]

Aha, that makes sense!

Is there a way to browse these to see what packages are where (eg. like packages.debian.org)?

https://packages.debian.org/stretch/php7.0

[DanTup]

I meant for Rasbpian - or are they the same?

[rpdom]

I meant for Rasbpian - or are they the same?

They are the same.

[plugwash]

We don't run an equivilent of packages.debian.org

For the most part things are similar enough between debian armhf and raspbian that you can look stuff up on packages.debian.org and more than likely it will be correct for raspbian too.

[peterlite]

For PHP 7, I added the Stretch repositories and gave the new repositories a lower priority so that packages are always selected from Jessie. When you install or request info PHP 7, it is only in the lower priority Stretch repository. You get the right info from Stretch.

When you request a package that is in both Stretch and Jessie, you can specify stretch or jessie in the command line to get the test version from Stretch or the stable one from Jessie.

[ghans]

Don't try this on a Zero or a Pi1 , folks - it won't work and
might break your system too.


ghans

[peterlite]

@ghans, don't try what? What breaks?

I am about to set up this type of configuration on a Zero and would like to know what happens.

I can understand problems with something smaller than the Pi Zero. NAS devices use processors and memory about equivalent to a Pi Zero. The NAS devices have PHP 5 based interfaces that work. PHP 7 uses less processor and less memory. PHP 7 should work on a Zero.

Many of the articles on PHP 7 suggest some weird repositories that supply more than PHP 7, they replace a random assortment of Jessie packages with Stretch packages. If you use the selective approach, you should get only PHP 7 from Stretch. I will be testing the selective approach on a Zero when my Zero arrives in the mail.

[ghans]

Debian "armhf" targets ARMv7 , Raspbian "armhf" targets
ARMv6 . The Zero and the Pi1 are ARMv6 processors.
ARMv7 processors can run ARMv6 code (backwards
compability) , but ARMv6 processors can't run ARMv7 code.

You are likely to get "Illegal Instruction" errors all over the place.
If you you aren't vigilant , you might even accidentally replace
your libc-bin package with the one from Debian (this has
happened to people in the past) and then you're truly
done for , since nearly everything on the system
uses the libc and now fails with "Illegal Instruction"
errors.


ghans

[plugwash]

Debian "armhf" targets ARMv7 , Raspbian "armhf" targets
ARMv6 . The Zero and the Pi1 are ARMv6 processors.
ARMv7 processors can run ARMv6 code (backwards
compability) , but ARMv6 processors can't run ARMv7 code.

You are likely to get "Illegal Instruction" errors all over the place.
If you you aren't vigilant , you might even accidentally replace
your libc-bin package with the one from Debian (this has
happened to people in the past) and then you're truly
done for , since nearly everything on the system
uses the libc and now fails with "Illegal Instruction"
errors.

Thats why you add raspbian stretch, not debian stretch duh

(of course you have all the usual risks of mixing releases, if it breaks you keep the peices)

[ghans]

Must've missed that Raspbian stretch exists - that
makes more sense.

ghans

[peterlite]

Interesting note about the differences between the Pi 3 and Zero, the ARMv6 and ARMv7 stuff. The Pi 3 is 64 bit but none of the Raspbian software can be 64 bit because of the other Pi models. 64 bit is only needed when you jump from 4 GB to 8 GB. I have one 16 GB computer and, running Linux, it rarely uses more than 1.6 GB. 8 GB is only needed for KDE.

[fruitoftheloom]

Interesting note about the differences between the Pi 3 and Zero, the ARMv6 and ARMv7 stuff. The Pi 3 is 64 bit but none of the Raspbian software can be 64 bit because of the other Pi models. 64 bit is only needed when you jump from 4 GB to 8 GB. I have one 16 GB computer and, running Linux, it rarely uses more than 1.6 GB. 8 GB is only needed for KDE.

Your analogy of memory requirements is totally screwed. I have a x86-64 PC with 1GB Men which runs x86-64 Lubuntu.

There are tinkerers who post in this forum who run Aarch64 Debian on the RPi 3B.

The reason that Raspbian is not Aarm64 is backward compatibilty, so RPF do not have to maintain 2 OSes...

.

[peterlite]

@ fruitoftheloom In what way is my post

totally screwed

? The Raspberry Pi 3 announcement said the 64 bit processor was for future development of 64 bit and Raspbian would remain 32 bit for a few years for compatibility with the other models.

Modern software gets more speed from using the graphics processor, with 512 bits or more, than from converting to 64 bit. The other use of 64 bit is virtual memory, something that would kill performance on a Pi with a microSD card. I expect the Pi will move to 64 bit mainly to simplify Broadcom's processor chip range.