Re: [Slackbuilds-users] A few scripts up for grab.
On 9/28/18, Arnaud wrote: > games/lightyears: up-to-date, last upstream update 2011/09/27 > games/tuxkart : up-to-date, last upstream update unknown but >5 years > games/pysolfc : SBo version 2.0, upstream version 2.4.0 I'll take these 3, if nobody's already claimed them. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] A few scripts up for grab.
On 28.09.18,18:40, Arnaud wrote: > Hello, > > Following the previous messages about warzone2100, I contacted both > Matthew and David Fillpot. Matthew answered for them both, and agrees to put > all > of their scripts up for grabs, I quote : > > Yes, please notify the mailing list that the scripts for both maintainers > > are up for grabs. > Though he is also ok to resume his work as maintainer, in about a > month, for anything that remains. It seems he has a bit more time at the > moment. > So those scripts doesn't require a new maintainer, but if you want to > take care of them, they are available ! > > Most of their scripts are for abandonwares, here they are, classified by > maintenance level : > * Nothing to do, mostly abandoned projects > academic/mathomatic : up-to-date, last upstream update 2012/10/30 > desktop/kcometen4 : up-to-date, last upstream update 2010/07/30 > system/freefont : up-to-date, last upstream update 2012/05/03 > games/lightyears: up-to-date, last upstream update 2011/09/27 > games/tuxkart : up-to-date, last upstream update unknown but >5 years > old > libraries/GLee : up-to-date, last upstream update unknown but >5 years > old > libraries/quesoglc : up-to-date, last upstream update 2013/08/23 > * active projects but SBo package is 5 years old > academic/gpredict : SBo version 1.3, upstream version 2.2.1 > network/axel : Sbo version 2.4, upstream version 2.16.1 > graphics/qrencode : Sbo version 3.4.0, upstream version 4.0.2 > games/pysolfc : SBo version 2.0, upstream version 2.4.0 > system/yakuake: SBo version 2.9.9, upstream version 3.0.5 > > And I'm ok taking ownership of warzone2100, having already done the > update work on it. > I can take the axel SlackBuild. Jostein ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Error building OpenBLAS
On Wed, 3 Oct 2018, Didier Spaier wrote: No problem. For your information clicking on: https://github.com/xianyi/OpenBLAS/ displays a page where you see under the description a line including (at time of writing): 39 releases This is a link and clicking on it displays a page where you will find links to compressed archives of the source code for each release. A lot of projects on GitHub provides that. Didier, Thanks for this knowledge. I did not explore that link but looked at the list of files for the tarball. Best regards, Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Error building OpenBLAS
On Wed, 3 Oct 2018, Didier Spaier wrote: Yes, you missed to read OpenBLAS.info that you downloaded, which provides a link to the source tarball like this: DOWNLOAD="https://github.com/xianyi/OpenBLAS/archive/v0.3.3/OpenBLAS-0.3.3.tar.gz"; I just checked the link, it is correct. Didier, Downloaded the tarball and tried building it. The error reported is: Makefile:135: *** OpenBLAS: Detecting CPU failed. Please set TARGET explicitly, e.g. make TARGET=your_cpu_target. Please read README for the detail.. Stop. README: OpenBLAS is an optimized BLAS library based on GotoBLAS2 1.13 BSD version. Added symbolic link to install a generic blas library that can be used by Octave and R. In OpenBLAS.SlackBuild the target looks at uname -m which here reports the processor type as x86_64. That target is not explicit in the build file, but I assume it's accepted in the last choice after i?586 and arm*. Should I add a target of x86_64 to the build script? Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Error building OpenBLAS
On 10/3/18 12:48 AM, Rich Shepard wrote: > On Wed, 3 Oct 2018, Didier Spaier wrote: > >> Yes, you missed to read OpenBLAS.info that you downloaded, which >> provides a link to the source tarball like this: >> DOWNLOAD="https://github.com/xianyi/OpenBLAS/archive/v0.3.3/OpenBLAS-0.3.3.tar.gz"; >> >> I just checked the link, it is correct. > > Didier, > > My apologies for not reading the .info file. I'll do this now. > > Rich No problem. For your information clicking on: https://github.com/xianyi/OpenBLAS/ displays a page where you see under the description a line including (at time of writing): 39 releases This is a link and clicking on it displays a page where you will find links to compressed archives of the source code for each release. A lot of projects on GitHub provides that. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Error building OpenBLAS
On Wed, 3 Oct 2018, Didier Spaier wrote: Yes, you missed to read OpenBLAS.info that you downloaded, which provides a link to the source tarball like this: DOWNLOAD="https://github.com/xianyi/OpenBLAS/archive/v0.3.3/OpenBLAS-0.3.3.tar.gz"; I just checked the link, it is correct. Didier, My apologies for not reading the .info file. I'll do this now. Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Error building OpenBLAS
On 10/2/18 11:56 PM, Rich Shepard wrote: > On Tue, 2 Oct 2018, David Spencer wrote: > >> But fortunately Mario has just updated OpenBLAS and the new version will >> be in the next public update :D >> >> Or (if you don't want to wait) you can grab the new version from here: >> https://git.slackbuilds.org/slackbuilds/tree/libraries/OpenBLAS?h=idlemoor&id=3eb342a21265826a61a9128906ab601565baec57 > > Dave/Mario: > > I downloaded the SlackBuild, info, desc, and README files. The build > script is looking for version 0.3.3 while the SBo repo has version 0.2.20. > > The home page on github has all the development branch files and I did not > see an 0.3.3 tarball. Did I miss it there? Yes, you missed to read OpenBLAS.info that you downloaded, which provides a link to the source tarball like this: DOWNLOAD="https://github.com/xianyi/OpenBLAS/archive/v0.3.3/OpenBLAS-0.3.3.tar.gz"; I just checked the link, it is correct. Didier ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Error building OpenBLAS
On Tue, 2 Oct 2018, David Spencer wrote: But fortunately Mario has just updated OpenBLAS and the new version will be in the next public update :D Or (if you don't want to wait) you can grab the new version from here: https://git.slackbuilds.org/slackbuilds/tree/libraries/OpenBLAS?h=idlemoor&id=3eb342a21265826a61a9128906ab601565baec57 Dave/Mario: I downloaded the SlackBuild, info, desc, and README files. The build script is looking for version 0.3.3 while the SBo repo has version 0.2.20. The home page on github has all the development branch files and I did not see an 0.3.3 tarball. Did I miss it there? Regards, Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] request to remove package: newlib-headers.
i would like to remove this package: https://slackbuilds.org/repository/14.2/development/newlib-headers/ -- Regards, Fernando Lopez Jr. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Error building OpenBLAS
On Tue, 2 Oct 2018, David Spencer wrote: I've had the same error in build testing recently and I don't know why Dave, Interesting. I hit this wall on a clean 14.2 on a brand new system. But fortunately Mario has just updated OpenBLAS and the new version will be in the next public update :D Or (if you don't want to wait) you can grab the new version from here: https://git.slackbuilds.org/slackbuilds/tree/libraries/OpenBLAS?h=idlemoor&id=3eb342a21265826a61a9128906ab601565baec57 I need this library to build GRASS, and I need GRASS to run a spatial interpolation model that runs out of room on the current desktop. Thanks! Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] several builds crashing looking for old libwebp
Il giorno mar 2 ott 2018 alle ore 12:36 David Melik ha scritto: > > On 10/2/18 2:35 AM, Matteo Bernardini wrote: > > Il giorno mar 2 ott 2018 alle ore 11:19 David Melik > > ha scritto: > >> NotepadQQ and KVIRC (though newly compiled) both immediately crash for > >> not finding libwebp.so.6. Well, that file is now at libwebp.so.7.0.2. > >> King Beowulf told me (when I finally had to upgrade libwebp for BOINC > >> instead of keeping an old one) this behaviour means libwebp is a runtime > >> dependency (the SlackBuild maintainers must become aware of) and to link > >> libwebp.so.6 to libwebp (which of course itself is a link to the > >> 7.0.2.) I did that, then both worked. Previously the NotepadQQ > >> maintainer said recompile/upgrade libwebp, then NotepadQQ... same thing > >> happened. Well, the problem appears to be poor source code in both > >> NotepadQQ and KVIRC (most likely) and/or SlackBuilds done wrong... or > >> maybe the libwebp maintainer should become aware that some programs try > >> to use a specific old version for some reason, and make a link in the > >> SlackBuild. > > if you upgrade a library to a newer major release with a shared > > library version bump, like in your case, you should also rebuild > > whatever links against it: I suspect the error you got is because you > > have to rebuild qt5 and qt5-webkit (that you built against the old > > libwebp in the first place). > > Okay; I had done that also but maybe in the wrong order... it's not > clear again what built 'against' means rather than built 'from' (or > 'depending on')... if qt5 and qt5-webkit depends on libwebp you should build first libwebp and then qt5 and then qt5-webkit (that depends on qt5), this is necessary for a program/library using a dependency to link to it at build-time. I wrote "built against it" meaning "built linking to it", both forms are often used on this mailing list, irc or the LQ forum. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] several builds crashing looking for old libwebp
On 10/2/18 2:35 AM, Matteo Bernardini wrote: Il giorno mar 2 ott 2018 alle ore 11:19 David Melik ha scritto: NotepadQQ and KVIRC (though newly compiled) both immediately crash for not finding libwebp.so.6. Well, that file is now at libwebp.so.7.0.2. King Beowulf told me (when I finally had to upgrade libwebp for BOINC instead of keeping an old one) this behaviour means libwebp is a runtime dependency (the SlackBuild maintainers must become aware of) and to link libwebp.so.6 to libwebp (which of course itself is a link to the 7.0.2.) I did that, then both worked. Previously the NotepadQQ maintainer said recompile/upgrade libwebp, then NotepadQQ... same thing happened. Well, the problem appears to be poor source code in both NotepadQQ and KVIRC (most likely) and/or SlackBuilds done wrong... or maybe the libwebp maintainer should become aware that some programs try to use a specific old version for some reason, and make a link in the SlackBuild. if you upgrade a library to a newer major release with a shared library version bump, like in your case, you should also rebuild whatever links against it: I suspect the error you got is because you have to rebuild qt5 and qt5-webkit (that you built against the old libwebp in the first place). Okay; I had done that also but maybe in the wrong order... it's not clear again what built 'against' means rather than built 'from' (or 'depending on')... ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Error building OpenBLAS
> I'm building all my SBo packages on a newly minted desktop running > -14.2/x86_64. I downloaded from the repository the *.tar.gz and build > directory so all files are fresh. > > Running the SlackBuild script stops with this: > > gemv.c: In function ‘sgemv_’: > gemv.c:219:42: error: ‘GEMM_MULTITHREAD_THRESHOLD’ undeclared (first use > in this function) Hey Rich, I've had the same error in build testing recently and I don't know why But fortunately Mario has just updated OpenBLAS and the new version will be in the next public update :D Or (if you don't want to wait) you can grab the new version from here: https://git.slackbuilds.org/slackbuilds/tree/libraries/OpenBLAS?h=idlemoor&id=3eb342a21265826a61a9128906ab601565baec57 Cheers! and thanks to Mario for perfect timing! -D. signature.asc Description: OpenPGP digital signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] several builds crashing looking for old libwebp
On 10/2/18, David Melik wrote: > Well, the problem appears to be poor source code in both > NotepadQQ and KVIRC (most likely) and/or SlackBuilds done wrong. It means you upgraded libwebp, but didn't upgrade other library packages that depend on it. One of the libs in one of these packages was linked when building NotepadQQ and KVIRC... OK, a bit more investigation reveals that notepadqq and kvirc both require qt5-webkit. And qt5-webkit lists libwebp as an optional dependency, in its README. So what happened here is you built some version of libwebp, then built qt5-webkit afterwards... and then you (possibly months later) upgraded libwebp. But qt5-webkit was still trying to find the old libwebp, which is gone... In this situation, newly-compiled programs that link with qt5-webkit won't fail to compile or link... but they *will* fail at runtime in exactly the way you describe. It's a common problem when upgrading libraries: there's not an easy way to find out what *other* libraries depend on it and need to be upgraded. Especially when they're optional ones (not listed in REQUIRES in the .info file). Usually when I get bit by this, it's ffpmeg (because it just has *so* many deps, most of which are optional). Generally you can figure this kind of runtime linking problem out by using ldd... or, even better, get lddsafe from here: https://github.com/rg3/lddsafe ...and use its -n option, which shows only direct library dependencies... then use lddsafe -n on each of those libraries, until you hit a 'not found'. The other way to diagnose this would have been to look at the REQUIRES for both notepadqq and kvirc (which is what I did) and notice they both say qt5-webkit, and then find the shared libs in qt5-webkit and run regular ldd on them. You would have gotten a 'not found' for the old version of libwebp... The general solution is to rebuild the offending library (in this case, qt5-webkit). Or you can use sbopkg to check for updates to *all* your installed packages, and upgrade them all (takes longer, but you're less likely to run into problems like this). Hopefully the above has been helpful to you, and makes up for what you'll perceive as rudeness in the rest of the message. But I feel this must be said, so: It's not "poor source code" and it's not "SlackBuilds done wrong", and it's kinda rude of you to say that, considering you're lacking some fundamental knowledge that would qualify you to actually make that judgement. Your original post should probably have been a request for help, without trying to place the blame on anyone. In fact, the blame is on you, *your* system was in an inconsistent state. Hopefully I've helped you to fix it and learn how to diagnose and fix it on your own next time. Please try to take this as constructive criticism, not flaming. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] several builds crashing looking for old libwebp
Il giorno mar 2 ott 2018 alle ore 11:19 David Melik ha scritto: > > NotepadQQ and KVIRC (though newly compiled) both immediately crash for > not finding libwebp.so.6. Well, that file is now at libwebp.so.7.0.2. > King Beowulf told me (when I finally had to upgrade libwebp for BOINC > instead of keeping an old one) this behaviour means libwebp is a runtime > dependency (the SlackBuild maintainers must become aware of) and to link > libwebp.so.6 to libwebp (which of course itself is a link to the > 7.0.2.) I did that, then both worked. Previously the NotepadQQ > maintainer said recompile/upgrade libwebp, then NotepadQQ... same thing > happened. Well, the problem appears to be poor source code in both > NotepadQQ and KVIRC (most likely) and/or SlackBuilds done wrong... or > maybe the libwebp maintainer should become aware that some programs try > to use a specific old version for some reason, and make a link in the > SlackBuild. if you upgrade a library to a newer major release with a shared library version bump, like in your case, you should also rebuild whatever links against it: I suspect the error you got is because you have to rebuild qt5 and qt5-webkit (that you built against the old libwebp in the first place). ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] several builds crashing looking for old libwebp
NotepadQQ and KVIRC (though newly compiled) both immediately crash for not finding libwebp.so.6. Well, that file is now at libwebp.so.7.0.2. King Beowulf told me (when I finally had to upgrade libwebp for BOINC instead of keeping an old one) this behaviour means libwebp is a runtime dependency (the SlackBuild maintainers must become aware of) and to link libwebp.so.6 to libwebp (which of course itself is a link to the 7.0.2.) I did that, then both worked. Previously the NotepadQQ maintainer said recompile/upgrade libwebp, then NotepadQQ... same thing happened. Well, the problem appears to be poor source code in both NotepadQQ and KVIRC (most likely) and/or SlackBuilds done wrong... or maybe the libwebp maintainer should become aware that some programs try to use a specific old version for some reason, and make a link in the SlackBuild. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] several builds crashing looking for old libwebp
NotepadQQ and KVIRC (though newly compiled) both immediately crash for not finding libwebp.so.6. Well, that file is now at libwebp.so.7.0.2. King Beowulf told me this behaviour means libwebp is a runtime dependency (the SlackBuild maintainers should be aware of) and to link libwebp.so.6 to libwebp (which of course itself is a link to the 7.0.2.) I did that, then both worked. Previously the NotepadQQ maintainer said recompile/upgrade libwebp, then NotepadQQ... same thing happened. Well, the problem appears to be poor source code in both NotepadQQ and KVIRC (most likely) and/or SlackBuilds done wrong. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Strange problem with KeePass 2.39.1
W dniu 30/09/2018 o 12:55, Shrivats pisze: I pushed an update for version 2.40 and included KeePass.config.xml in this update. It's currently in pending queue and you can try it out once it's uploaded. OK, thank you, I will try it :-) -- Thomas Szteliga ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
