[Slackbuilds-users] What packages do you upgrade?
I noticed that there were some updates on some SBo packages I had already installed on my new Slackware 13.37 installation. Given some possible options that come to my mind, what would you consider as the best practice? 1. Ignore them unless there are some security issues. 2. Upgrade them and rebuild any packages that were built against them. 3. Upgrade them but do not bother with any other packages even if they were built against them. I tend to find the last option as the most sensible but I would appreciate your opinions. Chris ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] What packages do you upgrade?
2011/6/16 Chris ABELA chris.ab...@maltats.com: 3. Upgrade them but do not bother with any other packages even if they were I got for that all the time. -- Ozan, BSc, BEng ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] What packages do you upgrade?
2011/6/16 Ozan Türkyılmaz ozan.turkyil...@gmail.com: 2011/6/16 Chris ABELA chris.ab...@maltats.com: 3. Upgrade them but do not bother with any other packages even if they were I got for that all the time. -- Ozan, BSc, BEng Well, if you upgrade a library, you might need to rebuild the packages that depend on it. This all depends on how big the change is in the lib - and how upstream developers took care of that... For instance, if you upgrade libxyz for 1.2.1 to 1.2.2 and upstream maintained compatibility, everything will be OK. But a change from 1.2.1 to 2.0.0 sounds like a major upgrade, with a new version of the shared object and might intruduce compatibility problems. My personal experience: - read the changelog of the upgrades package from upstream to find out why they released the new version. If they are responsible persons, the warn about possible impacts. - run ldd your_program after the upgrade and check for errors - test your_program - especially the functionality handled by libxyz if possible. - try at least to build your_program and see if it complains about libxyz. If it does, you might even send an e-mail to your_program developers telling them what you found out, or check their forum, mailing list etc. There might be a patch in their source repo already. This is all a lot of fun, but it takes some time. :) -- Niels Horn ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Remove loic from pending please
Will someone from the Admins please remove my submission for loic. I made some significant enhancements I would like to include before your review. Unlike other submissions I had made before, I did not receive the mail with instructions on how to do this. Chris ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Opera Widgets
On Wed, 2011-06-15 at 22:46:23 +0200, markus reichelt wrote: Reason I'm asking: I do not use Opera Widgets myself, at all. The more input the better. Thanks :) I do not use Opera widgets either, so I guess this doesn't count as useful input. :-) What I do use are UserJS scripts. I find them very valuable. -- Audrius Kažukauskas pgp93A1FklVym.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] GoogleEarth Won't Start
Using the new SlackBuild script and a fresh copy of GoogleEarth...bin for 13.37/x86_64 I'm running into a puzzling problem when trying to invoke the application. What I see on the virtual terminal is: /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: no such file or directory /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: success Well! googleearth-bin _is_ in /opt/GoogleEarth. And I added the LD_LIBRARY_PATH shown in /usr/bin/googleearth, but all to no avail. What might I have done wrong here? Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] GoogleEarth Won't Start
On Thu, Jun 16, 2011 at 2:55 PM, Rich Shepard rshep...@appl-ecosys.comwrote: Using the new SlackBuild script and a fresh copy of GoogleEarth...bin for 13.37/x86_64 I'm running into a puzzling problem when trying to invoke the application. What I see on the virtual terminal is: /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: no such file or directory /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: success Well! googleearth-bin _is_ in /opt/GoogleEarth. And I added the LD_LIBRARY_PATH shown in /usr/bin/googleearth, but all to no avail. What might I have done wrong here? Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ Is /opt/GoogleEarth/googleearth-bin executable? --JK ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] GoogleEarth Won't Start
On Thu, 2011-06-16 at 12:55:41 -0700, Rich Shepard wrote: Using the new SlackBuild script and a fresh copy of GoogleEarth...bin for 13.37/x86_64 I'm running into a puzzling problem when trying to invoke the application. What I see on the virtual terminal is: /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: no such file or directory /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: success Well! googleearth-bin _is_ in /opt/GoogleEarth. And I added the LD_LIBRARY_PATH shown in /usr/bin/googleearth, but all to no avail. What might I have done wrong here? Are you trying to run it on Slackware64? From GoogleEarth SlackBuild README: 3) GoogleEarth is a 32bit application only. You need to have the 32bit compatibility packages installed to have this work on a 64bit system. Otherwise you'll just see no such file or directory errors. -- Audrius Kažukauskas pgpenjFQRk3HK.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] GoogleEarth Won't Start
On Thu, 16 Jun 2011, JK Wood wrote: Is /opt/GoogleEarth/googleearth-bin executable? JK, I should have mentioned that it is, with 755 permissions. Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] GoogleEarth Won't Start
On Thu, 16 Jun 2011, Audrius Ka?ukauskas wrote: Are you trying to run it on Slackware64? From GoogleEarth SlackBuild README: 3) GoogleEarth is a 32bit application only. You need to have the 32bit compatibility packages installed to have this work on a 64bit system. Otherwise you'll just see no such file or directory errors. I installed AlienBob's compatibility libraries. There must be something I did incorrectly, however, as I'm also finding a build problem with another SlackBuild package (another thread). Acroread would not install until I added the compat32 libs; it has font issues so I may have missed something here. Thanks, Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] epdfview Build Problem
Working with a 64-bit system is new to me so I'm hitting issues that I expect will go away with experience. I installed AlienBob's multilibs and compat32 libraries this morning and I'm trying to get every application I might need on the machine before I leave on a business trip this Sunday. The current problem is with epdview. Running the SlackBuild script produces: In file included from /usr/include/glib-2.0/glib/gasyncqueue.h:34:0, from /usr/include/glib-2.0/glib.h:34, from /usr/include/glib-2.0/gobject/gbinding.h:30, from /usr/include/glib-2.0/glib-object.h:25, from /usr/include/glib-2.0/gio/gioenums.h:30, from /usr/include/glib-2.0/gio/giotypes.h:30, from /usr/include/glib-2.0/gio/gio.h:28, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from FindView.cxx:21: /usr/include/glib-2.0/glib/gthread.h: In function 'gboolean g_once_init_enter olatile gsize*)': /usr/include/glib-2.0/glib/gthread.h:347:6: error: size of array is negative make[3]: *** [libshell_gtk_a-FindView.o] Error 1 make[3]: Leaving directory /tmp/SBo/epdfview-0.1.7/src/gtk' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory /tmp/SBo/epdfview-0.1.7/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory /tmp/SBo/epdfview-0.1.7' make: *** [all] Error 2 This, along with the GoogleEarth issue, suggests to me that either the multilib upgrades or the compat32 installations are incomplete. Yesterday I downloaded all 210M of the 13.37/ subdirectory and this morning followed the web page Quick Start instructions step-by-step. What's your recommendations to find and fix these problems? Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] GoogleEarth Won't Start
/usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: no such file or directory /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: success That's what happens if you haven't done what's in the SlackBuild's README, note 2: 2) Google Earth 6 is LSB compliant meaning it was built on a LSB system. Slackware however does not have that symlink which is part of the LSB 3.0 specification. You'll need to create the symlink manually after installing the package: ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3 Yes, it's the Google Earth team being silly. -D. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Graphviz Build Error
If I have missed something with the installation of the multilib and compat32 libraries, how should I re-do the process to fix the errors? Graphviz tells me it cannot find a library which is in /usr/lib64; it's looking in /usr/lib. Is this a build script error? libtool: link: warning: /usr/lib/libstdc++.la' seems to be moved /usr/lib/libpangocairo-1.0.so: could not read symbols: File in wrong format collect2: ld returned 1 exit status make[3]: *** [libgvplugin_gd.la] Error 1 make[3]: Leaving directory /tmp/SBo/graphviz-2.28.0/plugin/gd' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory /tmp/SBo/graphviz-2.28.0/plugin' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory /tmp/SBo/graphviz-2.28.0' make: *** [all] Error 2 Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] GoogleEarth Won't Start
On Thu, 16 Jun 2011, David Spencer wrote: That's what happens if you haven't done what's in the SlackBuild's README, note 2: 2) Google Earth 6 is LSB compliant meaning it was built on a LSB system. Slackware however does not have that symlink which is part of the LSB 3.0 specification. You'll need to create the symlink manually after installing the package: ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3 David, Mea culpa! You're correct that I read the notes too quickly to really pay attention to them. Thank you. That fixed the Google Earth problem. One down, two to go. Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] GoogleEarth Won't Start
That tidbit caught me the other day too and was especially perplexing in the Slack32 VM until I put the beer down. I think it would be a good idea to put ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3 into the doinst.sh with maybe a quick check to see if the 32-bit libs are installed. After all why the heck not? -- You! What PLANET is this! -- McCoy, The City on the Edge of Forever, stardate 3134.0 ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] GoogleEarth Won't Start
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/16/2011 11:36 PM, King Beowulf wrote: After all why the heck not? THOU SHALL NOT MESS WITH LD-LINUX.SO.2 !!! On a more serious note: I agree the link is almost armless but I don't think install scripts should start messing around with other packages' files. Especially with glibc stuff. To me README and README.SLACKWARE are the standard places to look for slackbuilds.org notes on building and installing packages, if something is so important that has to be stressed several times, I'd suggest a note inside slack-desc but nothing more. Ciao! P.S.: or, why not a LSB-compat package with symlinks for needed stuff? Anyone up for it? - -- Marco Bonetti Tor research and other stuff: http://sid77.slackware.it/ Slackintosh Linux Project Developer: http://workaround.ch/ Linux-live for powerpc: http://workaround.ch/pub/rsync/mb/linux-live/ My GnuPG key id: 0x0B60BC5F -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk36fQEACgkQTYvJ9gtgvF8/dwCgtciGjQ/5Y0Ty7tAQj2pxLmb7 ItAAoOvLVd7dpWKHMmE66I7nc+T/LVzm =wUoi -END PGP SIGNATURE- ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] GoogleEarth Won't Start
On Thu, 16 Jun 2011, King Beowulf wrote: After all why the heck not? Because it would limit the opportunities for folks to make fun of me. :-) Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Graphviz Build Error
On 6/16/11, Rich Shepard rshep...@appl-ecosys.com wrote: Graphviz tells me it cannot find a library which is in /usr/lib64; it's looking in /usr/lib. Is this a build script error? Nope. The build scripts are tested supported only on non-multilib (pure 64-bit). This gets mentioned pretty often on this mailing list... However, a lot of builds that have this problem (looking for libs in /usr/lib) can be made to work by adding 'LDFLAGS=-L/usr/lib64' to the configure command (right before the CFLAGS and CXXFLAGS stuff). Another thing to check is PKG_CONFIG_PATH in the environment. It shouldn't include /usr/lib/pkgconfig (if it's not set, set it to something like /usr/local/lib64/pkgconfig:/usr/lib64/pkgconfig:/usr/local/lib64/pkgconfig in your .bash_profile or whatever). Worst-case scenario, you might have to hack up the Makefile or whatever the source uses for building. Not really difficult, most of the time. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] GoogleEarth Won't Start
On 06/16/2011 04:09 PM, David Spencer wrote: 2) Google Earth 6 is LSB compliant meaning it was built on a LSB system. Slackware however does not have that symlink which is part of the LSB 3.0 specification. You'll need to create the symlink manually after installing the package: ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3 Yes, it's the Google Earth team being silly. -D. Something important finally used the LSD, I mean LSB, and it only took 15 years! Is there a list of the usual silly symlinks, or is this the only one that anything is likely to use so far? I mean, as long as there's no matching .so it would be used at runtime only, so I don't see any obvious harm in supplying those in Slackware. -P. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Graphviz Build Error
On Thu, 16 Jun 2011, Slacker build user wrote: On the other hand, I have used Graphviz quite a bit for several years and do in fact find it very useful. I would encourage you to grit your teeth and get it running - it is worth some effort, and then you will know what you might have missed! Robert, As time permits. Right now I'm focused on using GRASS, R, and advanced statistical models for biologic data. If I get access to a 64 bit build platform I'll try to build it an post back to the list. Apparently it builds and runs on pure 64-bit systems, but not on multilib systems. Regards, Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] GoogleEarth Won't Start
On Thu, Jun 16, 2011 at 4:36 PM, Patrick J. Volkerding volke...@slackware.com wrote: On 06/16/2011 04:09 PM, David Spencer wrote: 2) Google Earth 6 is LSB compliant meaning it was built on a LSB system. Slackware however does not have that symlink which is part of the LSB 3.0 specification. You'll need to create the symlink manually after installing the package: ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3 Yes, it's the Google Earth team being silly. -D. Something important finally used the LSD, I mean LSB, and it only took 15 years! Is there a list of the usual silly symlinks, or is this the only one that anything is likely to use so far? I mean, as long as there's no matching .so it would be used at runtime only, so I don't see any obvious harm in supplying those in Slackware. -P. Well, all I know about LSB is a few seconds or skimming the wikipedia article. Since only a symlink was required, that sorta indicate Slackware is LSB compatible in terms of GoogleEarth. Heck, if it doesn't bother our Great Guru... On a more serious note: I agree the link is almost armless but I don't think install scripts should start messing around with other packages' files. Especially with glibc stuff. Er, from what little I can understand, glibc is LSB compliant. So what's the issue? There was some talk on Gentoo, Debian and elsewhere about LSB symlink post install packages ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355959) and sift through http://refspecs.freestandards.org/lsb.shtml ... but I tire easily and the beer won't drink itself The point I was trying to make was that the package built via SBo should work like any package native to Slackware. You run the script, installpkg, run it. If you need to do tweaking of symlinks, that should be set up via the package. Sometimes some post installation configuring is needed but that is not this case. And while its fun to make fun of anyone, esp Rich Shepard ;-) I repeat, why the heck not put the symlink in doinst.sh if it doesn't bother and Slackware libs etc.? DammitI burnt the pork chops during this rant Slackware SUCKS =:0 -- You! What PLANET is this! -- McCoy, The City on the Edge of Forever, stardate 3134.0 ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Graphviz Build Error
On 6/16/11, Rich Shepard rshep...@appl-ecosys.com wrote: Another thing to check is PKG_CONFIG_PATH in the environment. It shouldn't include /usr/lib/pkgconfig (if it's not set, set it to something like /usr/local/lib64/pkgconfig:/usr/lib64/pkgconfig:/usr/local/lib64/pkgconfig in your .bash_profile or whatever). I don't follow you here. /usr/lib/pkgconfig contains 208 files. Are you suggesting that I add the additional paths in ~/.bash_profile? Well, no, I was saying to make sure /usr/lib/pkgconfig is *not* listed in your PKG_CONFIG_PATH (and make sure /usr/lib64/pkgconfig *is* in there). You don't have to list 200-something .pc files, the PKG_CONFIG_PATH just contains the director(y|ies) where the .pc files are located. The ones in /usr/lib/pkgconfig (if you even have them) are 32-bit, and will specify things like -L/usr/lib, which you don't want. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] sawfish
I seem to recall sawfish was a problem for some previous versions of Slackware. I found it compiled nice and easy for 13.37, though I didn't bother writing the requisite SlackBuilds. If anybody is interested, email me and I'll draw them up and submit them. --Josiah ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
