raspbian-stable-main package repository very dated

[gwlester]

A lot of the packages in the raspbian-stable-main package repository are very dated. For example, the fossil SCM package is back at 1.1, the current version is 2.3 (the 2.x series is over a year old). Another example is Tcl, the repository has 8.6.6 which is from the summer of 2016, the current version is 2.6.8 (from 12/2017, but 2.6.7 was released in 08/2017).

Any idea how we can get more up to date packages into the raspbian-stable-main package repository?

[jamesh]

Raspbian stable is exactly that - stable. It follows the LTS Debian releases, currently Stretch, which can be some way behind the latest versions of packages, but very well tested, and stable.

If you want more recent packages, you need to download them and build yourself. Which is usually not too difficult a job.

[n67]

The short answer is: You can't. This is the way Debian is.

The longer answer is: The only way to get newer/better stuff is to compile it yourself.

BTW, are you sure about your version numbers for Tcl? It looks like you switched between 8.something.something to 2.something.something - with the 2.x.x being newer/later.

I though only MS did that sort of thing... (Windows 10 being later than Windows 98)

[sparkie777]

I don't understand why people often complain about debian being outdated. The opposite is true.

Ever heard about 'testing', 'unstable' or even 'experimental' debian repositories?

DebianTesting - Debian Wiki
DebianUnstable - Debian Wiki
DebianExperimental - Debian Wiki

For those who want bleeding edge packages simply use:

/etc/apt/sources.list:

Code: Select all

deb https://deb.debian.org/debian/ unstable main contrib non-free
deb-src https://deb.debian.org/debian/ unstable main contrib non-free

those requiring even daily snap shots (and feeling incapable compiling their own stuff) add the 'experimental' repositories.

Of course in that case you must get your kernel via 'rpi-update' to your machine. Since debian does not (yet) provide a specific raspberry-kernel in their own repositories.

Nothing comes from nothing.

[DougieLawson]

If you don't like DebIan's exceedingly conservative view of packages (not in testing or Sid) then your best choice is to switch to Arch or Ubuntu or Mint.

[klricks]

The Debian release cycle is about every 2 years. https://www.debian.org/releases/
There are more than 55,000 packages in the repository. There are about 1800 packages installed on the RPi. The RPF only touches a hand-full of those which are RPi specific. Everything else is pulled from Debian as is with no modifications.

[rpdom]

Of course in that case you must get your kernel via 'rpi-update' to your machine. Since debian does not (yet) provide a specific raspberry-kernel in their own repositories.

The simple answer to that is to leave the raspberrypi.org stretch repositories in your sources.list.d directory. You can even leave the raspbian repos in there and priority will be given to the newer Debian versions of anything non-raspberry pi specific.

[sparkie777]

The simple answer to that is to leave the raspberrypi.org stretch repositories in your sources.list.d directory.

wow, even better. Debian is simply configurable to any degree of up-to-dateness. Obviously some people don't know that but complain instead:-) There is nothing more to say.

[jonesypeter]

Related to to above comments is it OK just to add the Debian repository to the end of the current sources.list file rather than create a sources.list.d directory.

Also when I add the debian repository I get a message when I try and update that the repository is un-signed. I can proceed by pressing 'y', but is there a way to approve it permanently?

Finally, by keeping the raspian repositories in my sources.list will this guarantee that I still get the Raspberry Pi specific kernels etc?

Thanks

[bluenote]

Related to to above comments is it OK just to add the Debian repository to the end of the current sources.list file rather than create a sources.list.d directory.

Also when I add the debian repository I get a message when I try and update that the repository is un-signed. I can proceed by pressing 'y', but is there a way to approve it permanently?

Finally, by keeping the raspian repositories in my sources.list will this guarantee that I still get the Raspberry Pi specific kernels etc?

Thanks

I would also appreciate just a bit more expert advice on how to do this. I really only want to be able to pull newer versions for certain things. Like today I wanted to install firefox - but the debian, or rpi version is 7 versions behind. Arch is 1 behind for comparison. But maybe there's a newer version available in the newer debian repos. Thanks for any advice.

[binaryhermit]

It wouldn't surprise me if mixing debian and raspbian packages ended poorly.

[rpdom]

It wouldn't surprise me if mixing debian and raspbian packages ended poorly.

It's not that much of an issue with the Pi 2 or later. I've got a Pi 3B+ that was set up as Raspbian Stretch Lite, upgraded to Raspbian Buster and has a few packages from Debian Sid on it (it is not recommended to use Sid as things will break from time to time).

However, it is probably best to stick to Raspbian if you are likely to want any support from Raspberry Pi engineers on here.