Re: [Slackbuilds-users] openDKIM questions

On Wed, 22 Nov 2017, Gerardo Zamudio wrote: Lucky for me there was a typo :-) Gerardo, Yes, for both of us. I'm guilty as charged. The mail list is down at the moment. No idea when it'll be back. You can submit bug reports at SourceForge[1]. The LyX mail list has also been down since

Re: [Slackbuilds-users] openDKIM questions

On 11/22/2017 03:24 PM, Didier Spaier wrote: > please refrain writing email addresses in full in the body of your > emails, as that makes too easy for spammers to just click on them in the > email public archives to record them. Lucky for me there was a typo :-) > Le 22/11/2017 à 15:31, Rich

Re: [Slackbuilds-users] openDKIM questions

On Wed, 22 Nov 2017, Audrius Kažukauskas wrote: His name is Gerardo -- you missed the second "r", the same typo is in the email address you've used. Thank you, Audrius. I thought I had copied it correctly from the web page. My apologies to all, Rich

Re: [Slackbuilds-users] openDKIM questions

On Wed, 22 Nov 2017, Didier Spaier wrote: please refrain writing email addresses in full in the body of your emails, as that makes too easy for spammers to just click on them in the email public archives to record them. Will do, Didier. Rich ___

Re: [Slackbuilds-users] openDKIM questions

On Wed, 2017-11-22 at 06:31:59 -0800, Rich Shepard wrote: > I tried to directly contact Gerado Zamudio, the opendkim package > maintainer, but the message bounced: His name is Gerardo -- you missed the second "r", the same typo is in the email address you've used. -- Audrius Kažukauskas

Re: [Slackbuilds-users] openDKIM questions

@All, please refrain writing email addresses in full in the body of your emails, as that makes too easy for spammers to just click on them in the email public archives to record them. Le 22/11/2017 à 15:31, Rich Shepard a écrit : >   I tried to directly contact Gerado Zamudio, the opendkim

Re: [Slackbuilds-users] How to build .txz package without editing .SlackBuild file.

Hello, Thank you all for your suggestions. Anand On Wed, Nov 22, 2017 at 5:52 PM, Willy Sudiarto Raharjo < will...@slackbuilds.org> wrote: > >>> By default .SlackBuild files are written to make .tgz package. > >>> > >>> Is there any way to build .txz file from the buildscript without >

Re: [Slackbuilds-users] intel-microcode version 20171117

Thanks and sorry Andrzej, I misspelled your name in my original email. -- kjh On Wed, Nov 22, 2017 at 5:01 AM, Andrzej Telszewski wrote: > On 22/11/17 10:49, Konrad J Hambrick wrote: > >> Andrej -- >> >> Attached are diffs for last week's intel-microcode firmware update

Re: [Slackbuilds-users] How to build .txz package without editing .SlackBuild file.

>>> By default .SlackBuild files are written to make .tgz package. >>> >>> Is there any way to build .txz file from the buildscript without editing >>> the .SlackBuild file by passing parameter to the buildscript to create a >>> .txz file? >> Export PKGTYPE=txz to the SlackBuild script. >> >

Re: [Slackbuilds-users] How to build .txz package without editing .SlackBuild file.

On 11/22/2017 02:12 AM, Chris Novakovic wrote: On 22/11/17 03:45, Ananda Murthy R S wrote: By default .SlackBuild files are written to make .tgz package. Is there any way to build .txz file from the buildscript without editing the .SlackBuild file by passing parameter to the buildscript to

Re: [Slackbuilds-users] intel-microcode version 20171117

On 22/11/17 10:49, Konrad J Hambrick wrote: Andrej -- Attached are diffs for last week's intel-microcode firmware update ( Version 20171117 ). I've built and installed an updated Package ; rebuilt my two ucode initrd images ( GENERIC and HUGE ) and rebooted. All is OK on my system ( but

[Slackbuilds-users] intel-microcode version 20171117

Andrej -- Attached are diffs for last week's intel-microcode firmware update ( Version 20171117 ). I've built and installed an updated Package ; rebuilt my two ucode initrd images ( GENERIC and HUGE ) and rebooted. All is OK on my system ( but that's a moot point because the firmware for my