SymStretch adding stable-updates (?)


#1

If I’m stable but impatient and want, say, the latest version of clamd, in part to avoid incessant shouty messages telling me not to panic :wink:

Fri Aug 24 11:15:00 2018 -> WARNING: Your ClamAV installation is OUTDATED!
Fri Aug 24 11:15:00 2018 -> WARNING: Local version: 0.100.0 Recommended version: 0.100.1
Fri Aug 24 11:15:00 2018 -> DON’T PANIC! Read https://www.clamav.net/documents/upgrading-clamav

… presumably stable-updates will work via /etc/apt/sources.list with something like this…

deb     http://httpredir.debian.org/debian stretch-updates main
deb-src http://httpredir.debian.org/debian stretch-updates main

But, what if I’m really impatient – can https://mirror.bytemark.co.uk/debian/dists/stretch-updates/ be used? Is it simply a case of…

deb     https://mirror.bytemark.co.uk/debian/dists stretch-updates main
deb-src https://mirror.bytemark.co.uk/debian/dists stretch-updates main

… or is there a better course?


#2

stretch-updates and stretch-updates are the same mirror, it doesn’t really matter if you download them from the httprdir mirror or mirror.bytemark.co.uk.

The bytemark link would be

deb     https://mirror.bytemark.co.uk/debian stretch-updates main

stretch-updates will probably cause you less excitement than dot-deb or backports, but I’ve personally used backports with symbiosis before without issue


#3

Great, thanks. I went with http:// (not https:):…

deb http://mirror.bytemark.co.uk/debian stretch-updates main

because…

E: The method driver /usr/lib/apt/methods/https could not be found.
N: Is the package apt-transport-https installed?

And then:

Fri Aug 24 12:15:00 2018 -> --------------------------------------
Fri Aug 24 12:50:50 2018 -> Update process terminated
Fri Aug 24 12:50:54 2018 -> --------------------------------------
Fri Aug 24 12:50:54 2018 -> freshclam daemon 0.100.1 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64)
Fri Aug 24 12:50:54 2018 -> ClamAV update process started at Fri Aug 24 12:50:54 2018
Fri Aug 24 12:50:54 2018 -> main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
Fri Aug 24 12:50:54 2018 -> daily.cld is up to date (version: 24868, sigs: 2060944, f-level: 63, builder: neo)
Fri Aug 24 12:50:54 2018 -> bytecode.cld is up to date (version: 327, sigs: 91, f-level: 63, builder: neo)
Fri Aug 24 12:50:54 2018 -> --------------------------------------

:slight_smile:


#4

apt currently doesn’t support https out of the box - installing apt-transport-https would fix that if you preferred to use https.

In reality it doesn’t make much different - it’s the signature checking of the package that should prove it’s authenticity rather than if it was downloaded over https or not.


#5

I’ll stick with http for now, thanks. Despite all appearances to the contrary I like vanilla. :wink: