Re: [Slackbuilds-users] Haruna : before upgrading to 0.10.0
On Tue, 3 Jan 2023, marav wrote: KCrash: Arguments: /usr/bin/haruna /home/marav/Vidéos/Sans.titre.mkv It also crashs here when launched via Dolphin Can someone test it, to see if it's just me or not? It works for me, built using the existing haruna.SlackBuild with VERSION=0.10.0 in the environment. I did this on a 64-bit Slackware 15.0 box with tons of SBo packages installed... and on 32-bit Slackware 15.0 VM with nothing installed except haruna and its dependencies. I even tried naming a file the same as yours, in case the problem was caused by having a unicode character é in the path, but no problem. Does it crash for you with every video, or just that one? Does it crash for you if you run it by itself, with no argument?___ 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] Haruna : before upgrading to 0.10.0
Hi all, I'm facing an issue with the last haruna (0.10.0) So I prefer to share it with you guys before eventually submit the update Here is the error when launched from the command line (relative path for the file is not supported): terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = haruna path = /usr/bin pid = 5882 KCrash: Arguments: /usr/bin/haruna /home/marav/Vidéos/Sans.titre.mkv It also crashs here when launched via Dolphin Can someone test it, to see if it's just me or not? Thanks Cheers ___ 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] BuildScripts up for grabs
On Sat, 31 Dec 2022, Markus Reichelt via SlackBuilds-users wrote: parsley, xzgv, , vanguards, stem, nyx, mksh (all with stale dev.) Can I relicense xzgv and mksh when I take them over? I prefer the WTFPL for SlackBuild scripts, but I won't change your license without permission. ___ 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] BuildScripts up for grabs
On Sat, 31 Dec 2022, Markus Reichelt via SlackBuilds-users wrote: in case anyone likes to take parsley, xzgv, , vanguards, stem, nyx, mksh (all with stale dev.) I'll take xzgv and mksh. ___ 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] cryptography / pyOpenSSL notice
Hi all i just looked at cryptography and pyOpenSSL updates upstream and it seems that we have reached the limit for cryptography and pyOpenSSL releases that can be built on top of Slackware 15.0. Newer cryptography (39.x) dropped support for OpenSSL 1.1.0 and newer pyOpenSSL has raised the minimum version of cryptography into 39.x there are 13 scripts that depends on cryptography (including pyOpenSSL) and 10 scripts that depends on pyOpenSSL currently. -- Willy Sudiarto Raharjo OpenPGP_signature Description: OpenPGP digital signature ___ 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] Qemu 7.2.0
Le 02/01/2023 à 04:01, KB_SBo a écrit : On 1/1/23 18:06, marav wrote: Le 02/01/2023 à 02:49, KB_SBo a écrit : On 12/16/22 13:11, marav wrote: Hi Edward, hi all FYI *libslirp *is now required as an additional dependency to compile qemu 7.2.0 https://wiki.qemu.org/ChangeLog/7.2#Removal_of_the_.22slirp.22_submodule_.28affects_.22-netdev_user.22.29 Cheers Hello All, Actually not true. libslirp is NOT a compile dependency, but optional for user mode networking. Qemu compiles just fine without it. From Qemu ChangeLog/7.2 The "slirp" submodule / code (which is the code behind "-netdev user" / "-nic user") has been removed from the QEMU source tree, so you now need to install your distributions libslirp development package before compiling QEMU to get the user-mode networking feature included again. Since Slackware does not have a "distribution package" (SBo provides this functionality), libslirp is technically OPTIONAL. I should have been a bit more clear in the README and forgot to add the --enable-slirp option as a switch. -Ed Run-time dependency slirpfound: NO(tried pkgconfig) ../meson.build:679:2: ERROR:Dependency "slirp" not found, tried pkgconfig Pretty weird. Doesn't do that here. I'll check again later. -Ed Okay. I got it Because of my modified slackbuild, it fails... Now it builds fine today ___ 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/
