Re: [Slackbuilds-users] Call for Help
Willy Sudiarto Raharjo writes: > [[PGP Signed Part:Good signature from 3F617144D7238786 Willy Sudiarto Raharjo > (trust undefined) created at 2024-04-25T06:44:54+0800 > using RSA]] > Hi all > > Andrew has compiled a list of FTBFS (Fail to Build From Source) which are > listed > here: https://github.com/SlackBuildsOrg/slackbuilds/issues/5827. > > If you are the maintainer of those packages, please check them and fix it. If > you > are using those scripts and have some time, please help us to fix those > scripts. > > Some of those are just md5sum mismatches, so it's easy to fix, but some are > broken > due to updates from one of it's deps or maybe there's a chance in upstream > but the > maintainer didn't notice or maybe even worse, maintainer is no longer active > and > scripts are abandoned. > > You can submit fixes via pull requests, so it's easy to verify using our CI > engine. > > Thanks There are a few mine in that list. I will have a look at them when I have time (probably sooner rather than later), they are not abandoned. (But I am a bit busy at my dayjob now.) -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) signature.asc Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Help on testing netdata 1.45.0
Willy Sudiarto Raharjo writes: > [[PGP Signed Part:Good signature from 3F617144D7238786 Willy Sudiarto Raharjo > (trust undefined) created at 2024-03-25T23:18:17+0800 > using RSA]] > Hi > > i just bumped netdata to 1.45.0 and since this is a major changes compared to > 1.44.x, if you are using this package, please help by testing the new version > (mind > the new dependencies) > > changes/commit can be seen here: > https://git.slackbuilds.org/slackbuilds/log/?h=netdata > > if no major issue, it will be merged on this week's public update I haven't tested the build for 1.45.0, but I have just built the previous version on SBo, 1.44.3, and I am quite surprised that it listens on a public IP by default: 0.0.0.0:1. I would consider this to be a security vulnerability. Could you make it bind to 127.0.0.1 by default, and the user could adjust the port/ip if they wish. -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) signature.asc Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] updating dozens/hundreds packages/queues more easily/correctly weekly?
Jeremy Hansen writes: > On Mon, Apr 1, 2024, 8:07 PM wrote: > > I installed more packages built from SlackBuilds.org (SBo) than urchlay > (a few years ago 1150+, now more) and see after updates, some/many need > most/all dependencies rebuilt but you never know until either building > or using crashes. Is there a way to keep track and rebuild these > without having to manually load dozens/hundreds queues in sbopkg (nor > use its command-line)--I heard it may be easier with sborepo? I have no > need for my own repository and want to avoid creating one (other than > just a directory/folder) but are there instructions on updating more > easily/correctly weekly just for users? > > Simply put, sbopkg does not have any proper way to handle this other than > rebuilding the entire tree. > > The only program I know that decently handles this is slackrepo, but it seems > to be best used on a clean > machine (either virtual or not), which can be difficult with certain users > setups. > > But I also have only used sbopkg and slackrepo (with the latter used in > conjunction with slapt-get to handle > dependencies of packages), so others might be better set up for it without me > being aware of it. > > Jeremy > > ___ > 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/ Might it be that sboupgrade is what you need? Not sure if it can detect broken ldd, but it seems to be able to update the deps if the target package needs them. -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) signature.asc Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] suggestion for a new category for fonts
"B. Watson" writes: > On Thu, 21 Mar 2024, Willy Sudiarto Raharjo wrote: > >> Since we have search form in our website, i wonder how many people would go >> through each categories when looking for some scripts instead of just using >> the >> search form? > > OK, so in that case, why do we have categories at all? Would it bother > you to get rid of them entirely? Other than the amount of work it > would take to accomplish it, I mean. Would we be better off if there > had never been categories? > > We could just add a keyword for each build, with its former category. > system/dosbox would just become dosbox/, and get "system" added to its > list of keywords... > > ...which is silly of course. It's intended to be silly. > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ I do use categories often. I am finding them useful when understanding optional deps, and when searching for "related software". Admittedly, perhaps not _all_ of them are useful, but for me many make sense. I am often finding myself searching for packages using sbopkg -g. They are not fool-proof, but they do help when there are packages with similar names, but doing different things. For example, I might be searching for something which encrypts with aes: sbopkg -g aes. This is the result: academic/aeskulap 0.2.2_e710562d haskell/haskell-aeson 2.0.2.0 haskell/haskell-aeson-compat 0.3.10 haskell/haskell-aeson-pretty 0.8.9 haskell/haskell-cipher-aes0.2.11 haskell/haskell-hslua-aeson 2.1.0 libraries/SlowAES 0.1a1 libraries/libcaes 20230406 office/unaesgcm 0.4.1.20220827_0cf9cb perl/perl-Crypt-OpenSSL-AES 0.02 python/pyaes 1.6.1 system/aespipe2.4g From those I immediately see that I need no "academic, haskell, libraries, perl, python." Which leaves me with either unaesgcm or aespipe. And both of those generally do what I expect them to do. When a program is in the "network" category, very high chances are that it doesn't work without network access. Some things are not entirely clear, such as "desktop/office/development". Like, I am a developer, and I use a desktop computer, and I work in an office. But even so, a "desktop" program probably has a GUI, or at least and interactive TUI. Replacing categories _entirely_ with tags might be an option, but for me it seems too radical of a reform, to be honest. But at least (python, ruby, haskell), "network", and "libraries" do make a lot of sense. -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) signature.asc Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] suggestion for a new category for fonts
KB_SBo writes: > On 3/19/24 11:31, Qun-Ying wrote: >> Hi, >> >> Currently fonts are put under category system, they mix with other >> system tools. Would it be better to have a separate category (fonts) >> for them? >> >> > > +1 for fonts as its own category > > -kb > > > > ___ > 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/ +1 for fonts as its own category, and, if possible, please, one more category for "slackware-specific" stuffs, such as: 1. slackrepo 2. slackrepo-hints 3. sbotools 4. sbo-create 5. sbo-maintainer-tools 6. sbotools 7. sboui 8. slpkg 9. listpkg 10. gnome-pkgtool 11. findpkg 12. slack-osquery 13. slack-utils 14. slackchlog 15. slackroll 16. slackupdr 17. slackware-grub2-theme 18. slackyd 19. slack-wallpapers 20. slackware-xdg-menu 21. slackware-xdm-theme 22. xdm-slackware-theme 23. fortune-slackware 24. perl-CPANPLUS-Dist-Slackware 25. python2-slacklog This is comparable to the size of, say accessibility/ nowadays those packages are scattered over many categories, not just system/, and system/ has a lot of packages, whereas having all Slackware-related in one place would have been really convenient. -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) signature.asc Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Linphone maintenance
Sebastian Arcus writes: > On 08/02/2024 02:56, Willy Sudiarto Raharjo wrote: >>> What WSR is responding is factually wrong. >>> >>> I have submitted the slackbuild for the most recent version of linphone >>> (submitted as linphone-desktop, because nowadays linphone is very >>> different from what it was in the past, and the developers, Belledonne >>> Communications, keep it in a separate repo from the old linphone). >>> >>> The code is here: >>> https://gitlab.com/Lockywolf/lwfslackbuilds/-/tree/master/05_submitted/linphone-desktop?ref_type=heads >>> It was rejected for the reason of being "for the alpha version". >>> (WSR's own responce from Sat, 23 Sep 2023 10:34:46 +0700) >>> >>>> do you mind to wait until 5.2.0 is released or go for previous version >>>> which is >>>> released under stable label? >>> >>> So I have been waiting for the 5.2.0 since. >>> >>> You can roll-back to the most-recent non-alpha, and re-submit, I do not >>> mind. >> They have released 5.2.1 6 days ago >> https://gitlab.linphone.org/BC/public/linphone-desktop/-/tags > > Just checking if we reached any decision on this? Are we happy to use > Lockywolf's > scripts - and move Linphone to version 5.1.2 which compiles on Slackware 15.0 > - and > replace the old Linphone scripts? Is anybody going to take linphone-desktop away from me? -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) signature.asc Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Wrong md5sum for rav1e
Alexander Verbovetsky writes: > On Sat, Feb 17, 2024 at 02:40:28PM +0100, Heiko Rosemann via > SlackBuilds-users wrote: >> On 2/17/24 14:16, Alexander Verbovetsky wrote: >> > By some reason the building process for rav1e tries to use >> > Cargo.lock from cargo-c instead of downloading its own Cargo.lock. >> > >> > It seems an oversight or foul play is involved in >> > > Found Cargo.lock in /var/cache/sbopkg. > > >> That absolutely works as intended: Before downloading, sbopkg checks >> if a file of the correct name already exists in the cache directory. > >> It does not keep track where that file came from or when it was >> downloaded. > > To me it sounds like receipt for disaster. > > Are there any recommendation what a slackbuild script should do about > this problem? > > Clean $CWD at the very end? > > Best regards, > Alexander > ___ > 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/ Do we actually need those Cargo.lock files to successfully build a rust binary? I have a few rust slackbuilds (helvum, lean-elan, tzupdate), and they just use .crate files, not Cargo.lock files. I am pre-generating .info files with the following script: https://gitlab.com/Lockywolf/lwfslackbuilds/-/blob/master/02_lockywolf-sbo-scripts/lwf_make-cargolinks.bash?ref_type=heads -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Linphone maintenance
Sebastian Arcus writes: > On 08/02/2024 00:37, Willy Sudiarto Raharjo wrote: >>> Anyone knows if Linphone is still actively maintained? I have managed to >>> compile >>> a current version on Slackware, and it would be nice if it could be updated >>> at >>> SBo as well >> nope, maintainer is no longer active, so if you are willing to take over >> maintainership, that would be great idea > > Ok - thank you - I will take it over and try to update the scripts. I might > need a > hand with a few bits I haven't figured out yet - but I will send a separate > message > to the list > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ What WSR is responding is factually wrong. I have submitted the slackbuild for the most recent version of linphone (submitted as linphone-desktop, because nowadays linphone is very different from what it was in the past, and the developers, Belledonne Communications, keep it in a separate repo from the old linphone). The code is here: https://gitlab.com/Lockywolf/lwfslackbuilds/-/tree/master/05_submitted/linphone-desktop?ref_type=heads It was rejected for the reason of being "for the alpha version". (WSR's own responce from Sat, 23 Sep 2023 10:34:46 +0700) >do you mind to wait until 5.2.0 is released or go for previous version which is >released under stable label? So I have been waiting for the 5.2.0 since. You can roll-back to the most-recent non-alpha, and re-submit, I do not mind. -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Linphone sources and dependencies
Sebastian Arcus writes: > 2. However, if I just download version 5.0.0 directly from git (later versions > require cmake 3.2.2) on either Slackware -current or 15.0: > You don't have to do any of that, just change the hashes in my build, and re-submit. -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Updates - 20231202.1
t; > > python/python3-bidi: Added (BiDi Layout Implementation). >> > > python/python3-blessed: Added (python library). >> > > python/python3-celery: updated for version 5.3.6 >> > > python/python3-cloudflare: Updated for version 2.14.2 >> > > python/python3-eventlet: Added (concurrent networking library). >> > > python/python3-funcparserlib: Added (lisp parser). >> > > python/python3-gensim: Update README >> > > python/python3-google-api-python-client: Update script. >> > > python/python3-google-auth-httplib2: Added (Google Authentication >> > > Library). >> > > python/python3-google-python-api-core: Update script. >> > > python/python3-googleapis-common-protos: Added (Common protobufs). >> > > python/python3-httpx: fix deps. >> > > python/python3-inotify-simple: Added (inotify wrapper). >> > > python/python3-jsonschema: fix deps. >> > > python/python3-mediafile: fix deps. >> > > python/python3-pastedeploy: updated for version 3.1.0 >> > > python/python3-pyasn1: updated for version 0.5.1 >> > > python/python3-pydantic-core: fix deps. >> > > python/python3-pyproject-hooks: fix deps. >> > > python/python3-requests-cache: fix deps. >> > > python/python3-setuptools-rust: Update dependencies. >> > > python/python3-svglib: Added (read SVG). >> > > python/python3-sysrsync: Update dependencies. >> > > python/python3-toml: Added (Python lib for TOML). >> > > python/python3-trove-classifiers: Updated for version 2023.11.22. >> > > python/python3-uritools: Added (parsing URI library). >> > > python/python3-vharfbuzz: Added (shaping text tool). >> > > python/python3-wcwidth: updated for version 0.2.12 >> > > python/python3-xkeysnail: Update dependency. >> > > python/s3transfer: Updated for version 0.8.0. >> > > python/snowballstemmer: Updated for version 2.2.0. >> > > python/tqdm: Updated for version 4.66.1. >> > > system/CNS11643-font: Updated for version 20231103. >> > > system/android-udev-rules: Updated to version 2023.11.24. >> > > system/augeas: Updated for version 1.12.0. >> > > system/distrobox: Added (fancy wrapper for containers). >> > > system/docker-compose: Updated for version 2.23.3 >> > > system/duperemove: Updated for version 0.14.1. >> > > system/far2l: Added (file manager). >> > > system/fonts-kannada-extra: Updated for version 1.1. >> > > system/fonts-malayalam-extra: Updated for version 1.2. >> > > system/fonts-tamil-bharathi: Added (system fonts). >> > > system/fonts-tamil-libre: Updated for version 1.3. >> > > system/fonts-tamil-tva: Updated for version 1.1. >> > > system/fonts-telugu-extra: Updated for version 1.2. >> > > system/forkstat: Updated for version 0.03.01. >> > > system/fwupd: Update dependencies. >> > > system/gpustat: Added (query and monitor GPU). >> > > system/i8kutils: Updated for version 20210330_c993fb1d. >> > > system/locust: Updated for version 2.19.1. >> > > system/lssecret: Added (list secrets). >> > > system/mpollux-digisign-client: Updated for version 4.2.6. >> > > system/onefetch: Updated for version 2.19.0. >> > > system/openzfs: Updated for version 2.2.1. >> > > system/pgbadger: updated for version 12.3 >> > > system/powerline-status: Updated for version 2.8.3. >> > > system/powershell: Updated to version 7.4.0. >> > > system/pv: updated for version 1.8.5 >> > > system/python3-nvidia-ml-py: Added (Python Bindings for NVIDIA ML). >> > > system/qterminal: Updated for version 1.4.0. >> > > system/s6: Updated for version 2.12.0.2 >> > > system/squashfuse: Updated for version 0.5.0. >> > > system/tkinfo: Added (graphical browser). >> > > +--+ >> > > >> > > >> > > -- >> > > Willy Sudiarto Raharjo >> > >> > >> > >> > >> > > ___ >> > > SlackBuilds-users mailing list >> > > SlackBuilds-users@slackbuilds.org >> > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> > > FAQ - https://slackbuilds.org/faq/ >> > > >> > >> > ___ >> > 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 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 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/ -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) ___ 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] [RFC] Adding features to .info format.
Hello, colleagues There have been repeated discussions about two features that the current .info file format is missing: 1. aarch64 architecture. If in the past slarm64 was still an unofficial port, with -current it is official, and quite widely available, given the number of RPi machines available. 2. urls of the form https://example.test/address/ and https://example.test/address/1.json , which are either not supported by wget or can be mixed with each other, if downloaded into the same directory, which is especially bad with Golang and Haskell builds, which have many package-components, called 1.json. To address this issue, I propose a backward-compatible change to .info files format. 1. add DOWNLOAD_AARCH64 and DOWNLOAD_X86, a space-separated bash-string-list, identical in function to DOWNLOAD and DOWNLOAD_X86_64 2. add DOWNLOAD_NAME, DOWNLOAD_X86_64_NAME, DOWNLOAD_AARCH64_NAME, and DOWNLOAD_X86_NAME, space-separated _optional_ strings, which, if present, specify what the results of download should be named. If they are absent, current logic is not changed. Please, consider the upsides and downsides of this RFC. -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) ___ 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] config files for speech-dispatcher
Hello, Slackbuilders I have submitted a build for a Text-To-Speech engine called RHVoice, which is expected to sound less robotic that espeak. I tested it, and it works, by itself. It is also shipping a libexec module for speech-dispatcher in usr/lib64/speech-dispatcher-modules/sd_rhvoice However, many other modules (in particular, espeak and festival), also ship configuration files in /etc/speech-dispatcher/modules/ I don't know what to put there. Can someone suggest where to look? -- Your sincerely, Lockywolf (Laptop) ___ 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] Help with guile-dbi.
Hello, everyone I really should ask for help at guile-dbi or guile's channels, but I have already done so, and they are not particularly active. So, I have two slackbuilds: https://gitlab.com/Lockywolf/lwfslackbuilds/-/tree/master/guile-dbi https://gitlab.com/Lockywolf/lwfslackbuilds/-/tree/master/guile-dbd-mysql They compile and install fine, however, using the guile-dbi module fails with a cryptic error: scheme@(guile-user)> (load "/dbi/dbi.scm") guile: symbol lookup error: /usr/lib64/libguile-dbi.so: undefined symbol: lt_dlinit Indeed, nm'ing /usr/lib64/libguile-dbi.so I find lt_dlinit being U for "undefined". I have never seen such an error before. I know that libtool is not expected to be simple, but I have never ever seen libtool errors. Can someone sugges a debugging method? -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) ___ 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] LanguageTool SlackBuild
Hello, everyone, Dimitris Zlatanidis agreed that I take over the maintenance of the LanguageTool Slackbuild. -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] qemu updates roadmap
I cannot build qemu from SBo on a clean Slackware64. ../meson.build:1745:0: ERROR: Feature virtfs cannot be enabled: virtio-9p (virtfs) on Linux requires libcap-ng-devel and libattr-devel building like AUDIODRIVERS=pa VNC_ENABLE=no TARGETS=x86_64-linux-user bash qemu.SlackBuild KB_SBo writes: > On 5/16/23 06:57, Matteo Bernardini wrote: >> Hi Edward, >> >> here I'm building qemu 8.0.0 and virtiofsd like this (actually I see no >> issue in using the bundled meson) >> >> https://ponce.cc/slackware/testing/virtiofsd/ >> <https://ponce.cc/slackware/testing/virtiofsd/> >> https://ponce.cc/slackware/testing/qemu/ >> <https://ponce.cc/slackware/testing/qemu/> >> >> if you don't want it I'll submit virtiofsd to SBo. >> >> Matteo >> >> >> Il giorno lun 24 apr 2023 alle ore 02:13 KB_SBo > <mailto:s...@linuxgalaxy.org>> ha scritto: >> >> All, >> >> I'm going to hold off on qemu-8.0 for a bit and just bump to qemu-7.2.1 >> >> >> 1. For 8.0, virtiofsd is now an external dependency. This built with >> rust, of which I know absolutely nothing about. Since this may take me >> awhile to do (wtf is a 'cargo'?), if anyone has a burning desire to add >> virtiofsd to SBo, have at it! >> >> 2. Slackware 15.0 meson-0.59.4 is too old. qemu has an internal >> meson-0.61.5 that is currently used for 7.2.x, but I think using the >> system meson is better for consistency. >> >> 3. libslirp and a few others will be made hard dependencies to have >> those handy features available by default. Also, libslirp could use bump >> to version 4.7.0 (maintainer cc:'ed) >> >> >> -Ed > > > > Matteo, > > I'll take virtiofsd for SBo, and get gemu-8 script ready for next week's > update. > > Thanks > Ed > > > ___ > 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/ -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) ___ 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] txrequests fails to build
#+begin_src
Traceback (most recent call last):
File "setup.py", line 6, in
import txrequests
File "/tmp/SBo/txrequests-0.9.6/txrequests/__init__.py", line 30, in
from .sessions import Session
File "/tmp/SBo/txrequests-0.9.6/txrequests/sessions.py", line 24, in
from twisted.internet import defer, reactor
File "/usr/lib64/python2.7/site-packages/twisted/internet/defer.py", line 32,
in
from twisted.logger import Logger
File "/usr/lib64/python2.7/site-packages/twisted/logger/__init__.py", line
102, in
from ._logger import Logger, _loggerFor
File "/usr/lib64/python2.7/site-packages/twisted/logger/_logger.py", line
274, in
_log = Logger()
File "/usr/lib64/python2.7/site-packages/twisted/logger/_logger.py", line 70,
in __init__
from ._global import globalLogPublisher
File "/usr/lib64/python2.7/site-packages/twisted/logger/_global.py", line 16,
in
from ._buffer import LimitedHistoryLogObserver
File "/usr/lib64/python2.7/site-packages/twisted/logger/_buffer.py", line 11,
in
from zope.interface import implementer
File "/usr/lib64/python2.7/site-packages/zope/interface/__init__.py", line
53, in
from zope.interface.interface import Interface
File "/usr/lib64/python2.7/site-packages/zope/interface/interface.py", line
660, in
{'__slots__': ()}
File "/usr/lib64/python2.7/site-packages/zope/interface/interface.py", line
641, in __new__
kind = type.__new__(cls, name, bases, attrs)
TypeError: a new-style class can't have only classic bases
Failures:
txrequests: txrequests.SlackBuild return non-zero
#+end_src
Has anyone seen this problem before?
--
Your sincerely,
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)
___
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/
