Re: [Slackbuilds-users] Using a Git repo as the source
On Sat, 8 Jun 2024, Shahab Vahedi via SlackBuilds-users wrote: https://github.com/csmith-project/creduce/archive/refs/heads/llvm-13.0.zip I didn't know about this. Thanks! That will solve the problem. In general, any push to this branch, will require an update of the MD5. I guess it is what it is. Download the file and host it somewhere else. If you decide to use the github link, beware: the link results in a different filename being saved, depending on whether or not the client uses the Content-disposition header. Example: $ mkdir a $ cd a $ wget --quiet --content-disposition https://github.com/csmith-project/creduce/archive/refs/heads/llvm-13.0.zip $ ls creduce-llvm-13.0.zip $ wget --quiet --no-content-disposition https://github.com/csmith-project/creduce/archive/refs/heads/llvm-13.0.zip creduce-llvm-13.0.zip llvm-13.0.zip This is annoying, but not fatal. Just make sure your SlackBuild script can cope with either filename. One way to do it: ZIPFILE=$CWD/$PRGNAM-llvm-13.0.zip [ ! -e $ZIPFILE ] || ZIPFILE=$CWD/llvm-13.0.zip unzip $ZIPFILE Another thing... if you change the .zip to .tar.gz in the URL, you get a tarball instead of a zip file. I just checked, and the .tar.gz file is 25% smaller than the zip file, but the contents are identical. So that seems like a win. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Using something other than bash for rc scripts?
On Sat, 11 May 2024, Didier Spaier wrote: Also, taking the risk of beating a dead horse, I suggest using only the features specified by POSIX, and not bash specific ones, for the sake of portability. That, or, put #!/bin/bash at the top of the script instead of #!/bin/sh. I don't think bash is going to disappear from Slackware, even if the #!/bin/sh link someday points to something else. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] What is the better way to have the linker look into additional paths to find shared objects and why?
On Sun, 5 May 2024, Didier Spaier wrote: Hello, a very few SlackBuilds @ Sbo write config files including additional paths in /etc/ld.so.conf.d but a lot more export LD_LIBRARY_PATH with the additional path appended in as script stored in /etc/profile.d Which way is better and why? /etc/ld.so.conf.d/ is a bad idea. sbopkglint will complain about it, and there's a good reason for it. Any library path mentioned in /etc/ld.so.conf.d/ will be used *before* the standard paths or the ones in /etc/ld.so.conf. This means, if you use it in a SBo package, and if that package includes a library that lots of software uses, *everything else* on the system will use the new library instead of the Slackware-provided one. A concrete example: a while back we had a package that broke wget, because wget (a stock Slackware package) was using a library in /etc/ld.so.conf.d/ that was linked with systemd's libraries. Sorry I can't remember the name of the build now, but sooner or later I will... ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] All-writable directory under /opt
On Sat, 4 May 2024, Daniel Prosser wrote: Thanks for the ideas. I like the idea of using the setgid bit, but I'm having trouble getting it to work. First, the main executable is a wrapper script, which may be a problem, but even applying the setguid bit to the binary file and foregoing the wrapper script (doing the stuff the wrapper script would have done manually in the shell for testing purposes) results in library import errors. I assume this is due to permissions somehow, but I don't really understand why. Because the wrapper script exports LD_LIBRARY_PATH (to tell the executable where to find the libs), and glibc deliberately ignores that variable on binaries with the setuid or setgid bits set. So that approach wouldn't work. Asking the user to run as root the first time would work, but I would also have to tell them to then copy the configuration directory from /root to their user directory and set permissions accordingly, which seems rather unwieldy and inconvenient. Hm. You mean, if the copy was created by running it as root, it *still* tries to make a new copy, if run without a config file? In a related idea, what about installing the program with some group ownership (say "LucasChess") and asking the user to join that group before running? That could work. Go with a lowercase group name though, lucaschess or just lucas. For that matter, you could go with the system games group. Ask user to join that group. Though, it would also let the user edit the high scores for games that save high scores as the games group. Realistically I don't think this matters much. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] All-writable directory under /opt
On Fri, 3 May 2024, Daniel Prosser wrote: The copy it makes is called stockfish-16.1-64. On my machine, it seems to have copied the bmi2 version, but maybe the plain -x86-64 version would be more universal. (For that matter, if I take this approach, I'll probably just make a symbolic link instead of wasting disk space with a copy.) I can think of one more approach... assuming the stockfish-16.1-x86-64 binary will run on anything x86_64 (because it doesn't have fancy CPU-specific optimizations), pre-create the symlink to that one. Advise the user that the other engines exist (in the README) and give a short set of instructions on how to choose the right one (basically as simple as, rm the symlink, run the engine as root once). This way, people who just install it without paying much attention will at least get a working (if unoptimized) package. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] All-writable directory under /opt
On Fri, 3 May 2024, Daniel Prosser wrote: An alternative potential solution that I think would work would be to have the SlackBuild script copy the file, selecting a build that would work for everyone. I can think of three approaches that avoid a world-writable directory in /opt. 1. Duplicate (or copy/paste, if possible) the logic it uses to decide which binary to copy, and put the logic in the SlackBuild (you could also just rm the other binaries, since they'll be unused). Or maybe do it in the doinst.sh. 2. Mention in the README that it has to be run as root, once, to set up the engine. Further, you could replace the game binary with a script that checks whether the copy/symlink exists, and if it doesn't exist, bail out with a message telling the user to run it as root. 3. If the main game binary (the thing that copies the engine file) is a regular binary (not a script), you could make it run setgid games, and make the engine directory writable by (owned by) the games group. This is how a lot of games handle their high-scores file (in /var/games//). But this won't work if the main game binary is a script (shell, perl, python, etc). ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] malloc runtime error, any suggestions?
On Mon, 15 Apr 2024, phala...@komputermatrix.com wrote: It's version 3.5.1 -- it's pushed but not distributed yet. OK, I just built 3.5.1 with the existing script (VERSION=3.5.1 in the environment) and it starts up and seems to work OK. It does say this: spectrwm: Welcome to spectrwm V3.5.1 Build: 3.5.1 ...so I know I'm running the right version. So whatever's going on might be specific to your system... ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] malloc runtime error, any suggestions?
On Mon, 15 Apr 2024, phala...@komputermatrix.com wrote: Hi all, I'm getting a malloc() runtime error startx-ing a window manager called spectrwm. Any suggestions on how to get more details on this? It seems this version of spectrwm runs on other distros, like Alpine for example. I'd like to report it to the developer if it's really a bug, or patch it in Slackware. It builds and runs fine here. Can you give us more detail? Try 'startx &> ~/x.log', and attach the resulting x.log to a list email... Also, are you on Slackware 15.0? Slackware-current isn't officially supported, but if it's a problem with -current, we'd like to know. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] rpi-imager
On Sun, 14 Apr 2024, Jay Lanagan via SlackBuilds-users wrote: Rpi-imager does work just fine. I made a slackbuild for it recently before I realized it was already on sbo. You should be the maintainer of rpi-imager. I don't think suncon is going to maintain it... I base this on the fact that suncon submitted that one package, and has no other activity in the log (no other builds, no updates to his one build, in the past year). That, and the non-working email address, and lack of response on this mailing list. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] rpi-imager
On Sat, 13 Apr 2024, Jude DaShiell wrote: Wasn't that package taken over by the raspberry foundation itself? That may be where to find the source code now. Github has the sources for both 1.7.5 and the new 1.8.5. The problem here isn't that the source is missing, the problem is that the SBo maintainer is missing. The good news is, if you download the 1.8.5 source from github: https://github.com/raspberrypi/rpi-imager/archive/v1.8.5/rpi-imager-1.8.5.tar.gz ...and run rpi-imager.SlackBuild with VERSION=1.8.5 set in the environment, it runs OK, and creates a rpi-imager-1.8.5-x86_64-1_SBo.tgz package that at least looks plausible. I don't own a Raspberry Pi and don't have any microSD cards left, so I can't test to see if it actually works, but presumably Jim can... ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] rpi-imager
On Sat, 13 Apr 2024, Jim wrote: The 15.0 version of rpi-imager is at 1.7.5, and rpi-imager is up to (at least) 1.8.5. I emailed the maintainer (sun...@posteo.net), and got a bounce from a mail server saying that recipient doesn't exist. Does anyone know whether this person has a new email address, has beamed up to the mother ship, or ... ? We don't know... but, now that you've asked on the mailing list, there's a chance the maintainer will see it and respond here. If not, if you get no response after a week, feel free to take over the build yourself. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] oidentd very outdated and won't be updated?
On Mon, 1 Apr 2024, dchme...@gmail.com wrote: I use oidentd but don't make network utility SlackBuilds (I'm far from a network expert) so if anyone else does, one might consider asking him you can takeover oidentd? Yet you maintain network/icyque... which uses the network in more complex ways than oidentd does. It's not rocket science. There's already a slackbuild and it already works. You could take it over and update it. You don't have to be a network expert, you just have to know how to use whatever you're packaging, and make sure it works (you probably use it for IRC and already know how to tell if the IRC server got an ident response). Since the build is unmaintained, whoever wants it updated badly enough can take it over. You're the only one who's interested enough to post to the mailing list about it in the 5+ years since it was last updated, so you're the #1 candidate to become its new maintainer. Just for testing, I downloaded the latest oidentd source (v3.1.0) and ran oidentd.SlackBuild with VERSION=3.1.0 in the environment, and it built just fine. So updating the build isn't going to take you a lot of time and effort (just VERSION and DOWNLOAD need to be changed). I'd say, go for it. You can do this. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Running rxvt-unicode
On Wed, 27 Mar 2024, Rich Shepard wrote: I find the file rxvt-unicode in /usr/share/terminfo/r/ but it's not executable. How do I tell xfce4 to use rxvt-unicode as the terminal emulator? Again, wrong list for this question. Absolutely nothing to do with SBo. It's not even a Slackware-specific question. Most likely, if you just do a google or duckduckgo search for something like "set default terminal in xfce4", you will be illuminated. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] skypeforlinux cannot be fetched
On Sat, 23 Mar 2024, Shahab Vahedi via SlackBuilds-users wrote: Hi Jay, March 22, 2024, Jay via SlackBuilds-users wrote: People using 'sbopkg' to manage their SBo packages get an option to get sources from this archive automatically if a normal download fails. How can I trigger this fall-back mechanism in "sbopkg"? I've checked the /usr/sbin/sbopkg script and it looks like that "make_archive_url()" should automatically take care of it through the the default hardcoded "http://slackware.uk/sbosrcarch; URL. However, the fall-back doesn't kick in. I've also tried uncommenting the "SRC_REPO" line in /etc/sbo/sbopkg.conf that points to "http://slackware.uk/sbosrcarch; to no avail. Am I doing something wrong or do I need to investigate the situation better? No, it's broken, and has never worked properly, despite what people have said. The only time it works correctly is if wget succeeds in downloading *something*, but the downloaded file's md5sum doesn't match the .info file. If wget fails to download anything at all (404 not found, or site down entirely), the archive stuff doesn't get called at all. I know this because I'm the one who put the sbosrcarch support in sbopkg, I checked it into git as a proof of concept, and hoped that someone who *knows* the sbopkg codebase would be able to finish it. But no such person exists (or, anyway, no such person is actively working on sbopkg any more). The sbopkg codebase is utterly alien to my ways of thinking about code. It's not "bad" or "wrong", it obviously works very well. But I found it difficult to follow the logic, so I punted and tried to hand it over to someone who already knew how it worked. Finishing the job is now on my TODO list, I'll go back and work out a better solution, one that actually works. I had honestly forgot about this (I'm not a sbopkg user, myself), so thanks for reminding me. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] suggestion for a new category for fonts
On Thu, 21 Mar 2024, Willy Sudiarto Raharjo wrote: Since we have search form in our website, i wonder how many people would go through each categories when looking for some scripts instead of just using the search form? OK, so in that case, why do we have categories at all? Would it bother you to get rid of them entirely? Other than the amount of work it would take to accomplish it, I mean. Would we be better off if there had never been categories? We could just add a keyword for each build, with its former category. system/dosbox would just become dosbox/, and get "system" added to its list of keywords... ...which is silly of course. It's intended to be silly. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] jq fails to build
On Wed, 20 Mar 2024, nnb via SlackBuilds-users wrote: Some tests fail because of locale setting. I did run sbopkg like this and the build worked fine 'LANG=C sbopkg'. Hopefully the maintainer can add 'export LANG=C' somewhere near the top of the script. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Linphone maintenance
On Wed, 20 Mar 2024, Sebastian Arcus wrote: I have copied Euan into the email I sent to the list on 07 Feb 2024 asking if the Linphone scripts could be updated - but there hasn't been any reply. I already accepted to look after BcToolbox, which he used to maintain - as he hasn't been active in a long time. Should I try to contact Euan again? Don't bother. Euan Thoms' last activity was in November of 2017, over 6 years ago. I think we can consider this one an ex-maintainer. Whoever wants to take over linphone, and any other of his builds, just submit an update (possibly after discussing it on this mailing list). I recommend whoever takes linphone also takes its dependencies that were maintained by Euan: libraries/libantlr3c libraries/libsrtp libraries/bzrtp libraries/belle-sip Whoever wants them should also take Euan's other builds: libraries/ccrtp libraries/libzrtpcpp libraries/msx264 libraries/ucommon network/netdrive-connector ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] suggestion for a new category for fonts
On Tue, 19 Mar 2024, Qun-Ying wrote: Currently fonts are put under category system, they mix with other system tools. Would it be better to have a separate category (fonts) for them? If we're voting, I vote for this. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] eclipse-platform slackbuild
On Sat, 9 Mar 2024, Tim Dickson via SlackBuilds-users wrote: the download link for the source?/binary for this package appears not be be available any more. newer versions are available, but they require java 17 or higher. regards, Tim If you just want to build the existing version, there's a copy of the source in the SBo source archive, here: https://slackware.uk/sbosrcarch/by-md5/4/8/48253adbb219851359613344d942d934/eclipse-platform-4.19-linux-gtk-x86_64.tar.gz ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] tracking down missing sbo dependencies
On Mon, 4 Mar 2024, Didier Spaier wrote: To sum it up, gkterm, glktemrw and glulxe are all stand-alone software. Close. Actually, on further research, I've found that glulxe isn't standalone: it depends on having a glk implementation. Which can be either glkterm or glktermw. So Jude got the relationship backwards, glktermw doesn't have glulxe as a dependency, it *is* a dependency of glulxe. Now that I've worked out the relationship between them, I'll be submitting glulxe to SBo, with REQUIRES="glktermw". Jude, you can build glulxe with my glktermw package with a command like: make OPTIONS="-DOS_UNIX -DUNIX_RAND_GETRANDOM" \ GLKINCLUDEDIR=/usr/include/glktermw \ GLKLIBDIR=/usr/lib64 \ GLKMAKEFILE=Make.glktermw I haven't tested it thoroughly yet, but it at least will load up Advent.ulx from the glulxe homepage, here: https://www.eblong.com/zarf/glulx/ ...or, wait 5 days or so and glulxe will be on SBo. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] tracking down missing sbo dependencies
On Mon, 4 Mar 2024, Jude DaShiell wrote: It turns out glktermw is for unicode wide character support but didn't make glulxe so far as I can tell. The out of slackbuilds made that for me and installed it in /usr/local/bin. glulxe isn't included in glktermw at all, the only mention of it is in in readme-widechar.txt... What source were you building that gave you a glulxe binary? I might want to add it to SBo... I thought it might be https://github.com/erkyrath/glkterm but that doesn't have glulxe either (it looks like the non-wide-char version of glktermw). ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] tracking down missing sbo dependencies
On Mon, 4 Mar 2024, Jude DaShiell wrote: I found the glktermw package had at least one missing dependency so ended up building glkterm directly from git packages outside of slackware and outside of slackbuilds What dependency is missing? It builds on a clean full install of 15.0, and it works when fizmo is built with glktermw installed: I get a fizmo-glktermw executable, which works (I'm playing Zork in it now). Looking at glktermw's Makefile, the only dependency I see is libncursesw, which is in a full Slackware install. What did you mean by "at least one missing dependency"? What problems did you have building glktermw with the SBo script? Can you post the full log (stdout and stderr) of the build? Does this routinely happen when scripts on slackbuilds could have been written better so those dependencies get pulled in and compiled? No, broken builds do not routinely happen. If they do, they get fixed ASAP... which is why I want to see your build log: if something's wrong with my build, I want to fix it. If you're using -current rather than 15.0, well, SBo only supports 15.0 (or whatever the latest stable is). Still, if there's a way to fix it so it works on -current, I'll go ahead & do that if I can. I think that glktermw package is meant for graphical user environment not necessarily text user interfaces. Now I already have glkterm working here, I could download glktermw and see if it will build and if it can work in text user interface. fizmo-glktermw is definitely a text user interface. It runs in a terminal. Also, glktermw's own readme.txt says: GlkTerm: Curses.h Implementation of the Glk API. ... This is source code for an implementation of the Glk library which runs in a terminal window, using the curses.h library for screen control. Curses definitely means terminal, not GUI. fizmo is actually the only thing on SBo that uses glktermw. I don't know any other applications that use it... what are you using when you say you have it "working here"? ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] hw-probe should be arch independent
On Tue, 27 Feb 2024, Dimitar Nikov via SlackBuilds-users wrote: Slackware package is arch independent too, hence x86_64 download is marked as unsupported. I do believe this is correct for acrh independent packages. No, it should just be blank... DOWNLOAD_x86_64="" ...which means "x86_64 uses the same source as the regular DOWNLOAD". UNSUPPORTED would mean the package can't be built on x86_64, which is obviously not the case here. Upstream doesn't provide a man page, but it looks like Debian just uses help2man, which Slackware has. Nice shout, will move to help2man in next version update. Beware: Slackware's help2man isn't the same as Debian's. You might make it work, but it might take some messing with. If you have trouble, just grab the man page from the Debian package and include it with your script. Install with something like: mkdir -p $PKG/usr/man/man1 gzip -9c < $CWD/$PRGNAM.1 > $PKG/usr/man/man1/$PRGNAM.1.gz Hope this helps... ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] opera-ffmpeg-codecs needs update for opera-107...
On Sun, 11 Feb 2024, Heiko Rosemann via SlackBuilds-users wrote: So: Is anyone working on opera-ffmpeg-codecs still or should I take over? Looks like its maintainer, Dmitris Zlatanidis, just updated it in January: commit ab0440d8ba06f78e20b1fcdd87ab25de8012db82 Author: Dimitris Zlatanidis Date: Thu Jan 4 23:22:08 2024 +0200 multimedia/opera-ffmpeg-codecs: Updated for version 0.83.0. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] ngspice42
On Sat, 27 Jan 2024, Ralph Spitzner via SlackBuilds-users wrote: gives me this: make[2]: Leaving directory '/tmp/SBo/ngspice-42/release' make[1]: Leaving directory '/tmp/SBo/ngspice-42/release' chmod: cannot access 'ngspice-42/usr/doc/ngspice-42/examples/klu/Circuits/libraries/*.lib': No such file or directory Confirmed, I get the same thing here, and an IRC user says he does too. Looks broken. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] potrace download error.
On Fri, 26 Jan 2024, Fernando Lopez wrote: Resolving potrace.sourceforge.net (potrace.sourceforge.net)... failed: Temporary failure in name resolution. Did you try again, a bit later? "Temporary"... Anyway, it works here. Either a network hiccup in sourceforge's CDN, or your ISP, or whatever. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] edk2-ovmf
On Sat, 20 Jan 2024, Jim Brewster wrote: Hi all, I got a 404 trying to fetch the source for this package (it's actually a Fedora binary), and when I did some snooping, I couldn't find that exact version or one I could trivially substitute. The Slackbuild is looking for both an x86_64 binary and one for ia32, and that's where I'm hitting a brick wall. Archived copies here: https://slackware.uk/sbosrcarch/by-name/system/edk2-ovmf/ The fact that sbosrcarch has the files means the URLs were good at one time... maybe Fedora rearranged things on their site? If someone is maintaining the package, I don't want to reinvent the wheel; otherwise I could dig deeper. Maybe it's just a temporary issue with accessing the source? Looks like the maintainer is active: commit df72ea1966c19c9b25f7b67574c7abe7180f1800 Author: Gene Carlson Date: Thu Jan 4 09:13:02 2024 +0900 system/edk2-ovmf: Updated for version 202311. Signed-off-by: Willy Sudiarto Raharjo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Trying to build offline trello-cli with npm
On Sat, 20 Jan 2024, Tonus wrote: Or shall I download, check against sha512 and create a md5sum fingerprint ? Since .info files only support md5sums, yes, you'll have to list the md5sums there. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Can't get this build right : trello-cli
On Sat, 20 Jan 2024, Tonus wrote: Thank you for the alert, I didn't realize that. Previous build hadn't this problem and will investigate that. Shall I cancel my submission or let admins do ? Go ahead and cancel it. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Can't get this build right : trello-cli
On Sat, 20 Jan 2024, Tonus wrote: Thanks a lot for your answer. It solves the link issues. I think I looked at the wrong template and am on the right way for stripping the binairies. I see one serious problem with your build: It requires network access when it runs. npm downloads stuff from the 'net. See if you can come up a way to do a purely local build... maybe just pre-download the files npm wants to download, add them to your DOWNLOAD in the .info file, have the script copy them to where npm would put them? I'm not a npm expert so I don't know if this would be feasible... ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Can't get this build right : trello-cli
On Sat, 20 Jan 2024, Tonus wrote: I don't know either how I should manage the symlinks. If someone has a pointer or two... You used "-l n" with makepkg (last line of the script), so the package .tgz contains actual symlinks. The correct thing to do is "-l y", which causes makepkg to generate a doinst.sh which creates the symlinks at package install time. I haven't tried to build this yet so I'm not sure about stripping the binary, or why you're having problems with it. Will get back to you. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Gradle version upgrade
On Fri, 19 Jan 2024, Riza Dindir wrote: I was wondering if it would be ok if I submit that package to slackbuilds.org? Since the maintainer hasn't been active for 3.5 years (last activitiy May 2020), yes, go ahead. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Issues with webkit2gtk / webkit2gtk4.1 in a Slackware 32 bit
On Fri, 12 Jan 2024, B. Watson wrote:
But this actually would have been OK and not resulted in "-j0" on a
single-proc
system:
"${NINJA:=ninja}" -j$(expr $(nproc) / 2 + 1)
That would have done what the author intended: use half the available
cores, or 1 core on a single-core box.
The perils of posting code in an email without testing it. Slight correction:
"${NINJA:=ninja}" -j$(expr \( $(nproc) + 1 \) / 2 )
...works out to -j1 if you have 1, 2, or 3 cores, -j2 if you
have 4 or 5, -j4 if you have 8...
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Issues with webkit2gtk / webkit2gtk4.1 in a Slackware 32 bit
On Fri, 12 Jan 2024, Christoph Willing wrote:
Is this idiom a thing that sbolint could check for and warn about (or fail)?
It could... though, it's complex enough that it might not be all that reliable.
Also consider... The original code was:
"${NINJA:=ninja}" -j$(expr $(nproc) / 2)
But this actually would have been OK and not resulted in "-j0" on a single-proc
system:
"${NINJA:=ninja}" -j$(expr $(nproc) / 2 + 1)
That would have done what the author intended: use half the available
cores, or 1 core on a single-core box.
Possibly sbolint could just warn if it sees -j passed to ninja at all
(not an error, just a "make sure this does what you expect" kind of
thing).
I thought using -j option like this in SBo SlackBuilds was banned (or at
least highly discouraged).
For make, that's true. The only 'approved' use of -j for make is -j1, for
stuff that fails to build with parallelism.
Reading up a bit on ninja... without the -j, its default number of jobs
is based on the number of cores. On mine, with 8 cores, "ninja --help" says:
-j N run N jobs in parallel (0 means infinity) [default=10 on this system]
So there's theoretically no need for a MAKEFLAGS-like setting for ninja.
In practice, for large projects like webkit2gtk, the limiting factor
becomes virtual memory (RAM + swap). If I don't have enough memory to
support 10 jobs, the build fails. Whoever added the -j$(expr $(nproc) / 2)
to webkit2gtk was probably trying to avoid running out of
memory... ninja doesn't have an environment variable to set options
like make does, or else it could have just been a comment in the
README. Sigh.
Personally, I like the idea of having a ninja-using SlackBuild grab
the -jN option from MAKEFLAGS in the environment, to give the user
some control that's otherwise lacking. But I wouldn't try to make that
a requirement for everyone else.
Another idea, we could define our own NINJAFLAGS. Code in the SlackBuild
would be simple:
"${NINJA:=ninja}" $NINJAFLAGS
That could become part of meson.template.
Opinions?
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Issues with webkit2gtk / webkit2gtk4.1 in a Slackware 32 bit
On Thu, 11 Jan 2024, Qun-Ying wrote:
"${NINJA:=ninja}" -j$(expr $(nproc) / 2)
What maniac wrote this? If you run it on a single-core box, nproc says
1, integer-divided by 2... means it runs "ninja -j0". And according to
ninja's --help, -j0 means "infinity". This might be the cause of the
OP's problem.
It'd be better to extract the -j# from MAKEFLAGS (if set) and use that
for ninja's -j option (or, if MAKEFLAGS not set, don't pass ninja a -j
at all, which works the same way as make: 1 job).
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Error when starting grk-pipe-viewer (package pipe-viewer)
On Thu, 11 Jan 2024, Didier Spaier wrote: Attached. Diffed the two... 200d199 < }, Meaning, your gtk-pipe-viewer is old, it doesn't have the corrected restore_mplayer.diff from January 3. It probably is the BUILD=1 version (the updated one is BUILD=2). ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Error when starting grk-pipe-viewer (package pipe-viewer)
On Thu, 11 Jan 2024, Didier Spaier wrote: The issue remains: does not work here (TM) One thing I see you're missing in your list of installed perl packages is libwww-perl. That's pretty important for pipe-viewer... but you might have it installed, you just did a "ls perl-*", and that one doesn't start with "perl". 2 more that are listed in the .sqf: perl-PAR-Dist perl-File-ShareDir-Install Just to be sure, can you gzip your /usr/bin/gtk-pipe-viewer and attach it to an email? It works out to about 30KB compressed, not too much for a mail attachment, and that way I can make sure we're both looking at the same thing. Also... does pipe-viewer (the non-GTK one) work OK for you? ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Error when starting grk-pipe-viewer (package pipe-viewer)
On Thu, 11 Jan 2024, Didier Spaier wrote: I attach the error message and the list of installed perl packages. I don't see the attachment... However, I just updated pipe-viewer on January 3, with a fix for a gtk-pipe-viewer issue. Are you using the latest? That'd be version 0.4.8, BUILD=2. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Using Web Archive links for the sites and downloads that are not available anymore?
On Sun, 7 Jan 2024, Bojan Popovic wrote: I was just trying to see if the original is still available via Internet Archive's "Web Archive" and it is. Should in these cases (when there is an archived version at IA) maybe try and post IA links instead? The last version of the web page that contian XbmBrowser is from 2019: https://web.archive.org/web/20190910064117/http://www.ict.griffith.edu.au/anthony/software/ I'd say yes, use the IA link. It's better to have the DOWNLOAD hosted somewhere besides slackware.uk, if possible, because slackware.uk is also where the SBo source archive is hosted. While you're at it, you could use the IA copy of the site as HOMEPAGE, since the current version of the page doesn't mention xbmbrowser at all. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] relinquishing scripts (e16, e16-themes, fmit, rfk, skulpture)
On Wed, 3 Jan 2024, Josiah Boothby wrote: No objection from me...please do as you will! Many thanks. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] relinquishing scripts (e16, e16-themes, fmit, rfk, skulpture)
On Wed, 3 Jan 2024, Josiah Boothby wrote: audio/fmit For fmit, do you mind if I change the license? I prefer WTFPL for my scripts. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] relinquishing scripts (e16, e16-themes, fmit, rfk, skulpture)
On Wed, 3 Jan 2024, Josiah Boothby wrote: All my scripts are available to new and loving homes! Sad to hear that... audio/fmit I'll take fmit, I was the last one to touch it anyway (version updated it in Feb 2022). ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Tests updating Lazarus to version 3.0
Sorry this got so long & verbose, hopefully it'll be helpful. On Tue, 26 Dec 2023, Antonio Leal via SlackBuilds-users wrote: So doublecmd-qt5 and winff don't build with new Lazarus. Looks like doublecmd development moved from sourceforge to github, see https://github.com/doublecmd/doublecmd/releases Possibly the latest 1.1.x release will build & work with lazarus 3.0? This would be a case where you coordinate with the maintainer. However, he's given his email address as "n...@no.n.ooo" which doesn't look like a real address. Maybe he's subscribed to this mailing list, and will see this thread...? For winff, there's also new releases. What we've got in our repo is a random git commit from September 2022. If you look here: https://github.com/WinFF/winff/tags ...you'll see that there have been several releases since then. Perhaps the latest will work with lazarus 3.0. Here, the SBo maintainer is active and has a real email address, so you should coordinate with him. What is the SlackBuilds policy in this situation? a) Stay with current Lazarus 2.2.6 and hope that all packages will eventually build correctly? Who keeps checking this and how? You're the lazarus maintainer, so you check it... which you have done, and are doing. Also the maintainers of the other builds should check. b) Notify maintainers and upgrade Lazarus to 3.0 anyway? Breaking peoples' builds by updating their dependencies is rude. Notifying them that you're about to do it is slightly less rude, but it's still a hassle: puts pressure on the maintainer to drop whatever else he's doing and fix his build (that wasn't broken until you broke it). Not a good way to treat unpaid volunteers... c) Other? My preferred way of dealing with this situation is, I'd patch the dependees (doublecmd-qt5 and winff), possibly updating them to new versions. Get them working with the new lazarus. Then send the diffs to their builds (and lazarus) to the maintainers for their consideration. If they're OK with your changes, either they can submit the updates, or allow you to do it. If you use github or some other public git repo, you can do it as a fork/branch. If you'd rather, you can just email the diffs (I'd say gzip them first). Since the doublecmd-qt5 maintainer's email address is bogus, I guess you have to mail the diffs to this mailing list too. If you do that, and we don't hear from him within some reasonable amount of time, most likely an SBo admin will step in and update his build. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] I'm back to maintaining SlackBuilds (Merry Christmas everyone!)
On Mon, 25 Dec 2023, Isaac Yu via SlackBuilds-users wrote: - Qtile: I will not be updating qtile. I have a small request for qtile: the README doesn't actually say what the heck it is. "Qtile is simple, small, and extensible. It's easy to write your own layouts, widgets, and built-in commands", but what *is* it? Looks like it's a window manager, maybe the README could say: Qtile is a simple, small, extensible window manager for X and Wayland ...something like that. The slack-desc should also get the same treatment. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Dos line endings in patch file
On Fri, 22 Dec 2023, B. Watson wrote: This is an ongoing issue. The best way we've found to handle it, is to gzip the patch, then use "zcat $CWD/whatever.diff.gz | patch -p1" or similar. For examples, see games/oblige and system/unage. If you're wondering, the problem is caused by git. It tries to "correct" the line endings for whatever system it's running on. Now that I think of it. This might be a good check to add to sbolint. If it finds a *.diff or *.patch file with \r\n or mixed line endings, it could warn you that you should gzip it. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Dos line endings in patch file
On Fri, 22 Dec 2023, Daniel Prosser wrote: I recently updated xflr5 to the latest version. The SlackBuild includes a patch which is supposed to have dos line endings, since the source file also has dos line endings. The patch file I uploaded had dos line endings (and I tested before uploading), but now in the repo, it has unix line endings, This is an ongoing issue. The best way we've found to handle it, is to gzip the patch, then use "zcat $CWD/whatever.diff.gz | patch -p1" or similar. For examples, see games/oblige and system/unage. If you're wondering, the problem is caused by git. It tries to "correct" the line endings for whatever system it's running on. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Dungeon Crawl Stone Soup 0.30.1 game
On Mon, 11 Dec 2023, David Chmelik wrote: When I built and did 'sbolint crawl-0.30.1-x86_64-1_SBo.tgz' it said errors: not a .tar.gz rather than .tgz, and size warning, and "not a SBo- compliant tarball, contains extra junk './'"... sbolint is for the SlackBuild itself, not the package. Try running sbopkglint on the package. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] KDE kuickshow image viewer (testing, needs extra-cmake-modules)
On Mon, 11 Dec 2023, David Chmelik wrote: Still learning sbo-maintainer-tools. Will address these before I formally upload. All below failed tests are about stuff in the source code file itself. Should I fix these in script and/or graphics editor, or contact/ bug-report KDE? Probably both: they're trivial issues... Wrong permissions on a .desktop file can be fixed with a chmod in your script (after the 'make install'). For wrong-sized icons, you can just include correct-sized ones with your build and have your SlackBuild overwrite the ones in $PKG with your own. Or, you can have your script use 'convert' (from ImageMagick) to resize them. And *also* let upstream know, so maybe it'll get fixed there and you can simplify your SlackBuild in the future. Question: Why you're packaging random git commits... usually it's best to stick with releases, unless (a) there are no releases (but, there are, for kuickshow), or (b) the later git code has fixes that are needed to get the app to compile and/or run (or, that fix a major bug). I'm not trying to tell you what to do, just wondering why you did what you did. If you put a comment in your script, explaining the situation, nobody will have to wonder... ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] KDE kuickshow image viewer (testing, needs extra-cmake-modules)
On Mon, 11 Dec 2023, David Chmelik wrote: I have updated the old KDE image viewer (simple/minimalist) kuickshow.SlackBuild for testing. You probably can update kuickshow without having to have a cmake-extras package, if your script manually sets some -D variables on the cmake command line. Also. Have you addressed these issues, found by sbopkglint? Using tests from /home/urchlay/sbo-maintainer-tools/sbopkglint.d Exploding /tmp/kuickshow-20220618_a9c29cc-x86_64-1_SBo.tgz to /tmp/SBo/sbopkglint.JHkxoo ...OK Running pre-doinst test...OK Installing /tmp/kuickshow-20220618_a9c29cc-x86_64-1_SBo.tgz to /tmp/SBo/sbopkglint.JHkxoo ...OK Running test: 05-basic-sanity... --- usr/share/applications should not contain files with executable permission: -rwxr-xr-x 1 root root 4027 Jun 17 2022 usr/share/applications/org.kde.kuickshow.desktop FAILED Running test: 10-docs...OK Running test: 15-noarch...OK Running test: 20-arch...OK Running test: 25-lafiles...OK Running test: 30-manpages...OK Running test: 35-desktop... --- bad permissions/owner on .desktop files (should be 0644 root:root): -rwxr-xr-x 1 root root 4027 Jun 17 2022 usr/share/applications/org.kde.kuickshow.desktop FAILED Running test: 40-newconfig...OK Running test: 45-doinst...OK Running test: 50-icons... --- usr/share/icons/hicolor/32x32/apps/kuickshow.png: icon is 32x29, but is in a dir with 32x32 in the name. resize it, or rename the dir. --- usr/share/icons/hicolor/16x16/apps/kuickshow.png: icon is 16x14, but is in a dir with 16x16 in the name. resize it, or rename the dir. --- usr/share/icons/hicolor/22x22/apps/kuickshow.png: icon is 22x20, but is in a dir with 22x22 in the name. resize it, or rename the dir. OK Running test: 60-usr_info...OK Running test: 65-python...OK Running test: 70-tmp_path...OK Running test: 75-static_libs...OK Running test: 80-fonts...OK Running test: 85-perl...OK !!! kuickshow-20220618_a9c29cc-x86_64-1_SBo.tgz: 2 failures ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] qt5ct (1.8) Doesn't Compile in Slack 15 & DEV Email Not Working
On Fri, 20 Oct 2023, royal.post via SlackBuilds-users wrote: Hello, This SBo doesn't compile in Slack 15; https://slackbuilds.org/repository/15.0/desktop/qt5ct/ It compiles for me, on both x86 and x86_64 Slackware 15.0. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Removing comments from borgbackup
On Thu, 19 Oct 2023, Andrzej Telszewski wrote: I'm about to push a version update to _borgbackup_. While doing that, I would like to remove and/ or reformat comments introduced to the SlackBuild by SBo admins. (introduced when the SlackBuild was update by SBo, and not by me.) Is that OK? Sure. The script has code in it that you didn't write. The comments are there to explain to you why that code was added/changed and what it's for. So long as you understand the code, you don't need the comments. The other answer is: It's your script, so yes you can remove the comments if you want. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] memtest86 vs memtest86+
On Thu, 5 Oct 2023, Rich Shepard wrote: On Thu, 5 Oct 2023, Rich Shepard wrote: Thank you, B. That's excellent advice and I'll follow it. Slight discrepancy between the source file number and the SlackBuild script. The Debian version is 4.6.0-1 while the build script version is 4.6.0_1. I changed the latter to match the filename. There's a reason for the discrepancy: Slackware package version numbers are not allowed to contain hyphens. The - is used as a delimiter by pkgtools. memtester is far from the only build that has this 'issue'. I put it in quotes because it's not a real issue, it's just standard operating procedure for Slackware and SBo. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] memtest86 vs memtest86+
On Thu, 5 Oct 2023, Rich Shepard wrote: Thanks for sharing. When I re-read both SBo pages more carefully I saw that the plus version had instructions for installation on EFI systems so that's what I now have installed. This weekend I'll test both the installed DIMMs and the new ones. You also might want to install memtester. Unlike memtest86 and memtest86+, it runs as a regular Linux process, meaning you don't have to reboot to use it. Its testing can't be as thorough (it can't test the memory that holds the kernel + its modules for instance), but you can use it for a quick check. Maybe even run it weekly from cron, if you're worried about flaky DIMMs. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] *.rej files creeping in to git commits
On Mon, 2 Oct 2023, Erich Ritz wrote: 1) Add a check to sbolint (this is why I've included B. Watson in the email). Easily done. Comments? Good idea? Bad idea? I can't see a reason why anything would ever need rejects from patch as part of its build process. Seems like a good idea to me. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] precompiled "sources" missing libraries
How do we check if a package is really missing some libs? SBo has scripts that just repackage the binaries provided by upstream. Using sbbdep can tell if a package is missing libs in the standard locations. However, many of these precompiled programs ship with their own libs installed in a custom location. Yet, sbbdep will see these as missing. I never used sbbdep, but try setting LD_LIBRARY_PATH=/path/to/libs. E.g. if you have /opt/someprogram/lib: root@host# LD_LIBRARY_PATH=/opt/someprogram/lib sbbdep This probably will work as sbbdep probably just uses ldd to find libs, and ldd respects the LD_LIBRARY_PATH variable. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Intent for python SlackBuilds with SLKCFLAGS and LIBDIRSUFFIX
On Thu, 21 Sep 2023, Vladimir Nikishkin wrote: Those are not useless. Firstly, some python packages build c-based components "behind the scenes", and it is better to pass some CFLAGS to them. Secondly, python packages install things into /usr/lib$LIBDIRSUFFIX/python$PYTHONVERSION/site-packages, and sometimes it does not autodetect LIBDIRSUFFIX correctly. In those cases, sbolint will not complain about them. It only gives the "note" about SLKCFLAGS or LIBDIRSUFFIX if the variable is set but never used. The builds you're talking about, you would definitely use them, so sbolint wouldn't say anything. Also... you are 100% correct, "it is better to pass some CFLAGS to them", but *so many* python builds DON'T pass the flags (even though they get set). sbolint will detect that correctly, that's the whole point of having the checks. Basically the rule is "if they're set, but never used, remind the user of that fact". It's not an error, just a "note, you might have forgotten to do this". Probably what should happen in the template: the ARCH-detection if/then block should stay there, with a comment above it reading something like: # If your build doesn't require SLKCFLAGS or LIBDIRSUFFIX, you can remove # this entire block. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Intent for python SlackBuilds with SLKCFLAGS and LIBDIRSUFFIX
On Wed, 20 Sep 2023, Jeremy Hansen wrote: Since sbolint (from system/sbo-maintainer-tools) is being ran on github PR requests and newer versions of sbolint are catching when SLKCFLAGS and LIBDIRSUFFIX are not being used, are we expected to not include them on the SlackBuilds? If so, should we remove the entire if/then block for the ARCH detection since that's typically all it does? They're not even warnings, they're "notes". They're more useful for other kinds of builds (with compiled C or C++ code), to remind the script author to actually use the flags and lib64. If you know SLKCFLAGS and/or LIBDIRSUFFIX are not going to be used, you can remove the whole if/then block. But nobody's going to force you to remove it, or complain if you don't. Eventually the python template may be changed, but that won't mean your scripts have to change.___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] desktop/arandr info file is missing PRGNAM
On Sun, 17 Sep 2023, Ruben Schuller wrote: Hi List, https://slackbuilds.org/slackbuilds/15.0/desktop/arandr/arandr.info lacks a PRGNAM line. Thanks... fixed on my branch. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Packages Up for Grabs
On Thu, 14 Sep 2023, Bru Barwal via SlackBuilds-users wrote: I'll take development/micro ...and featherpad and bashmount, unless someone else wants either one. I already snagged bashmount... you and Glenn Becker have both asked for featherpad, I guess decide between you who should have it. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Status of Brandon Pribula's builds
On Thu, 14 Sep 2023, glenn_e_becker via SlackBuilds-users wrote: We still need maintainers for these two: office/featherpad desktop/xwallpaper Any takers? I haven't maintained any builds in a long while & would be willing to take these on. Welcome back! Go ahead & submit updates with your name/email, so it doesn't get forgotten about. I only mention this because it's a recurring problem (it's something I've done myself multiple times...) ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Status of Brandon Pribula's builds
OK, I took a few of these... here's what we have: misc/discount - B. Watson desktop/ufetch - B. Watson desktop/bashmount - B. Watson office/anorack - B. Watson graphics/farbfeld - B. Watson misc/dos2unix - K. Eugene Carlson office/leafpad - Franzen development/micro - Bru Barwal system/bitrot - Logan Rathbone Reminder to the new maintainers: please submit an update ASAP, even if all you change is the maintainer and email address in the .info file. We still need maintainers for these two: office/featherpad desktop/xwallpaper Any takers? ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Packages Up for Grabs
On Wed, 13 Sep 2023, Brandon Pribula wrote: Hello, Unfortunately I don't have the time to maintain my slackbuilds. As a result they are all up for grabs. I'll take at least ufetch, maybe one or two more. Do you mind if I change the licenses? I prefer the WTFPL for my SlackBuilds. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] network/urlgrabber needs a maintainer
Ricardo J. Barberis has abandoned his SlackBuilds. It looks like urlgrabber is required by 3 builds: clive (Javier Rojas ) python2-oauth2 (David Somero ) evernote-python (Dimitris Zlatanidis ) Javier, Davis, Dimitris: Would one of you like to take over as maintainer of urlgrabber? ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Had to move off Slackware, so consider all my slackbuilds unmaintained.
On Mon, 28 Aug 2023, Willy Sudiarto Raharjo wrote: earlyoom fuse-archive mount-zip muon tup I'll take these, unless someone else has a burning desire to take them. None of them are dependencies for anything else... ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Pale Moon SlackBuilds many versions behind--no longer updated?
On Thu, 17 Aug 2023, dchme...@gmail.com wrote: Feel free to take over maintainership if the maintainer doesn't respond after some time It's too complicated a build for me to take over, and not in a category if interest, but someone who actually uses it and wants to keep it up-to-date should be maintaining it. You sound like someone who actually uses it, and wants to keep it up-to-date... Don't worry if you think it's too complicated. Unlike writing a new build from scratch, you have a working one to base your work on. It might be as simple as just changing VERSION and the download and md5sum. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] abuse SBo fix for Slackware 15.0
On Sat, 12 Aug 2023, Nick Smallbone wrote: I can take development/zeal. Yours. Please send an update with your name/email in the .info file, so we don't forget. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Orphaning my SlackBuilds
On Thu, 10 Aug 2023, port...@use.startmail.com wrote: When the Build was submitted, it was in a working state. I think I have not tried it with the last release so maybe that's the point where it got broken. In that case, it looks like something about SDL changed, between Slackware 14.2 and 15.0. Fixed now, anyway. Thanks. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] abuse SBo fix for Slackware 15.0
On Mon, 7 Aug 2023, Erich Ritz via SlackBuilds-users wrote: I will take: development/colordiff I just pushed an update for colordiff with a version update, making myself the maintainer. If you want the build, I'll change the maintainer info to yours and re-push. I was only going to take it to keep it from disappearing; if you actually use it, it's better off with you. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Orphaning my SlackBuilds
On Mon, 7 Aug 2023, Erich Ritz via SlackBuilds-users wrote: I've played this a few times in the past and didn't know what you were talking about, so I launched KoboDeluxe and tried to start a game and sure enough it was just stuck in the paused state. Honestly I can't remember the last time I played it. But since 15.0 would be a good guess. Yah, something in SDL changed between 14.2 and 15.0, it looks like. I've fixed it on my git branch. Just pushed it, if you want to have a look on my branch. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Orphaning my SlackBuilds
On Thu, 3 Aug 2023, Rubén Llorente via SlackBuilds-users wrote: games/KoboDeluxe Found a solution for the stuck-in-pause problem, Debian has a patch that fixes it. Now I'm just wondering, how long was this broken for? Since 15.0 came out, or...?___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Orphaning my SlackBuilds
On Thu, 3 Aug 2023, Rubén Llorente via SlackBuilds-users wrote: The list of orphaned builds includes: system/unhide I'll take unhide. Do you mind if I change the license at the top of the script? I prefer the WTFPL for my scripts.___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] UltimateDailyWallpaper bad md5sum
Should be c353157601c8c8e1b5e278a5497119f3, I get f9f12d789259114e81a913f631a903da. Package seems to build OK. You might compare your local download file (if you didn't delete it) against a fresh download, see what changed. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Build in search of a home
On Mon, 17 Jul 2023, Eugen Wissner wrote: I looked into the build script and what is required for the next update and I think I can manage it. Excellent! Do you mind if I push an update this week, to change MAINTAINER and EMAIL to your information? ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] epy - md5 mismatch
On Sat, 15 Jul 2023, Eduardo Sanchez wrote: Hi there, epy md5 sums do not match: Found epy-2023.6.11.tar.gz in /var/cache/sbopkg. Checking MD5SUM: MD5SUM check for epy-2023.6.11.tar.gz ... FAILED! Expected: ca8f734192c12a56e637219c84877f70 Found:95dbaf919c3bc46c10138dd4bd27d648 Besides that, I cannot verify if it's just a misreporting, since the software GitHub page does not list a 2023.6.11 release. OK, I got the URL wrong. If you use this: DOWNLOAD="https://github.com/wustho/epy/archive/v2023.6.11/epy-2023.6.11.tar.gz; ...the md5sum matches and the package will build. You'll see 2023.6.11 listed here: https://github.com/wustho/epy/tags ...though you're right, it's not on the releases page. Sorry about the mess. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] epy - md5 mismatch
On Sat, 15 Jul 2023, Eduardo Sanchez wrote: Hi there, epy md5 sums do not match: Found epy-2023.6.11.tar.gz in /var/cache/sbopkg. Checking MD5SUM: MD5SUM check for epy-2023.6.11.tar.gz ... FAILED! Expected: ca8f734192c12a56e637219c84877f70 Found:95dbaf919c3bc46c10138dd4bd27d648 Besides that, I cannot verify if it's just a misreporting, since the software GitHub page does not list a 2023.6.11 release. Sorry, I somehow managed to screw that one up. Will fix. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Build in search of a home
Does anyone here use kitty, and want to take over maintenance of it? I've just updated kitty-bin to the latest release, but the build-from-source kitty build is still at 0.26.5. I'm unlikely to ever update it, because google-go-lang is just too much of a moving target for me to want to aim at... and because kitty-bin works OK anyway. Furthermore... I just don't like kitty much. I prefer rxvt-unicode, or plain old xterm. Any takers? ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Scripts up for grabs
On Sat, 8 Jul 2023, Willy Sudiarto Raharjo wrote: extundelete Guess I'll take extundelete and too, unless someone else wants them badly. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Scripts up for grabs
On Sat, 8 Jul 2023, Willy Sudiarto Raharjo wrote: Hi all, Markus Reichelt has announced that he has no time maintaining his scripts anymore, so scripts below are up for grabs: dietlibc libowfat I'll take libowfat, it's a dep for my ncp build. And I'll take dietlibc because it's an optional dep for libowfat. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] About ttf-ibm-plex
On Tue, 4 Jul 2023, ABE Shin-ichi wrote: If SBo team approved that I take over ttf-ibm-plex, I will submit the updated ttf-ibm-plex (version 6.3.0) within a couple of days. OK, that works. Go ahead and submit your ttf-ibm-plex update whenever you're ready. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20230617.1
On Mon, 3 Jul 2023, 414N wrote: Il 17/06/23 12:38, Willy Sudiarto Raharjo ha scritto: office/LanguageTool: Updated for version 6.1. Using sbopkg I find a different MD5 than the expected one: Found LanguageTool-6.1.zip in /var/cache/sbopkg. Checking MD5SUM: MD5SUM check for LanguageTool-6.1.zip ... FAILED! Expected: b750011ec97d2fd94e41fc37899844d3 Found:fc4875d72950bb1302379559fc1168c5 I tried re-downloading the source package several times to no avail. Does anyone have the same issue? Yes. I get fc4875d72950bb1302379559fc1168c5 also. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] About ttf-ibm-plex
On Mon, 3 Jul 2023, ABE Shin-ichi wrote: Today, I e-mailed to the maintainer(Lazar Isailovic) of ttf-ibm-plex and told him that I'd like to take over his maintainership of ttf-ibm-plex from now. Then, he kindly approved my recommendation. Can you forward his email to the list, just for the record? ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Builds up for grabs
On Sun, 2 Jul 2023, Kevin Bryant wrote: I'll take castnow. I use it regularly. Yours. Please send an update this week, so this doesn't get forgotten about. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Builds up for grabs
On Mon, 3 Jul 2023, Kenneth Chan wrote: If it's not too late, I'd like to take desktop/variety, please. It's yours. Please send an update with your name and email in the .info file this week. You can also make whatever other changes you see fit, at the same time (or not, if the build is OK). ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] argyllcms owner.
On Sun, 25 Jun 2023, Fernando Lopez wrote: Can you guys change owner to me on argyllcms sbo. It was approved a week ago (or two). thank you. Done, on my branch. Will be merged in the next weekly update.___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] slackrepo fails to build youtube-dl due to URL encoding
On Fri, 23 Jun 2023, Markus Reichelt via SlackBuilds-users wrote: * Didier Spaier wrote: IMHO yt-dlp can replace youtube-dl with more features. A new version has been released yesterday. Ack. I have been happily using it for quite some time. Nothing wrong with having them both in the repo. We have both vlc and mpv, and Slackware has both gcc and clang... ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] slackrepo fails to build youtube-dl due to URL encoding
On Fri, 23 Jun 2023, Didier Spaier wrote: IMHO yt-dlp can replace youtube-dl with more features. A new version has been released yesterday. We already have yt-dlp... and now that you mentioned it's been updated, I've just updated the version on SBo :) ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] slackrepo fails to build youtube-dl due to URL encoding
On Fri, 23 Jun 2023, Erich Ritz via SlackBuilds-users wrote: What's the best way forward? If I remember correctly SBo policy allows for (if not encourages) the use of the "--content-disposition" flag for wget and similarly the "-J" flag for curl. However, these break the filename in this case. Should slackrepo do its own URL decoding when using curl? Should slackrepo use wget for sourceforge and rename the files (stripping off "?viasf=1")? Should SBo discourage URL encoding in filenames? I don't use slackrepo, but from looking at its output, it's not checking for the source file itself: the error comes from tar, when the SlackBuild tries to extract the source. Probably the best solution is to have the SlackBuild handle all the possible filenames the source might be saved as. The '?viasf=1' part could be handled by putting a * at the end (.tar.xz*) ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] so-called terminal image viewers
On Thu, 22 Jun 2023, dchme...@gmail.com wrote: Recent years there have been a few so-called 'terminal image viewers' SlackBuilds uploaded but in these descriptions people are lying through their teeth: when I tried these on pure (non-X) terminals (/dev/tty*) they don't work at all. They were made for X terminals (xterms) or The trouble is, the word 'terminal' is ill-defined and overloaded. When I say "this runs in a terminal", I might mean an X terminal emulator (xterm, urxvt, konsole, etc), or I might mean the Linux console, or I might (unlikely but possible) mean a real piece of hardware like a Wyse or a DEC VT220, plugged into an RS232 port. Or, a piece of software like minicom (also with RS232). Other replies to this thread talk about framebuffer image viewers. I personally wouldn't call those "terminal" image viewers, I'd actually use the word "framebuffer". I agree that the descriptions in the READMEs should be more specific. But aggressively calling people liars isn't likely to win them over to your point of view...___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] OpenCASCADE build issue
On Tue, 20 Jun 2023, Tim Dickson via SlackBuilds-users wrote: Hi all, I'm getting build failure with the error [100%] Linking CXX executable ../../lin64/gcc/bin/DRAWEXE /usr/bin/ld: /usr/lib64/libldb.so.2: undefined reference to `rep_memset_s@SAMBA_4.15.13' What happens if you run this? ldd /usr/lib64/libldb.so.2 I bet you get a 'libreplace-samba4.so => not found' error. If so, try reinstalling samba. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] icon-theme.cache/doinst.sh(template)/sbo-maintainer-tools
On Sun, 18 Jun 2023, Franzen wrote: And why does the slackware-installer then deals with the cache, as there can't be one on a fresh installation, /var/lib/pkgtools/setup/setup.08.gtk-update-icon-cache Look at the comments in that file: # This is needed since XFce adds a few hicolor icons that would # not otherwise be cached. Really, I'm not sure the idea of # caching icons is a good one -- the use of gtk-update-icon-cache # could disappear from future install scripts. ...a bit lower down: if [ -e usr/share/icons/hicolor/icon-theme.cache ]; then # ONLY run this is there's already a cache!!! Not sure if that clarifies anything or further confuses the issue. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] icon-theme.cache/doinst.sh(template)/sbo-maintainer-tools
On Sat, 17 Jun 2023, Franzen via SlackBuilds-users wrote:
Hi all,
the content of a icon-file-cache(icon-theme.cache) like
/usr/share/icons/ICON_DIRECTORY/icon-theme.cache
depends on the tool "gtk-update-icon-cache".
Also all present icon caches like
/usr/share/icons/{ICON_DIRECTORY1,ICON_DIECTORY2}/icon-theme.cache
are regenerated at boot by /etc/rc.d/rc.M.
Almost right. The caches only get regenerated if they already exist.
The code:
if find /usr/share/icons -maxdepth 2 2> /dev/null | grep -q icon-theme.cache ;
then
for theme_dir in /usr/share/icons/* ; do
if [ -r ${theme_dir}/icon-theme.cache ]; then
echo "Updating icon-theme.cache in ${theme_dir}..."
/usr/bin/gtk-update-icon-cache -t -f ${theme_dir} 1> /dev/null 2> /dev/null
&
fi
done
...and, by default, the caches *don't* exist, on a fresh
Slackware install. They only get created if the user manually runs
gtk-update-icon-cache to create them the first time [*].
That's why our doinst.sh has the "if [ -e usr/share/icons/hicolor/icon-theme.cache
];"
[*] We do have some builds which unconditionally create the icon
cache. These are errors, and should be fixed (and will be, this
week). One of them is games/steam, if you want an example. Probably I
will add a check to sbolint for this, too.
So, i think icon-theme.cache in the icon-directory should never be present in
a package.
Correct. sbopkglint already checks for this, in predoinst.sh.
-> sbo-maintainer-tools might check that presence
-> sbo-maintainer-tools might warn if /usr/share/icons/ICON_DIRECTORY/
is present, but doinst.sh does not call gtk-update-icon-cache
It does this, but only for hicolor.
The logic to regenerate the cache if the cache is present does not make sense
to me,
the cache should simply be (re)generated on installation.
Nope, see above.
That said, it seems a lot of builds use the example from doinst.sh with
usr/share/icons/hicolor, which does not make sense at all if there is no icon
in usr/share/icons/hicolor in the package.
Maybe sbo-maintainer-tools should also check for that.
sbopkglint does check this. Again, only for hicolor.
What do you think? Feedback is welcome, thanks!
It might be worthwhile to have it check all icon dirs it finds,
rather than just hicolor. The vast majority of our packages only
install icons in hicolor (exceptions being *-icon-theme packages), so
I haven't worried too much about it...
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] wterm
Does anyone here use wterm? Its maintainer has been inactive for ~5 years (for all of his builds, not just wterm). Upstream hasn't done a release, so we have the latest version of wterm... If you build it, you'll notice it doesn't actually build correctly: the compile fails (but doesn't kill the script) and you end up with a package consisting only of man pages and documentation. It's trivial to fix. But, it's been broken since 15.0 released (about a year and a half now) and nobody's complained. Does anyone want this build? I can update it with my fixes and put your name as maintainer in the .info file. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] unmaintained SlackBuilds
On Tue, 13 Jun 2023, Franzen via SlackBuilds-users wrote: may I assume that Steven King is not maintaining his builds anymore, and that anybody may take these? Since over 6 years no commit. A few months ago a asked him via mail and got no response. Yes, feel free to take them over. This goes for anyone else who wants any of them, too. The full list: libraries/iniparser libraries/log4c network/aiccu network/csync network/dkimproxy network/httping network/mailman network/webalizer python/python2-pydns python/python2-pypolicyd-spf python/python2-pyspf system/newrelic-sysmond ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] libgsasl
On Fri, 9 Jun 2023, spaceman via SlackBuilds-users wrote: libgsasl is out of date (1.8.0 --> 2.2.0) and over 10 years old. Is there any reason for this? Its maintainer abandoned all his slackbuilds a few years ago. libgsasl is up for grabs. I am asking because it is a very optional dependency of mpop. Feel free to take over maintenance, and submit an update. However, before you send us the new version, test the builds that depend on it: https://slackbuilds.org/advsearch.php?stype=revdep=libgsasl An update shouldn't break anything else. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] xmlsec was reverted to 1.2.27
On Wed, 7 Jun 2023, Julian Grinblat wrote: For some reason, in 27504d39f215cb7a8a74b6a7edab9b0fd6768914 xmlsec was reverted to 1.2.27. c5603f5d4cb83f82265772cb8b9f1ee0e521d398 upgraded to 1.3.0, and the changelog lists it as being upgraded to 1.3.0. Just reporting It was reverted to 1.2.37 because oath-toolkit won't build with 1.3.0 (and consequently glewlwyd and pass-otp won't build as they depend on oath-toolkit). The git log message for is incorrect (typo'ed) and should read "Downgraded to 1.2.37" or such. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] sbo-maintainer-tools and .info-files
On Sun, 28 May 2023, Franzen via SlackBuilds-users wrote: While we are here, i had an rejected build because i didn't have a if [ -x /usr/bin/... ]; then in doinst.sh/douninst.sh Maybe sbo-maintainer-tools could also warn if an executed command in doinst.sh has no -x test, That could possibly be added. Though, any parse I write for that, will not be a real shell that parses the full shell syntax... and warn if executed commands don't actually exist. How can it? It has no idea what commands do or do not exist on whatever system you end up installing the package on... it could check if they exist currently on the system it's running on, which (probably 99.9% of the time) is the same one you install it on for real... but requiring all the dependencies for a package to be installed just to lint that package seems kinda onerous. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Building TeXLive 2023
On Sat, 27 May 2023, Franzen via SlackBuilds-users wrote: my submission of texlive-docs 2023 was rejected, the sbo-maintainer said it exits with: ... tar: texmf-dist/doc/bibtex/apalike-ejor: Directory renamed before its status could be extracted tar: texmf-dist/doc/bibtex: Directory renamed before its status could be extracted tar: Exiting with failure status due to previous errors I'm pretty sure I know what happened there: Someone did a "rm -rf /tmp/SBo" while the build was running. That's the only explanation I can come up with for those particular error messages. The build runs fine here, sbolint is happy with it, but sbopkglint complains a bit: Using tests from /home/urchlay/sbo-maintainer-tools/sbopkglint.d Exploding /tmp/texlive-docs-2023.230322-noarch-1_SBo.tgz to /tmp/sbopkglint.84Yqp5 ...OK Running pre-doinst test...OK Installing /tmp/texlive-docs-2023.230322-noarch-1_SBo.tgz to /tmp/sbopkglint.84Yqp5 ...OK Running test: 05-basic-sanity...find: ‘./usr/share/texmf-dist/doc/latex/catechis/lppl.txt’: Too many levels of symbolic links find: ‘./usr/share/texmf-dist/doc/latex/bondgraph/License.txt’: Too many levels of symbolic links find: ‘./usr/share/texmf-dist/doc/latex/crefthe/LICENSE’: Too many levels of symbolic links find: ‘./usr/share/texmf-dist/doc/latex/bussproofs-extra/LICENSE.txt’: Too many levels of symbolic links find: ‘./usr/share/texmf-dist/doc/latex/beamerauxtheme/LICENSE’: Too many levels of symbolic links find: ‘./usr/share/texmf-dist/doc/latex/circledsteps/lppl-1-3c_license.txt’: Too many levels of symbolic links find: ‘./usr/share/texmf-dist/doc/latex/create-theorem/LICENSE’: Too many levels of symbolic links find: ‘./usr/share/texmf-dist/doc/latex/changelog/LICENSE.txt’: Too many levels of symbolic links find: ‘./usr/share/texmf-dist/doc/latex/altsubsup/LICENSE’: Too many levels of symbolic links find: ‘./usr/share/texmf-dist/doc/latex/colophon/lppl.txt’: Too many levels of symbolic links find: ‘./usr/share/texmf-dist/doc/latex/beamer/licenses/lppl-1-3c.txt’: Too many levels of symbolic links find: ‘./usr/share/texmf-dist/doc/latex/basicarith/lppl.txt’: Too many levels of symbolic links find: ‘./usr/share/texmf-dist/doc/latex/autofancyhdr/LICENSE’: Too many levels of symbolic links find: ‘./usr/share/texmf-dist/doc/latex/clrdblpg/lppl.txt’: Too many levels of symbolic links find: ‘./usr/share/texmf-dist/doc/bibtex/apalike-ejor/LICENSE’: Too many levels of symbolic links find: ‘./usr/share/texmf-dist/doc/bibtex/urlbst/LICENCE-lppl.txt’: Too many levels of symbolic links find: ‘./usr/share/texmf-dist/doc/generic/modulus/lppl.txt’: Too many levels of symbolic links find: ‘./usr/share/texmf-dist/doc/generic/texdate/lppl.txt’: Too many levels of symbolic links OK Running test: 10-docs... --- docs outside of usr/doc/texlive-docs-2023.230322: drwxr-xr-x 2 root root 4096 May 27 19:52 usr/doc/texlive-2023.230322 FAILED Running test: 15-noarch...OK Running test: 20-arch...OK Running test: 25-lafiles...OK Running test: 30-manpages...OK Running test: 35-desktop...OK Running test: 40-newconfig...OK Running test: 45-doinst...OK Running test: 50-icons...OK Running test: 60-usr_info...OK Running test: 65-python...OK !!! texlive-docs-2023.230322-noarch-1_SBo.tgz: 1 failures The "too many levels of symbolic links" is due to broken symlinks (though I don't know why it says "too many levels" instead of "file not found"). The other... there's a /usr/doc/texlive-2023.230322/packages.docs.gz file. Does texlive actually use this file at runtime? If not, it ought to be moved to /usr/doc/texlive-docs-2023.230322 instead. If it does use it, I'll add an exception to sbopkglint so it won't complain.___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Building TeXLive 2023
On Sat, 27 May 2023, Franzen via SlackBuilds-users wrote: tar: texmf-dist/doc/bibtex/apalike-ejor: Directory renamed before its status could be extracted tar: texmf-dist/doc/bibtex: Directory renamed before its status could be extracted tar: Exiting with failure status due to previous errors That's a new one on me, never seen that message from tar before. Could please someone on this list build the attached script, and report back if it works or not, I'm about to go to sleep, apparently it's going to take 40 minutes to download the source, so I'll have to get back to you tomorrow. Anyone else who's going to be awake for a while might have a go... ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] sbo-maintainer-tools and .info-files
On Sat, 27 May 2023, Franzen via SlackBuilds-users wrote: Hi, i have build where sbopkglint complaints: --- package has info files, but doinst.sh does not call install-info FAILED There is no info on SBo what the "best practice" is for .info-files in doinst.sh. Maybe put some info in the templates? Yeah, that would be a good idea. Actually there was an example install-info command in the doinst template until recently... https://slackbuilds.org/templates/doinst.sh if [ -x /usr/bin/install-info ]; then /usr/bin/install-info --info-dir=usr/info usr/info/PRGNAM.info.gz 2> /dev/null fi Looks OK to me. The previous template used chroot, and that bit of template got removed last week, but not replaced with anything (yet). The above looks like a good candidate, unless someone else sees something wrong with it? https://slackbuilds.org/templates/douninst.sh if [ -x /usr/bin/install-info ]; then /usr/bin/install-info --remove --info-dir=usr/info usr/info/PRGNAM.info.gz 2> /dev/null fi Won't work. douninst.sh runs after all the files have been removed, and install-info can't remove the info file if it's deleted (it needs the file to find out the human-readable name in the info dir). Or, does this not work for douninst.sh, and needs to be done this way(re-generate /usr/info/dir)? if [ -x /usr/bin/install-info -a -d usr/info ]; then ( cd usr/info rm -f dir for i in *.info*; do /usr/bin/install-info $i dir 2>/dev/null; done ) fi I think that's the right way to do it. I use that in a few of my builds, and it should go in the douninst.sh template. douninst.sh is new enough that we haven't really given it enough thought yet. For instance, anything that installs fonts and calls mkfontscale and/or mkfontfir and/or fc-cache in doinst, should run the commands again in douninst to clean up afterwards. Avoids seeing old unusable entries in lists of fonts in applications (e.g. selecting the font in a terminal, or a word processor). Other candidates would be update-desktop-database, update-icon-cache, glib-compile-schemas. Not being a 'desktop' user (I use Windowmaker, not KDE or XFCE), I'm not sure what happens when a .desktop file or an icon gets removed from the filesystem but is still in the cache. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] non-stripped binaries
On Thu, 25 May 2023, Andrzej Telszewski wrote: On 25/05/2023 06:59, B. Watson wrote: If that doesn't work, leave it unstripped. sbopkglint's supposed to help you, not control you. Maybe `sbopkglint` supports annotation to tell it to treat some code as correct event though it thinks it is incorrect? I've thought about that. "Magic comment" syntax in the SlackBuild (which sbopkglint will find in /usr/doc/$PRGNAM-$VERSION). The trouble is, we don't want it to be overused/abused. If every test can be disabled, inevitably someone will start submitting builds with all the tests disabled, which sorta defeats the purpose of having sbopkglint. But if only a few tests can be disabled, it might work out OK. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
