From willysr at slackbuilds.org Sat May 1 10:25:44 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 1 May 2021 17:25:44 +0700 Subject: [Slackbuilds-users] linphone 404 not found In-Reply-To: References: Message-ID: > > From a month ago or so that I first mentioned to the list and yourself, > there are still [a few] '404 not found' being returned for source > packages re:linphone > > e.g. from slackbuilds page: > https://www.linphone.org/releases/sources/linphone/linphone-3.12.0.tar.gz > > Is it still being maintained, or is it in hand ? Hi Habs, It seems the maintainer is no longer active would you mind taking over this script? -- 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 gen-bch at useyouresp.org.uk Sun May 2 09:01:44 2021 From: gen-bch at useyouresp.org.uk (Habs) Date: Sun, 2 May 2021 10:01:44 +0100 (BST) Subject: [Slackbuilds-users] linphone 404 not found In-Reply-To: References: Message-ID: <7sp82p34-4284-or90-n03p-1421rq71r2q@hfrlbherfc.bet.hx> On Sat, 1 May 2021, Willy Sudiarto Raharjo wrote: >> >> From a month ago or so that I first mentioned to the list and yourself, >> there are still [a few] '404 not found' being returned for source >> packages re:linphone >> >> e.g. from slackbuilds page: >> https://www.linphone.org/releases/sources/linphone/linphone-3.12.0.tar.gz >> >> Is it still being maintained, or is it in hand ? > > Hi Habs, > > It seems the maintainer is no longer active > would you mind taking over this script? > > > > -- > Willy Sudiarto Raharjo > Hello there Willy Thank you for the info. I am not sure that "would you mind" is the issue (it isn't). I do not believe I have the skills in compilation etc, being unashamedly just a 'user' of the very much appreciated work that you and others put in to this project for everyone. I realise this doesn't help any. I will, however, spend some time looking at the script maintenance process to see what's involved, but in the mean time, hopefully some one better enabled can take it on if it [linphone] is in demand*. Regards, peace and best wishes Habs *(I wonder how much SIP/Linphone is used, as other messaging apps have somewhat taken over). --- Sent using Alpine/Pine, probably the best MUA --- My Tox Messaging Id: 9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925 https://tox.chat/ From wedinm at gmail.com Sun May 2 11:51:42 2021 From: wedinm at gmail.com (M Wedin) Date: Sun, 2 May 2021 13:51:42 +0200 Subject: [Slackbuilds-users] linphone 404 not found In-Reply-To: <7sp82p34-4284-or90-n03p-1421rq71r2q@hfrlbherfc.bet.hx> References: <7sp82p34-4284-or90-n03p-1421rq71r2q@hfrlbherfc.bet.hx> Message-ID: > > *(I wonder how much SIP/Linphone is used, as other messaging apps have > somewhat taken over). > I use it Wedin -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackcoder at server.ky Sun May 2 13:30:42 2021 From: slackcoder at server.ky (Slack Coder) Date: Sun, 2 May 2021 08:30:42 -0500 Subject: [Slackbuilds-users] Jansson SlackBuild uses unofficial mirror In-Reply-To: References: Message-ID: <34b57326-3d94-039e-8c45-00770f1d3f55@server.ky> On 4/28/21 8:49 AM, Matteo Bernardini wrote: > it might happen that the official mirror is unreachable (for various > reasons) so, in these cases, the download link is updated with some > mirror locations: this is most probably what is happened with jansson > (that was submitted with the official download link on SBo). > > in any case that's actually not a problem as long as the md5sum of the > file is the same (and in this case it is). Thanks Matteo, >From what I understand, the md5 hash is used to check whether file has been changed by the author and not for security purposes.? Therefore shouldn't the official source be used when its available? From yalhcru at gmail.com Sun May 2 16:08:19 2021 From: yalhcru at gmail.com (B Watson) Date: Sun, 2 May 2021 12:08:19 -0400 Subject: [Slackbuilds-users] Jansson SlackBuild uses unofficial mirror In-Reply-To: <34b57326-3d94-039e-8c45-00770f1d3f55@server.ky> References: <34b57326-3d94-039e-8c45-00770f1d3f55@server.ky> Message-ID: On 5/2/21, Slack Coder wrote: > > From what I understand, the md5 hash is used to check whether file has > been changed by the author and not for security purposes. Therefore > shouldn't the official source be used when its available? What happens a lot of the time: the original download link becomes unreachable for some reason. So someone (the script maintainer, or an SBo admin) finds a working link and updates the .info file. Then later on, the original link starts working again, but nobody changes the .info file back. This happens because of the "If it ain't broke, don't fix it" principle. Ideally, the script maintainer would check the official site when he does a version update. This doesn't always happen: sometimes he just edits the URL and changes the version number. So long as the new URL works, nobody's going to notice or care that it's not the official download site. From belka at caraus.de Sun May 2 16:28:01 2021 From: belka at caraus.de (Eugen Wissner) Date: Sun, 2 May 2021 18:28:01 +0200 Subject: [Slackbuilds-users] Jansson SlackBuild uses unofficial mirror In-Reply-To: References: <34b57326-3d94-039e-8c45-00770f1d3f55@server.ky> Message-ID: <20210502162801.tpzskfk3g5ocdrxu@slave.caraus.de> And other people avoid sites that may regenerate tarballs like GitHub, because GitHub changed the md5 sums in the past and it broke a lot of .info files. On Sun, May 02, 2021 at 12:08:19PM -0400, B Watson wrote: > On 5/2/21, Slack Coder wrote: > > > > From what I understand, the md5 hash is used to check whether file has > > been changed by the author and not for security purposes. Therefore > > shouldn't the official source be used when its available? > > What happens a lot of the time: the original download link becomes > unreachable for some reason. So someone (the script maintainer, or > an SBo admin) finds a working link and updates the .info file. Then > later on, the original link starts working again, but nobody changes > the .info file back. This happens because of the "If it ain't broke, > don't fix it" principle. > > Ideally, the script maintainer would check the official site when he > does a version update. This doesn't always happen: sometimes he just > edits the URL and changes the version number. So long as the new URL > works, nobody's going to notice or care that it's not the official > download site. > _______________________________________________ > 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 belka at caraus.de Mon May 3 20:37:00 2021 From: belka at caraus.de (Eugen Wissner) Date: Mon, 3 May 2021 22:37:00 +0200 Subject: [Slackbuilds-users] My -current scripts In-Reply-To: <20210417061837.cbyqqnc4vmbrpzm4@slave.caraus.de> References: <20210417061837.cbyqqnc4vmbrpzm4@slave.caraus.de> Message-ID: <20210503203700.oyjlssuj2okslssk@slave.caraus.de> I've just pushed the hhvm update to the latest LTS release to my branch. php-apcu builds and works on current; I'll push an update after the Slackware release. Eugen On Sat, Apr 17, 2021 at 08:18:37AM +0200, Eugen Wissner wrote: > Hi, > > I would like to ask to remove the following SlackBuilds: > > - gcc-d: Part of Slackware current > - gkrellm-volume: The home page and download link are dead, I'm not sure > if this software still exists > - oniguruma: In Slackware current > - opendbx: It builds on current, but opendbx doesn't seem to be active, > the last release was in 2012 and nothing depends on it. > - tanya: It is my own development; I wasn't working on it a lot in the > last time and I'm not sure I will. Anyway it is not the best way to > build D dependencies. > > I don't use the following SlackBuilds anymore. I will maintain them if > someone needs them, but it would be great if they can be removed or find > a new maintainer who can update them on a regular basis: > > - ioncube-loader: It probably builds on current, but it won't work > since it should be updated for PHP 7. > - psi > - universal-ctags: Language servers replaced this one in the most cases > > The following scripts work on current: > - composer > - d-tools > - dmd > > I'll try to update php-apcu and hhvm next week. > > On my production server with Slackware current I have modified versions > of the following scripts: > > - colm > - dovecot-pigeonhole > - hyperscan > - php-pgsql > - ragel > > The reason I have them is that I couldn't build them at some point. > Maybe I'm just ignorant and some problems where already fixed. Just for > the case some of the maintainers struggle with an update, clone > git://caraus.tech/pub/slackbuilder.git and look into private/ directory. > Here is the web view: > https://www.caraus.tech/projects/pub-slackbuilds/repository/26/revisions/master/show/private > I have dovecot-pgsql and postfix-pgsql there if someone uses dovecot and > postfix with PostgreSQL since the SBo's scripts support PostgreSQL, but > the slackware's ones don't. > > Eugen > _______________________________________________ > 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 slackalaxy at gmail.com Mon May 3 20:57:35 2021 From: slackalaxy at gmail.com (Petar Petrov) Date: Mon, 3 May 2021 23:57:35 +0300 Subject: [Slackbuilds-users] My SlackBuilds on -current Message-ID: Hi, as I notified in IRC, I am updating and testing my script on 15.0beta: https://github.com/slackalaxy/15beta for now I am checking if things build on x86_64 and I already went through all. There are a few issues reported in the README that I will still investigate in the next few days. Hope this makes things a bit easier for you. best, Petar From didier at slint.fr Tue May 4 11:39:10 2021 From: didier at slint.fr (Didier Spaier) Date: Tue, 4 May 2021 13:39:10 +0200 Subject: [Slackbuilds-users] (re)naming of Python software Message-ID: <31e1ff50-ea20-cc58-ceba-886dd136d12a@slint.fr> Hello, Now that Python 2 is end-of-life and its support ended how should we handle the naming of Python packages? I'd be tempted to us python for python3 packages and packages still built against both 2 and 3 and python2 when built against python2 only. I ask as I am in the process of upgrading Python3 in Slint to 3.9.x (I won't wait until Slackware 15 be released because we ship 3.5.9, really too old) and would like that the naming in Slint be consistent with the one in SBo to help users check if a software "packaged" by SBo is included in Slint and avoid installing a software twice. Also, how to best handle the transition in case of a renaming? Cheers, Didier From arnaud.garcia-fernandez at laposte.net Tue May 4 13:08:32 2021 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Tue, 04 May 2021 13:08:32 +0000 Subject: [Slackbuilds-users] (re)naming of Python software In-Reply-To: <31e1ff50-ea20-cc58-ceba-886dd136d12a@slint.fr> References: <31e1ff50-ea20-cc58-ceba-886dd136d12a@slint.fr> Message-ID: <80322754-02BC-4D81-B40D-B186B88E29C3@laposte.net> I'm working on a lot of python stuff too. And I do agree : Python3 by default Python3 MoDuLe is named python-module Python2 MoDuLe is named python2-module Python Software is named software (like mercurial for example) It seems it is often pertinent de separate both because requirements differs, even if the version is the same fir Python 2 and 3. That being said, I'd be glad to rename my different python MoDuLe called MoDuLe for consistency. - Arnaud. Le May 4, 2021 11:39:10 AM UTC, Didier Spaier a ?crit : >Hello, > >Now that Python 2 is end-of-life and its support ended how should we >handle the >naming of Python packages? I'd be tempted to us python for python3 >packages and >packages still built against both 2 and 3 and python2 when built >against >python2 only. > >I ask as I am in the process of upgrading Python3 in Slint to 3.9.x (I >won't >wait until Slackware 15 be released because we ship 3.5.9, really too >old) and >would like that the naming in Slint be consistent with the one in SBo >to >help >users check if a software "packaged" by SBo is included in Slint and >avoid >installing a software twice. > >Also, how to best handle the transition in case of a renaming? > >Cheers, >Didier >_______________________________________________ >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 thomas at beingboiled.info Tue May 4 17:36:43 2021 From: thomas at beingboiled.info (Thomas Morper) Date: Tue, 4 May 2021 19:36:43 +0200 (CEST) Subject: [Slackbuilds-users] Exim 4.94.2 security upgrade Message-ID: Hello there, Today Exim 4.94.2 was released, fixing a number of local and remote vulnerabilities. An upgrade is highly recommened. See the announcement for full details and additional information for users of versions older than 4.94: Announcement: https://marc.info/?l=exim-users&m=162013704804315&w=2 Because submissions are closed there won't be an official update of my SlackBuild for some time, but you can either use the existing SlackBuild setting VERSION accordingly or get an updated SlackBuild from here: https://www.beingboiled.info/file/exim-4.94.2-SlackBuild.tar.gz Cheers! -- From matteo.bernardini at gmail.com Tue May 4 17:52:54 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 4 May 2021 19:52:54 +0200 Subject: [Slackbuilds-users] Exim 4.94.2 security upgrade In-Reply-To: References: Message-ID: thanks Thomas, I pushed this in my git branch that will be merged on git's master branch. Matteo Il giorno mar 4 mag 2021 alle ore 19:37 Thomas Morper ha scritto: > > Hello there, > > Today Exim 4.94.2 was released, fixing a number of local and remote > vulnerabilities. An upgrade is highly recommened. > > See the announcement for full details and additional information for users > of versions older than 4.94: > > Announcement: https://marc.info/?l=exim-users&m=162013704804315&w=2 > > Because submissions are closed there won't be an official update of my > SlackBuild for some time, but you can either use the existing SlackBuild > setting VERSION accordingly or get an updated SlackBuild from here: > > https://www.beingboiled.info/file/exim-4.94.2-SlackBuild.tar.gz > > Cheers! > > -- > _______________________________________________ > 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 skaendo at linuxmail.org Tue May 4 22:54:16 2021 From: skaendo at linuxmail.org (Edward Ender) Date: Wed, 5 May 2021 00:54:16 +0200 Subject: [Slackbuilds-users] (re)naming of Python software In-Reply-To: <80322754-02BC-4D81-B40D-B186B88E29C3@laposte.net> References: <31e1ff50-ea20-cc58-ceba-886dd136d12a@slint.fr> <80322754-02BC-4D81-B40D-B186B88E29C3@laposte.net> Message-ID: An HTML attachment was scrubbed... URL: From spycrowsoft at gmail.com Wed May 5 09:31:54 2021 From: spycrowsoft at gmail.com (Spycrowsoft) Date: Wed, 5 May 2021 11:31:54 +0200 Subject: [Slackbuilds-users] (re)naming of Python software In-Reply-To: References: <31e1ff50-ea20-cc58-ceba-886dd136d12a@slint.fr> <80322754-02BC-4D81-B40D-B186B88E29C3@laposte.net> Message-ID: Given Slackware's long release cycles implied by its release philosophy (when it's done) and the fact that there is already talk about python 4 buzzing around, I can see the value of "just sticking a version number on it". It's almost a certainty that we will see one or maybe even two new major versions of Python in the Slackware 15 era. The duplicity might be worthwhile, because we will end up with multiple simultaneous versions in the repository anyway. Spycrowsoft Op 05-05-2021 om 00:54 schreef Edward Ender: > Personally, I like and use python2- for python 2 libs, and python3- > for python 3 libs?while python software has no prefix. I generally > avoid mixing them unless absolutely required like python-caja, there I > dont use a number.?I think that in the distant future when python 4 > arrives?this will make it easier to transition, and easier to just > dump the previous versions. It may seem like almost duplicating > scripts, but I have managed to ditch *all* my own python2 scripts for > -current. > But this is only my personal preference. > *Sent:*?Tuesday, May 04, 2021 at 8:08 AM > *From:*?"Arnaud via SlackBuilds-users" > *To:*?"SlackBuilds.org Users List" > *Cc:*?"Arnaud" > *Subject:*?Re: [Slackbuilds-users] (re)naming of Python software > I'm working on a lot of python stuff too. > And I do agree : > Python3 by default > Python3 MoDuLe is named python-module > Python2 MoDuLe is named python2-module > Python Software is named software (like mercurial for example) > > It seems it is often pertinent de separate both because requirements > differs, even if the version is the same fir Python 2 and 3. > > That being said, I'd be glad to rename my different python MoDuLe > called MoDuLe for consistency. > > - Arnaud. > Le May 4, 2021 11:39:10 AM UTC, Didier Spaier a ?crit : > > Hello, > > Now that Python 2 is end-of-life and its support ended how should we > handle the > naming of Python packages? I'd be tempted to us python for python3 > packages and > packages still built against both 2 and 3 and python2 when built against > python2 only. > > I ask as I am in the process of upgrading Python3 in Slint to 3.9.x (I won't > wait until Slackware 15 be released because we ship 3.5.9, really too > old) and > would like that the naming in Slint be consistent with the one in SBo to > help > users check if a software "packaged" by SBo is included in Slint and avoid > installing a software twice. > > Also, how to best handle the transition in case of a renaming? > > Cheers, > Didier > > ------------------------------------------------------------------------ > 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/ > > > -- > _______________________________________________ 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/ > > _______________________________________________ > 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 ozan.turkyilmaz at gmail.com Thu May 6 08:05:31 2021 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Thu, 6 May 2021 11:05:31 +0300 Subject: [Slackbuilds-users] (re)naming of Python software In-Reply-To: <31e1ff50-ea20-cc58-ceba-886dd136d12a@slint.fr> References: <31e1ff50-ea20-cc58-ceba-886dd136d12a@slint.fr> Message-ID: Hello All, I look from this point: If something only works with python2 then we should mark it. Same goes for any modules. If it works with both python2 and python3 then no real need for marking. Couple of my python software added patches for dropping python2 support actually. Regards, Ozan -------------- next part -------------- An HTML attachment was scrubbed... URL: From higuita at GMX.net Sun May 9 01:11:29 2021 From: higuita at GMX.net (higuita) Date: Sun, 9 May 2021 02:11:29 +0100 Subject: [Slackbuilds-users] My -current scripts In-Reply-To: <20210417061837.cbyqqnc4vmbrpzm4@slave.caraus.de> References: <20210417061837.cbyqqnc4vmbrpzm4@slave.caraus.de> Message-ID: <20210509021129.431c60a9@couracado.motaleite.net> Hi > - gkrellm-volume: The home page and download link are dead, I'm not sure > if this software still exists The site looks like was lost, but it still exists in other places: https://aur.archlinux.org/packages/gkrellm-volume/ https://packages.debian.org/sid/gkrellm-volume Both have the source for the plugin Best regards higuita -- Naturally the common people don't want war... but after all it is the leaders of a country who determine the policy, and it is always a simple matter to drag the people along, whether it is a democracy, or a fascist dictatorship, or a parliament, or a communist dictatorship. Voice or no voice, the people can always be brought to the bidding of the leaders. That is easy. All you have to do is tell them they are being attacked, and denounce the pacifists for lack of patriotism and exposing the country to danger. It works the same in every country. -- Hermann Goering, Nazi and war criminal, 1883-1946 From jdashiel at panix.com Sun May 9 20:31:41 2021 From: jdashiel at panix.com (Jude DaShiell) Date: Sun, 9 May 2021 16:31:41 -0400 Subject: [Slackbuilds-users] djgpp cross compiler for slackware Message-ID: Does anyone know if this is in the works? The dosemu2 package needs it and https://github.com/dosemu2/comcom32 built so it will work. For now dosemu2 is missing at least comcom32 and maybe other parts as well. I tried editing the Makefile for comcom32 and making it but it needs dos.h from the djgpp environment to get past the error I got and maybe other things than that too. What I don't yet know how to do in C is to discover what a package wanted to use from a missing library so maybe the right #include line could be given to make a port compile possible. The original dosemu1.x package is no longer supported on linux-msdos at vger.kernel.org which is a reason to upgrade the version but in doing so this comcom32 package is a new dependency. I don't know expected difficulty level or time requirements to do a port of dosemu2/comcom32 out of djgpp and into gcc either. From yalhcru at gmail.com Sun May 9 20:35:02 2021 From: yalhcru at gmail.com (B Watson) Date: Sun, 9 May 2021 16:35:02 -0400 Subject: [Slackbuilds-users] djgpp cross compiler for slackware In-Reply-To: References: Message-ID: On 5/9/21, Jude DaShiell wrote: > > I don't know expected difficulty level or time requirements to do a port > of dosemu2/comcom32 out of djgpp and into gcc either. You could punt: Find prebuilt dosemu2 and/or comcom32 packages for some other distro (e.g. debian), and extract/repack the binaries into a Slackware package. From jdashiel at panix.com Sun May 9 22:22:06 2021 From: jdashiel at panix.com (Jude DaShiell) Date: Sun, 9 May 2021 18:22:06 -0400 Subject: [Slackbuilds-users] djgpp cross compiler for slackware In-Reply-To: References: Message-ID: dosemu2/comcom32 will build in debian and even in debian it uses a djgpp-to-gcc cross compiler. Same thing with archlinux that has a djgpp-to-gcc cross compiler. So punting will be difficult. On Sun, 9 May 2021, B Watson wrote: > On 5/9/21, Jude DaShiell wrote: > > > > I don't know expected difficulty level or time requirements to do a port > > of dosemu2/comcom32 out of djgpp and into gcc either. > > You could punt: Find prebuilt dosemu2 and/or comcom32 packages for > some other distro (e.g. debian), and extract/repack the binaries into > a Slackware package. > _______________________________________________ > 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 jdashiel at panix.com Sun May 9 22:53:40 2021 From: jdashiel at panix.com (Jude DaShiell) Date: Sun, 9 May 2021 18:53:40 -0400 Subject: [Slackbuilds-users] comcom32 this may work Message-ID: I may be able to use dosemu2 on archlinux and install djgpp and the comcom32 github contents and build comcom32.exe in dosemu2 then copy that over into the slint environment. If it breaks anything I can reinstall archlinux or slint depending on the breakage location. From willysr at slackbuilds.org Thu May 13 03:53:47 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 13 May 2021 10:53:47 +0700 Subject: [Slackbuilds-users] Python 2/3 convention Message-ID: Hi all, I *think* we've come to a decision on python2/3 with respect to SBo. Generally speaking, we'll go with upstream defaults, taking these into consideration: * if the build in question supports only python2 *or* python3, then it/they will need to be named as "python2-$build" or "python3-$build" * if the build in question supports *both* python2 *and* python3, then the general rule will be to name it as python-$build There are surely going to be exceptions to those, and we may well have already created some of those exceptions ourselves (and not necessarily on purpose), and ultimately there are sure to be lots of corner cases and perhaps outright "we did this badly" cases that show up later. The best we can do right now is the best we can do, and we'll all fix whatever we break once we realize we've broken it... :-) Some work has been merged into master branch and more to come soon. This will take some time since we have lots of python scripts in our repository and multi-layered dependencies. Stay tuned for another email regarding how you can help us... -- 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 slackalaxy at gmail.com Sat May 15 11:00:17 2021 From: slackalaxy at gmail.com (Petar Petrov) Date: Sat, 15 May 2021 14:00:17 +0300 Subject: [Slackbuilds-users] I can take LX-Colors-Revival Message-ID: Hi guys, LX-Colors-Revival has no maintainer and has been removed from ponce's repo for -current. If no one takes it, I can do that. The sources are long gone, but I managed to find them here: https://www.lxle.net/forums/discussion/1239/lx-colors-revival/p1 so I uploaded them to my SourceForge repo, just in case: https://sourceforge.net/projects/sboppetrov/files/LX/ The updated SlackBuild is here: https://github.com/slackalaxy/15beta/tree/master/desktop/LX-Colors-Revival best, Petar From sb at rbn.im Mon May 17 00:05:37 2021 From: sb at rbn.im (Ruben Schuller) Date: Mon, 17 May 2021 02:05:37 +0200 Subject: [Slackbuilds-users] netsurf desktop file Message-ID: <20210517020537.2ba7c33e@kirsche.kuchen> hi, someone just dropped me a note that the desktop file of netsurf is running the wrong executable, it should be "netsurf-gtk2". see the attached patch. cheers ruben -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-fix-executable-in-netsurf-desktop-file.patch Type: text/x-patch Size: 696 bytes Desc: not available URL: From willysr at slackbuilds.org Mon May 17 01:40:55 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 17 May 2021 08:40:55 +0700 Subject: [Slackbuilds-users] netsurf desktop file In-Reply-To: <20210517020537.2ba7c33e@kirsche.kuchen> References: <20210517020537.2ba7c33e@kirsche.kuchen> Message-ID: <67ce5325-2a1d-5a8f-6d6b-f871f7a94607@slackbuilds.org> > someone just dropped me a note that the desktop file of netsurf is > running the wrong executable, it should be "netsurf-gtk2". see the > attached patch. merged in my branch Thanks -- 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 slackalaxy at gmail.com Mon May 17 14:45:56 2021 From: slackalaxy at gmail.com (Petar Petrov) Date: Mon, 17 May 2021 17:45:56 +0300 Subject: [Slackbuilds-users] updates Message-ID: hi guys, I recently built my stuff on -current from 14 May. A couple of things: academic/cufflinks: broke due to boost, so I made the script repackage the binaries, instead desktop/LX-Colors-Revival: I'll take this, since noone objected libraries/gconfmm: this is not mine, but I took a patch from Gentoo to make it build these are all here: https://github.com/slackalaxy/15beta if someone made a SlackBuild for QT4, please send me a link so I can check the stuff I maintain that requires it. best, Petar From willysr at slackbuilds.org Mon May 17 18:24:49 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 18 May 2021 01:24:49 +0700 Subject: [Slackbuilds-users] updates In-Reply-To: References: Message-ID: <30f78c46-898c-3254-b87f-d11e8f1ae52e@slackbuilds.org> > I recently built my stuff on -current from 14 May. A couple of things: > > academic/cufflinks: broke due to boost, so I made the script repackage > the binaries, instead > desktop/LX-Colors-Revival: I'll take this, since noone objected > libraries/gconfmm: this is not mine, but I took a patch from Gentoo to > make it build > > these are all here: https://github.com/slackalaxy/15beta > > if someone made a SlackBuild for QT4, please send me a link so I can > check the stuff I maintain that requires it. If you can push a PR or MR, that would be great Petar :) -- 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 slackalaxy at gmail.com Mon May 17 18:54:25 2021 From: slackalaxy at gmail.com (Petar Petrov) Date: Mon, 17 May 2021 21:54:25 +0300 Subject: [Slackbuilds-users] updates In-Reply-To: <30f78c46-898c-3254-b87f-d11e8f1ae52e@slackbuilds.org> References: <30f78c46-898c-3254-b87f-d11e8f1ae52e@slackbuilds.org> Message-ID: let me first familiarize myself with how to do that... I feel very uncomfortable with git, still -p On 17/05/2021, Willy Sudiarto Raharjo wrote: >> I recently built my stuff on -current from 14 May. A couple of things: >> >> academic/cufflinks: broke due to boost, so I made the script repackage >> the binaries, instead >> desktop/LX-Colors-Revival: I'll take this, since noone objected >> libraries/gconfmm: this is not mine, but I took a patch from Gentoo to >> make it build >> >> these are all here: https://github.com/slackalaxy/15beta >> >> if someone made a SlackBuild for QT4, please send me a link so I can >> check the stuff I maintain that requires it. > > If you can push a PR or MR, that would be great Petar :) > > > -- > Willy Sudiarto Raharjo > > From ozan.turkyilmaz at gmail.com Tue May 18 06:22:00 2021 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Tue, 18 May 2021 09:22:00 +0300 Subject: [Slackbuilds-users] Updates on -current Message-ID: HeyAll, I checked out my packages on -current and here's the status: splint - broken compile. pychm - built fine. There's couple of patches upstream prelink - built fine. mkvtoolnix - built fine with the latest version. Version bump was waiting for -current anyway. QT5 included in -current now. libupnp and libupnpn-legacy built fine. liboop built fine libebml built fine libmatroska built fine kildclient built fine. Version bump to 3.2.0 possible but it needs gtkspell3 gsnmp built fine gnet built fine fortune-ASR built fine. (I graduated from university 12 years ago but the link still works. I don't remember my password. Good thing there is no need for an update.) chm2pdf built fine boncuk it needs QT4. Patches to build with QT5. It's not updated for a long time. As I read, it just needs fixing headers. I will give it a try. If it works, I fork a copy to my gitlab account. chatbot-Eliza built fine aMule - built fine. Also there's a new release and it's built fine. I don't really use amule anymore. Any users? bootchard - built fine and I charted my -current boot. cldr- built fine iBus-Anthy built fine but its development stuck. Regards, Ozan -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at optusnet.com.au Tue May 18 07:46:36 2021 From: chris.willing at optusnet.com.au (Christoph Willing) Date: Tue, 18 May 2021 17:46:36 +1000 Subject: [Slackbuilds-users] updates In-Reply-To: References: Message-ID: <418c97b6-1437-9f17-5d16-8f4dcaacf0e5@optusnet.com.au> On 18/5/21 12:45 am, Petar Petrov wrote: > > libraries/gconfmm: this is not mine, but I took a patch from Gentoo to > make it build > Thanks for the tip. I've pushed an update which includes that patch. chris From sb at rbn.im Wed May 19 21:35:56 2021 From: sb at rbn.im (Ruben Schuller) Date: Wed, 19 May 2021 23:35:56 +0200 Subject: [Slackbuilds-users] anyone interested in maintaining gajim/python-nbxmpp? Message-ID: <20210519233556.58ce3dde@kirsche.kuchen> hi, i don't really use XMPP anymore, is anyone interested in maintaining gajim and python-nbxmpp? both also really need an update (which i've never done because something was too old on 14.2 iirc). if it helps, i can prepare a last update before handing it over. i have some parts already working. cheers ruben From gerardo.zamudio at linux.com Wed May 19 22:17:30 2021 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Wed, 19 May 2021 17:17:30 -0500 Subject: [Slackbuilds-users] anyone interested in maintaining gajim/python-nbxmpp? In-Reply-To: <20210519233556.58ce3dde@kirsche.kuchen> References: <20210519233556.58ce3dde@kirsche.kuchen> Message-ID: <7f129c5e1581cbcad71d2d73dba9fecd@linux.com> On 2021-05-19 4:35 pm, Ruben Schuller wrote: > hi, > > i don't really use XMPP anymore, is anyone interested in maintaining > gajim and python-nbxmpp? both also really need an update (which i've > never done because something was too old on 14.2 iirc). if it helps, i > can prepare a last update before handing it over. i have some parts > already working. > > cheers > ruben Hello Ruben I will gladly take it. I use Gajim every single day. Regards -- Gerardo Zamudio From sb at rbn.im Wed May 19 23:31:30 2021 From: sb at rbn.im (Ruben Schuller) Date: Thu, 20 May 2021 01:31:30 +0200 Subject: [Slackbuilds-users] anyone interested in maintaining gajim/python-nbxmpp? In-Reply-To: <7f129c5e1581cbcad71d2d73dba9fecd@linux.com> References: <20210519233556.58ce3dde@kirsche.kuchen> <7f129c5e1581cbcad71d2d73dba9fecd@linux.com> Message-ID: <20210520013130.6e34bc4c@kirsche.kuchen> hi gerardo! 2021-05-19 Gerardo Zamudio : > I will gladly take it. I use Gajim every single day. nice, it will be in better care than i can provide currently :) cheers ruben From kingbeowulf at gmail.com Thu May 20 00:23:33 2021 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 19 May 2021 17:23:33 -0700 Subject: [Slackbuilds-users] Drop aqemu (GUI front end to qemu) Message-ID: Although aqemu can be patched to build, numerous qemu CLI options have changed (deprecated, added, updated). Therefore, it is no longer viable. I don't have the time to fork and re-write, so I am dropping aqemu. I recommend Aqemu be dropped from 15.0. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From sb at rbn.im Thu May 20 00:33:03 2021 From: sb at rbn.im (Ruben Schuller) Date: Thu, 20 May 2021 02:33:03 +0200 Subject: [Slackbuilds-users] cantata for grabs Message-ID: <20210520023303.194ae882@kirsche.kuchen> hi, as i'm currently going through my slackbuilds: cantata also could use a new maintainer as i don't use mpd anymore. cheers ruben From jdashiel at panix.com Fri May 21 00:53:00 2021 From: jdashiel at panix.com (Jude DaShiell) Date: Thu, 20 May 2021 20:53:00 -0400 Subject: [Slackbuilds-users] chromium-90 package Message-ID: This one fails to download due to an incorrect md5sum. From jdashiel at panix.com Fri May 21 00:58:49 2021 From: jdashiel at panix.com (Jude DaShiell) Date: Thu, 20 May 2021 20:58:49 -0400 Subject: [Slackbuilds-users] dosemu package builds broken Message-ID: Missing prerequisite or prerequisites makes this package fail to run once built. At least dosemu/comcom32 hasn't been built since slackware has no gcc cross compiler that can build this package. I can't state that comcom32 is the only missing prerequisite since the package fails to run before displaying the c:\ prompt. If the package runs successfully it's possible after the c:\ prompt comes up to type exitemu to return to linux. If done once dosemu creates ~/.dosemu/boot.log and if done more than that ~/.dosemu/boot.log.1 and so on. Those boot.log files are text so can be read. From thomas at beingboiled.info Sat May 22 20:19:43 2021 From: thomas at beingboiled.info (Thomas Morper) Date: Sat, 22 May 2021 22:19:43 +0200 (CEST) Subject: [Slackbuilds-users] separating source archives and SlackBuilds Message-ID: <822f95a0-20a3-ccfc-29cd-8a20fcc0f471@beingboiled.info> Hello there! There's a certain feature in FreeBSD ports that I think I'd like to have in SlackBuilds, too, and I want to know what you think about it: FreeBSD ports keep all source archives in the /usr/ports/distfiles folder while SlackBuilds expect the source archive in the same folder as the SlackBuld itself. With a simple "DISTFILES=${DISTFILES:-$CWD}" and "tar xvf $DISTFILES/..." rather than "tar xvf $CWD/..." in the template we could have both ways. The reason for keeping it the way it is: simplicity. The reason for having a separate distfiles folder: you can keep as many source archive versions around as you want without affecting the way you work with the SlackBuilds directory tree, e.g. always using a pristine and possibly read-only copy, or going all-in on git without ever accidentally adding and comitting the LibreOffice tar ball. Would this be desirable and feasible? Cheers! -- From dickson.tim at googlemail.com Sat May 22 21:39:53 2021 From: dickson.tim at googlemail.com (Tim Dickson) Date: Sat, 22 May 2021 22:39:53 +0100 Subject: [Slackbuilds-users] separating source archives and SlackBuilds In-Reply-To: <822f95a0-20a3-ccfc-29cd-8a20fcc0f471@beingboiled.info> References: <822f95a0-20a3-ccfc-29cd-8a20fcc0f471@beingboiled.info> Message-ID: Unfortunately it doesn't quite work. A number of the source files have the same name, even though they are different. Especially for multi-versions available, such as various versions of jdk. On the other hand, if you use sbopkg for creating packages, it already has a default location for source, /var/cache/sbopkg/? and that is checked first before the source url's, to save re-downloading the same files. You might want to try it, as it sounds like the behaviour you are looking for. It still suffers from the issue mentioned, but as it checks md5sums, it offers to download the correct source, which is useful. regards, Tim On 22/05/2021 21:19, Thomas Morper wrote: > Hello there! > > There's a certain feature in FreeBSD ports that I think I'd like to have > in SlackBuilds, too, and I want to know what you think about it: > > FreeBSD ports keep all source archives in the /usr/ports/distfiles folder > while SlackBuilds expect the source archive in the same folder as the > SlackBuld itself. > > With a simple "DISTFILES=${DISTFILES:-$CWD}" and "tar xvf $DISTFILES/..." > rather than "tar xvf $CWD/..." in the template we could have both ways. > > The reason for keeping it the way it is: simplicity. > > The reason for having a separate distfiles folder: you can keep as many > source archive versions around as you want without affecting the way you > work with the SlackBuilds directory tree, e.g. always using a pristine and > possibly read-only copy, or going all-in on git without ever accidentally > adding and comitting the LibreOffice tar ball. > > Would this be desirable and feasible? > > Cheers! > -- This email has been checked for viruses by AVG. https://www.avg.com From didier at slint.fr Tue May 25 12:45:37 2021 From: didier at slint.fr (Didier Spaier) Date: Tue, 25 May 2021 14:45:37 +0200 Subject: [Slackbuilds-users] avahi without the server. Caveats. Message-ID: <702e251d-5603-6b8f-287d-e3d0b559bfbc@slint.fr> Hi, reviewing the dameon managers in Slint to document their purposes and default "executability" in our handbook made me realize that although /etc/rc.d/rc.avahidaemon and rc.avahidnsconfd are executable in Slint by default, they don't run as not started by a code snippet in /etc/rc.d/rc.local. This puzzled me as avahi is a dependency of following packages in Slint: geoclue2-2.4.7-x86_64-1slint gnome-vfs-2.24.4-x86_64-1slint gnustep-base-1.25.1-x86_64-2slint mod_dnssd-0.6-x86_64-1slint mpd-sacd-0.20.18-x86_64-1slint mumble-gitc32b8fdf-x86_64-1slint. unar-1.10.1-x86_64-2slint vlc-3.0.12-x86_64-1slint But nobody complained about a missing features related to these packages so far. Having removed avahi from a clean system, ldd told me that some binary files missed these dependencies: libavahi-client.so.3 libavahi-glib.so.1 libavahi-common.so.3 Having also seen this (cryptic to me) message in the ChangeLog for Slackware64-current posted on Fri Mar 12 23:01:08 UTC 2021: ap/hplip-3.20.5-x86_64-3.txz: Rebuilt. Switched to hplip-3.20.5 to fix regressions in the hp-plugin subsystem. Patched to use is_alive() rather than the deprecated isAlive(). Thanks to Andypoo. Newer versions than 3.20.6 require avahi. We'll stick with this version for now and leave the decision about whether we love HP more than we hate avahi for another day. I am wondering: why not install *only* the so files from the avahi package? What would users miss? which inconveniences, caveats? Or, can I just remove the daemon managers Thanks and best regards, Didier From chris.willing at linux.com Tue May 25 13:20:47 2021 From: chris.willing at linux.com (Christoph Willing) Date: Tue, 25 May 2021 23:20:47 +1000 Subject: [Slackbuilds-users] avahi without the server. Caveats. In-Reply-To: <702e251d-5603-6b8f-287d-e3d0b559bfbc@slint.fr> References: <702e251d-5603-6b8f-287d-e3d0b559bfbc@slint.fr> Message-ID: On 25/5/21 10:45 pm, Didier Spaier wrote: > > I am wondering: why not install *only* the so files from the avahi package? > What would users miss? which inconveniences, caveats? > Or, can I just remove the daemon managers > Are you asking just in general terms (for your own interest/use) or are you suggesting that the SlackBuild should be changed to install only .so files? People may use avahi for purposes other than the ones you've examined. Even if the .so files are sufficient for runtime use, what about building software that may need avahi's include files (don't ask me to name them) - perhaps a separate avahi-dev package? I don't hate avahi enough to treat it differently to half (or more?) of the packages at SBo that could also be trimmed in some way or other. In fact I prefer as many features built into my SlackBuilds as possible; even features I'm not necessarily using today. chris From didier at slint.fr Tue May 25 15:48:12 2021 From: didier at slint.fr (Didier Spaier) Date: Tue, 25 May 2021 17:48:12 +0200 Subject: [Slackbuilds-users] avahi without the server. Caveats. In-Reply-To: References: <702e251d-5603-6b8f-287d-e3d0b559bfbc@slint.fr> Message-ID: Hi Christoph, ,On 25/05/2021 15:20, Christoph Willing wrote: > On 25/5/21 10:45 pm, Didier Spaier wrote: >> >> I am wondering: why not install *only* the so files from the avahi package? >> What would users miss? which inconveniences, caveats? >> Or, can I just remove the daemon managers >> > Are you asking just in general terms (for your own interest/use) or are > you suggesting that the SlackBuild should be changed to install only .so > files? In general terms for my own interest, it didn't come to my mind to request a change in the SlackBuild you maintain > People may use avahi for purposes other than the ones you've examined. > Even if the .so files are sufficient for runtime use, what about > building software that may need avahi's include files (don't ask me to > name them) - perhaps a separate avahi-dev package? That could would be an idea. I could include a package with just the .so and .h files. Users needing more would install a full package. I have to think about the implications though. or start the daemon managers in rc.M if -x but leave them -x by default, which seems more logical if the whole package is installed by default I realize that this maybe off-topic for this lit, sorry if it bothered anyone. > I don't hate avahi enough to treat it differently to half (or more?) of > the packages at SBo that could also be trimmed in some way or other. In > fact I prefer as many features built into my SlackBuilds as possible; > even features I'm not necessarily using today. which is perfectly fine with me. Thanks and best regards, Didier From sb at rbn.im Tue May 25 21:15:54 2021 From: sb at rbn.im (Ruben Schuller) Date: Tue, 25 May 2021 23:15:54 +0200 Subject: [Slackbuilds-users] avahi without the server. Caveats. In-Reply-To: <702e251d-5603-6b8f-287d-e3d0b559bfbc@slint.fr> References: <702e251d-5603-6b8f-287d-e3d0b559bfbc@slint.fr> Message-ID: <20210525231554.502861e5@kiwi.kuchen> hi, 2021-05-25 Didier Spaier : > I am wondering: why not install *only* the so files from the avahi > package? What would users miss? which inconveniences, caveats? > Or, can I just remove the daemon managers i'll just chime in with my two cents: it is in fact one thing which i really like about slackware, there are no "development" packages or similar shenanigans. it's usually just one package. the need to constantly install a myriad of packages drives me insane when compiling something on other linux distributions. cheers ruben From spycrowsoft at gmail.com Tue May 25 21:30:51 2021 From: spycrowsoft at gmail.com (Spycrowsoft) Date: Tue, 25 May 2021 23:30:51 +0200 Subject: [Slackbuilds-users] avahi without the server. Caveats. In-Reply-To: <20210525231554.502861e5@kiwi.kuchen> References: <702e251d-5603-6b8f-287d-e3d0b559bfbc@slint.fr> <20210525231554.502861e5@kiwi.kuchen> Message-ID: <516b4634-969d-fcd5-6812-d3fac0afce2a@gmail.com> Op 25-05-2021 om 23:15 schreef Ruben Schuller: > hi, > > 2021-05-25 Didier Spaier : > >> I am wondering: why not install *only* the so files from the avahi >> package? What would users miss? which inconveniences, caveats? >> Or, can I just remove the daemon managers > i'll just chime in with my two cents: > it is in fact one thing which i really like about slackware, there are > no "development" packages or similar shenanigans. it's usually just one > package. the need to constantly install a myriad of packages drives me > insane when compiling something on other linux distributions. I'll second that. I'd also like to note that I actually use the daemons to announce some non-avahi services to other zeroconf compatible devices. From andrew.m.goth at gmail.com Mon May 31 19:26:47 2021 From: andrew.m.goth at gmail.com (Andy Goth) Date: Mon, 31 May 2021 14:26:47 -0500 Subject: [Slackbuilds-users] Mailing list subscription instructions Message-ID: <3b0f1162-0758-4f1b-74c0-222febf5934b@gmail.com> I can't find any instructions on how to actually subscribe to the mailing list, so I had to work it out from the GNU Mailman documentation. Per their documentation, there's typically a subscription web form, but if you have one, you don't seem to have it linked anywhere. -- Andy Goth | From andrew.m.goth at gmail.com Mon May 31 19:30:22 2021 From: andrew.m.goth at gmail.com (Andy Goth) Date: Mon, 31 May 2021 14:30:22 -0500 Subject: [Slackbuilds-users] ASC FAQ link issue Message-ID: <4315c576-f23f-ad7d-9740-4c383486b4fe@gmail.com> The ASC FAQ link on each package page technically works, but then the focusSearchBox() JavaScript function swoops in and scrolls the display off the ASC section back up to the top of the page. With the page already loaded, I either have to click into the address bar and hit enter, or click the ASC FAQ item in the table of contents, to actually get what was being linked to in the first place. -- Andy Goth | From gerardo.zamudio at linux.com Mon May 31 20:22:08 2021 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Mon, 31 May 2021 15:22:08 -0500 Subject: [Slackbuilds-users] Mailing list subscription instructions In-Reply-To: <3b0f1162-0758-4f1b-74c0-222febf5934b@gmail.com> References: <3b0f1162-0758-4f1b-74c0-222febf5934b@gmail.com> Message-ID: On 2021-05-31 2:26 pm, Andy Goth wrote: > I can't find any instructions on how to actually subscribe to the > mailing list, so I had to work it out from the GNU Mailman > documentation. > > Per their documentation, there's typically a subscription web form, > but if you have one, you don't seem to have it linked anywhere. Hello Andy In the footer of every page at SlackBuilds.org there is a link labeled Mailing Lists. Clicking this link takes you to https://lists.slackbuilds.org/ and here you can click on Slackbuilds mailing lists to see an overview of lists. Click on SlackBuilds-users and you will find the sign up web form. Regards -- Gerardo Zamudio From andrew.m.goth at gmail.com Mon May 31 20:25:52 2021 From: andrew.m.goth at gmail.com (Andy Goth) Date: Mon, 31 May 2021 15:25:52 -0500 Subject: [Slackbuilds-users] Mailing list subscription instructions In-Reply-To: References: <3b0f1162-0758-4f1b-74c0-222febf5934b@gmail.com> Message-ID: On 5/31/21 3:22 PM, Gerardo Zamudio wrote: > On 2021-05-31 2:26 pm, Andy Goth wrote: >> I can't find any instructions on how to actually subscribe to the >> mailing list, so I had to work it out from the GNU Mailman >> documentation. >> >> Per their documentation, there's typically a subscription web form, >> but if you have one, you don't seem to have it linked anywhere. > > In the footer of every page at SlackBuilds.org there is a link labeled > Mailing Lists. Clicking this link takes you to > https://lists.slackbuilds.org/ and here you can click on Slackbuilds > mailing lists to see an overview of lists. > > Click on SlackBuilds-users and you will find the sign up web form. Thanks, I see the signup form at http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users . I looked for entirely too long and just couldn't seem to find it. This will be helpful for the next Mailman list I use. -- Andy Goth |