New package format for slackware 13?

Woodsman · 05-10-2009, 01:06 PM

Quote:

This is untested completely (not even compile tested), and I probably missed some needed bits, but it should get you on the right track: see the attachment for a diff to kdeutils-3.5.10.

This is new territory for me.

Please correct me if I do not understand the method for patching.

(Path names are relative/arbitrary for learning purposes only.)

1. Obtain a copy of the kdeutils sources directory and source file.

2. Copy the diff to {wherever}/kdeutils/kdeutils-3.5.10-support_xz_and_lmza_stuff.diff.txt.

3. Create a text file named {wherever}/kdeutils/apply-patches.sh:

Code:

cat $CWD/kdeutils-3.5.10-support_xz_and_lmza_stuff.diff.txt | patch -p1 --verbose || exit 1

4. Create a text file named {wherever}/kdeutils/local.options:

Code:

BUILD=3

5. If using a different directory structure then modify all path names as necessary in kdeutils.SlackBuild.

6. Run sh kdeutils.SlackBuild

Question: Do I still need to installpkg the a/xz package from current? Or the lzma package from slackbuilds.org?

Question: I'm not much of an Xfce user, but does the new compression format affect other utilities too? Say, xarchiver from slackbuilds.org?

Thanks.

Shingoshi · 05-10-2009, 06:50 PM

Quote:

Question: Do I still need to installpkg the a/xz package from current? Or the lzma package from slackbuilds.org?

You must have the xz package installed to support the new .txz package format.

Shingoshi

cardboardtoast · 05-11-2009, 05:14 PM

Quote:

Originally Posted by Shingoshi

You must have the xz package installed to support the new .txz package format.

Shingoshi

So I got the xz package, and now I can INSTALL .txz packages. but there is no way to see whats inside the package. Using explodepkg, I get this:
"Exploding package gnutls-2.6.6 in current directory:
cat: gnutls-2.6.6: No such file or directory
/sbin/explodepkg: line 90: -dc: command not found"

Is there another package laying around that I have to download to do view the contents of the file, or is this just something I will have to deal with?

Weee...I spent 2 hours trying to install a single package, don't I feel accomplished?

rworkman · 05-11-2009, 06:10 PM

Quote:

Originally Posted by cardboardtoast

So I got the xz package, and now I can INSTALL .txz packages. but there is no way to see whats inside the package. Using explodepkg, I get this:
"Exploding package gnutls-2.6.6 in current directory:
cat: gnutls-2.6.6: No such file or directory
/sbin/explodepkg: line 90: -dc: command not found"

Is there another package laying around that I have to download to do view the contents of the file, or is this just something I will have to deal with?

Weee...I spent 2 hours trying to install a single package, don't I feel accomplished?

I don't know if you feel accomplished or not, but you just learned the hard way that your choices are as follows:
1. Run the most recent stable release (12.2 as of right now)
2. Run -current (the development tree)

When you try to mix the two - as an example, because you want some of the new features available in the development tree - bad things can (and often do) happen.

For what it's worth, you also need the pkgtools from -current. Again though, if you continue to "pick and choose" which packages you install from -current onto a 12.2 system, please don't bother posting support questions here.

rworkman · 05-11-2009, 06:13 PM

Quote:

Originally Posted by Woodsman

This is new territory for me.

Please correct me if I do not understand the method for patching.

(Path names are relative/arbitrary for learning purposes only.)

1. Obtain a copy of the kdeutils sources directory and source file.

2. Copy the diff to {wherever}/kdeutils/kdeutils-3.5.10-support_xz_and_lmza_stuff.diff.txt.

3. Create a text file named {wherever}/kdeutils/apply-patches.sh:

Code:

cat $CWD/kdeutils-3.5.10-support_xz_and_lmza_stuff.diff.txt | patch -p1 --verbose || exit 1

4. Create a text file named {wherever}/kdeutils/local.options:

Code:

BUILD=3

5. If using a different directory structure then modify all path names as necessary in kdeutils.SlackBuild.

6. Run sh kdeutils.SlackBuild

Something like that, yes.

Quote:

Question: Do I still need to installpkg the a/xz package from current? Or the lzma package from slackbuilds.org?

Neither. You build the xz package using the -current build script.

Quote:

Question: I'm not much of an Xfce user, but does the new compression format affect other utilities too? Say, xarchiver from slackbuilds.org?

Not without patches to xarchiver. Feel free to file bug reports (feature enhancement) and CC me on them.

janhe · 05-11-2009, 06:47 PM

Quote:

Originally Posted by Alien Bob

[ ... ]
Also I've verified that the -current installer still works on hardware that is equipped with just 64 MB of RAM.
[ ... ]

Well, I run slackpkg to keep a -current install up to date on a machine with 128 MB RAM.

When it wanted to upgrade to the latest coreutils, xz stopped with a message saying it only was given 40 MB RAM, and that it really wanted 65 MB. Seems xz limits its RAM usage depending on the physical RAM available. I adapted the installpkg script to execute xz with the "--memory=70000000" option, now it wants to install coreutils*.txz

Sidenote: after xz stopped uncompressing the tar file, upgradepkg went ahead and removed the old coreutils package. Turns out you don't need coreutils to boot slackware. You only get lots of error messages like "/bin/ls not found" "cut: no such file or directory".

I got it recovered, but it wasn't something I expected to happen with a slackware package compiled for i486.

PS: does anybody know about side effects from manually extracting a slackware package in the root directory using standard (>1.13) tar?

Shingoshi · 05-11-2009, 06:52 PM

Quote:

Originally Posted by cardboardtoast

So I got the xz package, and now I can INSTALL .txz packages. but there is no way to see whats inside the package. Using explodepkg, I get this:
"Exploding package gnutls-2.6.6 in current directory:
cat: gnutls-2.6.6: No such file or directory
/sbin/explodepkg: line 90: -dc: command not found"

Is there another package laying around that I have to download to do view the contents of the file, or is this just something I will have to deal with?

Weee...I spent 2 hours trying to install a single package, don't I feel accomplished?

Don't feel too bad! I don't think you had pkgtools-tukaani installed. If you did, you'd have to remove it after having already installed the new Slackware pkgtools-12.3456789. But I don't think that was the issue here for you. If it was (and you didn't mention it), Slackware and Tukaani/Vector installs pkgtools in different locations. Slackware installs to /sbin, while the Tukaani/Vector pkgtools installs to /usr/sbin. So if you didn't remove the latter, you would have the explodepkg from T/V interfering with Slackware's.

Shingoshi

Shingoshi · 05-11-2009, 06:57 PM

Quote:

PS: does anybody know about side effects from manually extracting a slackware package in the root directory using standard (>1.13) tar?

I've had to do that myself, after removing pkgtools without installing/upgrading the replacement first. The only side effect is having an /install directory in /. You can remove that directory afterwards, and then reinstall the package so that it's properly registered.

Shingoshi

cardboardtoast · 05-11-2009, 09:47 PM

Quote:

Originally Posted by rworkman

I don't know if you feel accomplished or not, but you just learned the hard way that your choices are as follows:
1. Run the most recent stable release (12.2 as of right now)
2. Run -current (the development tree)

When you try to mix the two - as an example, because you want some of the new features available in the development tree - bad things can (and often do) happen.

For what it's worth, you also need the pkgtools from -current. Again though, if you continue to "pick and choose" which packages you install from -current onto a 12.2 system, please don't bother posting support questions here.

Alright, I see what your saying. I have always just used -current when updating, just because it seemed like current would be just that, current. I had no idea that would cause any problems by itself <.<
--
And Shingoshi, I am using the new Slackware pkgtools, with no T/V pkgtools, so that is one thing I got right for that. But after reading the top, should I drop back to old pkgtools?

Thanks for the help, Sorry if that derailed the thread :/

Shingoshi · 05-11-2009, 10:08 PM

Quote:

And Shingoshi, I am using the new Slackware pkgtools, with no T/V pkgtools, so that is one thing I got right for that. But after reading the top, should I drop back to old pkgtools?

You should only drop back to the standard pkgtools, if you haven't already installed any of the new .txz packages on your system. Otherwise, you need to keep the pkgtools-12.3456789. It will still handle the standard .tgz packages. You would only want to change your repositories back to 12.2. But for the record, I do the same thing. I have the following slapt-get repositories:
SOURCE=http://slackware.osuosl.org/slackware-current/
SOURCE=http://dogbert.no-root.org/slackware-12.2/ ## Tremendous selection of packages!!
SOURCE=http://www.vislab.uq.edu.au/slackware/12.2/ ## Scientific software
SOURCE=http://rlworkman.net/pkgs/12.2/ ## xfce, Openoffice
SOURCE=http://slackware.oc9.org/slackware-12.2/rkeene/ ## Some non-standard software packages.
SOURCE=http://get.gnomeslackbuild.org/gsb/gsb-current/ ## Obviously, GNOME!!

I've kept the new pkgtools, because it allows me to build packages using the new .txz format. You only need to change the extension in your SlackBuilds for it to work.

Shingoshi
#100/205

disturbed1 · 05-12-2009, 02:07 AM

Quote:

Originally Posted by janhe

Well, I run slackpkg to keep a -current install up to date on a machine with 128 MB RAM.

When it wanted to upgrade to the latest coreutils, xz stopped with a message saying it only was given 40 MB RAM, and that it really wanted 65 MB. Seems xz limits its RAM usage depending on the physical RAM available. I adapted the installpkg script to execute xz with the "--memory=70000000" option, now it wants to install coreutils*.txz

I just attempted a fresh install with 128MB of RAM, and ran into the same issues as you. During the installation, 100MB of swap was used as well. The installation went through without an error popping up. Though, there were some quick messages under the dialog I caught no ????? cannot find ?????

Wish I could tail the log file?

Upon reboot, no ls, cut, mv, failed to mount /dev/pts .... looks like more than just coreutils fails to install.

I didn't spend anytime attempting to recover since mount did not work either. Swapped in an extra 128MB of RAM and reinstalled. Everything worked with 256MB RAM.

gmartin · 05-12-2009, 09:24 AM

I usually follow Pat's upgrade howto from the last version, but it appears that will be changing. How about these modified upgrade scripts? (Note, the first two steps are still correct)

First:

Code:

upgradepkg /root/slackware/a/pkgtools-*.tgz

Then:

Code:

installpkg /root/slackware/a/xz*.tgz

Code:

upgradepkg /root/slackware/a/glibc-solibs-*.t?z

(or possibly removepkg then installpkg)

Finally:

Code:

upgradepkg --install-new /root/slackware/*/*.t?z

or

Code:

#!/bin/sh
cd /tmp/slackware-current
sleep 10
    for dir in a ap d e f k kde l n t tcl x xap y ; do
      ( cd $dir ; upgradepkg --install-new *.t?z )
    done

janhe · 05-13-2009, 11:12 AM

Quote:

Originally Posted by disturbed1

I just attempted a fresh install with 128MB of RAM, and ran into the same issues as you. During the installation, 100MB of swap was used as well. The installation went through without an error popping up. Though, there were some quick messages under the dialog I caught no ????? cannot find ?????

Wish I could tail the log file?

Upon reboot, no ls, cut, mv, failed to mount /dev/pts .... looks like more than just coreutils fails to install.

I didn't spend anytime attempting to recover since mount did not work either. Swapped in an extra 128MB of RAM and reinstalled. Everything worked with 256MB RAM.

So it seems slackware-current only supports systems with 256 MB of RAM or more for now.

The workaround I posted above will worked with my system that has 128 MB of RAM, but it probably won't work on a system with 64 MB.

Then again, Alien_Bob reported success with a standard install on a 64 MB RAM system... Anyone who wants to guess what causes the difference?

vdemuth · 05-13-2009, 01:20 PM

On this theme of Slackware current, is anyone experiencing problems with both the links to the download mirrors from the Slackware website no longer being valid, and secondly with slackpkg not able to handle the new txz extension files. In particular when trying to upgrade. Might be that they are both related of course, and the mirrors just not keeping up to date correctly.

niels.horn · 05-13-2009, 03:50 PM

You might need to upgrade to the latest version of slackpkg & pkgtools first, as it is needed to upgrade other packages in the new tgz format.