Debian 8.3 released

Head_on_a_Stick · 2016-01-24 01:58:51

https://www.debian.org/News/2016/20160123

To update your system use:

sudo apt update
sudo apt upgrade

If `apt` says there are still packages left un-upgraded after the second command you may have to use:

sudo apt full-upgrade

Sector11 · 2016-01-24 02:18:51

Hmmmm "sudo apt update" is going slow ... there must be a bunch ...
and here's why:

  $ apt list --upgradable
Listing... Done
apt/stable 1.0.9.8.2 amd64 [upgradable from: 1.0.9.8.1]
apt-utils/stable 1.0.9.8.2 amd64 [upgradable from: 1.0.9.8.1]
base-files/stable 8+deb8u3 amd64 [upgradable from: 8+deb8u2]
bunsen-docs/unknown 8.0.2-1 all [upgradable from: 8.0-1]
bunsen-pipemenus/unknown 8.7.2-1 all [upgradable from: 8.7.1-1]
ca-certificates/stable 20141019+deb8u1 all [upgradable from: 20141019]
claws-mail/stable 3.11.1-3+deb8u1 amd64 [upgradable from: 3.11.1-3]
claws-mail-doc/stable 3.11.1-3+deb8u1 all [upgradable from: 3.11.1-3]
exim4/stable 4.84-8+deb8u2 all [upgradable from: 4.84-8]
exim4-base/stable 4.84-8+deb8u2 amd64 [upgradable from: 4.84-8]
exim4-config/stable 4.84-8+deb8u2 all [upgradable from: 4.84-8]
exim4-daemon-light/stable 4.84-8+deb8u2 amd64 [upgradable from: 4.84-8]
file/stable 1:5.22+15-2+deb8u1 amd64 [upgradable from: 1:5.22+15-2]
intel-microcode/stable 3.20151106.1~deb8u1 amd64 [upgradable from: 3.20150121.1]
libapt-inst1.5/stable 1.0.9.8.2 amd64 [upgradable from: 1.0.9.8.1]
libapt-pkg4.12/stable 1.0.9.8.2 amd64 [upgradable from: 1.0.9.8.1]
libc-bin/stable 2.19-18+deb8u2 amd64 [upgradable from: 2.19-18+deb8u1]
libc-dev-bin/stable 2.19-18+deb8u2 amd64 [upgradable from: 2.19-18+deb8u1]
libc6/stable 2.19-18+deb8u2 amd64 [upgradable from: 2.19-18+deb8u1]
libc6-dbg/stable 2.19-18+deb8u2 amd64 [upgradable from: 2.19-18+deb8u1]
libc6-dev/stable 2.19-18+deb8u2 amd64 [upgradable from: 2.19-18+deb8u1]
libc6-i386/stable 2.19-18+deb8u2 amd64 [upgradable from: 2.19-18+deb8u1]
libgudev-1.0-0/stable 215-17+deb8u3 amd64 [upgradable from: 215-17+deb8u2]
libjavascriptcoregtk-1.0-0/stable 2.4.9-1~deb8u1 amd64 [upgradable from: 2.4.8-2]
libjavascriptcoregtk-3.0-0/stable 2.4.9-1~deb8u1 amd64 [upgradable from: 2.4.8-2]
libldap-2.4-2/stable 2.4.40+dfsg-1+deb8u2 amd64 [upgradable from: 2.4.40+dfsg-1+deb8u1]
libmagic1/stable 1:5.22+15-2+deb8u1 amd64 [upgradable from: 1:5.22+15-2]
libpam-modules/stable 1.1.8-3.1+deb8u1 amd64 [upgradable from: 1.1.8-3.1]
libpam-modules-bin/stable 1.1.8-3.1+deb8u1 amd64 [upgradable from: 1.1.8-3.1]
libpam-runtime/stable 1.1.8-3.1+deb8u1 all [upgradable from: 1.1.8-3.1]
libpam-systemd/stable 215-17+deb8u3 amd64 [upgradable from: 215-17+deb8u2]
libpam0g/stable 1.1.8-3.1+deb8u1 amd64 [upgradable from: 1.1.8-3.1]
libpcre3/stable 2:8.35-3.3+deb8u2 amd64 [upgradable from: 2:8.35-3.3]
libpcre3-dev/stable 2:8.35-3.3+deb8u2 amd64 [upgradable from: 2:8.35-3.3]
libpcrecpp0/stable 2:8.35-3.3+deb8u2 amd64 [upgradable from: 2:8.35-3.3]
libperl5.20/stable 5.20.2-3+deb8u3 amd64 [upgradable from: 5.20.2-3+deb8u2]
libsystemd0/stable 215-17+deb8u3 amd64 [upgradable from: 215-17+deb8u2]
libudev1/stable 215-17+deb8u3 amd64 [upgradable from: 215-17+deb8u2]
libwebkitgtk-1.0-0/stable 2.4.9-1~deb8u1 amd64 [upgradable from: 2.4.8-2]
libwebkitgtk-1.0-common/stable 2.4.9-1~deb8u1 all [upgradable from: 2.4.8-2]
libwebkitgtk-3.0-0/stable 2.4.9-1~deb8u1 amd64 [upgradable from: 2.4.8-2]
libwebkitgtk-3.0-common/stable 2.4.9-1~deb8u1 all [upgradable from: 2.4.8-2]
linux-kbuild-3.16/stable 3.16.7-ckt20-1 amd64 [upgradable from: 3.16-3]
locales/stable 2.19-18+deb8u2 all [upgradable from: 2.19-18+deb8u1]
login/stable 1:4.2-3+deb8u1 amd64 [upgradable from: 1:4.2-3]
multiarch-support/stable 2.19-18+deb8u2 amd64 [upgradable from: 2.19-18+deb8u1]
passwd/stable 1:4.2-3+deb8u1 amd64 [upgradable from: 1:4.2-3]
perl/stable 5.20.2-3+deb8u3 amd64 [upgradable from: 5.20.2-3+deb8u2]
perl-base/stable 5.20.2-3+deb8u3 amd64 [upgradable from: 5.20.2-3+deb8u2]
perl-modules/stable 5.20.2-3+deb8u3 all [upgradable from: 5.20.2-3+deb8u2]
rsyslog/stable 8.4.2-1+deb8u2 amd64 [upgradable from: 8.4.2-1+deb8u1]
systemd/stable 215-17+deb8u3 amd64 [upgradable from: 215-17+deb8u2]
systemd-sysv/stable 215-17+deb8u3 amd64 [upgradable from: 215-17+deb8u2]
udev/stable 215-17+deb8u3 amd64 [upgradable from: 215-17+deb8u2]
 
 23 Jan 16 @ 23:12:47 ~
  $

working:

 23 Jan 16 @ 23:12:47 ~
  $ sudo apt upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  inotify-tools libinotifytools0
The following packages will be upgraded:
  apt apt-utils base-files bunsen-docs bunsen-pipemenus ca-certificates claws-mail claws-mail-doc exim4
  exim4-base exim4-config exim4-daemon-light file intel-microcode libapt-inst1.5 libapt-pkg4.12 libc-bin
  libc-dev-bin libc6 libc6-dbg libc6-dev libc6-i386 libgudev-1.0-0 libjavascriptcoregtk-1.0-0
  libjavascriptcoregtk-3.0-0 libldap-2.4-2 libmagic1 libpam-modules libpam-modules-bin libpam-runtime
  libpam-systemd libpam0g libpcre3 libpcre3-dev libpcrecpp0 libperl5.20 libsystemd0 libudev1
  libwebkitgtk-1.0-0 libwebkitgtk-1.0-common libwebkitgtk-3.0-0 libwebkitgtk-3.0-common linux-kbuild-3.16
  locales login multiarch-support passwd perl perl-base perl-modules rsyslog systemd systemd-sysv udev
54 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 62.5 MB of archives.
After this operation, 3,154 kB disk space will be freed.

... looking good ...

Done ... and good.

I think.

Head_on_a_Stick · 2016-01-24 02:22:25

^ That's interesting -- the new kernel version didn't require a `full-upgrade` to go through.

Good to know 8)

Sector11 · 2016-01-24 02:25:11

We can move this later if there is a bettr place for it.

While updating/upgrading to Debian 8.3 I see this:

Setting up intel-microcode (3.20151106.1~deb8u1) ...
update-initramfs: deferring update (trigger activated)
intel-microcode: microcode will be updated at next boot
Processing triggers for libc-bin (2.19-18+deb8u2) ...
Processing triggers for ca-certificates (20141019+deb8u1) ...
Updating certificates in /etc/ssl/certs... 19 added, 18 removed; done.
Running hooks in /etc/ca-certificates/update.d....
Adding debian:CA_WoSign_ECC_Root.pem
Adding debian:Certification_Authority_of_WoSign_G2.pem
Adding debian:Certinomis_-_Root_CA.pem
Adding debian:CFCA_EV_ROOT.pem
Adding debian:COMODO_RSA_Certification_Authority.pem
Adding debian:Entrust_Root_Certification_Authority_-_EC1.pem
Adding debian:Entrust_Root_Certification_Authority_-_G2.pem
Adding debian:GlobalSign_ECC_Root_CA_-_R4.pem
Adding debian:GlobalSign_ECC_Root_CA_-_R5.pem
Adding debian:IdenTrust_Commercial_Root_CA_1.pem
Adding debian:IdenTrust_Public_Sector_Root_CA_1.pem
Adding debian:OISTE_WISeKey_Global_Root_GB_CA.pem
Adding debian:Staat_der_Nederlanden_EV_Root_CA.pem
Adding debian:Staat_der_Nederlanden_Root_CA_-_G3.pem
Adding debian:S-TRUST_Universal_Root_CA.pem
Adding debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H5.pem
Adding debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H6.pem
Adding debian:USERTrust_ECC_Certification_Authority.pem
Adding debian:USERTrust_RSA_Certification_Authority.pem
Removing debian:America_Online_Root_Certification_Authority_1.pem
Removing debian:America_Online_Root_Certification_Authority_2.pem
Removing debian:A-Trust-nQual-03.pem
Removing debian:Buypass_Class_3_CA_1.pem
Removing debian:ComSign_Secured_CA.pem
Removing debian:Digital_Signature_Trust_Co._Global_CA_1.pem
Removing debian:Digital_Signature_Trust_Co._Global_CA_3.pem
Removing debian:E-Guven_Kok_Elektronik_Sertifika_Hizmet_Saglayicisi.pem
Removing debian:GTE_CyberTrust_Global_Root.pem
Removing debian:SG_TRUST_SERVICES_RACINE.pem
Removing debian:TC_TrustCenter_Class_2_CA_II.pem
Removing debian:TC_TrustCenter_Universal_CA_I.pem
Removing debian:Thawte_Premium_Server_CA.pem
Removing debian:Thawte_Server_CA.pem
Removing debian:TURKTRUST_Certificate_Services_Provider_Root_1.pem
Removing debian:TURKTRUST_Certificate_Services_Provider_Root_2.pem
Removing debian:UTN_DATACorp_SGC_Root_CA.pem
Removing debian:Verisign_Class_4_Public_Primary_Certification_Authority_-_G3.pem

These have always puzzled me ...
1. what are they? and
2. why removal vs updating? and
3. why do I need an added Turkish ca-certificate?

Sector11 · 2016-01-24 02:31:08

Head_on_a_Stick wrote:

^ That's interesting -- the new kernel version didn't require a `full-upgrade` to go through.
Good to know 8)

What new kernel version?
I'm still running the same kernel:
- - 3.16.0-4-amd64 x86_64 (64 bit gcc: 4.8.4)

maybe I need a reboot ... I see this:

Setting up bunsen-pipemenus (8.7.2-1) ...
Setting up intel-microcode (3.20151106.1~deb8u1) ...
update-initramfs: deferring update (trigger activated)
intel-microcode: microcode will be updated at next boot
Processing triggers for libc-bin (2.19-18+deb8u2) ...

bold mine

Sector11 · 2016-01-24 02:34:31

And a HUGE Thank You to Head_on_a_Stick.

I award you the Gold Plated Stick!

HoaGPS

hhh · 2016-01-24 02:39:35

A note to newer users, the certificate upgrade message needs you to manually continue the upgrade by pressing "q" (to quit the message), then the upgrade continues.

tknomanzr · 2016-01-24 02:41:40

Well, for one, package signing will most likely use some sort of public/private key trust. Any use of SSL/TLS would require one as well. Activity on them suggests to me that Debian actually watches out for old and or compromised certificate authorities.

Horizon_Brave · 2016-01-24 03:04:51

Whoo my first real "knowledgeable" distro upgrade!

So, just to clarify here.. (my hobby), all of the packages being updated here in this 8.3 release, where previously in "Testing" at one point. If I were tracking testing, I could have downloaded and installed any of these prior to the release of 8.3 right? But now that they have been "blessed" as stable, they are released as a bundle in the stable debian package? Do I have that right?

And is rc2 BunsenLabs itself in the "Testing" repos at this point?

Anyway, excited to post my update/upgrade results!

Thanks HoaS

Sector11 · 2016-01-24 03:05:30

@hhh - Yea the noob in me saw that [Q]uit scrolling up the screen before the 'click' >>> Hit the [Q|q]

damo · 2016-01-24 03:11:46

Horizon_Brave wrote:

Whoo my first real "knowledgeable" distro upgrade!
So, just to clarify here.. (my hobby), all of the packages being updated here in this 8.3 release, where previously in "Testing" at one point. If I were tracking testing, I could have downloaded and installed any of these prior to the release of 8.3 right? But now that they have been "blessed" as stable, they are released as a bundle in the stable debian package? Do I have that right?
And is rc2 BunsenLabs itself in the "Testing" repos at this point?
...

Nope, Debian 8.3 (and therefore BunsenLabs) is Debian Stable. Everything in Jessie was in Testing at some point ie before Debian 8 was released.
Debian Release Management

Debian News wrote:

https://www.debian.org/News/2016/20160123
The Debian project is pleased to announce the third update of its stable distribution Debian 8 (codename jessie). This update mainly adds corrections for security problems to the stable release, along with a few adjustments for serious problems. Security advisories were published separately and are referenced where applicable.
Please note that this update does not constitute a new version of Debian 8 but only updates some of the packages included

It looks like there are some stable releases from upstream though, including vlc.

Last edited by damo (2016-01-24 03:19:56)

hhh · 2016-01-24 04:40:32

damo wrote:

Debian Release Management

@Horizon, at the bottom see the Suite Update Policy section as well as this page and the links there...
https://www.debian.org/releases/

Also...
https://raphaelhertzog.com/2010/12/20/5 … -its-name/

Horizon_Brave · 2016-01-24 05:10:18

damo wrote:

Nope, Debian 8.3 (and therefore BunsenLabs) is Debian Stable. Everything in Jessie was in Testing at some point ie before Debian 8 was released.

hhh wrote:

damo wrote:
Debian Release Management
@Horizon, at the bottom see the Suite Update Policy section as well as this page and the links there...
https://www.debian.org/releases/

Right... I think that's what I meant. I may have worded it wrong. In the link you provided:

stable
Fast response for security updates. Minor updates include security and other important fixes only. Major updates are sourced from testing, and are infrequent, but large.

Many of the packages in this new 8.3 update, where taken from Testing. Those packages passed their Testing validation and have now been approved for the 8.3 stable release?

I mean these updated packages that we just downloaded from 8.3, had to go through the Testing process right? Besides the security ones probably. When a software creator decides to update his software package, he has to re-submit to Testing, then it gets re-validated and put into Stable with the next release correct? If this isn't correct, I give up, I'm going to bed in tears...

pvsage · 2016-01-24 05:26:36

I think that release updates like the one for vlc are "the exception that proves the rule" and only make it into a stable point release in extraordinary circumstances.

hhh · 2016-01-24 07:24:14

Horizon_Brave wrote:

When a software creator decides to update his software package, he has to re-submit to Testing, then it gets re-validated and put into Stable with the next release correct?

Not quite. See #4 of Herzog's "5 Reasons" article that I linked. Maintainers upload everything including security updates to unstable, the Security Team can upload directly to stable if it's major, testing packages may have major security holes temporarily as it rolls.

Sector11 · 2016-01-24 12:55:49

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

inxi tells me I'm still running BL 8.2 though, not 8.3

Head_on_a_Stick · 2016-01-24 12:59:45

^ What does

lsb_release -a
cat /etc/debian_version

say?

Sector11 · 2016-01-24 13:02:44

 24 Jan 16 @ 10:02:18 ~
  $ lsb_release -a
No LSB modules are available.
Distributor ID:	BunsenLabs
Description:	BunsenLabs GNU/Linux 8.2 (Hydrogen)
Release:	8.2
Codename:	bunsen-hydrogen
 
 24 Jan 16 @ 10:02:21 ~
  $ cat /etc/debian_version
8.3
 
 24 Jan 16 @ 10:02:29 ~
  $

Head_on_a_Stick · 2016-01-24 13:10:23

The lsb-release package wasn't updated then.

My jessie system had that package upgraded so perhaps your mirror is a little slow.

EDIT: Hold on, this a BunsenLabs problem -- I think @nobody needs to update the bunsen-os-release package.

EDIT2: Issue raised in https://forums.bunsenlabs.org/viewtopic … 761#p16761

Last edited by Head_on_a_Stick (2016-01-24 13:21:20)

Sector11 · 2016-01-24 13:24:11

It's the same that is in the package list:

 24 Jan 16 @ 10:12:35 ~
  $ list lsb-release
apt list filename
Listing... Done
lsb-release/stable,now 4.1+Debian13+nmu1 all [installed,automatic]
 
 24 Jan 16 @ 10:12:46 ~
  $

or are you saying Debian didn't update "lsb-release"

#1 2016-01-24 01:58:51

Debian 8.3 released

#2 2016-01-24 02:18:51

Re: Debian 8.3 released

#3 2016-01-24 02:22:25

Re: Debian 8.3 released

#4 2016-01-24 02:25:11

Re: Debian 8.3 released

#5 2016-01-24 02:31:08

Re: Debian 8.3 released

#6 2016-01-24 02:34:31

Re: Debian 8.3 released

#7 2016-01-24 02:39:35

Re: Debian 8.3 released

#8 2016-01-24 02:41:40

Re: Debian 8.3 released

#9 2016-01-24 03:04:51

Re: Debian 8.3 released

#10 2016-01-24 03:05:30

Re: Debian 8.3 released

#11 2016-01-24 03:11:46

Re: Debian 8.3 released

#12 2016-01-24 04:40:32

Re: Debian 8.3 released

#13 2016-01-24 05:10:18

Re: Debian 8.3 released

#14 2016-01-24 05:26:36

Re: Debian 8.3 released

#15 2016-01-24 07:24:14

Re: Debian 8.3 released

#16 2016-01-24 12:55:49

Re: Debian 8.3 released

#17 2016-01-24 12:59:45

Re: Debian 8.3 released

#18 2016-01-24 13:02:44

Re: Debian 8.3 released

#19 2016-01-24 13:10:23

Re: Debian 8.3 released

#20 2016-01-24 13:24:11

Re: Debian 8.3 released

Board footer