Is 14.2 the same as the latest update 14.1 with Current?

Yaguar · 07-13-2016, 10:47 AM

Hello Slackers community.

I'm a Slackware intermediate level user. I use it because it's security.

As we know, the 14.2 version is now available. I'm a 14.1 user and I've been making a weekly update of my system using Slackpkg with Current (update, upgrade,install-new). With that, I have questions to ask: Is the latest update of Current equivalent with the new 14.2? What I have to change?

I hope you can help me with this question.

Thanks.

montagdude · 07-13-2016, 10:55 AM

These are the changes to -current since 14.2 was released:

Quote:

Originally Posted by ftp://ftp.osuosl.org/pub/slackware/slackware64-current/ChangeLog.txt

Code:

Tue Jul 12 03:48:34 UTC 2016
a/etc-14.2-x86_64-8.txz:  Rebuilt.
  In /etc/profile.d/lang.{csh,sh}.new, make en_US.UTF-8 the default locale.
a/kernel-generic-4.4.15-x86_64-1.txz:  Upgraded.
a/kernel-huge-4.4.15-x86_64-1.txz:  Upgraded.
a/kernel-modules-4.4.15-x86_64-1.txz:  Upgraded.
a/lilo-24.2-x86_64-3.txz:  Rebuilt.
  In liloconfig:  Skip the menu asking if the user wants a UTF-8 virtual
  console, and use the kernel default (currently this is UTF-8 active).
d/kernel-headers-4.4.15-x86-1.txz:  Upgraded.
k/kernel-source-4.4.15-noarch-1.txz:  Upgraded.
isolinux/initrd.img:  Rebuilt.
kernels/*:  Upgraded.
usb-and-pxe-installers/usbboot.img:  Rebuilt.
+--------------------------+
Sat Jul  9 18:35:56 UTC 2016
x/mesa-12.0.1-x86_64-1.txz:  Upgraded.
+--------------------------+
Fri Jul  8 23:17:22 UTC 2016
x/mesa-12.0.0-x86_64-1.txz:  Upgraded.
+--------------------------+
Thu Jul  7 19:52:36 UTC 2016
n/samba-4.4.5-x86_64-1.txz:  Upgraded.
  This release fixes a security issue:
  Client side SMB2/3 required signing can be downgraded.
  It's possible for an attacker to downgrade the required signing for an
  SMB2/3 client connection, by injecting the SMB2_SESSION_FLAG_IS_GUEST or
  SMB2_SESSION_FLAG_IS_NULL flags.  This means that the attacker can
  impersonate a server being connected to by Samba, and return malicious
  results.
  For more information, see:
    http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2119
  (* Security fix *)
+--------------------------+
Tue Jul  5 04:52:45 UTC 2016
xap/mozilla-thunderbird-45.2.0-x86_64-1.txz:  Upgraded.
  This release contains security fixes and improvements.
  For more information, see:
    http://www.mozilla.org/security/known-vulnerabilities/thunderbird.html
  (* Security fix *)
+--------------------------+
Sun Jul  3 19:29:33 UTC 2016
a/file-5.28-x86_64-1.txz:  Upgraded.
a/util-linux-2.28-x86_64-1.txz:  Upgraded.
xap/mozilla-firefox-47.0.1-x86_64-1.txz:  Upgraded.

The two security updates have also gone into 14.2. If you want to switch to 14.2, I believe you can just switch your mirror in /etc/slackpkg/mirrors to 14.2, and then do:

Code:

slackpkg update gpg
slackpkg update
slackpkg install slackware64  #(Assuming you are on slackware64)

(Someone correct me if I'm wrong on that.)

cwizardone · 07-13-2016, 10:58 AM

If I understand your question correctly, yes, you are running 14.2, plus any changes since its release. Put another way, you are running -current, if you have been installing the updates.

Gerard Lally · 07-13-2016, 11:04 AM

Quote:

Originally Posted by Yaguar

I'm a 14.1 user and I've been making a weekly update of my system using Slackpkg with Current (update, upgrade,install-new).

Your post is confusing. Are you a 14.1 user or a -current user? Which mirror have you enabled in /etc/slackpkg/mirrors?

Quote:

With that, I have questions to ask: Is the latest update of Current equivalent with the new 14.2? What I have to change?

The latest -current now incorporates changes that are not in 14.2. You can see the changes at, you guessed it, the changelog for -current, which is here.

Yaguar · 07-13-2016, 12:04 PM

Ok..

1. montandude, thanks for the information. I'll make the switches and will report the results.
2. cwizardone and gezley, sorry ... yes, I was confuse in my post: I started with 14.1, then I changed the the mirrors (slackpkg) to "current".
3. montandude, I'm using slackware64

montagdude · 07-13-2016, 12:19 PM

I'm not totally sure if the 'slackpkg install slackware64' command will take care of everything for you or not. If not, you might need to "upgrade" (actually downgrade) some things based on the ChangeLog. Be careful if you've already updated to kernel 4.4.15 on your -current machine, as you will probably want to keep that around at least temporarily to ensure you can boot your system, and you will need to reconfigure and run lilo if you add/change the kernel.

In any case, be careful while you are doing it and make sure to check what is going to be changed before you let slackpkg proceed with making the changes.

frushiyama · 07-13-2016, 12:22 PM

Quote:

Originally Posted by Yaguar

Ok..

2. cwizardone and gezley, sorry ... yes, I was confuse in my post: I started with 14.1, then I changed the the mirrors (slackpkg) to "current".

If you choose to do a 14.1 to 14.2 upgrade, first you should do this ftp://ftp.osuosl.org/pub/slackware/s...nt/UPGRADE.TXT .Then you can set mirrors to current.

onebuck · 07-13-2016, 05:58 PM

Hi,

Quote:

Originally Posted by Yaguar

Hello Slackers community.

I'm a Slackware intermediate level user. I use it because it's security.

As we know, the 14.2 version is now available. I'm a 14.1 user and I've been making a weekly update of my system using Slackpkg with Current (update, upgrade,install-new). With that, I have questions to ask: Is the latest update of Current equivalent with the new 14.2? What I have to change?

I hope you can help me with this question.

Thanks.

With PV's announcement;

Quote:

Thu Jun 30 20:26:57 UTC 2016 Slackware 14.2 x86_64 stable is released! The long development cycle (the Linux community has lately been living in "interesting times", as they say) is finally behind us, and we're proud to announce the release of Slackware 14.2. The new release brings many updates and modern tools, has switched from udev to eudev (no systemd), and adds well over a hundred new packages to the system. Thanks to the team, the upstream developers, the dedicated Slackware community, and everyone else who pitched in to help make this release a reality. The ISOs are off to be replicated, a 6 CD-ROM 32-bit set and a dual-sided 32-bit/64-bit x86/x86_64 DVD. Please consider supporting the Slackware project by picking up a copy from store.slackware.com. We're taking pre-orders now, and offer a discount if you sign up for a subscription. Have fun! :-)

After the June 30,2016 release then any changes would be '-current'. On June 30,2016 that would be the official Slackware 14.2 for any changes made to your system using the then '-current' changelog to get the updates however as a user gets the updates via slackpkg or even getting your local tree in sync via 'mirror-slackware-current.sh'. Once PV's starts updating the changelog then that is '-current' development cycle from then on until the next release.

Hope this helps.
Have fun & enjoy!

bormant · 07-13-2016, 06:28 PM

Yes on the release date and to first non-security update on current.
No after first update mention above.
Until glibc or another major update goes to current they are compatible in the common part.