shinji257

ZFS Master may need an update with the current 7.2-rc2 (and rc1 as well but that isn't current now). When this plugin is installed it causes the Unraid Connect icon to disappear on the Main tab. It doesn't prevent it from working in other areas but it is definitely annoying and I had to dig a little to figure out the cause.

Sorry. Been busy with some life stuff. Make sure you have the libjodycode package installed as well. Run un-get installed and send back the output if it still doesn't work. If for some reason they do not appear in the un-get search then you can use these links and install them manually. Make sure to put them in /boot/extra so they get reinstalled on reboot as well https://github.com/shinji257/unraid_pkgs/raw/refs/heads/main/slackware64-current/jdupes/jdupes-1.28.0-x86_64-2_SBo.tgz https://github.com/shinji257/unraid_pkgs/raw/refs/heads/main/slackware64-current/libjodycode/libjodycode-3.1.1-x86_64-2_SBo.tgz

This has been a very useful tool and have it loaded on Unraid 7 as well (it works right? -- hope so). Anyways while it doesn't seem to necessarily break anything I noticed that its portion on the Main page causes a couple of 404 errors to show in the log. Figured I'd let you know in case you didn't already know. Apr 7 06:26:27 Pithos nginx: 2025/04/07 06:26:27 [error] 43564#43564: *483992 open() "/usr/local/emhttp/plugins/dynamix.docker.manager/styles/style-black.css" failed (2: No such file or directory) while sending to client, client: 127.0.0.2, server: , request: "GET /plugins/dynamix.docker.manager/styles/style-black.css?v=autov_fileDoesntExist HTTP/1.1", host: "127.0.0.1", referrer: "http://127.0.0.1/Main" Apr 7 06:26:27 Pithos nginx: 2025/04/07 06:26:27 [error] 43564#43564: *483987 open() "/usr/local/emhttp/plugins/dynamix.docker.manager/styles/style-black.css" failed (2: No such file or directory) while sending to client, client: 127.0.0.2, server: , request: "GET /plugins/dynamix.docker.manager/styles/style-black.css?v=autov_fileDoesntExist HTTP/1.1", host: "127.0.0.1", referrer: "http://127.0.0.1/Main"

Open a ticket so I can add it to the todo list. I'll add it when I get a minute to do so.

I was working to fork NerdTools but I was only planning to support Unraid 7 at this time. From what I could tell from the code it gets the version Unraid currently running and builds that into the url for package downloads so it would be possible to just setup another folder named for the prior version (I think it would be 6.12) and installing NerdTools there would point to an appropriate folder automatically. As for a build system... I've been using lxc with the minimal slackware current environment and adding package as needed. It's a bit of trial and error. Getting errors, figuring out what slackware package has to be installed, and trying the build again.

I've been rebuilding packages to work on Unraid 7.

Many of the packages in the original NerdTools is broken in Unraid 7 because it is based on a newer slackware branch. That's why it is depreciated/unsupported now.

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.

Make sure you downloaded the raw file and not just the file link itself. Edit: See a couple of messages up.

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.

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

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.

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.

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.

Just want to say thank you for your work on this. I've setup a Slackware lxc container (for my repository work since it is on -current) and a Debian container for other stuff. I also found information on the config file setup and managed to have it create a dev/shm automatically for Slackware (one doesn't exist by default and is needed for certain things) and mount a host folder on Debian.

I've created a support/requests topic in order to split discussion there for my repository. Please redirect your attention there. It includes normal directions for package consumption.

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.

Of course.

Thanks. I'll make a post about it over there when I get a moment to do so. In the meantime I ask that you stop discussing my repository in here so that maybe it could get back to nerdtools. If you need to discuss repository specific things you can either DM me or open a discussion thread on the repository until I do so.

Is there some place I can setup a support thread for my repository? I'm not "supporting" un-get. It just happens to be the mechanism I have setup at the moment until I can sort out nerdtools and move it to use my own repository however I do want to split it off. The only place I see to create support threads is in here but it seems to be for Plugin Support.

Well I never asked for that tutorial to be created. I have instructions on my own github that are proper and correct. Disregard the one above as it isn't mine.

You made me realize I never actually said how to use un-get so I've added that information. I have some wiki pages as well that are setup to try and detail usage.

If you are setting up for un-get you don't need to use installpkg. It would just be un-get install package so un-get install 7zip

The repository is setup for use with un-get so people can use that. A forking of nerdtools is setup and implementing the same packages there is a work in progress.

I'm guessing you are asking how. Jdupes is available as a slackbuild package. I have it built on my repository for installation and it is version 1.68 as of right now. On a side note I rearranged my repository to be usable via un-get. This has been tested and the readme on it now includes instructions on where to get un-get from as well as where to add the repository. I forked nerdtools a bit back but trying to sort out how it is setup so I can make sure the plugin user interface will reflect it correctly. Be aware of dependencies for packages on my repository. un-get doesn't have a way (that I saw) to flag and install dependencies for packages you install.