[Slackbuilds-users] libxml2 issues
Hello, Since last update of libxml2 on December 10th, there are problems with packages that depends of this library - they crash, compilation also no longer works. I have workaround for Openconnect I use and maintain, but Openconnect autodetects libpskc which is part of oath-toolkit, which depends on xmlsec (also broken by update). So, beware, many things could be broken by libxml2 update. HINT: In many cases it helps just to add: #include in include section after including libxml/tree.h in program sources. Best regards Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg ___ 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 - 20201107.1
Hello, I had also recently some Intel related problems with Chromium (Alien's build) and also Opera. I didn't test Vivaldi, but it's also Chromium based. I think that there were some changes in Chromium engine which broke all these browsers on Intel cards. Browsers started ok, but full-screen didn't work and after some use of GL, application stopped redraw itself (it worked and responded to my clicks, but nothing changed on screen). I tried kernel upgrade (nothing changed), Mesa upgrade (Mesa 13.0.6 can be built on stock 14.2) - i have a feeling that this made things little better. Of course I tried disabling hardware acceleration in browser and it helped a lot, but in long term it didn't fixed issue. What fixed in my setup was creating configuration for Intel card for X11 (maybe together with new Mesa, but I didn't try to downgrade it) in /etc/X11/xorg.conf.d/20-intel.conf to force enabling DRI 3: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "DRI""3" EndSection Best regards, Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg On Tue, 10 Nov 2020, Spycrowsoft wrote: Hello, I can confirm that I had a similar experience with Vivaldi. Except in my case, the profile folder had been mutilated to such an extent by the new version that even the previous version of Vivaldi would just crash and burn when I tried to start it. Starting over with a clean profile folder and hardware acceleration disabled was easy because I'm using the sync feature. I've tried re-enabling hardware acceleration afterwards, which lead to the same result. I've also been running the latest versions of Vivaldi on SBo with hardware acceleration disabled on Slackware 14.2 without any issues since then. For what it's worth: I've seen the same thing happening on a system with NVIDIA Optimus disabled, and a system which only has an Intel embedded graphics card. So it seems to be some kind of Intel-related issue. Given that this is a pretty common setup, it might be feasible to make a note of this in the README file, or even to take precautions in the slackbuild-script itself. However, given that the general philosophy of Slackware is to assume that the user is smart and that other hardware configurations are not guaranteed to fail, such precautions should be optional. Therefore I think that a note in the README and a variable that can optionally be set to apply your fix directly from the slackbuild with something like "DEFAULT_DISABLE_GPU_ACCELERATION=yes ./vivaldi.Slackbuild", might be the most elegant solution here. Kind regards, Spycrowsoft Op 10-11-2020 om 01:55 schreef Luiz Carlos Ramos via SlackBuilds-users: Hello, just posting about a thing that happened here with vivaldi (the browser). When it was first upgraded to version 3.4, it became broken due to some anoying problems with the GUI (windows seemed to be opened but didn't react to mouse clicks; minimizing the window seemed to work but the screen didn't change, etc.). At that time I went back to the version 2022.47 (from the end of Setember and the last one from 3.3 series) and it ran flawlessly again. This happened again for two or three times, for each slackbuild version posted so far in the 3.4 series. Last week (in another frustating upgrade) I tried to investigate a little bit more about this and ultimately found an answer in one post on this thread: https://forum.vivaldi.net/topic/52242/vivaldi-3-4-freezes-constantly-debian-10-intel-gpu/9, which is to run vivaldi from the CLI this way: $ vivaldi --disable-gpu-compositing another way to solve the problem is to disable GPU acceleration in the settings page (but to do this one must bring to the "settings" screen, which seems to be impossible when the problem happens). Here I managed to change /usr/bin/vivaldi inserting that option hardcoded in the shell script which starts the real vivaldi binary. This way I can run vivaldi from the GUI as well. The issue seems to be related to the specifics of the GPU used and I would not risk talking about it as it seems to require a deep knowledge of the inner bits. A curiosity of mine is if anybody else has experienced such problem. Anyway (and supposing this isn't a problem specific of myself), a suggestion would be writing some notes in the README file about it. I would volunteer doing so if there are no objections. Many thanks, Luiz Carlos Ramos Sao Paulo - Brazil lramos dot prof at yahoo dot com dot br ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] SBo service migration #1 complete
On Fri, 3 Jul 2020, Erik Hanson wrote: On 7/3/20 7:02 AM, Marek Wodzinski wrote: Have you thought about splitting services and migrate them to some hosted solutions? To clarify, it's around $130 per month. Not a yearly lump sum. $130 for hosting AFAIK 10 years old EOL server which could fail anytime. Costs of renting modern dedicated server starts from half of that price, additionaly it's possible failure is not your problem in term of hardware replacements. On average, the website moves around 55GB/mo, ~530k pages/mo, the git server around 42GB/mo, ftp around 32GB/mo, and our Slackware mirror around 268GB/mo. DNS and email hosting are not affected by this move. Such amount of data could be hosted for less than $5/month on linux vps with full root access. It could cost some dollars extra when more storage would be needed, but basically 1TB/mo of transfer data is common limit seen even on small vps servers. Things are fairly interconnected just due to the way we've grown over the past 14 years. Splitting things out to other services would probably require a ground-up rebuild and I'm not convinced we would save any money in the end. Maintenance is also cost. Even if you do it for free and it's your hobby. You could just use saved time to do other cool things :-) I've been in similar point some years ago with my personal infrastructure. Everything connected to everything, single point of failures, lot of custom configuration and mess growing through years. Then I went into lxc containers to separate web servers, mail, wifi controller, database and so on. I migrated my personal svn repository to git and then to Gitlab to not worry about hosting it. It took time, but it's much easier to maintain now, while there are still some things on my to do list. That's my way, yours could be of course very different. I perfectly know that it's not possible to change everything at once and now, and maybe there will be no short term benefits. Purpose of my comment was to show that there are other ways of doing things and some of them are are even for free, so maybe you could use some of them to ease maintenance, maybe reduce costs, maybe just make some long term plans, or just ignore it. Your choice. No pushing, just trying to help showing options. If you feel offended, I do apologize. Also, I would sooner shutter the project than migrate to Github. Are you aware that Slackbuilds already got more than 500 updates via Github mirror? :-) Best regards, Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] SBo service migration #1 complete
On Thu, 2 Jul 2020, Robby Workman wrote: and have migrated git.slackbuilds.org, www.slackbuilds.org, dance.slackbuilds.org (DNS slave), and slackwiki.com to it. will not be free. We are investigating options for collecting needed funds for hosting (about $1500 per year) Have you thought about splitting services and migrate them to some hosted solutions? For example git to Github or Gitlab, DNS to some free providers as dns.he.net, wiki to some inexpensive hosting or even migrate to readthedocs.org or Github pages? I know that build machine, rsync and probably main site would be still main issue and I don't know numbers such as requests, i/o, cpu or monthly traffic, but maybe there is also some solution for it (like spin up one AWS instance to test build something and then kill it, or use some CI/CD solution)? Splitting would also help to find friendly hosting/sponsor for other parts of site, like rsync could be handled by some of many Slackware mirrors. $1500 is a real money and I believe that it would be better to get rid of these costs instead of worrying every year about paying it. Anyway, thank you for your great work! Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg ___ 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] perl-Mail-SPF is unusable
On Tue, 2 Jun 2020, B Watson wrote: On 6/2/20, Marek Wodzinski wrote: Hello, I'd like to report that despite build doesn't fail somehow, module is not working because it requires Error (not in SBo). Error requires Carp and Exporter (also not in SBo), so it's not easy fixable. Carp and Exporter are included with Perl, in Slackware's perl package, which is why you don't find them on SBo. My fault. I searched for dependencies on metacpan.org and these weren't marked as part of some perl version, I didn't checked what's in ditribution. Error, I'm not sure about: it's actually deprecated according to its own documentation: https://metacpan.org/pod/Error But still required by Mail-SPF which newest version is even older than latest Error. Best regards, Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg ___ 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-Mail-SPF is unusable
Hello, I'd like to report that despite build doesn't fail somehow, module is not working because it requires Error (not in SBo). Error requires Carp and Exporter (also not in SBo), so it's not easy fixable. For my needs I just packaged missing modules with cpan2tgz, but this is worth noting somewhere, maybe in README? Spamassassin builds fine whithout perl-Mail-SPF (autodetects not working module), so maybe it would be an idea also to remove perl-Mail-SPF from it's hard dependencies? I don't know what would be with policyd2, I didn't test it. Best regards Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg ___ 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 20200601
On Mon, 1 Jun 2020, Christoph Willing wrote: On 1/6/20 10:03 pm, Marek Wodzinski wrote: Hello, On Mon, 1 Jun 2020, Willy Sudiarto Raharjo wrote: we are a bit late on this update, Looks like some tar.gz files are not rebuilt for this update, so sbopkg finds packages to update, but builds old versions :-( For example openconnect, mosquitto, kicad-*. But zoom-linux is fine. I don't understand - is this a problem with the SBo updates or sbopkg? I maintain mosquitto and looking at the mosquitto files, after a git pull this morning, they all seem correct i.e. the SBo update went fine. Sbopkg gets repository using rsync by default. In rsync repository there are the same files as in git (and this part is ok) AND also tared files (and some of these are outdated). Sbopkg search for updates using these loose files, but for building it uncompress tared files. That's why there is such strange behavior. Best regards Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg ___ 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 20200601
Hello, On Mon, 1 Jun 2020, Willy Sudiarto Raharjo wrote: we are a bit late on this update, Looks like some tar.gz files are not rebuilt for this update, so sbopkg finds packages to update, but builds old versions :-( For example openconnect, mosquitto, kicad-*. But zoom-linux is fine. Best regards, Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg ___ 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] Outdated openconnect slackbuilds
On Fri, 8 May 2020, Robby Workman wrote: I also offered maintaing it if Robby don't want or can't do it anymore. Robby? Sorry; I mentally replied, but apparently it didn't go any farther. Busy life :-) No problem. They're all yours. :-) Thank you. I submited PR on Github for openconnect. But there are also NetworkManager-openconnect and plasma-nm-openconnect. I don't use any of these, I don't even use NM or KDE, so I'm not the best person to get them. I know, it's not very good situation to not get all three, but at least Michele, I and maybe others will get up-to-date openconnect package. Best regards Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg ___ 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] Outdated openconnect slackbuilds
On Fri, 8 May 2020, ilmich wrote: Hi all, after an infrastructure update, the vpn of my company does not work anymore with the openconnect version of slackbuild. Instead with the latest version (8.09) it works. It's possible an upgrade of version?! Thanks in advance I sent e-mail to Robby 2 weeks ago about it, but I didn't get any response. I also offered maintaing it if Robby don't want or can't do it anymore. Robby? Best regards Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg ___ 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] ATT: anyone using python3-PyQt5
On Thu, 23 Apr 2020, Dave Woodfall wrote: This is a heads-up for anyone using python3-PyQt5. The version we have now has had support for QtWebEngine python bindings split into a separate package - python3-PyQtWebEngine. So far, `anki' is the only one that I know that needs it and I've adjusted it in my branch. It looks like 'anki' also requires python3-soupsieve which is new and optional dependency of BeautifulSoup4. Best regards Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Unmaintained builds - want any of these?
On Thu, 2 Jan 2020, Robby Workman wrote: TL;DR version: if you would like to see any of the scripts on the following list stay around, please step up to maintain them. https://slackbuilds.org/DeadSBoBuilds Hello, I could get: development/avra network/ipvsadm network/keepalived Maybe I wouldn't do updates right away, but within few weeks I could handle it. Best regards Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg ___ 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 - 20190518.1 - intel-microcode
On Sat, 18 May 2019, Willy Sudiarto Raharjo wrote: system/intel-microcode: Updated for version 20190514a. Intel-microcode is broken :-( Processing intel-microcode intel-microcode: intel-microcode not found in /home/sbo/cache. --2019-05-20 13:15:47-- https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/archive/microcode-20190514a.tar.gz Resolving github.com... 140.82.118.3 Connecting to github.com|140.82.118.3|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://codeload.github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/tar.gz/microcode-20190514a [following] --2019-05-20 13:15:48-- https://codeload.github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/tar.gz/microcode-20190514a Resolving codeload.github.com... 192.30.253.120 Connecting to codeload.github.com|192.30.253.120|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 2447334 (2.3M) [application/x-gzip] Saving to: ‘microcode-20190514a.tar.gz’ microcode-20190514a 100%[===>] 2.33M 34.5KB/sin 49s 2019-05-20 13:16:38 (48.3 KB/s) - ‘microcode-20190514a.tar.gz’ saved [2447334/2447334] Found microcode-20190514a.tar.gz in /home/sbo/cache. Checking MD5SUM: MD5SUM check for microcode-20190514a.tar.gz ... OK Building package for intel-microcode... tar: /var/lib/sbopkg/SBo/14.2/system/intel-microcode/Intel-Linux-Processor-Microcode-Data-Files-microcode-20190514a.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now Best regards Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg ___ 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] targetcli-fb package
Hi Zach, Thank you for answer and your past work. I updated package and made PR on Github Best regards Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg On Fri, 30 Nov 2018, member koni wrote: Hi Marek, It's fine with me if you take the package over. Thank you for checking. ~Zach On Fri, Nov 30, 2018, 5:15 PM Marek Wodzinski ___ 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] targetcli-fb package
Hello, targectli-fb was not updated for 2 years. I tried to contact Zach Lewis more than week ago on e-mail from SBo and also another @hotmail I found somewhere in internet, but I've got no answer. If you agree, I could take care of it :-) Best regards Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg ___ 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 - 20181124.1 - jq checksum error
On Sat, 24 Nov 2018, Willy Sudiarto Raharjo wrote: Sat Nov 24 05:36:19 UTC 2018 system/jq: Updated for version 1.6. From build: Found jq-1.6.tar.gz in /var/cache/sbopkg. Checking MD5SUM: MD5SUM check for jq-1.6.tar.gz ... FAILED! Expected: f5f70ad5dc46d95e0128dc94c25c4d5d Found:e68fbd6a992e36f1ac48c99bbf825d6b Best regards Marek -- "If you want something done...do yourself!" Jean-Baptiste Emmanuel Zorg ___ 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/
