[Slackbuilds-users] nsca-ng - download mirror down?
Hello, there's a problem with http://www.nsca-ng.org/ Maybe https://github.com/weiss/nsca-ng will be a better source? -- Thomas Szteliga ___ 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] jdk 8u181 not available?
W dniu 19/10/2018 o 15:40, Sebastien BALLET pisze: you'll find it in the archive, here : https://www.oracle.com/technetwork/java/javase/downloads/java-archive-javase8-2177648.html Thank you. Downloading this requires now an ORACLE account, OMG! http://download.oracle.com/otn/java/jdk/8u181-b13/96a7b8442fe848ef90c96a2fad6ed6d1/jdk-8u181-linux-x64.tar.gz -- Thomas Szteliga ___ 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] TeamViewer - new version available - checksum mismatch
Hello, there's a new TeamViewer v13.2.26559 available https://www.teamviewer.com/en/download/linux/ teamviewer_amd64.deb and teamviewer_amd64.deb checksums have changed. -- Thomas Szteliga ___ 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] jdk 8u181 not available?
Hello. is there a problem with JDK 8u181, or is it just me? https://www.oracle.com/technetwork/java/javase/downloads/index.html 8u191 and 8u192 are available for download: + http://download.oracle.com/otn-pub/java/jdk/8u191-b12/2787e4a523244c269598db4e85c51e0c/jdk-8u191-linux-x64.tar.gz + http://download.oracle.com/otn-pub/java/jdk/8u192-b12/750e1c8617c5452694857ad95c3ee230/jdk-8u192-linux-x64.tar.gz but I can't find 181 anywhere... -- Thomas Szteliga smime.p7s Description: Kryptograficzna sygnatura S/MIME ___ 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] Strange problem with KeePass 2.39.1
W dniu 30/09/2018 o 12:55, Shrivats pisze: I pushed an update for version 2.40 and included KeePass.config.xml in this update. It's currently in pending queue and you can try it out once it's uploaded. OK, thank you, I will try it :-) -- Thomas Szteliga ___ 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] PHP 7.x
Hello, is there any reason why PHP 7.x (7.0, 7.1, 7.2, 7.3) is not available on Slackbuilds.org? I know about: As a general rule, we do not accept SlackBuild scripts of software that is included as part of Slackware; however, exceptions may be made by the admin staff on a case-by-case basis. <https://slackbuilds.org/guidelines/> There is <https://slackbuilds.org/repository/14.2/python/python3/> with Python 2.7 in the official repo. Would a PHP 7.x slackbuild be accepted by the admin staff? -- Thomas Szteliga smime.p7s Description: Kryptograficzna sygnatura S/MIME ___ 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] signal-desktop - download link not working
Hello, there's a problem with the download url for signal-desktop: https://slackbuilds.org/repository/14.2/network/signal-desktop/ https://updates.signal.org/desktop/apt/pool/main/s/signal-desktop/signal-desktop_1.14.0_amd64.deb returns 404 Not Found. -- Thomas Szteliga ___ 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] Strange problem with KeePass 2.39.1
W dniu 15/06/2018 o 07:52, Shrivats pisze: That may be true only if you download the binary release. But in the SlackBuild, we use the Source release and I don't include KeePass.config.xml in the package at all. There are a couple things you can do as an user, if you don't prefer keeping the config xml globally: * Pass the path to your local configuration file through the command line argument: '-cfg-local:' and override defaults. * Keep your local configuration file in `~/.config/KeePass` I'll think about including this file for global configuration (In the source, it's `true` by default) Hello Shrivats, I did not use another binary, I used the source tarball provided in the .nfo file. I did some digging and now everything is clear, but I guess you'll need to somehow embed the XML in the Slackbuild. I tested this now, normally there is no `/usr/lib/KeePass/Release/KeePass.config.xml` after installation and normal usage, but if a user with write access to `/usr/lib/KeePass/Release/` runs KeePass once (for instance root) then this file is being created there (`/usr/lib/KeePass/Release/KeePass.config.xml`) and it has the problematic PreferUserConfiguration set to false and from this moment on KeePass will ignore all congiguration changes made by other users. Just give it a try and run KeePass as root once and then check if `/usr/lib/KeePass/Release/KeePass.config.xml` and if you're able save any configuration changes as a normal user. -- Best regards Thomas Szteliga ___ 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] Strange problem with KeePass 2.39.1
Hello, I've noticed a strange problem with KeePass. I see now in the description, that's the portable version. https://slackbuilds.org/repository/14.2/misc/KeePass/ This version will not save user settings by default. So it won't remember the last opened file or any settings changed by a user without write permissions in /usr/lib/KeePass/Release/. The problem is caused by `PreferUserConfiguration` which is by default set to false in `/usr/lib/KeePass/Release/KeePass.config.xml` ~~~ ... false ... ~~~ Changing value to true will fix the problem and users will be able to have individual configs. Found this bit related: https://sourceforge.net/p/keepass/discussion/329221/thread/d8c595ac/ -- Best regards Thomas Szteliga ___ 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 `atom` fails
On 2018-06-13 22:46, Thomas Szteliga wrote: building `atom` on Slackware64 14.2 fails at: Package version: 0.8.3 not found child_process.js:624 throw err; ^ The latest stable 1.27.2 fails too: Dumping symbols in /tmp/SBo/atom-1.27.2/out/symbols Running electron-packager on /tmp/SBo/atom-1.27.2/out/app with app name "atom" Downloading electron-v1.7.15-linux-x64.zip [>] 100.0% of 51.2 MB (3.59 MB/s) Packaging app for platform linux x64 using electron v1.7.15 Changing permissions for node files in /tmp/SBo/atom-1.27.2/out/atom-1.27.2-amd64 Copying non-ASAR resources to /tmp/SBo/atom-1.27.2/out/atom-1.27.2-amd64/resources Writing LICENSE.md to /tmp/SBo/atom-1.27.2/out/atom-1.27.2-amd64/resources Application bundle created at /tmp/SBo/atom-1.27.2/out/atom-1.27.2-amd64 Generating snapshot script at "/tmp/SBo/atom-1.27.2/out/startup.js" (1552)Unable to transform source code for module /tmp/SBo/atom-1.27.2/out/app/node_modules/yauzl/index.js. Error: /tmp/SBo/atom-1.27.2/out/app/node_modules/yauzl/index.js Cannot replace with lazy function because the supplied node does not belong to an assignment expression or a variable declaration! at FileRequireTransform.replaceAssignmentOrDeclarationWithLazyFunction (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/lib/file-require-transform.js:180:11) at Context.visitIdentifier (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/lib/file-require-transform.js:72:18) at Context.invokeVisitorMethod (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:344:49) at Visitor.PVp.visitWithoutReset (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:196:32) at visitChildren (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:246:25) at Visitor.PVp.visitWithoutReset (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20) at visitChildren (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:246:25) at Visitor.PVp.visitWithoutReset (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20) at visitChildren (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:246:25) at Visitor.PVp.visitWithoutReset (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20) at NodePath.each (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path.js:101:26) at visitChildren (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:219:18) at Visitor.PVp.visitWithoutReset (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20) at visitChildren (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:246:25) at Visitor.PVp.visitWithoutReset (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20) at visitChildren (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:246:25) at Visitor.PVp.visitWithoutReset (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:204:20) at Visitor.PVp.visit (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:133:29) at Object.visit (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/node_modules/ast-types/lib/path-visitor.js:101:55) at FileRequireTransform.replaceDeferredRequiresWithLazyFunctions (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/lib/file-require-transform.js:68:20) at FileRequireTransform.apply (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/lib/file-require-transform.js:25:10) at /tmp/SBo/atom-1.27.2/script/node_modules/electron-link/lib/generate-snapshot-script.js:55:56 at Generator.next (:null:null) at step (/tmp/SBo/atom-1.27.2/script/node_modules/electron-link/lib/generate-snapshot-script.js:3:191) at /tmp/SBo/atom-1.27.2/script/node_modules/electron-link/lib/generate-snapshot-script.js:3:361 at :null:null ~~~~ -- Best regards Thomas Szteliga ___ 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] Building `atom` fails
Hello, building `atom` on Slackware64 14.2 fails at: apm 1.18.12 npm 3.10.10 node 6.9.5 x64 atom unknown python 2.7.15 git 2.14.4 Installing modules â Installing atom-dark-syntax@0.28.0 â Installing atom-dark-ui@0.53.0 â Installing atom-light-syntax@0.29.0 â Installing atom-light-ui@0.46.0 â Installing base16-tomorrow-dark-theme@1.5.0 â Installing base16-tomorrow-light-theme@1.5.0 â Installing one-dark-ui@1.10.8 â Installing one-light-ui@1.10.8 â Installing one-dark-syntax@1.8.0 â Installing one-light-syntax@1.8.0 â Installing solarized-dark-syntax@1.1.2 â Installing solarized-light-syntax@1.1.2 â Installing about@1.7.8 â Installing archive-view@0.64.1 â Installing autocomplete-atom-api@0.10.5 â Installing autocomplete-css@0.17.4 â Installing autocomplete-html@0.8.3 â Installing autocomplete-plus@2.40.0 â Installing autocomplete-snippets@1.11.2 â Installing autoflow@0.29.0 â Installing autosave@0.24.6 â Installing background-tips@0.27.1 â Installing bookmarks@0.44.4 â Installing bracket-matcher@0.88.0 â Installing command-palette@0.42.0 â Installing dalek@0.2.1 â Installing deprecation-cop@0.56.9 â Installing dev-live-reload@0.47.1 â Installing encoding-selector@0.23.7 â Installing exception-reporting@0.42.0 â Installing find-and-replace@0.215.0 â Installing fuzzy-finder@1.7.3 â Installing github@0.8.3 â Package version: 0.8.3 not found child_process.js:624 throw err; ^ Error: Command failed: /tmp/SBo/atom-1.23.3/apm/node_modules/atom-package-manager/bin/apm --loglevel=error install at checkExecSyncError (child_process.js:601:13) at Object.execFileSync (child_process.js:621:13) at module.exports (/tmp/SBo/atom-1.23.3/script/lib/run-apm-install.js:14:16) at Object. (/tmp/SBo/atom-1.23.3/script/bootstrap:35:1) at Module._compile (module.js:652:30) at Object.Module._extensions..js (module.js:663:10) at Module.load (module.js:565:32) at tryModuleLoad (module.js:505:12) at Function.Module._load (module.js:497:3) at Module.require (module.js:596:17) -- Best regards Thomas Szteliga ___ 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] pcsc-lite - download url not working
Hello, there's a problem with <http://alioth.debian.org/frs/download.php/file/4138/pcsc-lite-1.8.14.tar.bz2> which is unavailable. Maybe https://pcsclite.apdu.fr/files/ will be a better mirror? -- Best regards Thomas Szteliga ___ 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] KeePass-2.38 installed in wrong directory
Hello,
is there a real reason why KeePass-2.38 is being installed
in /usr/lib/KeePass-2.38 and not in /usr/lib/KeePass?
AFAIR few months ago I've submitted a patch and this was corrected,
but now I see KeePass is again installed in /usr/lib/KeePass-${VERSION}.
IMHO this is wrong, because this makes it harder to create packages
for KeePass plugins, like KeePassHttp, every time KeePass gets an update,
the plugin Slackbuilds need to be upgraded too, even if the plugin
was not changed. Plugins are compatible from one version to another,
and they are "recompiled" (by KeePass) at runtime.
I don't see any other program in /usr/lib/ which is installed
to /usr/lib/${PRGNAM}-${VERSION}, all go to /usr/lib/${PRGNAM}.
Can we maybe fix this once and for all? ;-)
https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-August/016939.html
--
Thomas Szteliga
___
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] runc: C source files not allowed when not using cgo: gccgo_c.c
W dniu 25/11/2017 o 21:03, Matteo Bernardini pisze: when you have installed google-go-lang you must log out, relogin again, and only after that build the rest of the dependencies of docker. Hello Matteo, thank you for this tip. Running . /etc/profile.d/go.sh before slpg -s sbo runc solved my problem. BTW, shouldn't this be addressed in the google-go-lang.SlackBuild? -- Thomas Szteliga ___ 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] runc: C source files not allowed when not using cgo: gccgo_c.c
Hello, I'm trying to build docker, but the following error occurs when building runc, which is a docker dependency: ~~ runc-3f2f8b84a77f73d38244dd690525642a72156c64/vendor/golang.org/x/sys/unix/ztypes_openbsd_amd64.go runc-3f2f8b84a77f73d38244dd690525642a72156c64/vendor/golang.org/x/sys/unix/ztypes_solaris_amd64.go go build -i -ldflags "-X main.gitCommit=3f2f8b84a77f73d38244dd690525642a72156c64 -X main.version=1.0.0-rc4+dev " -tags "secc omp" -o runc . build/src/github.com/opencontainers/runc/libcontainer/configs/namespaces_syscall.go:5:8: C source files not allowed when not using cgo: gccgo_c.c Makefile:28: recipe for target 'runc' failed make: *** [runc] Error 1 Total build time for package runc : 1.09 Sec +== | Some error on the package runc-1.0.0_rc4_3f2f8b8 [ FAILED ] +== | See log file in '/var/log/slpkg/sbo/build_logs' directory or read README +== ~~ /var/log/slpkg/sbo/build_logs/build_runc_log ends in: ~~ runc-3f2f8b84a77f73d38244dd690525642a72156c64/vendor/golang.org/x/sys/unix/ztypes_openbsd_amd64.go runc-3f2f8b84a77f73d38244dd690525642a72156c64/vendor/golang.org/x/sys/unix/ztypes_solaris_amd64.go go build -i -ldflags "-X main.gitCommit=3f2f8b84a77f73d38244dd690525642a72156c64 -X main.version=1.0.0-rc4+dev " -tags "seccomp" -o runc . build/src/github.com/opencontainers/runc/libcontainer/configs/namespaces_syscall.go:5:8: C source files not allowed when not using cgo: gccgo_c.c Makefile:28: recipe for target 'runc' failed make: *** [runc] Error 1 ~~ Any idea how to solve this problem? -- Thomas Szteliga smime.p7s Description: Kryptograficzna sygnatura S/MIME ___ 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] perl-Astro-SunTime - source download not found
There's a problem with perl-Astro-SunTime <https://slackbuilds.org/repository/14.2/perl/perl-Astro-SunTime> the source download url returns 404: <http://www.cpan.org/authors/id/R/RO/ROBF/Astro-SunTime-0.01.tar.gz> -- Thomas Szteliga ___ 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] KeePass location reverted
Hello, last year there was a discussion about the location for KeePass: <https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-August/016930.html> and after that I've posted an upgrade, which modified the destination to /usr/lib/KeePass (from /usr/lib/KeePass-$VERSION) so creating SlackBuilds for KeePass plugins would be much easier and wouldn't take an update of each plugin-Slackbuild after each KeePass version update: <https://git.slackbuilds.org/slackbuilds/commit/?id=7bcc6d2c0997d43594d163ff3aa8c6ae983a03f0> But then this happened: <https://git.slackbuilds.org/slackbuilds/commit/?id=5870c8973842c9d13878f1a4fdc1a14587bd5e8e> and KeePass is again in /usr/lib/KeePass-$VERSION And a few weeks after that Willy updated my KeePassHttp plugin: https://git.slackbuilds.org/slackbuilds/commit/?id=bcf6e82ea1f803b3b96bcb52e9d19944ebbd3a7c but only the version :-) the plugin is still installed in /usr/lib/KeePass (as expected). So my question is: can we please have KeePass in /usr/lib/KeePass again? 8-) -- Best regards Thomas Szteliga ___ 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] osinfo-db-tools: wrong MD5SUM / project moved to gitlab
+== | MD5SUM check for osinfo-db-tools-1.1.0.tar.gz [ FAILED ] +== | Expected: 5b346d7e361a7f510aa62da923cbdd8b | Found: a5619251bd9f91b5063d8a0d8a618f71 +== New location: https://gitlab.com/libosinfo/libosinfo Infrastructure/Fedorahosted-retirement: https://fedoraproject.org/wiki/Infrastructure/Fedorahosted-retirement -- Thomas Szteliga ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] owncloud-client dependency missing
On 01/09/2017 05:10 PM, reedych wrote: >> https://nextcloud.com/install/ > wt*... Has slackbuilds.org a client for nextcloud? Not yet. I'll try to prepare slackbuilds this weekend for nextcloud client and server. -- Thomas Szteliga ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] owncloud-client dependency missing
On 01/09/2017 04:56 PM, reedych wrote: > The slackbuild needs "qt5-webkit". Pls fix. BTW: https://owncloud.org/blog/owncloud-statement-concerning-the-formation-of-nextcloud-by-frank-karlitschek/ https://nextcloud.com/install/ -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates in doinst.sh template
On 01/09/2017 03:24 PM, Willy Sudiarto Raharjo wrote: > IMHO, it's easier to see in https://slackbuilds.org/ready/ OK, but just a notice about this requirement to make sure that maintainers are aware, that things like: > I have ran a script to update all remaining doinst.sh in > my branch so maintainer no need to change anything. may occur :-) Otherwise your work may be overwritten... -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates in doinst.sh template
On 01/09/2017 02:29 PM, Willy Sudiarto Raharjo wrote: > I have ran a script to update all remaining doinst.sh in my branch so > maintainer no need to change anything. Just an idea, maybe https://slackbuilds.org/guidelines/ should mention that maintainers should always check their packages in git://slackbuilds.org/slackbuilds.git before submitting upgrades of locally maintained slackbuilds? -- Thomas Szteliga ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir]
On 11/07/2016 12:14 PM, Andrzej Telszewski wrote: > I haven't slept too long and came up with the following idea > (this assumes that we do *somehow* agree on some tags in README): > The following optional, not auto-detected packages enable additional > features (you need to install the package and set environment variable): > [opt] libass, [env] ASS=yes|no [/opt], for ASS support, > [opt] libbluray, [env] BLURAY=yes|no [/opt], for BLURAY support, > [opt] libiec61883, libavc1394, [env] IEC61883=yes|no [/opt], for > IEC61883 support, IMVHO that's way too complicated. My suggestion: OPTIONAL=libass,libbluray,libiec61883,libavc1394 Slackbuilds could simply enable/disable optional deps by checking if the defined package is available in /var/log/packages. -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Suggestion: monospace font for README
On 11/06/2016 09:47 PM, B Watson wrote:
> On 11/6/16, Erik Hanson <e...@slackbuilds.org> wrote:
>> I've made the change. Not sure what I think about it. Instantly I can
>> see some README files are not word wrapped properly:
>> https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/
> Yuck.
> I was about to comment that un-word-wrapped READMEs violate the
> guidelines, but went & looked first... and there's nothing in there
> about word-wrapping or max line length in the README.
> Maybe there should be?
Definitely. Max line length should be mandatory.
> <urchlay@monolith:~/sbogit>$ find . -name README | wc -l
> 6124
> <urchlay@monolith:~/sbogit>$ find . -name README | xargs egrep -l
> '^.{81,}$'|wc -l
> 288
> Affects 5% of the builds. Shouldn't be too much work to fix, I'm willing
> to spend some time on it if you want. In theory, every maintainer should
> fix his own READMEs, but this is a cosmetic-only change, might be OK to
> just do it?
> Some of them are formatted OK, except they have URLs that are too
> long. Not much can be done about that.
That's IMHO why Markdown would be the best solution for README files.
--
Thomas Szteliga
smime.p7s
Description: S/MIME Cryptographic Signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Suggestion: monospace font for README
On 11/06/2016 08:56 PM, Erik Hanson wrote: > I've made the change. Not sure what I think about it. Instantly I can > see some README files are not word wrapped properly: > https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/ > It's probably smart to keep it though: > https://slackbuilds.org/repository/14.2/multimedia/JSampler/ I don't think ACII-art should be supported ;-) But if that's really needed the maintainer of JSampler will be able to achieve this using Markdown. So Markdown +1. -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir]
On 11/06/2016 09:15 PM, David Spencer wrote: > Maybe we should give some thought to making README files nicer to use. > Maybe they should become more like manpages, with less random > description and with standardised headings and layout. Markdown? Markdown is a very good idea. It would also solve the current problem which occurred after enabling the monospaced font: https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/ ;-) -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Error building atom package
On 11/05/2016 04:17 PM, 414N wrote: > Hi everyone, > it’s from some time that I’m not able anymore to build and upgrade my > atom <https://slackbuilds.org/repository/14.2/development/atom/> > installation to any of the newer versions (I’m currently running v1.9.8). > What I get during every build is this: ... > module.js:327 throw err; ^ Error: Cannot find module ... > Anyone has the same issue? I'm on 1.11.2 built few days ago (Oct 30). I had to build twice, because during the first build npm had problems downloading some required modules. I would suggest just try again because your issue looks similar. -- Thomas Szteliga ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Help offer
On 11/06/2016 12:47 PM, David Spencer wrote: > So the outline idea would be > - a submission arrives Will we be able to download submissions from the pending queue? That's a question to SlackBuilds.org maintainers :-) https://slackbuilds.org/pending/ > - our bot checks if it's a simple update, and how many packages > depend on it -- including optional deps ;) slpkg can do this (based on REQUIRES). Short example with virt-manager: # slpkg -t sbo virt-manager --check-deps Resolving dependencies... Done + | Package virt-manager dependencies : + \ +---[ Tree of dependencies ] | +--1: vala is dependency --> gtk-vnc, libosinfo, libvirt-glib, spice-gtk, virt-manager, virt-viewer, vte3 | +--2: celt051 is dependency --> spice, spice-gtk, virt-manager | +--3: pyparsing is dependency --> spice, spice-gtk, virt-manager | +--4: six is dependency --> spice, spice-gtk, virt-manager | +--5: spice-protocol is dependency --> spice, spice-gtk, virt-manager | +--6: spice is dependency --> spice-gtk, virt-manager | +--7: yajl is dependency --> libvirt, libvirt-glib, libvirt-python, virt-manager | +--8: urlgrabber is dependency --> libvirt, libvirt-glib, libvirt-python, virt-manager | +--9: libvirt is dependency --> libvirt-glib, libvirt-python, virt-manager | +--10: libosinfo is dependency --> virt-manager | +--11: libvirt-glib is dependency --> virt-manager | +--12: libvirt-python is dependency --> virt-manager | +--13: gnome-python2-gconf is dependency --> virt-manager | +--14: tunctl is dependency --> virt-manager | +--15: ipaddr-py is dependency --> virt-manager | +--16: python-urllib3 is dependency --> virt-manager | +--17: python-requests is dependency --> virt-manager | +--18: gtk-vnc is dependency --> virt-manager, virt-viewer | +--19: spice-gtk is dependency --> virt-manager | +--20: vte3 is dependency --> virt-manager > - if it's a simple update, and the total expected build time > (including depending packages) is less than a threshold, throw all > those builds and rebuilds at the automatic build queue (I already have > a database of build times) > - if possible, do builds with multiple build tools (sbopkg sbotools > slackrepo) because diverse tests catch more problems And don't forget about slpkg: https://github.com/dslackw/slpkg > - do some automated tests on the final package (e.g. Heinz's lintpkg) https://github.com/pprkut/lintpkg -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir]
On 11/05/2016 09:20 PM, Andrzej Telszewski wrote: > On 05/11/16 20:59, King Beowulf wrote: >> to sift and test all OPTIONAL >> deps. > No, no, no. > You're confusing what OPTIONAL is about. > It's about replicating *THE SAME INFORMATION THAT YOU PUT IN THE README* > into the .info file, so *MACHINES* can understand it. > You are not going to test it more than you do already. > Let's finally understand that. Exactly. What really needs to be discussed is the acceptable format of the OPTIONAL field. Implementation by the backend of SlackBuilds.org and package building tools (sbopkg/sbotools/slpkg) is another subject which is not important now, because we should let the maintainers of these tools (and Slackbuilds.org) decide if they implement this field or not. In the worst case, if we agree how the format of OPTIONAL should look, we don't have to put this field in *.nfo, we can put it in the README or README.slackware or even create a dedicated SaaS returning the OPTIONAL value for each package via SOAP API call ;-) -- Thomas Szteliga ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Best place to install the EasyRSA scripts?
On 11/05/2016 01:56 AM, Rob McGee wrote: > At least 3 problems I see with that as it implies: > 1. that you have your CA on an openvpn server or client; > 2. that you will be running these scripts as root; > 3. that your CA is limited to use for openvpn. > #1 is the big one, because that promotes insecure user practices; > Slackbuilds.org MUST NOT do that. I'm aware. I have a separated isolated VM just for generating CA's, keys and testing configs for multiple servers/clients. > Admittedly I have never been in the position of having to support > multiple servers, but I'd still only maintain a single CA for all of > them in any given organization. If you need to restrict access on > any given server, use a --client-config-dir and --ccd-exclusive > (touch a file in the CCD for any permitted client's commonName on > that server instance.) I have individual CA's for each server, even when in a single organization and of course if clients of a single server need individual settings ccd's are used. > Hehe, actually I don't have any strong feelings against this > suggestion. It's as good as any. I think /usr/doc/easy-rsa is way better than /usr/doc/easy-rsa- /usr/libexec somehow feels really wrong. CentOS: /usr/share/easy-rsa/ Archlinux: /etc/easy-rsa FreeBSD: /usr/local/share/easy-rsa >> and users will have to copy the contents of /usr/share/easyrsa >> to a writable location like /etc/openvpn/server/server1/easyrsa > Eeek! How about /home/ca/ ? Oh no, really, a user for each CA? ;-) And just another fun-fact ;-) If you are using Linux, BSD, or a unix-like OS, open a shell and cd to the easy-rsa subdirectory. If you installed OpenVPN from an RPM or DEB file, the easy-rsa directory can usually be found in /usr/share/doc/packages/openvpn or /usr/share/doc/openvpn (it's best to copy this directory to another location such as /etc/openvpn, before any edits, so that future OpenVPN package upgrades won't overwrite your modifications). If you installed from a .tar.gz file, the easy-rsa directory will be in the top level directory of the expanded source tree. Again: "it's best to copy this directory to another location such as /etc/openvpn" :- It's from the official howto: https://openvpn.net/index.php/open-source/documentation/howto.html -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Best place to install the EasyRSA scripts?
On 11/04/2016 12:02 PM, Sebastian Arcus wrote: > I am making the SBo scripts for EasyRSA, and I need to decide where they > will be installed. Before they were removed from Slackware - when they > were part of Openvpn, I think they used to go under > /usr/share/doc/openvpn. However, it seems a bit strange to install a > package in the directory of another package. Maybe > /usr/share/doc/easyrsa instead? However, they are sample scripts - not > really documentation. According to Linux filesystem standards, would > there be a better place? Maybe /usr/share directly, or /us/lib or > something? It was very handy to have them in /etc/openvpn/... EasyRSA scripts will create keys in the `keys` subdir, so /usr/share and /usr/doc are probably not the best location without patching KEY_DIR in easyrsa/*/vars to point to a more reasonable location export KEY_DIR="$EASY_RSA/keys" But this still should not be an absolute path, because when you're running multiple openvpn servers you would normally have something like: /etc/openvpn/server/server1/easyrsa/*/keys /etc/openvpn/server/server2/easyrsa/*/keys /etc/openvpn/server/server3/easyrsa/*/keys and a patched KEY_DIR would place all keys by default in one directory. That's not what you want (with multiple servers). So after rethinking this my suggestion is: /usr/share/easyrsa without patching KEY_DIR (keys placed in subdir) and users will have to copy the contents of /usr/share/easyrsa to a writable location like /etc/openvpn/server/server1/easyrsa -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Shouldn't KeePass (mono apps in general) be ARCH=noarch?
On 10/29/2016 08:37 PM, B Watson wrote: > On 10/29/16, Thomas Szteliga <t...@websafe.pl> wrote: >> Now I'm thinking that KeePass itself should be noarch too... >> Am I right? It's a pure mono application (binary). > If there are no native (ELF) binaries, the only other thing to watch > out for is LIBDIRSUFFIX. If it installs stuff in /usr/lib on 32-bit and > /usr/lib64 on 64-bit, you'll want to get rid of that (/usr/share/$PRGNAM > is probably better). I think this /usr/share/$PRGNAM in this case is much better than /usr/lib/$PRGNAM. I've seen this on Arch Linux. Fedora ships KeePass with defined ARCH and in /usr/lib (also the x86_64 pkg) but I see there's another thing, the Slackware pkg is coming with KeePassLibC32.dll and KeePassLibC64.dll and ShInstUtil.exe, which are probably not needed (not found in fedora's rpm). I'll check this before posting a noarch Slackbuild. > The test is whether the same binary package runs correctly on either > 32-bit or 64-bit. > Example: a lot of Perl packages install only perl code, nothing native, > but the install path is different (lib vs. lib64) so they can't use > noarch. All KeePass files (except icons) land in /usr/lib/KeePass/ on both - x86 and x86_64. > ...and, you have just made me realize that the 'domination' build I just > submitted should be noarch also (it's pure Java). :-) -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Shouldn't KeePass (mono apps in general) be ARCH=noarch?
Hello, lately I posted an update for KeePass https://slackbuilds.org/repository/14.2/misc/KeePass/ and now I'm creating a SlackBuild for KeePassHttp, which is a plugin for KeePass and this plugin is a pure plgx file, (no compilation needed) so the Slackbuild will contain ARCH=noarch. Now I'm thinking that KeePass itself should be noarch too... Am I right? It's a pure mono application (binary). https://slackbuilds.org/slackbuilds/14.2/misc/KeePass/KeePass.SlackBuild Just let me know and I'll post an updated Slackbuild. -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] qemu/spice-gtk and usbredir
On 10/23/2016 03:08 AM, King Beowulf wrote: > Some of you will just have to do some real work on your own. > For example, MOST of the slackbuilds I pull from SBo for my use are > customized. Perhaps I need a non-default function, or to drop a > function/dependency I can live without. I'm not going force the > maintainers toward my use case. > My LQ HOW-TO for Boinc-7.6.33 is a good example of this. Does anyone > REALLY want wxGTK3 to have a hard requirement for webkitgtk? I just wanted to talk about an ~OPTIONAL tag in *.nfo for better organized optional dependencies than checking each time the README. I'm not trying to force anyone, just wanted to discuss this. Something like CONFLICTS in *.nfo could be a good thing too, or not? https://slackbuilds.org/repository/14.2/network/postfix/ https://slackbuilds.org/repository/14.2/network/exim/ https://slackbuilds.org/repository/14.2/network/opensmtpd/ CONFLICTS: sendmail 8-) -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] qemu/spice-gtk and usbredir
Just a short review: http://www.rpm.org/wiki/PackagerDocs/BooleanDependencies "Requires, Recommends, Suggests, Supplements, Enhances, Conflicts" Weak dependencies In addition to the strong dependencies created by Requires, there are 4 dependencies that are completely ignored by rpm itself. Their purpose is to be used by dependency solvers to make choices about what packages to install. They come in two levels of strength: + Weak: By default the dependency solver shall attempt to process the dependency as though it were strong. If this is results in an error then they should be ignored and not trigger an error or warning. + Very weak: By default the dependency solver shall ignore them. But they may be used to show the matching packages as option to the user. The depsolver may offer to treat the weak like very weak relations or the other way round. In addition to normal, forward relations that behave the same way as Requires: there are also two weak dependencies that work backward. Instead of adding packages that match the relations of to-be-installed packages these Relations add packages that contain relations matching to-be-installed packages. More here: http://www.rpm.org/wiki/PackagerDocs/Dependencies -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] qemu/spice-gtk and usbredir
On 10/23/2016 01:56 AM, Christoph Willing wrote: > Who is going to decide REQUIRED vs OPTIONAL for the many (I suspect) non > obvious cases? Presumably the maintainer. If a maintainer's balance of > REQUIRED/OPTIONAL deps doesn't suit someone else's particular > needs/wants, then the builder will have to change their personal .info > files anyway (or complain to the maintainer). Hmm, I guess the source developer decides what is really required and what is optional, and the slackbuild maintainer decides which optional (for the developer) dependencies should be treated as REQUIRED by the distribution... -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] qemu/spice-gtk and usbredir
On 10/22/2016 07:28 PM, Andrzej Telszewski wrote: > Something that is not required, shouldn't be flagged as required as long > as it makes sense. > But your proposal to forcibly disable building against usbredir is viable. > If it solves your problem, then ask the maintainer to add it. > You can never have too few options ;-) OK, before I ask I wanted to discuss this. And yes, You're right: "Something that is not required, shouldn't be flagged as required" so maybe it's time to rethink the way OPTIONAL dependencies are announced? The README is OK, but it requires with every new release to re-read all READMEs and check, if any optional deps were added. It would be much easier to have an "OPTIONAL" tag in addition to "REQUIRES" in the *.nfo files. Don't you think? >> Before 14.1 usbredir was optional, because the official libusb >> was too old, that's not the case anymore. > No, it was optional, because it was optional ;-) ;-) -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] qemu/spice-gtk and usbredir
On 10/22/2016 09:39 AM, King Beowulf wrote: > qemu README already mentions spice and usbredir as optional > dependencies. spice-gtk README also mentions usbredir as an optional > dependency. Perhaps a more precise wording can ovoid confusion. > I suggest that the OP should assume that an optional dependency is > expected to be present at COMPILE-TIME unless otherwise specified. > Or the OP can just read the qemu/virt documentation. I'm aware. I can read, really ;-) But automated build tools won't know. And this causes, that the build order matters. We're no longer able to build qemu without usbredir when usbredir is somehow already present, because there's no way to pass --disable-usbredir to the qemu.Slackbuild. And what I'm really trying to say here is, that qemu without usbredir is missing an important feature and qemu without usbredir will make the virt-manager viewer unusable. So maybe usbredir should be considered as REQUIRED or at least there should be a switch for qemu.Slackbuild available, which would stop the build if usbredir is missing, so we have more control, or a switch allowing us to pass --disable-usbredir if we're building on a system, where usbredir is already installed. Before 14.1 usbredir was optional, because the official libusb was too old, that's not the case anymore. -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] qemu/spice-gtk and usbredir
On 10/20/2016 01:23 AM, King Beowulf wrote: > Usbredir is not a "hard" dependency that prevents qemu from compiling. > Rather, it is an optional dependency to add functionality. This is > mentioned in the README. I'm aware, but without usbredir virt-manager becomes kind of unusable. I remember on 14.1 usbredir was optional because the official libusb was too old, but since 14.2 that's not the case anymore... And in the current state the same slackbuild script will create two different binaries depending on the installed packages. And we're not able to build QEMU without usbredir support on a system with usbredir installed (no slackbuild switches / automatically enabled if found)... Maybe the *.nfo files should be extended by listing optional dependencies, so we could handle these an automated way? Another subject are dependencies required only during build-time vss dependencies required at runtime. I'm just thinking out loud ;-) -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] qemu/spice-gtk and usbredir
Hello, shouldn't usbredir be listed in REQUIRES of QEMU and spice-gtk? Because when QEMU is compiled without usbredir present (autodetected during compilation) virt-install usage will be problematic or even impossible. This won't work without usbredir: # virt-install \ --connect qemu:///system \ --name guest1 \ --cdrom /srv/storage/iso/CentOS-7-x86_64-Minimal-1511.iso \ --memory 1024 \ --disk none ERROR unsupported configuration: USB redirection is not supported by this version of QEMU Domain installation does not appear to have been successful. and will work when QEMU was compiled with usbredir present: # virt-install \ --connect qemu:///system \ --name guest1 \ --cdrom /srv/storage/iso/CentOS-7-x86_64-Minimal-1511.iso \ --memory 1024 \ --disk none Starting install... Creating domain... Same goes for spice-gtk. When spice-gtk is compiled without usbredir present then View Manager in virt-manager won't be able to connect to a VM's screen. -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Fixed and updated KeePass
Hello, + Upgraded to 2.34 + Fixed icons source path + Fixed installation prefix to /usr/lib/KeePass (removed version) as discussed here: https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-August/016930.html + Fixed SlackBuild to match new template (586) + Fixed final location of License.txt and KeePass.chm to /usr/doc/KeePass-2.34 Details: https://github.com/websafe/slackbuilds/commits/master/KeePass -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] SBo HowTo - Other Resources - SlackWiki.com down?
Hello, https://slackbuilds.org/howto/ refers to SlackWiki.com but the site is down? Is this a temporary problem? -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] apsw for 14.1 - wrong DOWNLOAD url
Of course this is not a critical issue and I'm able to handle it, I just wanted to let you know. -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] apsw for 14.1 - wrong DOWNLOAD url
TUS_DEFERRED_FKS),
^
src/apsw.c:1365:24: note: in definition of macro ‘ADDINT’
#define ADDINT(n) {#n, n}
^
src/apsw.c:1653:14: error: ‘SQLITE_IOCAP_IMMUTABLE’ undeclared (first
use in thi
s function)
ADDINT(SQLITE_IOCAP_IMMUTABLE),
^
src/apsw.c:1365:24: note: in definition of macro ‘ADDINT’
#define ADDINT(n) {#n, n}
^
src/apsw.c:1666:14: error: ‘SQLITE_CHECKPOINT_TRUNCATE’ undeclared
(first use in
this function)
ADDINT(SQLITE_CHECKPOINT_TRUNCATE),
^
src/apsw.c:1365:24: note: in definition of macro ‘ADDINT’
#define ADDINT(n) {#n, n}
^
src/apsw.c:1684:14: error: ‘SQLITE_FCNTL_TRACE’ undeclared (first use in
this fu
nction)
ADDINT(SQLITE_FCNTL_TRACE),
^
src/apsw.c:1365:24: note: in definition of macro ‘ADDINT’
#define ADDINT(n) {#n, n}
^
src/apsw.c:1685:14: error: ‘SQLITE_FCNTL_COMMIT_PHASETWO’ undeclared
(first use
in this function)
ADDINT(SQLITE_FCNTL_COMMIT_PHASETWO),
^
src/apsw.c:1365:24: note: in definition of macro ‘ADDINT’
#define ADDINT(n) {#n, n}
^
src/apsw.c:1686:14: error: ‘SQLITE_FCNTL_HAS_MOVED’ undeclared (first
use in thi
s function)
ADDINT(SQLITE_FCNTL_HAS_MOVED),
^
src/apsw.c:1365:24: note: in definition of macro ‘ADDINT’
#define ADDINT(n) {#n, n}
^
src/apsw.c:1687:14: error: ‘SQLITE_FCNTL_SYNC’ undeclared (first use in
this fun
ction)
ADDINT(SQLITE_FCNTL_SYNC),
^
src/apsw.c:1365:24: note: in definition of macro ‘ADDINT’
#define ADDINT(n) {#n, n}
^
src/apsw.c:1688:14: error: ‘SQLITE_FCNTL_WIN32_SET_HANDLE’ undeclared
(first use
in this function)
ADDINT(SQLITE_FCNTL_WIN32_SET_HANDLE),
^
src/apsw.c:1365:24: note: in definition of macro ‘ADDINT’
#define ADDINT(n) {#n, n}
^
src/apsw.c:1689:14: error: ‘SQLITE_FCNTL_LAST_ERRNO’ undeclared (first
use in th
is function)
ADDINT(SQLITE_FCNTL_LAST_ERRNO),
^
src/apsw.c:1365:24: note: in definition of macro ‘ADDINT’
#define ADDINT(n) {#n, n}
^
src/apsw.c:1690:14: error: ‘SQLITE_FCNTL_WAL_BLOCK’ undeclared (first
use in thi
s function)
ADDINT(SQLITE_FCNTL_WAL_BLOCK),
^
src/apsw.c:1365:24: note: in definition of macro ‘ADDINT’
#define ADDINT(n) {#n, n}
^
src/apsw.c:1691:14: error: ‘SQLITE_FCNTL_GET_LOCKPROXYFILE’ undeclared
(first us
e in this function)
ADDINT(SQLITE_FCNTL_GET_LOCKPROXYFILE),
^
src/apsw.c:1365:24: note: in definition of macro ‘ADDINT’
#define ADDINT(n) {#n, n}
^
src/apsw.c:1692:14: error: ‘SQLITE_FCNTL_SET_LOCKPROXYFILE’ undeclared
(first us
e in this function)
ADDINT(SQLITE_FCNTL_SET_LOCKPROXYFILE),
^
src/apsw.c:1365:24: note: in definition of macro ‘ADDINT’
#define ADDINT(n) {#n, n}
^
src/apsw.c:1693:14: error: ‘SQLITE_FCNTL_RBU’ undeclared (first use in
this func
tion)
ADDINT(SQLITE_FCNTL_RBU),
^
src/apsw.c:1365:24: note: in definition of macro ‘ADDINT’
#define ADDINT(n) {#n, n}
^
src/apsw.c:1694:14: error: ‘SQLITE_FCNTL_ZIPVFS’ undeclared (first use
in this f
unction)
ADDINT(SQLITE_FCNTL_ZIPVFS),
^
src/apsw.c:1365:24: note: in definition of macro ‘ADDINT’
#define ADDINT(n) {#n, n}
^
src/apsw.c:1695:14: error: ‘SQLITE_FCNTL_JOURNAL_POINTER’ undeclared
(first use
in this function)
ADDINT(SQLITE_FCNTL_JOURNAL_POINTER),
^
src/apsw.c:1365:24: note: in definition of macro ‘ADDINT’
#define ADDINT(n) {#n, n}
^
src/apsw.c:1696:14: error: ‘SQLITE_FCNTL_VFS_POINTER’ undeclared (first
use in t
his function)
ADDINT(SQLITE_FCNTL_VFS_POINTER),
^
src/apsw.c:1365:24: note: in definition of macro ‘ADDINT’
#define ADDINT(n) {#n, n}
^
src/apsw.c:1719:14: error: ‘SQLITE_INDEX_SCAN_UNIQUE’ undeclared (first
use in t
his function)
ADDINT(SQLITE_INDEX_SCAN_UNIQUE),
^
src/apsw.c:1365:24: note: in definition of macro ‘ADDINT’
#define ADDINT(n) {#n, n}
^
error: command 'gcc' failed with exit status 1
--
Thomas Szteliga
smime.p7s
Description: S/MIME Cryptographic Signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] apsw for 14.1 - wrong DOWNLOAD url
Hello,
there is a problem with apsw.SlackBuild for Slackware 14.1
https://slackbuilds.org/repository/14.1/python/apsw/
The new correct DOWNLOAD url is:
https://github.com/rogerbinns/apsw/archive/3.7.17-r1.zip
apsw.SlackBuild will require a small update too,
because it's looking for:
unzip $CWD/$PRGNAM-${VERSION/_/-}.zip
--
Thomas Szteliga
smime.p7s
Description: S/MIME Cryptographic Signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] KeePass.SlackBuild
On 28.08.2016 00:53, Doogster wrote: I would have suggested adding a KEEPASS_VERSION option to the plugin's SlackBuild. OK, but I don't see how this would solve the problem? Short example: Keepass v.2.30 Plugin: KeePassHttp v. 1.8.4.1 How would you name the compiled plugin package and not make tools like slackpkg/slpkg to go crazy when upgrading? As I mentioned in my previous post, other distributions have "normal" locations, like: Centos: /usr/lib/keepass Arch: /usr/share/keepass Ubuntu: /usr/lib/keepass2 -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] KeePass.SlackBuild
On 27.08.2016 09:39, B Watson wrote:
On 8/26/16, Thomas Szteliga <t...@websafe.pl> wrote:
they should be placed in:
/usr/lib/KeePass-${VERSION}/
And we can't really determine the version of Keepass
a user has installed in an extension SlackBuild, can we?
Never used KeePass, but to play the devil's advocate...
Why not? There's surely a way for a shell script to determine the version
number. Maybe by running 'KeePass --version' or similar, or maybe even
by just looking for the existence of /usr/lib/KeePass-* and using cut
or whatever to get the version number. Not saying that's a great idea,
but it's at least possible...
Sure, in a SlackBuild that's possible, but in a packaged binary
not really. I'm not saying that's not possible, but how should
we then name the plugin packages?
keepasshttp-for-keepass-2.30 ?
and what about automated upgrades? This is why I think that's
not the best way.
Whether or not that's a good idea partly depends on whether compiled
plugins are compatible from one KeePass version to another. If they are,
then your idea sounds like the best answer. If they aren't, then the
user's going to have to upgrade every plugin after upgrading KeePass
anyway, and if it's like e.g. perl or older versions of irssi, trying
to load an old/incompatible compiled module might cause the whole thing
to segfault...
Not being a KeePass user I can't answer that (looks like KeePass
is written in C# and built with mono, so I don't know enough to even
guess), but it's something you might want to investigate before making
any final decisions.
Plugins for Keepass2 should be compatible with all 2.x versions.
Plugins don't need to be compiled, they come mostly in the form
of a plgx file:
"PLGX is an optional plugin file format for KeePass ≥ 2.09. Instead of
compiling your plugin to a DLL assembly, the plugin source code files
can be packed into a PLGX file and KeePass will compile the plugin
itself when loading it. The advantage of this approach is that plugins
don't need to be recompiled by the plugin developers for each KeePass
release anymore (as KeePass compiles the plugin itself, the generated
plugin assembly references the current, correct KeePass assembly).
Instead of shipping a plugin DLL assembly, you ship the PLGX."
<http://keepass.info/help/v2_dev/plg_index.html>
Plugin example: https://github.com/pfn/keepasshttp
In the readme for keepasshttp you can find:
"Non-Windows / Manual Windows installation
1. Download KeePassHttp
2. Copy it into the KeePass directory
+ default directory in Ubuntu14.04: /usr/lib/keepass2/
+ default directory in Arch: /usr/share/keepass"
--
Thomas Szteliga
smime.p7s
Description: S/MIME Cryptographic Signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] KeePass.SlackBuild
Hello.
The current KeePass.SlackBuild
<https://slackbuilds.org/repository/14.2/misc/KeePass/>
makes it impossible to create SlackBuilds for KeePass plugins
and extensions <http://keepass.info/plugins.html>, because
they should be placed in:
/usr/lib/KeePass-${VERSION}/
And we can't really determine the version of Keepass
a user has installed in an extension SlackBuild, can we?
I think going this way would not really make sense.
My suggestion is to install KeePass in
/usr/lib/KeePass/
or just symlink /usr/lib/KeePass to /usr/lib/KeePass-${VERSION}
in doinst.sh.
This would make the creation of extension/plugin SlackBuilds
easier, or better - possible.
--
Thomas Szteliga
smime.p7s
Description: S/MIME Cryptographic Signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] php-pgsql appears not to be working
On 14.08.2016 02:58, Willy Sudiarto Raharjo wrote: Based on the message, it seems to be a syntax error? Yes, that's strange, because adodb has no file named adodb-postgresql.inc.php https://github.com/ADOdb/ADOdb/tree/master/drivers/ -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] php-pgsql appears not to be working
On 14.08.2016 01:47, Rich Shepard wrote: I downloaded, built, and installed php-pgsql for php-5.6.24, yet still cannot connect to the database as I try to install an application. Firefox shows me this error: Syntax error in file: /opt/xrms/include/adodb/drivers/adodb-postgresql.inc.php ADONewConnection: Unable to load database driver Can someone point me to what I've missed doing? Have you done the following: > To enable the pgsql extension for php, go to /etc/php.d/pgsql.ini > and uncomment the line: > ; extension=pgsql.so https://slackbuilds.org/slackbuilds/14.2/libraries/php-pgsql/README Apache restarted? Sometimes, when adding extensions, you'll need to stop apache and then start. If stoppping and starting apache wont help, please show the result of phpinfo(); -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Comments required for iperf3 submission
On 11.08.2016 16:42, Willy Sudiarto Raharjo wrote: I use iperf3 from time to time and find it very useful. I noticed that SBo only has iperf2 - and would like to submit scripts for iperf3. Is there much interest in this, and also, is there any reason why SBo shouldn't have iperf3? the maintainer is no longer active i guess his last update was 6 years ago i think you can take over this package and update it to iperf3 I would not update it to iperf3 but create a separate iperf3 SlackBuild, because there are iperf2 and iperf3 clients out there, and v2 is not compatible with v3. https://iperf.fr/iperf-download.php Not every platform has iperf3 available and both v2 and v3 are AFAIK still under development, so I think it would be good to have both available. Just a thought. -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] makeself - missing symlink
Hello, I'm trying to build veracrypt, and veracrypt requires makeself <https://slackbuilds.org/repository/14.1/system/makeself> but even after installing makeself the build script of veracrypt fails, because it's referring to it as makeself, not `makeself.sh`, so maybe updating the makeself.SlackBuild with something like (cd /usr/bin && ln -s makeself.sh makeself) would be a good idea? Other distributions have `makeself` available: https://pkgs.org/centos-7/epel-x86_64/makeself-2.2.0-3.el7.noarch.rpm.html https://packages.debian.org/jessie/all/makeself/filelist http://manpages.ubuntu.com/manpages/trusty/man1/makeself.1.html -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Problem building truecrypt
On 05.06.2016 06:50, Willy Sudiarto Raharjo wrote: wxPython = wxGTK + Python Bindings so you basically can use wxGTK or wxPython to build truecrypt the problem is that you probably install wxGTK3 later and this package overwrite wx-config that is used by other applications that depends on wxGTK/wxPython to check it's existence. You can solve it by reinstalling wxGTK or wxPython as mentioned in the README. Thank you for this explanation :-) -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] TrueCrypt
On 06/05/2016 05:50 AM, Ed Ender wrote: > TrueCrypt is actually outdated, vulnerable and unmaintained. > You might be better off using VeraCrypt, it will also handle the old > TrueCrypt containers. Eric has it prebuilt in his repo. I'm aware, on Windows I'm using Veracrypt, but I can't find Veracrypt on slackbuilds.org... I see zulucrypt? https://slackbuilds.org/repository/14.1/system/zuluCrypt/?search=veracrypt I need this only for encrypted volumes on pendrives (containing my password-protected private keys) used on both linux and Windows machines. -- Z poważaniem / Best regards / Mit freundlichen Grüßen, Thomas Szteliga websafe.pl Complete IT Solutions for Enterprises ul. Mazowiecka 8 PL 45-308 Opole https://websafe.pl/ NIP: 754-209-69-74 REGON: 531327129 BANK: PL 31 1050 1504 1000 0090 6254 7428 smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Problem building truecrypt
On 06/05/2016 05:11 AM, Willy Sudiarto Raharjo wrote: > Tested on lates current and it worked fine > truecrypt: > MD5SUM check for truecrypt-7.1a.tar.gz ... OK > Building package truecrypt-7.1a-x86_64-1_SBo.tgz ... OK > Installing package truecrypt-7.1a-x86_64-1_SBo.tgz ... OK > From your error message, it seems that you have wxGTK3 instead of > wxPython as requested I'm on 14.1 and: # ls -1 /var/log/packages/wx* /var/log/packages/wxGTK3-3.0.2-x86_64-2_SBo /var/log/packages/wxPython-2.8.12.1-x86_64-2_SBo I'll removepkg wxGTK3 and try again... OK, after removing of wxGTK3-3.0.2 I'm getting another error: ... Compiling CoreUnix.cpp Compiling CoreLinux.cpp Updating library Core.a make[1]: wx-config: Command not found make[1]: wx-config: Command not found Precompiling SystemPrecompiled.h SystemPrecompiled.h:9:19: fatal error: wx/wx.h: No such file or directory #include ^ compilation terminated. make[1]: *** [SystemPrecompiled.h.gch] Error 1 make: *** [all] Error 2 And finally I solved this problem by doing: slpkg -s sbo wxGTK after that I had: # ls -1 /var/log/packages/wx* /var/log/packages/wxGTK-2.8.12-x86_64-3_SBo /var/log/packages/wxPython-2.8.12.1-x86_64-2_SBo and I was able to build truecrypt :-) I'm not sure why I had wxGTK3 but I'll probably see it in a few days ;-) -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Problem building truecrypt
pto/Aeskey.c:527:34: warning: operation on ‘ss[7]’ may be
undefined [-Wsequence-point]
cx->ks[v(56,(7))] = ff(ss[7] = word_in(key, 7));
^
../Crypto/Aesopt.h:541:37: note: in definition of macro ‘bval’
#define bval(x,n) ((uint_8t)((x) >> (8 * (n
^
../Crypto/Aesopt.h:689:17: note: in expansion of macro ‘vf1’
^ tab[2][bval(vf(x,2,c),rf(2,c))] \
^
../Crypto/Aesopt.h:709:27: note: in expansion of macro ‘four_tables’
#define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0)
^
../Crypto/Aeskey.c:249:17: note: in expansion of macro ‘inv_mcol’
#define ff(x) inv_mcol(x)
^
../Crypto/Aeskey.c:527:25: note: in expansion of macro ‘ff’
cx->ks[v(56,(7))] = ff(ss[7] = word_in(key, 7));
^
Compiling Aestab.c
Compiling Blowfish.c
Compiling Cast.c
Compiling Des.c
Compiling Rmd160.c
Compiling Serpent.c
Compiling Sha1.c
Compiling Sha2.c
Compiling Twofish.c
Compiling Whirlpool.c
Compiling Crc.c
Compiling Endian.c
Compiling GfMul.c
Compiling Pkcs5.c
Compiling SecurityToken.cpp
Updating library Volume.a
Compiling FuseService.cpp
Updating library Driver.a
Compiling CoreBase.cpp
Compiling CoreException.cpp
Compiling FatFormatter.cpp
Compiling HostDevice.cpp
Compiling MountOptions.cpp
Compiling RandomNumberGenerator.cpp
Compiling VolumeCreator.cpp
Compiling CoreService.cpp
Compiling CoreServiceRequest.cpp
Compiling CoreServiceResponse.cpp
Compiling CoreUnix.cpp
Compiling CoreLinux.cpp
Updating library Core.a
Precompiling SystemPrecompiled.h
Compiling Application.cpp
In file included from /usr/include/wx-3.0/wx/stdpaths.h:185:0:
/usr/include/wx-3.0/wx/unix/stdpaths.h: In static member function
‘static TrueCrypt::FilePath
TrueCrypt::Application::GetConfigFilePath(const wxString&, bool)’:
/usr/include/wx-3.0/wx/unix/stdpaths.h:56:5: error:
‘wxStandardPaths::wxStandardPaths()’ is protected
wxStandardPaths() { }
^
TextUserInterface.h:99:19: error: within this context
In file included from /usr/include/wx-3.0/wx/stdpaths.h:185:0:
/usr/include/wx-3.0/wx/unix/stdpaths.h: In static member function
‘static TrueCrypt::DirectoryPath
TrueCrypt::Application::GetExecutableDirectory()’:
/usr/include/wx-3.0/wx/unix/stdpaths.h:56:5: error:
‘wxStandardPaths::wxStandardPaths()’ is protected
wxStandardPaths() { }
^
TextUserInterface.h:124:47: error: within this context
In file included from /usr/include/wx-3.0/wx/stdpaths.h:185:0:
/usr/include/wx-3.0/wx/unix/stdpaths.h: In static member function
‘static TrueCrypt::FilePath TrueCrypt::Application::GetExecutablePath()’:
/usr/include/wx-3.0/wx/unix/stdpaths.h:56:5: error:
‘wxStandardPaths::wxStandardPaths()’ is protected
wxStandardPaths() { }
^
TextUserInterface.h:129:35: error: within this context
make[1]: *** [Application.o] Error 1
make: *** [all] Error 2
Is it just me?
--
Thomas Szteliga
smime.p7s
Description: S/MIME Cryptographic Signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] remmina - wrong checksum?
Hello, http://slackbuilds.org/slackbuilds/14.1/network/remmina/remmina.info contains: DOWNLOAD=https://github.com/FreeRDP/Remmina/archive/v1.2.0-rcgit.1.tar.gz \ http://pkgs.fedoraproject.org/repo/pkgs/libssh/libssh-0.6.4.tar.gz/5d092f911492e3ee4cd7b473f09a0196/libssh-0.6.4.tar.gz; MD5SUM=bd92d1beb5c0c3acb6e32ad546e30d84 \ 5d092f911492e3ee4cd7b473f09a0196 but: wget https://github.com/FreeRDP/Remmina/archive/v1.2.0-rcgit.1.tar.gz md5sum v1.2.0-rcgit.1.tar.gz 7b5df647a9fb0be206cfabd273bc91f4 v1.2.0-rcgit.1.tar.gz -- Best regards, Thomas Szteliga https://github.com/websafe/ smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`?
SlackBuild templates (and scripts) contain this line: cat $CWD/$PRGNAM.SlackBuild \ $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild but what if a SlackBuild script requires patches applied during its execution. Shouldn't they be copied to $PKG/usr/doc/$PRGNAM-$VERSION/ as well? For example, `arj` http://slackbuilds.org/repository/14.1/system/arj/ requires a lot of patches http://slackbuilds.org/slackbuilds/14.1/system/arj/patches/ but the SlackBuild script http://slackbuilds.org/slackbuilds/14.1/system/arj/arj.SlackBuild still contains only: cat $CWD/$PRGNAM.SlackBuild \ $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild leaving the patches out. -- Best regards, Thomas Szteliga https://github.com/websafe/ smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Problem with mono (and probably mono2) on Slackware64
On 08/10/2015 06:07 AM, Christoph Willing wrote: That is not an appropriate patch; it is completely 64bit-centric, just as the config in the source code is completely 32bit-centric. Sorry for that, this patch wasn't meant to be a patch for the slackbuild package, just for visualisation of changes I've made that allowed me to run KeePass. Sorry for misleading. -- Best regards, Thomas Szteliga https://github.com/websafe/ smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Problem with building spice - celt051.SlackBuild needs an update?
Hello, I was trying to build virt-manager with dependencies, and a problem occured with `spice` http://slackbuilds.org/repository/14.1/network/spice/: make[4]: Entering directory `/tmp/SBo/spice-0.12.5/server' CC agent-msg-filter.lo CC char_device.lo CC glz_encoder.lo CC glz_encoder_dictionary.lo CC inputs_channel.lo CC jpeg_encoder.lo CC main_channel.lo CC mjpeg_encoder.lo CC red_channel.lo CC dispatcher.lo CC red_dispatcher.lo CC main_dispatcher.lo CC red_memslots.lo CC red_parse_qxl.lo CC red_worker.lo CC reds.lo CC reds_stream.lo CC reds_sw_canvas.lo CC snd_worker.lo CC spicevmc.lo CC spice_timer_queue.lo CC zlib_encoder.lo CC spice_bitmap_utils.lo CC spice_image_cache.lo CCLD libspice-server.la gcc: error: /usr/lib64/libcelt051.so: No such file or directory ^^^ make[4]: *** [libspice-server.la] Error 1 make[4]: Leaving directory `/tmp/SBo/spice-0.12.5/server' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/tmp/SBo/spice-0.12.5/server' make[2]: *** [all] Error 2 make[2]: Leaving directory `/tmp/SBo/spice-0.12.5/server' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/SBo/spice-0.12.5' make: *** [all] Error 2 Total build time for package spice : 41.58 Sec `celt051` http://slackbuilds.org/repository/14.1/audio/celt051/ was built and installed before, but the file expected during the spice build - `/usr/lib64/libcelt051.so` - was not available: # ls -la /usr/lib64/libcelt051.so ls: cannot access /usr/lib64/libcelt051.so: No such file or directory There was a file: # ls -la /usr/lib64/libcelt051.so.0 lrwxrwxrwx 1 root root 19 Aug 9 01:57 /usr/lib64/libcelt051.so.0 - libcelt051.so.0.0.0 What solved this issue was: cd /usr/lib64 ln -s libcelt051.so.0 libcelt051.so So I guess `celt051.SlackBuild` needs an update? -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Problem with mono (and probably mono2) on Slackware64
I've compiled KeePass http://slackbuilds.org/repository/14.1/misc/KeePass/ with mono http://slackbuilds.org/repository/14.1/development/mono/ but there was a problem and KeePass wouldn't start: $ keepass SendMessage (77594663, 0x112c, 0x4, 0x4) SendMessage (77594657, 0x101f, (nil), (nil)) SendMessage (0, 0x1203, (nil), 0x7fff90c590e0) SendMessage (0, 0x1204, (nil), 0x7fff90c590e0) SendMessage (0, 0x1203, 0x1, 0x7fff90c590e0) SendMessage (0, 0x1204, 0x1, 0x7fff90c590e0) SendMessage (0, 0x1203, 0x2, 0x7fff90c590e0) SendMessage (0, 0x1204, 0x2, 0x7fff90c590e0) SendMessage (0, 0x1203, 0x3, 0x7fff90c590e0) SendMessage (0, 0x1204, 0x3, 0x7fff90c590e0) SendMessage (0, 0x1203, 0x4, 0x7fff90c590e0) SendMessage (0, 0x1204, 0x4, 0x7fff90c590e0) System.TypeInitializationException: An exception was thrown by the type initializer for Mono.Unix.Native.Syscall --- System.DllNotFoundException: /usr/lib/libMonoPosixHelper.so ^^^ at (wrapper managed-to-native) Mono.Unix.Native.Syscall:get_at_fdcwd () at Mono.Unix.Native.Syscall..cctor () [0x0] in filename unknown:0 --- End of inner exception stack trace --- Then I found this https://bugzilla.xamarin.com/show_bug.cgi?id=24131 and after correcting the wrong path `/usr/lib/libMonoPosixHelper.so` to `/usr/lib64/libMonoPosixHelper.so` in `/etc/mono/config` everything worked as expected. So maybe a small update to `mono.Slackbuild` will be required? -- Best regards, Thomas Szteliga https://github.com/websafe/ --- etc/mono/config.orig 2015-08-09 20:49:22.656877857 +0200 +++ etc/mono/config 2015-08-09 20:49:41.571372337 +0200 @@ -10,7 +10,7 @@ dllmap dll=i:odbc32.dll target=libiodbc.dylib os=osx/ dllmap dll=oci target=libclntsh.so os=!windows/ dllmap dll=db2cli target=libdb2_36.so os=!windows/ - dllmap dll=MonoPosixHelper target=/usr/lib/libMonoPosixHelper.so os=!windows / + dllmap dll=MonoPosixHelper target=/usr/lib64/libMonoPosixHelper.so os=!windows / dllmap dll=i:msvcrt target=libc.so.6 os=!windows/ dllmap dll=i:msvcrt.dll target=libc.so.6 os=!windows/ dllmap dll=sqlite target=libsqlite.so.0 os=!windows/ smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] OpenDKIM download location has changed
OpenDKIM http://slackbuilds.org/repository/14.1/network/OpenDKIM/ download location http://iweb.dl.sourceforge.net/project/opendkim/opendkim-2.10.1.tar.gz is no longer valid. The valid location for 2.10.1 is http://garr.dl.sourceforge.net/project/opendkim/Previous%20Releases/opendkim-2.10.1.tar.gz but there's already v. 2.10.3 available... http://sourceforge.net/projects/opendkim/files/ -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Problem with building spice - celt051.SlackBuild needs an update?
On 08/09/2015 08:51 PM, John Vogel wrote: I have celt051 installed. I have the proper links. I didn't change anything. Perhaps the link was deleted post install. Hmm, I'm on a fresh full installation of x86_64 14.1. I did not remove anything... I'm checking now `install/doinst.sh` in the created package: ( cd usr/lib64 ; rm -rf libcelt051.so ) ( cd usr/lib64 ; ln -sf libcelt051.so.0.0.0 libcelt051.so ) ( cd usr/lib64 ; rm -rf libcelt051.so.0 ) ( cd usr/lib64 ; ln -sf libcelt051.so.0.0.0 libcelt051.so.0 ) so it should be there... I was building with slkpg (https://github.com/dslackw/slpkg) and between celt051 and spice-012.5 the following packages were built: + pyparsing-2.0.3 + spice-protocol-0.12.7 + orc-0.4.23 + gstreamer1-1.4.5 + gst1-plugins-base-1.4.5 I'll investigate this. -- Best regards, Thomas Szteliga https://github.com/websafe/ smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] libreoffice 5.0 crash and burn
On 08/09/2015 11:06 PM, Jim Diamond wrote: # sboupgrade libreoffice 2015-08-09 18:04:28 (4.88 MB/s) - 'LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz' saved [239927592/239927592] Unable to download/verify source file(s) for libreoffice: md5sum failure for /usr/local/poo/usr-sbo-141/distfiles/LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz. Do you want to proceed? [n] Failures: libreoffice: md5sum failure for /usr/local/poo/usr-sbo-141/distfiles/LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz. 6.23s user 2.02s system 8% cpu 1:39.01 total I was able to download http://download.documentfoundation.org/libreoffice/stable/5.0.0/rpm/x86_64/LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz but the checksum in the info file is wrong, should be: $ md5sum LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz 6e1c97eaa221748e328c80470d296583 LibreOffice_5.0.0_Linux_x86-64_rpm.tar.gz instead of: MD5SUM_x86_64=609182c7ebbf5d5a96ffdb5418eff3f7 -- Best regards, Thomas Szteliga https://github.com/websafe/ smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] libgdiplus 3.12 not compiling
Hello, I've noticed, the libgdiplus-3.12 package http://slackbuilds.org/repository/14.1/libraries/libgdiplus/ won't compile, because the line: ~~~ # patch -p1 $CWD/libgdiplus-giflib.patch ~~~ is commented in the SlackBuild. Uncomenting solves the problem. -- Best regards Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] gitorious acquired by gitlab
W dniu 2015-03-13 o 21:32, King Beowulf pisze: On Thursday, March 12, 2015, Klaatu kla...@straightedgelinux.com mailto:kla...@straightedgelinux.com wrote: Yeah, I moved my stuff from gitorious to gitlab. It was a one-click process, very simple. Added my ssh key and with one git remote command all my local repositories push to it. As service moves go, I'm not saying anything either way about the service itself; I'm just saying that if you are apprehensive about how much work it may be, I can assure you that it was no work at all. It was all done on one lunch break, and I haven't really given it any amount of thought since. Level of difficulty is not an issue. Just wondering how long the gitlab community edition will last. We all have to eat and pay rent/mortgage, but it seems the rush to monetization is thinning out F/OSS lately. Not related to gitorious/gitlab but Git in general. Google murders Google Code, orders everyone out to GitHub http://www.theregister.co.uk/2015/03/12/google_code_shutdown/ Google Code - Export to GitHub https://code.google.com/export-to-github/ -- Thomas Szteliga smime.p7s Description: Kryptograficzna sygnatura S/MIME ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] libreoffice-langpack - problems / questions
Hello, few words about what I've noticed when I tried to build libreoffice-langpack (other than en-GB) with md5sum checking enabled (using slpkg). The build fails, because each langpack has another md5sum, and http://slackbuilds.org/slackbuilds/14.1/office/libreoffice-langpack/libreoffice-langpack.info contains the md5sum only for the en-GB pack. Question is, should we: 1. create a cloned slackbuild for each langpack with a valid DOWNLOAD and MD5SUM in .nfo or 2. modify the SlackBuild and .nfo to include all languages by default or 3. leave it as it is? Any ideas? -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] UID/GID for another Dovecot case
On 02/15/2015 01:42 AM, Willy Sudiarto Raharjo wrote: please use 303 for vmail I'm not sure if this (303) is a good idea? Everywhere I look I see uid 5000. I'm running Dovecot + Postfix on multiple machines, and I'm always using vmail/5000. http://wiki2.dovecot.org/HowTo/VirtualUserFlatFilesPostfix https://workaround.org/book/export/html/60 https://workaround.org/ispmail/squeeze/setting-up-dovecot http://www.openchange.org/cookbook/backends/sogo/dovecot.html https://www.linode.com/docs/email/postfix/email-with-postfix-dovecot-and-mysql-on-centos-5 And as Slacker stated, this is not required for building packages, so I don't think this should be defined in http://slackbuilds.org/uid_gid.txt The vmail user/group is not required for packaging and fully optional during dovecot usage. Slackbuilds do not create users/groups so the vmail group should not be defined there. For example, on some machines I'm using separate vmail groups for separate customers, starting with vmail/5000, vmail2/5001, vmail3/5002... -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] UID/GID for another Dovecot case
On 02/14/2015 10:21 PM, Slacker wrote: I am writing a Slackdocs article for setting up a virtual mail server using Postfix, Dovecot and MySQL. In this use case we require a separate non-priv user/group for which the Dovecot documents suggest vmail ( http://wiki.dovecot.org/VirtualUsers ), and which I have used in my own implementation. This is purely a configuration option and is not required to build the Dovecot package. But it seems to me it is a common enough use case and that having an SBo assigned uid/gid for vmail would dovetail nicely with the dovecot docs and simplify virtual mail setup for those building with SBo scripts. It would also simplify my Slackdocs article. So, please consider this a request for either discussion or simply for an assigned uid/gid for a vmail user. Hello Slacker, please consider using the default uid 5000 http://wiki2.dovecot.org/HowTo/VirtualUserFlatFilesPostfix https://wiki.archlinux.org/index.php/Virtual_user_mail_system http://www.stefan-seelmann.de/wiki/mailserver-postfix-dovecot and please let us know when Your article is published :-) -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] SDL2_mixer compilation fails
On 01/17/2015 07:52 PM, Thomas Szteliga wrote: SDL2_mixer http://slackbuilds.org/repository/14.1/development/SDL2_mixer compilation fails with: SDL2_mixer compilation fails only on machines where `libmodplug` http://slackbuilds.org/repository/14.1/libraries/libmodplug/ is installed (which is an optional dep for SDL2_mixer). Without libmodplug installed everything is fine. -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] SDL2_mixer compilation fails
SDL2_mixer http://slackbuilds.org/repository/14.1/development/SDL2_mixer compilation fails with: libtool: compile: gcc -O2 -fPIC -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL2 -DHAVE_SIGNAL_H -DHAVE_SETBUF -fvisibility=hidden -DHAVE_FORK -DCMD_MUSIC -DWAV_MUSIC -DMODPLUG_MUSIC -DMODPLUG_DYNAMIC=\libmodplug.so.1\ -DMID_MUSIC -DUSE_TIMIDITY_MIDI -I./timidity -DOGG_MUSIC -DOGG_DYNAMIC=\libvorbisfile.so.3\ -DFLAC_MUSIC -DFLAC_DYNAMIC=\libFLAC.so.8\ -MMD -MT build/mixer.lo -c mixer.c -fPIC -DPIC -o build/.libs/mixer.o In file included from mixer.c:38:0: dynamic_modplug.h:24:21: fatal error: modplug.h: No such file or directory #include modplug.h ^ compilation terminated. make: *** [build/mixer.lo] Error 1 Total build time for package SDL2_mixer : 6.16 Sec I found this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725564 Adding -I/usr/include/libmodplug to the compiler flags solved the problem. -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] ANNOUNCEMENT: qemu-2.2.0
On 01/10/2015 12:48 AM, King Beowulf wrote: -current already has the new(er) libusb so there is no need to build a static version. The build system should pickup the system libusb. Don't forget to read the README! Don't forget usbredir. Please check my http://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-January/013448.html spice-gtk (dependency of virt-manager) already requires usbredir so maybe usbredir should become a default for qemu? -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Missing requirement: spice-gtk requires usbredir
spice-gtk http://slackbuilds.org/repository/14.1/network/spice-gtk/ requires usbredir http://slackbuilds.org/repository/14.1/system/usbredir/ otherwise: configure: error: usbredir support explicitly requested, but some required packages are not available when building spice-gtk. -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Missing requirement: spice-gtk requires usbredir
On 01/10/2015 05:21 AM, Thomas Szteliga wrote: spice-gtk http://slackbuilds.org/repository/14.1/network/spice-gtk/ requires usbredir http://slackbuilds.org/repository/14.1/system/usbredir/ otherwise: configure: error: usbredir support explicitly requested, but some required packages are not available when building spice-gtk. Now I see there is: # enable support for usbredir and libcacard, if available if pkg-config --exists libusbredirhost; then usbredir=en; else usbredir=dis; fi if pkg-config --exists libcacard; then cacard=en; else cacard=dis; fi if [ $GTK = 2 ]; then gtkver=2; else gtkver=3; fi in spice-gtk.SlackBuild (I was building with slpkg). The slackbuild enabled in my case usbredir automatically, but the build failed, so I assumed usbredir is missing in REQUIRED... -- Thomas Szteliga ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] gnome-python2-gconf.SlackBuild breaks
First I thought it's a missing dependency: gnome-python2-gconf http://slackbuilds.org/repository/14.1/libraries/gnome-python2-gconf/ probably requires pyorbit http://slackbuilds.org/repository/14.1/python/pyorbit/ otherwise build fails with: Note: PyORBit 2.0.1 or later is required by bonobo and gnomeui bindings. Download it from: http://ftp.gnome.org/pub/GNOME/sources/pyorbit/2.0/ but then I've noticed, gnome-python2-gconf.SlackBuild fails on this: find $PKG | xargs file | egrep ELF.*shared object | cut -f 1 -d : \ | xargs strip --strip-unneeded 2 /dev/null After commenting these two lines the package is created without problems. -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] virt-manager - hompage changed
http://virt-manager.et.redhat.com is not valid anymore. The new homepage is located at http://virt-manager.org/ http://slackbuilds.org/repository/14.1/system/virt-manager/ -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] xbmc - missing tarball
Hello, in the xbmc slackbuild http://slackbuilds.org/repository/14.1/multimedia/xbmc/ the location of xbmc-13.1.tar.gz has changed to http://mirrors.kodi.tv/releases/source/old/xbmc-13.1.tar.gz -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Indirect download links in *.info
Hello, I would like to create slackbuilds for some Google TTF fonts and I have a problem with the .info file. For example, the `Open Sans` font collection is nowhere available for direct download, it's distributed by Google and the Google download link is the following: http://www.google.com/fonts/download?kit=3hvsV99qyKCBS55e5pvb3ltkqrIMaAZWyLYEoB48lSQ Downloading this with `wget` requires the flag --content-disposition to be set and then everything works fine - the link is being downloaded to `Open_Sans.zip`, otherwise we end up with a download?kit=3hvsV99qyKCBS55e5pvb3ltkqrIMaAZWyLYEoB48lSQ file. This case breaks the default `sbopkg` configuration, because WGETFLAGS does not contain --content-disposition by default. My question is what to do in cases like this (indirect download links)? I'm asking here because in `template.info` http://slackbuilds.org/templates/template.info there is: DOWNLOAD=direct download link(s) of application source tarball(s) ^^^ arch-independent or x86 I'll of course mention this issue on the `sbopkg` mailing list but please let me know if it's legal ;) to use an indirect download link in *.info files. If yes, then fixing `sbopkg` is simple, it would only require altering the default configuration by extending WGETFLAGS with --content-disposition. If not, then I don't know, because handling this situation directly in the SlackBuild is too late (at least for `sbopkg`, because `sbopkg` will download the source and check the md5sum before the slackbuild is called). -- Thomas Szteliga https://github.com/websafe smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Indirect download links in *.info
On 01/02/2015 07:46 AM, Willy Sudiarto Raharjo wrote: i have uploaded the source in this URL https://sourceforge.net/projects/slackbuildsdirectlinks/files/OpenSans/ OK, thank You Willy, but please check the result of this script: https://gist.github.com/websafe/c172f6a99cf2ff28f8f0 Why do the md5 sums differ? ls -l -rw-r--r-- 1 root root 1144311 Jan 2 2015 Open_Sans.zip -rw-r--r-- 1 root root 1144311 Jan 2 07:08 download?kit=3hvsV99qyKCBS55e5pvb3ltkqrIMaAZWyLYEoB48lSQ md5sum 811d92c69a9d75e17c148b28226c6eab download?kit=3hvsV99qyKCBS55e5pvb3ltkqrIMaAZWyLYEoB48lSQ b7b32f9e7f22b772d83117407ed48f1b Open_Sans.zip md5sum -b 811d92c69a9d75e17c148b28226c6eab *download?kit=3hvsV99qyKCBS55e5pvb3ltkqrIMaAZWyLYEoB48lSQ b7b32f9e7f22b772d83117407ed48f1b *Open_Sans.zip I've noticed something strange for i in `seq 10`; do \ rm -f Open_Sans.zip; \ wget -q --content-disposition \ http://www.google.com/fonts/download?kit=3hvsV99qyKCBS55e5pvb3ltkqrIMaAZWyLYEoB48lSQ;; \ md5sum Open_Sans.zip; \ done; Result: 387a12ebc6ae95fc1d7d34ece556ab71 Open_Sans.zip 387a12ebc6ae95fc1d7d34ece556ab71 Open_Sans.zip 4b71e4dd4e82c0ae7119fce173c699c9 Open_Sans.zip 4b71e4dd4e82c0ae7119fce173c699c9 Open_Sans.zip 087871b0c521cdb33d4cf76fdd6554c4 Open_Sans.zip 087871b0c521cdb33d4cf76fdd6554c4 Open_Sans.zip 2bd0bd021b17e6c1b44885cb4cfa54f5 Open_Sans.zip 7f8d14883723c28087d352e53746635c Open_Sans.zip 7f8d14883723c28087d352e53746635c Open_Sans.zip f7b0244cc750069f99ddca02258e4118 Open_Sans.zip It's somehow Google's fault. So in this case I'll not be able to verify, that https://sourceforge.net/projects/slackbuildsdirectlinks/files/OpenSans/ matches http://www.google.com/fonts/download?kit=3hvsV99qyKCBS55e5pvb3ltkqrIMaAZWyLYEoB48lSQ hmmm... -- Thomas Szteliga https://github.com/websafe smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] [BUG] slack-desc for perl-IO-HTML has only 10 lines (one missing)
The section below handy-ruler in slack-desc for perl-IO-HTML http://slackbuilds.org/slackbuilds/14.1/perl/perl-IO-HTML/slack-desc has only 10 lines instead of expected 11 lines. -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] [BUG] slack-desc for perl-TermReadKey has only 8 lines (three missing)
The section below handy-ruler in slack-desc for perl-TermReadKey http://slackbuilds.org/slackbuilds/14.1/perl/perl-TermReadKey/slack-desc has only 8 lines instead of expected 11 lines. -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
