From dave at dawoodfall.net Thu Sep 1 03:58:38 2011 From: dave at dawoodfall.net (David Woodfall) Date: Thu, 1 Sep 2011 04:58:38 +0100 Subject: [Slackbuilds-users] Orphaned packages In-Reply-To: References: Message-ID: <20110901035838.GA5676@Junius> On (13:47 25/08/11), Mauro Giachero put forth the proposition: >I'm really sorry to announce I'm no longer able to maintain my SlackBuilds >(as all those folks asking for Ekiga updates probably noticed). >The following packages are therefore orphan: > > network/ekiga > libraries/ptlib > libraries/opal > libraries/libflashsupport > libraries/ilbc > academic/qtoctave > academic/octave-forge Since nobody else has stepped up I'm willing to take on ekiga and its deps opal and ptlib. I used to use it a lot for SIP so I'm familiar with it. One question though - does ekiga make use of ilbc? If it does I will take that on too. D. >Regards >-- >Mauro Giachero >_______________________________________________ >SlackBuilds-users mailing list >SlackBuilds-users at slackbuilds.org >http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >FAQ - http://slackbuilds.org/faq/ > -- Don't look back, the lemmings are gaining on you. From mauro.giachero at gmail.com Fri Sep 2 10:57:34 2011 From: mauro.giachero at gmail.com (Mauro Giachero) Date: Fri, 2 Sep 2011 12:57:34 +0200 Subject: [Slackbuilds-users] Orphaned packages In-Reply-To: <20110901035838.GA5676@Junius> References: <20110901035838.GA5676@Junius> Message-ID: On Thu, Sep 1, 2011 at 05:58, David Woodfall wrote: > Since nobody else has stepped up I'm willing to take on ekiga and its > deps opal and ptlib. > > I used to use it a lot for SIP so I'm familiar with it. > > One question though - does ekiga make use of ilbc? If it does I will > take that on too. > > D. > IIRC it's an optional dependency. -- Mauro Giachero -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at dawoodfall.net Fri Sep 2 21:48:01 2011 From: dave at dawoodfall.net (David Woodfall) Date: Fri, 2 Sep 2011 22:48:01 +0100 Subject: [Slackbuilds-users] Orphaned packages In-Reply-To: References: <20110901035838.GA5676@Junius> Message-ID: <20110902214801.GA4051@Junius> On (12:57 02/09/11), Mauro Giachero put forth the proposition: >On Thu, Sep 1, 2011 at 05:58, David Woodfall wrote: > >> Since nobody else has stepped up I'm willing to take on ekiga and its >> deps opal and ptlib. >> >> I used to use it a lot for SIP so I'm familiar with it. >> >> One question though - does ekiga make use of ilbc? If it does I will >> take that on too. >> >> D. >> > >IIRC it's an optional dependency. Unfortunately their website gives me a DNS failure. If you have the source yourself could you upload somewhere? D. >-- >Mauro Giachero >_______________________________________________ >SlackBuilds-users mailing list >SlackBuilds-users at slackbuilds.org >http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >FAQ - http://slackbuilds.org/faq/ > -- Don't look back, the lemmings are gaining on you. From disturbed1976 at gmail.com Fri Sep 2 23:27:17 2011 From: disturbed1976 at gmail.com (Keith Richie) Date: Fri, 2 Sep 2011 19:27:17 -0400 Subject: [Slackbuilds-users] Orphaned packages In-Reply-To: <20110902214801.GA4051@Junius> References: <20110901035838.GA5676@Junius> <20110902214801.GA4051@Junius> Message-ID: On Fri, Sep 2, 2011 at 5:48 PM, David Woodfall wrote: > On (12:57 02/09/11), Mauro Giachero put forth the > proposition: >> >> On Thu, Sep 1, 2011 at 05:58, David Woodfall wrote: >> >>> Since nobody else has stepped up I'm willing to take on ekiga and its >>> deps opal and ptlib. >>> >>> I used to use it a lot for SIP so I'm familiar with it. >>> >>> One question though - does ekiga make use of ilbc? If it does I will >>> take that on too. >>> >>> D. >>> >> >> IIRC it's an optional dependency. > > Unfortunately their website gives me a DNS failure. If you have the > source yourself could you upload somewhere? > > D. > >> -- >> Mauro Giachero > >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> > > > -- > Don't look back, the lemmings are gaining on you. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > http://www.webrtc.org/ilbc-freeware Or from Linphone ( http://www.linphone.org/eng/download/ ) msilbc: iLBC codec plugin based on c code extracted from IETF RFC page. Source code can be extracted using git repo git://git.linphone.org/libilbc-rfc3951 git clone git://git.linphone.org/libilbc-rfc3951 From biolizard.mail at gmail.com Sat Sep 3 02:21:33 2011 From: biolizard.mail at gmail.com (=?ISO-8859-1?Q?Jos=E9_Lopes?=) Date: Sat, 03 Sep 2011 03:21:33 +0100 Subject: [Slackbuilds-users] LibreOffice and Dropbox In-Reply-To: <4E618E40.6000508@gmail.com> References: <4E618E40.6000508@gmail.com> Message-ID: <4E618F2D.3040308@gmail.com> Hello, By the way, the links are the following: LibreOffice LibO_3.4.3_Linux_x86_install-rpm_en-US.tar.gz 146 MB LibO_3.4.3_Linux_x86_helppack-rpm_en-US.tar.gz 9 MB (en-US - English (US)) Dropbox Linux x86_64:http://dl-web.dropbox.com/u/17/dropbox-lnx.x86_64-1.2.30.tar.gz Linux x86:http://dl-web.dropbox.com/u/17/dropbox-lnx.x86-1.2.30.tar.gz On 09/03/2011 03:17 AM, Jos? Lopes wrote: > Hello, > > The official LibreOffice has been updated to version 3.4.3, therefore, > the SlackBuilds.org link is broken. > > The Dropbox link is also broken. > > Regards, > Jos? -------------- next part -------------- An HTML attachment was scrubbed... URL: From biolizard.mail at gmail.com Sat Sep 3 02:17:36 2011 From: biolizard.mail at gmail.com (=?ISO-8859-1?Q?Jos=E9_Lopes?=) Date: Sat, 03 Sep 2011 03:17:36 +0100 Subject: [Slackbuilds-users] LibreOffice and Dropbox Message-ID: <4E618E40.6000508@gmail.com> Hello, The official LibreOffice has been updated to version 3.4.3, therefore, the SlackBuilds.org link is broken. The Dropbox link is also broken. Regards, Jos? From niels.horn at gmail.com Sat Sep 3 03:26:29 2011 From: niels.horn at gmail.com (Niels Horn) Date: Sat, 3 Sep 2011 00:26:29 -0300 Subject: [Slackbuilds-users] LibreOffice and Dropbox In-Reply-To: <4E618E40.6000508@gmail.com> References: <4E618E40.6000508@gmail.com> Message-ID: 2011/9/2 Jos? Lopes : > Hello, > > The official LibreOffice has been updated to version 3.4.3, therefore, the > SlackBuilds.org link is broken. > > The Dropbox link is also broken. > > Regards, > Jos? A new version has been submitted already. -- Niels Horn From biolizard.mail at gmail.com Sat Sep 3 03:34:42 2011 From: biolizard.mail at gmail.com (=?ISO-8859-1?Q?Jos=E9_Lopes?=) Date: Sat, 03 Sep 2011 04:34:42 +0100 Subject: [Slackbuilds-users] LibreOffice and Dropbox In-Reply-To: References: <4E618E40.6000508@gmail.com> Message-ID: <4E61A052.3050203@gmail.com> Thanks. On 09/03/2011 04:26 AM, Niels Horn wrote: > 2011/9/2 Jos? Lopes: >> Hello, >> >> The official LibreOffice has been updated to version 3.4.3, therefore, the >> SlackBuilds.org link is broken. >> >> The Dropbox link is also broken. >> >> Regards, >> Jos? > A new version has been submitted already. > > -- > Niels Horn > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From dave at dawoodfall.net Sat Sep 3 03:36:21 2011 From: dave at dawoodfall.net (David Woodfall) Date: Sat, 3 Sep 2011 04:36:21 +0100 Subject: [Slackbuilds-users] Orphaned packages In-Reply-To: References: <20110901035838.GA5676@Junius> <20110902214801.GA4051@Junius> Message-ID: <20110903033621.GA32258@Junius> On (19:27 02/09/11), Keith Richie put forth the proposition: >On Fri, Sep 2, 2011 at 5:48 PM, David Woodfall wrote: >> On (12:57 02/09/11), Mauro Giachero put forth the >> proposition: >>> >>> On Thu, Sep 1, 2011 at 05:58, David Woodfall wrote: >>> >>>> Since nobody else has stepped up I'm willing to take on ekiga and its >>>> deps opal and ptlib. >>>> >>>> I used to use it a lot for SIP so I'm familiar with it. >>>> >>>> One question though - does ekiga make use of ilbc? If it does I will >>>> take that on too. >>>> >>>> D. >>>> >>> >>> IIRC it's an optional dependency. >> >> Unfortunately their website gives me a DNS failure. If you have the >> source yourself could you upload somewhere? >> >> D. >> >>> -- >>> Mauro Giachero > >http://www.webrtc.org/ilbc-freeware > >Or from Linphone ( http://www.linphone.org/eng/download/ ) >msilbc: iLBC codec plugin based on c code extracted from IETF RFC >page. Source code can be extracted using git repo >git://git.linphone.org/libilbc-rfc3951 > >git clone git://git.linphone.org/libilbc-rfc3951 I just had a quick look at this and find that it tries to download http://www.ilbcfreeware.org/documentation/extract-cfile.awk which of course fails due to the DNS error. D. From dave at dawoodfall.net Sat Sep 3 03:44:23 2011 From: dave at dawoodfall.net (David Woodfall) Date: Sat, 3 Sep 2011 04:44:23 +0100 Subject: [Slackbuilds-users] Orphaned packages In-Reply-To: <20110903033621.GA32258@Junius> References: <20110901035838.GA5676@Junius> <20110902214801.GA4051@Junius> <20110903033621.GA32258@Junius> Message-ID: <20110903034423.GA6270@Junius> On (04:36 03/09/11), David Woodfall put forth the proposition: >On (19:27 02/09/11), Keith Richie put forth the proposition: >>On Fri, Sep 2, 2011 at 5:48 PM, David Woodfall wrote: >>>On (12:57 02/09/11), Mauro Giachero put forth the >>>proposition: >>>> >>>>On Thu, Sep 1, 2011 at 05:58, David Woodfall wrote: >>>> >>>>>Since nobody else has stepped up I'm willing to take on ekiga and its >>>>>deps opal and ptlib. >>>>> >>>>>I used to use it a lot for SIP so I'm familiar with it. >>>>> >>>>>One question though - does ekiga make use of ilbc? If it does I will >>>>>take that on too. >>>>> >>>>>D. >>>>> >>>> >>>>IIRC it's an optional dependency. >>> >>>Unfortunately their website gives me a DNS failure. If you have the >>>source yourself could you upload somewhere? >>> >>>D. >>> >>>>-- >>>>Mauro Giachero >> >>http://www.webrtc.org/ilbc-freeware >> >>Or from Linphone ( http://www.linphone.org/eng/download/ ) >>msilbc: iLBC codec plugin based on c code extracted from IETF RFC >>page. Source code can be extracted using git repo >>git://git.linphone.org/libilbc-rfc3951 >> >>git clone git://git.linphone.org/libilbc-rfc3951 > >I just had a quick look at this and find that it tries to download >http://www.ilbcfreeware.org/documentation/extract-cfile.awk >which of course fails due to the DNS error. > >D. Ah the rcf file is still there and isn't hosted at their homepage so all it ok. D. From korgie at gmail.com Sat Sep 3 09:11:51 2011 From: korgie at gmail.com (korgman) Date: Sat, 03 Sep 2011 12:11:51 +0300 Subject: [Slackbuilds-users] Orphaned packages In-Reply-To: References: <20110901035838.GA5676@Junius> Message-ID: <4E61EF57.6090002@gmail.com> On 02/09/2011 01:57 ??, Mauro Giachero wrote: > On Thu, Sep 1, 2011 at 05:58, David Woodfall > wrote: > > Since nobody else has stepped up I'm willing to take on ekiga and its > deps opal and ptlib. > > I used to use it a lot for SIP so I'm familiar with it. > > One question though - does ekiga make use of ilbc? If it does I will > take that on too. > > D. > > > IIRC it's an optional dependency. Very... optional. It seems that the quality is low since my words are not recognizable to automated system. I switched to higher bit-rate G726.40. -- http://clavisound.dyndns-server.com Michales Michaloudes From black_rider at esdebian.org Sat Sep 3 10:55:32 2011 From: black_rider at esdebian.org (Black Rider) Date: Sat, 3 Sep 2011 12:55:32 +0200 Subject: [Slackbuilds-users] Replying to messages In-Reply-To: References: Message-ID: <20110903125532.76f28924@whitestar> El Wed, 31 Aug 2011 15:31:07 -0300 Niels Horn escribi?: > On Wed, Aug 31, 2011 at 2:48 PM, Roland Waggoner > wrote: > > The slackbuilds digest contains multiple messages. How can I reply > > to individual messages? > > > > Roland > > _______________________________________________ > > There is no simple answer to this question. > > You could copy & paste the message from the digest and make sure you > get the right subject in your answer. > But even then many e-mail readers wont group your answer with the > original thread, as they look for a marker in the header that will be > missing. > > That's the disadvantage of subscribing to the digest... > > -- > Niels Horn > Claws-mail is able to break the digest into individual messages and answer them individualy if desired. A bunch of icons is displayed at the right of the incomming message, so clicking in one of them will show only the selected message and not the whole digest.It works painlessly. Give it a try. From janherrygers at dommel.be Sat Sep 3 18:33:54 2011 From: janherrygers at dommel.be (Jan Herrygers) Date: Sat, 3 Sep 2011 20:33:54 +0200 Subject: [Slackbuilds-users] Replying to messages In-Reply-To: References: Message-ID: <201109032033.54684.janherrygers@dommel.be> Op woensdag 31 augustus 2011 19:48:53 schreef Roland Waggoner: > The slackbuilds digest contains multiple messages. How can I reply to > individual messages? Roland I altered the settings on my mail list subscription so I get multipart mime digests instead of plain text digests. Then Kmail displays every message with its own headers. From that I can open the individual message in a new window and go on from that. What mail client are you using? The gmail web interface? -- Jan From bob.snyder at cox.net Sun Sep 4 21:52:16 2011 From: bob.snyder at cox.net (Bob Snyder) Date: Sun, 04 Sep 2011 14:52:16 -0700 Subject: [Slackbuilds-users] Grip and Grip2 build same version Message-ID: <4E63F310.2050800@cox.net> The README for grip2 says "If you're looking for a modern version of Grip, see the package "grip"" but grip and grip2 both point to grip-2.96. Regards, Bob S From erik at slackbuilds.org Sun Sep 4 23:14:06 2011 From: erik at slackbuilds.org (Erik Hanson) Date: Sun, 04 Sep 2011 18:14:06 -0500 Subject: [Slackbuilds-users] Grip and Grip2 build same version In-Reply-To: <4E63F310.2050800@cox.net> References: <4E63F310.2050800@cox.net> Message-ID: <4E64063E.2070500@slackbuilds.org> On 09/04/2011 04:52 PM, Bob Snyder wrote: > The README for grip2 says "If you're looking for a modern version of > Grip, see the package "grip"" but > grip and grip2 both point to grip-2.96. Sorry, grip was replaced by grip2. I removed the old entry from the db. There was some talk on the list about "grip" being submitted, but it doesn't appear to have happened. -- Erik Hanson From bob.snyder at cox.net Sun Sep 4 23:23:26 2011 From: bob.snyder at cox.net (Bob Snyder) Date: Sun, 04 Sep 2011 16:23:26 -0700 Subject: [Slackbuilds-users] Grip and Grip2 build same version In-Reply-To: <4E64063E.2070500@slackbuilds.org> References: <4E63F310.2050800@cox.net> <4E64063E.2070500@slackbuilds.org> Message-ID: <4E64086E.8020608@cox.net> On 09/04/2011 04:14 PM, Erik Hanson wrote: > On 09/04/2011 04:52 PM, Bob Snyder wrote: >> The README for grip2 says "If you're looking for a modern version of >> Grip, see the package "grip"" but >> grip and grip2 both point to grip-2.96. > > Sorry, grip was replaced by grip2. I removed the old entry from the > db. There was some talk on the list about "grip" being submitted, but > it doesn't appear to have happened. > My impression is that the 'current' version of grip (3.x) is (was) called grip, and the older non-gnome version was called grip2 because it is Version 2.x. The README for grip2 agrees with this notion where it says "This is an older version of Grip that does not require GNOME. If you're looking for a modern version of Grip, see the package "grip"" Bob S. From erik at slackbuilds.org Mon Sep 5 00:59:32 2011 From: erik at slackbuilds.org (Erik Hanson) Date: Sun, 04 Sep 2011 19:59:32 -0500 Subject: [Slackbuilds-users] Grip and Grip2 build same version In-Reply-To: <4E64086E.8020608@cox.net> References: <4E63F310.2050800@cox.net> <4E64063E.2070500@slackbuilds.org> <4E64086E.8020608@cox.net> Message-ID: <4E641EF4.4040008@slackbuilds.org> On 9/4/2011 6:23 PM, Bob Snyder wrote: > On 09/04/2011 04:14 PM, Erik Hanson wrote: >> On 09/04/2011 04:52 PM, Bob Snyder wrote: >>> The README for grip2 says "If you're looking for a modern version of >>> Grip, see the package "grip"" but >>> grip and grip2 both point to grip-2.96. >> >> Sorry, grip was replaced by grip2. I removed the old entry from the >> db. There was some talk on the list about "grip" being submitted, but >> it doesn't appear to have happened. >> > > My impression is that the 'current' version of grip (3.x) is (was) > called grip, and the older non-gnome version was called grip2 because > it is Version 2.x. The README for grip2 agrees with this notion where > it says "This is an older version of Grip that does not require GNOME. > If you're looking for a modern version of Grip, see the package "grip"" Right, and like I said, "grip" (3.x) hasn't been submitted. "grip" (2.x) became "grip2" to make way for it. Confusing, I know. -- Erik Hanson From bob.snyder at cox.net Mon Sep 5 01:55:01 2011 From: bob.snyder at cox.net (Bob Snyder) Date: Sun, 04 Sep 2011 18:55:01 -0700 Subject: [Slackbuilds-users] Grip and Grip2 build same version In-Reply-To: <4E641EF4.4040008@slackbuilds.org> References: <4E63F310.2050800@cox.net> <4E64063E.2070500@slackbuilds.org> <4E64086E.8020608@cox.net> <4E641EF4.4040008@slackbuilds.org> Message-ID: <4E642BF5.7000400@cox.net> On 09/04/2011 05:59 PM, Erik Hanson wrote: > On 9/4/2011 6:23 PM, Bob Snyder wrote: >> On 09/04/2011 04:14 PM, Erik Hanson wrote: >>> On 09/04/2011 04:52 PM, Bob Snyder wrote: >>>> The README for grip2 says "If you're looking for a modern version >>>> of Grip, see the package "grip"" but >>>> grip and grip2 both point to grip-2.96. >>> >>> Sorry, grip was replaced by grip2. I removed the old entry from the >>> db. There was some talk on the list about "grip" being submitted, >>> but it doesn't appear to have happened. >>> >> >> My impression is that the 'current' version of grip (3.x) is (was) >> called grip, and the older non-gnome version was called grip2 because >> it is Version 2.x. The README for grip2 agrees with this notion where >> it says "This is an older version of Grip that does not require >> GNOME. If you're looking for a modern version of Grip, see the >> package "grip"" > > Right, and like I said, "grip" (3.x) hasn't been submitted. "grip" > (2.x) became "grip2" to make way for it. Confusing, I know. > Okay, thanks Eric. Bob S. From niels.horn at gmail.com Mon Sep 5 02:00:36 2011 From: niels.horn at gmail.com (Niels Horn) Date: Sun, 4 Sep 2011 23:00:36 -0300 Subject: [Slackbuilds-users] Updates - 20110905.1 Message-ID: Mon Sep 5 01:02:24 UTC 2011 academic/EMBASSY: Added (EMBOSS associated software) academic/EMBOSS: Added (European Molecular Biology OSS) academic/PhyML: Added (Phylogeny software) academic/amplicon: Added (Design PCR primers) academic/arka: Added (A GUI for genpak) academic/celestia: Updated for version 1.6.1. academic/clustalw: Added (Multiple Sequence Alignment) academic/clustalx: Added (Multiple Sequence Alignment GUI) academic/genpak: Added (Utilities to manipulate DNA sequences) academic/gp2fasta: Added (Convert gp files to fasta) academic/isoelectric-point: Added (Isoelectric point calculator) academic/lalnview: Added (Visualize local alignments) academic/muscle: Added (A multiple sequence alignments program) academic/perlprimer: Added (Design primers for PCR and sequencing) academic/plasmidomics: Added (Plasmid Drawing Program) academic/primer3: Added (Design PCR primers) academic/seaview: Added (sequence alignment and phylogeny GUI) academic/sequence-analysis: Added (Biologic sequences analysis) academic/spidey: Added (mRNA-to-genomic alignment) audio/gnomad2: Updated for version 2.9.6. audio/jack-audio-connection-kit: Updated for version 0.121.2. desktop/xcm: Added (colour management tool) development/nexus: Updated download location. development/tiled-qt: Added (Tiled map editor) development/viewvc: Updated for version 1.1.11. development/vile: Updated for version 9.8e. development/xvile: Updated for version 9.8e. games/freeciv: Updated for version 2.2.7. games/warmux: Updated for version 11.04.1. graphics/LDraw_data: Updated for version 201101. graphics/brlcad: Updated for version 7.20.2. graphics/oyranos: Added (Colour Management System) graphics/qcomicbook: Updated for version 0.8.1. libraries/PDFlib-Lite: Added (A library to generate PDF files) libraries/gl2ps: Added (OpenGL to PostScript printing library) libraries/libXcm: Added (implementation of the net-color spec) libraries/libalkimia: Added (KDE finance library) libraries/libssh: Updated for version 0.5.1. multimedia/flash-player-plugin: Updated for version 11_b2. multimedia/minitube: Updated for version 1.5. multimedia/miro: Updated for version 4.0.3. multimedia/parole: Added (GStreamer based media player) network/GeoIP: Updated for version 1.4.8. network/cclive: Updated for version 0.7.5. network/claws-mail-extra-plugins: Updated for version 3.7.10. network/claws-mail: Updated for version 3.7.10. network/ddclient: Updated for version 3.8.1. network/ipset: Added (administration tool for IP sets) network/leafnode: Updated for version 2.0.0.alpha20110807a. network/nagios: Updated for version 3.3.1. network/opera: Updated for version 11.51. network/quvi: Updated for version 0.2.19. network/rt3xxx: Updated e-mail maintainer + cleanup script. network/transmission: Updated for version 2.33. network/uwsgi: Updated for version 0.9.8.3. network/zabbix_agentd: Updated for version 1.8.6. network/zabbix_proxy: Updated for version 1.8.6. network/zabbix_server: Updated for version 1.8.6. office/libreoffice-langpack: Updated for version 3.4.3. office/libreoffice: Updated for version 3.4.3. office/nts: Updated for version 82. office/texlive: Included some patches from branch2011 python/paramiko: Updated for version 1.7.7.1. system/freefont: Updated for version 20100919 (+ new maintainer) system/herculesstudio: Updated for version 1.3.0. system/nvidia-driver: Updated for version 280.13. system/nvidia-kernel: Updated for version 280.13. system/oss: Updated for version 4.2.2005. system/p7zip: Updated for version 9.20.1. system/unalz: Updated e-mail mainainer + cleanup script. system/unhide: Added (utility for discovering hidden processes) From yalhcru at gmail.com Mon Sep 5 10:57:12 2011 From: yalhcru at gmail.com (B Watson) Date: Mon, 5 Sep 2011 06:57:12 -0400 Subject: [Slackbuilds-users] Grip and Grip2 build same version In-Reply-To: <4E64086E.8020608@cox.net> References: <4E63F310.2050800@cox.net> <4E64063E.2070500@slackbuilds.org> <4E64086E.8020608@cox.net> Message-ID: On 9/4/11, Bob Snyder wrote: > My impression is that the 'current' version of grip (3.x) is (was) > called grip, and the older non-gnome version was called grip2 because it > is Version 2.x. So far, there's never been a grip 3.x on slackbuilds.org. Originally, "grip" was grip 2.x, same version as grip2 is now. I was asked to rename "grip" to "grip2" so that someone else could submit a build for the 3.x one, which was going to just be called "grip". > The README for grip2 agrees with this notion where it > says "This is an older version of Grip that does not require GNOME. If > you're looking for a modern version of Grip, see the package "grip"" Right, when I wrote that README, I was under the impression that someone was going to be submitting the 3.x version (as "grip") within the next few days after I submitted grip2. Apparently nobody actually did it though. I won't be submitting grip 3.x as I have no interest in messing with all the gnome stuff required to make it work, and because 2.x works just fine for my needs. So, if you wanted to, you could write the SlackBuild for grip 3.x and submit it... If nobody's going to do this any time soon, I'll edit my README so it stops pretending there's a 3.x package where there clearly isn't. From rshepard at appl-ecosys.com Mon Sep 5 20:39:04 2011 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 5 Sep 2011 13:39:04 -0700 (PDT) Subject: [Slackbuilds-users] Upgraded LibreOffice-3.4.3 Has No Executable Message-ID: I've been running Eric's LO-3.3.3 on -13.1/32-bit and saw that the application has been upgraded to 3.4.3 so I thought it a good idea to build the new package and replace the older version. libreoffice.SlackBuild ran without error and everything looked copesetic: Verifying package libreoffice-3.4.3_en_US-i586-1_SBo.tgz. Installing package libreoffice-3.4.3_en_US-i586-1_SBo.tgz: ... Executing install script for libreoffice-3.4.3_en_US-i586-1_SBo.tgz. Package libreoffice-3.4.3_en_US-i586-1_SBo.tgz installed. Package libreoffice-3.3.3-i486-1alien upgraded with new package /tmp/libreoffice-3.4.3_en_US-i586-1_SBo.tgz. But I cannot invoke the application. When I look for where it is to be found I see only these: [root at salmo /opt/slackbuilds/libreoffice]# find / -name libreoffice /var/lib/sbopkg/SBo/13.1/office/libreoffice /opt/slackbuilds/libreoffice /usr/lib/libreoffice and the last directory contains only [rshepard at salmo /opt/slackbuilds]$ ls /usr/lib/libreoffice/ share/ [rshepard at salmo /opt/slackbuilds]$ ls /usr/lib/libreoffice/share/ uno_packages/ [rshepard at salmo /opt/slackbuilds]$ ls /usr/lib/libreoffice/share/uno_packages/ cache/ [rshepard at salmo /opt/slackbuilds]$ ls /usr/lib/libreoffice/share/uno_packages/cache/ uno_packages/ [rshepard at salmo /opt/slackbuilds]$ ls /usr/lib/libreoffice/share/uno_packages/cache/uno_packages/ 7xc8pn 7xc8pn_/ [rshepard at salmo /opt/slackbuilds]$ ls /usr/lib/libreoffice/share/uno_packages/cache/uno_packages/7xc8pn /usr/lib/libreoffice/share/uno_packages/cache/uno_packages/7xc8pn There is nothing in /usr/bin and there appears to be no executable. Please suggest what I should do to gain a working LO once again. TIA, Rich From niels.horn at gmail.com Mon Sep 5 21:58:02 2011 From: niels.horn at gmail.com (Niels Horn) Date: Mon, 5 Sep 2011 18:58:02 -0300 Subject: [Slackbuilds-users] Upgraded LibreOffice-3.4.3 Has No Executable In-Reply-To: References: Message-ID: On Mon, Sep 5, 2011 at 5:39 PM, Rich Shepard wrote: > ?I've been running Eric's LO-3.3.3 on -13.1/32-bit and saw that the > application has been upgraded to 3.4.3 so I thought it a good idea to build > the new package and replace the older version. > > ?libreoffice.SlackBuild ran without error and everything looked copesetic: > > Verifying package libreoffice-3.4.3_en_US-i586-1_SBo.tgz. > Installing package libreoffice-3.4.3_en_US-i586-1_SBo.tgz: > > ?... > > Executing install script for libreoffice-3.4.3_en_US-i586-1_SBo.tgz. > Package libreoffice-3.4.3_en_US-i586-1_SBo.tgz installed. > > Package libreoffice-3.3.3-i486-1alien upgraded with new package > /tmp/libreoffice-3.4.3_en_US-i586-1_SBo.tgz. > > ?But I cannot invoke the application. When I look for where it is to be > found I see only these: > > [root at salmo /opt/slackbuilds/libreoffice]# find / -name libreoffice > /var/lib/sbopkg/SBo/13.1/office/libreoffice > /opt/slackbuilds/libreoffice > /usr/lib/libreoffice > > and the last directory contains only > > [rshepard at salmo /opt/slackbuilds]$ ls /usr/lib/libreoffice/ > share/ > [rshepard at salmo /opt/slackbuilds]$ ls /usr/lib/libreoffice/share/ > uno_packages/ > [rshepard at salmo /opt/slackbuilds]$ ls > /usr/lib/libreoffice/share/uno_packages/ > cache/ > [rshepard at salmo /opt/slackbuilds]$ ls > /usr/lib/libreoffice/share/uno_packages/cache/ > uno_packages/ > [rshepard at salmo /opt/slackbuilds]$ ls > /usr/lib/libreoffice/share/uno_packages/cache/uno_packages/ > 7xc8pn ?7xc8pn_/ > [rshepard at salmo /opt/slackbuilds]$ ls > /usr/lib/libreoffice/share/uno_packages/cache/uno_packages/7xc8pn > /usr/lib/libreoffice/share/uno_packages/cache/uno_packages/7xc8pn > > ?There is nothing in /usr/bin and there appears to be no executable. > > ?Please suggest what I should do to gain a working LO once again. > > TIA, > > Rich First of all, there is a big difference between Eric's package and the one built with the script on SlackBuilds.org. Eric's package is built from source and installed in /usr/lib{,64}/libreoffice The SBo package is a repackaging of the binaries from The Document Foundation, installed in /opt/libreofficeN.N The SBo package (which you have installed now) creates symlinks in /usr/bin for each individual program, for example: /usr/bin/scalc points to /opt/libreoffice3.4/program/scalc The script that creates these symlinks was run at the end of the installation ("Executing install script for libreoffice-3.4.3_en_US-i586-1_SBo.tgz."). I never tried upgrading Eric's package to the SBO package, but it should work fine. -- Niels Horn From rshepard at appl-ecosys.com Mon Sep 5 22:58:39 2011 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 5 Sep 2011 15:58:39 -0700 (PDT) Subject: [Slackbuilds-users] Upgraded LibreOffice-3.4.3 Has No Executable In-Reply-To: References: Message-ID: On Mon, 5 Sep 2011, Niels Horn wrote: > The SBo package (which you have installed now) creates symlinks in usr/bin > /for each individual program, for example: usr/bin/scalc points to > //opt/libreoffice3.4/program/scalc Niels, Aha! I was not aware of this. And this solves an issue I had with Eric's previous version: starting it using soffice (which the shell script now calls using /usr/bin/soffice) brought up a blank page with an illustrated menu in the center. Now, running /usr/bin/soffice brings up a blank writer document and my templates are once again visible and can be selected. I'm happy. > I never tried upgrading Eric's package to the SBO package, but it should > work fine. It does when one understands the differences. :-) Many thanks for the lesson, Rich From rworkman at slackbuilds.org Tue Sep 6 04:17:33 2011 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 5 Sep 2011 23:17:33 -0500 Subject: [Slackbuilds-users] Updates - 20110906.1 Message-ID: <20110905231733.21b7d243@liberty.rlwhome.lan> Tue Sep 6 04:04:19 UTC 2011 academic/gtypist: Updated for version 2.8.5. academic/mathomatic: Updated for version 15.6.4. academic/mendeleydesktop: Updated for version 1.0.1. academic/sage: Updated for version 4.7.1. desktop/scrotwm: Updated for version 0.9.34. development/Pivy: Updated for version hg_20101207. development/bigloo: Added (Bigloo Scheme implementation) development/tig: Updated for version 0.18. development/valgrind: Apply upstream patches to fix a bug. games/bsnes: Updated for version 0.082. games/ltris: Updated for version 1.0.17. games/openttd: Updated for version 1.1.2. games/playonlinux: Updated for version 4.0.9. games/snes9x: Updated for version 1.53. graphics/OpenCASCADE: Updated for version 6.5.1. graphics/feh: Updated for version 1.15.1. libraries/Botan: Updated for version 1.8.13. libraries/Net-SSLeay: Updated for version 1.36. libraries/argparse: Updated for version 1.2.1. libraries/fltk2: Updated for version 2.0.x_alpha_r8800. libraries/foolscap: Updated for version 0.6.1. libraries/imlib2: Updated for version 1.4.5. libraries/libmicrohttpd: Updated for version 0.9.13. libraries/libmodplug: Updated for version 0.8.8.4. libraries/newt: Updated for version 0.52.13. libraries/ptlib: Updated for version 2.6.7. libraries/zbase32: Updated for version 1.1.3. libraries/zfec: Updated for version 1.4.22. multimedia/lircaile: Updated for version 0.3.0. multimedia/tovid: Updated for version 0.34. network/aMule: Control building some optimal features. network/amap: Updated for version 5.4. network/deluge: Updated for version 1.3.3. network/filezilla: Updated for version 3.5.1. network/frostwire: Updated for version 5.1.4. network/mod_perl: Updated for version 2.0.5. network/openvswitch: Updated for version 1.2.1. network/tor: Updated for version 0.2.2.32. office/kmymoney: Updated for version 4.6.0. office/openoffice.org: Added (yes, re-added) office/sigil: Updated for version 0.4.2. office/task: Updated for version 1.9.4 and moved from misc. office/xpad: Updated for version 4.0. python/Pyro: Updated for version 3.14. python/pyOpenSSL: Updated for version 0.12. python/pyPdf: Updated for version 1.13. python/pycryptopp: Updated for version 0.5.29. python/pyutil: Updated for version 1.8.4. system/kvm-kmod: Updated for version 3.0b. system/laptop-mode-tools: Updated for version 1.59. system/mariadb: Updated for version 5.2.8. system/mksh: Updated for version R40b. system/sakura: Updated for version 2.4.2. system/slack-utils: Updated for version 0.6.2. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From rshepard at appl-ecosys.com Tue Sep 6 22:41:20 2011 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 6 Sep 2011 15:41:20 -0700 (PDT) Subject: [Slackbuilds-users] monit version upgrade Message-ID: The utility, monit, is now at version 5.2.5 but the SBo page shows (and downloads) 5.0. FYI, Rich From fakhry.linux at gmail.com Wed Sep 7 07:55:08 2011 From: fakhry.linux at gmail.com (Fakhry) Date: Wed, 7 Sep 2011 15:55:08 +0800 Subject: [Slackbuilds-users] Google Earth now support ARCH x86_64 Message-ID: I just open http://www.google.com/earth/download/ge/agree.html. And it seems Google Earth support x86_64. GoogleEarth.Slackbuild may need to updated. -- PS: Sorry if my English is bad :( Fakhry http://www.fakhry.web.id http://www.slackware.kendari.linux.or.id/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Wed Sep 7 08:16:15 2011 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 07 Sep 2011 10:16:15 +0200 Subject: [Slackbuilds-users] Google Earth now support ARCH x86_64 In-Reply-To: References: Message-ID: <4E67284F.60803@gmail.com> On 07/09/2011 09:55, Fakhry wrote: > I just open http://www.google.com/earth/download/ge/agree.html. > And it seems Google Earth support x86_64. > GoogleEarth.Slackbuild may need to updated. unfortunately it's still a 32bit app -> it needs a multilib setup -> as per slackbuilds rules is unsupported. https://www.linuxquestions.org/questions/slackware-14/google-earth-6-0-64-bit-901089/ Matteo From leva at ecentrum.hu Fri Sep 9 08:24:39 2011 From: leva at ecentrum.hu (LEVAI Daniel) Date: Fri, 9 Sep 2011 10:24:39 +0200 Subject: [Slackbuilds-users] ksh-openbsd name/version change Message-ID: <20110909082438.GC32113@digidani.digicable.hu> Hi! I would like to change the versioning scheme of the ksh-openbsd package. It would be ksh-openbsd-$DATE, eg. ksh-openbsd-20110909 from now on. This wouldn't be a straight forward upgrade, because you must removepkg the old one, and install the new version. Ok? Daniel -- L?VAI D?niel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F From audrius at neutrino.lt Fri Sep 9 08:43:16 2011 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Fri, 9 Sep 2011 11:43:16 +0300 Subject: [Slackbuilds-users] ksh-openbsd name/version change In-Reply-To: <20110909082438.GC32113@digidani.digicable.hu> References: <20110909082438.GC32113@digidani.digicable.hu> Message-ID: <20110909084316.GA3479@kiras> On Fri, 2011-09-09 at 10:24:39 +0200, LEVAI Daniel wrote: > I would like to change the versioning scheme of the ksh-openbsd package. > It would be ksh-openbsd-$DATE, eg. ksh-openbsd-20110909 from now on. Correct me if I'm wrong, but at the moment PRGNAM=ksh and VERSION=openbsd49, and you want it to change to PRGNAM=ksh-openbsd and VERSION=20110909, right? If so, I don't see any problems in that. > This wouldn't be a straight forward upgrade, because you must removepkg > the old one, and install the new version. Or you can use: upgradepkg oldpackagename%newpackagename -- Audrius Ka?ukauskas -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From leva at ecentrum.hu Fri Sep 9 08:50:23 2011 From: leva at ecentrum.hu (LEVAI Daniel) Date: Fri, 9 Sep 2011 10:50:23 +0200 Subject: [Slackbuilds-users] ksh-openbsd name/version change In-Reply-To: <20110909084316.GA3479@kiras> References: <20110909082438.GC32113@digidani.digicable.hu> <20110909084316.GA3479@kiras> Message-ID: <20110909085022.GD32113@digidani.digicable.hu> On Fri, Sep 09, 2011 at 11:43:16 +0300, Audrius Ka?ukauskas wrote: > On Fri, 2011-09-09 at 10:24:39 +0200, LEVAI Daniel wrote: > > I would like to change the versioning scheme of the ksh-openbsd package. > > It would be ksh-openbsd-$DATE, eg. ksh-openbsd-20110909 from now on. > > Correct me if I'm wrong, but at the moment PRGNAM=ksh and > VERSION=openbsd49, and you want it to change to PRGNAM=ksh-openbsd and > VERSION=20110909, right? If so, I don't see any problems in that. Well, it wouldn't be exactly like that. PRGNAM would stay 'ksh', and the version string would be s,49$,$DATE,. > > This wouldn't be a straight forward upgrade, because you must removepkg > > the old one, and install the new version. > > Or you can use: > > upgradepkg oldpackagename%newpackagename Wow, I didn't you can do that :/ Thanks, Daniel -- L?VAI D?niel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F From audrius at neutrino.lt Fri Sep 9 09:31:03 2011 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Fri, 9 Sep 2011 12:31:03 +0300 Subject: [Slackbuilds-users] ksh-openbsd name/version change In-Reply-To: <20110909085022.GD32113@digidani.digicable.hu> References: <20110909082438.GC32113@digidani.digicable.hu> <20110909084316.GA3479@kiras> <20110909085022.GD32113@digidani.digicable.hu> Message-ID: <20110909093103.GA4466@kiras> On Fri, 2011-09-09 at 10:50:23 +0200, LEVAI Daniel wrote: > On Fri, Sep 09, 2011 at 11:43:16 +0300, Audrius Ka?ukauskas wrote: > > On Fri, 2011-09-09 at 10:24:39 +0200, LEVAI Daniel wrote: > > > I would like to change the versioning scheme of the ksh-openbsd package. > > > It would be ksh-openbsd-$DATE, eg. ksh-openbsd-20110909 from now on. > > > > Correct me if I'm wrong, but at the moment PRGNAM=ksh and > > VERSION=openbsd49, and you want it to change to PRGNAM=ksh-openbsd and > > VERSION=20110909, right? If so, I don't see any problems in that. > > Well, it wouldn't be exactly like that. PRGNAM would stay 'ksh', and the > version string would be s,49$,$DATE,. Ah, so version would be openbsd20110909? I'm asking because in your first mail you wrote 'ksh-openbsd-20110909', and Slackware package name convention doesn't allow hyphens in version segment. Package name scheme looks like this: name-version-arch-build Only name segment can have additional hyphens, because pkgtools removes three last segments in the string to figure out program name. If package would be named as ksh-openbsd-20110909-i486-1_SBo pkgtools would treat is as ksh-openbsd. So your version should be openbsd20110909 or openbsd_20110909, but not openbsd-20110909. And the program name stays the same as it is now (ksh). -- Audrius Ka?ukauskas -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From dave at dawoodfall.net Fri Sep 9 22:21:50 2011 From: dave at dawoodfall.net (David Woodfall) Date: Fri, 9 Sep 2011 23:21:50 +0100 Subject: [Slackbuilds-users] libraries/ilbc new maintainer Message-ID: <20110909222150.GA5915@Junius> I will take over maintainership of libraries/ilbc from Mauro. There is no update at the present, but if someone could just edit the info with my details I take it that is better than having a submission for it? MAINTAINER="David Woodfall" EMAIL="davd at dawoodfall.net" Cheers D. -- Don't look back, the lemmings are gaining on you. From thomas at beingboiled.info Fri Sep 9 22:57:04 2011 From: thomas at beingboiled.info (Thomas Morper) Date: Sat, 10 Sep 2011 00:57:04 +0200 Subject: [Slackbuilds-users] perl-xml-sax doinst.sh Message-ID: <20110909225657.GA20752@arktinen> Hello there, While playing with some Perl modules I noticed that the doinst.sh for perl-xml-sax won't work as expected because of a version- and platform- dependent path that is hardcoded for Slackware 13.0 32-bit. Fortunately, Perl itself knows the correct path, so the problem is easy to fix with a doinst.sh like this: ---8<--- chroot . /usr/bin/perl -MConfig -MXML::SAX -e ' XML::SAX->add_parser(q(XML::SAX::PurePerl))->save_parsers unless (-f $Config{installvendorlib} . "/XML/SAX/ParserDetails.ini");' --->8--- Cheers! -- http://beingboiled.info/slackware/ From xgizzmo at slackbuilds.org Sat Sep 10 00:27:21 2011 From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org) Date: Fri, 9 Sep 2011 20:27:21 -0400 Subject: [Slackbuilds-users] perl-xml-sax doinst.sh In-Reply-To: <20110909225657.GA20752@arktinen> References: <20110909225657.GA20752@arktinen> Message-ID: <201109092027.22244.xgizzmo@slackbuilds.org> On Friday 09 September 2011 18:57:04 Thomas Morper wrote: > Hello there, > > While playing with some Perl modules I noticed that the doinst.sh for > perl-xml-sax won't work as expected because of a version- and platform- > dependent path that is hardcoded for Slackware 13.0 32-bit. > > Fortunately, Perl itself knows the correct path, so the problem is easy > to fix with a doinst.sh like this: > > ---8<--- > chroot . /usr/bin/perl -MConfig -MXML::SAX -e ' > XML::SAX->add_parser(q(XML::SAX::PurePerl))->save_parsers > unless (-f $Config{installvendorlib} . "/XML/SAX/ParserDetails.ini");' > --->8--- > > Cheers! > Fixed this in my git branch. It should go out with the next public push. Thanks for the bug report. http://slackbuilds.org/cgit/slackbuilds/commit/?h=gizzmo&id=95299b4c3b9789a8cb8e9c6b25d2bb298968ad71 --dsomero From info at microlinux.fr Sat Sep 10 09:08:21 2011 From: info at microlinux.fr (Nicolas Kovacs) Date: Sat, 10 Sep 2011 11:08:21 +0200 Subject: [Slackbuilds-users] Virtualbox addons and Virtualbox kernel addons Message-ID: <4E6B2905.3090500@microlinux.fr> Hi, I just built and installed Virtualbox on two different desktops, running respectively Slackware 13.37 and multilib-enabled Slackware64 13.37. I duly followed the build instructions, and so far, virtualbox and virtualbox-kernel built OK. I'm a bit confused about the virtualbox-addons and virtualbox-kernel-addons SlackBuilds. I know they're supposed to be *used* within the GUEST system (I've worked with Virtualbox on CentOS before), but where are they supposed to be *built*? On the host or guest system? Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From ozan.turkyilmaz at gmail.com Sat Sep 10 09:17:07 2011 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Sat, 10 Sep 2011 14:17:07 +0500 Subject: [Slackbuilds-users] Virtualbox addons and Virtualbox kernel addons In-Reply-To: <4E6B2905.3090500@microlinux.fr> References: <4E6B2905.3090500@microlinux.fr> Message-ID: 2011/9/10 Nicolas Kovacs : > > I'm a bit confused about the virtualbox-addons and virtualbox-kernel-addons > SlackBuilds. I know they're supposed to be *used* within the GUEST system > (I've worked with Virtualbox on CentOS before), but where are they supposed > to be *built*? On the host or guest system? If they are some systems (Slackware version and kernel version etc) then it won't matter but if your guess different than your host, build on guest system. -- Ozan, BSc, BEng From leva at ecentrum.hu Sun Sep 11 15:24:10 2011 From: leva at ecentrum.hu (LEVAI Daniel) Date: Sun, 11 Sep 2011 17:24:10 +0200 Subject: [Slackbuilds-users] ksh-openbsd name/version change In-Reply-To: <20110909093103.GA4466@kiras> References: <20110909082438.GC32113@digidani.digicable.hu> <20110909084316.GA3479@kiras> <20110909085022.GD32113@digidani.digicable.hu> <20110909093103.GA4466@kiras> Message-ID: <20110911152409.GA29572@serenity.chello.hu> On p, szept 09, 2011 at 12:31:03 +0300, Audrius Ka?ukauskas wrote: > On Fri, 2011-09-09 at 10:50:23 +0200, LEVAI Daniel wrote: > > On Fri, Sep 09, 2011 at 11:43:16 +0300, Audrius Ka?ukauskas wrote: > > > On Fri, 2011-09-09 at 10:24:39 +0200, LEVAI Daniel wrote: > > > > I would like to change the versioning scheme of the ksh-openbsd package. > > > > It would be ksh-openbsd-$DATE, eg. ksh-openbsd-20110909 from now on. > > > > > > Correct me if I'm wrong, but at the moment PRGNAM=ksh and > > > VERSION=openbsd49, and you want it to change to PRGNAM=ksh-openbsd and > > > VERSION=20110909, right? If so, I don't see any problems in that. > > > > Well, it wouldn't be exactly like that. PRGNAM would stay 'ksh', and the > > version string would be s,49$,$DATE,. > > Ah, so version would be openbsd20110909? I'm asking because in your > first mail you wrote 'ksh-openbsd-20110909', and Slackware package name > convention doesn't allow hyphens in version segment. Package name > scheme looks like this: > > name-version-arch-build > > Only name segment can have additional hyphens, because pkgtools removes > three last segments in the string to figure out program name. If > package would be named as > > ksh-openbsd-20110909-i486-1_SBo > > pkgtools would treat is as ksh-openbsd. > > So your version should be openbsd20110909 or openbsd_20110909, but not > openbsd-20110909. And the program name stays the same as it is now > (ksh). Oh, I see now! Thank You for the elaborate answer. Then I think the package name will have to change. Daniel -- L?VAI D?niel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F From the_emmel at gmx.net Mon Sep 12 17:07:37 2011 From: the_emmel at gmx.net (emmel) Date: Mon, 12 Sep 2011 19:07:37 +0200 Subject: [Slackbuilds-users] Virtualbox addons and Virtualbox kernel addons In-Reply-To: References: <4E6B2905.3090500@microlinux.fr> Message-ID: <20110912170737.GA2461@pollux.mlnet> On Sat, Sep 10, 2011 at 02:17:07PM +0500, Ozan T?rky?lmaz wrote: > 2011/9/10 Nicolas Kovacs : > > > > I'm a bit confused about the virtualbox-addons and virtualbox-kernel-addons > > SlackBuilds. I know they're supposed to be *used* within the GUEST system > > (I've worked with Virtualbox on CentOS before), but where are they supposed > > to be *built*? On the host or guest system? > > If they are some systems (Slackware version and kernel version etc) > then it won't matter but if your guess different than your host, build > on guest system. Since we are talking about VirtualBox... I'm having a problem and maybe one of you can help. I have built virtualbox and the virtualbox-kernel packages on Slackware64. Now, I'm aware that Slack64 is not exactly supported (for virttualbox, nothing said about virtualbox-kernel) and neither is current - which might have something to do with it. Still, it built fine and as far as I can tell it ought to work. Except my system won't load the kernel module. dmesg says: [11687.026629] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use) [11788.213363] vboxdrv: Unknown symbol pv_irq_ops (err 0) Any ideas? What confuses me is that the modul did build without problems, I just can't use it. Any help appreciated. As a side note, the current version is 4.1.2. Wondering if there is a version bump planned for the slackbuild. -- emmel GPG signed Fingerprint: 60B4 D8E3 9617 900C 6726 168F D677 5AAD D40F CCE7 Certserver : hkp://pgp.mit.edu -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From ozan.turkyilmaz at gmail.com Mon Sep 12 17:19:56 2011 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Mon, 12 Sep 2011 22:19:56 +0500 Subject: [Slackbuilds-users] Virtualbox addons and Virtualbox kernel addons In-Reply-To: <20110912170737.GA2461@pollux.mlnet> References: <4E6B2905.3090500@microlinux.fr> <20110912170737.GA2461@pollux.mlnet> Message-ID: 2011/9/12 emmel : > Still, it built fine and as far as I can tell it ought to work. Except > my system won't load the kernel module. dmesg says: > > [11687.026629] warning: `VirtualBox' uses 32-bit capabilities (legacy > support in use) > [11788.213363] vboxdrv: Unknown symbol pv_irq_ops (err 0) > I think you lack visualization support in kernel. -- Ozan, BSc, BEng From vmj at linuxbox.fi Mon Sep 12 18:06:05 2011 From: vmj at linuxbox.fi (Mikko Varri) Date: Mon, 12 Sep 2011 21:06:05 +0300 Subject: [Slackbuilds-users] nose-1.0.0 download link broken In-Reply-To: References: Message-ID: <20110912180605.GE15855@linuxbox.fi> On Mon, Sep 05, 2011 at 11:34:00PM +0200, Xavier Maillard wrote: > > Latest version for nose is 1.1.2 thus the redirection on the website no > longer points to version 1.0.0. Consequence: 404 for 1.0.0. > > The good URL is: > http://pypi.python.org/packages/source/n/nose/nose-1.0.0.tar.gz > > Another choice would be to use lastest nose release (1.1.2) > You are right. I've been slacking off. I'll try to get to it sometime this week. -vmj From black_rider at esdebian.org Mon Sep 12 20:39:49 2011 From: black_rider at esdebian.org (Black Rider) Date: Mon, 12 Sep 2011 22:39:49 +0200 Subject: [Slackbuilds-users] Making a build that converts and mixes a .deb package Message-ID: <20110912223949.5cac7bde@whitestar> Hello. I am thinking about creating a SlackBuild for Kobo Deluxe (space shooting game) in the same fashion it was done in order to create the PorteusBuild attached to this message. As you can see, what this PorteusBuild does is to take two .deb packages (Kobo and Kobo-data), mix them and compress the whole thing as a single package. It works on Porteus and under Slackware too (yeah, it took two days to beat the last level!) Now, if I upload the build-pack, I will have to set a source for Kobodeluxe x86 and Kobodeluxe x86_64. Kobodeluxe-data is, however, architecture agnostic. I had thought about uploading kobodeluxe-data inside the SlackBuild tarball, but I guess that would be unacceptable. I have thought too about modifying the script so it downloads kobodeluxe-data from a remote file server, but I really dislike the idea (I want scripts to be as Internet agnostic as possible). Before you come with a bright idea: last time I tried to compile Kobo from source, I got a failure. There was a bug that prevented Kobo from compiling in certain versions of GCC, I think. Is there any acceptable way I could take to use these three packages (Kobodeluxe x86/x86_64 and Kobodeluxe-data) for combining in a single .tgz and stay compilant with SlackBuilds.org's policies? I don't like the idea of making two separated build scripts, as I see this stupid (you don't really need a SlackBuid script to convert two .debs and install them, right?) For those who want to try, the original PorteusBuild (which can be adapted easily to Slackware by just removing some lines) is here: http://www.porteus.org/forum/viewtopic.php?f=76&t=694 -------------- next part -------------- A non-text attachment was scrubbed... Name: kobodeluxe.PorteusBuild Type: application/octet-stream Size: 2591 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From matteo.bernardini at gmail.com Tue Sep 13 04:15:24 2011 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 13 Sep 2011 06:15:24 +0200 Subject: [Slackbuilds-users] Making a build that converts and mixes a .deb package In-Reply-To: <20110912223949.5cac7bde@whitestar> References: <20110912223949.5cac7bde@whitestar> Message-ID: FYI, builds fine here (64-current) from source with the two patches from archlinux http://projects.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/kobodeluxe From niels.horn at gmail.com Tue Sep 13 12:33:00 2011 From: niels.horn at gmail.com (Niels Horn) Date: Tue, 13 Sep 2011 09:33:00 -0300 Subject: [Slackbuilds-users] Making a build that converts and mixes a .deb package In-Reply-To: References: <20110912223949.5cac7bde@whitestar> Message-ID: On Tue, Sep 13, 2011 at 1:15 AM, Matteo Bernardini wrote: > FYI, builds fine here (64-current) from source with the two patches > from archlinux > > http://projects.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/kobodeluxe Unless it takes hours to build or needs huge amounts of free space, building from source is definitely the preferred option. -- Niels Horn From korgie at gmail.com Tue Sep 13 21:58:01 2011 From: korgie at gmail.com (korgman) Date: Wed, 14 Sep 2011 00:58:01 +0300 Subject: [Slackbuilds-users] pd-extended - wget compatible link Message-ID: <4E6FD1E9.5090808@gmail.com> Hello there. There is a better link (wget compatible) for pd-extended http://downloads.sourceforge.net/project/pure-data/pd-extended/0.42.5/Pd-0.42.5-extended.tar.gz -- http://clavisound.dyndns-server.com Michales Michaloudes From Manuel.Spam at nurfuerspam.de Wed Sep 14 19:44:56 2011 From: Manuel.Spam at nurfuerspam.de (Manuel Reimer) Date: Wed, 14 Sep 2011 21:44:56 +0200 Subject: [Slackbuilds-users] Making a build that converts and mixes a .deb package In-Reply-To: References: <20110912223949.5cac7bde@whitestar> Message-ID: Niels Horn wrote: > Unless it takes hours to build or needs huge amounts of free space, > building from source is definitely the preferred option. +1 Only very huge projects should be repackaged. Most of those projects offer prebuilt packages on their own (like LibreOffice). Yours Manuel From kingbeowulf at gmail.com Thu Sep 15 07:06:46 2011 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 15 Sep 2011 00:06:46 -0700 Subject: [Slackbuilds-users] certified nvidia drivers Message-ID: I am not yet sure what this means, but the certified nvidia drivers 208.13 (Aug 1) recently posted to the repository, have been "superseded" by Nvidia recommended version 275.28 September 7, 2011, if you check on www.nvidia.com However, over at www.geforce.com, version 280.13 is the current recommended version for Linux I'm running the 280.13 successfully and don't have the energy to maintain 2 separate families or series. As always, any feedback is welcome if you have any issues with the nvidia slackbuilds. -Ed -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From the_emmel at gmx.net Thu Sep 15 08:05:29 2011 From: the_emmel at gmx.net (emmel) Date: Thu, 15 Sep 2011 10:05:29 +0200 Subject: [Slackbuilds-users] Virtualbox addons and Virtualbox kernel addons In-Reply-To: References: <4E6B2905.3090500@microlinux.fr> <20110912170737.GA2461@pollux.mlnet> Message-ID: <20110915080529.GA2283@pollux.mlnet> On Mon, Sep 12, 2011 at 10:19:56PM +0500, Ozan T?rky?lmaz wrote: > 2011/9/12 emmel : > > Still, it built fine and as far as I can tell it ought to work. Except > > my system won't load the kernel module. dmesg says: > > > > [11687.026629] warning: `VirtualBox' uses 32-bit capabilities (legacy > > support in use) > > [11788.213363] vboxdrv: Unknown symbol pv_irq_ops (err 0) > > > > I think you lack visualization support in kernel. Never mind, I figured it out. For some reason (i.e. me being stupid) I had the kernel sources patched for xen and that clached. Works fine now. One (minor) annoyance remains, though. For some reason the Help button in the GUI doesn't find the UserManual.PDF, apparently expecting it to be installed in /. -- emmel GPG signed Fingerprint: 60B4 D8E3 9617 900C 6726 168F D677 5AAD D40F CCE7 Certserver : hkp://pgp.mit.edu -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From black_rider at esdebian.org Thu Sep 15 14:38:12 2011 From: black_rider at esdebian.org (Black Rider) Date: Thu, 15 Sep 2011 16:38:12 +0200 Subject: [Slackbuilds-users] Making a build that converts and mixes a .deb package Message-ID: <20110915163812.71d6bab5@whitestar> Niels Horn wrote: > Unless it takes hours to build or needs huge amounts of free space, > building from source is definitely the preferred option. I know. I prefer building from source too. It is just that last time I tried (and that's not much time ago) direct building didn't work, while repackaging worked in half a second. Matteo wrote: > FYI, builds fine here (64-current) from source with the two patches > from archlinux > > http://projects.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/kobodeluxe I'll have a look at those Arch patches when I find the time to do so. Thanks for the info. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From disturbed1976 at gmail.com Thu Sep 15 15:50:51 2011 From: disturbed1976 at gmail.com (Keith Richie) Date: Thu, 15 Sep 2011 11:50:51 -0400 Subject: [Slackbuilds-users] certified nvidia drivers In-Reply-To: References: Message-ID: On Thu, Sep 15, 2011 at 3:06 AM, King Beowulf wrote: > I am not yet sure what this means, but the certified nvidia drivers 208.13 > (Aug 1) recently posted to the repository, have been "superseded" by Nvidia > recommended version 275.28 September 7, 2011, if you check on www.nvidia.com > > However, over at www.geforce.com, version 280.13 is the current recommended > version for Linux > > I'm running the 280.13 successfully and don't have the energy to maintain 2 > separate families or series.? As always, any feedback is welcome if you have > any issues with the nvidia slackbuilds. > > -Ed > > -- > You! What PLANET is this! > ? ? -- McCoy, "The City on the Edge of Forever", stardate 3134.0 > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > Looks like Nvidia is releasing a type of LTS driver + a current driver. 275.28 released as the current long-lived branch release. >From the {some what} official Nvidia support forum http://www.nvnews.net/vbulletin/showthread.php?t=122606 This is a new category of releases, so I think it needs a little explanation. We've started maintaining longer-lived release branches that only take critical or low-risk fixes. These releases are intended for users of non-legacy GPUs who don't necessarily need the latest and greatest features. If you've ever used Ubuntu's LTS releases, these should be a similar idea. From thedoogster at gmail.com Thu Sep 15 16:21:32 2011 From: thedoogster at gmail.com (Doogster) Date: Thu, 15 Sep 2011 09:21:32 -0700 Subject: [Slackbuilds-users] certified nvidia drivers In-Reply-To: References: Message-ID: 275.28 is the LTS series. 280.13 is the state-of-the-art series. I would prefer to have the state-of-the-art series. On Thu, Sep 15, 2011 at 12:06 AM, King Beowulf wrote: > I am not yet sure what this means, but the certified nvidia drivers 208.13 > (Aug 1) recently posted to the repository, have been "superseded" by Nvidia > recommended version 275.28 September 7, 2011, if you check on www.nvidia.com > > However, over at www.geforce.com, version 280.13 is the current recommended > version for Linux > > I'm running the 280.13 successfully and don't have the energy to maintain 2 > separate families or series.? As always, any feedback is welcome if you have > any issues with the nvidia slackbuilds. > > -Ed > > -- > You! What PLANET is this! > ? ? -- McCoy, "The City on the Edge of Forever", stardate 3134.0 > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > From thedoogster at gmail.com Thu Sep 15 16:20:39 2011 From: thedoogster at gmail.com (Doogster) Date: Thu, 15 Sep 2011 09:20:39 -0700 Subject: [Slackbuilds-users] certified nvidia drivers In-Reply-To: References: Message-ID: http://www.nvnews.net/vbulletin/showpost.php?p=2479770&postcount=7 275.28 is the LTS On Thu, Sep 15, 2011 at 12:06 AM, King Beowulf wrote: > I am not yet sure what this means, but the certified nvidia drivers 208.13 > (Aug 1) recently posted to the repository, have been "superseded" by Nvidia > recommended version 275.28 September 7, 2011, if you check on www.nvidia.com > > However, over at www.geforce.com, version 280.13 is the current recommended > version for Linux > > I'm running the 280.13 successfully and don't have the energy to maintain 2 > separate families or series.? As always, any feedback is welcome if you have > any issues with the nvidia slackbuilds. > > -Ed > > -- > You! What PLANET is this! > ? ? -- McCoy, "The City on the Edge of Forever", stardate 3134.0 > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > From martin at lb7ye.net Thu Sep 15 21:16:30 2011 From: martin at lb7ye.net (Odd Martin Baanrud) Date: Thu, 15 Sep 2011 23:16:30 +0200 Subject: [Slackbuilds-users] Help with build script for brlapi Message-ID: <4E726B2E.8080204@lb7ye.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I'm planning to install Slackware 13.37, and gnome, from the gnome-slackbuild project. The reason for me to use gnome is that I'm blind, and gnome is the only desktop environment which so far provides accessibility. It does this using the orca screen reader. Orca supports text to speech out of the box. However, for orca to also output braille, it needs brlapi, the brltty aplication programmable interface. brlapi is not part of either the official Slackware packages, or the gnome slackbuild project. I'm not an experienced SlackBuild-script writer. So I wonder if someone on this list can take a look at it, and post a build-script in the Accessibility section on slackbuilds.org? The brlapi stuff can be downloaded here: http://www.mielke.cc/brltty/download.html And the brlapi manual can be found here: http://www.mielke.cc/brltty/doc/Manual-BrlAPI/English/BrlAPI.html The brltty program itself is provided in the official Slackware release, it's just brlapi that needs to be looked at. Thanks! Regards, Martin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk5yay4ACgkQTSwM/NWKZ6Ec9ACgz18uUqUp6NsXbLUjll6iTbv6 j2EAoIQdpRMPyqZjVHD/S9P6hD+o6FgZ =C6QH -----END PGP SIGNATURE----- From yalhcru at gmail.com Thu Sep 15 21:58:54 2011 From: yalhcru at gmail.com (B Watson) Date: Thu, 15 Sep 2011 17:58:54 -0400 Subject: [Slackbuilds-users] Help with build script for brlapi In-Reply-To: <4E726B2E.8080204@lb7ye.net> References: <4E726B2E.8080204@lb7ye.net> Message-ID: On 9/15/11, Odd Martin Baanrud wrote: > The brltty program itself is provided in the official Slackware release, > it's just brlapi that needs to be looked at. It looks like brlapi is included in the brltty package already. At least, there's a /usr/lib/libbrlapi.so, several /usr/include/brlapi* files, a bunch of man pages called brlapi_*, and brlapi bindings for python and tcl. This is a difference between Slackware and most other distros: "development" files are generally included in the same package as the binary (e.g. the SDL package doesn't need a separate SDL-devel package). It's just a bit confusing in this case because the other distros' package is named differently (brlapi instead of brltty-devel). Have you actually gotten errors trying to compile something that needs brlapi? From martin at lb7ye.net Thu Sep 15 22:23:14 2011 From: martin at lb7ye.net (Odd Martin Baanrud) Date: Fri, 16 Sep 2011 00:23:14 +0200 Subject: [Slackbuilds-users] Help with build script for brlapi In-Reply-To: References: <4E726B2E.8080204@lb7ye.net> Message-ID: <4E727AD2.6070404@lb7ye.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, On 09/15/2011 11:58 PM, B Watson wrote: > It looks like brlapi is included in the brltty package already. At least, > there's a /usr/lib/libbrlapi.so, several /usr/include/brlapi* files, > a bunch of man pages called brlapi_*, and brlapi bindings for python > and tcl. Ahhh, I didn't know that! Seems that I was confused over the brlapi packages I've seen in other distros. Thanks for the clear-up! > Have you actually gotten errors trying to compile something that needs > brlapi? I have not tried to compile something that needs brlapi at all, because I thaught the brlapi packages was needed. Regards, Martin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk5yetIACgkQTSwM/NWKZ6HEuQCgkDxQNUDkfSGCJiX1U17dmduI dnMAoIfwN/MX8sqFVfNTE7LDCUc9uGXJ =VqS3 -----END PGP SIGNATURE----- From kingbeowulf at gmail.com Fri Sep 16 00:51:23 2011 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 15 Sep 2011 17:51:23 -0700 Subject: [Slackbuilds-users] certified nvidia drivers In-Reply-To: References: Message-ID: Thanks for the clarification. I don't know why I couldn't figure that out when I checked...but it was after midnight BTW, is anyone on this list using any of the nvidia-legacy drivers? At the moment, all I have left running are a 7600GS, GT430 and GT550 for testing. My old TNT2, GF256 DDR, GF4 TI 4800 are long gone. Since nouveau is almost there, I'm thinking about dropping support for the old chipsets not supported on the 28x series. -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Fri Sep 16 03:22:12 2011 From: yalhcru at gmail.com (B Watson) Date: Thu, 15 Sep 2011 23:22:12 -0400 Subject: [Slackbuilds-users] certified nvidia drivers In-Reply-To: References: Message-ID: On 9/15/11, King Beowulf wrote: > > BTW, is anyone on this list using any of the nvidia-legacy drivers? At the > moment, all I have left running are a 7600GS, GT430 and GT550 for testing. > My old TNT2, GF256 DDR, GF4 TI 4800 are long gone. Since nouveau is almost > there, I'm thinking about dropping support for the old chipsets not > supported on the 28x series. I was using nvidia-legacy96 until about a week ago. I might be re-using that old card in someone else's Slackware machine in the near future (it's an upgrade compared to the onboard intel graphics he's stuck with now). He's in the "baby steps" phase of learning to use Slackware, so effectively I'm sysadmin of his pile-of-parts PC. Nouveau actually sucks pretty horribly on that card BTW. 3D isn't functional, and 2D is slow (takes maybe 1/4 second to redraw a fullscreen xterm, you can actually see it drawing). With the legacy96 driver, 3D works (fast enough for quake 3 at 1024x768 at least, but not doom 3 at any res) and 2D is very snappy. So I'd vote for not dropping legacy96 in favor of nouveau just yet... Would I take over maintenance of legacy96? Probably, if I really do end up re-using the card that needs it. Otherwise I'd have no way to test new versions really. From info at microlinux.fr Fri Sep 16 20:46:42 2011 From: info at microlinux.fr (Nicolas Kovacs) Date: Fri, 16 Sep 2011 22:46:42 +0200 Subject: [Slackbuilds-users] certified nvidia drivers In-Reply-To: References: Message-ID: <4E73B5B2.4080200@microlinux.fr> Le 16/09/2011 02:51, King Beowulf a ?crit : > Thanks for the clarification. I don't know why I couldn't figure that > out when I checked...but it was after midnight > > BTW, is anyone on this list using any of the nvidia-legacy drivers? Yes. Me. All the time. I often install Slackware on older Hardware, and I regularly use both legacy drivers for NVidia cards. Please don't drop support for these. Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From thedoogster at gmail.com Fri Sep 16 22:00:00 2011 From: thedoogster at gmail.com (Doogster) Date: Fri, 16 Sep 2011 15:00:00 -0700 Subject: [Slackbuilds-users] certified nvidia drivers In-Reply-To: <4E73B5B2.4080200@microlinux.fr> References: <4E73B5B2.4080200@microlinux.fr> Message-ID: King Beowulf, The state-of-the-art driver is more important to me, so that's the series I would personally like to see you focus on. There should be room now for a separate nvidia-legacy-kernel and nvidia-legacy-driver series of SlackBuilds. If you don't want to maintain those, then I'm sure that someone will step up. On Fri, Sep 16, 2011 at 1:46 PM, Nicolas Kovacs wrote: > Le 16/09/2011 02:51, King Beowulf a ?crit : >> >> Thanks for the clarification. ?I don't know why I couldn't figure that >> out when I checked...but it was after midnight >> >> BTW, is anyone on this list using any of the nvidia-legacy drivers? > > Yes. Me. All the time. I often install Slackware on older Hardware, and I > regularly use both legacy drivers for NVidia cards. Please don't drop > support for these. > > Niki > -- > Microlinux - Solutions informatiques 100% Linux et logiciels libres > 7, place de l'?glise - 30730 Montpezat > Web ?: http://www.microlinux.fr > Mail : info at microlinux.fr > T?l. : 04 66 63 10 32 > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From pc_warner at yahoo.com Sat Sep 17 01:23:29 2011 From: pc_warner at yahoo.com (Phillip Warner) Date: Fri, 16 Sep 2011 18:23:29 -0700 (PDT) Subject: [Slackbuilds-users] certified nvidia drivers In-Reply-To: Message-ID: <1316222609.35582.YahooMailClassic@web161703.mail.bf1.yahoo.com> --- On Thu, 9/15/11, King Beowulf wrote: BTW, is anyone on this list using any of the nvidia-legacy drivers?? At the moment, all I have left running are a 7600GS, GT430 and GT550 for testing.? My old TNT2, GF256 DDR, GF4 TI 4800 are long gone.? Since nouveau is almost there, I'm thinking about dropping support for the old chipsets not supported on the 28x series. I use the legacy173 slackBuilds. ?nouveau is stable, but VERY slow for me compared to the performance I get with Nvidia's binary drivers. --phillip -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Sat Sep 17 06:45:32 2011 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 16 Sep 2011 23:45:32 -0700 Subject: [Slackbuilds-users] certified nvidia drivers In-Reply-To: <1316222609.35582.YahooMailClassic@web161703.mail.bf1.yahoo.com> References: <1316222609.35582.YahooMailClassic@web161703.mail.bf1.yahoo.com> Message-ID: A plenty good enough survey for me. I can continue to support the legacy nvidia drivers. I was just wondering if any one was using them. Pending wife "to-do" list this weekend, I'll take a look at the current state or affairs. I know Nvidia has posted a few updates for newer kernel support. -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mjjzf at syntaktisk.dk Sat Sep 17 23:47:59 2011 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fejer?=) Date: Sun, 18 Sep 2011 01:47:59 +0200 Subject: [Slackbuilds-users] MuPDF source: Broken link Message-ID: <20110918014759.02896efb@espero.syntaktisk.dk> Seems like the source download link for MuPDF at http://slackbuilds.org/repository/13.37/office/mupdf/ is broken. There is a 0.9 release, and they seem to have pulled the sources for the 0.8 series. I modified the SlackBuild to 0.9, and it built without any issues. CC maintainer. -mjjzf From mjjzf at syntaktisk.dk Sat Sep 17 23:51:17 2011 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fejer?=) Date: Sun, 18 Sep 2011 01:51:17 +0200 Subject: [Slackbuilds-users] MuPDF source: Broken link Message-ID: <20110918015117.40b24d3b@espero.syntaktisk.dk> Seems like the source download link for MuPDF at http://slackbuilds.org/repository/13.37/office/mupdf/ is broken. There is a 0.9 release, and they seem to have pulled the sources for the 0.8 series. I modified the SlackBuild to 0.9, and it built without any issues. CC maintainer. -mjjzf From dragonwisard at gmail.com Sun Sep 18 04:55:27 2011 From: dragonwisard at gmail.com (Ben Mendis) Date: Sun, 18 Sep 2011 00:55:27 -0400 Subject: [Slackbuilds-users] MuPDF source: Broken link In-Reply-To: <20110918015117.40b24d3b@espero.syntaktisk.dk> References: <20110918015117.40b24d3b@espero.syntaktisk.dk> Message-ID: I just tried this on Slackware 13.37 (32-bit) and it worked fine with the 0.9 release. What platform are you on? What error do you get? On Sat, Sep 17, 2011 at 7:51 PM, Morten Juhl-Johansen Z?lde-Fejer < mjjzf at syntaktisk.dk> wrote: > Seems like the source download link for MuPDF at > http://slackbuilds.org/repository/13.37/office/mupdf/ is broken. > There is a 0.9 release, and they seem to have pulled the sources for > the 0.8 series. I modified the SlackBuild to 0.9, and it built without > any issues. > > CC maintainer. > > -mjjzf > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Sun Sep 18 06:51:31 2011 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 18 Sep 2011 08:51:31 +0200 Subject: [Slackbuilds-users] MuPDF source: Broken link In-Reply-To: <20110918014759.02896efb@espero.syntaktisk.dk> References: <20110918014759.02896efb@espero.syntaktisk.dk> Message-ID: tried it now: seems libraries get installed in /usr/lib on x86_64, so I added this before make # fix library installation path sed -i "s/(prefix)\/lib/(prefix)\/lib$LIBDIRSUFFIX/" Makefile Matteo From nishant at mnspace.net Sun Sep 18 14:27:57 2011 From: nishant at mnspace.net (Nishant Limbachia) Date: Sun, 18 Sep 2011 09:27:57 -0500 Subject: [Slackbuilds-users] phpmyadmin in approved Message-ID: <4E75FFED.9090704@mnspace.net> Admins, Can you please remove phpmyadmin from approved? There's a new version (3.4.5) out with security fixes and I would like to submit that. Thanks! -- Nishant Limbachia nishant at mnspace.net GPG Key: 0x0FF9D6D5 GPG Fingerprint: CC77 2954 DBDD CA46 49D5 BC90 786E 5DA2 0FF9 D6D5 From mjjzf at syntaktisk.dk Tue Sep 20 22:21:57 2011 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fejer?=) Date: Wed, 21 Sep 2011 00:21:57 +0200 Subject: [Slackbuilds-users] Flash: Broken link Message-ID: <20110921002157.2a2a712b@espero.syntaktisk.dk> Seems the Flash download link is broken on http://slackbuilds.org/repository/13.37/multimedia/flash-player-plugin/ Yours, M __ Morten Juhl-Johansen Z?lde-Fejer www.syntaktisk.dk * mjjzf at syntaktisk.dk From artourter at gmail.com Tue Sep 20 22:29:42 2011 From: artourter at gmail.com (Greg' Ar Tourter) Date: Tue, 20 Sep 2011 23:29:42 +0100 Subject: [Slackbuilds-users] Flash: Broken link In-Reply-To: <20110921002157.2a2a712b@espero.syntaktisk.dk> References: <20110921002157.2a2a712b@espero.syntaktisk.dk> Message-ID: Hi, Yes as this is the development version of the new 11.0 release, adobe removes it as soon as a new version is released. As Adobe release RC1, beta2 is now gone. I believe, the new slackbuild is in ready and should be out at the next public release, (provided Adobe doesn't release RC2 by then at which point the new one will not work again):-P Now why people cannot leave stuff in place, I don't understand, but it is not an adobe specific problem. Cheers ArTourter On 20 September 2011 23:21, Morten Juhl-Johansen Z?lde-Fejer wrote: > Seems the Flash download link is broken on > http://slackbuilds.org/repository/13.37/multimedia/flash-player-plugin/ > > Yours, > M > __ > Morten Juhl-Johansen Z?lde-Fejer > www.syntaktisk.dk * mjjzf at syntaktisk.dk > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From pr0f3ss0r1492 at yahoo.com Tue Sep 20 23:15:03 2011 From: pr0f3ss0r1492 at yahoo.com (Ottavio) Date: Wed, 21 Sep 2011 00:15:03 +0100 Subject: [Slackbuilds-users] Flash: Broken link In-Reply-To: <20110921002157.2a2a712b@espero.syntaktisk.dk> References: <20110921002157.2a2a712b@espero.syntaktisk.dk> Message-ID: On 20 September 2011 23:21, Morten Juhl-Johansen Z?lde-Fejer wrote: > Seems the Flash download link is broken on > http://slackbuilds.org/repository/13.37/multimedia/flash-player-plugin/ WARNING: first post from a complete sb n00b, be patient: is there really a need for a slackbuild to install the flash plugin? All one has to do is to unpack the file and copy the libflashplayer.so to /usr/lib[64]/firefox-[version]/plugins/ (I think)? -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From acummingsus at gmail.com Wed Sep 21 04:14:49 2011 From: acummingsus at gmail.com (Al) Date: Tue, 20 Sep 2011 21:14:49 -0700 Subject: [Slackbuilds-users] Flash: Broken link In-Reply-To: References: <20110921002157.2a2a712b@espero.syntaktisk.dk> Message-ID: <4E7964B9.8060900@gmail.com> Ottavio wrote: > On 20 September 2011 23:21, Morten Juhl-Johansen Z?lde-Fejer > wrote: > >> Seems the Flash download link is broken on >> http://slackbuilds.org/repository/13.37/multimedia/flash-player-plugin/ >> > > > is there really a need for a slackbuild to install the flash plugin? > All one has to do is to unpack the file and copy the libflashplayer.so > to /usr/lib[64]/firefox-[version]/plugins/ (I think)? > That's /usr/lib/mozilla/plugins unless it's very recently changed. I've copied the flash plugin to there (and, BTW, I've found that to do so, it works). But then a removepkg flashplayer does nothing. (instead, you must go to the folder and remove the flashplayer). So, **it depends upon what you want** (as to a whether or not a slack pkg is needed). Go slackbuilds admins and contributors and thank you very much for the super fine, excellent job that all of you do. It's on my wish list that when I get enough time that I'd then sufficiently learn the slackbuild.whatever_app script -- Alan. From erik at slackbuilds.org Wed Sep 21 07:12:29 2011 From: erik at slackbuilds.org (Erik Hanson) Date: Wed, 21 Sep 2011 02:12:29 -0500 Subject: [Slackbuilds-users] Flash: Broken link In-Reply-To: References: <20110921002157.2a2a712b@espero.syntaktisk.dk> Message-ID: <4E798E5D.2070200@slackbuilds.org> On 09/20/2011 06:15 PM, Ottavio wrote: > On 20 September 2011 23:21, Morten Juhl-Johansen Z?lde-Fejer > wrote: >> Seems the Flash download link is broken on >> http://slackbuilds.org/repository/13.37/multimedia/flash-player-plugin/ > > WARNING: first post from a complete sb n00b, be patient: > is there really a need for a slackbuild to install the flash plugin? > All one has to do is to unpack the file and copy the libflashplayer.so > to /usr/lib[64]/firefox-[version]/plugins/ (I think)? There isn't any need to, however that logic can be extended to all SlackBuilds/packages. Any way, the package will also contain something called "kcm_adobe_flash_player.so" which I gather is for KDE4, and the flash-player-properties binary along with several other minor files. The package makes it easy to install/remove all of this. However if you're more comfortable doing it by hand then you may as well just drop the .so in ~/.mozilla/plugins with each new version. -- Erik Hanson From niels.horn at gmail.com Wed Sep 21 23:42:09 2011 From: niels.horn at gmail.com (Niels Horn) Date: Wed, 21 Sep 2011 20:42:09 -0300 Subject: [Slackbuilds-users] Updates - 20110921.1 Message-ID: Wed Sep 21 22:54:36 UTC 2011 audio/rosegarden: Updated for version 11.06. desktop/compiz-boxmenu: Added (fork of compiz-deskmenu) development/avrdude: Updated for version 5.11. development/cudatoolkit: Added (parallel computing architecture) development/mono-debugger: Updated for version 2.10. development/monodevelop-database: Updated for version 2.6. development/monodevelop-debugger-gdb: Updated for version 2.6. development/monodevelop-python: Updated for version 2.6. development/monodevelop: Updated for version 2.6. development/wxHexEditor: Updated for version 0.11. graphics/FreeCAD: Updated for version 0.11.3729. graphics/gnome-themes-extras: Added (gnome metathemes and icons) graphics/lilypond: Updated for version 2.14.2. graphics/mftrace: Updated for version 1.2.17. graphics/potrace: Updated for version 1.10. haskell/haskell-base64-bytestring: Added (base64 encoding/decoding) haskell/haskell-citeproc-hs: Added (implementation of CSL) haskell/haskell-dlist: Added (differences lists for Haskell) haskell/haskell-json: Added (JSON implementation for Haskell) haskell/haskell-pandoc-types: Added (type definitions for Pandoc) haskell/haskell-tagsoup: Added (HTML/XML parser for Haskell) haskell/haskell-texmath: Updated for version 0.5.0.1. libraries/nltk: Updated for version 2.0.1rc1. misc/g15daemon: Patch to fix Gn keys and suspend fixes. multimedia/flash-player-plugin: Updated for version 11_rc1. multimedia/guvcview: Updated for version 1.5.0. multimedia/makemkv: Added (DVD/Blu-ray ripper and transcoder) network/claws-mail-extra-plugins: Fixed MD5SUM network/dillo: Updated for version 2.2.1. network/ebtables: Added (Ethernet frame filtering on a Linux bridge) network/ferm: Added (For Easy Rule Making) network/loic: Added (open source network attack application) network/phpmyadmin: Updated for version 3.4.4. network/vidalia: Updated for version 0.2.14. office/pandoc: Updated for version 1.8.2.1. perl/perl-File-Slurp: Build clean up, removed ref. to old perl. perl/perl-xml-sax: Fix doinst.sh path and clean up build. system/avermedia-a867: Added (AVerMedia A867 DVB-T kernel module) system/freedup: Added (Duplicate file finder and linker) system/gpsd: Downgraded to version 2.95 due to API breakage. system/t1utils: Updated for version 1.37. From martin at lb7ye.net Fri Sep 23 18:03:29 2011 From: martin at lb7ye.net (Odd Martin Baanrud) Date: Fri, 23 Sep 2011 20:03:29 +0200 Subject: [Slackbuilds-users] Skype on x86_64 Message-ID: <4E7CC9F1.9030206@lb7ye.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I just built Skype using the skype SlackBuild script on my x86_64 system, but the skype package is an i486 package. Can I install this on my stock x86_64 system, or do I need to install some sort of compatibility stuff first? Regards, Martin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk58yfEACgkQTSwM/NWKZ6Hz1ACgpbNfh3/9AWKPDTBf4w1qPDLA bwYAn15Czzq9yq+3QV2+VaCbk+unbEi6 =gyRh -----END PGP SIGNATURE----- From mickeytintincolle at yahoo.fr Fri Sep 23 18:15:07 2011 From: mickeytintincolle at yahoo.fr (/dev/ammo42) Date: Fri, 23 Sep 2011 20:15:07 +0200 Subject: [Slackbuilds-users] Skype on x86_64 In-Reply-To: <4E7CC9F1.9030206@lb7ye.net> References: <4E7CC9F1.9030206@lb7ye.net> Message-ID: <20110923201507.3f314881@ammo42.ens-lyon.fr> > Hello, > > I just built Skype using the skype SlackBuild script on my x86_64 > system, but the skype package is an i486 package. > Can I install this on my stock x86_64 system, or do I need to install > some sort of compatibility stuff first? The default Slackware64 installation doesn't include the multilib libraries necessary to run x86 programs. You need either: -A Slackware32 chroot -A set of multilib libraries, which you can get/build for example at http://connie.slackware.com/~alien/multilib/ From mjjzf at syntaktisk.dk Sat Sep 24 00:30:37 2011 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fejer?=) Date: Sat, 24 Sep 2011 02:30:37 +0200 Subject: [Slackbuilds-users] Evince browser Message-ID: <20110924023037.1b3cd37a@espero.syntaktisk.dk> Dear all, I built Evince from the Slackbuild and run it with Xfce. However, I see that it does not accept external, i.e. web links - it simply says "unable to open external link. Operation not supported." Is this fixable, or is that the price od building a Gnome component without Gnome support? Yours, M __ Morten Juhl-Johansen Z?lde-Fejer www.syntaktisk.dk * mjjzf at syntaktisk.dk From mario at slackverse.org Sat Sep 24 07:31:37 2011 From: mario at slackverse.org (Mario) Date: Sat, 24 Sep 2011 09:31:37 +0200 Subject: [Slackbuilds-users] Skype on x86_64 In-Reply-To: <20110923201507.3f314881@ammo42.ens-lyon.fr> References: <4E7CC9F1.9030206@lb7ye.net> <20110923201507.3f314881@ammo42.ens-lyon.fr> Message-ID: <4E7D8759.9040807@slackverse.org> On 09/23/2011 08:15 PM, /dev/ammo42 wrote: >> Hello, >> >> I just built Skype using the skype SlackBuild script on my x86_64 >> system, but the skype package is an i486 package. >> Can I install this on my stock x86_64 system, or do I need to install >> some sort of compatibility stuff first? > The default Slackware64 installation doesn't include the multilib > libraries necessary to run x86 programs. > You need either: > -A Slackware32 chroot > -A set of multilib libraries, which you can get/build for example at > http://connie.slackware.com/~alien/multilib/ And if you are going with the multilib option, heres a minimal list of dependancies that skype needs: These replace original packages (upgradepkg): gcc gcc-g++ glibc And these you can just installpkg, they do not replace anything: alsa-lib-compat32 expat-compat32 fontconfig-compat32 freetype-compat32 glib2-compat32 libICE-compat32 libSM-compat32 libX11-compat32 libXScrnSaver-compat32 libXau-compat32 libXdmcp-compat32 libXext-compat32 libXrender-compat32 libXv-compat32 libpng-compat32 libxcb-compat32 qt-compat32 util-linux-compat32 zlib-compat32 Sometimes people just need skype, but if you need to run other 32bit only apps, full compat32 should be preffered. Hope it helps, mario > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- "The power to command frequently causes failure to think." From dn2010 at km.ru Sat Sep 24 05:44:49 2011 From: dn2010 at km.ru (Daniil Bratashov) Date: Sat, 24 Sep 2011 09:44:49 +0400 Subject: [Slackbuilds-users] Evince browser In-Reply-To: <20110924023037.1b3cd37a@espero.syntaktisk.dk> References: <20110924023037.1b3cd37a@espero.syntaktisk.dk> Message-ID: <20110924094449.428390aa@darkstar.example.net> On Sat, 24 Sep 2011 02:30:37 +0200 Morten Juhl-Johansen Z?lde-Fejer wrote: > Is this fixable, or is that the price od building a Gnome component > without Gnome support? One need to build evince with gvfs to make web links work. WBR, Daniil Bratashov. . From martin at lb7ye.net Sat Sep 24 10:08:18 2011 From: martin at lb7ye.net (Odd Martin Baanrud) Date: Sat, 24 Sep 2011 12:08:18 +0200 Subject: [Slackbuilds-users] Skype on x86_64 In-Reply-To: <4E7D8759.9040807@slackverse.org> References: <4E7CC9F1.9030206@lb7ye.net> <20110923201507.3f314881@ammo42.ens-lyon.fr> <4E7D8759.9040807@slackverse.org> Message-ID: <4E7DAC12.6050204@lb7ye.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Mario, Thanks for all the info! I wondered how I could make my x86_64 system compatible with 32-bit programs. I'll take a look at the link you posted. Regards, Martin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk59rBIACgkQTSwM/NWKZ6HJXgCgvW6bQEt1xPRsNx22ntZPf9Nv zxwAniB9j+58utH4kTH57hJ7QYv7RCkO =rBIl -----END PGP SIGNATURE----- From rshepard at appl-ecosys.com Sat Sep 24 15:11:04 2011 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 24 Sep 2011 08:11:04 -0700 (PDT) Subject: [Slackbuilds-users] Cannot Build OpenCASCADE Message-ID: I'd like to use FreeCAD for 2D designs but I cannot build OpenCASCADE (Slackware-13.1/32-bit running on an AMD Athlon II X2 255 Processor (dual-core) with 4G RAM. Because the build requires ~2.5G disk space and /tmp has only ~2.6G free I changed the .SlackBuild to point to ~/workspace which has > 100G free. The problem is that sometime during the build the system shuts down. This happened twice yesterday afternoon when the outside temperature was about 81F (and about 88F here at my desk). I had this problem with building the latest TeXLive which was resolved by running the build in the early morning when the outside temperature is < 60F. Today, this did not work. At my desk the temperature is ~74F (but < 60F outside). All I see in /var/log/messages is: Sep 24 06:50:09 salmo -- MARK -- Sep 24 07:10:09 salmo -- MARK -- Sep 24 07:36:45 salmo syslogd 1.4.1: restart. So some time after 07:10:09 the system shut down. ~/workspace/package-OpenCASCADE/ shows 4.0K of disk space while ~/workspace/OpenCASCADE-6.5.1/ occupies 1.6G of disk space. df -h tells me there currently is 154G available in /home. This seems to be a problem only with very large applications. I'd greatly appreciate any insights on why this might be occurring and what, if anything, I can do to build large applications any time. TIA, Rich From pr0f3ss0r1492 at yahoo.com Sat Sep 24 15:15:35 2011 From: pr0f3ss0r1492 at yahoo.com (Ottavio) Date: Sat, 24 Sep 2011 16:15:35 +0100 Subject: [Slackbuilds-users] Cannot Build OpenCASCADE In-Reply-To: References: Message-ID: On 24 September 2011 16:11, Rich Shepard wrote: > ?I'd like to use FreeCAD for 2D designs but I cannot build OpenCASCADE > (Slackware-13.1/32-bit running on an AMD Athlon II X2 255 Processor > (dual-core) with 4G RAM. Because the build requires ~2.5G disk space and > /tmp has only ~2.6G free I changed the .SlackBuild to point to ~/workspace > which has > 100G free. Have you tried mounting tmpfs on /tmp ? If 4 G is not enough, it will use swap (see also my post on slackware uk lug mailing list about this). -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From rshepard at appl-ecosys.com Sat Sep 24 15:24:18 2011 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 24 Sep 2011 08:24:18 -0700 (PDT) Subject: [Slackbuilds-users] Cannot Build OpenCASCADE In-Reply-To: References: Message-ID: On Sat, 24 Sep 2011, Ottavio wrote: > Have you tried mounting tmpfs on /tmp ? If 4 G is not enough, it will use > swap (see also my post on slackware uk lug mailing list about this). Ottavio, No, I haven't. According to 'df -h' tmpfs 1.7G 0 1.7G 0% /dev/shm I don't know the purpose or function of tmpfs, but my home directory has 154G available on that partition. Isn't that sufficient? Thanks, Rich From pr0f3ss0r1492 at yahoo.com Sat Sep 24 16:13:27 2011 From: pr0f3ss0r1492 at yahoo.com (Ottavio) Date: Sat, 24 Sep 2011 17:13:27 +0100 Subject: [Slackbuilds-users] Cannot Build OpenCASCADE In-Reply-To: References: Message-ID: On 24 September 2011 16:24, Rich Shepard wrote: > ?No, I haven't. According to 'df -h' > tmpfs ? ? ? ? ? ? ? ? 1.7G ? ? 0 ?1.7G ? 0% /dev/shm This only means that /dev/shm is using 1.7 of (probably virtual) ram ( a bit too much I think). But if you have 4G of ram you still have (4 - 1.7) G of ram available + swap. If you mount tmpfs on /tmp, /tmp will be located in ram + swap. Then you can change the .SlackBuild to point to /tmp. I have this line in /etc/fstab: tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0 You can take the "noatime" out of that line. -- Ottavio A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From rshepard at appl-ecosys.com Sat Sep 24 16:56:56 2011 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 24 Sep 2011 09:56:56 -0700 (PDT) Subject: [Slackbuilds-users] Cannot Build OpenCASCADE In-Reply-To: References: Message-ID: On Sat, 24 Sep 2011, Ottavio wrote: > But if you have 4G of ram you still have (4 - 1.7) G of ram available + > swap. If you mount tmpfs on /tmp, /tmp will be located in ram + swap. Then > you can change the .SlackBuild to point to /tmp. I have 8G swap space. Does it matter where .SlackBuild points? > I have this line in /etc/fstab: > tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0 > You can take the "noatime" out of that line. What is the role of tmpfs during a SlackBuild? If there's sufficient disk space is tmpfs used at all? I understand that it functions like a RAM disk, but if there's ~6G RAM available for the build, and the swap space, why does it crash the machine? I'm trying to understand so I can avoid the inconvenience of a reboot. Thanks, Rich From asamardzic at gmail.com Sat Sep 24 19:18:20 2011 From: asamardzic at gmail.com (Aleksandar Samardzic) Date: Sat, 24 Sep 2011 21:18:20 +0200 Subject: [Slackbuilds-users] Cannot Build OpenCASCADE In-Reply-To: References: Message-ID: On Sat, Sep 24, 2011 at 5:11 PM, Rich Shepard wrote: > > [ ... ] > > ?The problem is that sometime during the build the system shuts down. This > happened twice yesterday afternoon when the outside temperature was about > 81F (and about 88F here at my desk). I had this problem with building the > latest TeXLive which was resolved by running the build in the early morning > when the outside temperature is < 60F. Today, this did not work. > > [ ... ] > It could be that ACPI automatically shut your machine down, due to too high CPU temperature. You may wist to try to clean, or replace, your CPU fan, as well as to vacuum your machine air inlets. Also, you may try with setting your CPU freq, using cpufreq-set, to lowest allowed value, and then to re-try compilation. Regards, Alex From rshepard at appl-ecosys.com Sat Sep 24 20:01:21 2011 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 24 Sep 2011 13:01:21 -0700 (PDT) Subject: [Slackbuilds-users] Cannot Build OpenCASCADE In-Reply-To: References: Message-ID: On Sat, 24 Sep 2011, Aleksandar Samardzic wrote: > It could be that ACPI automatically shut your machine down, due to too > high CPU temperature. You may wist to try to clean, or replace, your CPU > fan, as well as to vacuum your machine air inlets. Also, you may try with > setting your CPU freq, using cpufreq-set, to lowest allowed value, and > then to re-try compilation. Alex, I assumed it was due to incipient CPU overheating. I've been meaning to clean the inside of the case but haven't yet done it. But, I will. Thanks, Rich From niels.horn at gmail.com Sat Sep 24 19:58:45 2011 From: niels.horn at gmail.com (Niels Horn) Date: Sat, 24 Sep 2011 16:58:45 -0300 Subject: [Slackbuilds-users] Cannot Build OpenCASCADE In-Reply-To: References: Message-ID: On Sat, Sep 24, 2011 at 4:18 PM, Aleksandar Samardzic wrote: > On Sat, Sep 24, 2011 at 5:11 PM, Rich Shepard wrote: >> >> ?[ ... ] >> >> ?The problem is that sometime during the build the system shuts down. This >> happened twice yesterday afternoon when the outside temperature was about >> 81F (and about 88F here at my desk). I had this problem with building the >> latest TeXLive which was resolved by running the build in the early morning >> when the outside temperature is < 60F. Today, this did not work. >> >> ?[ ... ] >> > > It could be that ACPI automatically shut your machine down, due to too > high CPU temperature. ?You may wist to try to clean, or replace, your > CPU fan, as well as to vacuum your machine air inlets. ?Also, you may > try with setting your CPU freq, using cpufreq-set, to lowest allowed > value, and then to re-try compilation. > > Regards, > Alex > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > If' you don't mind "cheating", you can get pre-built packages from my site: http://www.nielshorn.net/slackware/slack_pkg.php -- Niels Horn From rshepard at appl-ecosys.com Sat Sep 24 20:39:30 2011 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 24 Sep 2011 13:39:30 -0700 (PDT) Subject: [Slackbuilds-users] Cannot Build OpenCASCADE In-Reply-To: References: Message-ID: On Sat, 24 Sep 2011, Niels Horn wrote: > If' you don't mind "cheating", you can get pre-built packages from my > site: http://www.nielshorn.net/slackware/slack_pkg.php Niels, Thank you. I don't see using pre-built packages as cheating. After all, the goal is to have running applications. If I wanted to build everything from source I'd be running Gentoo and doing nothing but compiling, linking, and installing the distribution. :-) Thanks, Rich From mjjzf at syntaktisk.dk Sun Sep 25 05:18:47 2011 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fejer?=) Date: Sun, 25 Sep 2011 07:18:47 +0200 Subject: [Slackbuilds-users] Evince browser In-Reply-To: <20110924094449.428390aa@darkstar.example.net> References: <20110924023037.1b3cd37a@espero.syntaktisk.dk> <20110924094449.428390aa@darkstar.example.net> Message-ID: <20110925071847.1387868f@espero.syntaktisk.dk> On Sat, 24 Sep 2011 09:44:49 +0400 Daniil Bratashov wrote: > On Sat, 24 Sep 2011 02:30:37 +0200 > Morten Juhl-Johansen Z?lde-Fejer wrote: > > > Is this fixable, or is that the price od building a Gnome component > > without Gnome support? > > One need to build evince with gvfs to make web links work. > > WBR, Daniil Bratashov. Right, okay. Would this need to be done explicitly, or will it pick it up automagically, do you know? Maintainer Michiel, would you consider making a note of Gvfs in the Evince README? Also, a little confusing: DVI support is mentioned in the Evince description, but the script builds --without-dvi. As always, thank you all for your efforts. Sincerely, Morten __ Morten Juhl-Johansen Z?lde-Fejer www.syntaktisk.dk * mjjzf at syntaktisk.dk From korgie at gmail.com Sun Sep 25 15:07:59 2011 From: korgie at gmail.com (korgman) Date: Sun, 25 Sep 2011 18:07:59 +0300 Subject: [Slackbuilds-users] youtube-dl is obsolete Message-ID: <4E7F43CF.2040201@gmail.com> Hello there, youtube-dl is obsolete (not working) Can you update please? New version seems fine http://rg3.github.com/youtube-dl/download.html CC the SBo list. -- Michales Michaloudes From dn2010 at km.ru Sun Sep 25 16:49:24 2011 From: dn2010 at km.ru (Daniil Bratashov) Date: Sun, 25 Sep 2011 20:49:24 +0400 Subject: [Slackbuilds-users] Evince browser In-Reply-To: <20110925071847.1387868f@espero.syntaktisk.dk> References: <20110924023037.1b3cd37a@espero.syntaktisk.dk> <20110924094449.428390aa@darkstar.example.net> <20110925071847.1387868f@espero.syntaktisk.dk> Message-ID: <20110925204924.6018eb0f@darkstar.example.net> On Sun, 25 Sep 2011 07:18:47 +0200 Morten Juhl-Johansen Z?lde-Fejer wrote: > Would this need to be done explicitly, or will it pick it > up automagically, do you know? In GSB [1] it is done via --enable-nautilus flag. And list of requirements to build evince with gnome support is large, you can look at slack-required files there. [1] http://gnomeslackbuild.org/ WBR, Daniil Bratashov. . From schnee72 at gmail.com Wed Sep 28 23:46:00 2011 From: schnee72 at gmail.com (Dustin Schnee) Date: Wed, 28 Sep 2011 18:46:00 -0500 Subject: [Slackbuilds-users] avrdude in approved list Message-ID: <4E83B1B8.7030406@gmail.com> I just completed an update to the avrdude SlackBuild that I am the maintainer of, and I see that an update is already sitting in the approved queue. Perhaps someone got impatient with the time I took to get the update submitted, but I hadn't given up maintainer-ship to anyone. I just wanted to make sure there wasn't a problem. Thanks, Dustin From niels.horn at gmail.com Thu Sep 29 00:29:56 2011 From: niels.horn at gmail.com (Niels Horn) Date: Wed, 28 Sep 2011 21:29:56 -0300 Subject: [Slackbuilds-users] avrdude in approved list In-Reply-To: <4E83B1B8.7030406@gmail.com> References: <4E83B1B8.7030406@gmail.com> Message-ID: On Wed, Sep 28, 2011 at 8:46 PM, Dustin Schnee wrote: > I just completed an update to the avrdude SlackBuild that I am the > maintainer of, and I see that an update is already sitting in the approved > queue. Perhaps someone got impatient with the time I took to get the update > submitted, but I hadn't given up maintainer-ship to anyone. I just wanted to > make sure there wasn't a problem. > > Thanks, > Dustin > _______________________________________________ Hi, The "update" in the approved queue is just to fix a wrong md5sum... nothing else was changed: http://slackbuilds.org/cgit/slackbuilds/commit/?h=niels&id=a6b0f8070 -- Niels Horn From niels.horn at gmail.com Thu Sep 29 22:40:08 2011 From: niels.horn at gmail.com (Niels Horn) Date: Thu, 29 Sep 2011 19:40:08 -0300 Subject: [Slackbuilds-users] Updates - 20110929.1 Message-ID: Thu Sep 29 22:06:59 UTC 2011 academic/EMBOSS: Added patch with bug-fixes. academic/PhyML: Updated for version 20110526. academic/clustalo: Added (protein sequence alignment program) audio/hydrogen: Fixed doinst.sh installation. audio/podget: Updated for version 0.6.2. desktop/bashrun2: Updated for version 0.2.2. desktop/cwp: Updated for version 1.5.5. desktop/icewm: Updated for version 1.3.7. desktop/oxygen-gtk: Updated for version 1.1.2. desktop/wmname: Added (print/set the window manager name) development/alloy: Added (lightweight modelling language) development/apache-maven: Fixed wrong permission development/avr-binutils: Updated for version 2.21.1. development/avrdude: Fixed md5sum. development/gauche: Added (R5RS Scheme implementation) development/kdiff3: Updated for version 0.9.96. development/kiwi: Updated for version 1.9.29. development/nose: Updated for version 1.1.2. development/spin: Added (model checker) development/zope.interface: Updated for version 3.7.0. games/digger: Added (Digger remastered!) games/gnubg: Updated for version 20110906. games/lightyears: Updated for version 1.4. graphics/blender: Fix symlinks to icons in build script haskell/haskell-HTTP: Updated for version 4000.1.2. haskell/haskell-MonadCatchIO-mtl: Updated for version 0.3.0.4. haskell/haskell-dataenc: Updated for version 0.14.0.2. haskell/haskell-fgl: Updated for version 5.4.2.4. haskell/haskell-hashed-storage: Updated for version 0.5.8. haskell/haskell-haskeline: Updated for version 0.6.4.3. haskell/haskell-network: Updated for version 2.3.0.5. haskell/haskell-syb: Updated for version 0.3.3. haskell/haskell-text: Updated for version 0.11.1.5. haskell/haskell-utf8-string: Updated for version 0.3.7. haskell/haskell-xhtml: Updated for version 3000.2.0.4. libraries/Jinja2: Updated for version 2.6. libraries/SQLObject: Updated for version 1.1.3. libraries/decorator: Updated for version 3.3.2. libraries/eeze: Updated for version 1.0.2. libraries/libmemcached: Updated for version 0.52. libraries/libotf: Updated for version 0.9.12. libraries/librelp: Added (a reliable logging library) libraries/opal: Updated for version 3.6.8 (+new maintainer) libraries/simplegeneric: Updated for version 0.8. libraries/yaz: Updated for version 4.2.13. libraries/zita-resampler: Added (library for resampling audio) libraries/zope.event: Updated for version 3.5.1. libraries/zope.i18nmessageid: Updated for version 3.6.1. libraries/zope.location: Updated for version 3.9.1. misc/dos2unix: Added (DOS/Mac to Unix and v.v. file conversion) network/ekiga: Updated for version 3.2.7 (+new maintainer) network/memcached: Updated for version 1.4.7. network/phpmyadmin: Updated for version 3.4.5. network/quassel: Updated for version 0.7.3. network/shorewall6: Updated for version 4.4.23.3. network/shorewall: Updated for version 4.4.23.3. network/vnstat: Updated for version 1.11. network/w3af: Updated for version 1.0. office/calcurse: Updated for version 2.9.1. office/texstudio: Added (LaTeX editor) python/pycxx: Added (Write Python Extensions in C++) python/pygoogle: Removed (no longer functional) python/pysvn: Added (Python SVN extension) python/python-twisted: Updated for version 11.0.0. python/python3: Updated for version 3.2.2. python/subvertpy: Updated for version 0.8.5. system/clamav: Updated for version 0.97.2 (+new maintainer) system/numlockx: Fixed homepage / download link. From dickson.tim at googlemail.com Fri Sep 30 09:13:15 2011 From: dickson.tim at googlemail.com (Tim Dickson) Date: Fri, 30 Sep 2011 10:13:15 +0100 Subject: [Slackbuilds-users] Re blobwars and starfighter In-Reply-To: References: Message-ID: <4E85882B.50908@googlemail.com> just an information email for those interested. the original website for the sources of these projects is now down. the projects have been moved to sourceforge, but as my slack32/64 test machine is sick, I haven't got round to updating the sbuilds for the "new" versions. hopefully that will happen in the next week or so. regards, Tim