Hi,

a little bug ???

the file slackware/ap/ghostscript-9.18-arm-2
is not in PACKAGES.TXT nor in FILELIST.TXT nor in ChangeLog.txt

greetings
W.Slacker

Re: Hi again,

is anyone interesting in, or willing to, build an hardfloat Slack-ARM-Pi2 complete distribution ???

i would spend my time (and machine power) for compiling, error detection, maybee some translations (to german) but just a very litle bit .. ....

W.Slacker

It's not there in the master FTP sites.
Is it a particular mirror you're using?

Hi,

.. you are right, it's not there (anymore ??) ... ?
mine had been from ftp.halifax.rwth-aachen.de/slackwarearm/slackwarearm-current/ i think ..

14221988 Jan 4 00:55 ghostscript-9.18-arm-2.txz

but as you said its not there and i can't find it online anymore ???
the namings inside this file are also 9.18 ...
can't reproduce where i did get that ...

.. i have a lock at my own notices ... it says ..
--
Slack(14.2)-current
installed by help of rpi2-slackwarearm-install_13Mar15_fd.img
dd if=rpi2-slackwarearm-install_13Mar15_fd.img of=/dev/sdd bs=512
to temporary boot"disk" (SD32GB) ...
--

maybe that helps ...

That's one of the master servers I sync to and only gets updated by me.

I haven't pushed anything since the last time stamp in -current (apart from right now).

I don't know who produces that or what's in it (presumably ghostscript is included?), but what I suspect has happened is that if you look in the change log for -current, you'll see the reversion to the older version of ghostscript 9.07 due the newer one segfaulting.
You should downgrade to the version in -current if you did not already do so.
If you're using an automated update tool, make sure it can downgrade packages. If it can't you're going to have to check the change log and manually take care of any downgrades.

Re Hi,

thanks for your "personal support"

it could be exact this way you said ...
but i wonder why you dont know of http://rpi2.fatdog.eu/ where i get this initial image from ...
(it uses the ftp.slackware.org.uk::slackwarearm/slackwarearm-current/ for initial pkg downloading)

maybe "we" should put our knowlege together instead of anyone did try to build its own system ...

yes - i will do that ...

and then i will spend some days to build an minimal initial slack-current hardfp for my raspi2's because i want to get rid of the debianisch outdated and unstable "standard pi linux" - lol

i need the slack way for my pi's - install it and forget it - it just had to do what i want - 24/7 the same way my other computers do ...

thank you so far
W.Slacker

I do know of that project but I'm not familiar with the file names, and aren't about to go looking for them all when it's easier to ask you, and I was also pretty confident that I knew what the issue was anyway :-)

Most of the people who created the community support have been in touch with me for a few years now and I help where I can; but my interest and focus is on the core OS plus the devices I own personally (the "officially supported" ones). If I can merge anything back (normally small things such as device namings to enable root login over serial ports) into the core that saves the community some continual effort and doesn't move in to "fork" territory, then I consider it.

Have fun :-)

Hmm, so if you own a device personally it becomes officially supported?

That's always the plan, but some of the kit still sitting in the desk drawer is now evidence that the plan is either a long term thing, or that there are other things with higher priorities - like concreting in fence posts for my fences that almost became horizontal during recent winds, etc etc. There is no doorway where you were thinking ;-)

That was my thought, a Raspberry Pi or two could easily be shipped to you.

Oh - yea - i Will spend them - they do rearly "kost nix" - german words for not expencive ... lol

i have got 2x PiB and 4xPi2B - one PiB is an 24/7 webcam to thes west direction, one Pi2B is a webcam to the east direction, the rest are for other projects and to test the new software before i put it onto the headless webcams - there have always been one spare one ...

gretting
(from Pi-Land) W.Slacker

The Slackware ARM userland will run perfectly well on almost any arm device that is of any interest currently (although it could possibly run a litter faster on some).
The miniroot images is a good and fast way to get Slackware ARM on any of them provided you can find a suitable kernel for whatever deice you want to try, specially if it's not officially supported. In fact all my ARM devices were installed by starting off with a miniroot image (including the ones that had official support).
I like the miniroot thing so much that I've built my own x86_64 miniroot image ... as far as I'm concerned it beats a custom tagfile installation in may situations.

Stuart:
thanks for giving us such a handy thing
I noticed that you added slackpkg in the miniroot but still it's missing some deps to get it to work right (I dropped you an email about it ... well maybe more then just one)

I did the minirootfs on my Pi3, I was thinking of asking about slackpkg as well, only thing its missing is gpnpg right (thats all I saw missing anyway)?

Nope, I had to add l/mpfr and l/ncurses to get slackpkgs to do all the tasks (including the post installation config file stuff).
I also twigged a little the build script to make it work for both 32 and 64 bit package directories and to do nochroottest by default.
These are the things I changed:
TESTCHROOT=${1:-nochroottest}

if [ ! -d slackware -a ! -d slackware64 ]; then
echo "Unable to find slackware package directory"
exit 1
fi


[ -d slackware64 ] && pushd slackware64 > /dev/null || pushd slackware > /dev/null

Stuart: You got them too via email

I don't recall having to add either of those packages. Only issue I have so far with minirootfs is I can't seem to separate root and boot on two different drives. Not sure why but I tried mounting both during the extract and tried copying over afterward. Guess I need to post a thread on it.