#1 2016-07-06 00:28:20

Sector11

Mod Squid Tpyo Knig

From: Upstairs

Registered: 2015-08-20

Posts: 8,028

Debian Security Upgrade

https://forums.bunsenlabs.org/viewtopic.php?id=2285

How?  update/dist-upgrade doesn't do it.

---

Debian 12 Beardog, SoxDog and still a Conky 1.9er

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,143

Website

Re: Debian Security Upgrade

I bet you already have it, post the output of apt-cache policy linux-image-3.16.0-4-586, linux-image-3.16.0-4-686-pae or linux-image-3.16.0-4-amd64, depending on which architecture you run.

---

I don't care what you do at home. Would you care to explain?

Sector11

Mod Squid Tpyo Knig

From: Upstairs

Registered: 2015-08-20

Posts: 8,028

Re: Debian Security Upgrade

 06 Jul 16 @ 00:19:24 ~
  $ cpol linux-image-3.16.0-4-amd64
alias cpol = apt-cache policy
linux-image-3.16.0-4-amd64:
  Installed: 3.16.7-ckt25-2+deb8u3
  Candidate: 3.16.7-ckt25-2+deb8u3
  Version table:
 *** 3.16.7-ckt25-2+deb8u3 0
        500 http://security.debian.org/ jessie/updates/main amd64 Packages
        100 /var/lib/dpkg/status
     3.16.7-ckt25-2 0
        500 http://ftp.us.debian.org/debian/ jessie/main amd64 Packages
        500 http://ftp.us.debian.org/debian/ jessie-updates/main amd64 Packages
 
 06 Jul 16 @ 00:20:26 ~
  $ 

Well hell, I saw linux-image-3.16.0 and thought that 0 meant I didn't have it.

  $ sys
System:    Host: bunsen Kernel: 3.16.0-4-amd64 x86_64 (64 bit) Desktop: Openbox 3.5.2
           Distro: BunsenLabs 8.5 bunsen-hydrogen

Thank you.

Why doesn't inxi or screenfetch see it as 3.16.7 ???
Just thinking (typing) out loud....

---

Debian 12 Beardog, SoxDog and still a Conky 1.9er

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,143

Website

Re: Debian Security Upgrade

Actually, I've never understood Debian's naming scheme for packages. I'm sure it's explained in the debian handbook, but maybe someone will explain it here.

-edit- I know that the package name is <foo> <version> <revision> <arch>.deb. I think I get it, the part in parenthesis is the revision number...
https://packages.debian.org/jessie/linu … .0-4-amd64

Your not installing a new kernel, just updating it, so the bulk of the file name stays the same. You can see though that the deb file has been renamed...

https://packages.debian.org/jessie/i386 … 4/download

http://security.debian.org/debian-secur … 3_i386.deb

I guess <foo> <version> <arch> <revision>.deb is more accurate. neofetch is correctly reporting which kernel version you are running.

-edit- My explanation is a bit off. neofetch is displaying the kernel-release name...

$ uname -r
3.16.0-4-amd64

The stuff in parenthesis is the security revision number, which is a part of the version number. Version (3), major revision (16), minor revision (7), and detail/fix revision (ckt25-2+deb8u3)...

$ uname -v
#1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02)

http://www.liquidweb.com/kb/how-to-chec … tu-centos/

---

I don't care what you do at home. Would you care to explain?