LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 07-10-2012, 06:26 AM   #1
jaycee4
Member
 
Registered: Aug 2009
Posts: 42

Rep: Reputation: 7
Upgrading from 13.37 to Current (30th June) - Bug with xz


Hello fellow Slackers! Earlier today I made a clean installation of Slackware 13.37 and attempted upgrading it to Slackware Current. My first attempt was unsuccessful, despite following the official instructions (ftp://ftp.slackware.no/slackware/sla...37/UPGRADE.TXT), although starting from step 1 (i.e. I was in init 3, not init 1), and using slackpkg instead of pkgtools. However, after downgrading xz from the Current version to the 13.37 version and installing all the security updates for 13.37, I quickly realised the issue - the new xz package (xz-5.0.4-x86_64-1.tgz) isn't compatible with .txz packages made using older releases (i.e. xz-5.0.3-x86_64-2.tgz and earlier). Once I ignored upgrading it (until very last) and followed the remaining instructions, my upgrade was successful. So (Pat), would it be possible to rebuild xz so that it's compatible with older .txz packages?
 
Old 07-10-2012, 10:00 AM   #2
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,334

Rep: Reputation: Disabled
Please note that by choosing to install and run Slackware-current, you accept that you are essentially a beta tester for our next public stable release. This implies that you are able to fix any breakage yourself, possibly with the help of users in this forum.

Slackware-current is a development effort, meant to work toward a new stable release (Slackware 14 is our next target). It is not a release in itself (i.e. it is not a "rolling release" as offered by other distros). In particular, it is not advised to use a file like UPGRADE.TXT for upgrading to Slackware-current. this file, and CHANGES_AND_HINTS.TXT are applicable to stable releases only.

Having said that, I am curious why you think the new xz is incompatible with .txz packages created by older versions? Lots of people have upgraded to Slackware-current and do not have the problem you are describing.

Note that apart from upgrading everything manually, I think that using slackpkg is the most reliable way of performing an upgrade to any version of Slackware, including -current, as long as you do not skip an intermediate stable release.

Eric
 
Old 07-10-2012, 10:22 AM   #3
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,896

Rep: Reputation: 952Reputation: 952Reputation: 952Reputation: 952Reputation: 952Reputation: 952Reputation: 952Reputation: 952
Quote:
Originally Posted by jaycee4 View Post
the new xz package (xz-5.0.4-x86_64-1.tgz) isn't compatible with .txz packages made using older releases (i.e. xz-5.0.3-x86_64-2.tgz and earlier).
No problems with 5.0.4 here. It opens any XZ compressed file I throw at it, including older Slackware packages. For example:

Code:
$ xz --version
xz (XZ Utils) 5.0.4
liblzma 5.0.4
$ wget -q http://ftp.slackware.no/pub/linux/slackware/slackware-13.37/slackware/a/aaa_base-13.37-i486-3.txz
$ xz -cd aaa_base-13.37-i486-3.txz | tar t | head
./
tmp/
opt/
boot/
srv/
install/
install/slack-desc
install/doinst.sh
etc/
etc/slackware-version
 
Old 07-10-2012, 10:33 AM   #4
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,619
Blog Entries: 2

Rep: Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076
I have recently downgraded from -current to 13.37 (due to problems with AMD's driver policy) and upgraded later to -current again (driver problems solved), without any problem. So I can assure you that xz must be compatible with older versions, your problem must have a different cause.
 
Old 07-10-2012, 10:48 AM   #5
Bazzaah
Member
 
Registered: Mar 2007
Distribution: Slackware64-current, Slackware64 14
Posts: 327

Rep: Reputation: 49
I upgraded to 14 a few days back and all went smoothly and I've had no trouble with anything at all. If I do, I'm pretty sure it'll be down to something I've done or not done.
 
Old 07-10-2012, 11:41 AM   #6
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,248

Rep: Reputation: 574Reputation: 574Reputation: 574Reputation: 574Reputation: 574Reputation: 574
Slackware-current running smooth as silk here. No issues to report.
 
Old 07-10-2012, 02:06 PM   #7
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 875

Rep: Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823Reputation: 1823
Quote:
Originally Posted by hitest View Post
Slackware-current running smooth as silk here. No issues to report.
We'll see what we can do about that soon.
 
7 members found this post helpful.
Old 07-10-2012, 02:13 PM   #8
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,248

Rep: Reputation: 574Reputation: 574Reputation: 574Reputation: 574Reputation: 574Reputation: 574
Quote:
Originally Posted by volkerdi View Post
We'll see what we can do about that soon.
You caught me off guard with that one, Pat! Awesome. I look forward to it, man.
 
Old 07-10-2012, 02:57 PM   #9
Dominian
LQ Newbie
 
Registered: Aug 2007
Distribution: Slackware-current
Posts: 4

Rep: Reputation: 0
Quote:
Originally Posted by jaycee4 View Post
Hello fellow Slackers! Earlier today I made a clean installation of Slackware 13.37 and attempted upgrading it to Slackware Current. My first attempt was unsuccessful, despite following the official instructions (ftp://ftp.slackware.no/slackware/sla...37/UPGRADE.TXT), although starting from step 1 (i.e. I was in init 3, not init 1), and using slackpkg instead of pkgtools. However, after downgrading xz from the Current version to the 13.37 version and installing all the security updates for 13.37, I quickly realised the issue - the new xz package (xz-5.0.4-x86_64-1.tgz) isn't compatible with .txz packages made using older releases (i.e. xz-5.0.3-x86_64-2.tgz and earlier). Once I ignored upgrading it (until very last) and followed the remaining instructions, my upgrade was successful. So (Pat), would it be possible to rebuild xz so that it's compatible with older .txz packages?

I just performed an upgrade just yesterday and it went without issue. xz didn't fail at all.. I only ever recall one time during a distribution upgrade that we had to install an xz (or upgrade it or what not) and that was when the packaging formats were changing and defaulting to .txz. During that upgrade, you had to install the xz package before going through with it or it would completely fail.
 
Old 07-10-2012, 06:22 PM   #10
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482

Rep: Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534
I have not had any problems with the newer version of xz reading older xz files, but I did run into a problem with older versions of xz (Slackware 13.1/xz-4.999.9beta) not being able to read xz packages from Current. I did not perform any exhaustive testing --- instead I rebuilt the newer version on the 13.1 system and then blacklisted with slackpkg. Possibly this (possible) incompatibility is what the OP is referring?

Edit:
When backporting the latest xz to previous versions of Slackware, also rebuilt the rpm package.

Last edited by Woodsman; 07-14-2012 at 11:58 AM.
 
Old 07-11-2012, 04:55 AM   #11
jaycee4
Member
 
Registered: Aug 2009
Posts: 42

Original Poster
Rep: Reputation: 7
Quote:
Originally Posted by Alien Bob View Post
Please note that by choosing to install and run Slackware-current, you accept that you are essentially a beta tester for our next public stable release. This implies that you are able to fix any breakage yourself, possibly with the help of users in this forum.

Slackware-current is a development effort, meant to work toward a new stable release (Slackware 14 is our next target). It is not a release in itself (i.e. it is not a "rolling release" as offered by other distros). In particular, it is not advised to use a file like UPGRADE.TXT for upgrading to Slackware-current. this file, and CHANGES_AND_HINTS.TXT are applicable to stable releases only.

Having said that, I am curious why you think the new xz is incompatible with .txz packages created by older versions? Lots of people have upgraded to Slackware-current and do not have the problem you are describing.

Note that apart from upgrading everything manually, I think that using slackpkg is the most reliable way of performing an upgrade to any version of Slackware, including -current, as long as you do not skip an intermediate stable release.

Eric
Hey Eric!
Don't worry, I'm aware -current is the development branch (although I now see how referring to it as Current may indicate otherwise), and that I'm expected to attempt my own fixes. In this case, my fix was successful. I performed the upgrade with the intention of finding potential issues so they could be fixed for the release of Slackware 14.
I inferred that the new xz was incompatible with older versions from the following experience:

1. Zeros written to entire hard drive with dc3dd (using Parted Magic).
2. Slackware64 13.37 installed (with all available packages except /extra) from the dvd.
3. Enabled -current mirror and upgraded xz-5.0.2-x86_64-1.tgz to xz-5.0.4-x86_64-1.tgz with slackpkg.
4. Using slackpkg I downloaded glibc-solibs-2.15-x86_64-4.txz and its signature, but slackpkg didn't even remove the old version before encountering an error. (From memory, the error essentially said that the new version couldn't be installed, and that reinstalling the old version was recommended.) Tried once more and failed as before. Tried with some other glibc packages and still failed.
5. Removed xz-5.0.4, enabled 13.37 mirror instead, and installed xz-5.0.2.
6. Successfully upgraded glibc-solibs and then all other packages to the latest available on the 13.37 mirror.
7. Had a change of heart (sorry, but 13.37 is too awesomely stable for my liking), changed back to -current mirror, successfully upgraded glibc-solibs and then all other packages except xz until very last.
8. Slackware-current working!
9. (In the near future) Pat delivers some exciting breakage to -current!

The only difference I can deduce between my failure to upgrade and my successful upgrade is the version of xz used. What else might the issue be?
If fellow Slackers desire, I could attempt to reproduce the issue, but I think my laptop hard drive is a little tired of having zeros written to it (I've done that a few times the past week for various reasons). At least I'll give it a rest for a few days...
In any case, thanks Eric and other Slackers for your suggestions and assistance!
 
Old 07-11-2012, 05:20 AM   #12
wildwizard
Member
 
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 755

Rep: Reputation: 227Reputation: 227Reputation: 227
My money is on the glibc update.

If you follow the ChangeLog (which is highly recommended when running -current) you will see that glibc is updated before xz.
 
Old 07-11-2012, 05:44 AM   #13
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,082
Blog Entries: 52

Rep: Reputation: Disabled
Quote:
Originally Posted by jaycee4 View Post
3. Enabled -current mirror and upgraded xz-5.0.2-x86_64-1.tgz to xz-5.0.4-x86_64-1.tgz with slackpkg.
4. Using slackpkg I downloaded glibc-solibs-2.15-x86_64-4.txz and its signature, but slackpkg didn't even remove the old version before encountering an error. (From memory, the error essentially said that the new version couldn't be installed, and that reinstalling the old version was recommended.) Tried once more and failed as before. Tried with some other glibc packages and still failed.
5. Removed xz-5.0.4, enabled 13.37 mirror instead, and installed xz-5.0.2.
6. Successfully upgraded glibc-solibs and then all other packages to the latest available on the 13.37 mirror.
7. Had a change of heart (sorry, but 13.37 is too awesomely stable for my liking), changed back to -current mirror, successfully upgraded glibc-solibs and then all other packages except xz until very last.
8. Slackware-current working!
I thought this was the correct way to upgrade to -current, from the slackpkg man page:
Quote:
Slackpkg can be used to upgrade the whole distribution.
The usual way is to do:
# slackpkg update
# slackpkg install-new
# slackpkg upgrade-all
# slackpkg clean-system
 
Old 07-11-2012, 08:07 AM   #14
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,619
Blog Entries: 2

Rep: Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076
Quote:
Originally Posted by jaycee4 View Post
I think my laptop hard drive is a little tired of having zeros written to it (I've done that a few times the past week for various reasons).
Then don't do it. There is no need to zero out the disk before installing an OS.
 
Old 07-11-2012, 09:08 AM   #15
caduqued
Member
 
Registered: Apr 2008
Location: Coventry, United Kingdom
Distribution: Slackware64, Slackware64 13.37, linuxslackware
Posts: 81

Rep: Reputation: 19
Quote:
Originally Posted by volkerdi View Post
We'll see what we can do about that soon.
Yes, waiting for something to be done.... I've been holding on next release to setup my small server... it can wait all time is needed, but if something is going to happen soon... well GREAT!!! The sooner the merrier (Just teasing some around!!!)

Thanks Pat and team...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
May have found a bug in 64 current? corbintechboy Slackware 11 07-11-2009 09:42 AM
[BUG] Current pkgtools installpkg bug jazzor Slackware 7 04-16-2009 06:30 AM
A bug about QT in current zhoun Slackware 5 03-15-2009 10:14 PM
Python bug in -current? Rupa Slackware 2 04-06-2008 06:46 PM
Is this a bug in current? slackware_newbie Slackware 3 09-19-2006 02:46 PM


All times are GMT -5. The time now is 06:36 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration