From willysr at slackbuilds.org Wed Nov 1 00:20:05 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 1 Nov 2017 07:20:05 +0700 Subject: [Slackbuilds-users] Spotify correct md5sum In-Reply-To: <4b841fdb-8609-c073-8c6a-c0662676bce7@lemintown.eu> References: <4b841fdb-8609-c073-8c6a-c0662676bce7@lemintown.eu> Message-ID: > MD5SUM="5249a52cdbcc59637cca6b2d43484e2d" > MD5SUM_x86_64="95d29a231d2e615790439770fabf8ec6" Thanks fixed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Wed Nov 1 00:59:49 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 1 Nov 2017 07:59:49 +0700 Subject: [Slackbuilds-users] Updates - 20171101.1 Message-ID: <4c6e03f6-9954-c5df-2bb0-735ad193f4d0@slackbuilds.org> Welcome to the first update in November. Its a bit early, but we have strong reason for that. First, we have two security updates in this batch. First one is lxterminal and the second one is jdk. Please note that Oracle is declaring EOL for JDK 8 and they are moving to 9.x in 2017 and they will move again to a new numbering scheme in March 2018. Please see http://www.oracle.com/technetwork/java/javase/eol-135779.html for more information. Robby is now testing jdk9 in a separate branch. Feel free to test to see whether it deemed stable enough to be merged into master soon. Second, David has fixed lots of scripts in our repository, mostly slack-desc and VERSION line. We tried to avoid conflicts with maintainer's update so we pushed this public update early so that you can use the current master as base for future updates. Please respect his work by using the latest tarball from our website before you submit an update. DO NOT use your local copy as it will revert the previous work. He also found that CoinMP is broken due to previous commit so it gets reverted for now. You will notice that there's a SDL2-review branch in our cgit interface that wasn't merged in this batch. David (again, he's the hero) found out that this update broke three other scripts (doomretro, dunelegacy and Kivy), so he's still testing them for this week and hopefully we can resolve that in the next public update this weekend. Start syncing and start building guys :) Wed Nov 1 00:35:35 UTC 2017 audio/mp4tools: Updated for version 3.5. desktop/cwm: Updated for version 6.2. desktop/lxpanel: Fixed slack-desc. desktop/obmenu-generator: Updated for version 0.84. development/QStlink: Fixed slack-desc. development/blocksruntime: Added (BlocksRunTime library). development/dpkg: Updated for version 1.19.0.4. development/gcclegacy494: Fixed slack-desc and .info. development/google-go-lang: Updated for version 1.8.5 development/groovy: Install doinst.sh. development/jdk: Updated for version 8u152. development/jupyter-nbdime: Fixed slack-desc. development/jupyter_core: Update for version 4.4.0. development/obnc: Updated for version 0.9.1. development/python3-cycler: Fixed slack-desc. development/systemtap: Added (Linux trace/probe tool). games/nsuds: Fixed slack-desc. games/quakeforge: Fixed VERSION. games/scribble: Fixed VERSION. games/tome-ah: Fixed slack-desc. gis/qgis: Updated for version 2.18.14. graphics/openimageio: Patch to include cstdio (missing since openjpeg update) libraries/CoinMP: Reverted previous bad fix 2ed1509ad31. libraries/QUSB: Fixed slack-desc. libraries/QtUsb: Fixed slack-desc. libraries/isodate: Updated for version 0.6.0. libraries/libfastjson: Updated for version 0.99.7. libraries/libwebp: Updated for version 0.6.0. libraries/live555: Updated for version 2017.10.28 libraries/obnc-libstd: Updated for version 0.3.1. libraries/pylast: Updated for version 2.0.0. libraries/python-efl: Fixed slack-desc. libraries/tbb: Updated for version 2018u1. libraries/vte3: Updated for version 0.50.2. libraries/webkit2gtk: Updated for version 2.18.2. misc/bsdmainutils: Fixed .info. misc/fcitx-qt5: Updated for version 1.1.1. misc/grc: Update DEP. misc/moreutils: Fixed .info. misc/paperkey: Updated for version 1.5. multimedia/mkclean: Updated for version 0.8.10. multimedia/mkvalidator: Updated for version 0.5.2. multimedia/obs-studio: Updated for version 20.1.1 multimedia/pitivi: Fixed slack-desc. multimedia/spotify: Fix MD5SUM. multimedia/whistle: Updated for version 0.9.3. network/atheme: Updated SlackBuild. network/elinks: Switch to i586 + new README. network/lighttpd: Updated for version 1.4.47. network/luakit: Fixed tarball handling. network/opera-developer: Updated for version 50.0.2759.0. network/prosody: Fixed slack-desc. network/pure-ftpd: Updated for version 1.0.47. network/speedtest-cli: Updated for version 1.0.7. network/tinc: Fixed slack-desc. network/tor: Updated for version 0.3.1.8. network/torsocks: Updated for version 2.2.0. network/vivaldi: Updated for version 1.12.955.48. network/yandex-browser-beta: Updated for version 17.9.1.982. office/adobe-reader: Fixed VERSION. office/aspell6-es: Fixed SlackBuild. office/hyphen-id: Fixed slack-desc. office/mythes-id: Fixed slack-desc. perl/perl-Math-LongDouble: Updated for version 0.19. perl/perl-Types-Serialiser: Fixed slack-desc. python/APScheduler: Updated for version 3.4.0. python/mistune: Updated for version 0.8. python/obspy: Updated for version 1.1.0. python/python-d2to1: Fixed slack-desc. python/python-odict: Added (ordered dictionary). python/python-webencodings: Fixed slack-desc. python/python3-jedi: Fixed slack-desc. python/python3-pyzmq: Updated for version 16.0.3 python/python3-wcwidth: Fixed slack-desc. python/pyzmq: Updated for version 16.0.3. python/sphinxcontrib-websupport: Fixed slack-desc. python/waitress: Updated for version 1.1.0. system/afdko: Remove backup file. system/dosbox-dev: Fixed slack-desc. system/fish: Updated for version 2.7b1. system/fswatch: Fixed slack-desc. system/gimp-help: Fixed homepage. system/grub_legacy: Added (legacy version of GRUB bootloader). system/kexec-tools: Updated for version 2.0.15. system/lxterminal: Updated for version 0.3.1. system/lynis: Updated for version 2.5.7. system/noto-fonts: Updated for version 20171026. system/overpass-desktop-fonts: Fixed slack-desc. system/rdiff-backup: Fixed VERSION. system/rsyslog: Updated for version 8.30.0. system/sleepd: Install doinst.sh. system/thermald: Updated for version 1.7.1. system/zuluCrypt: Updated for version 5.3.0. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From fernando.lopezjr at gmail.com Wed Nov 1 01:03:21 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Tue, 31 Oct 2017 19:03:21 -0600 Subject: [Slackbuilds-users] Updates - 20171101.1 In-Reply-To: <4c6e03f6-9954-c5df-2bb0-735ad193f4d0@slackbuilds.org> References: <4c6e03f6-9954-c5df-2bb0-735ad193f4d0@slackbuilds.org> Message-ID: just so you know, android sdk is not jdk9 ready yet. On Tue, Oct 31, 2017 at 6:59 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > Welcome to the first update in November. > Its a bit early, but we have strong reason for that. > > First, we have two security updates in this batch. First one is > lxterminal and the second one is jdk. Please note that Oracle is > declaring EOL for JDK 8 and they are moving to 9.x in 2017 and they will > move again to a new numbering scheme in March 2018. Please see > http://www.oracle.com/technetwork/java/javase/eol-135779.html for more > information. Robby is now testing jdk9 in a separate branch. Feel free > to test to see whether it deemed stable enough to be merged into master > soon. > > Second, David has fixed lots of scripts in our repository, mostly > slack-desc and VERSION line. We tried to avoid conflicts with > maintainer's update so we pushed this public update early so that you > can use the current master as base for future updates. Please respect > his work by using the latest tarball from our website before you submit > an update. DO NOT use your local copy as it will revert the previous > work. He also found that CoinMP is broken due to previous commit so it > gets reverted for now. > > You will notice that there's a SDL2-review branch in our cgit interface > that wasn't merged in this batch. David (again, he's the hero) found out > that this update broke three other scripts (doomretro, dunelegacy and > Kivy), so he's still testing them for this week and hopefully we can > resolve that in the next public update this weekend. > > Start syncing and start building guys :) > > > Wed Nov 1 00:35:35 UTC 2017 > audio/mp4tools: Updated for version 3.5. > desktop/cwm: Updated for version 6.2. > desktop/lxpanel: Fixed slack-desc. > desktop/obmenu-generator: Updated for version 0.84. > development/QStlink: Fixed slack-desc. > development/blocksruntime: Added (BlocksRunTime library). > development/dpkg: Updated for version 1.19.0.4. > development/gcclegacy494: Fixed slack-desc and .info. > development/google-go-lang: Updated for version 1.8.5 > development/groovy: Install doinst.sh. > development/jdk: Updated for version 8u152. > development/jupyter-nbdime: Fixed slack-desc. > development/jupyter_core: Update for version 4.4.0. > development/obnc: Updated for version 0.9.1. > development/python3-cycler: Fixed slack-desc. > development/systemtap: Added (Linux trace/probe tool). > games/nsuds: Fixed slack-desc. > games/quakeforge: Fixed VERSION. > games/scribble: Fixed VERSION. > games/tome-ah: Fixed slack-desc. > gis/qgis: Updated for version 2.18.14. > graphics/openimageio: Patch to include cstdio (missing since openjpeg > update) > libraries/CoinMP: Reverted previous bad fix 2ed1509ad31. > libraries/QUSB: Fixed slack-desc. > libraries/QtUsb: Fixed slack-desc. > libraries/isodate: Updated for version 0.6.0. > libraries/libfastjson: Updated for version 0.99.7. > libraries/libwebp: Updated for version 0.6.0. > libraries/live555: Updated for version 2017.10.28 > libraries/obnc-libstd: Updated for version 0.3.1. > libraries/pylast: Updated for version 2.0.0. > libraries/python-efl: Fixed slack-desc. > libraries/tbb: Updated for version 2018u1. > libraries/vte3: Updated for version 0.50.2. > libraries/webkit2gtk: Updated for version 2.18.2. > misc/bsdmainutils: Fixed .info. > misc/fcitx-qt5: Updated for version 1.1.1. > misc/grc: Update DEP. > misc/moreutils: Fixed .info. > misc/paperkey: Updated for version 1.5. > multimedia/mkclean: Updated for version 0.8.10. > multimedia/mkvalidator: Updated for version 0.5.2. > multimedia/obs-studio: Updated for version 20.1.1 > multimedia/pitivi: Fixed slack-desc. > multimedia/spotify: Fix MD5SUM. > multimedia/whistle: Updated for version 0.9.3. > network/atheme: Updated SlackBuild. > network/elinks: Switch to i586 + new README. > network/lighttpd: Updated for version 1.4.47. > network/luakit: Fixed tarball handling. > network/opera-developer: Updated for version 50.0.2759.0. > network/prosody: Fixed slack-desc. > network/pure-ftpd: Updated for version 1.0.47. > network/speedtest-cli: Updated for version 1.0.7. > network/tinc: Fixed slack-desc. > network/tor: Updated for version 0.3.1.8. > network/torsocks: Updated for version 2.2.0. > network/vivaldi: Updated for version 1.12.955.48. > network/yandex-browser-beta: Updated for version 17.9.1.982. > office/adobe-reader: Fixed VERSION. > office/aspell6-es: Fixed SlackBuild. > office/hyphen-id: Fixed slack-desc. > office/mythes-id: Fixed slack-desc. > perl/perl-Math-LongDouble: Updated for version 0.19. > perl/perl-Types-Serialiser: Fixed slack-desc. > python/APScheduler: Updated for version 3.4.0. > python/mistune: Updated for version 0.8. > python/obspy: Updated for version 1.1.0. > python/python-d2to1: Fixed slack-desc. > python/python-odict: Added (ordered dictionary). > python/python-webencodings: Fixed slack-desc. > python/python3-jedi: Fixed slack-desc. > python/python3-pyzmq: Updated for version 16.0.3 > python/python3-wcwidth: Fixed slack-desc. > python/pyzmq: Updated for version 16.0.3. > python/sphinxcontrib-websupport: Fixed slack-desc. > python/waitress: Updated for version 1.1.0. > system/afdko: Remove backup file. > system/dosbox-dev: Fixed slack-desc. > system/fish: Updated for version 2.7b1. > system/fswatch: Fixed slack-desc. > system/gimp-help: Fixed homepage. > system/grub_legacy: Added (legacy version of GRUB bootloader). > system/kexec-tools: Updated for version 2.0.15. > system/lxterminal: Updated for version 0.3.1. > system/lynis: Updated for version 2.5.7. > system/noto-fonts: Updated for version 20171026. > system/overpass-desktop-fonts: Fixed slack-desc. > system/rdiff-backup: Fixed VERSION. > system/rsyslog: Updated for version 8.30.0. > system/sleepd: Install doinst.sh. > system/thermald: Updated for version 1.7.1. > system/zuluCrypt: Updated for version 5.3.0. > +--------------------------+ > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > 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 dpross1100 at msn.com Wed Nov 1 04:27:56 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Wed, 1 Nov 2017 04:27:56 +0000 Subject: [Slackbuilds-users] Email rejected during submission In-Reply-To: References: Message-ID: Anyone? I see Jorge Giner Cordero had the exact same problem on October 1, but no one posted a solution. Actually, one person posted a suggestion to use (applying it to my case) "dpross1100 at msn.com," but that doesn't work. I would like to be able to update my scripts. Dan On Tue, Oct 31, 2017 at 03:43:20AM +0000, Daniel Prosser wrote: > Trying to submit an update to one of my SlackBuilds, I get this error: > > ***** > [my email address] was rejected by mx2.hotmail.com. > Go back and enter a valid E-Mail address. > > If your mailserver uses Greylisting you may want to Whitelist > slackbuilds-users at slackbuilds.org. > ***** > > I have added slackbuilds-users at slackbuilds.org and also the > slackbuilds.org domain to my safe senders list. Anything else I can do? > This has never happened to me in the past. > > Dan > _______________________________________________ > 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 yalhcru at gmail.com Wed Nov 1 16:41:15 2017 From: yalhcru at gmail.com (B Watson) Date: Wed, 1 Nov 2017 12:41:15 -0400 Subject: [Slackbuilds-users] fpc and ptop conflict Message-ID: development/fpc and system/ptop both install a /usr/bin/ptop file. Easiest solution is to add a note to the READMEs of both builds, saying they conflict, and to only install one or the other. Fancier solution would be for ptop (the smaller/simpler of the two) to be installed as /usr/bin/ptop.py, or else /opt/ptop/bin/ptop, and add a note to its README explaining how to run it. From fernando.lopezjr at gmail.com Thu Nov 2 02:32:09 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Wed, 1 Nov 2017 20:32:09 -0600 Subject: [Slackbuilds-users] help building OpenVizsla-ov_ftdi Message-ID: *can anyone help me build:* https://github.com/openvizsla/ov_ftdi *build instructions:* https://github.com/openvizsla/ov_ftdi/wiki/building *this is what i get:* bash-4.4$ pwd ov_ftdi-1f980e821659d87bb0ed704e54ebb256a0547d92/software/fpga/ov3 bash-4.4$ make python3 build.py build_dir build build_name ov3 Traceback (most recent call last): File "build.py", line 1, in from ovplatform.ov3 import Platform File "/home/ferdna/Downloads/slackbuilds/ov-ftdi/ov-ftdi/ov_ftdi-1f980e821659d87bb0ed704e54ebb256a0547d92/software/fpga/ov3/ovplatform/ov3.py", line 1, in from mibuild.generic_platform import * ModuleNotFoundError: No module named 'mibuild' make: *** [Makefile:18: build/ov3.bit] Error 1 bash-4.4$ *thank you!! =)* -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Thu Nov 2 02:44:04 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 2 Nov 2017 09:44:04 +0700 Subject: [Slackbuilds-users] help building OpenVizsla-ov_ftdi In-Reply-To: References: Message-ID: <1965a7c4-85cc-b01c-75fc-983a76444253@slackbuilds.org> > *can anyone help me build:* > https://github.com/openvizsla/ov_ftdi > > *build instructions:* > https://github.com/openvizsla/ov_ftdi/wiki/building > > *this is what i get:* > > bash-4.4$ pwd > ov_ftdi-1f980e821659d87bb0ed704e54ebb256a0547d92/software/fpga/ov3 > bash-4.4$ make > python3 build.py build_dir build build_name ov3 > Traceback (most recent call last): > File "build.py", line 1, in > from ovplatform.ov3 import Platform > File > "/home/ferdna/Downloads/slackbuilds/ov-ftdi/ov-ftdi/ov_ftdi-1f980e821659d87bb0ed704e54ebb256a0547d92/software/fpga/ov3/ovplatform/ov3.py", > line 1, in > from mibuild.generic_platform import * > ModuleNotFoundError: No module named 'mibuild' > make: *** [Makefile:18: build/ov3.bit] Error 1 > bash-4.4$ You probably need https://github.com/brandonhamilton/mibuild -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From rworkman at slackbuilds.org Thu Nov 2 03:09:18 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 1 Nov 2017 22:09:18 -0500 Subject: [Slackbuilds-users] Email rejected during submission In-Reply-To: References: Message-ID: <20171101220918.345a3374@home.rlworkman.net> Top-posting to keep the pattern, even if I don't like it... Sorry, I have no idea what's wrong there - rob0? -RW On Wed, 1 Nov 2017 04:27:56 +0000 Daniel Prosser wrote: > Anyone? I see Jorge Giner Cordero had the exact same problem on > October 1, but no one posted a solution. Actually, one person posted a > suggestion to use (applying it to my case) "dpross1100 at msn.com," > but that doesn't work. I would like to be able to update my scripts. > > Dan > > On Tue, Oct 31, 2017 at 03:43:20AM +0000, Daniel Prosser wrote: > > Trying to submit an update to one of my SlackBuilds, I get this > > error: > > > > ***** > > [my email address] was rejected by mx2.hotmail.com. > > Go back and enter a valid E-Mail address. > > > > If your mailserver uses Greylisting you may want to Whitelist > > slackbuilds-users at slackbuilds.org. > > ***** > > > > I have added slackbuilds-users at slackbuilds.org and also the > > slackbuilds.org domain to my safe senders list. Anything else I can > > do? This has never happened to me in the past. > > > > Dan > > _______________________________________________ > > 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 -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From fernando.lopezjr at gmail.com Thu Nov 2 03:19:20 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Wed, 1 Nov 2017 21:19:20 -0600 Subject: [Slackbuilds-users] help building OpenVizsla-ov_ftdi In-Reply-To: <1965a7c4-85cc-b01c-75fc-983a76444253@slackbuilds.org> References: <1965a7c4-85cc-b01c-75fc-983a76444253@slackbuilds.org> Message-ID: thanks =) On Wed, Nov 1, 2017 at 8:44 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > *can anyone help me build:* > > https://github.com/openvizsla/ov_ftdi > > > > *build instructions:* > > https://github.com/openvizsla/ov_ftdi/wiki/building > > > > *this is what i get:* > > > > bash-4.4$ pwd > > ov_ftdi-1f980e821659d87bb0ed704e54ebb256a0547d92/software/fpga/ov3 > > bash-4.4$ make > > python3 build.py build_dir build build_name ov3 > > Traceback (most recent call last): > > File "build.py", line 1, in > > from ovplatform.ov3 import Platform > > File > > "/home/ferdna/Downloads/slackbuilds/ov-ftdi/ov-ftdi/ov_ftdi- > 1f980e821659d87bb0ed704e54ebb256a0547d92/software/fpga/ov3/ > ovplatform/ov3.py", > > line 1, in > > from mibuild.generic_platform import * > > ModuleNotFoundError: No module named 'mibuild' > > make: *** [Makefile:18: build/ov3.bit] Error 1 > > bash-4.4$ > > You probably need https://github.com/brandonhamilton/mibuild > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > 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 dpross1100 at msn.com Thu Nov 2 03:55:36 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Thu, 2 Nov 2017 03:55:36 +0000 Subject: [Slackbuilds-users] Email rejected during submission In-Reply-To: <20171101220918.345a3374@home.rlworkman.net> References: <20171101220918.345a3374@home.rlworkman.net> Message-ID: Well, in the meantime I submitted it with my alternate email address. I'll try to remember to do that in the future unless I hear otherwise. Thanks for looking into it. Dan On Wed, Nov 01, 2017 at 10:09:18PM -0500, Robby Workman wrote: > Top-posting to keep the pattern, even if I don't like it... > > Sorry, I have no idea what's wrong there - rob0? > > -RW > > > On Wed, 1 Nov 2017 04:27:56 +0000 > Daniel Prosser wrote: > > > Anyone? I see Jorge Giner Cordero had the exact same problem on > > October 1, but no one posted a solution. Actually, one person posted a > > suggestion to use (applying it to my case) "dpross1100 at msn.com," > > but that doesn't work. I would like to be able to update my scripts. > > > > Dan > > > > On Tue, Oct 31, 2017 at 03:43:20AM +0000, Daniel Prosser wrote: > > > Trying to submit an update to one of my SlackBuilds, I get this > > > error: > > > > > > ***** > > > [my email address] was rejected by mx2.hotmail.com. > > > Go back and enter a valid E-Mail address. > > > > > > If your mailserver uses Greylisting you may want to Whitelist > > > slackbuilds-users at slackbuilds.org. > > > ***** > > > > > > I have added slackbuilds-users at slackbuilds.org and also the > > > slackbuilds.org domain to my safe senders list. Anything else I can > > > do? This has never happened to me in the past. > > > > > > Dan > > > _______________________________________________ > > > 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/ > From kristofru at gmail.com Thu Nov 2 07:59:06 2017 From: kristofru at gmail.com (Chris Abela) Date: Thu, 2 Nov 2017 08:59:06 +0100 Subject: [Slackbuilds-users] ffmpeg does not build against libwebp Message-ID: ffmpeg builds fine against libwebp-0.5.2, but fails when built against libwebp-0.6.0: ffmpeg-3.2.4/tests/tiny_psnr.c ffmpeg-3.2.4/ffserver.c ffmpeg-3.2.4/ffmpeg.h ffmpeg-3.2.4/ffmpeg_dxva2.c ffmpeg-3.2.4/cmdutils_opencl.c ffmpeg-3.2.4/COPYING.LGPLv2.1 ffmpeg-3.2.4/ffmpeg_vaapi.c ffmpeg-3.2.4/README.md ffmpeg-3.2.4/CONTRIBUTING.md patching file configure patching file libavcodec/libopenjpegdec.c patching file libavcodec/libopenjpegenc.c ERROR: tesseract not found using pkg-config All the other dependencies are installed and updated, including tesseract. This is my sbopkg queue file: $ cat ffmpeg.sqf #ffmpeg @libass @libbluray @libbs2. @celt @libdc1394 @libebur128 @libfdk-aac @flite @frei0r @libgme @gsm @libiec61883 @libavc1394 @libilbc @ladspa_sdk @lame @libmodplug @netcdf @OpenAL @opencore-amr @opus @rtmpdump @rubberband @schroedinger @snappy @speex @tesseract @twolame @vid.stab @libwebp @x264 @x265 @xvidcore @zeromq @zvbi @jack-audio-connection-kit @SDL2 ffmpeg | ASS=yes BLURAY=yes BS2B=yes CELT=yes CHROMAPRINT=no DC1394=yes DECKLINK=no EBUR128=yes FDK_AAC=yes FLITE=yes FREI0R=yes GME=yes GSM=yes IEC61883=yes ILBC=yes LADSPA=yes LAME=yes MODPLUG=yes NETCDF=yes OPENAL=yes OPENCORE=yes OPENCV=no OPENSSL=yes OPUS=yes RTMP=yes RUBBERBAND=yes SCHROEDINGER=yes SNAPPY=yes SPEEX=yes TESSERACT=yes TWOLAME=yes VIDSTAB=yes WEBP=yes X264=yes X265=yes XVID=yes ZMQ=yes ZVBI=yes Chris From slackbuilds at schoepfer.info Thu Nov 2 08:42:50 2017 From: slackbuilds at schoepfer.info (Franzen) Date: Thu, 2 Nov 2017 09:42:50 +0100 Subject: [Slackbuilds-users] Email rejected during submission In-Reply-To: References: Message-ID: On 01.11.2017 05:27, Daniel Prosser wrote: > Anyone? I see Jorge Giner Cordero had the exact same problem on October > 1, but no one posted a solution. Actually, one person posted a > suggestion to use (applying it to my case) "dpross1100 at msn.com," but > that doesn't work. I assume it's about greylisting, especially because hotmail has many mx-records it may take several tries, depending on their setup. You may ask hotmail to whitelist the slackbuilds.org mta, but i got several bad experiences in the last few years with hotmail and their unpredictable mail handling/policy changes, spamhandling leading to disappead mails which accepted in first place with 250, broken html-Mails by the webfrontend etc. I doubt hotmail will help you, and if, it is likely it will be broken again some month later. Johannes From arnaud.garcia-fernandez at laposte.net Thu Nov 2 09:35:40 2017 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Thu, 2 Nov 2017 10:35:40 +0100 Subject: [Slackbuilds-users] ffmpeg does not build against libwebp In-Reply-To: References: Message-ID: <20171102103540.3d0e7a3fa49993acb5cc46e0@laposte.net> > ffmpeg builds fine against libwebp-0.5.2, but fails when built against > libwebp-0.6.0: > [...] > ERROR: tesseract not found using pkg-config > > All the other dependencies are installed and updated, including tesseract. > ffmpeg | ASS=yes BLURAY=yes BS2B=yes CELT=yes CHROMAPRINT=no DC1394=yes > DECKLINK=no EBUR128=yes FDK_AAC=yes FLITE=yes FREI0R=yes GME=yes GSM=yes > IEC61883=yes ILBC=yes LADSPA=yes LAME=yes MODPLUG=yes NETCDF=yes > OPENAL=yes OPENCORE=yes OPENCV=no OPENSSL=yes OPUS=yes RTMP=yes > RUBBERBAND=yes SCHROEDINGER=yes SNAPPY=yes SPEEX=yes TESSERACT=yes > TWOLAME=yes VIDSTAB=yes WEBP=yes X264=yes X265=yes XVID=yes ZMQ=yes ZVBI=yes I've just recompiled without problem ffmpeg with libwebp-0.6.0, here are my options : ASS=yes CELT=yes DC1394=yes FAAC=yes FDK_AAC=yes FLITE=yes FREI0R=yes GME=yes GSM=yes IEC61883=yes ILBC=yes LADSPA=yes LAME=yes MODPLUG=yes OPENAL=yes OPENCORE=yes OPENCV=yes OPENSSL=yes OPUS=yes QUVI=yes RTMP=yes SCHROEDINGER=yes SNAPPY=yes SPEEX=yes TWOLAME=yes VIDSTAB=yes WEBP=yes X264=yes X265=yes XVID=yes ZMQ=yes ZVBI=yes It looks to me the problem might be whith tesseract, and not libwebp. Maybe you should try recompiling/installing tesseract ? - Yth. From lists at osh.id.au Thu Nov 2 11:28:09 2017 From: lists at osh.id.au (David O'Shaughnessy) Date: Thu, 2 Nov 2017 21:28:09 +1000 Subject: [Slackbuilds-users] fzf 0.17.1 build failure Message-ID: <42134d4b-8621-6958-d7cc-b00ea0d234a9@osh.id.au> I'm having trouble building fzf 0.17.1 on Slack 14.2. I'm guessing this has something to do with the google-go-lang dependency (which I've installed). Some of the fzf errors look like: > fatal: Not a git repository (or any parent up to mount point /) > Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). > mkdir -p /tmp/SBo/fzf-0.17.1/gopath/src/github.com/junegunn/fzf > ... > gopath/src/github.com/junegunn/fzf/src/util/util.go:8:2: cannot find package "github.com/mattn/go-isatty" in any of: > /usr/src/github.com/mattn/go-isatty (from $GOROOT) > /tmp/SBo/fzf-0.17.1/gopath/src/github.com/mattn/go-isatty (from $GOPATH) > ... > Failures: > fzf: fzf.SlackBuild return non-zero Maybe this has something to do with GOPATH, but I have no idea what it's meant to be set to. The readme for google-go-lang doesn't seem that clear to me. -- Dave From willysr at slackbuilds.org Thu Nov 2 11:46:25 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 2 Nov 2017 18:46:25 +0700 Subject: [Slackbuilds-users] fzf 0.17.1 build failure In-Reply-To: <42134d4b-8621-6958-d7cc-b00ea0d234a9@osh.id.au> References: <42134d4b-8621-6958-d7cc-b00ea0d234a9@osh.id.au> Message-ID: <7e8046cd-0c0d-b717-d138-091ccfc124b6@slackbuilds.org> > I'm having trouble building fzf 0.17.1 on Slack 14.2. I'm guessing this > has something to do with the google-go-lang dependency (which I've > installed). Some of the fzf errors look like: > >> fatal: Not a git repository (or any parent up to mount point /) >> Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). >> mkdir -p /tmp/SBo/fzf-0.17.1/gopath/src/github.com/junegunn/fzf >> ... >> gopath/src/github.com/junegunn/fzf/src/util/util.go:8:2: cannot find package "github.com/mattn/go-isatty" in any of: >> /usr/src/github.com/mattn/go-isatty (from $GOROOT) >> /tmp/SBo/fzf-0.17.1/gopath/src/github.com/mattn/go-isatty (from $GOPATH) >> ... >> Failures: >> fzf: fzf.SlackBuild return non-zero > > Maybe this has something to do with GOPATH, but I have no idea what it's > meant to be set to. The readme for google-go-lang doesn't seem that > clear to me. please make sure you use "su -" instead of just regular su when building with google-go-lang since it needs to have correct environment variable. Other alternative is to log out and re-login before building -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From kristofru at gmail.com Thu Nov 2 12:33:25 2017 From: kristofru at gmail.com (Chris Abela) Date: Thu, 2 Nov 2017 13:33:25 +0100 Subject: [Slackbuilds-users] ffmpeg does not build against libwebp (SOLVED) In-Reply-To: References: Message-ID: Both tesseract and leptonica (required by tesseract) picked libwebp as a dependency. I removed libwebp, rebuilt leptonica and tesseract, reinstalled libwebp and now ffmpeg is building fine. Thanks to Arnaud for his hint. Chris On 02/11/17 08:59, Chris Abela wrote: > ffmpeg builds fine against libwebp-0.5.2, but fails when built against > libwebp-0.6.0: > > ffmpeg-3.2.4/tests/tiny_psnr.c > ffmpeg-3.2.4/ffserver.c > ffmpeg-3.2.4/ffmpeg.h > ffmpeg-3.2.4/ffmpeg_dxva2.c > ffmpeg-3.2.4/cmdutils_opencl.c > ffmpeg-3.2.4/COPYING.LGPLv2.1 > ffmpeg-3.2.4/ffmpeg_vaapi.c > ffmpeg-3.2.4/README.md > ffmpeg-3.2.4/CONTRIBUTING.md > patching file configure > patching file libavcodec/libopenjpegdec.c > patching file libavcodec/libopenjpegenc.c > ERROR: tesseract not found using pkg-config > > All the other dependencies are installed and updated, including > tesseract. > > This is my sbopkg queue file: > > $ cat ffmpeg.sqf > #ffmpeg > @libass > @libbluray > @libbs2. > @celt > @libdc1394 > @libebur128 > @libfdk-aac > @flite > @frei0r > @libgme > @gsm > @libiec61883 > @libavc1394 > @libilbc > @ladspa_sdk > @lame > @libmodplug > @netcdf > @OpenAL > @opencore-amr > @opus > @rtmpdump > @rubberband > @schroedinger > @snappy > @speex > @tesseract > @twolame > @vid.stab > @libwebp > @x264 > @x265 > @xvidcore > @zeromq > @zvbi > @jack-audio-connection-kit > @SDL2 > ffmpeg | ASS=yes BLURAY=yes BS2B=yes CELT=yes CHROMAPRINT=no > DC1394=yes DECKLINK=no EBUR128=yes FDK_AAC=yes FLITE=yes FREI0R=yes > GME=yes GSM=yes IEC61883=yes ILBC=yes LADSPA=yes LAME=yes MODPLUG=yes > NETCDF=yes OPENAL=yes OPENCORE=yes OPENCV=no OPENSSL=yes OPUS=yes > RTMP=yes RUBBERBAND=yes SCHROEDINGER=yes SNAPPY=yes SPEEX=yes > TESSERACT=yes TWOLAME=yes VIDSTAB=yes WEBP=yes X264=yes X265=yes > XVID=yes ZMQ=yes ZVBI=yes > > Chris > From lists at osh.id.au Thu Nov 2 17:01:53 2017 From: lists at osh.id.au (David O'Shaughnessy) Date: Fri, 3 Nov 2017 03:01:53 +1000 Subject: [Slackbuilds-users] fzf 0.17.1 build failure In-Reply-To: <7e8046cd-0c0d-b717-d138-091ccfc124b6@slackbuilds.org> References: <42134d4b-8621-6958-d7cc-b00ea0d234a9@osh.id.au> <7e8046cd-0c0d-b717-d138-091ccfc124b6@slackbuilds.org> Message-ID: <7eec91f7-13db-1990-e071-1ea67a001a20@osh.id.au> On 11/02/2017 09:46 PM, Willy Sudiarto Raharjo wrote: > > please make sure you use "su -" instead of just regular su when building > with google-go-lang since it needs to have correct environment variable. > Other alternative is to log out and re-login before building > I don't think that is the problem, since I do all my SBo stuff with "su -" these days (including for google-go-lang). Maybe I am missing something else, but I have no idea what. -- Dave From willysr at slackbuilds.org Thu Nov 2 17:03:20 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 3 Nov 2017 00:03:20 +0700 Subject: [Slackbuilds-users] fzf 0.17.1 build failure In-Reply-To: <7eec91f7-13db-1990-e071-1ea67a001a20@osh.id.au> References: <42134d4b-8621-6958-d7cc-b00ea0d234a9@osh.id.au> <7e8046cd-0c0d-b717-d138-091ccfc124b6@slackbuilds.org> <7eec91f7-13db-1990-e071-1ea67a001a20@osh.id.au> Message-ID: <7341a517-6bdd-3f3f-4765-b302ee34c8d2@slackbuilds.org> > I don't think that is the problem, since I do all my SBo stuff with "su > -" these days (including for google-go-lang). Maybe I am missing > something else, but I have no idea what. Well, i just tried to build fzf and it went fine after installing google-go-lang, have you logged out ? this ensures that the new environment is setup correctly in order to build fzf -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From lists at osh.id.au Thu Nov 2 18:52:14 2017 From: lists at osh.id.au (David O'Shaughnessy) Date: Fri, 3 Nov 2017 04:52:14 +1000 Subject: [Slackbuilds-users] fzf 0.17.1 build failure In-Reply-To: <7341a517-6bdd-3f3f-4765-b302ee34c8d2@slackbuilds.org> References: <42134d4b-8621-6958-d7cc-b00ea0d234a9@osh.id.au> <7e8046cd-0c0d-b717-d138-091ccfc124b6@slackbuilds.org> <7eec91f7-13db-1990-e071-1ea67a001a20@osh.id.au> <7341a517-6bdd-3f3f-4765-b302ee34c8d2@slackbuilds.org> Message-ID: <74b758ca-52f3-d0fd-eb81-0ae1c23b4cf1@osh.id.au> On 11/03/2017 03:03 AM, Willy Sudiarto Raharjo wrote: >> I don't think that is the problem, since I do all my SBo stuff with "su >> -" these days (including for google-go-lang). Maybe I am missing >> something else, but I have no idea what. > > Well, i just tried to build fzf and it went fine > after installing google-go-lang, have you logged out ? > this ensures that the new environment is setup correctly in order to > build fzf > I just tried building fzf in a console (with Ctrl-Alt-F2 to get outside of X), and it built. Thanks Willy. -- Dave From jorge.giner at hotmail.com Thu Nov 2 22:15:43 2017 From: jorge.giner at hotmail.com (Jorge Giner Cordero) Date: Thu, 2 Nov 2017 22:15:43 +0000 Subject: [Slackbuilds-users] Email rejected during submission In-Reply-To: References: <20171101220918.345a3374@home.rlworkman.net> Message-ID: Hi, I didn't find a solution. I submit with a different email address too. On 02/11/17 04:55, Daniel Prosser wrote: > Well, in the meantime I submitted it with my alternate email address. > I'll try to remember to do that in the future unless I hear otherwise. > Thanks for looking into it. > > Dan > > On Wed, Nov 01, 2017 at 10:09:18PM -0500, Robby Workman wrote: >> Top-posting to keep the pattern, even if I don't like it... >> >> Sorry, I have no idea what's wrong there - rob0? >> >> -RW >> >> >> On Wed, 1 Nov 2017 04:27:56 +0000 >> Daniel Prosser wrote: >> >>> Anyone? I see Jorge Giner Cordero had the exact same problem on >>> October 1, but no one posted a solution. Actually, one person posted a >>> suggestion to use (applying it to my case) "dpross1100 at msn.com," >>> but that doesn't work. I would like to be able to update my scripts. >>> >>> Dan >>> >>> On Tue, Oct 31, 2017 at 03:43:20AM +0000, Daniel Prosser wrote: >>>> Trying to submit an update to one of my SlackBuilds, I get this >>>> error: >>>> >>>> ***** >>>> [my email address] was rejected by mx2.hotmail.com. >>>> Go back and enter a valid E-Mail address. >>>> >>>> If your mailserver uses Greylisting you may want to Whitelist >>>> slackbuilds-users at slackbuilds.org. >>>> ***** >>>> >>>> I have added slackbuilds-users at slackbuilds.org and also the >>>> slackbuilds.org domain to my safe senders list. Anything else I can >>>> do? This has never happened to me in the past. >>>> >>>> Dan >>>> _______________________________________________ >>>> 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/ >> > _______________________________________________ > 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 aclemons at runbox.no Fri Nov 3 02:55:27 2017 From: aclemons at runbox.no (Andrew Clemons) Date: Fri, 3 Nov 2017 15:55:27 +1300 Subject: [Slackbuilds-users] stevedore fails to build, pbr too old Message-ID: <20171103025525.GC30602@runbox.no> Building stevedore is currently failing because the version of pbr on slackbuilds.org is too old. distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('pbr>=2.0.0') Bogdan, Dimitris - I'll let you two sort it out. I updated the slackbuild for the latest pbr (3.1.1) and the things I tested seem to be fine with that. Andrew -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From willysr at slackbuilds.org Fri Nov 3 05:52:33 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 3 Nov 2017 12:52:33 +0700 Subject: [Slackbuilds-users] stevedore fails to build, pbr too old In-Reply-To: <20171103025525.GC30602@runbox.no> References: <20171103025525.GC30602@runbox.no> Message-ID: > Building stevedore is currently failing because the version of pbr on > slackbuilds.org is too old. > > distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('pbr>=2.0.0') > > Bogdan, Dimitris - I'll let you two sort it out. I updated the > slackbuild for the latest pbr (3.1.1) and the things I tested seem to be > fine with that. Hi I just build stevedore using the one available in our repository and it build fine six: MD5SUM check for six-1.11.0.tar.gz ... OK Building package six-1.11.0-x86_64-1_SBo.tgz ... OK Installing package six-1.11.0-x86_64-1_SBo.tgz ... OK pbr: MD5SUM check for pbr-1.8.1.tar.gz ... OK Building package pbr-1.8.1-x86_64-1_SBo.tgz ... OK Installing package pbr-1.8.1-x86_64-1_SBo.tgz ... OK stevedore: MD5SUM check for stevedore-1.25.0.tar.gz ... OK Building package stevedore-1.25.0-x86_64-1_SBo.tgz ... OK Installing package stevedore-1.25.0-x86_64-1_SBo.tgz ... OK Did you build them on -current? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From aclemons at runbox.no Fri Nov 3 06:20:32 2017 From: aclemons at runbox.no (Andrew Clemons) Date: Fri, 3 Nov 2017 19:20:32 +1300 Subject: [Slackbuilds-users] stevedore fails to build, pbr too old In-Reply-To: References: <20171103025525.GC30602@runbox.no> Message-ID: <20171103062031.GA872@runbox.no> Hi, On 2017-11-03 12:52:33 +0700, willysr at slackbuilds.org wrote: > Hi > > I just build stevedore using the one available in our repository and it > build fine > > six: > MD5SUM check for six-1.11.0.tar.gz ... OK > Building package six-1.11.0-x86_64-1_SBo.tgz ... OK > Installing package six-1.11.0-x86_64-1_SBo.tgz ... OK > > pbr: > MD5SUM check for pbr-1.8.1.tar.gz ... OK > Building package pbr-1.8.1-x86_64-1_SBo.tgz ... OK > Installing package pbr-1.8.1-x86_64-1_SBo.tgz ... OK > > stevedore: > MD5SUM check for stevedore-1.25.0.tar.gz ... OK > Building package stevedore-1.25.0-x86_64-1_SBo.tgz ... OK > Installing package stevedore-1.25.0-x86_64-1_SBo.tgz ... OK > > Did you build them on -current? I am building on a clean build box of stable (14.2). You only notice if you are offline during the build. Otherwise it downloads silently from python.org during the build. pbr >= 2.0.0 is also in the requirements.txt: $ tar -xOf stevedore-1.25.0.tar.gz stevedore-1.25.0/requirements.txt # The order of packages is significant, because pip processes them in the order # of appearance. Changing the order has an impact on the overall integration # process, which may cause wedges in the gate later. pbr!=2.1.0,>=2.0.0 # Apache-2.0 six>=1.9.0 # MIT Thanks, Andrew # ./stevedore.SlackBuild stevedore-1.25.0/ stevedore-1.25.0/releasenotes/ stevedore-1.25.0/releasenotes/source/ stevedore-1.25.0/releasenotes/source/ocata.rst stevedore-1.25.0/releasenotes/source/_templates/ stevedore-1.25.0/releasenotes/source/_templates/.placeholder stevedore-1.25.0/releasenotes/source/unreleased.rst stevedore-1.25.0/releasenotes/source/conf.py stevedore-1.25.0/releasenotes/source/index.rst stevedore-1.25.0/releasenotes/source/_static/ stevedore-1.25.0/releasenotes/source/_static/.placeholder stevedore-1.25.0/releasenotes/notes/ stevedore-1.25.0/releasenotes/notes/add-reno-996dd44974d53238.yaml stevedore-1.25.0/.travis.yml stevedore-1.25.0/CONTRIBUTING.rst stevedore-1.25.0/.testr.conf stevedore-1.25.0/requirements.txt stevedore-1.25.0/tools/ stevedore-1.25.0/tools/tox_install.sh stevedore-1.25.0/test-requirements.txt stevedore-1.25.0/MANIFEST.in stevedore-1.25.0/setup.cfg stevedore-1.25.0/LICENSE stevedore-1.25.0/AUTHORS stevedore-1.25.0/stevedore/ stevedore-1.25.0/stevedore/dispatch.py stevedore-1.25.0/stevedore/__init__.py stevedore-1.25.0/stevedore/enabled.py stevedore-1.25.0/stevedore/example2/ stevedore-1.25.0/stevedore/example2/__init__.py stevedore-1.25.0/stevedore/example2/fields.py stevedore-1.25.0/stevedore/example2/setup.py stevedore-1.25.0/stevedore/hook.py stevedore-1.25.0/stevedore/driver.py stevedore-1.25.0/stevedore/exception.py stevedore-1.25.0/stevedore/named.py stevedore-1.25.0/stevedore/example/ stevedore-1.25.0/stevedore/example/__init__.py stevedore-1.25.0/stevedore/example/simple.py stevedore-1.25.0/stevedore/example/load_as_extension.py stevedore-1.25.0/stevedore/example/load_as_driver.py stevedore-1.25.0/stevedore/example/setup.py stevedore-1.25.0/stevedore/example/base.py stevedore-1.25.0/stevedore/sphinxext.py stevedore-1.25.0/stevedore/extension.py stevedore-1.25.0/stevedore/tests/ stevedore-1.25.0/stevedore/tests/test_dispatch.py stevedore-1.25.0/stevedore/tests/__init__.py stevedore-1.25.0/stevedore/tests/test_enabled.py stevedore-1.25.0/stevedore/tests/test_extension.py stevedore-1.25.0/stevedore/tests/utils.py stevedore-1.25.0/stevedore/tests/test_hook.py stevedore-1.25.0/stevedore/tests/test_example_fields.py stevedore-1.25.0/stevedore/tests/test_callback.py stevedore-1.25.0/stevedore/tests/test_example_simple.py stevedore-1.25.0/stevedore/tests/test_driver.py stevedore-1.25.0/stevedore/tests/manager.py stevedore-1.25.0/stevedore/tests/extension_unimportable.py stevedore-1.25.0/stevedore/tests/test_sphinxext.py stevedore-1.25.0/stevedore/tests/test_named.py stevedore-1.25.0/stevedore/tests/test_test_manager.py stevedore-1.25.0/PKG-INFO stevedore-1.25.0/setup.py stevedore-1.25.0/announce.rst stevedore-1.25.0/tox.ini stevedore-1.25.0/doc/ stevedore-1.25.0/doc/source/ stevedore-1.25.0/doc/source/user/ stevedore-1.25.0/doc/source/user/essays/ stevedore-1.25.0/doc/source/user/essays/invocation.jpg stevedore-1.25.0/doc/source/user/essays/api-enforcement.jpg stevedore-1.25.0/doc/source/user/essays/ceilometer-design.jpg stevedore-1.25.0/doc/source/user/essays/pycon2013.rst stevedore-1.25.0/doc/source/user/essays/importing.jpg stevedore-1.25.0/doc/source/user/essays/enabling.jpg stevedore-1.25.0/doc/source/user/essays/integration.jpg stevedore-1.25.0/doc/source/user/essays/discovery.jpg stevedore-1.25.0/doc/source/user/tutorial/ stevedore-1.25.0/doc/source/user/tutorial/driver_output.txt stevedore-1.25.0/doc/source/user/tutorial/extension_output.txt stevedore-1.25.0/doc/source/user/tutorial/loading.rst stevedore-1.25.0/doc/source/user/tutorial/creating_plugins.rst stevedore-1.25.0/doc/source/user/tutorial/naming.rst stevedore-1.25.0/doc/source/user/tutorial/index.rst stevedore-1.25.0/doc/source/user/tutorial/testing.rst stevedore-1.25.0/doc/source/user/history.rst stevedore-1.25.0/doc/source/user/sphinxext.rst stevedore-1.25.0/doc/source/user/patterns_loading.rst stevedore-1.25.0/doc/source/user/patterns_enabling.rst stevedore-1.25.0/doc/source/user/index.rst stevedore-1.25.0/doc/source/reference/ stevedore-1.25.0/doc/source/reference/index.rst stevedore-1.25.0/doc/source/conf.py stevedore-1.25.0/doc/source/index.rst stevedore-1.25.0/doc/source/install/ stevedore-1.25.0/doc/source/install/index.rst stevedore-1.25.0/doc/Makefile stevedore-1.25.0/ChangeLog stevedore-1.25.0/stevedore.egg-info/ stevedore-1.25.0/stevedore.egg-info/SOURCES.txt stevedore-1.25.0/stevedore.egg-info/not-zip-safe stevedore-1.25.0/stevedore.egg-info/top_level.txt stevedore-1.25.0/stevedore.egg-info/pbr.json stevedore-1.25.0/stevedore.egg-info/dependency_links.txt stevedore-1.25.0/stevedore.egg-info/PKG-INFO stevedore-1.25.0/stevedore.egg-info/entry_points.txt stevedore-1.25.0/stevedore.egg-info/requires.txt stevedore-1.25.0/README.rst Download error on https://pypi.python.org/simple/pbr/: [Errno -3] Temporary failure in name resolution -- Some packages may not be found! Download error on https://pypi.python.org/simple/: [Errno -3] Temporary failure in name resolution -- Some packages may not be found! No local packages or download links found for pbr>=2.0.0 Traceback (most recent call last): File "setup.py", line 29, in pbr=True) File "/usr/lib64/python2.7/distutils/core.py", line 111, in setup _setup_distribution = dist = klass(attrs) File "/usr/lib64/python2.7/site-packages/setuptools/dist.py", line 269, in __init__ self.fetch_build_eggs(attrs['setup_requires']) File "/usr/lib64/python2.7/site-packages/setuptools/dist.py", line 313, in fetch_build_eggs replace_conflicting=True, File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 826, in resolve dist = best[req.key] = env.best_match(req, ws, installer) File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 1092, in best_match return self.obtain(req, installer) File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 1104, in obtain return installer(requirement) File "/usr/lib64/python2.7/site-packages/setuptools/dist.py", line 380, in fetch_build_egg return cmd.easy_install(req) File "/usr/lib64/python2.7/site-packages/setuptools/command/easy_install.py", line 659, in easy_install raise DistutilsError(msg) distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('pbr>=2.0.0') -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From duncan_roe at optusnet.com.au Fri Nov 3 02:11:20 2017 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Fri, 3 Nov 2017 13:11:20 +1100 Subject: [Slackbuilds-users] Spelling error in perl-Unicode-Map README Message-ID: <20171103021119.GA16585@dimstar.local.net> Hi Larry, The fiorst word in README (perl-Unicod-Map) is missing 'e' after 'd' Cheers ... Duncan. From willysr at slackbuilds.org Fri Nov 3 14:44:53 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 3 Nov 2017 21:44:53 +0700 Subject: [Slackbuilds-users] Spelling error in perl-Unicode-Map README In-Reply-To: <20171103021119.GA16585@dimstar.local.net> References: <20171103021119.GA16585@dimstar.local.net> Message-ID: > The fiorst word in README (perl-Unicod-Map) is missing 'e' after 'd' Fixed in my branch thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From falsetti at clansco.org Fri Nov 3 16:59:24 2017 From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti) Date: Fri, 3 Nov 2017 17:59:24 +0100 Subject: [Slackbuilds-users] ffmpeg fails with new openjpeg-2.3 Message-ID: <20171103175924.dc1c878bba645caa2bf09698@clansco.org> Hi, ffmpeg fails with new openjpeg-2.3 config.log: fatal error: openjpeg-2.1/openjpeg.h: No such file or directory fatal error: openjpeg-2.0/openjpeg.h: No such file or directory fatal error: openjpeg-1.5/openjpeg.h: No such file or directory ERROR: libopenjpeg not found the same with ffmpeg 3.2.9 in ffmpeg 3.4 there seems to be a lot changes in features options From matteo.bernardini at gmail.com Fri Nov 3 19:07:20 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 3 Nov 2017 20:07:20 +0100 Subject: [Slackbuilds-users] ffmpeg fails with new openjpeg-2.3 In-Reply-To: <20171103175924.dc1c878bba645caa2bf09698@clansco.org> References: <20171103175924.dc1c878bba645caa2bf09698@clansco.org> Message-ID: 2017-11-03 17:59 GMT+01:00 Fr?d?ric Falsetti : > Hi, > ffmpeg fails with new openjpeg-2.3 > config.log: > fatal error: openjpeg-2.1/openjpeg.h: No such file or directory > fatal error: openjpeg-2.0/openjpeg.h: No such file or directory > fatal error: openjpeg-1.5/openjpeg.h: No such file or directory > ERROR: libopenjpeg not found > > the same with ffmpeg 3.2.9 > > in ffmpeg 3.4 there seems to be a lot changes in features options Hi Frederic, I think you haven't synced yet with the latest version in our repository because I added a patch for the newer openjpeg a couple of weeks ago. https://slackbuilds.org/repository/14.2/multimedia/ffmpeg/ Matteo From willysr at slackbuilds.org Sat Nov 4 00:48:30 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 4 Nov 2017 07:48:30 +0700 Subject: [Slackbuilds-users] Updates - 20171104.1 Message-ID: Back to our regular schedule and we are still busy as usual, with 80+ commits from maintainers in just three days. As promised, the SDL2 issue we found in the previous public update is now fixed and SDL2 updates (image, mixer) are merged in this batch. Andrew Clemons have managed to fix a bunch of broken script due to source URLs missing and a couple of other fixes while Audrius Ka?ukauskas delivered updates for docker-related and python-related scripts. At this moment, i'm testing nodejs-8.9.x which is now promoted into active LTS replacing the previous 6.11.x in a separate branch (node8-review). The new version requires some changes to some scripts which depends on nodejs and AFAIK, there's one script that's not building with the latest nodejs and that's vscode. Andre is still testing it and hopefully it will be fixed soon and we can move on to the next LTS release as suggested by upstream. have a nice weekend. PS: I made a WRONG force-push on master for a couple of minutes, before it gets reverted and restored to previous state. If you had a chance to get the wrong commits on master and having problems using third party tools, i suggest to re-clone the repo and it should be fixed. If you update your local repository after you read this announcement, then you can simply skip this step and do the normal update. My apologies for those who are affected. It happened while we (me and David) accidentally push the same xed update and i wanted to revert it. I ran the git reset and git push -f while not looking at the current branch i'm in at that moment. Luckily i have other machine which has the old state (not yet updated with the latest one) and i can revert it quickly. Sat Nov 4 00:18:47 UTC 2017 academic/itex2mml: Remove obsolete patch. academic/paml: Update DOWNLOAD url. academic/pyCRAC: Added (Next generation sequencing analysis). academic/veusz: Updated for version 2.1. desktop/XDecorations: Update DOWNLOAD url. desktop/jgmenu: Added (Small X11 menu for openbox and tint2). desktop/polybar: Fix building against newer libcurl. desktop/xed: Updated for version 1.6.0. development/android-tools: Updated for version 8.0.0_r24. development/casperjs: Fix M5SUM and tarball handling. development/d-tools: Updated for version 2.077.0 development/dmd: Updated for version 2.077.0 development/ebe: Update DOWNLOAD url. development/fsharp - Fix tarball handling. development/gecode: Update DOWNLOAD url. development/gsoap: Update DOWNLOAD url. development/ioncube-loader: Updated for version 10.0.4 development/jupyter-notebook: Updated for version 5.2.1. development/racer: Updated for version 2.0.12. development/universal-ctags: Updated for version 96ceef6 games/bloodcm: Fix DOWNLOAD url. games/doomretro: Patched to support SDL2. games/dunelegacy: Patched to support SDL2. games/galaxyv2: Update DOWNLOAD url. games/pangzero: Update deb version and DOWNLOAD url. games/supermariowar: Add patch to find newer yaml-cpp. gis/osgEarth: Update DOWNLOAD url. graphics/fbpic: Update DOWNLOAD url. graphics/fotoxx: Update DOWNLOAD url. graphics/opencollada: Updated for version 1.6.60 graphics/sxiv: Updated for version 24. ham/demorse: Update DOWNLOAD url. ham/fldigi: Updated for version 4.0.12. ham/xdemorse: Update DOWNLOAD url. ham/xwxapt: Update DOWNLOAD url. libraries/Kivy: Patched to support SDL2. libraries/SDL2: Updated for version 2.0.7. libraries/SDL2_image: Updated for version 2.0.2. libraries/SDL2_mixer: Updated for version 2.0.2. libraries/log4net: Update DOWNLOAD url. libraries/mysql++: Update DOWNLOAD url. libraries/zuluplay: Added (fork for tcplay). misc/dcc: Update DOWNLOAD url and tarball handling. misc/floating-IPS: Update DOWNLOAD url. multimedia/ctl: Fix tarball handling. multimedia/flowblade: Updated for version 1.14. multimedia/flvtool2: Update DOWNLOAD url. network/WireGuard: Updated for version 0.0.20171101. network/apt-mirror: Added (APT sources mirroring tool). network/cacti-spine: Updated for version 1.1.27. network/cacti: Updated for version 1.1.27. network/dobbscoin: Fix MD5SUM. network/psi: Updated for version 1.3 office/pyspread: Updated for version 1.1.1. perl/perl-Unicode-Map: Fix typo. python/defusedxml: Added (XML bomb protection for Python). python/dulwich: Updated for version 0.18.5. python/hg-git: Updated for version 0.8.10. python/hgsubversion: Updated for version 1.9. python/mibuild: Added (Milkymist Build system). python/migen: Added (Milkymist generator). python/pypy3: Updated for version 5.9_beta. python/pypy: Updated for version 5.9. python/python-cached-property: Updated for version 1.3.1. python/python-faulthandler: Updated for version 3.0. python/python-fonttools: Updated for version 3.18.0. python/python3-jupyter_core: Updated for version 4.4.0. python/python3: Updated for version 3.6.3. python/selenium: Updated for version 3.7.0. system/containerd: Updated for version 0.2.9_06b9cb3. system/docker-compose: Updated for version 1.17.0. system/docker-machine-kvm: Added (KVM driver for docker-machine). system/docker-machine: Updated for version 0.13.0. system/docker: Updated for version 17.09.0. system/hashcat: Switch to github URL. system/isdct: Updated for version 3.0.9. system/mkslack: Added (a SlackBuild generation system). system/redis: Updated for version 4.0.2. system/runc: Updated for version 1.0.0_rc4_3f2f8b8. system/sboui: Updated for version 0.5. system/sddm: Patched + important info in README. system/sysdig: Fix building against newer libcurl. system/zuluCrypt: Add new optional dep zuluplay. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From fernando.lopezjr at gmail.com Sat Nov 4 00:58:19 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Fri, 3 Nov 2017 18:58:19 -0600 Subject: [Slackbuilds-users] help building OpenVizsla-ov_ftdi In-Reply-To: References: <1965a7c4-85cc-b01c-75fc-983a76444253@slackbuilds.org> Message-ID: now it is asking for fhdl, it is supposedly in the repo... https://github.com/m-labs/migen/tree/master/migen/fhdl bash-4.4$ python3 build.py Traceback (most recent call last): File "build.py", line 1, in from ovplatform.ov3 import Platform File "ov_ftdi-1f980e821659d87bb0ed704e54ebb256a0547d92/software/fpga/ov3/ovplatform/ov3.py", line 1, in from mibuild.generic_platform import * File "/usr/lib64/python3.6/site-packages/mibuild/generic_platform.py", line 4, in from migen.fhdl.std import * ModuleNotFoundError: No module named 'migen.fhdl.std' any ideas? thank you! On Wed, Nov 1, 2017 at 9:19 PM, Fernando Lopez wrote: > thanks =) > > On Wed, Nov 1, 2017 at 8:44 PM, Willy Sudiarto Raharjo < > willysr at slackbuilds.org> wrote: > >> > *can anyone help me build:* >> > https://github.com/openvizsla/ov_ftdi >> > >> > *build instructions:* >> > https://github.com/openvizsla/ov_ftdi/wiki/building >> > >> > *this is what i get:* >> > >> > bash-4.4$ pwd >> > ov_ftdi-1f980e821659d87bb0ed704e54ebb256a0547d92/software/fpga/ov3 >> > bash-4.4$ make >> > python3 build.py build_dir build build_name ov3 >> > Traceback (most recent call last): >> > File "build.py", line 1, in >> > from ovplatform.ov3 import Platform >> > File >> > "/home/ferdna/Downloads/slackbuilds/ov-ftdi/ov-ftdi/ov_ftdi- >> 1f980e821659d87bb0ed704e54ebb256a0547d92/software/fpga/ov3/o >> vplatform/ov3.py", >> > line 1, in >> > from mibuild.generic_platform import * >> > ModuleNotFoundError: No module named 'mibuild' >> > make: *** [Makefile:18: build/ov3.bit] Error 1 >> > bash-4.4$ >> >> You probably need https://github.com/brandonhamilton/mibuild >> >> >> -- >> Willy Sudiarto Raharjo >> >> >> _______________________________________________ >> 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. > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From falsetti at clansco.org Sat Nov 4 06:45:16 2017 From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti) Date: Sat, 4 Nov 2017 07:45:16 +0100 Subject: [Slackbuilds-users] ffmpeg fails with new openjpeg-2.3 In-Reply-To: References: <20171103175924.dc1c878bba645caa2bf09698@clansco.org> Message-ID: <20171104074516.dbac53d5ef5adc4301cd304f@clansco.org> Oops, you're right, I forgot to update. Sorry for the inconvenience. I must finally decide to use rsync! On Fri, 3 Nov 2017 20:07:20 +0100 Matteo Bernardini wrote: > 2017-11-03 17:59 GMT+01:00 Fr?d?ric Falsetti : > > Hi, > > ffmpeg fails with new openjpeg-2.3 > > config.log: > > fatal error: openjpeg-2.1/openjpeg.h: No such file or directory > > fatal error: openjpeg-2.0/openjpeg.h: No such file or directory > > fatal error: openjpeg-1.5/openjpeg.h: No such file or directory > > ERROR: libopenjpeg not found > > > > the same with ffmpeg 3.2.9 > > > > in ffmpeg 3.4 there seems to be a lot changes in features options > > Hi Frederic, > > I think you haven't synced yet with the latest version in our > repository because I added a patch for the newer openjpeg a couple of > weeks ago. > > https://slackbuilds.org/repository/14.2/multimedia/ffmpeg/ > > Matteo > _______________________________________________ > 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 falsetti at clansco.org Sat Nov 4 17:37:17 2017 From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti) Date: Sat, 4 Nov 2017 18:37:17 +0100 Subject: [Slackbuilds-users] saga including vigra fails Message-ID: <20171104183717.f93dee1e90f74da1859d17ff@clansco.org> Hi, build_saga-gis_log : .../ /usr/include/c++/5.3.0/bits/c++0x_warning.h:32:2: erreur: #error This file requires compiler and library support for the ISO C++ 2011 standard. This support is currently experimental, and must be enabled with the -std=c++11 or -std=gnu++11 compiler options. From rob0 at slackbuilds.org Sat Nov 4 20:14:26 2017 From: rob0 at slackbuilds.org (Rob McGee) Date: Sat, 4 Nov 2017 15:14:26 -0500 Subject: [Slackbuilds-users] Email rejected during submission In-Reply-To: References: Message-ID: <20171104201426.GD2027@harrier.slackbuilds.org> On Thu, Nov 02, 2017 at 09:42:50AM +0100, Franzen wrote: > On 01.11.2017 05:27, Daniel Prosser wrote: > > Anyone? I see Jorge Giner Cordero had the exact same problem on > > October 1, but no one posted a solution. Actually, one person > > posted a suggestion to use (applying it to my case) "dpross1100 > > at msn.com," but that doesn't work. > > I assume it's about greylisting, especially because hotmail has > many mx-records it may take several tries, depending on their > setup. You may ask hotmail to whitelist the slackbuilds.org mta, Actually no, the Slackbuilds.org MTA has no trouble delivering mail to Microsoft addresses. There are several here on the users' list. The address verification probes are done on the SBo web server, not on the mail server. > but i got several bad experiences in the last few years with > hotmail and their unpredictable mail handling/policy changes, > spamhandling leading to disappead mails which accepted in first > place with 250, broken html-Mails by the webfrontend etc. > > I doubt hotmail will help you, and if, it is likely it will be > broken again some month later. Actually no again. Right now it seems that Microsoft is among the most responsive in the industry. I would not hesitate to ask them for help, but unfortunately I have nothing to go on. We would need to have logs of these delivery attempts along with exact rejection messages received. What gets to the submitter's browser is inadequate for troubleshooting. -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From johannes at schoepfer.info Sat Nov 4 21:52:22 2017 From: johannes at schoepfer.info (johannes at schoepfer.info) Date: Sat, 04 Nov 2017 22:52:22 +0100 Subject: [Slackbuilds-users] Email rejected during submission In-Reply-To: <20171104201426.GD2027@harrier.slackbuilds.org> References: <20171104201426.GD2027@harrier.slackbuilds.org> Message-ID: <0e66807be9a3045ac8b5f88f577508c6@schoepfer.info> On 2017-11-04 21:14, Rob McGee wrote: > On Thu, Nov 02, 2017 at 09:42:50AM +0100, Franzen wrote: >> On 01.11.2017 05:27, Daniel Prosser wrote: >> > Anyone? I see Jorge Giner Cordero had the exact same problem on >> > October 1, but no one posted a solution. Actually, one person >> > posted a suggestion to use (applying it to my case) "dpross1100 >> > at msn.com," but that doesn't work. >> >> I assume it's about greylisting, especially because hotmail has >> many mx-records it may take several tries, depending on their >> setup. You may ask hotmail to whitelist the slackbuilds.org mta, > > Actually no, the Slackbuilds.org MTA has no trouble delivering mail > to Microsoft addresses. There are several here on the users' list. I don't want to blame SBo's mta, it's just a guess with greylisting, i don't have your maillog. I meant that greylisting may be a problem for submitting, not for this list where the mta has several tries until sending succseeds. > The address verification probes are done on the SBo web server, not > on the mail server. Ok, then the web server does something with hotmail's mx servers, are there logs? >> but i got several bad experiences in the last few years with >> hotmail and their unpredictable mail handling/policy changes, >> spamhandling leading to disappead mails which accepted in first >> place with 250, broken html-Mails by the webfrontend etc. >> >> I doubt hotmail will help you, and if, it is likely it will be >> broken again some month later. > > Actually no again. Right now it seems that Microsoft is among the > most responsive in the industry. I would not hesitate to ask them > for help, but unfortunately I have nothing to go on. Daniel and Jorge aren't able to submit via hotmail, and your statement is that the problem is not an SBo's side. @Jorge: The git log says you submitted obnc-libstd on 2017-10-31 with your hotmail-address. I don't know much of git and what's possible, was that mailaddress the one you used to submit or not? Johannes From erik at slackbuilds.org Sat Nov 4 23:18:50 2017 From: erik at slackbuilds.org (Erik Hanson) Date: Sat, 4 Nov 2017 18:18:50 -0500 Subject: [Slackbuilds-users] Email rejected during submission In-Reply-To: <0e66807be9a3045ac8b5f88f577508c6@schoepfer.info> References: <20171104201426.GD2027@harrier.slackbuilds.org> <0e66807be9a3045ac8b5f88f577508c6@schoepfer.info> Message-ID: On 11/04/2017 04:52 PM, johannes at schoepfer.info wrote: >> The address verification probes are done on the SBo web server, not >> on the mail server. > > Ok, then the web server does something with hotmail's mx servers, are > there logs? No, it's not an MTA. It does this: lookup MX and connect, wait for 220 send HELO slackbuilds.org wait for response send MAIL FROM: wait for 250 send RCPT TO: <$Email> wait for 250 send QUIT If either response is not 250 then it's considered rejected. It's very simple, follows the RFC, and works 99.99% of the time. I'm not personally interested in any suggestions for making it more robust, as I'm confident that would only raise the failure rate until we've either written an entire MTA or unnecessarily swapped it out for a proper one. >>> but i got several bad experiences in the last few years with >>> hotmail and their unpredictable mail handling/policy changes, >>> spamhandling leading to disappead mails which accepted in first >>> place with 250, broken html-Mails by the webfrontend etc. >>> >>> I doubt hotmail will help you, and if, it is likely it will be >>> broken again some month later. >> >> Actually no again.? Right now it seems that Microsoft is among the >> most responsive in the industry.? I would not hesitate to ask them >> for help, but unfortunately I have nothing to go on. > > Daniel and Jorge aren't able to submit via hotmail, and your statement > is that the problem is not an SBo's side. > > @Jorge: The git log says you submitted obnc-libstd on 2017-10-31 with > your hotmail-address. I don't know much of git and what's possible, was > that mailaddress the one you used to submit or not? A quick check of old submissions suggests they are not. The email address you use to submit does not need to match the info file, is not stored anywhere, and will not be displayed anywhere. It is only used for sending you a confirmation email containing a removal code. At the end of the day, it was working and now it isn't. The code on the server for checking emails has not changed in many years, so something at hotmail has changed. Either use another address on the submit form, or contact Microsoft if it really bothers you and you want it fixed. -- Erik -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From slackbuilds at jaxartes.net Sun Nov 5 00:14:10 2017 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sat, 04 Nov 2017 17:14:10 -0700 Subject: [Slackbuilds-users] saga including vigra fails In-Reply-To: <20171104183717.f93dee1e90f74da1859d17ff@clansco.org> References: <20171104183717.f93dee1e90f74da1859d17ff@clansco.org> Message-ID: <5969312.VeGTXEUWYz@wintermute> On Saturday, November 4, 2017 10:37:17 AM PDT Fr?d?ric Falsetti wrote: > Hi, > build_saga-gis_log : > .../ > /usr/include/c++/5.3.0/bits/c++0x_warning.h:32:2: erreur: #error This file > requires compiler and library support for the ISO C++ 2011 standard. This > support is currently experimental, and must be enabled with the -std=c++11 > or -std=gnu++11 compiler options. Seems like there is a known issue with compiling SAGA with vigra (not the exact issue, but see https://sourceforge.net/p/saga-gis/bugs/244/). Since this is an optional dependency that isn't expected by this SlackBuild, I will put a note in the README that it is currently not compatible. Thanks for the report! From thedoogster at gmail.com Sun Nov 5 13:31:37 2017 From: thedoogster at gmail.com (Doogster) Date: Sun, 5 Nov 2017 05:31:37 -0800 Subject: [Slackbuilds-users] Please remove my email address from the tint2 SlackBuild keywords Message-ID: Could you please remove my email address from the list of keywords for the tint2 SlackBuilds? From willysr at slackbuilds.org Sun Nov 5 17:12:35 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 6 Nov 2017 00:12:35 +0700 Subject: [Slackbuilds-users] Please remove my email address from the tint2 SlackBuild keywords In-Reply-To: References: Message-ID: <7cc97e97-4dae-19da-074b-9b96c76bf912@slackbuilds.org> > Could you please remove my email address from the list of keywords for > the tint2 SlackBuilds? Done already -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From kristofru at gmail.com Mon Nov 6 07:24:52 2017 From: kristofru at gmail.com (Chris Abela) Date: Mon, 6 Nov 2017 08:24:52 +0100 Subject: [Slackbuilds-users] Tor builds against libseccomp if found Message-ID: $ requiredbuilder -i tor attr glibc-solibs libcap libevent *libseccomp* openssl | openssl-solibs xz zlib $ whereis libseccomp libseccomp: /usr/lib64/libseccomp.la /usr/lib64/libseccomp.so $ grep usr/lib64/libseccomp /var/log/packages/* /var/log/packages/libseccomp-2.3.2-x86_64-1_SBo:usr/lib64/libseccomp.la /var/log/packages/libseccomp-2.3.2-x86_64-1_SBo:usr/lib64/libseccomp.so.2.3.2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristofru at gmail.com Mon Nov 6 09:20:56 2017 From: kristofru at gmail.com (Chris Abela) Date: Mon, 6 Nov 2017 10:20:56 +0100 Subject: [Slackbuilds-users] nextcloud-client conditional dependency Message-ID: qt5-webkit is listed a dependency for nextcloud-client, however this is only required if qt5 is found. From dpross1100 at msn.com Tue Nov 7 03:55:50 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Tue, 7 Nov 2017 03:55:50 +0000 Subject: [Slackbuilds-users] perl-MailTools source download 404 Message-ID: Hi, The source download for perl-MailTools seems to have disappeared. However, a newer version is available and the SlackBuild at least completes with a simple version bump. Here are patches to the .info and SlackBuild files for consideration. Regards, Dan -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: perl-MailTools.SlackBuild.diff URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: perl-MailTools.info.diff URL: From dpross1100 at msn.com Tue Nov 7 03:59:11 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Tue, 7 Nov 2017 03:59:11 +0000 Subject: [Slackbuilds-users] Change needed in ZoneMinder README Message-ID: Hi, The ZoneMinder README says that perl-MIME-Entity is an optional dependency for automatic event mail notification. However, there is no such SlackBuild in the repo. I believe the correct one is perl-MIME-tools. Regards, Dan From willysr at slackbuilds.org Tue Nov 7 06:18:08 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 7 Nov 2017 13:18:08 +0700 Subject: [Slackbuilds-users] Change needed in ZoneMinder README In-Reply-To: References: Message-ID: > The ZoneMinder README says that perl-MIME-Entity is an optional > dependency for automatic event mail notification. However, there is no > such SlackBuild in the repo. I believe the correct one is > perl-MIME-tools. Done in my branch thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Tue Nov 7 06:21:34 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 7 Nov 2017 13:21:34 +0700 Subject: [Slackbuilds-users] perl-MailTools source download 404 In-Reply-To: References: Message-ID: <26b1ee45-1a81-3afc-ea0d-c3c74154fb40@slackbuilds.org> > The source download for perl-MailTools seems to have disappeared. > However, a newer version is available and the SlackBuild at least > completes with a simple version bump. Here are patches to the .info and > SlackBuild files for consideration. Thanks applied in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From baildon.research at googlemail.com Tue Nov 7 10:21:51 2017 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 7 Nov 2017 10:21:51 +0000 Subject: [Slackbuilds-users] nextcloud-client conditional dependency In-Reply-To: References: Message-ID: > qt5-webkit is listed a dependency for nextcloud-client, however this is only > required if qt5 is found. That's my fault -- sorry about that, I'll correct it in time for the next public update. I incorrectly assumed that the latest version now requires qt5, and "fixed" it, but in fact, I had introduced the qt5 dependency myself via qtkeychain :-( Thanks for the feedback, it's always welcome :) -D. From vytautas1987 at yahoo.com Tue Nov 7 11:37:22 2017 From: vytautas1987 at yahoo.com (Vytautas Rakeviius) Date: Tue, 7 Nov 2017 11:37:22 +0000 (UTC) Subject: [Slackbuilds-users] http://slackbuilds.org/repository/14.2/perl/perl-xml-libxml/?search=perl-xml-libxml References: <1140413748.3633815.1510054642684.ref@mail.yahoo.com> Message-ID: <1140413748.3633815.1510054642684@mail.yahoo.com> http://slackbuilds.org/repository/14.2/perl/perl-xml-libxml/?search=perl-xml-libxml I tried this one and it seems bad.It builds into same folder where Slackbuild is not into tmp.File extension is non standard I had to rename.I installed it and I do not see way to remove it.I do not think that I have functional install. -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackbuilds at schoepfer.info Tue Nov 7 13:27:13 2017 From: slackbuilds at schoepfer.info (Franzen) Date: Tue, 7 Nov 2017 14:27:13 +0100 Subject: [Slackbuilds-users] Email rejected during submission In-Reply-To: References: <20171104201426.GD2027@harrier.slackbuilds.org> <0e66807be9a3045ac8b5f88f577508c6@schoepfer.info> Message-ID: On 05.11.2017 00:18, Erik Hanson wrote: > On 11/04/2017 04:52 PM, johannes at schoepfer.info wrote: >>> The address verification probes are done on the SBo web server, not >>> on the mail server. >> >> Ok, then the web server does something with hotmail's mx servers, are >> there logs? > > No, it's not an MTA. It does this: > lookup MX and connect, wait for 220 > send HELO slackbuilds.org > wait for response > send MAIL FROM: > wait for 250 > send RCPT TO: <$Email> > wait for 250 > send QUIT > > If either response is not 250 then it's considered rejected. It's very > simple, follows the RFC, and works 99.99% of the time. I'm not > personally interested in any suggestions for making it more robust, as > I'm confident that would only raise the failure rate until we've either > written an entire MTA or unnecessarily swapped it out for a proper one. No suggestion for anything, just fyi, it seems hotmail enforces starttls, the smtp dialog works e.g. when openssl is used for the connection. It doesn't work if "rcpt to" is written in caps in conjunction with openssl: openssl s_client -starttls smtp -crlf -connect hotmail-com.olc.protection.outlook.com:25 ... 250 CHUNKING helo mail2.0ur.de 250 SN1NAM04FT013.mail.protection.outlook.com Hello [37.187.104.228] mail from: 250 2.1.0 Sender OK rcpt to: 250 2.1.5 Recipient OK quit 221 2.0.0 Service closing transmission channel read:errno=0 Enforced starttls may occour more often in the future. Johannes From andrew at stevens.is Tue Nov 7 20:25:11 2017 From: andrew at stevens.is (Andrew) Date: Tue, 07 Nov 2017 15:25:11 -0500 Subject: [Slackbuilds-users] nextcloud-client conditional dependency In-Reply-To: References: Message-ID: Not entirely your fault, I take blame for maybe not being clear enough in the patch I sent. Thanks for the work you do! Warm Regards, Andrew Stevens andrew at stevens.is > -------- Original Message -------- > Subject: Re: [Slackbuilds-users] nextcloud-client conditional dependency > Local Time: November 7, 2017 11:21 PM > UTC Time: November 7, 2017 10:21 AM > From: baildon.research at googlemail.com > To: SlackBuilds.org Users List > >> qt5-webkit is listed a dependency for nextcloud-client, however this is only >> required if qt5 is found. >> >> That's my fault -- sorry about that, I'll correct it in time for the >> next public update. >> >> I incorrectly assumed that the latest version now requires qt5, and >> "fixed" it, but in fact, I had introduced the qt5 dependency myself >> via qtkeychain :-( >> >> Thanks for the feedback, it's always welcome :) >> -D. > > --------------------------------------------------------------- > > 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 andreas.guldstrand at gmail.com Thu Nov 9 16:22:11 2017 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Thu, 9 Nov 2017 17:22:11 +0100 Subject: [Slackbuilds-users] The future of the mpv SlackBuild Message-ID: Hi all, I'm the current maintainer of the mpv SlackBuild, and don't worry, I'm not about to give it up or anything like that. I am however looking for opinions on how to proceed in the future because of a rather drastic change in mpv's dependencies. What has happened is this: mpv has dropped its dependency on ffmpeg, and instead depend on a specific mpv fork of ffmpeg that they call 'ffmpeg-mpv'. The reasons they've done so are not really relevant for this list, so let's not dwell on those (for the curious, you can take a look through https://github.com/mpv-player/mpv/commit/83d44aca7dc7f46b8d3b64d441f5a8317a40e080 ). The issue I'm facing is how to deal with this change once a new version is released. I'm currently considering three options for how to proceed: 1. Include the building of 'ffmpeg-mpv' inside the mpv SlackBuild and statically link it, since it's likely that only mpv will be relying on the 'ffmpeg-mpv' fork. 2. Make a new 'ffmpeg-mpv' SlackBuild and try to make sure it doesn't conflict with the regular ffmpeg SlackBuild. 3. Wait for other distributions to make patches for mpv available so it can play nice with the regular ffmpeg. I'd of course also take such patches from the SlackBuilds.org community should you be able to provide such things. There is no chance that I would make one on my own however. I'm personally favouring option 1, but would like input from the rest of the community. There are a few things that make me consider option 3 as my least favourite option. For instance the mpv folks are less likely to support a nonstandard build like that, and it makes us dependent on other distributions keeping up with changes to both ffmpeg and mpv. I am still considering it though since it will mean there is only one ffmpeg on SBo, so you only need to build it for the first program that depends on it, it won't cause conflicts, and all the options for ffmpeg are quite a chore to need to make sure they all work as they should. Regards / Andreas Guldstrand From matteo.bernardini at gmail.com Thu Nov 9 16:31:44 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 9 Nov 2017 17:31:44 +0100 Subject: [Slackbuilds-users] The future of the mpv SlackBuild In-Reply-To: References: Message-ID: 2017-11-09 17:22 GMT+01:00 Andreas Guldstrand : > Hi all, > > I'm the current maintainer of the mpv SlackBuild, and don't worry, I'm > not about to give it up or anything like that. I am however looking > for opinions on how to proceed in the future because of a rather > drastic change in mpv's dependencies. > > What has happened is this: mpv has dropped its dependency on ffmpeg, > and instead depend on a specific mpv fork of ffmpeg that they call > 'ffmpeg-mpv'. The reasons they've done so are not really relevant for > this list, so let's not dwell on those (for the curious, you can take > a look through https://github.com/mpv-player/mpv/commit/83d44aca7dc7f46b8d3b64d441f5a8317a40e080 > ). > > The issue I'm facing is how to deal with this change once a new > version is released. I'm currently considering three options for how > to proceed: > > 1. Include the building of 'ffmpeg-mpv' inside the mpv SlackBuild and > statically link it, since it's likely that only mpv will be relying on > the 'ffmpeg-mpv' fork. > > 2. Make a new 'ffmpeg-mpv' SlackBuild and try to make sure it doesn't > conflict with the regular ffmpeg SlackBuild. > > 3. Wait for other distributions to make patches for mpv available so > it can play nice with the regular ffmpeg. I'd of course also take such > patches from the SlackBuilds.org community should you be able to > provide such things. There is no chance that I would make one on my > own however. > > I'm personally favouring option 1, but would like input from the rest > of the community. > > There are a few things that make me consider option 3 as my least > favourite option. For instance the mpv folks are less likely to > support a nonstandard build like that, and it makes us dependent on > other distributions keeping up with changes to both ffmpeg and mpv. > > I am still considering it though since it will mean there is only one > ffmpeg on SBo, so you only need to build it for the first program that > depends on it, it won't cause conflicts, and all the options for > ffmpeg are quite a chore to need to make sure they all work as they > should. IMHO I would go for the first option (looks the cleanest to me), eventually moving to the second only if needed by something else. Matteo From atelszewski at gmail.com Thu Nov 9 17:51:11 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 9 Nov 2017 18:51:11 +0100 Subject: [Slackbuilds-users] The future of the mpv SlackBuild In-Reply-To: References: Message-ID: On 09/11/17 17:31, Matteo Bernardini wrote: > 2017-11-09 17:22 GMT+01:00 Andreas Guldstrand : >> Hi all, >> >> I'm the current maintainer of the mpv SlackBuild, and don't worry, I'm >> not about to give it up or anything like that. I am however looking >> for opinions on how to proceed in the future because of a rather >> drastic change in mpv's dependencies. >> >> What has happened is this: mpv has dropped its dependency on ffmpeg, >> and instead depend on a specific mpv fork of ffmpeg that they call >> 'ffmpeg-mpv'. The reasons they've done so are not really relevant for >> this list, so let's not dwell on those (for the curious, you can take >> a look through https://github.com/mpv-player/mpv/commit/83d44aca7dc7f46b8d3b64d441f5a8317a40e080 >> ). >> >> The issue I'm facing is how to deal with this change once a new >> version is released. I'm currently considering three options for how >> to proceed: >> >> 1. Include the building of 'ffmpeg-mpv' inside the mpv SlackBuild and >> statically link it, since it's likely that only mpv will be relying on >> the 'ffmpeg-mpv' fork. >> >> 2. Make a new 'ffmpeg-mpv' SlackBuild and try to make sure it doesn't >> conflict with the regular ffmpeg SlackBuild. >> >> 3. Wait for other distributions to make patches for mpv available so >> it can play nice with the regular ffmpeg. I'd of course also take such >> patches from the SlackBuilds.org community should you be able to >> provide such things. There is no chance that I would make one on my >> own however. >> >> I'm personally favouring option 1, but would like input from the rest >> of the community. >> >> There are a few things that make me consider option 3 as my least >> favourite option. For instance the mpv folks are less likely to >> support a nonstandard build like that, and it makes us dependent on >> other distributions keeping up with changes to both ffmpeg and mpv. >> >> I am still considering it though since it will mean there is only one >> ffmpeg on SBo, so you only need to build it for the first program that >> depends on it, it won't cause conflicts, and all the options for >> ffmpeg are quite a chore to need to make sure they all work as they >> should. > > IMHO I would go for the first option (looks the cleanest to me), > eventually moving to the second only if needed by something else. > If possible, I wouldn't link statically, but install shared ffmpeg-mpv in lib dir specifically created and known for mpv. But, meh ;-) Option (2) makes sense if both mpv and ffmpeg-mpv are kept and updated separately. So for example ffmpeg-mpv is at version 0.1 and mpv goes from 0.1 -> 0.2, then you only need to update mpv. Otherwise, use method (1) to keep house clean. You can surely wait to see what others do (i.e. option 3). The more input, the better :-) Thanks for the job! -- Best regards, Andrzej Telszewski From thedoogster at gmail.com Thu Nov 9 18:01:33 2017 From: thedoogster at gmail.com (Doogster) Date: Thu, 9 Nov 2017 10:01:33 -0800 Subject: [Slackbuilds-users] The future of the mpv SlackBuild In-Reply-To: References: Message-ID: Have the mpv SlackBuild install ffmpeg-mpv into /usr/lib/mpv or /usr/lib64/mpv. Then have it build mpv with -Wl,-rpath,/usr/lib/mpv or -Wl,-rpath,/usr/lib64/mpv. Have both /usr/lib$LIBDIRSUFFIX/mpv and mpv in the same package. On Thu, Nov 9, 2017 at 9:51 AM, Andrzej Telszewski wrote: > On 09/11/17 17:31, Matteo Bernardini wrote: >> >> 2017-11-09 17:22 GMT+01:00 Andreas Guldstrand >> : >>> >>> Hi all, >>> >>> I'm the current maintainer of the mpv SlackBuild, and don't worry, I'm >>> not about to give it up or anything like that. I am however looking >>> for opinions on how to proceed in the future because of a rather >>> drastic change in mpv's dependencies. >>> >>> What has happened is this: mpv has dropped its dependency on ffmpeg, >>> and instead depend on a specific mpv fork of ffmpeg that they call >>> 'ffmpeg-mpv'. The reasons they've done so are not really relevant for >>> this list, so let's not dwell on those (for the curious, you can take >>> a look through >>> https://github.com/mpv-player/mpv/commit/83d44aca7dc7f46b8d3b64d441f5a8317a40e080 >>> ). >>> >>> The issue I'm facing is how to deal with this change once a new >>> version is released. I'm currently considering three options for how >>> to proceed: >>> >>> 1. Include the building of 'ffmpeg-mpv' inside the mpv SlackBuild and >>> statically link it, since it's likely that only mpv will be relying on >>> the 'ffmpeg-mpv' fork. >>> >>> 2. Make a new 'ffmpeg-mpv' SlackBuild and try to make sure it doesn't >>> conflict with the regular ffmpeg SlackBuild. >>> >>> 3. Wait for other distributions to make patches for mpv available so >>> it can play nice with the regular ffmpeg. I'd of course also take such >>> patches from the SlackBuilds.org community should you be able to >>> provide such things. There is no chance that I would make one on my >>> own however. >>> >>> I'm personally favouring option 1, but would like input from the rest >>> of the community. >>> >>> There are a few things that make me consider option 3 as my least >>> favourite option. For instance the mpv folks are less likely to >>> support a nonstandard build like that, and it makes us dependent on >>> other distributions keeping up with changes to both ffmpeg and mpv. >>> >>> I am still considering it though since it will mean there is only one >>> ffmpeg on SBo, so you only need to build it for the first program that >>> depends on it, it won't cause conflicts, and all the options for >>> ffmpeg are quite a chore to need to make sure they all work as they >>> should. >> >> >> IMHO I would go for the first option (looks the cleanest to me), >> eventually moving to the second only if needed by something else. >> > > If possible, I wouldn't link statically, but install shared ffmpeg-mpv in > lib dir specifically created and known for mpv. But, meh ;-) > > Option (2) makes sense if both mpv and ffmpeg-mpv are kept and updated > separately. So for example ffmpeg-mpv is at version 0.1 and mpv goes from > 0.1 -> 0.2, then you only need to update mpv. Otherwise, use method (1) to > keep house clean. > > You can surely wait to see what others do (i.e. option 3). The more input, > the better :-) > > Thanks for the job! > > -- > Best regards, > Andrzej Telszewski > > _______________________________________________ > 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 pprkut at liwjatan.at Thu Nov 9 20:47:55 2017 From: pprkut at liwjatan.at (Heinz Wiesinger) Date: Thu, 09 Nov 2017 21:47:55 +0100 Subject: [Slackbuilds-users] The future of the mpv SlackBuild In-Reply-To: References: Message-ID: <1829064.rm3txPPX7S@titania> On Thursday, 9 November 2017 17:22:11 CET Andreas Guldstrand wrote: > Hi all, > > I'm the current maintainer of the mpv SlackBuild, and don't worry, I'm > not about to give it up or anything like that. I am however looking > for opinions on how to proceed in the future because of a rather > drastic change in mpv's dependencies. > > What has happened is this: mpv has dropped its dependency on ffmpeg, > and instead depend on a specific mpv fork of ffmpeg that they call > 'ffmpeg-mpv'. The reasons they've done so are not really relevant for > this list, so let's not dwell on those (for the curious, you can take > a look through > https://github.com/mpv-player/mpv/commit/83d44aca7dc7f46b8d3b64d441f5a8317a > 40e080 ). > > The issue I'm facing is how to deal with this change once a new > version is released. IMHO, just wait. At this point emotions are high and pretty much anything can happen going forward. AFAICS there's no release out yet that would require the fork. But even if there was, we don't *need* to have the latest version in the repo. Sure, it's nice, but if upstream throws a tantrum, just give them some time and space to cool down. Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part. URL: From jgraha8 at gmail.com Fri Nov 10 04:28:45 2017 From: jgraha8 at gmail.com (Jason Graham) Date: Thu, 9 Nov 2017 23:28:45 -0500 Subject: [Slackbuilds-users] openssh-krb5: source package updated Message-ID: The source package for openssh-krb5 has been updated to http://slackware.osuosl.org/slackware-14.2/patches/source/openssh/openssh-7.4p1.tar.gz which breaks the current SlackBuild link.Also the SlackBuild uses the --with-tcp-wrappers configure option which now requires the patch: http://slackware.osuosl.org/slackware-14.2/patches/source/openssh/openssh-7.4p1-libwrap.diff.gz to enable this option. Maintainer is CC'd. Regards, Jason -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Fri Nov 10 16:51:49 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 10 Nov 2017 23:51:49 +0700 Subject: [Slackbuilds-users] openssh-krb5: source package updated In-Reply-To: References: Message-ID: <720dfffd-0c25-2dc7-6be9-e5363ed34855@slackbuilds.org> > The source package for openssh-krb5 has been updated to > > > http://slackware.osuosl.org/slackware-14.2/patches/source/openssh/openssh-7.4p1.tar.gz > > which breaks the current SlackBuild link.Also the SlackBuild uses the > --with-tcp-wrappers configure option which now requires the patch: > > > http://slackware.osuosl.org/slackware-14.2/patches/source/openssh/openssh-7.4p1-libwrap.diff.gz > > to enable this option. Maintainer is CC'd. Thanks, it's now fixed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Fri Nov 10 17:06:21 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 10 Nov 2017 09:06:21 -0800 (PST) Subject: [Slackbuilds-users] sbopkg update issues Message-ID: I just created a new local copy of the repository and am running sbopkg. Several packages report different md5sums; proj4 and google-earth are two that I recall. There also seem to be other issues with the downloads as the scripts attempt to update packages. Please suggest what I should check to find the reason for these errors. Rich From slackbuilds at jaxartes.net Fri Nov 10 17:44:35 2017 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Fri, 10 Nov 2017 09:44:35 -0800 Subject: [Slackbuilds-users] sbopkg update issues In-Reply-To: References: Message-ID: On 2017-11-10 09:06 AM, Rich Shepard wrote: > ? I just created a new local copy of the repository and am running sbopkg. > Several packages report different md5sums; proj4 and google-earth are two > that I recall. There also seem to be other issues with the downloads as the > scripts attempt to update packages. Please suggest what I should check to > find the reason for these errors. From gis/google-earth/README: Therefore, this script is subject to failing (and a different MD5SUM) at any time due to the fact that you might get a newer version of GoogleEarth than what the script is designed to use. Please notify the maintainer if this is the case. The md5sums in gis/proj do not appear incorrect to me and sbopkg does not report any inconsistencies when I run the script. Ben From willysr at slackbuilds.org Fri Nov 10 17:45:14 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 11 Nov 2017 00:45:14 +0700 Subject: [Slackbuilds-users] sbopkg update issues In-Reply-To: References: Message-ID: <24de0f61-9303-aaad-dfc8-e84cb5d9417e@slackbuilds.org> > ? I just created a new local copy of the repository and am running sbopkg. > Several packages report different md5sums; proj4 and google-earth are two > that I recall. There also seem to be other issues with the downloads as the > scripts attempt to update packages. Please suggest what I should check to > find the reason for these errors. Both are fine here -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Fri Nov 10 18:05:49 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 10 Nov 2017 10:05:49 -0800 (PST) Subject: [Slackbuilds-users] sbopkg update issues In-Reply-To: <24de0f61-9303-aaad-dfc8-e84cb5d9417e@slackbuilds.org> References: <24de0f61-9303-aaad-dfc8-e84cb5d9417e@slackbuilds.org> Message-ID: On Sat, 11 Nov 2017, Willy Sudiarto Raharjo wrote: > Both are fine here Willy, Can you think of a reason why these differences occur here? Rich From willysr at slackbuilds.org Fri Nov 10 23:35:39 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 11 Nov 2017 06:35:39 +0700 Subject: [Slackbuilds-users] sbopkg update issues In-Reply-To: References: <24de0f61-9303-aaad-dfc8-e84cb5d9417e@slackbuilds.org> Message-ID: <52bdc881-f922-b527-9e7a-e5d170176900@slackbuilds.org> > ? Can you think of a reason why these differences occur here? can you try to remove the sources and re-download again? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Fri Nov 10 23:41:33 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 10 Nov 2017 15:41:33 -0800 (PST) Subject: [Slackbuilds-users] sbopkg update issues In-Reply-To: <52bdc881-f922-b527-9e7a-e5d170176900@slackbuilds.org> References: <24de0f61-9303-aaad-dfc8-e84cb5d9417e@slackbuilds.org> <52bdc881-f922-b527-9e7a-e5d170176900@slackbuilds.org> Message-ID: On Sat, 11 Nov 2017, Willy Sudiarto Raharjo wrote: > can you try to remove the sources and re-download again? Willy, I'll do this ... can't promise when, but likely this weekend. Rich From willysr at slackbuilds.org Sat Nov 11 00:34:41 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 11 Nov 2017 07:34:41 +0700 Subject: [Slackbuilds-users] Updates - 20171111.1 Message-ID: <6563a428-76c0-7c65-2435-7e3d5a47d2ae@slackbuilds.org> In this batch, we have several interesting new submission, including swift, cadabra2, mlr, nyx, ecryptfs-utils, and vmfs-tools. We also bumped LibreOffice and libreoffice to the just-released 5.4.3 which fixed more than 50 regressions. After testing for one week, we still didn't have a solution for vscode, so we might have 2 different nodejs script in the repository soon. The original nodejs will be based on 6.9.0 LTS and the new script nodejs8 will be based on 8.9.x LTS. I also have a request to bump Electrum to 3.0.x, but this new version requires a change in the dependency, which are Python3 and Qt5. I want to ask for people's opinion on this since Qt5 is quite time consuming to build for some people. Sat Nov 11 00:08:36 UTC 2017 academic/cadabra2: Added (field-theory motivated computer algebra). desktop/alarm: Updated for version 2.2. desktop/arc-openbox: Added (Arc theme for Openbox window manager). desktop/awesome-extra: Updated for version 2017110501. desktop/fbautostart: Added (XDG Autostarter for Fluxbox). desktop/qt5ct: Updated for version 0.34. desktop/spectrwm: Updated for version 3.1.0. desktop/tint2: Updated for version 15.3. development/cargo-vendor: Updated for version 0.1.13. development/gcclegacy494: Update SlackBuild. development/le: Updated for version 1.16.5. development/mlr: Added (structured text processor). development/mutagen: Updated for version 1.39. development/neovim: Updated for version 0.2.1. development/pandas: Updated for version 0.21.0. development/pycharm: Updated for version 2017.2.4. development/rtags: Updated for version 2.15. development/sbcl: Updated for version 1.4.1. development/swift: Added (the Swift programming language). development/uncrustify: Updated for version 0.66. games/crispy-doom: Updated for version 5.0. games/planetblupi: Updated for version 1.12.0. gis/saga-gis: Note issue with building when vigra installed. libraries/Botan: Updated for version 2.3.0. libraries/dropbox-python: Updated for version 8.4.1. libraries/libfilezilla: Updated for version 0.11.1 libraries/libsass: Updated for version 3.4.6. libraries/libuv: Updated for version 1.16.0. libraries/libvirt-python: Updated for version 3.9.0. libraries/libvirt: Updated for version 3.9.0. libraries/libxnvctrl: Updated for version 384.90. libraries/pyftpdlib: Updated for version 1.5.3. libraries/wxGTK3: Fix assert in FileZilla. libraries/wxSQLite3: Updated for version 3.5.8. misc/no-more-secrets: Updated for version 0.3.3. misc/sunwait: Added (calculates sunrise or sunset times) multimedia/opera-ffmpeg-codecs: Updated for version 62.0.3202.62. network/PaleMoon: Updated for version 27.6.0. network/aria2: Updated for version 1.33.1. network/fail2ban: Updated for version 0.10.1. network/filezilla: Updated for version 3.29.0. network/nextcloud-client: Fixed deps, update README. network/offlineimap: Updated for version 7.1.4. network/openssh-krb5: Updated for version 7.4p1. network/opera: Updated for version 49.0.2725.34. network/palemoon: Updated for version 27.6.0. network/phpmyadmin: Updated for version 4.7.5. network/slimjet: Updated for version 16.0.3.0. network/tor-browser: Updated for version 7.0.9. network/yle-dl: Updated for version 2.27. network/youtube-dl: Updated for version 2017.11.06. office/LibreOffice: Updated for version 5.4.3.2 office/jstock: Updated for version 1.0.7.29. office/libreoffice-helppack: Updated for version 5.4.3. office/libreoffice-langpack: Updated for version 5.4.3. office/libreoffice: Updated for version 5.4.3. perl/perl-Algorithm-Combinatorics: Added (combinatorial sequences). perl/perl-Algorithm-Loops: Added (Looping constructs). perl/perl-Glib-Object-Introspection: Updated for version 0.044. perl/perl-MailTools: Updated for version 2.19. perl/perl-Math-Prime-Util-GMP: Updated for version 0.47. perl/perl-Role-Tiny: Updated for version 2.000006. perl/perl-Sidef: Updated for version 3.05. perl/perl-String-Scanf: Added (emulate sscanf() of the C library). perl/perl-gnome2: Updated for version 1.047. python/coverage: Updated for version 4.4.2. python/nyx: Added (Terminal status monitor for Tor). python/parso: Updated for version 0.1.1. python/path.py: Updated for version 10.5. python/pbr: Updated for version 3.1.1. python/pyamf: Added (Action Message Format support for Python). python/python-certifi: Updated for version 2017.11.5. python/python-fonttools: Updated for version 3.19.0. python/python-neovim: Updated for version 0.2.0. python/python3-parso: Updated for version 0.1.1. python/pytzdata: Updated for version 2017.3.1. python/stem: Updated for version 1.6.0. python/stevedore: Updated for version 1.27.1. system/ZoneMinder: Update README. system/blktrace: Updated for version 1.2.0. system/dar: Updated for version 2.5.13. system/docker-compose: Updated for version 1.17.1. system/docker-machine-kvm: Updated libvirt-go for version 3.9.0. system/dosbox-dev: Updated for version 0.74.r4063. system/ecryptfs-utils: Added (cryptographic filesystem). system/hh: Updated for version 1.23. system/mksh: Updated for version R56b. system/monit: Updated for version 5.25.0. system/pommed-light: Updated for version 1.51lw. system/vagrant: Updated for version 2.0.1. system/vmfs-tools: Added (tools to access vmware VMFS). system/wine-staging: Updated for version 2.20. system/xrdp: Updated for version 0.9.4. system/yash: Updated for version 2.46. system/zstd: Updated for version 1.3.2. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From duncan_roe at optusnet.com.au Sat Nov 11 00:59:59 2017 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Sat, 11 Nov 2017 11:59:59 +1100 Subject: [Slackbuilds-users] [PATCH] SLURM no longer building Message-ID: <20171111005959.GA30766@dimstar.local.net> Hi, The URL for slurm-17.02.7.tar.bz2 gets a 404. It is possible to get this version via the home page, but the current version slurm-17.02.9 fetches just fine. Also, the README was still referring to slurm-14.x for configuration file build. The following patch fixes everything, Cheers ... Duncan. diff --git a/network/slurm/README b/network/slurm/README index faf584c..3ae7439 100644 --- a/network/slurm/README +++ b/network/slurm/README @@ -16,7 +16,7 @@ is executed. # useradd -u 311 -d /var/lib/slurm -s /bin/false -g slurm slurm Next, a configuration file can be build using your favorite web browser -and the file /usr/doc/slurm-14.11.8/html/configurator.html. +and the file /usr/doc/slurm-17.02.9/html/configurator.html. Optional dependencies: HWLOC=yes|no (default: no), requires hwloc diff --git a/network/slurm/slurm.SlackBuild b/network/slurm/slurm.SlackBuild index 4f0adab..41e935d 100644 --- a/network/slurm/slurm.SlackBuild +++ b/network/slurm/slurm.SlackBuild @@ -23,7 +23,7 @@ # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PRGNAM=slurm -VERSION=${VERSION:-17.02.7} +VERSION=${VERSION:-17.02.9} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} diff --git a/network/slurm/slurm.info b/network/slurm/slurm.info index 61fdd20..3b5d50f 100644 --- a/network/slurm/slurm.info +++ b/network/slurm/slurm.info @@ -1,8 +1,8 @@ PRGNAM="slurm" -VERSION="17.02.7" +VERSION="17.02.9" HOMEPAGE="http://slurm.schedmd.com/" -DOWNLOAD="http://www.schedmd.com/download/latest/slurm-17.02.7.tar.bz2" -MD5SUM="64009c1ed120b9ce5d79424dca743a06" +DOWNLOAD="http://www.schedmd.com/download/latest/slurm-17.02.9.tar.bz2" +MD5SUM="6bd0b38e6bf08f3426a7dd1e663a2e3c" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="munge" From rshepard at appl-ecosys.com Sat Nov 11 18:16:49 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 11 Nov 2017 10:16:49 -0800 (PST) Subject: [Slackbuilds-users] Postgis not finding installed gdal Message-ID: Attempting to upgrade postgis to 2.4.1 fails during configuration: checking for gdal-config... /usr/bin/gdal-config checking GDAL version... 2.2.2 checking for OGR enabled... yes checking gdal.h usability... yes checking gdal.h presence... yes checking for gdal.h... yes ... checking for library containing GDALAllRegister... no configure: error: could not find GDAL The script seems to find gdal-2.2.2 (the current SBo version) and the header file. I don't understand how to fix this error and would appreciate a pointer. TIA, Rich From slackbuilds at jaxartes.net Sat Nov 11 21:37:06 2017 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sat, 11 Nov 2017 13:37:06 -0800 Subject: [Slackbuilds-users] Postgis not finding installed gdal In-Reply-To: References: Message-ID: <9014218.m76eP3ypzB@wintermute> On Saturday, November 11, 2017 10:16:49 AM PST Rich Shepard wrote: > Attempting to upgrade postgis to 2.4.1 fails during configuration: > > checking for gdal-config... /usr/bin/gdal-config > checking GDAL version... 2.2.2 > checking for OGR enabled... yes > checking gdal.h usability... yes > checking gdal.h presence... yes > checking for gdal.h... yes > ... > checking for library containing GDALAllRegister... no > configure: error: could not find GDAL > > The script seems to find gdal-2.2.2 (the current SBo version) and the > header file. I don't understand how to fix this error and would appreciate a > pointer. A fresh install of GDAL and then PostGIS on my 64-bit 14.2 does not produce this error and the build completes successfully. Ben From rshepard at appl-ecosys.com Sat Nov 11 22:44:33 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 11 Nov 2017 14:44:33 -0800 (PST) Subject: [Slackbuilds-users] Postgis not finding installed gdal In-Reply-To: <9014218.m76eP3ypzB@wintermute> References: <9014218.m76eP3ypzB@wintermute> Message-ID: On Sat, 11 Nov 2017, Benjamin Trigona-Harany wrote: > A fresh install of GDAL and then PostGIS on my 64-bit 14.2 does not > produce this error and the build completes successfully. Ben, I thought of doing this, but had other builds going at the time. I'll do this. Thanks, Rich From rshepard at appl-ecosys.com Sun Nov 12 00:41:00 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 11 Nov 2017 16:41:00 -0800 (PST) Subject: [Slackbuilds-users] Postgis not finding installed gdal In-Reply-To: References: <9014218.m76eP3ypzB@wintermute> Message-ID: On Sat, 11 Nov 2017, Rich Shepard wrote: > I thought of doing this, but had other builds going at the time. I'll do > this. Ben, That worked here, too. I should have thought of rebuilding gdal when the postgis build reported it both did and did not find it. I'll try to remember this for the next time I get a build failure for a similar reason. Best regards, Rich From fernando.lopezjr at gmail.com Sun Nov 12 02:32:34 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sat, 11 Nov 2017 19:32:34 -0700 Subject: [Slackbuilds-users] python wont install errors. Message-ID: I cant get it to work with the slackbuild, but if i do it manually it works... any ideas? -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: responder.tar.xz Type: application/x-xz Size: 814568 bytes Desc: not available URL: From andreas.guldstrand at gmail.com Sun Nov 12 11:57:36 2017 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Sun, 12 Nov 2017 12:57:36 +0100 Subject: [Slackbuilds-users] python wont install errors. In-Reply-To: References: Message-ID: On 12 November 2017 at 03:32, Fernando Lopez wrote: > I cant get it to work with the slackbuild, but if i do it manually it > works... any ideas? I'm not sure what you're actually doing, but python isn't provided by SlackBuilds.org, it's part of Slackware itself. // Andreas From fernando.lopezjr at gmail.com Sun Nov 12 21:36:17 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sun, 12 Nov 2017 14:36:17 -0700 Subject: [Slackbuilds-users] python wont install errors. In-Reply-To: References: Message-ID: Sorry it was late night and I was tired. What I mean is that python wont compile my slackbuild but if i do it manually it works fine. I think the problem is the setup.py I think I need to add more stuff to it. I know here there are python experts who can help me fix that setup.py. Sorry for the crippled email. On Sun, Nov 12, 2017 at 4:57 AM, Andreas Guldstrand < andreas.guldstrand at gmail.com> wrote: > On 12 November 2017 at 03:32, Fernando Lopez > wrote: > > I cant get it to work with the slackbuild, but if i do it manually it > > works... any ideas? > > I'm not sure what you're actually doing, but python isn't provided by > SlackBuilds.org, it's part of Slackware itself. > > // Andreas > _______________________________________________ > 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 d.zlatanidis at gmail.com Mon Nov 13 01:39:30 2017 From: d.zlatanidis at gmail.com (Dimitris Zlatanidis) Date: Mon, 13 Nov 2017 02:39:30 +0100 Subject: [Slackbuilds-users] python wont install errors. In-Reply-To: References: Message-ID: Have you see my changes? It's works for me. On Nov 12, 2017 22:36, "Fernando Lopez" wrote: > Sorry it was late night and I was tired. > > What I mean is that python wont compile my slackbuild but if i do it > manually it works fine. I think the problem is the setup.py I think I need > to add more stuff to it. I know here there are python experts who can help > me fix that setup.py. Sorry for the crippled email. > > > > On Sun, Nov 12, 2017 at 4:57 AM, Andreas Guldstrand < > andreas.guldstrand at gmail.com> wrote: > >> On 12 November 2017 at 03:32, Fernando Lopez >> wrote: >> > I cant get it to work with the slackbuild, but if i do it manually it >> > works... any ideas? >> >> I'm not sure what you're actually doing, but python isn't provided by >> SlackBuilds.org, it's part of Slackware itself. >> >> // Andreas >> _______________________________________________ >> 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. > > _______________________________________________ > 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 fernando.lopezjr at gmail.com Mon Nov 13 01:59:07 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sun, 12 Nov 2017 18:59:07 -0700 Subject: [Slackbuilds-users] python wont install errors. In-Reply-To: References: Message-ID: dimitris it works! thanks =) On Sun, Nov 12, 2017 at 6:39 PM, Dimitris Zlatanidis wrote: > Have you see my changes? It's works for me. > > On Nov 12, 2017 22:36, "Fernando Lopez" > wrote: > >> Sorry it was late night and I was tired. >> >> What I mean is that python wont compile my slackbuild but if i do it >> manually it works fine. I think the problem is the setup.py I think I need >> to add more stuff to it. I know here there are python experts who can help >> me fix that setup.py. Sorry for the crippled email. >> >> >> >> On Sun, Nov 12, 2017 at 4:57 AM, Andreas Guldstrand < >> andreas.guldstrand at gmail.com> wrote: >> >>> On 12 November 2017 at 03:32, Fernando Lopez >>> wrote: >>> > I cant get it to work with the slackbuild, but if i do it manually it >>> > works... any ideas? >>> >>> I'm not sure what you're actually doing, but python isn't provided by >>> SlackBuilds.org, it's part of Slackware itself. >>> >>> // Andreas >>> _______________________________________________ >>> 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. >> >> _______________________________________________ >> 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/ > > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgraha8 at gmail.com Mon Nov 13 05:23:21 2017 From: jgraha8 at gmail.com (Jason Graham) Date: Mon, 13 Nov 2017 00:23:21 -0500 Subject: [Slackbuilds-users] perl-Convert-ASN1: upstream updated/broken link Message-ID: Hi, perl-Convert-ASN1 has been updated 0.26 -> 0.27 which has broken the origin SlackBuilds link. Attached is a patch for the updated version. Maintainer is CC'd. Best, Jason -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-updated-perl-Convert-ASN1-to-0.27.patch Type: text/x-patch Size: 1518 bytes Desc: not available URL: From willysr at slackbuilds.org Tue Nov 14 09:42:30 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 14 Nov 2017 16:42:30 +0700 Subject: [Slackbuilds-users] perl-Convert-ASN1: upstream updated/broken link In-Reply-To: References: Message-ID: > perl-Convert-ASN1 has been updated 0.26 -> 0.27 which has broken the origin > SlackBuilds link. Attached is a patch for the updated version. Thanks updated in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Tue Nov 14 19:06:02 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 14 Nov 2017 11:06:02 -0800 (PST) Subject: [Slackbuilds-users] zim md5sum mis-match Message-ID: Downloaded zim-0.67.tar.gz; SBo shows md5sum (e87975727f1166c723912c949bea51f2) The downloaded file shows md5sum (6c3cddd2c48a894a32ce4c7796dd8ddc). When zim.SlackBuild is invoked there's an error: # time ./zim.SlackBuild tar: This does not look like a tar archive tar: Skipping to next header tar: Exiting with failure status due to previous errors real 0m0.049s user 0m0.036s sys 0m0.004s Please advise. Rich From brent at exitstatusone.com Tue Nov 14 19:34:44 2017 From: brent at exitstatusone.com (Brenton Earl) Date: Tue, 14 Nov 2017 12:34:44 -0700 Subject: [Slackbuilds-users] zim md5sum mis-match In-Reply-To: References: Message-ID: <1510688084.3494.1.camel@exitstatusone.com> On Tue, 2017-11-14 at 11:06 -0800, Rich Shepard wrote: > ???Downloaded zim-0.67.tar.gz; SBo shows md5sum > (e87975727f1166c723912c949bea51f2) > > ???The downloaded file shows md5sum > (6c3cddd2c48a894a32ce4c7796dd8ddc). > > ???When zim.SlackBuild is invoked there's an error: > > # time ./zim.SlackBuild? > tar: This does not look like a tar archive > tar: Skipping to next header > tar: Exiting with failure status due to previous errors I just built zim with sbopkg in both x86 and x86_64 fresh Slackware 14.2 virtual machines without issue. Zim runs as expected in X as well. Please double check that you have the right files. -- Brenton Earl From dpross1100 at msn.com Tue Nov 14 20:08:46 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Tue, 14 Nov 2017 20:08:46 +0000 Subject: [Slackbuilds-users] zim md5sum mis-match In-Reply-To: Message-ID: I also checked. Downloading the source with wget works and gives the right md5sum, but clicking the link on the SBo website to download the file results in the error Rich reported. Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Tue Nov 14 20:12:53 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 14 Nov 2017 12:12:53 -0800 (PST) Subject: [Slackbuilds-users] zim md5sum mis-match In-Reply-To: References: Message-ID: On Tue, 14 Nov 2017, Daniel Prosser wrote: > I also checked. Downloading the source with wget works and gives the right > md5sum, but clicking the link on the SBo website to download the file > results in the error Rich reported. Dan, Thanks for confirming. I've not before seen this happen so it did not occur to me to use wget. I'll do that now. Many thanks, Rich From matteo.bernardini at gmail.com Tue Nov 14 20:13:36 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 14 Nov 2017 21:13:36 +0100 Subject: [Slackbuilds-users] zim md5sum mis-match In-Reply-To: <1510688084.3494.1.camel@exitstatusone.com> References: <1510688084.3494.1.camel@exitstatusone.com> Message-ID: 2017-11-14 20:34 GMT+01:00 Brenton Earl : > On Tue, 2017-11-14 at 11:06 -0800, Rich Shepard wrote: >> Downloaded zim-0.67.tar.gz; SBo shows md5sum >> (e87975727f1166c723912c949bea51f2) >> >> The downloaded file shows md5sum >> (6c3cddd2c48a894a32ce4c7796dd8ddc). >> >> When zim.SlackBuild is invoked there's an error: >> >> # time ./zim.SlackBuild >> tar: This does not look like a tar archive >> tar: Skipping to next header >> tar: Exiting with failure status due to previous errors > > I just built zim with sbopkg in both x86 and x86_64 fresh Slackware > 14.2 virtual machines without issue. Zim runs as expected in X as > well. > > Please double check that you have the right files. Hi Brenton, it looks like the tar.gz has a different dimension and different md5 at every download with wget here $ ls -1 zim-0.67.tar.gz* zim-0.67.tar.gz zim-0.67.tar.gz.1 zim-0.67.tar.gz.2 zim-0.67.tar.gz.3 $ md5sum zim* dffaac1401f62db18862633bcec443d8 zim-0.67.tar.gz 0709950d79ffcb24b5f621672405ed9e zim-0.67.tar.gz.1 513786446c319989791cafde60a2d2ac zim-0.67.tar.gz.2 3259556cbf87ce054d31a41de2194d62 zim-0.67.tar.gz.3 Matteo From rshepard at appl-ecosys.com Tue Nov 14 20:42:51 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 14 Nov 2017 12:42:51 -0800 (PST) Subject: [Slackbuilds-users] zim md5sum mis-match In-Reply-To: References: <1510688084.3494.1.camel@exitstatusone.com> Message-ID: On Tue, 14 Nov 2017, Matteo Bernardini wrote: > it looks like the tar.gz has a different dimension and different md5 at > every download with wget here Matteo, I found this, too. They also have different file sizes. My solution was to take the SlackBuild error message as correct. I ungzipped the file, untarred it, and rebuilt the .tar.gz from the source directory. It's now building with zim.SlackBuild. The file size that worked here is 2049660, all other downloads were smaller. Regards, Rich From brent at exitstatusone.com Tue Nov 14 22:00:08 2017 From: brent at exitstatusone.com (Brenton Earl) Date: Tue, 14 Nov 2017 15:00:08 -0700 Subject: [Slackbuilds-users] zim md5sum mis-match In-Reply-To: References: <1510688084.3494.1.camel@exitstatusone.com> Message-ID: <1510696808.4215.1.camel@exitstatusone.com> On Tue, 2017-11-14 at 21:13 +0100, Matteo Bernardini wrote: > 2017-11-14 20:34 GMT+01:00 Brenton Earl : > > On Tue, 2017-11-14 at 11:06 -0800, Rich Shepard wrote: > > > ???Downloaded zim-0.67.tar.gz; SBo shows md5sum > > > (e87975727f1166c723912c949bea51f2) > > > > > > ???The downloaded file shows md5sum > > > (6c3cddd2c48a894a32ce4c7796dd8ddc). > > > > > I just built zim with sbopkg in both x86 and x86_64 fresh Slackware > > 14.2 virtual machines without issue.??Zim runs as expected in X as > > well. > > > > Please double check that you have the right files. > > Hi Brenton, > > it looks like the tar.gz has a different dimension and different md5 > at every download with wget here > > $ ls -1 zim-0.67.tar.gz* > zim-0.67.tar.gz > zim-0.67.tar.gz.1 > zim-0.67.tar.gz.2 > zim-0.67.tar.gz.3 > $ md5sum zim* > dffaac1401f62db18862633bcec443d8??zim-0.67.tar.gz > 0709950d79ffcb24b5f621672405ed9e??zim-0.67.tar.gz.1 > 513786446c319989791cafde60a2d2ac??zim-0.67.tar.gz.2 > 3259556cbf87ce054d31a41de2194d62??zim-0.67.tar.gz.3 As a test I downloaded zim with wget on my CentOS 7.4 machine. The zim md5sum on my CentOS 7 installation matches for every copy downloaded. On my Slackware installations a download of zim with wget does not match, but downloads with the links (web browser) do match. Sbopkg does not report a md5sum mismatch. I am not really sure what I can do to fix this. Does anyone have any suggestions? -- Brenton Earl From ricardo at palmtx.com.ar Tue Nov 14 22:28:20 2017 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Tue, 14 Nov 2017 19:28:20 -0300 Subject: [Slackbuilds-users] zim md5sum mis-match In-Reply-To: <1510696808.4215.1.camel@exitstatusone.com> References: <1510696808.4215.1.camel@exitstatusone.com> Message-ID: <201711141928.20393.ricardo@palmtx.com.ar> El Martes 14/11/2017 a las 19:00, Brenton Earl escribi?: > On Tue, 2017-11-14 at 21:13 +0100, Matteo Bernardini wrote: > > 2017-11-14 20:34 GMT+01:00 Brenton Earl : > > > On Tue, 2017-11-14 at 11:06 -0800, Rich Shepard wrote: > > > > ???Downloaded zim-0.67.tar.gz; SBo shows md5sum > > > > (e87975727f1166c723912c949bea51f2) > > > > > > > > ???The downloaded file shows md5sum > > > > (6c3cddd2c48a894a32ce4c7796dd8ddc). > > > > > > I just built zim with sbopkg in both x86 and x86_64 fresh Slackware > > > 14.2 virtual machines without issue.??Zim runs as expected in X as > > > well. > > > > > > Please double check that you have the right files. > > > > Hi Brenton, > > > > it looks like the tar.gz has a different dimension and different md5 > > at every download with wget here > > > > $ ls -1 zim-0.67.tar.gz* > > zim-0.67.tar.gz > > zim-0.67.tar.gz.1 > > zim-0.67.tar.gz.2 > > zim-0.67.tar.gz.3 > > $ md5sum zim* > > dffaac1401f62db18862633bcec443d8??zim-0.67.tar.gz > > 0709950d79ffcb24b5f621672405ed9e??zim-0.67.tar.gz.1 > > 513786446c319989791cafde60a2d2ac??zim-0.67.tar.gz.2 > > 3259556cbf87ce054d31a41de2194d62??zim-0.67.tar.gz.3 > > As a test I downloaded zim with wget on my CentOS 7.4 machine. The zim > md5sum on my CentOS 7 installation matches for every copy downloaded. > On my Slackware installations a download of zim with wget does not > match, but downloads with the links (web browser) do match. Sbopkg > does not report a md5sum mismatch. > > I am not really sure what I can do to fix this. Does anyone have any > suggestions? Some issue with wget's compression detection? $ LANG=C wget http://zim-wiki.org/downloads/zim-0.67.tar.gz -O zim-0.67.tar.gz ; md5sum zim-0.67.tar.gz ; rm -f zim-0.67.tar.gz --2017-11-14 19:24:13-- http://zim-wiki.org/downloads/zim-0.67.tar.gz Resolving zim-wiki.org... 95.170.72.161, 2a01:7c8:eb:0:95:170:72:161 Connecting to zim-wiki.org|95.170.72.161|:80... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [application/gzip] Saving to: 'zim-0.67.tar.gz' zim-0.67.tar.gz [ <=> ] 1.94M 1.15MB/s in 1.7s 2017-11-14 19:24:15 (1.15 MB/s) - 'zim-0.67.tar.gz' saved [2035901] 3259556cbf87ce054d31a41de2194d62 zim-0.67.tar.gz With '--compression=none' the md5sum matches what's on SBo: $ LANG=C wget --compression=none http://zim-wiki.org/downloads/zim-0.67.tar.gz -O zim-0.67.tar.gz ; md5sum zim-0.67.tar.gz ; rm -f zim-0.67.tar.gz --2017-11-14 19:24:22-- http://zim-wiki.org/downloads/zim-0.67.tar.gz Resolving zim-wiki.org... 95.170.72.161, 2a01:7c8:eb:0:95:170:72:161 Connecting to zim-wiki.org|95.170.72.161|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2034747 (1.9M) [application/gzip] Saving to: 'zim-0.67.tar.gz' zim-0.67.tar.gz 100%[=====================================================================================>] 1.94M 1.15MB/s in 1.7s 2017-11-14 19:24:24 (1.15 MB/s) - 'zim-0.67.tar.gz' saved [2034747/2034747] e87975727f1166c723912c949bea51f2 zim-0.67.tar.gz Cheers, -- Ricardo J. Barberis Usuario Linux N? 250625: http://counter.li.org/ Usuario LFS N? 5121: http://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - www.DonWeb.com From matteo.bernardini at gmail.com Tue Nov 14 23:02:49 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 15 Nov 2017 00:02:49 +0100 Subject: [Slackbuilds-users] zim md5sum mis-match In-Reply-To: <201711141928.20393.ricardo@palmtx.com.ar> References: <1510696808.4215.1.camel@exitstatusone.com> <201711141928.20393.ricardo@palmtx.com.ar> Message-ID: I think the problem is in the zimi-wiki.org webserver, that compresses on the fly already gzip compressed tar archives, behaving differently depending on browser/wget downloads. IMHO the best way to handle this is to produce/download a working tar.gz tarball, self-host it somewhere and use that as DOWNLOAD. Matteo From slackbuilds at schoepfer.info Wed Nov 15 08:18:32 2017 From: slackbuilds at schoepfer.info (Franzen) Date: Wed, 15 Nov 2017 09:18:32 +0100 Subject: [Slackbuilds-users] Texlive 2017.171108 texmf_get.sh Message-ID: <0e6f21662704c26ac7691d1ab0ee1d66@schoepfer.info> Hi, i wrongly submitted a dev version of texmf_get.sh in https://git.slackbuilds.org/slackbuilds/diff/office/texlive?h=idlemoor&id=13719b058a5d79d160975753d93b34b1d579d008 Attached is the version what will occour in -current. Should i submit again, or may some admin put this script into git? Thanks, Johannes -------------- next part -------------- A non-text attachment was scrubbed... Name: texmf_get.sh Type: text/x-shellscript Size: 23533 bytes Desc: not available URL: From rshepard at appl-ecosys.com Tue Nov 14 23:07:39 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 14 Nov 2017 15:07:39 -0800 (PST) Subject: [Slackbuilds-users] zim md5sum mis-match In-Reply-To: References: <1510696808.4215.1.camel@exitstatusone.com> <201711141928.20393.ricardo@palmtx.com.ar> Message-ID: On Wed, 15 Nov 2017, Matteo Bernardini wrote: > I think the problem is in the zimi-wiki.org webserver, that compresses on > the fly already gzip compressed tar archives, behaving differently > depending on browser/wget downloads. IMHO the best way to handle this is > to produce/download a working tar.gz tarball, self-host it somewhere and > use that as DOWNLOAD. Matteo, The one I downloaded and repackaged (.tar.gz) worked for me. A copy's attached if that helps any. I really appreciate everyone here looking at this issue and working on a solution. Best regards, Rich -------------- next part -------------- A non-text attachment was scrubbed... Name: zim-0.67.tar.gz Type: application/x-gzip Size: 2049660 bytes Desc: URL: From baildon.research at googlemail.com Wed Nov 15 16:54:51 2017 From: baildon.research at googlemail.com (David Spencer) Date: Wed, 15 Nov 2017 16:54:51 +0000 Subject: [Slackbuilds-users] Texlive 2017.171108 texmf_get.sh In-Reply-To: <0e6f21662704c26ac7691d1ab0ee1d66@schoepfer.info> References: <0e6f21662704c26ac7691d1ab0ee1d66@schoepfer.info> Message-ID: > Should i submit again, or may some admin put this script into git? Hi! I did it this morning, you've probably already seen it, sorry for the delay replying and thanks for the update :D Cheers -D. From klaatu at member.fsf.org Wed Nov 15 12:03:02 2017 From: klaatu at member.fsf.org (Klaatu) Date: Thu, 16 Nov 2017 01:03:02 +1300 Subject: [Slackbuilds-users] patchage missing dependency listing Message-ID: <6bf59d4e-7412-187a-5a34-2f8e9fa2cb96@member.fsf.org> I'm sending this to the list because I think Ryan surrendered this build script and I'm not sure who owns it now. Eh, maybe I'm misremembering. Patchage requires libgvc, which is provided by graphviz. So graphviz should be listed as a dep for patchage. Incidentally, if nobody has claimed Patchage and Ryan did indeed give it up, I'll take it. -klaatu -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Thu Nov 16 02:22:48 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 16 Nov 2017 09:22:48 +0700 Subject: [Slackbuilds-users] patchage missing dependency listing In-Reply-To: <6bf59d4e-7412-187a-5a34-2f8e9fa2cb96@member.fsf.org> References: <6bf59d4e-7412-187a-5a34-2f8e9fa2cb96@member.fsf.org> Message-ID: <0d823d32-8da2-981d-a5c0-41f6c80d7aa6@slackbuilds.org> > I'm sending this to the list because I think Ryan surrendered this build > script and I'm not sure who owns it now. Eh, maybe I'm misremembering. > > Patchage requires libgvc, which is provided by graphviz. > > So graphviz should be listed as a dep for patchage. > > Incidentally, if nobody has claimed Patchage and Ryan did indeed give it > up, I'll take it. I just build patchage without graphviz and it works fine here ganv: MD5SUM check for ganv-1.4.2.tar.bz2 ... OK Building package ganv-1.4.2-x86_64-1_SBo.tgz ... OK Installing package ganv-1.4.2-x86_64-1_SBo.tgz ... OK patchage: MD5SUM check for patchage-1.0.0.tar.bz2 ... OK Building package patchage-1.0.0-x86_64-1_SBo.tgz ... OK Installing package patchage-1.0.0-x86_64-1_SBo.tgz ... OK -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From klaatu at member.fsf.org Thu Nov 16 06:12:03 2017 From: klaatu at member.fsf.org (Klaatu) Date: Thu, 16 Nov 2017 19:12:03 +1300 Subject: [Slackbuilds-users] patchage missing dependency listing In-Reply-To: <0d823d32-8da2-981d-a5c0-41f6c80d7aa6@slackbuilds.org> References: <6bf59d4e-7412-187a-5a34-2f8e9fa2cb96@member.fsf.org> <0d823d32-8da2-981d-a5c0-41f6c80d7aa6@slackbuilds.org> Message-ID: Did you launch it? It won't launch for me, citing a missing libgvc On 16 November 2017 3:22:48 PM NZDT, Willy Sudiarto Raharjo wrote: >> I'm sending this to the list because I think Ryan surrendered this >build >> script and I'm not sure who owns it now. Eh, maybe I'm >misremembering. >> >> Patchage requires libgvc, which is provided by graphviz. >> >> So graphviz should be listed as a dep for patchage. >> >> Incidentally, if nobody has claimed Patchage and Ryan did indeed give >it >> up, I'll take it. > >I just build patchage without graphviz and it works fine here > >ganv: > MD5SUM check for ganv-1.4.2.tar.bz2 ... OK > Building package ganv-1.4.2-x86_64-1_SBo.tgz ... OK > Installing package ganv-1.4.2-x86_64-1_SBo.tgz ... OK > >patchage: > MD5SUM check for patchage-1.0.0.tar.bz2 ... OK > Building package patchage-1.0.0-x86_64-1_SBo.tgz ... OK > Installing package patchage-1.0.0-x86_64-1_SBo.tgz ... OK > > > >-- >Willy Sudiarto Raharjo -- Klaatu -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackbuilds at schoepfer.info Thu Nov 16 09:04:06 2017 From: slackbuilds at schoepfer.info (Franzen) Date: Thu, 16 Nov 2017 10:04:06 +0100 Subject: [Slackbuilds-users] Texlive 2017.171108 texmf_get.sh In-Reply-To: References: <0e6f21662704c26ac7691d1ab0ee1d66@schoepfer.info> Message-ID: Hi, >> Should i submit again, or may some admin put this script into git? > > Hi! I did it this morning, you've probably already seen it, sorry for > the delay replying and thanks for the update :D Thanks, and apologizies for the extra work, especially as texlive-extra also needs a fix. It seems i used an old out-of-sync git checkout as base for the commit, sorry. Corrected buildscript attached. Johannes -------------- next part -------------- A non-text attachment was scrubbed... Name: texlive-extra.SlackBuild Type: text/x-shellscript Size: 2350 bytes Desc: not available URL: From willysr at slackbuilds.org Thu Nov 16 15:27:59 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 16 Nov 2017 22:27:59 +0700 Subject: [Slackbuilds-users] patchage missing dependency listing In-Reply-To: References: <6bf59d4e-7412-187a-5a34-2f8e9fa2cb96@member.fsf.org> <0d823d32-8da2-981d-a5c0-41f6c80d7aa6@slackbuilds.org> Message-ID: <430be243-0005-6cc7-ba95-f353879e60f1@slackbuilds.org> > Did you launch it? It won't launch for me, citing a missing libgvc Yes, i did try to launch it just now and it works fine without libgvc -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Thu Nov 16 15:46:15 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 16 Nov 2017 22:46:15 +0700 Subject: [Slackbuilds-users] [PATCH] SLURM no longer building In-Reply-To: <20171111005959.GA30766@dimstar.local.net> References: <20171111005959.GA30766@dimstar.local.net> Message-ID: <843fb184-9e24-a21b-3289-04f5464a8789@slackbuilds.org> > The URL for slurm-17.02.7.tar.bz2 gets a 404. It is possible to get this version > via the home page, but the current version slurm-17.02.9 fetches just fine. > > Also, the README was still referring to slurm-14.x for configuration file build. > > The following patch fixes everything, Thanks i updated slurm in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From emmanueln at gmail.com Thu Nov 16 15:48:25 2017 From: emmanueln at gmail.com (Emmanuel) Date: Thu, 16 Nov 2017 12:48:25 -0300 Subject: [Slackbuilds-users] [PATCH] SLURM no longer building In-Reply-To: <843fb184-9e24-a21b-3289-04f5464a8789@slackbuilds.org> References: <20171111005959.GA30766@dimstar.local.net> <843fb184-9e24-a21b-3289-04f5464a8789@slackbuilds.org> Message-ID: Thanks Willy for applying the patch and Duncan for finding and fixing the error. Best regards. On Thu, Nov 16, 2017 at 12:46 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > The URL for slurm-17.02.7.tar.bz2 gets a 404. It is possible to get this > version > > via the home page, but the current version slurm-17.02.9 fetches just > fine. > > > > Also, the README was still referring to slurm-14.x for configuration > file build. > > > > The following patch fixes everything, > > Thanks > i updated slurm in my branch > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > 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/ > > > -- ***************** Emmanuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From klaatu at member.fsf.org Thu Nov 16 08:06:18 2017 From: klaatu at member.fsf.org (Klaatu) Date: Thu, 16 Nov 2017 21:06:18 +1300 Subject: [Slackbuilds-users] patchage missing dependency listing In-Reply-To: <430be243-0005-6cc7-ba95-f353879e60f1@slackbuilds.org> References: <6bf59d4e-7412-187a-5a34-2f8e9fa2cb96@member.fsf.org> <0d823d32-8da2-981d-a5c0-41f6c80d7aa6@slackbuilds.org> <430be243-0005-6cc7-ba95-f353879e60f1@slackbuilds.org> Message-ID: <5ef1d3d5-b18a-ecbb-f210-c5e62eb029da@member.fsf.org> On 11/17/2017 04:27 AM, Willy Sudiarto Raharjo wrote: >> Did you launch it? It won't launch for me, citing a missing libgvc > > Yes, i did try to launch it just now and it works fine without libgvc > > > > > _______________________________________________ > 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/ > Here's what I was getting before: bash-4.3$ su -c 'removepkg patchage' bash-4.3$ ldd /usr/bin/patchage | grep -i found libgvc.so.6 => not found libcgraph.so.6 => not found libcdt.so.5 => not found bash-4.3$ ls /var/log/packages/patchage-1.0.0-x86_64-1_SBo /var/log/packages/patchage-1.0.0-x86_64-1_SBo bash-4.3# installpkg /tmp/graphviz-2.40.1-x86_64-1_SBo.tgz bash-4.3$ ldd /usr/bin/patchage | grep -i found bash-4.3$ But after you tested yours, I removed graphviz, ganv, and patchage. Rebuilt ganv and patchage, and it they worked without graphviz. I guess I must have somehow built patchage against graphviz at some point...?? Anyway, working now. Thanks for the sanity check, Willy. -klaatu -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From jebrhansen+SBo at gmail.com Fri Nov 17 02:43:03 2017 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Thu, 16 Nov 2017 21:43:03 -0500 Subject: [Slackbuilds-users] Request to take over maintainership of openresolv Message-ID: SBo Admins, syncbq, the current maintainer for openresolv hasn't made any updates since 2013. There were several issues with the SlackBuild that prevented it from working on my system. I've figured out the issues after emailing the developer, and I've adjusted the SlackBuild to now build a properly working package. A user on the LQ forum already attempted to email the maintainer with no response, and I'd rather not wait another week or two to try emailing him/her to see if they respond. Are there any issues with me taking over the maintenance? The last few git updates have been made by admins, including a version bump by Willy earlier this year. https://slackbuilds.org/repository/14.2/network/openresolv/ Thanks, Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Fri Nov 17 05:25:05 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 17 Nov 2017 12:25:05 +0700 Subject: [Slackbuilds-users] Request to take over maintainership of openresolv In-Reply-To: References: Message-ID: <3711836f-315e-38dd-f15a-8c1c9b399cd3@slackbuilds.org> > syncbq, the current maintainer for openresolv hasn't made any updates since > 2013. There were several issues with the SlackBuild that prevented it from > working on my system. I've figured out the issues after emailing the > developer, and I've adjusted the SlackBuild to now build a properly working > package. > > A user on the LQ forum already attempted to email the maintainer with no > response, and I'd rather not wait another week or two to try emailing > him/her to see if they respond. Are there any issues with me taking over > the maintenance? The last few git updates have been made by admins, > including a version bump by Willy earlier this year. > > https://slackbuilds.org/repository/14.2/network/openresolv/ Feel free to submit a takeover :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Fri Nov 17 06:22:45 2017 From: yalhcru at gmail.com (B Watson) Date: Fri, 17 Nov 2017 01:22:45 -0500 Subject: [Slackbuilds-users] patchage missing dependency listing In-Reply-To: <5ef1d3d5-b18a-ecbb-f210-c5e62eb029da@member.fsf.org> References: <6bf59d4e-7412-187a-5a34-2f8e9fa2cb96@member.fsf.org> <0d823d32-8da2-981d-a5c0-41f6c80d7aa6@slackbuilds.org> <430be243-0005-6cc7-ba95-f353879e60f1@slackbuilds.org> <5ef1d3d5-b18a-ecbb-f210-c5e62eb029da@member.fsf.org> Message-ID: On 11/16/17, Klaatu wrote: > bash-4.3$ su -c 'removepkg patchage' > bash-4.3$ ldd /usr/bin/patchage | grep -i found > libgvc.so.6 => not found > libcgraph.so.6 => not found > libcdt.so.5 => not found > bash-4.3$ ls /var/log/packages/patchage-1.0.0-x86_64-1_SBo > /var/log/packages/patchage-1.0.0-x86_64-1_SBo > > bash-4.3# installpkg /tmp/graphviz-2.40.1-x86_64-1_SBo.tgz > bash-4.3$ ldd /usr/bin/patchage | grep -i found > bash-4.3$ Probly a good idea to mention graphviz as an optional dependency in the README. From roy.lanek at yandex.com Fri Nov 17 20:54:49 2017 From: roy.lanek at yandex.com (Roy Lanek) Date: Sat, 18 Nov 2017 03:54:49 +0700 Subject: [Slackbuilds-users] conky doesn't build LONGER Message-ID: <20171117205449.GA4687@sirih.local.host> Conky not building since a LONG time now. Likely for lua + tolua++ way too old while gcc less forgiving. I am on current, even the very last one, but it shouldn't matter, in fact don't even report the detailed errors which should be reproducible by anyone anyway, I guess. Cheers, /Roy -- 555555555555555555555555555555555 jadilah orang pandai bagai padi yang merunduk 55555 . 5 l 4 c K W 4 r 3 555555 be a smart man, like drooping paddy--which droops 55555 +------------ L1NuX 555555 more as it matures since its kernel is getting 555555555555555555555555555555555 heavier [means: smart man is usually humble] From willysr at slackbuilds.org Sat Nov 18 06:00:48 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 18 Nov 2017 13:00:48 +0700 Subject: [Slackbuilds-users] Updates - 20171118.1 Message-ID: <2c7da9e6-2504-3161-74d4-c51763c018d0@slackbuilds.org> Sat Nov 18 05:42:01 UTC 2017 academic/copasi: Updated for version 4.22.170. academic/reduce-algebra: Updated for version 20171112svn4264. academic/veusz: Updated for version 2.1.1. audio/clyrics: Updated for version 0.09. desktop/evilwm: Updated for version 1.1.1. desktop/jgmenu: Updated for version 0.7.4. desktop/libqtxdg: Added (Specs implementations for Qt). desktop/moka-icon-theme: Updated for version 20171021. desktop/numix-icon-theme: Updated for version 20171110. desktop/paper-gtk-theme: Updated for version 20160816. desktop/paper-icon-theme: Updated for version 20170917. desktop/qtpass: Updated for version 1.2.0. desktop/rofi: Updated for version 1.4.2. desktop/xed: Updated for version 1.6.2. development/arm-binutils: Updated for version 2.29. development/binwalk: Amend email address. development/check: Updated for version 0.12.0 + new maintainer. development/codeblocks: Updated for version 16.01. development/dart: Updated for version 1.24.2. development/diffoscope: Updated for version 88. development/gcc-d: Updated for version 2.076.0_b2 development/gcclegacy494: Patched for glibc-2.26 (-current). development/google-webdesigner: Updated for version 2.0.0.1113. development/jupyter-ipywidgets: Updated for version 7.0.4. development/jupyter-nbdime: Updated for version 0.4.0. development/kicad: Updated for version 4.0.7. development/meson: Updated for version 0.43.0. development/newlib: Added (C Library). development/robotframework: Added (acceptance test framework). development/sassc: Updated for version 3.4.7. development/universal-ctags: Updated for version b6031a8 development/vstudio: Updated for version 7.5.3. games/mangband: Fix .desktop and doinst.sh. games/mrboom: Added (Bomberman clone). games/tome-ah: Fix .desktop. games/tome-sx: Add .desktop. gis/mapnik: Updated for version 3.0.16. gis/pgrouting: Updated for version 2.5.2. gis/postgis: Updated for version 2.4.2. gis/python-mapnik: Updated for version 3.0.16. graphics/feh: Updated for version 2.22.2. graphics/scour: Amend email address. ham/chirp: Updated for version 20171104. libraries/GitPython: Updated for version 2.1.7. libraries/appstream-glib: Updated for version 0.7.4. libraries/bctoolbox: Added (Tools for Linphone components). libraries/belle-sip: Updated for version 1.6.3. libraries/bzrtp: Updated for version 1.0.6. libraries/json-parser: Added (very low footprint JSON parser). libraries/libmediainfo: Updated for version 17.10. libraries/libopenshot-audio: Updated for version 0.1.5 libraries/libopenshot: Updated for version 0.1.9 libraries/libsass: Updated for version 3.4.7. libraries/libsrtp: Added (Secure RTP libraries). libraries/libuv: Updated for version 1.16.1. libraries/libversion: Updated for version 2.3.0. libraries/linphone-srtp: Removed (replaced by libsrtp). libraries/mbedtls: Updated for version 2.6.1. libraries/msx264: Updated for version 1.5.3. libraries/netcdf: Updated for version 4.5.0. libraries/opensaml: Updated for version 2.6.1. libraries/polarssl: Removed (replaced by mbedtls). libraries/webkit2gtk: Updated for version 2.18.3. libraries/xmltooling: Updated for version 1.6.1. misc/no-more-secrets: Compress manpages. multimedia/flashplayer-plugin: Updated for version 27.0.0.187. multimedia/mediainfo: Updated for version 17.10. multimedia/obs-studio: Updated for version 20.1.3 multimedia/openshot: Updated for version 2.4.1 multimedia/opera-ffmpeg-codecs: Updated for version 62.0.3202.89. multimedia/pepperflash-plugin: Updated for version 27.0.0.187. network/PaleMoon: Updated for version 27.6.1. network/WireGuard: Updated for version 0.0.20171111. network/elinks: Patched to fix gopher html links. network/geomyidae: Added (A small C-based gopherd). network/linphone: Updated for version 3.12.0. network/mpop: Updated for version 1.2.6. network/openresolv: Updated for version 3.9.0. network/opera-developer: Updated for version 51.0.2776.0. network/opera: Updated for version 49.0.2725.39. network/palemoon: Updated for version 27.6.1. network/shibboleth-sp: Updated for version 2.6.1. network/slurm: Updated for version 17.02.9. network/stride: Added (cloud-based collaboration tool). network/suricata: Updated for version 4.0.1. network/transgui: Added a desktop menu entry network/ucarp: Added (portable implementation of the CARP protocol). network/urlwatch: Updated for version 2.7. network/wire: Updated for version 3.0.2816. network/youtube-dl: Updated for version 2017.11.15. office/texlive-docs: Updated for version 2017.171108. office/texlive-extra: Updated for version 2017.171108. office/texlive-fonts: Updated for version 2017.171108. office/texlive: Updated for version 2017.171108. perl/perl-CGI: Updated for version 4.37. perl/perl-Convert-ASN1: Updated for version 0.27. perl/perl-Math-Prime-Util-GMP: Updated for version 0.48. python/Pyro4: Updated for version 4.63. python/monty: Updated for version 1.0.2. python/pendulum: Updated for version 1.3.1. python/py: Updated for version 1.5.1. python/pyglet: Updated for version 1.3.0. python/pypng: Added (library for PNG image encoding and decoding). python/pytest-runner: Updated for version 3.0. python/python-autobahn: Updated for version 17.10.1. python/python-docker: Updated for version 2.6.1. python/python-libsass: Updated for version 0.13.4. python/python-serpent: Added (Serializer for Python expressions). python/python3-pexpect: Updated for version 4.3.0. python/regex: Updated for version 2017.11.09. python/responder: Added (LLMNR, NBT-NS and MDNS poisoner). python/tqdm: Updated for version 4.19.4. ruby/rubygem-pry: Updated for version 0.11.3. system/alacritty: Added (cross-platform, GPU-accelerated terminal). system/fd: Added (simple, fast, user-friendly alternative to find). system/fwupd: Updated for version 1.0.1. system/ksh-openbsd: Updated for version 20171112. system/lzop: Updated for version 1.04. system/mpich: Updated for version 3.2.1 system/noto-emoji: Updated for version git11275b5. system/passwordsafe: Updated for version 1.03BETA. system/pspg: Updated for version 0.5. system/slackroll: Patched for Slackware ARM support. system/sysdig: Remove old patch. system/wine: Updated for version 2.0.3. system/xrdp: Fixed doinst.sh. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From matteo.bernardini at gmail.com Sat Nov 18 06:01:47 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 18 Nov 2017 07:01:47 +0100 Subject: [Slackbuilds-users] conky doesn't build LONGER In-Reply-To: <20171117205449.GA4687@sirih.local.host> References: <20171117205449.GA4687@sirih.local.host> Message-ID: 2017-11-17 21:54 GMT+01:00 Roy Lanek : > Conky not building since a LONG time now. Likely for lua + > tolua++ way too old while gcc less forgiving. I am on current, > even the very last one, but it shouldn't matter, in fact don't > even report the detailed errors which should be reproducible by > anyone anyway, I guess. Hi Roy, conky builds fine here with just a patch for the newer gcc http://cgit.ponce.cc/slackbuilds/commit/?h=conky no problem at all with lua. Matteo From willysr at slackbuilds.org Sat Nov 18 06:08:10 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 18 Nov 2017 13:08:10 +0700 Subject: [Slackbuilds-users] Updates - 20171118.1 In-Reply-To: <2c7da9e6-2504-3161-74d4-c51763c018d0@slackbuilds.org> References: <2c7da9e6-2504-3161-74d4-c51763c018d0@slackbuilds.org> Message-ID: <0a5136b0-c4ba-f723-2cf1-0ce92fdd9b69@slackbuilds.org> > gis/mapnik: Updated for version 3.0.16. I forgot to mention a warning about mapnik update. There has been a slight typo during the batch update and it may broke third party tools due to a missing "\" for MD5SUM in gis/mapnik. You may need to add the "\" manually to fix the issue. It has been fixed on my branch and it will be included in the next public update. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From matteo.bernardini at gmail.com Sat Nov 18 07:33:47 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 18 Nov 2017 08:33:47 +0100 Subject: [Slackbuilds-users] conky doesn't build LONGER In-Reply-To: References: <20171117205449.GA4687@sirih.local.host> Message-ID: 2017-11-18 7:01 GMT+01:00 Matteo Bernardini : > 2017-11-17 21:54 GMT+01:00 Roy Lanek : >> Conky not building since a LONG time now. Likely for lua + >> tolua++ way too old while gcc less forgiving. I am on current, >> even the very last one, but it shouldn't matter, in fact don't >> even report the detailed errors which should be reproducible by >> anyone anyway, I guess. > > Hi Roy, > > conky builds fine here with just a patch for the newer gcc > > http://cgit.ponce.cc/slackbuilds/commit/?h=conky > > no problem at all with lua. sorry Roy, just an addition to clarify a misunderstanding that seem to pop in you original mail: the official SlackBuilds.org repository doesn't support current at all, just the latest stable Slackware release. Matteo From yth at ythogtha.org Sat Nov 18 09:00:40 2017 From: yth at ythogtha.org (Ythogtha) Date: Sat, 18 Nov 2017 10:00:40 +0100 Subject: [Slackbuilds-users] Dependency error for python3-matplotlib Message-ID: <20171118100040.6cfc50439236360cf92f3fed@ythogtha.org> Hi! python3-matplotlib lists python-dateutil as requirement, but it needs to be python3-dateutil. The README tells datetutil and pytz needs to be compiled against python3, so I guess dateutil was like pytz and needed to be bluit with PYTHON3=yes, but that doesn't seems to be the case anymore. -- Arnaud From kjhambrick at gmail.com Sat Nov 18 10:06:53 2017 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sat, 18 Nov 2017 04:06:53 -0600 Subject: [Slackbuilds-users] postfix version 3.2.4 Message-ID: Mario -- I saw that Slackware Current included postfix version 3.2.4 so I updated the SBo for version 3.2.4 ; built it and installed it yesterday. Running fine here after doing 'the usual' update procedure. Attached are diffs to bump the postfix.SlackBuild from version 3.2.3 to version 3.2.4 HTH and thanks for the postfix.SlackBuild ! -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- # diff -Naur postfix/postfix.info postfix-kjh/postfix.info # ----- cut here ----- --- postfix/postfix.info 2017-10-01 04:07:11.463351688 -0500 +++ postfix-kjh/postfix.info 2017-11-18 03:53:43.050581475 -0600 @@ -1,8 +1,8 @@ PRGNAM="postfix" -VERSION="3.2.3" +VERSION="3.2.4" HOMEPAGE="http://www.postfix.org/" -DOWNLOAD="http://cdn.postfix.johnriley.me/mirrors/postfix-release/official/postfix-3.2.3.tar.gz" -MD5SUM="cf62bfb8f379a0936d9a6d84d9c4504b" +DOWNLOAD="http://cdn.postfix.johnriley.me/mirrors/postfix-release/official/postfix-3.2.4.tar.gz" +MD5SUM="1137d95a3326ddf3d65296ba1c2d2430" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" # ----- cut there ----- # # diff -Naur postfix/postfix.SlackBuild postfix-kjh/postfix.SlackBuild # ----- cut here ----- --- postfix/postfix.SlackBuild 2017-10-01 04:07:11.463351688 -0500 +++ postfix-kjh/postfix.SlackBuild 2017-11-17 16:47:22.467573949 -0600 @@ -22,7 +22,7 @@ # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PRGNAM=postfix -VERSION=${VERSION:-3.2.3} +VERSION=${VERSION:-3.2.4} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} # ----- cut there ----- From roy.lanek at yandex.com Sat Nov 18 12:26:31 2017 From: roy.lanek at yandex.com (Roy Lanek) Date: Sat, 18 Nov 2017 19:26:31 +0700 Subject: [Slackbuilds-users] conky doesn't build LONGER In-Reply-To: References: <20171117205449.GA4687@sirih.local.host> Message-ID: <20171118122631.GA15942@sirih.local.host> > the official SlackBuilds.org repository doesn't support current > at all, just the latest stable Slackware release S?, vero, Willy gentilmente gi? me l'aveva ricordato mesi or sono al riguardo di altro software che mi aveva creato qualche problema, poi risolto. Grazie moltissimo. Applicher? il patch nelle prossime ore. Domanda: Non che Lua mi interessi pi? di tanto, ma come mai cos? indietro? La versione 5.1.5 risale al 2012, mentre la serie 5.1.3.x ? datata a partire dal 2015 con release regolari, l'ultimo del gennaio di quest'anno. Grazie ancora, siete tutti fortissimi, ciao /Roy (Padang/Sumatra Ovest) -- 555555555555555555555555555555555 malu bertanya, sesat di jalan 55555 . 5 l 4 c K W 4 r 3 555555 embarrassed to ask will result in 55555 +------------ L1NuX 555555 getting lost 555555555555555555555555555555555 From roy.lanek at yandex.com Sat Nov 18 12:33:46 2017 From: roy.lanek at yandex.com (Roy Lanek) Date: Sat, 18 Nov 2017 19:33:46 +0700 Subject: [Slackbuilds-users] conky doesn't build LONGER In-Reply-To: <20171118122631.GA15942@sirih.local.host> References: <20171117205449.GA4687@sirih.local.host> <20171118122631.GA15942@sirih.local.host> Message-ID: <20171118123346.GA25978@sirih.local.host> Erratum corrige > La versione 5.1.5 risale al 2012, mentre la serie 5.1.3.x ? > datata a partire dal 2015 mentre la serie 5.3.x /Roy -- 555555555555555555555555555555555 jadilah orang pandai bagai padi yang merunduk 55555 . 5 l 4 c K W 4 r 3 555555 be a smart man, like drooping paddy--which droops 55555 +------------ L1NuX 555555 more as it matures since its kernel is getting 555555555555555555555555555555555 heavier [means: smart man is usually humble] From roy.lanek at yandex.com Sat Nov 18 15:58:48 2017 From: roy.lanek at yandex.com (Roy Lanek) Date: Sat, 18 Nov 2017 22:58:48 +0700 Subject: [Slackbuilds-users] conky doesn't build LONGER In-Reply-To: <20171118123346.GA25978@sirih.local.host> References: <20171117205449.GA4687@sirih.local.host> <20171118122631.GA15942@sirih.local.host> <20171118123346.GA25978@sirih.local.host> Message-ID: <20171118155848.GA586@sirih.local.host> Okay, fatto, funziona: ora della fine si trattava soltanto di inserire un include, #include , tra altri due include, e nel header luamm.hh cosa che ho anche fatto manualmente, oltre che ad avere incrementato la versione di SlackBuild (avevo sempre il mio vecchio conky ancora)... non ho usato il patch per quest'ultimo. Ancora una volta MILLE GRAZIE. Cercher? di restituire il favore tempo permettendo. /Roy -- 555555555555555555555555555555555 bagai air di daun talas--as if water on a 55555 . 5 l 4 c K W 4 r 3 555555 leaf of talas [two things that never get 55555 +------------ L1NuX 555555 along ... talas has a thin waxy layer and 555555555555555555555555555555555 therefore is waterproof] From slackbuilds at jaxartes.net Sat Nov 18 16:22:27 2017 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sat, 18 Nov 2017 08:22:27 -0800 Subject: [Slackbuilds-users] Dependency error for python3-matplotlib In-Reply-To: <20171118100040.6cfc50439236360cf92f3fed@ythogtha.org> References: <20171118100040.6cfc50439236360cf92f3fed@ythogtha.org> Message-ID: <1685817.zaX0le0u4y@wintermute> On Saturday, November 18, 2017 1:00:40 AM PST Ythogtha wrote: > Hi! > > python3-matplotlib lists python-dateutil as requirement, but it needs to > be python3-dateutil. > The README tells datetutil and pytz needs to be compiled against python3, so > I guess dateutil was like pytz and needed to be bluit with PYTHON3=yes, but > that doesn't seems to be the case anymore. The confusion may be down to the different ways of doing SlackBuilds for Python 3 modules. By my count, there are four: 1. Silently install Python 3 support if python/python3 is installed. 2. Install Python 3 support if you pass PYTHON3=yes (or some other option) to the SlackBuild. 3. Have a separate python3-XYZ SlackBuild. Personally, I much prefer option 3 since I can then be explicit about what is installed and what should go in REQUIRES without complicated instructions in README about dependencies. Now that Python 3 is in current, however, the next release of Slackware and its Slackbuilds offers an opportunity. Option 1, previously my least favourite, is now viable except where a module exists for Python 2 but not 3 (or vice versa) and a few other edge cases (Jupyter kernels is one I know of). I know we don't like enforcing rules on maintainers, but a friendly recommendation for Python SlackBuilds would be welcome :) Ben From rob0 at slackbuilds.org Sat Nov 18 17:29:09 2017 From: rob0 at slackbuilds.org (Rob McGee) Date: Sat, 18 Nov 2017 11:29:09 -0600 Subject: [Slackbuilds-users] postfix version 3.2.4 In-Reply-To: References: Message-ID: <20171118172909.GK2027@harrier.slackbuilds.org> On Sat, Nov 18, 2017 at 04:06:53AM -0600, Konrad J Hambrick wrote: > I saw that Slackware Current included postfix version 3.2.4 so I > updated the SBo for version 3.2.4 ; built it and installed it > yesterday. Note that Slackware's Postfix slackbuild differs from the SBo build in important ways. Most importantly it discards the *.new files, instead using Postfix's own "postfix upgrade-configuration" command to more intelligently add new configuration items and failsafe overrides of default settings. Also, the Slackware package will be more upgrade-friendly because there are no longer any version-named directories in the default configuration. A symlink "postfix" in /usr/doc points to the postfix-$VERSION directory. Another significant change is that all the Slackware-provided map types, as well as both Dovecot and Cyrus SASL, are now enabled by default. IIRC the existing SBo script didn't even offer sqlite3 support, and it offered Cyrus vs. Dovecot as an either/or choice (you actually get Dovecot SASL support if you enable Cyrus.) I would recommend using the build in -current. -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From rshepard at appl-ecosys.com Sat Nov 18 17:37:49 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 18 Nov 2017 09:37:49 -0800 (PST) Subject: [Slackbuilds-users] postfix version 3.2.4 In-Reply-To: <20171118172909.GK2027@harrier.slackbuilds.org> References: <20171118172909.GK2027@harrier.slackbuilds.org> Message-ID: On Sat, 18 Nov 2017, Rob McGee wrote: > Note that Slackware's Postfix slackbuild differs from the SBo build in > important ways. Most importantly it discards the *.new files, instead > using Postfix's own "postfix upgrade-configuration" command to more > intelligently add new configuration items and failsafe overrides of > default settings. > I would recommend using the build in -current. Rob, I've been using the SBo script for years, and upgrade when Wietse sends a notice of a new release. I'm running 14.2, not current, and specify Cyrus on the SlackBuild command line because that works and I had issues getting dovecot to work. And I need to be careful about not overwriting files with new ones, but looking for changes to make manually. Should I copy the build script from -current and replace the SBo script for future upgrades? I'm already running 3.2.4 here. Thanks, Rich From kjhambrick at gmail.com Sat Nov 18 22:20:34 2017 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sat, 18 Nov 2017 16:20:34 -0600 Subject: [Slackbuilds-users] postfix version 3.2.4 In-Reply-To: References: <20171118172909.GK2027@harrier.slackbuilds.org> Message-ID: All -- I too use the SBo postfix.SlackBuild via a wrapper script ( attached ) so that I am consistent with my opptions. In addition, the postfix.SlackBuild wrapper script includes a reminder so I 'do it right' each time. Sorry if I gave the impression that I wanted to change the SBo postfix.SlaokBuild to the Slackware Current SlackBuild. I didn't mean to imply that :) -- kjh On Sat, Nov 18, 2017 at 11:37 AM, Rich Shepard wrote: > On Sat, 18 Nov 2017, Rob McGee wrote: > > Note that Slackware's Postfix slackbuild differs from the SBo build in >> important ways. Most importantly it discards the *.new files, instead >> using Postfix's own "postfix upgrade-configuration" command to more >> intelligently add new configuration items and failsafe overrides of >> default settings. >> > > I would recommend using the build in -current. >> > > Rob, > > I've been using the SBo script for years, and upgrade when Wietse sends a > notice of a new release. I'm running 14.2, not current, and specify Cyrus > on > the SlackBuild command line because that works and I had issues getting > dovecot to work. And I need to be careful about not overwriting files with > new ones, but looking for changes to make manually. > > Should I copy the build script from -current and replace the SBo script > for future upgrades? I'm already running 3.2.4 here. > > Thanks, > > Rich > > _______________________________________________ > 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: -------------- next part -------------- #!/bin/sh DoName="postfix.SlackBuild" . ./postfix.info MyVersion="$VERSION" LogNam="$DoName-$MyVersion.log" unset PRGNAM unset VERSION unset HOMEPAGE unset DOWNLOAD unset MD5SUM unset DOWNLOAD_x86_64 unset MD5SUM_x86_64 unset REQUIRES unset MAINTAINER unset EMAIL # # set and export any extra variables here # export SASL=cyrus export DATABASE=pgsql # # the README is here # # Postfix is Wietse Venema's mailer that started life as an alternative to the # widely-used Sendmail program. It attempts to be fast, easy to administer, and # secure, while at the same time, being sendmail compatible enough to not upset # existing users. Thus, the outside has a sendmail-ish flavor, but the inside is # completely different. # # This script builds postfix with optional support for Dovecot SASL, Cyrus SASL # can be enabled with: # # SASL=cyrus ./postfix.SlackBuild # # You can also enable support for MySQL: # # DATABASE=mysql ./postfix.SlackBuild # # PostgreSQL support can be enabled with: # # DATABASE=pgsql ./postfix.SlackBuild # # On systems with multiple instances, add major version, eg: DATABASE=pgsql-9.5 # # This script will find support for BerkleyDB and PCRE automagically; TLS support # requires openssl package, openssl-solibs alone is not enough. Additionally, this # script doesn't add postfix user and groups, instead it offers sane defaults that # won't conflict with system users and groups, and other scripts from the SBo. # # Package created with this script will conflict with stock sendmail package, you # *should* remove sendmail before installing postfix, otherwise sendmail updates # could break your postfix instance. # # When upgrading from an older postfix version, make sure the variables such as # html_directory and readme_directory in /etc/postfix/main.cf point to the new # location. These can also be fixed later, afterwards make sure to run: # # postfix set-permissions # # Furthermore, many of the utilities in postfix have multiple manpages such as # postconf(5) and postconf(8). Use man -k to find them, and don't forget to # subscribe to the postfix-users mailing list! # # the README is there # # do the deed # echo "$DoName startup at `date`" |tee $LogNam ./$DoName 2>&1 |tee -a $LogNam RetCode=$? UpPkg="# cannot find the new postfix package in /tmp/ ... RetCode = $RetCode" MvPkg="$UpPkg" if [ "$RetCode" = "0" ] then MyPkg="`ls -1t /tmp/postfix-$MyVersion-*.tgz |head -1`" RetCode=${PIPESTATUS[0]} if [ "$MyPkg" = "" -o "$RetCode" != "0" ] then UpPkg="# could not find /tmp/postfix-$MyVersion-*.tgz ... RetCode = $RetCode" MvPkg="$UpPkg" else UpPkg="upgradepkg $MyPkg" MvPkg="mv $MyPkg ../pkg/" fi else UpPkg="# $DoName FAILED ... RetCode = $RetCode" MvPkg="$UpPkg" fi # # postfix set-permissions will fail because I've got an old main.cf and # because my main.cf points at symlink /usr/doc/postfix and because the # symlink points at the old version. Set a reminder for myself here ! # cat <&2 ########################################################################### ### REMINDER ### ########################################################################### # # be sure to stop postfix before upgradepkg: # /etc/rc.d/rc.postfix stop # # NOW it is safe to upgradepkg # $UpPkg # # now fix your /usr/doc/postfix symlink like this: # rm -f /usr/doc/postfix && ln -s /usr/doc/postfix-$MyVersion /usr/doc/postfix # # and rerun postfix set-permissions: # /usr/sbin/postfix set-permissions # # finally, restart postfix # /etc/rc.d/rc.postfix start # # and save the package: # $MvPkg FixME_Tag # # log your results # echo "$DoName complete at `date` ... RetCode = $RetCode" |tee -a $LogNam exit $RetCode From rworkman at slackbuilds.org Sat Nov 18 22:36:54 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 18 Nov 2017 16:36:54 -0600 Subject: [Slackbuilds-users] Dependency error for python3-matplotlib In-Reply-To: <1685817.zaX0le0u4y@wintermute> References: <20171118100040.6cfc50439236360cf92f3fed@ythogtha.org> <1685817.zaX0le0u4y@wintermute> Message-ID: <20171118163654.639820fb@home.rlworkman.net> On Sat, 18 Nov 2017 08:22:27 -0800 Benjamin Trigona-Harany wrote: > On Saturday, November 18, 2017 1:00:40 AM PST Ythogtha wrote: > > Hi! > > > > python3-matplotlib lists python-dateutil as requirement, > > but it needs to be python3-dateutil. > > The README tells datetutil and pytz needs to be compiled against > > python3, so I guess dateutil was like pytz and needed to be bluit > > with PYTHON3=yes, but that doesn't seems to be the case anymore. > > The confusion may be down to the different ways of doing SlackBuilds > for Python 3 modules. By my count, there are four: > > 1. Silently install Python 3 support if python/python3 is installed. > 2. Install Python 3 support if you pass PYTHON3=yes (or some other > option) to the SlackBuild. > 3. Have a separate python3-XYZ SlackBuild. > > Personally, I much prefer option 3 since I can then be explicit about > what is installed and what should go in REQUIRES without complicated > instructions in README about dependencies. > > Now that Python 3 is in current, however, the next release of > Slackware and its Slackbuilds offers an opportunity. Option 1, > previously my least favourite, is now viable except where a module > exists for Python 2 but not 3 (or vice versa) and a few other edge > cases (Jupyter kernels is one I know of). > > I know we don't like enforcing rules on maintainers, but a friendly > recommendation for Python SlackBuilds would be welcome :) For Slackware 15.0, I think the best option is to have both python2 and python3 support in a single package, since there's the expectation that both python2 and python3 are on the system already. -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 kingbeowulf at gmail.com Sun Nov 19 18:08:32 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 19 Nov 2017 10:08:32 -0800 Subject: [Slackbuilds-users] conky doesn't build LONGER In-Reply-To: <20171118155848.GA586@sirih.local.host> References: <20171117205449.GA4687@sirih.local.host> <20171118122631.GA15942@sirih.local.host> <20171118123346.GA25978@sirih.local.host> <20171118155848.GA586@sirih.local.host> Message-ID: <85c0e8ec-0fd2-2f99-60df-c3a5cd8b98ce@gmail.com> On 11/18/2017 07:58 AM, Roy Lanek wrote: > Okay, fatto, funziona: ora della fine si trattava soltanto di > inserire un include, #include , tra altri due > include, e nel header luamm.hh cosa che ho > anche fatto manualmente, oltre che ad avere incrementato la > versione di SlackBuild (avevo sempre il mio vecchio conky > ancora)... non ho usato il patch per quest'ultimo. > > Ancora una volta MILLE GRAZIE. Cercher? di restituire il favore > tempo permettendo. > > /Roy > Not to belittle your culture or language ("Okay, fatto" might be misunderstood by some anglophiles here - especially us obese Americans), but you may find this list more constructive in English (UK or USA), as that has been the historical standard for Slackware. Google translate helps but can mangle meaning a bit sometimes. Wir k?nnen uns also auf Deutsch unterhalten, aber vielleicht das ist noch unklarer als Italienische. This is important also when posting a solution, that may be useful to some once CURRENT goes STABLE. Thanks Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From roy.lanek at yandex.com Sun Nov 19 19:13:45 2017 From: roy.lanek at yandex.com (Roy Lanek) Date: Mon, 20 Nov 2017 02:13:45 +0700 Subject: [Slackbuilds-users] conky doesn't build LONGER In-Reply-To: <85c0e8ec-0fd2-2f99-60df-c3a5cd8b98ce@gmail.com> References: <20171117205449.GA4687@sirih.local.host> <20171118122631.GA15942@sirih.local.host> <20171118123346.GA25978@sirih.local.host> <20171118155848.GA586@sirih.local.host> <85c0e8ec-0fd2-2f99-60df-c3a5cd8b98ce@gmail.com> Message-ID: <20171119191345.GA2754@sirih.local.host> > "Okay, fatto" might be misunderstood by some anglophiles here - > especially us obese Americans HAHAHA, true, didn't think at that. I have relatives who have migrated to the US generations ago, from Switzerland, married there with Italians who went to the US also, became Americans, and live in California since: San Francisco, Salinas, Soledad, Monterey. In San Francisco, looking at the sea once, I remember--was eighteen years old--to have said, look... *foche* (= Italian x seals, 1x seal = foca) for in Switzerland we do look at the seals at the zoo or at he circus only. There were other people present, looking at the sea, so they remembered me to better keep my mouth shut :^) /Roy -- 555555555555555555555555555555555 bagai air di daun talas--as if water on a 55555 . 5 l 4 c K W 4 r 3 555555 leaf of talas [two things that never get 55555 +------------ L1NuX 555555 along ... talas has a thin waxy layer and 555555555555555555555555555555555 therefore is waterproof] -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From roy.lanek at yandex.com Sun Nov 19 20:17:17 2017 From: roy.lanek at yandex.com (Roy Lanek) Date: Mon, 20 Nov 2017 03:17:17 +0700 Subject: [Slackbuilds-users] conky doesn't build LONGER In-Reply-To: <20171118122631.GA15942@sirih.local.host> References: <20171117205449.GA4687@sirih.local.host> <20171118122631.GA15942@sirih.local.host> Message-ID: <20171119201717.GA26323@sirih.local.host> > > the official SlackBuilds.org repository doesn't support current > > at all, just the latest stable Slackware release > > S?, vero, Willy gentilmente gi? me l'aveva ricordato mesi or sono > al riguardo di altro software che mi aveva creato qualche > problema, poi risolto. True, Willy kindly told me so a couple of months ago already (I am on current) when other software gave me a few problems which went solved eventually. > Grazie moltissimo. Applicher? il patch nelle prossime ore. Thank you very much. I will apply the patch in the next few hours. > Domanda: Non che Lua mi interessi pi? di tanto, ma come mai cos? > indietro? La versione 5.1.5 risale al 2012, mentre la serie > 5.1.3.x ? datata a partire dal 2015 con release regolari, > l'ultimo del gennaio di quest'anno. Question: Not that Lua interests me more than much, but why let it behind that much? Version 5.1.5 dates back to 2012, while the series 5.3.x begins 2015 with regular releases, the last in January of this year. > Grazie ancora, siete tutti fortissimi, ciao Thanks again, you all rock, ciao. > Okay, fatto, funziona: ora della fine si trattava soltanto di > inserire un include, #include , tra altri due > include, e nel header luamm.hh cosa che ho > anche fatto manualmente, oltre che ad avere incrementato la > versione di SlackBuild (avevo sempre il mio vecchio conky > ancora)... non ho usato il patch per quest'ultimo Okay, done, it works: Finally it was only about inserting an include, #include , between two others includes, and in the header luamm.hh which I even have done manually; plus have bumped up the version of SlackBuild (I had my old conky around) have hence not even applied the patch via the patch utility Once again a HUGE THANK YOU. I will try to return the favor time permitting. Meglio cos?? ;) Better so? Was thinking that being me on current and having only myself to complain it would have interested nobody. Cheers, /Roy -- 555555555555555555555555555555555 buruk muka cermin dibelah 55555 . 5 l 4 c K W 4 r 3 555555 ugly face, the mirror is split [blaming 55555 +------------ L1NuX 555555 the wrong cause or creating a scapegoat] 555555555555555555555555555555555 From slackbuilds at jaxartes.net Mon Nov 20 07:27:38 2017 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sun, 19 Nov 2017 23:27:38 -0800 Subject: [Slackbuilds-users] Dependency error for python3-matplotlib In-Reply-To: <20171118163654.639820fb@home.rlworkman.net> References: <20171118100040.6cfc50439236360cf92f3fed@ythogtha.org> <1685817.zaX0le0u4y@wintermute> <20171118163654.639820fb@home.rlworkman.net> Message-ID: <2170065.IK3XKz1iaR@wintermute> On Saturday, November 18, 2017 2:36:54 PM PST Robby Workman wrote: > For Slackware 15.0, I think the best option is to have both python2 and > python3 support in a single package, since there's the expectation that > both python2 and python3 are on the system already. This would be preferable, and this is also the approach Pat is taking with Python packages in current. It will take some extra work for maintainers come release time, but the time investment will pay off in fewer scripts to maintain. Ben From willysr at slackbuilds.org Mon Nov 20 08:29:59 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 20 Nov 2017 15:29:59 +0700 Subject: [Slackbuilds-users] Dependency error for python3-matplotlib In-Reply-To: <2170065.IK3XKz1iaR@wintermute> References: <20171118100040.6cfc50439236360cf92f3fed@ythogtha.org> <1685817.zaX0le0u4y@wintermute> <20171118163654.639820fb@home.rlworkman.net> <2170065.IK3XKz1iaR@wintermute> Message-ID: <5ab84a45-57c4-a198-38c6-defe81950306@slackbuilds.org> >> For Slackware 15.0, I think the best option is to have both python2 and >> python3 support in a single package, since there's the expectation that >> both python2 and python3 are on the system already. > > This would be preferable, and this is also the approach Pat is taking with > Python packages in current. It will take some extra work for maintainers come > release time, but the time investment will pay off in fewer scripts to > maintain. I agree with this settings, suppose Slackware drop Python 2 someday, it's very easy to remove the python setup.py line instead of removing the whole script -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From yth at ythogtha.org Mon Nov 20 09:12:47 2017 From: yth at ythogtha.org (Ythogtha) Date: Mon, 20 Nov 2017 10:12:47 +0100 Subject: [Slackbuilds-users] Dependency error for python3-matplotlib In-Reply-To: <20171118163654.639820fb@home.rlworkman.net> References: <20171118100040.6cfc50439236360cf92f3fed@ythogtha.org> <1685817.zaX0le0u4y@wintermute> <20171118163654.639820fb@home.rlworkman.net> Message-ID: <20171120101247.76f808ecb37de8c82ea7d939@ythogtha.org> > On Sat, 18 Nov 2017 08:22:27 -0800 > Benjamin Trigona-Harany wrote: > > > On Saturday, November 18, 2017 1:00:40 AM PST Ythogtha wrote: > > > Hi! > > > > > > python3-matplotlib lists python-dateutil as requirement, > > > but it needs to be python3-dateutil. > > > The README tells datetutil and pytz needs to be compiled against > > > python3, so I guess dateutil was like pytz and needed to be bluit > > > with PYTHON3=yes, but that doesn't seems to be the case anymore. > > > > The confusion may be down to the different ways of doing SlackBuilds > > for Python 3 modules. By my count, there are four: > > > > 1. Silently install Python 3 support if python/python3 is installed. > > 2. Install Python 3 support if you pass PYTHON3=yes (or some other > > option) to the SlackBuild. > > 3. Have a separate python3-XYZ SlackBuild. > > > > Personally, I much prefer option 3 since I can then be explicit about > > what is installed and what should go in REQUIRES without complicated > > instructions in README about dependencies. > > > > Now that Python 3 is in current, however, the next release of > > Slackware and its Slackbuilds offers an opportunity. Option 1, > > previously my least favourite, is now viable except where a module > > exists for Python 2 but not 3 (or vice versa) and a few other edge > > cases (Jupyter kernels is one I know of). > > > > I know we don't like enforcing rules on maintainers, but a friendly > > recommendation for Python SlackBuilds would be welcome :) > > > For Slackware 15.0, I think the best option is to have both python2 and > python3 support in a single package, since there's the expectation that > both python2 and python3 are on the system already. > > -RW I agree. Anyway, the python3-matplotlib.info still needs to list python3-dateutil instead as python-dateutil as requirement. At least for the time being ! -- Arnaud From willysr at slackbuilds.org Mon Nov 20 10:39:14 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 20 Nov 2017 17:39:14 +0700 Subject: [Slackbuilds-users] Dependency error for python3-matplotlib In-Reply-To: <20171120101247.76f808ecb37de8c82ea7d939@ythogtha.org> References: <20171118100040.6cfc50439236360cf92f3fed@ythogtha.org> <1685817.zaX0le0u4y@wintermute> <20171118163654.639820fb@home.rlworkman.net> <20171120101247.76f808ecb37de8c82ea7d939@ythogtha.org> Message-ID: > I agree. > Anyway, the python3-matplotlib.info still needs to list python3-dateutil instead > as python-dateutil as requirement. At least for the time being ! Done in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Mon Nov 20 11:07:37 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 20 Nov 2017 18:07:37 +0700 Subject: [Slackbuilds-users] Updates - 20171120.1 Message-ID: <907bf72e-dcaa-7186-4d75-9cc1edd24f8a@slackbuilds.org> Just a quick update to fix mapnik typo and also more migration to https Mon Nov 20 10:59:58 UTC 2017 academic/cadabra2: Switch to https. academic/fet: Updated for version 5.34.0. academic/pyCRAC: Updated for version 1.2.4.0. audio/alsa-plugin-jack: Switch to https. development/hhvm: Switch to https. development/ign-math2: Switch to https. development/libcutl: Switch to https. development/libodb-boost: Switch to https. development/libodb-mysql: Switch to https. development/libodb-pgsql: Switch to https. development/libodb-qt: Switch to https. development/libodb-sqlite: Switch to https. development/libodb: Switch to https. development/neovim: Updated for version 0.2.2. development/nexus: Updated for version 3.6.1_02. development/odb: Switch to https. development/python3-matplotlib: Fix DEP and README. games/fortune-futurama: Switch to https. gis/mapnik: Fix .info. ham/wsjtx: Added (Weak Signal Communication, by K1JT). ham/xlog: Updated for version 2.0.15 libraries/CherryPy: Updated for version 12.0.0. libraries/ignition-math2: Switch to https. libraries/ignition-transport: Switch to https. misc/dwdiff: Switch to https. misc/heimdall: Switch to https. multimedia/opera-developer-ffmpeg-codecs: Updated for version 64.0. network/dropbox: Updated for version 39.4.49. network/elinks: Add options to disable mouse and gpm. network/ipscan: Updated for version 3.5.2. network/newsbeuter: Update to https. network/nmh: Updated for version 1.7. network/ntop: Switch to https. network/you-get: Updated for version 0.4.964. perl/perl-File-Share: Added (perl module File::Share). python/cheroot: Updated for version 5.9.1. python/dulwich: Updated for version 0.18.6. python/flakes8: Updated for version 3.5.0. python/jaraco.classes: Added (functions for Python). python/msgpack-python: Switch to https. python/pyflakes: Updated for version 1.6.0. ruby/rubygem-msgpack: Switch to https. system/docker: Disable warning when building CLI. system/gtklp: Switch to https. system/jenkins: Updated for version 2.73.3. system/lshw: Switch to https. system/ovmf: Added (uefi firmware for qemu). system/rtirq: Switch to https. system/zuluCrypt: Updated for version 5.4.0. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From matteo.bernardini at gmail.com Mon Nov 20 12:02:47 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 20 Nov 2017 13:02:47 +0100 Subject: [Slackbuilds-users] conky doesn't build LONGER In-Reply-To: <20171119201717.GA26323@sirih.local.host> References: <20171117205449.GA4687@sirih.local.host> <20171118122631.GA15942@sirih.local.host> <20171119201717.GA26323@sirih.local.host> Message-ID: 2017-11-19 21:17 GMT+01:00 Roy Lanek : > Question: Not that Lua interests me more than much, but why > let it behind that much? Version 5.1.5 dates back to 2012, > while the series 5.3.x begins 2015 with regular releases, the > last in January of this year. because newer lua versions cannot be used with much of the stuff we have on SBo (that supports only lua-5.1.x): lua 5.3 introduced a compatiblity mode but it doesn't actually work well. the solution would be to: - parallel install different lua versions; - checking that the various things that need those find the right one in each case. ...but this solution is really hard to implement, as the script being involved are =~ 150 and they have to be all tested working to implement it on the repository. if someone feels like doing this work it would be highly appreciated. Matteo From roy.lanek at yandex.com Mon Nov 20 15:37:26 2017 From: roy.lanek at yandex.com (Roy Lanek) Date: Mon, 20 Nov 2017 22:37:26 +0700 Subject: [Slackbuilds-users] conky doesn't build LONGER In-Reply-To: References: <20171117205449.GA4687@sirih.local.host> <20171118122631.GA15942@sirih.local.host> <20171119201717.GA26323@sirih.local.host> Message-ID: <20171120153726.GA4989@sirih.local.host> > - parallel install different lua versions; Which looks feasible if I am not mistaken > - checking that the various things that need those find the right one > in each case. > ...but this solution is really hard to implement, as the script being > involved are =~ 150 and they have to be all tested working to > implement it on the repository. > if someone feels like doing this work it would be highly appreciated. What about DISTRIBUTING the work: five, then, more scripts to run, verify poor man style, and fix if possible and be it by just sending feedback, per person? Myself I am not a champion in bash (it would be a matter of weeks OTOH) preferring ksh and mksh which are my bread and butter on scripting. Would do my part nonetheless of course. Establishing a partition along PRIORITIES -- which are those packages who depend on Lua, are the most important and demand to NOT be *dangling* -- is of course to be done 1st. It's anyway something that will need to be done one day. It recalls me Python and Perl. /Roy -- 555555555555555555555555555555555 gajah bertarung lawsan gajah, 55555 . 5 l 4 c K W 4 r 3 555555 pelanduk mati di tengah-tengah 55555 +------------ L1NuX 555555 elephants wage war against elephants, 555555555555555555555555555555555 deers die in the midst From roy.lanek at yandex.com Mon Nov 20 15:42:41 2017 From: roy.lanek at yandex.com (Roy Lanek) Date: Mon, 20 Nov 2017 22:42:41 +0700 Subject: [Slackbuilds-users] conky doesn't build LONGER In-Reply-To: References: <20171117205449.GA4687@sirih.local.host> <20171118122631.GA15942@sirih.local.host> <20171119201717.GA26323@sirih.local.host> Message-ID: <20171120154241.GA30212@sirih.local.host> > script being involved are =~ 150 Can a transitive closure on those be done, how? -- 555555555555555555555555555555555 kalau tak ingin terlimbur pasang, 55555 . 5 l 4 c K W 4 r 3 555555 jangan berumah di tepi laut 55555 +------------ L1NuX 555555 if you don't want to get flooded, 555555555555555555555555555555555 don't build a house next to the sea From yalhcru at gmail.com Mon Nov 20 17:47:24 2017 From: yalhcru at gmail.com (B Watson) Date: Mon, 20 Nov 2017 12:47:24 -0500 Subject: [Slackbuilds-users] conky doesn't build LONGER In-Reply-To: References: <20171117205449.GA4687@sirih.local.host> <20171118122631.GA15942@sirih.local.host> <20171119201717.GA26323@sirih.local.host> Message-ID: On 11/20/17, Matteo Bernardini wrote: > - parallel install different lua versions; > - checking that the various things that need those find the right one > in each case. > ...but this solution is really hard to implement, as the script being > involved are =~ 150 and they have to be all tested working to > implement it on the repository. > if someone feels like doing this work it would be highly appreciated. Looks like a lot of stuff links with lua's shared libs. I'd say, keep things exactly as they are for lua 5.1, and add a lua53 build that installs version 5.3 to a different prefix (maybe /opt/lua-5.3), and doesn't install anything *at all* in /usr (except for /usr/doc/ I suppose), so there's no chance of conflict. The lua53 build could also include a script, *disabled by default*, that sets $PATH and whatever else lua uses, with instructions in the README explaining how to source that script in .bash_profile. So if you want your user account to use lua-5.3 when you run a script that says "#!/usr/bin/env lua", you can, but root won't be set up that way. A script that says "#!/usr/bin/lua" will always run lua-5.1 though. Doing it that way, everything that currently uses lua 5.1 should continue to work as-is. Anything new that needs lua-5.3 will need to explicitly set the paths when building (maybe --with-lua=/opt/lua-5.3 or such, if it uses autotools), including -Wl,-rpath or whatever's needed to get the correct libs linked. SlackBuild scripts could also source the abovementioned environment script, if that would help. Once this is working, those 150 lua-using builds can slowly be tested against 5.3, and fixed/patched as needed. Or not: why bother? Working scripts are working scripts. Unless switching a script to use lua-5.3 actually makes the built package more useful to end-users, what would be the point? Disclaimer: I know very little about lua. The only reason it's impinged on my awareness is that mame uses it... but it has to build its own lua-5.3 from bundled sources, because it can't use 5.1. The rest of mame's build system is actually written in lua, I'd love it if things could be arranged so that mame could use a pre-existing lua 5.3 install. The only game-changer here would be if Pat someday decided to include lua in core Slackware. No idea if that's likely, so no point worrying about it now. From mario at slackware.hr Mon Nov 20 20:29:10 2017 From: mario at slackware.hr (Mario) Date: Mon, 20 Nov 2017 21:29:10 +0100 Subject: [Slackbuilds-users] postfix version 3.2.4 In-Reply-To: References: Message-ID: <63bf6a09-5817-c3cf-2dfe-4ef7962380c9@slackware.hr> On 11/18/2017 11:06 AM, Konrad J Hambrick wrote: > Mario -- > > I saw that Slackware Current included postfix version 3.2.4 so I updated > the SBo for version 3.2.4 ; built it and installed it yesterday. > > Running fine here after doing 'the usual' update procedure. > > Attached are diffs to bump the postfix.SlackBuild from version 3.2.3 to > version 3.2.4 > > HTH and thanks for the postfix.SlackBuild ! > > -- kjh Thanks. Updated in my branch :) -- Mario From duncan_roe at optusnet.com.au Tue Nov 21 21:38:30 2017 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Wed, 22 Nov 2017 08:38:30 +1100 Subject: [Slackbuilds-users] conky doesn't build LONGER In-Reply-To: References: <20171117205449.GA4687@sirih.local.host> <20171118122631.GA15942@sirih.local.host> <20171119201717.GA26323@sirih.local.host> Message-ID: <20171121213830.GB3386@dimstar.local.net> On Mon, Nov 20, 2017 at 12:47:24PM -0500, B Watson wrote: > On 11/20/17, Matteo Bernardini wrote: > > > - parallel install different lua versions; > > - checking that the various things that need those find the right one > > in each case. > > ...but this solution is really hard to implement, as the script being > > involved are =~ 150 and they have to be all tested working to > > implement it on the repository. > > if someone feels like doing this work it would be highly appreciated. > > Looks like a lot of stuff links with lua's shared libs. I'd say, > keep things exactly as they are for lua 5.1, and add a lua53 build > that installs version 5.3 to a different prefix (maybe /opt/lua-5.3), > and doesn't install anything *at all* in /usr (except for /usr/doc/ > I suppose), so there's no chance of conflict. > > The lua53 build could also include a script, *disabled by default*, > that sets $PATH and whatever else lua uses, with instructions in the > README explaining how to source that script in .bash_profile. So if you > want your user account to use lua-5.3 when you run a script that says > "#!/usr/bin/env lua", you can, but root won't be set up that way. A > script that says "#!/usr/bin/lua" will always run lua-5.1 though. > > Doing it that way, everything that currently uses lua 5.1 should continue > to work as-is. Anything new that needs lua-5.3 will need to explicitly > set the paths when building (maybe --with-lua=/opt/lua-5.3 or such, > if it uses autotools), including -Wl,-rpath or whatever's needed to > get the correct libs linked. SlackBuild scripts could also source the > abovementioned environment script, if that would help. > > Once this is working, those 150 lua-using builds can slowly be tested > against 5.3, and fixed/patched as needed. Or not: why bother? Working > scripts are working scripts. Unless switching a script to use lua-5.3 > actually makes the built package more useful to end-users, what would > be the point? > > Disclaimer: I know very little about lua. The only reason it's impinged > on my awareness is that mame uses it... but it has to build its own > lua-5.3 from bundled sources, because it can't use 5.1. The rest of > mame's build system is actually written in lua, I'd love it if things > could be arranged so that mame could use a pre-existing lua 5.3 install. > > The only game-changer here would be if Pat someday decided to include > lua in core Slackware. No idea if that's likely, so no point worrying > about it now. If liblua.so has been bunped to liblua.so.6.x.y, then from a runtime point of view it should be all right to install as standard. If not, report to upstream as a bug. What must not happen is for upgradepkg to remove liblua.so.5. That could be achieved by having a new package say lua53, or having lua build liblua.so.5 as well as liblua.so.6 (needs 2 tarballs: could have a COMPAT option to not build old library). Either way that should allow gentle migration, or am I missing something? Cheers ... Duncan. From yalhcru at gmail.com Wed Nov 22 01:14:25 2017 From: yalhcru at gmail.com (B Watson) Date: Tue, 21 Nov 2017 20:14:25 -0500 Subject: [Slackbuilds-users] conky doesn't build LONGER In-Reply-To: <20171121213830.GB3386@dimstar.local.net> References: <20171117205449.GA4687@sirih.local.host> <20171118122631.GA15942@sirih.local.host> <20171119201717.GA26323@sirih.local.host> <20171121213830.GB3386@dimstar.local.net> Message-ID: On 11/21/17, Duncan Roe wrote: > If liblua.so has been bunped to liblua.so.6.x.y, then from a runtime point > of > view it should be all right to install as standard. If not, report to > upstream > as a bug. Agreed, incompatible shared lib without .so version bump = a bug. Someone who actually cares about lua want to confirm that 5.3's shared lib is liblua.so.6 and not .so.5? > What must not happen is for upgradepkg to remove liblua.so.5. > > That could be achieved by having a new package say lua53, or having lua > build > liblua.so.5 as well as liblua.so.6 (needs 2 tarballs: could have a COMPAT > option > to not build old library). > > Either way that should allow gentle migration, or am I missing something? The other piece of the puzzle will be lua scripts that start with #!/usr/bin/lua or #!/usr/bin/env lua. Not being a lua expert, I dunno how common standalone lua scripts are, as compared to embedding lua via liblua.so. From rsamurti at gmail.com Wed Nov 22 03:45:57 2017 From: rsamurti at gmail.com (Ananda Murthy R S) Date: Wed, 22 Nov 2017 09:15:57 +0530 Subject: [Slackbuilds-users] How to build .txz package without editing .SlackBuild file. Message-ID: Hello, 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? Anand -- Close Windows ! Open source !! Free software from proprietary mafia !!! -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at chrisn.me.uk Wed Nov 22 04:12:35 2017 From: chris at chrisn.me.uk (Chris Novakovic) Date: Wed, 22 Nov 2017 04:12:35 +0000 Subject: [Slackbuilds-users] How to build .txz package without editing .SlackBuild file. In-Reply-To: References: Message-ID: 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 create a > .txz file? Export PKGTYPE=txz to the SlackBuild script. From kjhambrick at gmail.com Wed Nov 22 09:49:04 2017 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Wed, 22 Nov 2017 03:49:04 -0600 Subject: [Slackbuilds-users] intel-microcode version 20171117 Message-ID: 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 M-F-S = 06-5e-03 ( Intel i7-6700K ) has not been updated since April ): # ver intel-microcode -rw-r--r-- 1 root root 4206 Nov 22 03:28 /var/log/packages/intel-microcode-20171117-noarch-1_SBo # dmesg -t |grep micro microcode: CPU0 microcode updated early to revision 0xba, date = 2017-04-09 microcode: CPU1 microcode updated early to revision 0xba, date = 2017-04-09 microcode: CPU2 microcode updated early to revision 0xba, date = 2017-04-09 microcode: CPU3 microcode updated early to revision 0xba, date = 2017-04-09 microcode: CPU0 sig=0x506e3, pf=0x2, revision=0xba microcode: CPU1 sig=0x506e3, pf=0x2, revision=0xba microcode: CPU2 sig=0x506e3, pf=0x2, revision=0xba microcode: CPU3 sig=0x506e3, pf=0x2, revision=0xba microcode: CPU4 sig=0x506e3, pf=0x2, revision=0xba microcode: CPU5 sig=0x506e3, pf=0x2, revision=0xba microcode: CPU6 sig=0x506e3, pf=0x2, revision=0xba microcode: CPU7 sig=0x506e3, pf=0x2, revision=0xba microcode: Microcode Update Driver: v2.01 , Peter Oruba Anyhow, diffs for intel-microcode.info and intel-microcode.SlackBuild are attached. Thanks for the SlackBuilds Andrej ! -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- --- intel-microcode/intel-microcode.SlackBuild 2017-07-15 05:28:53.345899123 -0500 +++ intel-microcode-kjh/intel-microcode.SlackBuild 2017-11-22 02:58:08.798187961 -0600 @@ -24,7 +24,7 @@ PRGNAM=intel-microcode SRCNAM=microcode -VERSION=${VERSION:-20170707} +VERSION=${VERSION:-20171117} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} ARCH=noarch -------------- next part -------------- --- intel-microcode/intel-microcode.info 2017-07-15 05:28:53.345899123 -0500 +++ intel-microcode-kjh/intel-microcode.info 2017-11-22 02:57:46.805188907 -0600 @@ -1,8 +1,8 @@ PRGNAM="intel-microcode" -VERSION="20170707" +VERSION="20171117" HOMEPAGE="https://downloadcenter.intel.com/" -DOWNLOAD="https://downloadmirror.intel.com/26925/eng/microcode-20170707.tgz" -MD5SUM="fe4bcb12e4600629a81fb65208c34248" +DOWNLOAD="https://downloadmirror.intel.com/26925/eng/microcode-20171117.tgz" +MD5SUM="b294245d1f7f6c20f01edba53185f258" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" From atelszewski at gmail.com Wed Nov 22 11:01:55 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 22 Nov 2017 12:01:55 +0100 Subject: [Slackbuilds-users] intel-microcode version 20171117 In-Reply-To: References: Message-ID: <0d28cf33-6854-c9aa-8fb9-7ad04ed91bce@gmail.com> 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 that's a moot point because the firmware > for my M-F-S = 06-5e-03 ( Intel i7-6700K ) has not been updated since > April ): > > # ver intel-microcode > > -rw-r--r-- 1 root root 4206 Nov 22 03:28 > /var/log/packages/intel-microcode-20171117-noarch-1_SBo > > # dmesg -t |grep micro > > microcode: CPU0 microcode updated early to revision 0xba, date = 2017-04-09 > microcode: CPU1 microcode updated early to revision 0xba, date = 2017-04-09 > microcode: CPU2 microcode updated early to revision 0xba, date = 2017-04-09 > microcode: CPU3 microcode updated early to revision 0xba, date = 2017-04-09 > microcode: CPU0 sig=0x506e3, pf=0x2, revision=0xba > microcode: CPU1 sig=0x506e3, pf=0x2, revision=0xba > microcode: CPU2 sig=0x506e3, pf=0x2, revision=0xba > microcode: CPU3 sig=0x506e3, pf=0x2, revision=0xba > microcode: CPU4 sig=0x506e3, pf=0x2, revision=0xba > microcode: CPU5 sig=0x506e3, pf=0x2, revision=0xba > microcode: CPU6 sig=0x506e3, pf=0x2, revision=0xba > microcode: CPU7 sig=0x506e3, pf=0x2, revision=0xba > microcode: Microcode Update Driver: v2.01 >, Peter Oruba > > Anyhow, diffs for intel-microcode.info and > intel-microcode.SlackBuild are attached. > > Thanks for the SlackBuilds Andrej ! > > -- kjh I'll push an update soon enough. Thanks for letting me know. -- Best regards, Andrzej Telszewski From fellype at gmail.com Wed Nov 22 11:48:15 2017 From: fellype at gmail.com (Fellype do Nascimento) Date: Wed, 22 Nov 2017 09:48:15 -0200 Subject: [Slackbuilds-users] How to build .txz package without editing .SlackBuild file. In-Reply-To: References: Message-ID: <26684b49-e813-0ba2-8a51-757985e1d61d@gmail.com> 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 create a >> .txz file? > Export PKGTYPE=txz to the SlackBuild script. > Examples: PKGTYPE=txz ./yourprogram.SlackBuild PKGTYPE=txz sboinstall desired_program PKGTYPE=txz sboupgrade upgradable_programs Best regards Fellype From willysr at slackbuilds.org Wed Nov 22 12:22:16 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 22 Nov 2017 19:22:16 +0700 Subject: [Slackbuilds-users] How to build .txz package without editing .SlackBuild file. In-Reply-To: <26684b49-e813-0ba2-8a51-757985e1d61d@gmail.com> References: <26684b49-e813-0ba2-8a51-757985e1d61d@gmail.com> Message-ID: >>> 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. >> > Examples: > PKGTYPE=txz ./yourprogram.SlackBuild > PKGTYPE=txz sboinstall desired_program > PKGTYPE=txz sboupgrade upgradable_programs Even better, export it in your .bashrc or in your /etc/profile for global settings -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From kjhambrick at gmail.com Wed Nov 22 14:46:30 2017 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Wed, 22 Nov 2017 08:46:30 -0600 Subject: [Slackbuilds-users] intel-microcode version 20171117 In-Reply-To: <0d28cf33-6854-c9aa-8fb9-7ad04ed91bce@gmail.com> References: <0d28cf33-6854-c9aa-8fb9-7ad04ed91bce@gmail.com> Message-ID: 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 ( >> 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 M-F-S = 06-5e-03 ( Intel i7-6700K ) has not been updated since April ): >> >> # ver intel-microcode >> >> -rw-r--r-- 1 root root 4206 Nov 22 03:28 /var/log/packages/intel-microc >> ode-20171117-noarch-1_SBo >> >> # dmesg -t |grep micro >> >> microcode: CPU0 microcode updated early to revision 0xba, date = >> 2017-04-09 >> microcode: CPU1 microcode updated early to revision 0xba, date = >> 2017-04-09 >> microcode: CPU2 microcode updated early to revision 0xba, date = >> 2017-04-09 >> microcode: CPU3 microcode updated early to revision 0xba, date = >> 2017-04-09 >> microcode: CPU0 sig=0x506e3, pf=0x2, revision=0xba >> microcode: CPU1 sig=0x506e3, pf=0x2, revision=0xba >> microcode: CPU2 sig=0x506e3, pf=0x2, revision=0xba >> microcode: CPU3 sig=0x506e3, pf=0x2, revision=0xba >> microcode: CPU4 sig=0x506e3, pf=0x2, revision=0xba >> microcode: CPU5 sig=0x506e3, pf=0x2, revision=0xba >> microcode: CPU6 sig=0x506e3, pf=0x2, revision=0xba >> microcode: CPU7 sig=0x506e3, pf=0x2, revision=0xba >> microcode: Microcode Update Driver: v2.01 > >, Peter Oruba >> >> Anyhow, diffs for intel-microcode.info and >> intel-microcode.SlackBuild are attached. >> >> Thanks for the SlackBuilds Andrej ! >> >> -- kjh >> > > I'll push an update soon enough. > Thanks for letting me know. > > -- > Best regards, > Andrzej Telszewski > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rsamurti at gmail.com Wed Nov 22 17:52:44 2017 From: rsamurti at gmail.com (Ananda Murthy R S) Date: Wed, 22 Nov 2017 23:22:44 +0530 Subject: [Slackbuilds-users] How to build .txz package without editing .SlackBuild file. In-Reply-To: References: <26684b49-e813-0ba2-8a51-757985e1d61d@gmail.com> Message-ID: Hello, Thank you all for your suggestions. Anand On Wed, Nov 22, 2017 at 5:52 PM, Willy Sudiarto Raharjo < willysr at 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 > editing > >>> the .SlackBuild file by passing parameter to the buildscript to create > a > >>> .txz file? > >> Export PKGTYPE=txz to the SlackBuild script. > >> > > Examples: > > PKGTYPE=txz ./yourprogram.SlackBuild > > PKGTYPE=txz sboinstall desired_program > > PKGTYPE=txz sboupgrade upgradable_programs > > Even better, export it in your .bashrc or in your /etc/profile for > global settings > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > 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/ > > > -- Close Windows ! Open source !! Free software from proprietary mafia !!! -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Wed Nov 22 14:31:59 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 22 Nov 2017 06:31:59 -0800 (PST) Subject: [Slackbuilds-users] openDKIM questions Message-ID: I tried to directly contact Gerado Zamudio, the opendkim package maintainer, but the message bounced: : host smtp2.linuxfoundation.org[140.211.169.14] said: 550 5.1.1 : Recipient address rejected: User unknown in virtual alias table (in reply to RCPT TO command) I have not been able to access the web page for the opendkim.org mail list and I'm trying to find a mail list or web forum where I can get help. If anyone here has suggestions, please let me know. Regards, Rich From didier at slint.fr Wed Nov 22 20:24:20 2017 From: didier at slint.fr (Didier Spaier) Date: Wed, 22 Nov 2017 21:24:20 +0100 Subject: [Slackbuilds-users] openDKIM questions In-Reply-To: References: Message-ID: <8597c555-4b62-de68-322e-cf01902cc377@slint.fr> @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 package > maintainer, but the message bounced: > > : host smtp2.linuxfoundation.org[140.211.169.14] > ??? said: 550 5.1.1 : Recipient address rejected: > ??? User unknown in virtual alias table (in reply to RCPT TO command) > > ? I have not been able to access the web page for the opendkim.org mail > list and I'm trying to find a mail list or web forum where I can get help. > If anyone here has suggestions, please let me know. > > Regards, > > Rich > > _______________________________________________ > 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 audrius at neutrino.lt Wed Nov 22 20:46:41 2017 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Wed, 22 Nov 2017 22:46:41 +0200 Subject: [Slackbuilds-users] openDKIM questions In-Reply-To: References: Message-ID: <20171122204641.GA2325@varna> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: not available URL: From rshepard at appl-ecosys.com Wed Nov 22 20:59:16 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 22 Nov 2017 12:59:16 -0800 (PST) Subject: [Slackbuilds-users] openDKIM questions In-Reply-To: <8597c555-4b62-de68-322e-cf01902cc377@slint.fr> References: <8597c555-4b62-de68-322e-cf01902cc377@slint.fr> Message-ID: 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 From rshepard at appl-ecosys.com Wed Nov 22 21:00:15 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 22 Nov 2017 13:00:15 -0800 (PST) Subject: [Slackbuilds-users] openDKIM questions In-Reply-To: <20171122204641.GA2325@varna> References: <20171122204641.GA2325@varna> Message-ID: 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 From gerardo.zamudio at linux.com Wed Nov 22 21:05:51 2017 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Wed, 22 Nov 2017 16:05:51 -0500 Subject: [Slackbuilds-users] openDKIM questions In-Reply-To: <8597c555-4b62-de68-322e-cf01902cc377@slint.fr> References: <8597c555-4b62-de68-322e-cf01902cc377@slint.fr> Message-ID: <434293c0-6c41-869c-571f-5442db7e630b@linux.com> 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 Shepard a ?crit?: >> ? I have not been able to access the web page for the opendkim.org mail >> list and I'm trying to find a mail list or web forum where I can get help. >> If anyone here has suggestions, please let me know. >> > The mail list is down at the moment. No idea when it'll be back. You can submit bug reports at SourceForge[1]. Message me privately and I can probably offer some assistance. I would recommend waiting for the list to be back or submitting a bug report. This list is for SlackBuild packaging issues. Assistance with using the software should be handled through an appropriate channel. Regards, Gerardo Zamudio [1]https://sourceforge.net/p/opendkim/_list/tickets -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Wed Nov 22 21:27:34 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 22 Nov 2017 13:27:34 -0800 (PST) Subject: [Slackbuilds-users] openDKIM questions In-Reply-To: <434293c0-6c41-869c-571f-5442db7e630b@linux.com> References: <8597c555-4b62-de68-322e-cf01902cc377@slint.fr> <434293c0-6c41-869c-571f-5442db7e630b@linux.com> Message-ID: 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 10 November. I don't think there's a bug in the software. I think it's in /etc/opendkim.conf and the files in /etc/opendkim/ subdirectories. > Message me privately and I can probably offer some assistance. Did so just now. > I would recommend waiting for the list to be back or submitting a bug > report. This list is for SlackBuild packaging issues. Assistance with > using the software should be handled through an appropriate channel. I don't expect help from the SBo mail list and my message to it pointed out the type I kept not seeing. Regards, Rich From rshepard at appl-ecosys.com Fri Nov 24 21:08:02 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 24 Nov 2017 13:08:02 -0800 (PST) Subject: [Slackbuilds-users] TexLive: beamer class Message-ID: Installed here are texlive-2017.170622-i586-1_SBo, texlive-extra-2017.170622-i586-2_SBo, and texlive-fonts-2017.170622-noarch-1_SBo. In /usr/share/texmf/tex/latex/beamer/ is an old version (3.01) from 2004. I just downloaded the latest release (3.44) from CTAN and the user guide's installation section includes, "In TEX Live, use the tlmgr tool to install the packages called beamer, pgf, and xcolor. If you have a fairly recent version of TEX Live, and you have done full installation, beamer is included." Is the included beamer in a different directory? Rich From rshepard at appl-ecosys.com Fri Nov 24 21:14:11 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 24 Nov 2017 13:14:11 -0800 (PST) Subject: [Slackbuilds-users] TexLive: beamer class [UPDATE] In-Reply-To: References: Message-ID: On Fri, 24 Nov 2017, Rich Shepard wrote: > In /usr/share/texmf/tex/latex/beamer/ is an old version (3.01) from 2004. > I just downloaded the latest release (3.44) from CTAN and the user guide's > installation section includes, "In TEX Live, use the tlmgr tool to install > the packages called beamer, pgf, and xcolor. If you have a fairly recent > version of TEX Live, and you have done full installation, beamer is > included." OK. Found that there are newer versions of all packages in /usr/share/texmf-dist/tex/latex/. I suppose that I need to remove the /usr/share/texmf/tex/latex/ subdirectories. Is this correct? Rich From didier at slint.fr Fri Nov 24 21:30:36 2017 From: didier at slint.fr (Didier Spaier) Date: Fri, 24 Nov 2017 22:30:36 +0100 Subject: [Slackbuilds-users] TexLive: beamer class In-Reply-To: References: Message-ID: <92be2113-a6ff-f01f-a0a8-966ca29b22a7@slint.fr> I wrongly only answered to Rich, sorry. Le 24/11/2017 ? 22:20, Didier Spaier a ?crit?: > Hello, > > Le 24/11/2017 ? 22:08, Rich Shepard a ?crit?: >> ? Installed here are texlive-2017.170622-i586-1_SBo, >> texlive-extra-2017.170622-i586-2_SBo, and >> texlive-fonts-2017.170622-noarch-1_SBo. >> >> ? In /usr/share/texmf/tex/latex/beamer/ is an old version (3.01) from 2004. >> I just downloaded the latest release (3.44) from CTAN and the user guide's >> installation section includes, "In TEX Live, use the tlmgr tool to install >> the packages called beamer, pgf, and xcolor. If you have a fairly recent >> version of TEX Live, and you have done full installation, beamer is >> included." >> >> ? Is the included beamer in a different directory? > > I don't know but in https://slackbuilds.org/repository/14.2/office/texlive/ > it is said: > >> Note that this package conflicts with the tetex packages in Slackware, >> so you'll need to remove tetex and tetex-doc before installing TeXLive. > > You did that, didn't you? > From didier at slint.fr Fri Nov 24 21:30:59 2017 From: didier at slint.fr (Didier Spaier) Date: Fri, 24 Nov 2017 22:30:59 +0100 Subject: [Slackbuilds-users] Fwd: Re: TexLive: beamer class [UPDATE] In-Reply-To: <7ddbdf35-4649-acfb-d27b-77794bb39dac@slint.fr> References: <7ddbdf35-4649-acfb-d27b-77794bb39dac@slint.fr> Message-ID: <2974b41b-d369-bb85-76d5-44213f0e2b5a@slint.fr> I wrongly only answered to Rich, sorry. -------- Message transf?r? -------- Sujet?: Re: [Slackbuilds-users] TexLive: beamer class [UPDATE] Date?: Fri, 24 Nov 2017 22:25:40 +0100 De?: Didier Spaier Pour?: Rich Shepard Le 24/11/2017 ? 22:14, Rich Shepard a ?crit?: > On Fri, 24 Nov 2017, Rich Shepard wrote: > >> ?In /usr/share/texmf/tex/latex/beamer/ is an old version (3.01) from 2004. >> I just downloaded the latest release (3.44) from CTAN and the user guide's >> installation section includes, "In TEX Live, use the tlmgr tool to install >> the packages called beamer, pgf, and xcolor. If you have a fairly recent >> version of TEX Live, and you have done full installation, beamer is >> included." > > ? OK. Found that there are newer versions of all packages in > /usr/share/texmf-dist/tex/latex/. I suppose that I need to remove the > /usr/share/texmf/tex/latex/ subdirectories. Is this correct? You should remove *everything* from your previous installation. I just hope that you had installed it as a regular Slackware package. using installpkg, so you can use removepkg to remove the old stuff. Also, you should have made this removal *before* installing texlive. If you didn't, remove everything then reinstall texlive. From rshepard at appl-ecosys.com Fri Nov 24 21:36:08 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 24 Nov 2017 13:36:08 -0800 (PST) Subject: [Slackbuilds-users] TexLive: beamer class Message-ID: On Fri, 24 Nov 2017, Didier Spaier wrote: > I don't know but in https://slackbuilds.org/repository/14.2/office/texlive/ > it is said: > >> Note that this package conflicts with the tetex packages in Slackware, >> so you'll need to remove tetex and tetex-doc before installing TeXLive. > > You did that, didn't you? Didier, I removed tetex years ago when Slackware replaced it with TeXLive. I think (as I just posted on Trac) that I need to remove the entire /usr/share/texmf/ directory tree because texhash works only on /usr/share/texmf-config/, /usr/share/texmf-dist/, /usr/share/texmf-local/, /and /usr/share/texmf-var/. I can do this and restore from a backup if necessary. Thanks, Rich From rshepard at appl-ecosys.com Fri Nov 24 21:46:38 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 24 Nov 2017 13:46:38 -0800 (PST) Subject: [Slackbuilds-users] TexLive: beamer class [RESOLVED] In-Reply-To: References: Message-ID: On Fri, 24 Nov 2017, Rich Shepard wrote: > I can do this and restore from a backup if necessary. I removed /usr/share/texmf/ and left ../../texmf-config/, ../../texmf-dist/, ../../texmf-local/, and ../../texmf-var/. Copied the latest beamer version to ../../texmf-dist/tex/latex/beamer/. Rich From johannes at schoepfer.info Fri Nov 24 22:11:03 2017 From: johannes at schoepfer.info (johannes at schoepfer.info) Date: Fri, 24 Nov 2017 23:11:03 +0100 Subject: [Slackbuilds-users] TexLive: beamer class In-Reply-To: References: Message-ID: Hi Rich, >> I don't know but in >> https://slackbuilds.org/repository/14.2/office/texlive/ >> it is said: >> >>> Note that this package conflicts with the tetex packages in >>> Slackware, >>> so you'll need to remove tetex and tetex-doc before installing >>> TeXLive. >> >> You did that, didn't you? > > Didier, > > I removed tetex years ago when Slackware replaced it with TeXLive. I dont't really understand, you mean years ago when robby added texlive to SBo? If you have /usr/share/texmf/ in your system, it looks like tetex is installed. You mentioned your beamer class is from 2004, that would also match. > I think > (as I just posted on Trac) that I need to remove the entire > /usr/share/texmf/ directory tree because texhash works only on > /usr/share/texmf-config/, /usr/share/texmf-dist/, > /usr/share/texmf-local/, > /and /usr/share/texmf-var/. Yes, like Didier said, remove all (te)tex(live) packages, and leftovers /usr/share/texmf-{config,var,local}, and also ~/.tex* and ~/texmf if present. Logout/Login as you still might have tetex env variables from /etc/profile.d. Install texlive from SBo, it might be sufficient to not install texlive-extra/fonts. btw. texhash is a link to mktexlsr, but that's already covered by the package's doinst.sh, that should be all. Johannes From johannes at schoepfer.info Fri Nov 24 22:32:24 2017 From: johannes at schoepfer.info (johannes at schoepfer.info) Date: Fri, 24 Nov 2017 23:32:24 +0100 Subject: [Slackbuilds-users] TexLive: beamer class [RESOLVED] In-Reply-To: References: Message-ID: <832ef927fb03b29cbfe47bb38ba83582@schoepfer.info> > ../../texmf-dist/, ../../texmf-local/, and ../../texmf-var/. Copied the > latest beamer version to ../../texmf-dist/tex/latex/beamer/. The recommended and most easy way would have been to simply update to the newest texlive from SBo. Is beamer coming with texlive really too old([2017/08/22 v3.43)? If you update texlive, it will be overridden again. If you really want a special beamer version, put it in TEXMFHOME kpsewhich -var-value TEXMFHOME Johannes From rshepard at appl-ecosys.com Fri Nov 24 23:15:32 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 24 Nov 2017 15:15:32 -0800 (PST) Subject: [Slackbuilds-users] TexLive: beamer class [RESOLVED] In-Reply-To: <832ef927fb03b29cbfe47bb38ba83582@schoepfer.info> References: <832ef927fb03b29cbfe47bb38ba83582@schoepfer.info> Message-ID: On Fri, 24 Nov 2017, johannes at schoepfer.info wrote: > The recommended and most easy way would have been to simply update to the > newest texlive from SBo. Johannes, Earlier this week I checked and saw that my 170622 version was shown as the current one. Now I see there's a 171108. I'll upgrade all packages tomorrow morning. > Is beamer coming with texlive really too old([2017/08/22 v3.43)? No. I had version 3.01 installed in texmf/. That directory has been removed. I downloaded 3.44; the differences between it and 3.43 are probably minor. > If you update texlive, it will be overridden again. If you really want a > special beamer version, put it in TEXMFHOME > > kpsewhich -var-value TEXMFHOME I assume that REXMFHOME is a directory in ~/ that's exported from ~/.bash_profile. Thanks, Rich From rshepard at appl-ecosys.com Fri Nov 24 23:25:45 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 24 Nov 2017 15:25:45 -0800 (PST) Subject: [Slackbuilds-users] TexLive: beamer class In-Reply-To: References: Message-ID: On Fri, 24 Nov 2017, johannes at schoepfer.info wrote: > I dont't really understand, you mean years ago when robby added texlive to > SBo? Johannes, Yes. > If you have /usr/share/texmf/ in your system, it looks like tetex is > installed. You mentioned your beamer class is from 2004, that would also > match. There's no installed package by that name, and the only files with that name are in: # find / -name tetex /usr/share/texmf-dist/dvips/tetex /usr/share/texmf-dist/fonts/enc/dvips/tetex /usr/share/texmf-dist/fonts/map/dvips/tetex Which will go away when I remove all TeX-related files and install the 2017.171108 release. Best regards, Rich From willysr at slackbuilds.org Fri Nov 24 23:27:45 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 25 Nov 2017 06:27:45 +0700 Subject: [Slackbuilds-users] Updates - 20171124.1 Message-ID: <8cffc9cf-dfd1-c7b2-aa43-da9b9f0bc915@slackbuilds.org> This could be our last update in November and one hour before my regular release schedule to avoid last-minute submission. the old skype is now officially removed from the repository after the extended period is now over for real. Please use skypeforlinux as the official application for skype. I removed skype4pidgin as well as it has no maintainer and also depends on skype. This removal wasn't recorded in the commit log yet but i will add it on my branch after this. Fri Nov 24 23:11:32 UTC 2017 academic/ngspice: Updated for version 27. desktop/faba-icon-theme: Updated for version 20170712. desktop/faba-mono-icons: Updated for version 20160430. desktop/paper-icon-theme: Updated for version 20171120. development/apitrace: Updated for version 2017.11.20_19c33cb. development/hhvm: Updated for version 3.23.2 development/jupyter-ipywidgets: Updated for version 7.0.5. development/openjdk8: Updated for version 8u151b12. development/openjdk: Updated for version 7u151b01. development/rust: Updated for version 1.22.1. development/universal-ctags: Updated for version 157918c games/RetroArch: Updated for version 1.6.9. ham/flrig: Added (Amateur Radio transceiver control program). haskell/hscolour: Updated for version 1.24.2 libraries/libuv: Updated for version 1.17.0. multimedia/opencaster: Added (MPEG-TS stream tool). multimedia/opera-developer-ffmpeg-codecs: Updated for v 64.0.3260.2. multimedia/vivaldi-codecs-ffmpeg-extra: Updated for version 62.0. network/WireGuard: Updated for version 0.0.20171122. network/cyrus-imapd: Updated for version 2.5.11. network/dovecot-pigeonhole: Updated for version 0.4.21. network/dovecot: Updated for version 2.2.33.2. network/imapfilter: Updated for version 2.6.11. network/iptv-analyzer: Added (IPTV MPEG2 Transport Stream Analyzer). network/opera-developer: Updated for version 51.0.2781.0. network/postfix: Updated for version 3.2.4. network/quagga: Updated for version 1.2.2. network/skype: Removed (replaced by skypeforlinux). network/skypeforlinux: Updated for version 8.11.76.8. network/slimjet: Updated for version 16.0.8.0. network/tor-browser: Updated for version 7.0.10. network/transgui: Updated for version 5.11.0. network/urlwatch: Fixed md5sum. network/vivaldi: Updated for version 1.13.1008.32. network/yle-dl: Updated for version 2.28. office/osmo: Updated for version 0.4.2. perl/perl-Geo-Coordinates-OSGB: Updated for version 2.20. perl/perl-Moo: Updated for version 2.003003. perl/perl-Params-ValidationCompiler: Updated for version 0.25. python/python-fonttools: Updated for version 3.20.1. python/pywal: Added (generate and change colorschemes on the fly). python/txtorcon: Updated for version 0.19.3. ruby/rubygem-pry: Fixed md5sum. system/alacritty: Updated for version git8ff3c5d. system/fd: Updated for version 6.0.0. system/fish: Updated for version 2.7.0. system/intel-microcode: Updated for version 20171117. system/ksh-openbsd: Updated for version 20171122. system/pspg: Updated for version 0.6. system/rar2fs: Updated for version 1.26.0. system/vtcol: Silenced deprecation in newer rust versions. system/wine-staging: Updated for version 2.21. system/xen: Updated for version 4.9.1. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From ts at websafe.pl Sat Nov 25 19:57:45 2017 From: ts at websafe.pl (Thomas Szteliga) Date: Sat, 25 Nov 2017 20:57:45 +0100 Subject: [Slackbuilds-users] runc: C source files not allowed when not using cgo: gccgo_c.c Message-ID: Hello, I'm trying to build docker, but the following error occurs when building runc, which is a docker dependency: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ runc-3f2f8b84a77f73d38244dd690525642a72156c64/vendor/golang.org/x/sys/unix/ztypes_openbsd_amd64.go runc-3f2f8b84a77f73d38244dd690525642a72156c64/vendor/golang.org/x/sys/unix/ztypes_solaris_amd64.go go build -i -ldflags "-X main.gitCommit=3f2f8b84a77f73d38244dd690525642a72156c64 -X main.version=1.0.0-rc4+dev " -tags "secc omp" -o runc . build/src/github.com/opencontainers/runc/libcontainer/configs/namespaces_syscall.go:5:8: C source files not allowed when not using cgo: gccgo_c.c Makefile:28: recipe for target 'runc' failed make: *** [runc] Error 1 Total build time for package runc : 1.09 Sec +============================================================================== | Some error on the package runc-1.0.0_rc4_3f2f8b8 [ FAILED ] +============================================================================== | See log file in '/var/log/slpkg/sbo/build_logs' directory or read README +============================================================================== ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /var/log/slpkg/sbo/build_logs/build_runc_log ends in: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ runc-3f2f8b84a77f73d38244dd690525642a72156c64/vendor/golang.org/x/sys/unix/ztypes_openbsd_amd64.go runc-3f2f8b84a77f73d38244dd690525642a72156c64/vendor/golang.org/x/sys/unix/ztypes_solaris_amd64.go go build -i -ldflags "-X main.gitCommit=3f2f8b84a77f73d38244dd690525642a72156c64 -X main.version=1.0.0-rc4+dev " -tags "seccomp" -o runc . build/src/github.com/opencontainers/runc/libcontainer/configs/namespaces_syscall.go:5:8: C source files not allowed when not using cgo: gccgo_c.c Makefile:28: recipe for target 'runc' failed make: *** [runc] Error 1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Any idea how to solve this problem? -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3719 bytes Desc: Kryptograficzna sygnatura S/MIME URL: From matteo.bernardini at gmail.com Sat Nov 25 20:03:41 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 25 Nov 2017 21:03:41 +0100 Subject: [Slackbuilds-users] runc: C source files not allowed when not using cgo: gccgo_c.c In-Reply-To: References: Message-ID: Hi Thomas, when you have installed google-go-lang you must log out, relogin again, and only after that build the rest of the dependencies of docker. Matteo From rshepard at appl-ecosys.com Sat Nov 25 20:36:15 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 25 Nov 2017 12:36:15 -0800 (PST) Subject: [Slackbuilds-users] TexLive: beamer class In-Reply-To: References: Message-ID: On Fri, 24 Nov 2017, Rich Shepard wrote: > Which will go away when I remove all TeX-related files and install the > 2017.171108 release. Done. Does not resolve the LyX beamer presentation issue, though. Will use straight LaTeX on the presentation. Thanks, Rich From ts at websafe.pl Sat Nov 25 21:36:50 2017 From: ts at websafe.pl (Thomas Szteliga) Date: Sat, 25 Nov 2017 22:36:50 +0100 Subject: [Slackbuilds-users] runc: C source files not allowed when not using cgo: gccgo_c.c In-Reply-To: References: Message-ID: <15ba4465-0034-00fa-2842-ffea482a129a@websafe.pl> W dniu 25/11/2017 o?21:03, Matteo Bernardini pisze: > when you have installed google-go-lang you must log out, relogin > again, and only after that build the rest of the dependencies of > docker. Hello Matteo, thank you for this tip. Running . /etc/profile.d/go.sh before slpg -s sbo runc solved my problem. BTW, shouldn't this be addressed in the google-go-lang.SlackBuild? -- Thomas Szteliga From matteo.bernardini at gmail.com Sat Nov 25 22:06:27 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 25 Nov 2017 23:06:27 +0100 Subject: [Slackbuilds-users] runc: C source files not allowed when not using cgo: gccgo_c.c In-Reply-To: <15ba4465-0034-00fa-2842-ffea482a129a@websafe.pl> References: <15ba4465-0034-00fa-2842-ffea482a129a@websafe.pl> Message-ID: 2017-11-25 22:36 GMT+01:00 Thomas Szteliga : > BTW, shouldn't this be addressed in the google-go-lang.SlackBuild? quoting from the README: "The tools are added to the path by putting go.sh and go.csh files in /etc/profile.d and letting the system's /etc/profile or /etc/csh.login pick it up." IMHO, it looks clear enough already... Matteo From thomas at beingboiled.info Sun Nov 26 01:52:23 2017 From: thomas at beingboiled.info (Thomas Morper) Date: Sun, 26 Nov 2017 02:52:23 +0100 (CET) Subject: [Slackbuilds-users] Exim remote code execution Message-ID: Hello there, A remote code execution vulnerability has been reported in Exim. If you're running Exim, disable the ESMTP CHUNKING extension by putting... chunking_advertise_hosts = ...into the main section of your exim.conf. This should do as a workaround until a proper fix is available. https://marc.info/?l=exim-announce&m=151158351116562&w=2 -- From alik at ejik.org Tue Nov 28 20:49:59 2017 From: alik at ejik.org (Alexander Verbovetsky) Date: Tue, 28 Nov 2017 23:49:59 +0300 Subject: [Slackbuilds-users] Updates - 20171124.1 In-Reply-To: <8cffc9cf-dfd1-c7b2-aa43-da9b9f0bc915@slackbuilds.org> References: <8cffc9cf-dfd1-c7b2-aa43-da9b9f0bc915@slackbuilds.org> Message-ID: <1511902199.3031534.1187305408.6F8A6850@webmail.messagingengine.com> Hello, > network/skypeforlinux: Updated for version 8.11.76.8. This looks like an _unstable_ version of skype. Stable versions are listed in https://repo.skype.com/deb/dists/stable/main/binary-amd64/Packages The latest one is 8.11.0.4. Downloading skype via https://www.skype.com/en/get-skype/ also gives 8.11.0.4. Best regards, Alexander From mario at slackware.hr Wed Nov 29 10:41:59 2017 From: mario at slackware.hr (Mario) Date: Wed, 29 Nov 2017 11:41:59 +0100 Subject: [Slackbuilds-users] Updates - 20171124.1 In-Reply-To: <1511902199.3031534.1187305408.6F8A6850@webmail.messagingengine.com> References: <8cffc9cf-dfd1-c7b2-aa43-da9b9f0bc915@slackbuilds.org> <1511902199.3031534.1187305408.6F8A6850@webmail.messagingengine.com> Message-ID: Hi, >> network/skypeforlinux: Updated for version 8.11.76.8. > This looks like an _unstable_ version of skype. Thanks, I have also received direct messages about this one. The "update" can be found in my branch ;-) Regards, -- Mario From ml at mareichelt.com Thu Nov 30 16:00:45 2017 From: ml at mareichelt.com (Markus Reichelt) Date: Thu, 30 Nov 2017 17:00:45 +0100 Subject: [Slackbuilds-users] How to build .txz package without editing .SlackBuild file. In-Reply-To: References: Message-ID: <20171130160045.GB2641@pc21.mareichelt.com> * Ananda Murthy R S wrote: > 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? also, you might want to consider exporting XZ_DEFAULTS="-T 0", especially when you are building large packages on a multicore system. HTH -- I wouldn't leave the house without Tahoe-LAFS.