This is a support thread for requests or issues with packages supplied in my repository.  Currently my repository supports being used by ich777's un-get plugin however a fork of NerdTools is in the works in order to redirect it to my own repository.  Now that this exists please do not clutter the old NerdTools discussion with information for the contents of my repository or issues that stem from the applications within.

 

Repository URL: https://github.com/shinji257/unraid_pkgs

 

Usage of packages

Download the packages and place them in the extra folder on the flash drive. If you are doing this from a system currently running this is at

/boot/extra

 

To install the package run

installpkg file.t?z

 

All packages built using scripts from SlackBuilds.org or pulled from official repos unless otherwise specified.  Any scripts I modified in order to fix an issue with a package or update to a newer version will be included in the repository for inspection.

 

Heed any package requirements posted in my package list.  I've listed the ones I know about.  If a package doesn't work until you install a different package then please let me know by posting a bug issue so I can update the list with that information.

 

I won't post the un-get instructions here but they are on my repository.  Please be aware that un-get is meant for advanced users only!

 

Requests and bugs with existing packages on my repository should get posted as an issue on my repository so I can track it better.  You can request multiple packages in the same issue if you wish.  I'll note if a package has already been included or if it is duplicated in another issue.

 

Current package list: https://github.com/shinji257/unraid_pkgs/wiki/Available-Packages

Probably more detailed package management instructions using stock tools: https://github.com/shinji257/unraid_pkgs/wiki/Manually-maintaining-packages

 

Disclaimer: The installation of packages not included with Unraid may have unknown effects.  Please be aware of this.  It may be suggested to simply install a package before putting it in /boot/extra in order to test it's viability and effect before putting it there for future reboots.

 

Edit: Just a note here.  All packages are built for Unraid 7 (Slackware -current) and are not tested or guaranteed to work on Unraid 6.12.x.  Any python based packages will require Python 3.12 since that is the version currently released on Slackware -current.  They will not work with Python 3.9 as their package is not bundled for that version.

Edited January 31, 20251 yr by shinji257
Note about package requirements.

Thanks for your trouble... everything I tried works like a charm.

Hmm.  I got an email notification that someone has an issue with vim but seems reply might be deleted?  If you are still having issues let me know either here or open an issue on my repository and I'll look into it. 

 

Edit: My vim package is the same as the one from slackware-current as I just copy theirs rather than rebuilding it. Pretty sure there are no other builds of vim by default but still let me know if you have issues and post any errors you are getting. 

Edited January 27, 20251 yr by shinji257

6 minutes ago, shinji257 said:

Hmm.  I got an email notification that someone has an issue with vim but seems reply might be deleted?  If you are still having issues let me know either here or open an issue on my repository and I'll look into it. 

 

Edit: My vim package is the same as the one from slackware-current as I just copy theirs rather than rebuilding it. Pretty sure there are no other builds of vim by default but still let me know if you have issues and post any errors you are getting. 

 

Yes - that was me being dumb - vim didnt work because I failed to dig a bit deeper. I just had in do "un-get install libsodium" and all was fine. Question was that stupid that I had to remove it

Ahh. Then I at least have to note that libsodium is a dependency on my packages list. This is the type of stuff I need to know since I don't yet know where to look on the slackware repos for package dependencies. 

Could you possibly add the 'bat' program? It is A cat(1) clone with syntax highlighting and Git integration. There is a version that un-get installs from the Conraid repository but the current version (bat-0.25.0-x86_64-1cf.txz) is linked with a newer version of GLIBC than is installed on Unraid 6.12.15.

 

EDIT: I just tried to install 'fastfetch' from your repo and I get the same error:

fastfetch: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by fastfetch)

is there a way to install the new GLIBC without causing problems with the existing system?

 

Edited January 27, 20251 yr by kfonda
added new info

Sorry my repository targets and requires Unraid 7 as it was created in response to NerdTools depreciation on that version.  I don't currently have packages built for Unraid 6.12. 

I kind of figured that, I guess I'll have to build them my self or cave in and upgrade to 7.  Any suggestions on how to set up a build system in a VM?

 

For me I started even more barebones but I just used slackbuilds and you can pull packages from slackware-15 directly.  I think un-get points at slackware-current by default for the slackware packages repo but you can switch it to slackware-15 instead since you are on 6.12.5.  This will at least work for slackware official where vim was sourced from.

https://mirrors.slackware.com/slackware/slackware64-15.0/slackware64/ slackware-15

 

Slacker.it (conraid) builds for slackware-current as well as myself.  I'll see about making a slackware-15.0 repo folder for those staying on 6.12.x.

 

My current build environment is actually the Slackware LXC container running on Unraid 7.  XD

 

Forgot to address the actual question.  If you install it yourself I think Slackware installs all packages.  The only packages I actually build are the ones from Slackbuilds since they don't distribute binaries.  You would download the source and slackbuilds archives.  Unpack the slackbuilds archive, place the source archive in the same folder and run the SlackBuilds script.  It's a shell script and should automate everything.  Note any errors and try to resolve them.  They actually target slackware-15

Edited January 27, 20251 yr by shinji257

Thanks, I've managed to get started with a few using AutoSlackPack from SpaceInvaderOne. I actually started using Linux in the early 90's when the first Slackware came out. It was on about a million 3.5 inch floppies. Unfortunately, I haven't really kept up my command line skills over the last few years but now is as good a time as any to get back into it. 😀

would be handy if un-get got a silence install - now we always need to tap Y (but I think @ich777 needs to implement a  -y or --yes switch. Apart of that - I'm quite happy that you set up a new repo

37 minutes ago, sjoerd said:

would be handy if un-get got a silence install - now we always need to tap Y (but I think @ich777 needs to implement a  -y or --yes switch. Apart of that - I'm quite happy that you set up a new repo

Just try:

yes | un-get install python3

 

This was already discussed here:

https://github.com/ich777/un-get/issues/12

 

Can you please explain to me why you would need that? Usually you only install packages by hand anyways and the packages are installed each reboot.

Please also keep in mind un-get is not a package manager, un-get is just a tool to install packages for advanced users on Unraid.

3 hours ago, shinji257 said:

Slackware LXC container running on Unraid 7

Really cool to hear that you make use of my LXC plugin.

I had (and still have) a Docker container for that since I sometimes also have to build packages/plugins for Slackware.

 

3 hours ago, shinji257 said:

slackware-current by default for the slackware packages repo

For new installations un-get points to these two repositories:

https://mirrors.slackware.com/slackware/slackware64-current/slackware64/ current
https://slackers.it/repository/slackware64-current/ conraid

 

Sorry for the noob question, but when you place a .tgz file in /boot/extra what is the effect of that?

 

From my understanding, on each reboot of unraid this will essentially run "installpkg" on any files in that folder so that they end up in memory (since unraid runs in a ram disk) and are placed within the /usr/bin folder.

 

Questions:

 

1. I noticed you mentioned this isn't built for "6.12". What specifically prevents your builds from running on 6.12? 

2. Will we have problems running existing downloaded files from this repo when say unraid 7.1 comes out since for the same reasons these packages don't run on 6.12 they will break when doing unraid upgrades?

 

Suggestions:

 

1. Include instructions for download. Such as this example for 7-zip:

 

wget https://github.com/shinji257/unraid_pkgs/raw/refs/heads/main/slackware64-current/7zip/7zip-24.09-x86_64-1_SBo.tgz

Adding packages in /boot/extra allows Unraid to reinstall them (using installpkg) at boot so that they may persist between reboots.  You have this correct.

 

1.) Unraid 7 has a newer GLIB than Unraid 6.12 and since they are built for Unraid 7 (actually Slackware -current) many of them won't work and will throw an error regarding that fact.

 

2.) This should not impact the packages running on future versions pending compatibility.  There is always that risk when running software on the host system that were not included by default.

 

How the files are downloaded are left as an exercise to the end user.  There are many ways to go about doing it including the one you mentioned.

This is the error I keep getting in unraid 7 when trying to install one of the packages.

 

root@VideoArchives:/boot/extra# installpkg libmediainfo-24.12-x86_64-1_SBo.tgz
Verifying package libmediainfo-24.12-x86_64-1_SBo.tgz.

gzip: stdin: not in gzip format
cat: write error: Broken pipe
Unable to install libmediainfo-24.12-x86_64-1_SBo.tgz:  tar archive is corrupt (tar returned error code 2)

Make sure you downloaded the raw file and not just the file link itself. 

 

Edit: See a couple of messages up. 

Edited February 1, 20251 yr by shinji257

I'm struggling to get this to work. Is there step by step instructions for this? A tutorial video? I'm getting 

installpkg jdupes-1.28.0-x86_64-2_SBo.tgz
Verifying package jdupes-1.28.0-x86_64-2_SBo.tgz.

gzip: stdin: not in gzip format
Unable to install jdupes-1.28.0-x86_64-2_SBo.tgz:  tar archive is corrupt (tar returned error code 2)

 

Any plans to get this added into apps?

You're clicking on the file and that gives you a corrupt archive. Click on the Raw option.

6 hours ago, jhoan said:

I'm struggling to get this to work. Is there step by step instructions for this? A tutorial video? I'm getting 

installpkg jdupes-1.28.0-x86_64-2_SBo.tgz
Verifying package jdupes-1.28.0-x86_64-2_SBo.tgz.

gzip: stdin: not in gzip format
Unable to install jdupes-1.28.0-x86_64-2_SBo.tgz:  tar archive is corrupt (tar returned error code 2)

 

Any plans to get this added into apps?

I plan to modify NerdTools to point at a varient of my repo but I need to see how it determined dependencies and file paths so I can get it done properly. Currently been busy with work so have not had much chance to look at it. 

2 hours ago, Krakout said:

You're clicking on the file and that gives you a corrupt archive. Click on the Raw option.

I managed to figure it out. The file was fine. The installation command failed to include the path.

 

This is the correct way:

installpkg /boot/extra/jdupes-1.28.0-x86_64-2_SBo.tgz

 

Hey there,

sorry if I made a double post about problem which I also have right now.

So I have still installed NerdTools, but since I'm on v.7.0.0 of Unraid, I'd like to upgrade my files from boot/extra folder.

 

Here are my installed packages:

 

My question is, what should I do first? 

1. Remove NERD TOOLS (or leave it?) 

2. Download latest packages from shinji's github? 

 * Can I download latest python3 package from official site with .tgz extension?

3. Remove every file from boot/extra and right after that replace with latest files ?

4. Antyhing else?

 

Just for Your notice, I don't want to create more problems with this, so that's why (for some of You silly) I ask those type of questions.

Thanks.

Thanks for the repo!

 

Just for my own clarification, your slackware repo is more up to date and compatible than the default in un-get am I correct Therefore, should we disable the default one in un-get they target the current slackware version but unraid use different kernel so I'm unsure here.

 

Thanks :3

 

 

Edited March 13, 20251 yr by Neïla
More specifc question

@shinji257

 

a few github issues exist some with build scripts and packages requests. Was unable to set label.

 

 

Does anyone have a working repo for un-get that that will install jdupes and run on Unraid 7.1.2?