Requests for -current (14.2-->15.0)

marav · 08-17-2021, 04:10 AM

Quote:

Originally Posted by LuckyCyborg

Probably I missed to read those legends, that's why I had no issues to build on the last five years my own Firefox packages on my flagship box with a 45W Athlon x4 605e. Usually it spent an evening for this task.

IF I managed to do this as a regular Slackware user, I have all the trust that the interested companies can find and hire very qualified people to build their wanted Firefox ESR and any other LTS things they desire.

OR, they can all can gather their moneys together and can ask for a Slackware Enterprise Linux edition full of shinny LTS things.

I have neither the desire nor the time to compile my own firefox
And, as far as I now, you're not just a "regular user" :-) even if you like to present yourself as such
"regular user" doesn't spend an evening compiling his own browser

regdub · 08-17-2021, 05:16 AM

Hi,

Cross-post from https://www.linuxquestions.org/quest...2/#post6275984

I have sound but errors with amixer commands and selecting a card with mplayer.

Digging the alsa-lib tip, I think there is a problem with the latest aaa_libraries package.

It contains a /usr/lib64/libasound.so.2.0.0 file dating from February, much more older than the alsa-lib one.

EDIT: Re-installing the /usr/lib64/libasound.so.2.0.0 file from before the upgrade solves my problems immediately.
Thanks to pomf for suggesting re-installing alsa-lib.

saxa · 08-17-2021, 07:02 AM

network-manager-applet-1.24.0
https://download.gnome.org/sources/n...-1.24.0.tar.xz

ArTourter · 08-17-2021, 07:56 AM

Quote:

Originally Posted by saxa

Freshly baked:

vala-0.52.5
https://download.gnome.org/sources/v...-0.52.5.tar.xz

This version also fixes a change in API that prevents some applications from compiling (pdfpc being one of them). So an update would be welcome.

TheTKS · 08-17-2021, 08:34 AM

Quote:

Originally Posted by Alien Bob

I tried that version and while vncviewer works, the developer is braindead and made some incompatible architectural changes to the vncserver which makes it unfit for Slackware unless we patch it a great deal. For more background see: https://github.com/TigerVNC/tigervnc/issues/1099
Pat and I thought it was too much effort and therefore we stick with 1.10.1.

Eric, thanks for letting us know why TigerVNC is not moving to the latest version, and the link to the background.

TKS

zeebra · 08-17-2021, 08:39 AM

Is it possible to update this file for users of Slackware 14.2?
https://mirror.netcologne.de/slackwa...nux/README.TXT

I'm not an expert on making iso images, so I pretty much have to follow these instructions step by step. I have an idea what is going on, but if a step is not available, it will lead me into trouble.

1) So, those current instructions don't work for Slackware 14.2 as "xorriso" is not part of the default packages for Slackware 14.2.
- using Slackware 14.2 /isolinux/README.txt is also not possible, as 15.0 RC1 lacks isolinux/isolinux.boot
Can these instructions somehow be harmonized for Slackware 14.2 users and idiots like me?
2) The instructions are also not "correct" for Slackware 15 RC1 users as Slackware RC1 lacks isolinux/boot.cat

I actually have a Slackware15.rc1.iso working, based on guesswork. It works on the bios laptop I'm testing on, so it's not a problem for me, but it probably wount work on a UEFI laptop (I got ehm, some warnings..)..

Anyways, I was hoping it would be possible to update those instructions. And I would hope there would be instructions in that file for users of Slackware 14.2 as well.

Petri Kaukasoina · 08-17-2021, 09:19 AM

Quote:

Originally Posted by zeebra

lacks isolinux/isolinux.boot
lacks isolinux/boot.cat

The filename specified with -c should not pre-exist. It will be created in the ISO image.

Alien Bob · 08-17-2021, 09:22 AM

For Slackware 14.2 you would of course use the instructions for Slackware 14.2 at https://mirror.netcologne.de/slackwa...nux/README.TXT
That file "isolinux.boot" does not exist in the Slackware directory tree indeed, and that is also correct. Because mkisofs will create that file inside the ISO.

GazL · 08-17-2021, 09:39 AM

Hmmm, I hadn't noticed the instructions had changed.

Any issue if one still used mkisofs + isohybrid per the old instructions?

I've been using this:

Code:

#!/bin/bash

: ${OUT:=/local/slackware/iso/slackware64-current.iso}

cd /local/slackware/mirror/slackware64-current || exit 1

mkisofs -o "$OUT" \
  -R -J -A "Slackware Install" \
  -hide-rr-moved \
  -v -d -N \
  -no-emul-boot -boot-load-size 4 -boot-info-table \
  -sort isolinux/iso.sort \
  -b isolinux/isolinux.bin \
  -c isolinux/isolinux.boot \
  -eltorito-alt-boot -no-emul-boot -eltorito-platform 0xEF \
  -eltorito-boot isolinux/efiboot.img \
  -m 'source' \
  -V "SlackDVD" .

isohybrid -u "$OUT"

bassmadrigal · 08-17-2021, 09:52 AM

Quote:

Originally Posted by LuckyCyborg

Let's hope this never happen, because both the LTS kernel and the Firefox for Enterprise gives no advantages to home users.

Except for not having potentially disrupting changes thrusted on them... which I've told you many times and you continually choose to be ignorant of it. This isn't a call for Pat to change, but just for you to be less ignorant of why some might want that.

zeebra · 08-17-2021, 10:08 AM

Quote:

Originally Posted by Alien Bob

For Slackware 14.2 you would of course use the instructions for Slackware 14.2 at https://mirror.netcologne.de/slackwa...nux/README.TXT
That file "isolinux.boot" does not exist in the Slackware directory tree indeed, and that is also correct. Because mkisofs will create that file inside the ISO.

Quote:

Originally Posted by Petri Kaukasoina

The filename specified with -c should not pre-exist. It will be created in the ISO image.

So.. To sum it up. It is perfectly fine to use the instructions in Slackware 14.2? It should all work as expected? (that's basically what I did, but I mixed some 15.0RC1 instructions into it).
But, probably most people will download the iso anyways, and not the filetree. But if you did in 14.2, you wouldn't have the 14.2 instructions available. I only had those because I'm messing around with 14.2 alot on that same computer currently.

Ps. It's my first Slackware -current

yay

UPDATE: Trying instructions from Slackware 14.2 caused ISOLINUX "unknown keyword in configuration file:" followed by a bunch of weird charachters and "no deault or ui configuration directive found"..
So I ended up making the Slackware15rc1.iso from Slackware-current with Slackware-current xorriso instructions from the same filetree.

oily · 08-17-2021, 10:41 AM

Quote:

Originally Posted by zeebra

So.. To sum it up. It is perfectly fine to use the instructions in Slackware 14.2? It should all work as expected? (that's basically what I did, but I mixed some 15.0RC1 instructions into it).
But, probably most people will download the iso anyways, and not the filetree. But if you did in 14.2, you wouldn't have the 14.2 instructions available. I only had those because I'm messing around with 14.2 alot on that same computer currently.

Ps. It's my first Slackware -current

yay

I created an iso about 3-4 weeks ago using the 14.2 instructions. I think one file might have been absent from the -current tree (can't remember which), but it was easy enough to figure out. The ISO worked fine anyway.

DryFalls · 08-17-2021, 12:39 PM

squashfs-tools-4.5-x86_64-1 symlinks in /usr/bin point to /tmp/package-squashfs-tools/usr/bin/. sqfscat should link with unsquashfs and sqfstar with mksquashfs.

df.

drumz · 08-17-2021, 02:02 PM

Quote:

Originally Posted by DryFalls

squashfs-tools-4.5-x86_64-1 symlinks in /usr/bin point to /tmp/package-squashfs-tools/usr/bin/. sqfscat should link with unsquashfs and sqfstar with mksquashfs.

df.

I can confirm:

Code:

# ls -l /usr/bin/sqf*
lrwxrwxrwx 1 root root 46 Aug 16 09:49 /usr/bin/sqfscat -> /tmp/package-squashfs-tools/usr/bin/unsquashfs
lrwxrwxrwx 1 root root 46 Aug 16 09:49 /usr/bin/sqfstar -> /tmp/package-squashfs-tools/usr/bin/mksquashfs

Because:

Code:

# cat /var/lib/pkgtools/scripts/squashfs-tools-4.5-x86_64-1
( cd usr/bin ; rm -rf sqfscat )
( cd usr/bin ; ln -sf /tmp/package-squashfs-tools/usr/bin/unsquashfs sqfscat )
( cd usr/bin ; rm -rf sqfstar )
( cd usr/bin ; ln -sf /tmp/package-squashfs-tools/usr/bin/mksquashfs sqfstar )

It's due to a bug in the Makefile (lines 409 and 410):

Code:

        ln -fs $(INSTALL_DIR)/unsquashfs $(INSTALL_DIR)/sqfscat
        ln -fs $(INSTALL_DIR)/mksquashfs $(INSTALL_DIR)/sqfstar

should be:

Code:

        ln -fs unsquashfs $(INSTALL_DIR)/sqfscat
        ln -fs mksquashfs $(INSTALL_DIR)/sqfstar

instead.

drumz · 08-17-2021, 02:06 PM

... and already fixed upstream:
https://github.com/plougher/squashfs...a266d9e3bfd415