From andrzej at telszewski.com Thu Jun 3 17:54:57 2021 From: andrzej at telszewski.com (Andrzej Telszewski) Date: Thu, 3 Jun 2021 19:54:57 +0200 Subject: [Slackbuilds-users] eagle: Rename to eagle7 Message-ID: <9a3cca62-40ef-2107-9d1f-e1ac6c38449b@telszewski.com> Hi, for *-current*, please rename *eagle* to *eagle7*. Version 7 is the last of it's kind (before Autodesk changed the licensing), so it makes sense to keep it. But it also makes sense to have newer version, following Autodesk releases. FYI, I don't plan on following, as I don't use Eagle anymore. BTW, it served me well I spent significant amount of time with it. Cheers. -- Best regards, Andrzej Telszewski From rshepard at appl-ecosys.com Mon Jun 7 18:18:05 2021 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 7 Jun 2021 11:18:05 -0700 (PDT) Subject: [Slackbuilds-users] Directory name Message-ID: I need to upgrade python3-PyQt5 because the current version cannot access postgresql tables. Attempting to build PyQt5-5.15.4 halts at this error: configure.py: error: '/usr/include/python3.7' is not a directory There is a /usr/include/python2.7/ but a /usr/include/python3.7m/. Why the difference in directory names? Could I rename 3.7m to 3.7? I need to upgrade to build my business tracking application and can't wait for a 15.0. Rich From jvbernts at online.no Mon Jun 7 20:03:00 2021 From: jvbernts at online.no (Jostein Berntsen) Date: Mon, 7 Jun 2021 22:03:00 +0200 Subject: [Slackbuilds-users] Directory name In-Reply-To: References: Message-ID: On 07.06.21,11:18, Rich Shepard wrote: > I need to upgrade python3-PyQt5 because the current version cannot access > postgresql tables. > > Attempting to build PyQt5-5.15.4 halts at this error: > configure.py: error: '/usr/include/python3.7' is not a directory > > There is a /usr/include/python2.7/ but a /usr/include/python3.7m/. Why the > difference in directory names? Could I rename 3.7m to 3.7? > > I need to upgrade to build my business tracking application and can't wait > for a 15.0. > There is a thread on this at this mailing list from last year that might give some input: http://lists.slackbuilds.org/pipermail/slackbuilds-users/2020-April/thread.html#24464 Jostein From rshepard at appl-ecosys.com Mon Jun 7 20:29:14 2021 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 7 Jun 2021 13:29:14 -0700 (PDT) Subject: [Slackbuilds-users] Directory name In-Reply-To: References: Message-ID: On Mon, 7 Jun 2021, Jostein Berntsen wrote: > There is a thread on this at this mailing list from last year that might > give some input: > http://lists.slackbuilds.org/pipermail/slackbuilds-users/2020-April/thread.html#24464 Jostein, My reading of the thread is that python3.7m/ is where things should go ... as far as the PyQt5 version at that time was concerned. Unfortunately, the newer versions of PyQt5 changed and are seeking a python3.7/ include directory. Thanks for the URL. Rich From chris.willing at linux.com Wed Jun 9 12:00:17 2021 From: chris.willing at linux.com (Christoph Willing) Date: Wed, 9 Jun 2021 22:00:17 +1000 Subject: [Slackbuilds-users] Bad character in snappy.info Message-ID: An HTML attachment was scrubbed... URL: From didier at slint.fr Wed Jun 9 12:55:48 2021 From: didier at slint.fr (Didier Spaier) Date: Wed, 9 Jun 2021 14:55:48 +0200 Subject: [Slackbuilds-users] Bad character in snappy.info In-Reply-To: References: Message-ID: <12998839-e04e-7060-37ab-4895c16c51c0@slint.fr> Hi, Le 09/06/2021 ? 14:00, Christoph Willing a ?crit?: > While working on updating HooRex for python 3, I discovered that in > development/snappy/snappy.info, there is an errant character in the > MAINTAINER field. Could someone fix please? > > To see the resulting error when reading that file in python, run the > following python script in the development/snappy directory: > > #!/usr/bin/env python3 > with open('snappy.info', 'r') as f: > ???? txt = f.read() The second character of the maintainer's first name : "M?rio" is a LATIN SMALL LETTER A WITH ACUTE according to UNICODE, in an UTF-8 encoding (U+00DE1 or ?). Which leads to a request. In http://slackbuilds.org/guidelines/ it is written: "It's recommended to use plain ASCII for all files that are being submitted to SBo" However, most languages use characters outside of the ASCII set. Why not allow an UTF-8 encoding, in which all maintainers names can be properly written? Didier From didier at slint.fr Wed Jun 9 12:57:57 2021 From: didier at slint.fr (Didier Spaier) Date: Wed, 9 Jun 2021 14:57:57 +0200 Subject: [Slackbuilds-users] Bad character in snappy.info In-Reply-To: <12998839-e04e-7060-37ab-4895c16c51c0@slint.fr> References: <12998839-e04e-7060-37ab-4895c16c51c0@slint.fr> Message-ID: Erratum: please read U+00E1 Le 09/06/2021 ? 14:55, Didier Spaier a ?crit?: econd character of the maintainer's first name : "M?rio" is a LATIN > SMALL > LETTER A WITH ACUTE according to UNICODE, in an UTF-8 encoding (U+00DE1 > or ?). From chris.willing at linux.com Wed Jun 9 13:23:43 2021 From: chris.willing at linux.com (Christoph Willing) Date: Wed, 9 Jun 2021 23:23:43 +1000 Subject: [Slackbuilds-users] Bad character in snappy.info In-Reply-To: <12998839-e04e-7060-37ab-4895c16c51c0@slint.fr> References: <12998839-e04e-7060-37ab-4895c16c51c0@slint.fr> Message-ID: <0fba1987-be6a-58b8-9cc1-4dddc5d59e3a@linux.com> On 9/6/21 10:55 pm, Didier Spaier wrote: > Hi, > > Le 09/06/2021 ? 14:00, Christoph Willing a ?crit?: >> While working on updating HooRex for python 3, I discovered that in >> development/snappy/snappy.info, there is an errant character in the >> MAINTAINER field. Could someone fix please? >> >> To see the resulting error when reading that file in python, run the >> following python script in the development/snappy directory: >> >> #!/usr/bin/env python3 >> with open('snappy.info', 'r') as f: >> ????? txt = f.read() > > The second character of the maintainer's first name : "M?rio" is a LATIN > SMALL > LETTER A WITH ACUTE according to UNICODE, in an UTF-8 encoding (U+00DE1 > or ?). > > Which leads to a request. In? http://slackbuilds.org/guidelines/ it is > written: > > "It's recommended to use plain ASCII for all files that are being > submitted to > SBo" > > However, most languages use characters outside of the ASCII set. Why not > allow > ?an UTF-8 encoding, in which all maintainers names can be properly written? > As a matter of principle, that would be the right thing to do. However the tools we commonly use to parse SlackBuilds aren't particularly consistent in their dealings with UTF-8. I quickly tried less, cat, elvis, vim, nvi, pico and, of course, my little python3 reader above on that file and found several different interpretations. chris From erich.public at protonmail.com Wed Jun 9 13:45:54 2021 From: erich.public at protonmail.com (Erich Ritz) Date: Wed, 09 Jun 2021 13:45:54 +0000 Subject: [Slackbuilds-users] Bad character in snappy.info In-Reply-To: <12998839-e04e-7060-37ab-4895c16c51c0@slint.fr> References: <12998839-e04e-7060-37ab-4895c16c51c0@slint.fr> Message-ID: On Wednesday, June 9th, 2021 at 5:55 AM, Didier Spaier wrote: > Hi, > > Which leads to a request. In http://slackbuilds.org/guidelines/ it is > written: > > "It's recommended to use plain ASCII for all files that are being > submitted to > SBo" > > However, most languages use characters outside of the ASCII set. Why not > allow > an UTF-8 encoding, in which all maintainers names can be properly written? > > Didier > With Slackware 15.0 switching to a UTF-8 locale by default: Tue Jul 12 03:48:34 UTC 2016 a/etc-14.2-x86_64-8.txz: Rebuilt. In /etc/profile.d/lang.{csh,sh}.new, make en_US.UTF-8 the default locale. I agree I would like to see all files as being encoded in UTF-8. However, in the case of snappy.info it needs to be converted: $ file snappy.info snappy.info: ISO-8859 text I think this is why python is choking on it. Indeed, the webview also can't correctly show the file: https://git.slackbuilds.org/slackbuilds/tree/development/snappy/snappy.info?h=14.2 But using vim locally vim correctly detects the file encoding and displays properly. Erich From jvbernts at online.no Wed Jun 9 14:41:45 2021 From: jvbernts at online.no (Jostein Berntsen) Date: Wed, 9 Jun 2021 16:41:45 +0200 Subject: [Slackbuilds-users] Multitail SlackBuild does not install Message-ID: It seems like the info pointer to the Multitail source package is not working anymore and the package will not install: http://www.vanheusden.com/multitail/multitail-6.5.0.tgz Jostein From matteo.bernardini at gmail.com Wed Jun 9 15:08:23 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 9 Jun 2021 17:08:23 +0200 Subject: [Slackbuilds-users] Bad character in snappy.info In-Reply-To: References: <12998839-e04e-7060-37ab-4895c16c51c0@slint.fr> Message-ID: I save it as utf-8 encoded and pushed it into my branch: thanks for the report and discussion! https://git.slackbuilds.org/slackbuilds/commit/?id=a71a0965 Matteo Il giorno mer 9 giu 2021 alle ore 15:46 Erich Ritz via SlackBuilds-users ha scritto: > > On Wednesday, June 9th, 2021 at 5:55 AM, Didier Spaier wrote: > > > Hi, > > > > Which leads to a request. In http://slackbuilds.org/guidelines/ it is > > written: > > > > "It's recommended to use plain ASCII for all files that are being > > submitted to > > SBo" > > > > However, most languages use characters outside of the ASCII set. Why not > > allow > > an UTF-8 encoding, in which all maintainers names can be properly written? > > > > Didier > > > > With Slackware 15.0 switching to a UTF-8 locale by default: > > Tue Jul 12 03:48:34 UTC 2016 > a/etc-14.2-x86_64-8.txz: Rebuilt. > In /etc/profile.d/lang.{csh,sh}.new, make en_US.UTF-8 the default locale. > > I agree I would like to see all files as being encoded in UTF-8. However, in the case of snappy.info it needs to be converted: > > $ file snappy.info > snappy.info: ISO-8859 text > > I think this is why python is choking on it. Indeed, the webview also can't correctly show the file: > https://git.slackbuilds.org/slackbuilds/tree/development/snappy/snappy.info?h=14.2 > But using vim locally vim correctly detects the file encoding and displays properly. > > Erich > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From sb at rbn.im Wed Jun 9 19:44:38 2021 From: sb at rbn.im (Ruben Schuller) Date: Wed, 9 Jun 2021 21:44:38 +0200 Subject: [Slackbuilds-users] Bad character in snappy.info In-Reply-To: References: <12998839-e04e-7060-37ab-4895c16c51c0@slint.fr> Message-ID: <20210609214438.08b72e91@kiwi.kuchen> hi, 2021-06-09 Erich Ritz via SlackBuilds-users : > On Wednesday, June 9th, 2021 at 5:55 AM, Didier Spaier > wrote: > > > Hi, > > > > Which leads to a request. In http://slackbuilds.org/guidelines/ it > > is written: > > > > "It's recommended to use plain ASCII for all files that are being > > submitted to > > SBo" > > > > However, most languages use characters outside of the ASCII set. > > Why not allow > > an UTF-8 encoding, in which all maintainers names can be properly > > written? > > > > Didier > > > > With Slackware 15.0 switching to a UTF-8 locale by default: > > Tue Jul 12 03:48:34 UTC 2016 > a/etc-14.2-x86_64-8.txz: Rebuilt. > In /etc/profile.d/lang.{csh,sh}.new, make en_US.UTF-8 the > default locale. > > I agree I would like to see all files as being encoded in UTF-8. seconded. > However, in the case of snappy.info it needs to be converted: > > $ file snappy.info > snappy.info: ISO-8859 text > > I think this is why python is choking on it. Indeed, the webview > also can't correctly show the file: > https://git.slackbuilds.org/slackbuilds/tree/development/snappy/snappy.info?h=14.2 > But using vim locally vim correctly detects the file encoding and > displays properly. my experience with python is that it's horrible to deal with encodings in it. python3 isn't better, it just has different modes of failing. converting everything to UTF-8 would help with that as that seems to be the default encoding in python3, at least from what i've read. one still needs to guard any place with exception handling where another encoding _might_ be used. cheers ruben From richard at aaazen.com Thu Jun 10 16:17:03 2021 From: richard at aaazen.com (Richard Narron) Date: Thu, 10 Jun 2021 09:17:03 -0700 (PDT) Subject: [Slackbuilds-users] Bad character in snappy.info In-Reply-To: <12998839-e04e-7060-37ab-4895c16c51c0@slint.fr> References: <12998839-e04e-7060-37ab-4895c16c51c0@slint.fr> Message-ID: On Wed, 9 Jun 2021, Didier Spaier wrote: > Hi, > > Le 09/06/2021 ? 14:00, Christoph Willing a ?crit?: > > While working on updating HooRex for python 3, I discovered that in > > development/snappy/snappy.info, there is an errant character in the > > MAINTAINER field. Could someone fix please? > > > > To see the resulting error when reading that file in python, run the > > following python script in the development/snappy directory: > > > > #!/usr/bin/env python3 > > with open('snappy.info', 'r') as f: > > ???? txt = f.read() > > The second character of the maintainer's first name : "M?rio" is a LATIN > SMALL > LETTER A WITH ACUTE according to UNICODE, in an UTF-8 encoding (U+00DE1 > or ?). > > Which leads to a request. In http://slackbuilds.org/guidelines/ it is > written: > > "It's recommended to use plain ASCII for all files that are being > submitted to > SBo" > > However, most languages use characters outside of the ASCII set. Why not > allow > an UTF-8 encoding, in which all maintainers names can be properly written? If we use UTF-8 for names in Spanish, where does it end? I cannot easily recognize UTF-8 names in Chinese or Thai or Russian or Japanese. My keyboard does not easily support such languages. If we allow UTF-8 names in SlackBuild scripts then how about UTF-8 in documentation and descriptions? Where does it end? I would hope that we keep the English language as a standard for software that I can, read and write and that matches my keyboard. Richard Narron From arnaud.garcia-fernandez at laposte.net Thu Jun 10 16:45:16 2021 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Thu, 10 Jun 2021 18:45:16 +0200 Subject: [Slackbuilds-users] Bad character in snappy.info In-Reply-To: References: <12998839-e04e-7060-37ab-4895c16c51c0@slint.fr> Message-ID: <20210610184516.2f7a0352ece274d0a5deb177@laposte.net> > If we use UTF-8 for names in Spanish, where does it end? > > I cannot easily recognize UTF-8 names in Chinese or Thai or Russian or > Japanese. > > My keyboard does not easily support such languages. > > If we allow UTF-8 names in SlackBuild scripts then how about UTF-8 in > documentation and descriptions? > > Where does it end? > > I would hope that we keep the English language as a standard for > software that I can, read and write and that matches my keyboard. > > Richard Narron Well,mostly, you do not need to write people's names, and you could always easily cut and paste them. So it could stop at them names. To be noted that UTF-8 email addresses are valid, per the standard, so we can't really forbid UTF-8 in EMAIL field, so .info files should be UTF-8 valid, hence MAINTAINER field could also have UTF-8. That being said, as a rule, everything should always work with UTF-8. - Yth. From fernando.lopezjr at gmail.com Thu Jun 10 16:49:37 2021 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 10 Jun 2021 10:49:37 -0600 Subject: [Slackbuilds-users] Bad character in snappy.info In-Reply-To: <20210610184516.2f7a0352ece274d0a5deb177@laposte.net> References: <12998839-e04e-7060-37ab-4895c16c51c0@slint.fr> <20210610184516.2f7a0352ece274d0a5deb177@laposte.net> Message-ID: +1 on UTF-8 On Thu, Jun 10, 2021 at 10:44 AM Arnaud via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > > If we use UTF-8 for names in Spanish, where does it end? > > > > I cannot easily recognize UTF-8 names in Chinese or Thai or Russian or > > Japanese. > > > > My keyboard does not easily support such languages. > > > > If we allow UTF-8 names in SlackBuild scripts then how about UTF-8 in > > documentation and descriptions? > > > > Where does it end? > > > > I would hope that we keep the English language as a standard for > > software that I can, read and write and that matches my keyboard. > > > > Richard Narron > > > Well,mostly, you do not need to write people's names, and you could > always easily cut and paste them. > So it could stop at them names. > > To be noted that UTF-8 email addresses are valid, per the > standard, so > we can't really forbid UTF-8 in EMAIL field, so .info files should be UTF-8 > valid, hence MAINTAINER field could also have UTF-8. > > That being said, as a rule, everything should always work with > UTF-8. > > - Yth. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From spycrowsoft at gmail.com Fri Jun 11 10:44:35 2021 From: spycrowsoft at gmail.com (Spycrowsoft) Date: Fri, 11 Jun 2021 12:44:35 +0200 Subject: [Slackbuilds-users] Bad character in snappy.info In-Reply-To: References: <12998839-e04e-7060-37ab-4895c16c51c0@slint.fr> Message-ID: <4622c5b8-ff2c-4efb-51b7-b3b59f9ec071@gmail.com> Op 10-06-2021 om 18:17 schreef Richard Narron: > If we use UTF-8 for names in Spanish, where does it end? > I cannot easily recognize UTF-8 names in Chinese or Thai or Russian or > Japanese. SBo could require that Japanese names can be required to be transliterated into Romaji form . However real Japanese names are written in kanji. The problem here is that while different kanji may be pronounced the same (and therefore they can also map onto the same romaji-string) while in the Japanese script, these different symbols refer to different persons. Therefore, if you only have the romaji representation while you don't have the name as it is written in the Japanese script, you'll have a hard time tracking down the person and or verifying that you have found that particular person if the need should arise. So you should just use the Japanese or Chinese representation for the names. Please note that Chinese also has the exact same problems. (the terminology for "kanji and romaji" is "hanzi and pinyin" for Chinese, so the Chinese languages behave the same in this regard) A fix might be to request that Chinese and Japanese people include both a transliterated name and a name in their native script. But for matters of accountability or the acknowledgement of merit, there is no way around writing the names in their native script. Therefore, I don't see any other appropriate solution than using UTF-8. > My keyboard does not easily support such languages. If you run "chmod +x /etc/profile.d/scim.*sh" and do some configuration your keyboard does support Japanese and Chinese characters. I use SCIM on Slackware 14.2 on a regular basis. > If we allow UTF-8 names in SlackBuild scripts then how about UTF-8 in > documentation and descriptions? > > Where does it end? I hope that it's clear that this issue should have been resolved years ago and that there's really no way around UTF8 anymore. It should just be implemented and used by default. Slackware 15 apparently uses it by default so that's the direction in which things are moving. We should be thinking about how we are going to support UTF8 as well, because UTF8 is going to be the default that will be used everywhere whether we like it or not. However, I am also aware that quite a lot of software is still incapable of processing UTF-8 properly and that this might cause problems in the actual .SlackBuild scripts and documentation-files at the time of writing. So as a compromise I propose that we use UTF8 for the .info files, but allow the use of ASCII in the scripts for now. If we combine this with a kanji and a transliterated version of the names written in Japanese, Chinese, etc. we can properly allocate merit and accountability without having to worry about this right now. Note that this solution is not a permanent one. Its main benefit would be that it provides us with a proper amount of time to come up with something better. > I would hope that we keep the English language as a standard for > software that I can, read and write and that matches my keyboard. I understand your desire for "Keep It Simple Stupid", but I just don't see a way around UTF8 anymore if SBo, Slackware and Linux in general, want to stay relevant for the next 10 years. This map really drives the home the point about the enormous number (billions) of people in Asia and those aren't the only people which use a writing system that cannot be expressed adequately through ASCII, because these problems also apply to Dutch (my native language), French, German, Polish, Swedish, Norwegian, Italian and many more. If we are not going to support them, we're going to get marginalized and replaced in less than a decade by something which does support their native languages. Spycrowsoft -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard at aaazen.com Sat Jun 12 20:35:25 2021 From: richard at aaazen.com (Richard Narron) Date: Sat, 12 Jun 2021 13:35:25 -0700 (PDT) Subject: [Slackbuilds-users] Bad character in snappy.info In-Reply-To: <20210610184516.2f7a0352ece274d0a5deb177@laposte.net> References: <12998839-e04e-7060-37ab-4895c16c51c0@slint.fr> <20210610184516.2f7a0352ece274d0a5deb177@laposte.net> Message-ID: On Thu, 10 Jun 2021, Arnaud via SlackBuilds-users wrote: > > If we use UTF-8 for names in Spanish, where does it end? > > > > I cannot easily recognize UTF-8 names in Chinese or Thai or Russian or > > Japanese. > > > > My keyboard does not easily support such languages. > > > > If we allow UTF-8 names in SlackBuild scripts then how about UTF-8 in > > documentation and descriptions? > > > > Where does it end? > > > > I would hope that we keep the English language as a standard for > > software that I can, read and write and that matches my keyboard. > > > > Richard Narron > > > Well,mostly, you do not need to write people's names, and you could > always easily cut and paste them. > So it could stop at them names. I do not use UTF-8 much. So cutting and pasting do not work for me. > To be noted that UTF-8 email addresses are valid, per the standard, so > we can't really forbid UTF-8 in EMAIL field, so .info files should be UTF-8 > valid, hence MAINTAINER field could also have UTF-8. > > That being said, as a rule, everything should always work with UTF-8. I think there are two issues. One is using UTF-8 for data which I have no problem with and two using UTF-8 for programming code. I feel that adding characters to computer language character sets (c, c++, perl, python, bash) just makes them more complex and harder to understand and debug. So if the issue is whether or not to allow UTF-8 in bash scripts, then I vote no. Richard Narron From rworkman at slackbuilds.org Sun Jun 13 01:59:49 2021 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 12 Jun 2021 20:59:49 -0500 Subject: [Slackbuilds-users] K-Line on Freenode Message-ID: <20210612205949.1a872165@home.rlworkman.net> Consider the SBo and Slackware freenode IRC channels dead. I was K-Lined earlier today, apparenly for simply existing: 00:33 [freenode] -!- You are banned from this server- Courtesy of Phanes/Bagira (2021/6/13 01.33) 00:33 [freenode] -!- ERROR Closing Link: mirrors.slackware.com (K-Lined) 00:33 [freenode] -!- Irssi: Connection lost to irc.freenode.net There is personal history between he and I, but I was (and still am) content to let the past stay in the past, but... oh well. We're on the libera.chat network now. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From hitest at gmail.com Sun Jun 13 02:20:51 2021 From: hitest at gmail.com (George Nielsen) Date: Sat, 12 Jun 2021 19:20:51 -0700 Subject: [Slackbuilds-users] K-Line on Freenode In-Reply-To: <20210612205949.1a872165@home.rlworkman.net> References: <20210612205949.1a872165@home.rlworkman.net> Message-ID: Good riddance to freenode. I've happily moved to Libera. George AKA. hitest On Sat, Jun 12, 2021, 7:00 PM Robby Workman wrote: > Consider the SBo and Slackware freenode IRC channels dead. > > I was K-Lined earlier today, apparenly for simply existing: > > 00:33 [freenode] -!- You are banned from this server- Courtesy of > Phanes/Bagira (2021/6/13 01.33) > 00:33 [freenode] -!- ERROR Closing Link: mirrors.slackware.com (K-Lined) > 00:33 [freenode] -!- Irssi: Connection lost to irc.freenode.net > > There is personal history between he and I, but I was (and still am) > content to let the past stay in the past, but... oh well. > > We're on the libera.chat network now. > > -RW > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Mon Jun 14 04:16:13 2021 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 13 Jun 2021 23:16:13 -0500 Subject: [Slackbuilds-users] K-Line on Freenode In-Reply-To: <20210612205949.1a872165@home.rlworkman.net> References: <20210612205949.1a872165@home.rlworkman.net> Message-ID: <20210613231613.13067ea1@home.rlworkman.net> On Sat, 12 Jun 2021 20:59:49 -0500 Robby Workman wrote: > Consider the SBo and Slackware freenode IRC channels dead. > > I was K-Lined earlier today, apparenly for simply existing: > > 00:33 [freenode] -!- You are banned from this server- Courtesy of > Phanes/Bagira (2021/6/13 01.33) 00:33 [freenode] -!- ERROR Closing > Link: mirrors.slackware.com (K-Lined) 00:33 [freenode] -!- Irssi: > Connection lost to irc.freenode.net > > There is personal history between he and I, but I was (and still am) > content to let the past stay in the past, but... oh well. > > We're on the libera.chat network now. Apologies for the bad grammar -- it should read "between me and him" or "between him and me" -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Mon Jun 14 06:24:19 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 14 Jun 2021 13:24:19 +0700 Subject: [Slackbuilds-users] Changes in wxGTK3 Message-ID: <204e43ab-5789-60c4-957a-3213813af279@slackbuilds.org> Hi, i have pushed a change in wxGTK3 to use GTK+3 instead of GTK+2 and will only enable webkit support if webkit2gtk is available on the system. This might impact some of the scripts you maintain below academic/boinc academic/wxMaxima audio/sooperlooper development/codeblocks development/codelite development/poedit development/wxHexEditor games/SLADE games/dfarc games/fs2open games/golly games/odamex games/pcsx2 games/vbam gis/opencpn gis/saga-gis graphics/hugin graphics/tintii graphics/urbanlightscape ham/freedv libraries/wxPython3 libraries/wxsvg libraries/xylib multimedia/aegisub multimedia/spek network/filezilla system/passwordsafe system/veracrypt -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Mon Jun 14 12:46:34 2021 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 14 Jun 2021 05:46:34 -0700 (PDT) Subject: [Slackbuilds-users] K-Line on Freenode In-Reply-To: <20210613231613.13067ea1@home.rlworkman.net> References: <20210612205949.1a872165@home.rlworkman.net> <20210613231613.13067ea1@home.rlworkman.net> Message-ID: On Sun, 13 Jun 2021, Robby Workman wrote: > Apologies for the bad grammar -- it should read "between me and him" or > "between him and me" That's okay, Robby. It seems to me that pronouns have become a major focus of many people. Why, I don't know, but even LinkedIn offers an opportunity for subscribers to express their preferred pronouns. Me? I could care less. There are more important things in life. Stay well, Rich From simotrone at gmail.com Tue Jun 15 11:31:22 2021 From: simotrone at gmail.com (Simotrone) Date: Tue, 15 Jun 2021 13:31:22 +0200 Subject: [Slackbuilds-users] ledger and utfcpp slackbuild Message-ID: Hi all. Hi Lionel. I am the maintainer of ledger slackbuild. I recently received a couple of emails reporting me that ledger is not building as expected. After an investigation, I discovered that the utfcpp dependency ( http://slackbuilds.org/repository/14.2/libraries/utfcpp/ ) need to be update. The current version of utfcpp in sbo repo is 2.1 but on sourcefire is possibile to get the 2.3.4 - https://sourceforge.net/projects/utfcpp/ . I confirm the ledger sbo package build well and without changes with the utfcpp v2.3.4 installed. @Lionel: Is it possibile to update the utfcpp version? Thanks for your attention. Simone -------------- next part -------------- An HTML attachment was scrubbed... URL: From belka at caraus.de Wed Jun 16 18:32:22 2021 From: belka at caraus.de (Eugen Wissner) Date: Wed, 16 Jun 2021 20:32:22 +0200 Subject: [Slackbuilds-users] brace expansion Message-ID: <20210616183222.zkkpoq2qzsgmboqa@slave.caraus.de> Many Slackbuilds use brace expansion (mkdir {a,b}), which is a bashism. Can we fix this? I would help with patches if the change is desirable. You can get an approximated list of the affected Slackbuilds with grep -l -r --include='*.SlackBuild' '\{[[:alpha:]]\+,[[:alpha:]]\+' . executed from the slackbuilds repository. Current list (471): ./haskell/haskell-exceptions/haskell-exceptions.SlackBuild ./ruby/gem2tgz/gem2tgz.SlackBuild ./ham/SoapyRemote/SoapyRemote.SlackBuild ./ham/gsmlib/gsmlib.SlackBuild ./ham/gqrx-sdr/gqrx-sdr.SlackBuild ./ham/csdr/csdr.SlackBuild ./development/dmd/dmd.SlackBuild ./development/kdiff3/kdiff3.SlackBuild ./development/d-tools/d-tools.SlackBuild ./development/jdk14/jdk14.SlackBuild ./development/kelbt/kelbt.SlackBuild ./development/eclipse-platform/eclipse-platform.SlackBuild ./development/argouml/argouml.SlackBuild ./development/gprolog/gprolog.SlackBuild ./development/cf-cli/cf-cli.SlackBuild ./development/atom/atom.SlackBuild ./development/rstudio-desktop/rstudio-desktop.SlackBuild ./development/jasspa/jasspa.SlackBuild ./development/tea/tea.SlackBuild ./development/jdk12/jdk12.SlackBuild ./development/groovy/groovy.SlackBuild ./development/gisto/gisto.SlackBuild ./development/jdk11/jdk11.SlackBuild ./development/jdk15/jdk15.SlackBuild ./development/squirrel-sql/squirrel-sql.SlackBuild ./development/valgrind/valgrind.SlackBuild ./development/jdk/jdk.SlackBuild ./development/kotlin/kotlin.SlackBuild ./development/qt-creator-llvm/qt-creator-llvm.SlackBuild ./development/arduino/arduino.SlackBuild ./development/Arduino/Arduino.SlackBuild ./development/sonarqube/sonarqube.SlackBuild ./development/libbitcoin/libbitcoin.SlackBuild ./development/nwjs/nwjs.SlackBuild ./development/grails/grails.SlackBuild ./development/hopper/hopper.SlackBuild ./development/processing/processing.SlackBuild ./development/nexus/nexus.SlackBuild ./development/casperjs/casperjs.SlackBuild ./development/gambas3/gambas3.SlackBuild ./development/couchdb/couchdb.SlackBuild ./development/adoptopenjdk-openj9/adoptopenjdk-openj9.SlackBuild ./development/npm2tgz/npm2tgz.SlackBuild ./development/lua/lua.SlackBuild ./development/smlnj/smlnj.SlackBuild ./development/jbake/jbake.SlackBuild ./development/jdk13/jdk13.SlackBuild ./development/sourcenav/sourcenav.SlackBuild ./development/gitstats/gitstats.SlackBuild ./development/lazarus/lazarus.SlackBuild ./development/scala/scala.SlackBuild ./development/crystal-lang/crystal-lang.SlackBuild ./development/apache-maven/apache-maven.SlackBuild ./development/pip2tgz/pip2tgz.SlackBuild ./development/LLgen/LLgen.SlackBuild ./development/jdk16/jdk16.SlackBuild ./development/rapidsvn/rapidsvn.SlackBuild ./development/mysql-pinba/mysql-pinba.SlackBuild ./python/apprise/apprise.SlackBuild ./python/pydot/pydot.SlackBuild ./python/simplejson/simplejson.SlackBuild ./python/python-distutils-extra/python-distutils-extra.SlackBuild ./games/digger/digger.SlackBuild ./games/4digits/4digits.SlackBuild ./games/empire/empire.SlackBuild ./games/pipewalker/pipewalker.SlackBuild ./games/robotfindskitten/robotfindskitten.SlackBuild ./games/xye/xye.SlackBuild ./games/gl-117/gl-117.SlackBuild ./games/invasion3d/invasion3d.SlackBuild ./games/scid/scid.SlackBuild ./games/KoboDeluxe/KoboDeluxe.SlackBuild ./games/vkQuake/vkQuake.SlackBuild ./games/frogatto/frogatto.SlackBuild ./games/glPortal/glPortal.SlackBuild ./games/mangband/mangband.SlackBuild ./games/pingus/pingus.SlackBuild ./games/ppsspp/ppsspp.SlackBuild ./games/tworld/tworld.SlackBuild ./games/an/an.SlackBuild ./games/openarena/openarena.SlackBuild ./games/iortcw/iortcw.SlackBuild ./games/lightyears/lightyears.SlackBuild ./games/lbreakout2/lbreakout2.SlackBuild ./games/neverball/neverball.SlackBuild ./games/sauerbraten/sauerbraten.SlackBuild ./games/oolite/oolite.SlackBuild ./games/moria/moria.SlackBuild ./games/onscripter/onscripter.SlackBuild ./games/speed-dreams/speed-dreams.SlackBuild ./games/bluez-sixaxis/bluez-sixaxis.SlackBuild ./games/ioquake3/ioquake3.SlackBuild ./games/ggmud/ggmud.SlackBuild ./games/darkplaces/darkplaces.SlackBuild ./games/blobby2/blobby2.SlackBuild ./games/loemu/loemu.SlackBuild ./games/brainparty/brainparty.SlackBuild ./games/o2em/o2em.SlackBuild ./games/njam/njam.SlackBuild ./games/pengupop/pengupop.SlackBuild ./games/uqm/uqm.SlackBuild ./games/warsow/warsow.SlackBuild ./games/SpaceZero/SpaceZero.SlackBuild ./games/angband/angband.SlackBuild ./games/atari++/atari++.SlackBuild ./games/opensonic/opensonic.SlackBuild ./games/widelands/widelands.SlackBuild ./games/brutalchess/brutalchess.SlackBuild ./games/abuse/abuse.SlackBuild ./games/yamagi-quake2/yamagi-quake2.SlackBuild ./games/fillets-ng/fillets-ng.SlackBuild ./games/Scorched3D/Scorched3D.SlackBuild ./games/rezerwar/rezerwar.SlackBuild ./games/xonotic/xonotic.SlackBuild ./games/stone_soup/stone_soup.SlackBuild ./games/chroma/chroma.SlackBuild ./system/ttf-arphic-uming/ttf-arphic-uming.SlackBuild ./system/graphite-web/graphite-web.SlackBuild ./system/virtualbox-kernel/virtualbox-kernel.SlackBuild ./system/herculesstudio/herculesstudio.SlackBuild ./system/sakura/sakura.SlackBuild ./system/smart/smart.SlackBuild ./system/virtualbox-addons/virtualbox-addons.SlackBuild ./system/setconf/setconf.SlackBuild ./system/cpu-g/cpu-g.SlackBuild ./system/image-analyzer/image-analyzer.SlackBuild ./system/sdltrs/sdltrs.SlackBuild ./system/xcdroast/xcdroast.SlackBuild ./system/CNS11643-font/CNS11643-font.SlackBuild ./system/pcsc-lite/pcsc-lite.SlackBuild ./system/bareos/bareos.SlackBuild ./system/pbzip2/pbzip2.SlackBuild ./system/virtualbox/virtualbox.SlackBuild ./system/nagvis/nagvis.SlackBuild ./system/fslint/fslint.SlackBuild ./system/nvidia-legacy340-driver/nvidia-legacy340-driver.SlackBuild ./system/cronie/cronie.SlackBuild ./system/osinfo-db/osinfo-db.SlackBuild ./system/nvidia-driver/nvidia-driver.SlackBuild ./system/dymo-cups-drivers/dymo-cups-drivers.SlackBuild ./system/tkdvd/tkdvd.SlackBuild ./system/displaylink/displaylink.SlackBuild ./system/clamtk/clamtk.SlackBuild ./system/lbench/lbench.SlackBuild ./system/newLd/newLd.SlackBuild ./system/ZoneMinder/ZoneMinder.SlackBuild ./system/daemontools-bin/daemontools-bin.SlackBuild ./system/nagios-plugins/nagios-plugins.SlackBuild ./system/Type1_to_OTF/Type1_to_OTF.SlackBuild ./system/udiskie/udiskie.SlackBuild ./system/mkslack/mkslack.SlackBuild ./system/c-icap/c-icap.SlackBuild ./system/nvidia-legacy390-driver/nvidia-legacy390-driver.SlackBuild ./system/qControlCenter/qControlCenter.SlackBuild ./system/ft2demos/ft2demos.SlackBuild ./system/socklog/socklog.SlackBuild ./system/bacula/bacula.SlackBuild ./system/hercules/hercules.SlackBuild ./system/rndaddentropy/rndaddentropy.SlackBuild ./system/ttf-ipaex/ttf-ipaex.SlackBuild ./system/multitail/multitail.SlackBuild ./system/flSynclient/flSynclient.SlackBuild ./system/driconf/driconf.SlackBuild ./system/vice/vice.SlackBuild ./system/freefont/freefont.SlackBuild ./system/fakeroot/fakeroot.SlackBuild ./system/symbola-font-ttf/symbola-font-ttf.SlackBuild ./system/ttf-open-sans/ttf-open-sans.SlackBuild ./system/fsvs/fsvs.SlackBuild ./system/icinga-web/icinga-web.SlackBuild ./system/ossec-local/ossec-local.SlackBuild ./system/lirc/lirc.SlackBuild ./system/mbootpack/mbootpack.SlackBuild ./system/argyllcms/argyllcms.SlackBuild ./system/webmin/webmin.SlackBuild ./system/nmtree/nmtree.SlackBuild ./system/linux-libertine-fonts/linux-libertine-fonts.SlackBuild ./system/wqy-microhei-font-ttf/wqy-microhei-font-ttf.SlackBuild ./system/kafka/kafka.SlackBuild ./system/runit/runit.SlackBuild ./system/xtrs/xtrs.SlackBuild ./system/cwtex-q-fonts-TTFs/cwtex-q-fonts-TTFs.SlackBuild ./system/spman/spman.SlackBuild ./system/oracle-xe/oracle-xe.SlackBuild ./system/ttf-inconsolata/ttf-inconsolata.SlackBuild ./system/fish/fish.SlackBuild ./system/apache-tomcat/apache-tomcat.SlackBuild ./system/fwupdate/fwupdate.SlackBuild ./system/apache-activemq/apache-activemq.SlackBuild ./system/courier-prime/courier-prime.SlackBuild ./system/nvidia-legacy304-driver/nvidia-legacy304-driver.SlackBuild ./system/i8kutils/i8kutils.SlackBuild ./system/ossec-agent/ossec-agent.SlackBuild ./system/atop/atop.SlackBuild ./system/gtklp/gtklp.SlackBuild ./system/kexec-tools/kexec-tools.SlackBuild ./system/ossec-server/ossec-server.SlackBuild ./system/mucommander/mucommander.SlackBuild ./system/rabbitmq-server/rabbitmq-server.SlackBuild ./system/cndrvcups-capt/cndrvcups-capt.SlackBuild ./system/ttf-charis-sil/ttf-charis-sil.SlackBuild ./system/freeswitch/freeswitch.SlackBuild ./system/zookeeper/zookeeper.SlackBuild ./system/daemontools/daemontools.SlackBuild ./system/intel-microcode/intel-microcode.SlackBuild ./system/ttf-paratype-pt-fonts/ttf-paratype-pt-fonts.SlackBuild ./system/cdemu-client/cdemu-client.SlackBuild ./system/icingaweb2/icingaweb2.SlackBuild ./system/xen/xen.SlackBuild ./system/qdirstat/qdirstat.SlackBuild ./system/wine-staging/wine-staging.SlackBuild ./misc/goldencheetah/goldencheetah.SlackBuild ./misc/yubikey-personalization-gui/yubikey-personalization-gui.SlackBuild ./misc/bdf2psf/bdf2psf.SlackBuild ./misc/BISP/BISP.SlackBuild ./misc/pmw/pmw.SlackBuild ./misc/asterixInspector/asterixInspector.SlackBuild ./misc/discount/discount.SlackBuild ./misc/weather/weather.SlackBuild ./misc/readesm/readesm.SlackBuild ./misc/ophcrack/ophcrack.SlackBuild ./misc/dcc/dcc.SlackBuild ./misc/xapian-omega/xapian-omega.SlackBuild ./office/smoffice2016/smoffice2016.SlackBuild ./office/pdftk/pdftk.SlackBuild ./office/vym/vym.SlackBuild ./office/kbbi-qt/kbbi-qt.SlackBuild ./office/wink/wink.SlackBuild ./office/devtodo/devtodo.SlackBuild ./office/hunspell-pl/hunspell-pl.SlackBuild ./office/ganttproject/ganttproject.SlackBuild ./office/freemind/freemind.SlackBuild ./office/LibreOffice/LibreOffice.SlackBuild ./office/texstudio/texstudio.SlackBuild ./office/SOGo/SOGo.SlackBuild ./office/fop/fop.SlackBuild ./office/scribus/scribus.SlackBuild ./office/text2pdf/text2pdf.SlackBuild ./office/calibre/calibre.SlackBuild ./office/ProjectLibre/ProjectLibre.SlackBuild ./office/kchmviewer-qt/kchmviewer-qt.SlackBuild ./office/broffice.org/broffice.org.SlackBuild ./office/adobe-reader/adobe-reader.SlackBuild ./office/libreoffice/libreoffice.SlackBuild ./office/ding/ding.SlackBuild ./office/latex2rtf/latex2rtf.SlackBuild ./office/texmaker/texmaker.SlackBuild ./office/gbgoffice/gbgoffice.SlackBuild ./network/shorewall/shorewall.SlackBuild ./network/pflogsumm/pflogsumm.SlackBuild ./network/LOIC/LOIC.SlackBuild ./network/slack/slack.SlackBuild ./network/mumble/mumble.SlackBuild ./network/hydra/hydra.SlackBuild ./network/havp/havp.SlackBuild ./network/dnscrypt-wrapper/dnscrypt-wrapper.SlackBuild ./network/exim/exim.SlackBuild ./network/jboss-as/jboss-as.SlackBuild ./network/siege/siege.SlackBuild ./network/c-toxcore/c-toxcore.SlackBuild ./network/pound/pound.SlackBuild ./network/dokuwiki/dokuwiki.SlackBuild ./network/jabberd2/jabberd2.SlackBuild ./network/snort/snort.SlackBuild ./network/sylpheed/sylpheed.SlackBuild ./network/mod_chroot/mod_chroot.SlackBuild ./network/icinga2/icinga2.SlackBuild ./network/putty/putty.SlackBuild ./network/bitcoin/bitcoin.SlackBuild ./network/syncthing/syncthing.SlackBuild ./network/sshguard/sshguard.SlackBuild ./network/wildfly/wildfly.SlackBuild ./network/fail2ban/fail2ban.SlackBuild ./network/pCloudDrive/pCloudDrive.SlackBuild ./network/shorewall6/shorewall6.SlackBuild ./network/vuze/vuze.SlackBuild ./network/airpwn/airpwn.SlackBuild ./network/squid/squid.SlackBuild ./network/murmur/murmur.SlackBuild ./network/lighttpd/lighttpd.SlackBuild ./network/dnstracer/dnstracer.SlackBuild ./network/bsflite/bsflite.SlackBuild ./network/bitlbee/bitlbee.SlackBuild ./network/gns3/gns3.SlackBuild ./network/firehol/firehol.SlackBuild ./network/netqmail/netqmail.SlackBuild ./network/arno-iptables-firewall/arno-iptables-firewall.SlackBuild ./network/b43-fwcutter/b43-fwcutter.SlackBuild ./network/bluejeans/bluejeans.SlackBuild ./network/spambayes/spambayes.SlackBuild ./network/vmware-horizon-client/vmware-horizon-client.SlackBuild ./network/graphite-carbon/graphite-carbon.SlackBuild ./network/snmptt/snmptt.SlackBuild ./network/wireshark/wireshark.SlackBuild ./network/dogecoin/dogecoin.SlackBuild ./network/udns/udns.SlackBuild ./network/opera-legacy/opera-legacy.SlackBuild ./network/pexip-infinity-connect/pexip-infinity-connect.SlackBuild ./network/tor/tor.SlackBuild ./network/freerapid/freerapid.SlackBuild ./network/policyd2/policyd2.SlackBuild ./network/serialmail/serialmail.SlackBuild ./network/amavisd-new/amavisd-new.SlackBuild ./network/toxcore/toxcore.SlackBuild ./network/dobbscoin/dobbscoin.SlackBuild ./network/qutebrowser-tox/qutebrowser-tox.SlackBuild ./network/transgui/transgui.SlackBuild ./network/fdns/fdns.SlackBuild ./network/mldonkey/mldonkey.SlackBuild ./network/rejik/rejik.SlackBuild ./gis/OTB/OTB.SlackBuild ./gis/google-earth/google-earth.SlackBuild ./graphics/brlcad/brlcad.SlackBuild ./graphics/mitsuba/mitsuba.SlackBuild ./graphics/gpaint/gpaint.SlackBuild ./graphics/whyteboard/whyteboard.SlackBuild ./graphics/SweetHome3D/SweetHome3D.SlackBuild ./graphics/ldglite/ldglite.SlackBuild ./graphics/LDView/LDView.SlackBuild ./graphics/xpe/xpe.SlackBuild ./graphics/tgif-QPL/tgif-QPL.SlackBuild ./graphics/gtkam/gtkam.SlackBuild ./graphics/LDraw_data/LDraw_data.SlackBuild ./graphics/meshlab/meshlab.SlackBuild ./graphics/librecad/librecad.SlackBuild ./graphics/ufraw/ufraw.SlackBuild ./graphics/k3d/k3d.SlackBuild ./graphics/fritzing/fritzing.SlackBuild ./graphics/zgv/zgv.SlackBuild ./graphics/VariCAD/VariCAD.SlackBuild ./graphics/Alchemy/Alchemy.SlackBuild ./libraries/stfl/stfl.SlackBuild ./libraries/tinyxml/tinyxml.SlackBuild ./libraries/libgme/libgme.SlackBuild ./libraries/jbigkit/jbigkit.SlackBuild ./libraries/gsm/gsm.SlackBuild ./libraries/libmusicbrainz3/libmusicbrainz3.SlackBuild ./libraries/libnova/libnova.SlackBuild ./libraries/libnet/libnet.SlackBuild ./libraries/freealut/freealut.SlackBuild ./libraries/ftplib/ftplib.SlackBuild ./libraries/ftgl/ftgl.SlackBuild ./libraries/libffado/libffado.SlackBuild ./libraries/SQLObject/SQLObject.SlackBuild ./libraries/manubulon-snmp-plugins/manubulon-snmp-plugins.SlackBuild ./libraries/php-pgsql/php-pgsql.SlackBuild ./libraries/libmediainfo/libmediainfo.SlackBuild ./libraries/libpgf/libpgf.SlackBuild ./libraries/libbson/libbson.SlackBuild ./libraries/ptypes/ptypes.SlackBuild ./libraries/flatbuffers/flatbuffers.SlackBuild ./libraries/wxPython4/wxPython4.SlackBuild ./libraries/barry/barry.SlackBuild ./libraries/libconfig/libconfig.SlackBuild ./libraries/libmusicbrainz5/libmusicbrainz5.SlackBuild ./libraries/pgplot/pgplot.SlackBuild ./libraries/wxPython/wxPython.SlackBuild ./libraries/libmspack/libmspack.SlackBuild ./libraries/mysql++/mysql++.SlackBuild ./libraries/libr3/libr3.SlackBuild ./libraries/libftdi1/libftdi1.SlackBuild ./libraries/wxPython3/wxPython3.SlackBuild ./perl/perl-Test-MockObject/perl-Test-MockObject.SlackBuild ./multimedia/aom/aom.SlackBuild ./multimedia/opencaster/opencaster.SlackBuild ./multimedia/AtomicParsley/AtomicParsley.SlackBuild ./multimedia/dvdrip/dvdrip.SlackBuild ./multimedia/LBRY/LBRY.SlackBuild ./multimedia/xvst/xvst.SlackBuild ./multimedia/spotify/spotify.SlackBuild ./multimedia/mythtv/mythtv.SlackBuild ./multimedia/transcode/transcode.SlackBuild ./desktop/gtk1-theme-switch/gtk1-theme-switch.SlackBuild ./desktop/vertex-maia-themes/vertex-maia-themes.SlackBuild ./desktop/numix-folders/numix-folders.SlackBuild ./desktop/gtk-engines/gtk-engines.SlackBuild ./desktop/wmMoonClock/wmMoonClock.SlackBuild ./desktop/Surfn/Surfn.SlackBuild ./desktop/macopix/macopix.SlackBuild ./desktop/wmSun/wmSun.SlackBuild ./desktop/wmCalClock/wmCalClock.SlackBuild ./desktop/murrine-themes/murrine-themes.SlackBuild ./desktop/vim-qt/vim-qt.SlackBuild ./desktop/wmSunMoon/wmSunMoon.SlackBuild ./desktop/dbgl-legacy/dbgl-legacy.SlackBuild ./desktop/e16/e16.SlackBuild ./desktop/gtk1-industrial-engine/gtk1-industrial-engine.SlackBuild ./desktop/LX-Colors-Revival/LX-Colors-Revival.SlackBuild ./desktop/tint2/tint2.SlackBuild ./desktop/hushboard/hushboard.SlackBuild ./desktop/oomox/oomox.SlackBuild ./academic/mendeleydesktop/mendeleydesktop.SlackBuild ./academic/copasi/copasi.SlackBuild ./academic/paml/paml.SlackBuild ./academic/sage-bin/sage-bin.SlackBuild ./academic/TreeGraph/TreeGraph.SlackBuild ./academic/wehi-weasel/wehi-weasel.SlackBuild ./academic/aliview/aliview.SlackBuild ./academic/staden/staden.SlackBuild ./academic/seaview/seaview.SlackBuild ./academic/samtools-legacy/samtools-legacy.SlackBuild ./academic/ladr/ladr.SlackBuild ./academic/wehi-deid/wehi-deid.SlackBuild ./academic/genpak/genpak.SlackBuild ./academic/amplicon/amplicon.SlackBuild ./academic/parmetis/parmetis.SlackBuild ./academic/aline/aline.SlackBuild ./academic/bibus/bibus.SlackBuild ./academic/fastqc/fastqc.SlackBuild ./academic/ds9/ds9.SlackBuild ./academic/karma/karma.SlackBuild ./academic/Data2FCS/Data2FCS.SlackBuild ./academic/isoelectric-point/isoelectric-point.SlackBuild ./academic/reduce-algebra/reduce-algebra.SlackBuild ./academic/plasmidomics/plasmidomics.SlackBuild ./academic/zotero/zotero.SlackBuild ./academic/wehi-hackit/wehi-hackit.SlackBuild ./academic/FCSalyzer/FCSalyzer.SlackBuild ./academic/chemtool/chemtool.SlackBuild ./academic/wehi-cellsymphony/wehi-cellsymphony.SlackBuild ./academic/SeqMonk/SeqMonk.SlackBuild ./academic/root/root.SlackBuild ./academic/arka/arka.SlackBuild ./academic/treebest-ensembl/treebest-ensembl.SlackBuild ./academic/qucs/qucs.SlackBuild ./academic/xephem/xephem.SlackBuild ./academic/EMBOSS/EMBOSS.SlackBuild ./academic/gp2fasta/gp2fasta.SlackBuild ./academic/tuxtype2/tuxtype2.SlackBuild ./academic/lpsolve/lpsolve.SlackBuild ./academic/perlprimer/perlprimer.SlackBuild ./academic/megax/megax.SlackBuild ./academic/jalview/jalview.SlackBuild ./academic/cld2/cld2.SlackBuild ./academic/archaeopteryx/archaeopteryx.SlackBuild ./academic/treeviewx/treeviewx.SlackBuild ./academic/xcircuit/xcircuit.SlackBuild ./academic/finchtv/finchtv.SlackBuild ./academic/grace/grace.SlackBuild ./academic/clustalx/clustalx.SlackBuild ./academic/scilab/scilab.SlackBuild ./academic/amplifx/amplifx.SlackBuild ./academic/lalnview/lalnview.SlackBuild ./academic/sequence-analysis/sequence-analysis.SlackBuild ./academic/sage/sage.SlackBuild ./academic/topdraw/topdraw.SlackBuild ./academic/pamlX/pamlX.SlackBuild ./academic/boinc/boinc.SlackBuild ./academic/iTest/iTest.SlackBuild ./academic/fiji/fiji.SlackBuild ./academic/QtiPlot/QtiPlot.SlackBuild ./academic/IGV/IGV.SlackBuild ./audio/japa/japa.SlackBuild ./audio/sbagen/sbagen.SlackBuild ./audio/fabla/fabla.SlackBuild ./audio/sunvox/sunvox.SlackBuild ./audio/clthreads/clthreads.SlackBuild ./audio/faac/faac.SlackBuild ./audio/ardour/ardour.SlackBuild ./audio/grip2/grip2.SlackBuild ./audio/a2jmidid/a2jmidid.SlackBuild ./audio/fantasia/fantasia.SlackBuild ./audio/waon/waon.SlackBuild ./audio/luppp/luppp.SlackBuild ./audio/schismtracker/schismtracker.SlackBuild ./audio/clxclient/clxclient.SlackBuild ./audio/tuxguitar/tuxguitar.SlackBuild ./audio/milkytracker/milkytracker.SlackBuild ./audio/ncmpc/ncmpc.SlackBuild ./audio/rezound/rezound.SlackBuild ./audio/id3v2/id3v2.SlackBuild From yalhcru at gmail.com Wed Jun 16 18:55:55 2021 From: yalhcru at gmail.com (B Watson) Date: Wed, 16 Jun 2021 14:55:55 -0400 Subject: [Slackbuilds-users] brace expansion In-Reply-To: <20210616183222.zkkpoq2qzsgmboqa@slave.caraus.de> References: <20210616183222.zkkpoq2qzsgmboqa@slave.caraus.de> Message-ID: On 6/16/21, Eugen Wissner wrote: > Many Slackbuilds use brace expansion (mkdir {a,b}), which is a bashism. > Can we fix this? I would help with patches if the change is desirable. What makes you say it's broken and needs fixing? SlackBuild scripts have #!/bin/sh at the top, yes. But they only have to work on Slackware. And, /bin/sh on Slackware *has to be* a symlink to /bin/bash. If you don't believe me, try changing it to ash, ksh, or zsh, then rebooting the box. Personally I'd prefer if SlackBuild scripts started with #!/bin/bash, but when I used to submit them that way, the admins would change it back to #!/bin/sh. So I quit worrying about it, and the world didn't end. Now, if the use of bashisms actually caused real problems (build failures), that would be worth looking into. But changing a bunch of scripts just to comply with what amounts to OCD... IMO not worth even thinking about. I'm just one opinionated guy though. What does the rest of the list think? From belka at caraus.de Wed Jun 16 19:09:19 2021 From: belka at caraus.de (Eugen Wissner) Date: Wed, 16 Jun 2021 21:09:19 +0200 Subject: [Slackbuilds-users] brace expansion In-Reply-To: References: <20210616183222.zkkpoq2qzsgmboqa@slave.caraus.de> Message-ID: <20210616190919.5svynvcn32hyob6n@slave.caraus.de> I changed /bin/sh to /bin/dash on all my machines months ago and it works perfectly. My patch to slackpkg to replace /bin/sh with /bin/bash was accepted. Pat changed /bin/sh to /bin/bash in all rc-scripts, so they work with other shells. So there is an ongoing effort to make everything work with other shells. Currently I get random build errors and have to restart the script with "bash xyz.SlackBuild" to see if it fixes the problem. On Wed, Jun 16, 2021 at 02:55:55PM -0400, B Watson wrote: > On 6/16/21, Eugen Wissner wrote: > > Many Slackbuilds use brace expansion (mkdir {a,b}), which is a bashism. > > Can we fix this? I would help with patches if the change is desirable. > > What makes you say it's broken and needs fixing? > > SlackBuild scripts have #!/bin/sh at the top, yes. But they only have > to work on Slackware. And, /bin/sh on Slackware *has to be* a symlink > to /bin/bash. If you don't believe me, try changing it to ash, ksh, > or zsh, then rebooting the box. > > Personally I'd prefer if SlackBuild scripts started with #!/bin/bash, > but when I used to submit them that way, the admins would change it > back to #!/bin/sh. So I quit worrying about it, and the world didn't > end. > > Now, if the use of bashisms actually caused real problems (build > failures), that would be worth looking into. But changing a bunch of > scripts just to comply with what amounts to OCD... IMO not worth even > thinking about. > > I'm just one opinionated guy though. What does the rest of the list > think? > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From spycrowsoft at gmail.com Wed Jun 16 19:51:41 2021 From: spycrowsoft at gmail.com (Spycrowsoft) Date: Wed, 16 Jun 2021 21:51:41 +0200 Subject: [Slackbuilds-users] brace expansion In-Reply-To: <20210616190919.5svynvcn32hyob6n@slave.caraus.de> References: <20210616183222.zkkpoq2qzsgmboqa@slave.caraus.de> <20210616190919.5svynvcn32hyob6n@slave.caraus.de> Message-ID: Op 16-06-2021 om 21:09 schreef Eugen Wissner: > Pat changed /bin/sh to /bin/bash in all > rc-scripts, so they work with other shells. We should confirm this with Patrick Volderding, but if he's doing that, my take on the matters is: "Follow what the BDFL is doing". The fact that the SlackBuild contains a pointer to the right shell also makes sense to me. From jebrhansen+SBo at gmail.com Wed Jun 16 22:56:25 2021 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Wed, 16 Jun 2021 16:56:25 -0600 Subject: [Slackbuilds-users] brace expansion In-Reply-To: References: <20210616183222.zkkpoq2qzsgmboqa@slave.caraus.de> <20210616190919.5svynvcn32hyob6n@slave.caraus.de> Message-ID: On Wed, Jun 16, 2021, 1:51 PM Spycrowsoft wrote: > > Op 16-06-2021 om 21:09 schreef Eugen Wissner: > > Pat changed /bin/sh to /bin/bash in all > > rc-scripts, so they work with other shells. > > We should confirm this with Patrick Volderding, but if he's doing that, > my take on the matters is: "Follow what the BDFL is doing". > > The fact that the SlackBuild contains a pointer to the right shell also > makes sense to me. > Here's the changelog entry. a/sysvinit-scripts-15.0-noarch-2.txz: Rebuilt. Use #!/bin/bash for these scripts so that bashisms don't cause script issues if /bin/sh is some other shell. Thanks to mumahendras3. rc.S: Use GazL's proposals for detecting/mounting /proc and /sys. I'd prefer to allow bashisms and just use a /bin/bash shebang with the SlackBuilds. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From mumahendras3 at gmail.com Wed Jun 16 22:57:20 2021 From: mumahendras3 at gmail.com (Muhammad Mahendra Subrata) Date: Thu, 17 Jun 2021 05:57:20 +0700 Subject: [Slackbuilds-users] brace expansion In-Reply-To: References: <20210616183222.zkkpoq2qzsgmboqa@slave.caraus.de> <20210616190919.5svynvcn32hyob6n@slave.caraus.de> Message-ID: Yeah, I also use dash as my /bin/sh and I sometimes encounter this and it's a little annoying to be honest. I mean, if you already use /bin/sh as the shebang line, technically you are expected to write POSIX-compliant shell scripts, even though it will still work correctly when having /bin/sh linked to bash. Not trying to bash on the maintainers here (thanks for all the hard work!), It's just a little bit unfortunate. I personally prefer that the scripts are updated to not use the brace expansion so I can use a more lightweight shell to run the script :D. But, I understand that some scripts are too complex to be converted to POSIX-compliant ones so it's just easier to use /bin/bash as the shebang line, like what Mr. Volkerding did with some of Slackware's core utilities. I'm happy with either decision, as long as I can rest assured that no scripts will fail randomly because of using the wrong shell :D. MMS On Thu, Jun 17, 2021, 02:51 Spycrowsoft wrote: > > Op 16-06-2021 om 21:09 schreef Eugen Wissner: > > Pat changed /bin/sh to /bin/bash in all > > rc-scripts, so they work with other shells. > > We should confirm this with Patrick Volderding, but if he's doing that, > my take on the matters is: "Follow what the BDFL is doing". > > The fact that the SlackBuild contains a pointer to the right shell also > makes sense to me. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From klaatu at mixedsignals.ml Thu Jun 17 01:54:01 2021 From: klaatu at mixedsignals.ml (Klaatu) Date: Thu, 17 Jun 2021 13:54:01 +1200 Subject: [Slackbuilds-users] brace expansion In-Reply-To: References: <20210616183222.zkkpoq2qzsgmboqa@slave.caraus.de> Message-ID: <2749744.kcDKJTPgTH@beast> On Thursday, June 17, 2021 6:55:55 AM NZST B Watson wrote: > I'm just one opinionated guy though. What does the rest of the list > think? The standard is that SlackBuilds.org expects a full install of Slackware. So I think the scripts should be allowed to feature Bashisms, and that Bash should be an expected requirement of a .SlackBuild script (because Slackware ships with Bash.) As long as the shell required ships with Slackware, script authors should update the #! line to accurately reflect the shell their script requires (or if unsure, then to the shell they have tested.) From duncan_roe at optusnet.com.au Thu Jun 17 07:35:41 2021 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Thu, 17 Jun 2021 17:35:41 +1000 Subject: [Slackbuilds-users] brace expansion In-Reply-To: References: <20210616183222.zkkpoq2qzsgmboqa@slave.caraus.de> <20210616190919.5svynvcn32hyob6n@slave.caraus.de> Message-ID: <20210617073541.GL14223@dimstar.local.net> On Wed, Jun 16, 2021 at 09:51:41PM +0200, Spycrowsoft wrote: > > Op 16-06-2021 om 21:09 schreef Eugen Wissner: > > Pat changed /bin/sh to /bin/bash in all > > rc-scripts, so they work with other shells. > > We should confirm this with Patrick Volderding, but if he's doing that, my > take on the matters is: "Follow what the BDFL is doing". > Yes it's fine to start *rc* scripts wih #!/bin/bash. All other scripts should start #!/bin/bash -p The reason being, plain /bin/bash will import functions from the environment. These functions will supplant commands of the same name (e.g. rm, mkdir). /bin/bash -p does not import functions. Cheers ... Duncan. From andrzej at telszewski.com Thu Jun 17 10:33:16 2021 From: andrzej at telszewski.com (Andrzej Telszewski) Date: Thu, 17 Jun 2021 12:33:16 +0200 Subject: [Slackbuilds-users] brace expansion In-Reply-To: References: <20210616183222.zkkpoq2qzsgmboqa@slave.caraus.de> <20210616190919.5svynvcn32hyob6n@slave.caraus.de> Message-ID: <4c4f62ef-8270-525d-1def-081f72b4dd5a@telszewski.com> On 6/17/21 12:56 AM, Jeremy Hansen wrote: > I'd prefer to allow bashisms and just use a /bin/bash shebang with the > SlackBuilds. I second that. From alik at ejik.org Fri Jun 25 16:26:44 2021 From: alik at ejik.org (Alexander Verbovetsky) Date: Fri, 25 Jun 2021 19:26:44 +0300 Subject: [Slackbuilds-users] pdfstudio and pdfstudioviewer up for grabs Message-ID: <58bba8b2-9d27-466b-8e9b-9c462ee7fad8@www.fastmail.com> Hello, pdfstudio/pdfstudioviewer upstream stopped providing deb packages, now the only option is a Windows style installer written in Java. I think that repackaging this installer is too tedious, so I want to put them for grabs (or deletion). Best regards, Alexander From dchmelik at gmail.com Sat Jun 26 23:23:51 2021 From: dchmelik at gmail.com (David Chmelik) Date: Sat, 26 Jun 2021 16:23:51 -0700 Subject: [Slackbuilds-users] gtk-chtheme Message-ID: <253fa6eb-3212-a315-3ffe-49f05e353b85@gmail.com> I reported a gtk-chtheme bug to the SlackBuild maintainer.? He says he can't help because he no longer uses Slackware. From yalhcru at gmail.com Sun Jun 27 16:55:46 2021 From: yalhcru at gmail.com (B Watson) Date: Sun, 27 Jun 2021 12:55:46 -0400 Subject: [Slackbuilds-users] gtk-chtheme In-Reply-To: <253fa6eb-3212-a315-3ffe-49f05e353b85@gmail.com> References: <253fa6eb-3212-a315-3ffe-49f05e353b85@gmail.com> Message-ID: On 6/26/21, David Chmelik wrote: > I reported a gtk-chtheme bug to the SlackBuild maintainer. He says he > can't help because he no longer uses Slackware. Basically 2 choices here: 1. Fix the bug (whatever it is) and take over as maintainer of gtk-chtheme. 2. Wait (possibly forever?) for someone on this mailing list to take over as maintainer. If you're taking this approach, it would be good to let the list know what the actual bug is. Submissions are still closed, so you have some time to think about it. From dchmelik at gmail.com Sun Jun 27 21:59:18 2021 From: dchmelik at gmail.com (David Chmelik) Date: Sun, 27 Jun 2021 14:59:18 -0700 Subject: [Slackbuilds-users] gtk-chtheme In-Reply-To: References: <253fa6eb-3212-a315-3ffe-49f05e353b85@gmail.com> Message-ID: <1ae4cd56-df7c-1d9f-9c34-61ab0a6739b5@gmail.com> On 6/27/21 9:55 AM, B Watson wrote: > On 6/26/21, David Chmelik wrote: >> I reported a gtk-chtheme bug to the SlackBuild maintainer. He says he >> can't help because he no longer uses Slackware. > Basically 2 choices here: > > 1. Fix the bug (whatever it is) and take over as maintainer of > gtk-chtheme. > > 2. Wait (possibly forever?) for someone on this mailing list to > take over as maintainer. If you're taking this approach, it would > be good to let the list know what the actual bug is. ??? I'm not taking it over. ??? There's a gtk-chtheme bug: if you select a theme (such as light theme) further down the list, then have to scroll back up to a dark theme (like Blackbird, near the top,) then it only turns on some parts of the dark theme and not others.? If you had chosen a theme (such as light theme) near the top (like Akasha) so didn't need to scroll, only then will the dark theme have all aspects turned on. However I want to use a light theme near the end of the list (oxygen-gtk) so always have to scroll up and always have this problem. From thomas at beingboiled.info Tue Jun 29 11:17:15 2021 From: thomas at beingboiled.info (Thomas Morper) Date: Tue, 29 Jun 2021 13:17:15 +0200 (CEST) Subject: [Slackbuilds-users] pdfstudio and pdfstudioviewer up for grabs In-Reply-To: <58bba8b2-9d27-466b-8e9b-9c462ee7fad8@www.fastmail.com> References: <58bba8b2-9d27-466b-8e9b-9c462ee7fad8@www.fastmail.com> Message-ID: <25f5b49-8de0-8585-22c1-27ed54a65da1@beingboiled.info> On Fri, 25 Jun 2021, Alexander Verbovetsky wrote: > pdfstudio/pdfstudioviewer upstream stopped providing deb packages The download page still looks like there might be a debian package, ?To install PDF Studio on multiple computers through command-line, you may use our 64 bit Debian package (right-click and save link as)?, but the download link is broken. I e-mailed their support about this, and as expected the answer was utterly useless, simply stating "there is no Debian package", completely ignoring the info and the broken link from the download page. I guess that's it then. -- From alik at ejik.org Tue Jun 29 11:35:42 2021 From: alik at ejik.org (Alexander Verbovetsky) Date: Tue, 29 Jun 2021 14:35:42 +0300 Subject: [Slackbuilds-users] pdfstudio and pdfstudioviewer up for grabs In-Reply-To: <25f5b49-8de0-8585-22c1-27ed54a65da1@beingboiled.info> References: <58bba8b2-9d27-466b-8e9b-9c462ee7fad8@www.fastmail.com> <25f5b49-8de0-8585-22c1-27ed54a65da1@beingboiled.info> Message-ID: <850211624965775@mail.yandex.ru> An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Tue Jun 29 16:51:06 2021 From: yalhcru at gmail.com (B Watson) Date: Tue, 29 Jun 2021 12:51:06 -0400 Subject: [Slackbuilds-users] pdfstudio and pdfstudioviewer up for grabs In-Reply-To: <850211624965775@mail.yandex.ru> References: <58bba8b2-9d27-466b-8e9b-9c462ee7fad8@www.fastmail.com> <25f5b49-8de0-8585-22c1-27ed54a65da1@beingboiled.info> <850211624965775@mail.yandex.ru> Message-ID: On 6/29/21, Alexander Verbovetsky wrote: > > Two years ago they already dropped the deb-packages, I wrote to the > support, they asked me why I want debs and restored them. This year the > answer was: "Not at this time." Are the old deb package versions no longer useful? I mean will they still install and run using your SlackBuild? And does the license allow redistributing the .deb packages? We have copies of them on sbosrcarch: https://slackware.uk/sbosrcarch/by-md5/d/4/d4b8f062f90d191a7fca0b003101e772/PDFStudio_v2020_4_0_linux64.deb https://slackware.uk/sbosrcarch/by-md5/5/4/54b767608e88afdeeeb7292c278624c2/PDFStudio_v2020_4_0_linux.deb If someone installs those, do they work in demo mode? Is it possible to register that version of the software to run them in standard/pro modes? I'd say don't remove pdfstudio unless the last .deb version is useless. From alik at ejik.org Tue Jun 29 21:27:55 2021 From: alik at ejik.org (Alexander Verbovetsky) Date: Wed, 30 Jun 2021 00:27:55 +0300 Subject: [Slackbuilds-users] pdfstudio and pdfstudioviewer up for grabs In-Reply-To: References: <58bba8b2-9d27-466b-8e9b-9c462ee7fad8@www.fastmail.com> <25f5b49-8de0-8585-22c1-27ed54a65da1@beingboiled.info> <850211624965775@mail.yandex.ru> Message-ID: <871721625000884@mail.yandex.ru> An HTML attachment was scrubbed... URL: