It seems my problem has been a temporary one.
Some weeks after posting my original question, the settings just started working. I did not actually do anything. I guess "stretch" was not really ready to be supported then under Raspbian, but now it is.
Currently, I have only the following effective lines in my sources.list, and they work fine now:
$ grep ^[[...
First of all update your Raspbian operating system version to get newer packages.
The general answer is no, unless you know exactly what are you doing.
Apparently there are different types of packages: Debian armel and Debian armhf. The formers are not compatible. The latters should be compatible but there might be differences in compilation or mixed ...
Raspbian is based on Debian and its repositories share the same code names. Basically:
wheezy and wheezy-staging are Debian 7 (code name Wheezy)
jessie and jessie-staging are Debian 8 (code name Jessie)
stretch and stretch-staging are repositories for Debian 9 (code name Stretch)
Repositories for officially released versions contain latest stable release. ...
You'll need to wait for Bullseye to emerge as the stable version.
RaspiOS is based on DebIan. The current RaspiOS version is Buster. The next (in autumn 2021) will be RaspiOS Bullseye (the DebIan versions are named after Toy Story characters). You won't get a python version change except on a DebIan version change - because that's how DebIan likes to do it ...
Raspbian is the project which recompiles the Debian archive for the Pi architecture. Debian is one of the principal Linux distributions.
raspberrypi.org is the charity and holds packages specifically created for the Pi and which are not part of Raspbian/Debian.
This is a futile endeavour. The System requirements for Document Server include:
CPU: dual core 2 GHz or better → while Raspberry Pi 2 & 3 have quad-core processors, they're ~ 1 GHz ARM quad core. Server spec software usually assumes Intel power per core
RAM: 2 GB or more → the most RAM that a Raspberry Pi supports is 1 GB
OS: 64-bit Debian, Ubuntu or ...
A Debian repository is mainly made for a specific distribution and even for a specific version of it. For Raspbian/Debian you will find different repositories e.g. for version Jessie (or old-old-stable), Stretch (or old-stable) , Buster (or stable) and so on. The packages in the repository are pre compiled for the version and the installable executable ...
I have tested it with a fresh flashed Raspbian Buster Light on a RPi 4B:
$ sudo apt-get install bind9 bind9utils dnsutils
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
dns-root-data libirs161 python3-ply
bind9-doc ufw rblcheck python-ply-...
They have the new "Stretch" version out now. You can find it here
That Q&A contains all the upgrade instructions.
To upgrade, first modify the files /etc/apt/sources.list and /etc/apt/sources.list.d/raspi.list. In both files, change every occurrence of the word ‘jessie’ to ‘stretch’. (Both files will require sudo to edit.)
To answer your question, ...
The latest version upstream from Rasbian 8 -- "upstream" being Debian, not the owncloud direct releases -- is 7.0.4. I don't know if that is the client, the server, or both.
I'm not an Owncloud user but it looks at first glance to be pure PHP, meaning you don't need to dig around for a version compiled for ARM. I could easily be wrong about that though. ...
As mentioned here the solution I found to building the 4.14.85 kernel was to simply clone the Raspberry Pi Linux repository with
git clone --depth=1 --branch rpi-4.14.y https://github.com/raspberrypi/linux
and then apply the incremental kernel patches in reverse, until reaching the 85-86 patch.
patch -R -p1 < ../patches-linux/patch-4.14.85-86
Go to https://GitHub.com/hexxeh/rpi-firmware and look at the commits.
The last commit @ 4.14.85 is eefe4b161f5e9730183c8dc1605e14c85b15cf51
So that gives you a commit id to use with the rpi-update script.
Run PRUNE_MODULES=1 rpi-update eefe4b161f5e9730183c8dc1605e14c85b15cf51 && reboot and you'll be back on the kernel from Dec 5, 2018.
I won't ...
An easier way to achieve this is to use git log --follow Makefile and from there scroll until you find the version you desire.
The only way I managed to find the commit was by manually scrolling through branch rpi-4.14.y's commits until I got the correct one. The Makefile indicates the commit's version, patch level, and sublevel. With ...
It works by generating signal on the GPIO4. You need to connect piece of wire to the pin and it works only in close proximity of few inches. It is for educational, testing purpose rather than for real applications.
If the drivers are only available on ubuntu your only option would be to try compiling the drivers from source. Download the tar.gz file and try to compile it. It won't be very simple but it's worth a shot. A few links.
This is what it was for according to their website at https://www.collabora.com/about-us/our-work.html
They might have provided a browser or driver's according to my quick read
They created the desktop environment after a tiny bit more reading of their webpage
There is a tool called katoolin. You can use that software. The script is written in python. Just opne the software from terminal with
sudo python katoolin.py
and you will find options for everything
Wheezy ("Old-Stable") is no longer the current distribution of Raspbian (and Debian from which it is derived) but not being familiar with Kali I am not sure from what it derives it's parentage - what do they say you should have in your sources.list currently - beware of using old documentation...!
Mixing repository sources is not a good idea unless a ...
The Raspberry Pi pulls from Debian repos and the Foundation's custom repo which holds RPi specific software. A tutorial on setting up an entire Debian mirror (same instructions should work for the RPi repo) is way outside the scope of this site. I would suggest you look at Debian's documentation on how to setup a repo mirror.
It's worth noting that the ...
As per this link here,
Chromium in Jessie will only install on the ARMv7 RPi 2B model as
above link ;)
If you have the ARMv6 RPi 1 models your only option is to install
Raspbian Wheezy which has an ancient Chromium version 22 in the
Looks like either you will have to downgrade to wheezy or use Rpi 2.
I'm guessing because in the answer to that other question, Octopus was working as root. You need privileges to edit sources.list, and this kind of thing:
sudo echo "whatever" >> /only/root/can/write/file
Won't work because of the >> redirection. The echo runs sudo, but the redirection is done by your shell, which does not. To get around this,...