From rshepard at appl-ecosys.com  Sun Feb  1 22:23:20 2009
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 1 Feb 2009 14:23:20 -0800 (PST)
Subject: [Slackbuilds-users] Package Build Issues
Message-ID: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>

    I'm trying to apply the SlackBuild script for tinyerp-client, but it tells
me that wxGTK is not present. It was, until I deleted it and just tried to
re-install it. This is all on my newly refurbished -12.2 server/workstation.
Unfortunately, it reminds me of the dependency hell I went through with
early versions of Red Hat that prompted me to switch to Slackware.

    So, let me start from the begining so you folks can tell me what I've
missed.

    When I grep for gtk in /var/log/packages these are returned:

gtk+-1.2.10-i486-4
gtk+2-2.12.12-i486-1
gtk-doc-1.7-noarch-3dl
gtkspell-2.0.14-i486-1
libgtkhtml-2.11.1-i486-1
pygtk-2.12.1-i486-2

    But, when I try to build wxGTK-2.8.9 with the SBo SlackBuild script I see
this:

checking for GTK+ version...
checking for pkg-config... /usr/bin/pkg-config
checking for GTK+ - version >= 2.0.0... no
*** Could not run GTK+ test program, checking why...
*** The test program failed to compile or link. See the file config.log for
the
*** exact error that occured. This usually means GTK+ is incorrectly
installed.
configure: error:
The development files for GTK+ were not found. For GTK+ 2, please
ensure that pkg-config is in the path and that gtk+-2.0.pc is
installed. For GTK+ 1.2 please check that gtk-config is in the path,
and that the version is 1.2.3 or above. Also check that the
libraries returned by 'pkg-config gtk+-2.0 --libs' or 'gtk-config
--libs' are in the LD_LIBRARY_PATH or equivalent.

    So, /uar/bin/pkg-config is in root's path.

    gtk+-2.0.pc is located in /usr/lib/pkgconfig/.

    'pkg-config gtk+-2.0 --libs' shows: [rshepard at salmo ~]$ pkg-config
gtk+-2.0 --libs
-lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0
-lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0

    What have I missed?

TIA,

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

From chess at chessgriffin.com  Sun Feb  1 22:34:30 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Sun, 1 Feb 2009 17:34:30 -0500
Subject: [Slackbuilds-users] Package Build Issues
In-Reply-To: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
Message-ID: <20090201223430.GA3293@localhost>

* Rich Shepard <rshepard at appl-ecosys.com> [2009-02-01 14:23:20]:

>    I'm trying to apply the SlackBuild script for tinyerp-client, but it tells
> me that wxGTK is not present. It was, until I deleted it and just tried to
> re-install it. This is all on my newly refurbished -12.2 server/workstation.
> Unfortunately, it reminds me of the dependency hell I went through with
> early versions of Red Hat that prompted me to switch to Slackware.
>
>    So, let me start from the begining so you folks can tell me what I've
> missed.
>
>    When I grep for gtk in /var/log/packages these are returned:
>
> gtk+-1.2.10-i486-4
> gtk+2-2.12.12-i486-1
> gtk-doc-1.7-noarch-3dl
> gtkspell-2.0.14-i486-1
> libgtkhtml-2.11.1-i486-1
> pygtk-2.12.1-i486-2
>
>    But, when I try to build wxGTK-2.8.9 with the SBo SlackBuild script I see
> this:
>
> checking for GTK+ version...
> checking for pkg-config... /usr/bin/pkg-config
> checking for GTK+ - version >= 2.0.0... no
> *** Could not run GTK+ test program, checking why...
> *** The test program failed to compile or link. See the file config.log for
> the
> *** exact error that occured. This usually means GTK+ is incorrectly
> installed.
> configure: error:
> The development files for GTK+ were not found. For GTK+ 2, please
> ensure that pkg-config is in the path and that gtk+-2.0.pc is
> installed. For GTK+ 1.2 please check that gtk-config is in the path,
> and that the version is 1.2.3 or above. Also check that the
> libraries returned by 'pkg-config gtk+-2.0 --libs' or 'gtk-config
> --libs' are in the LD_LIBRARY_PATH or equivalent.
>
>    So, /uar/bin/pkg-config is in root's path.
>
>    gtk+-2.0.pc is located in /usr/lib/pkgconfig/.
>
>    'pkg-config gtk+-2.0 --libs' shows: [rshepard at salmo ~]$ pkg-config
> gtk+-2.0 --libs
> -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0
> -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0
>
>    What have I missed?
>

I can confirm that the wxGTK SlackBuild works fine on a full install of
Slackware 12.2 -- I just did it today.  :-)

Is this a full clean install of Slackware 12.2?  If not, what is not
installed?  And if it's an upgrade, what did you upgrade from?

I think we need more information about the box.


-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090201/c24b96d0/attachment.sig>

From rshepard at appl-ecosys.com  Sun Feb  1 23:15:31 2009
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 1 Feb 2009 15:15:31 -0800 (PST)
Subject: [Slackbuilds-users] Package Build Issues
In-Reply-To: <20090201223430.GA3293@localhost>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
	<20090201223430.GA3293@localhost>
Message-ID: <alpine.LNX.2.00.0902011507050.14901@salmo.appl-ecosys.com>

On Sun, 1 Feb 2009, Chess Griffin wrote:

> I can confirm that the wxGTK SlackBuild works fine on a full install of
> Slackware 12.2 -- I just did it today.  :-)

   That's encouraging, Chess.

> Is this a full clean install of Slackware 12.2?  If not, what is not
> installed?  And if it's an upgrade, what did you upgrade from?

   It's a clean installation with data and other applications restored from
the backup tape. I've had two weeks of the server/workstation being down;
this past week because it just would not boot into any kernel I built. There
was something in /etc that was overwritten by an earlier file on the tape,
apparently because the mtime of the tape file was newer than that of the
freshly-installed file. Friday night and Saturday morning I carefully did a
file-by-file restore of /etc and the system now boots into the
2.6.27.7-generic-smp kernel. When I redid the full install Friday from the
12.2 distribution disks, I put everything from disks 1 and 2 on, but only
kdebase and kdelibs because I run Xfce, not KDE.

   The original attempt was an upgrade from a working 12.1 system to 12.2.
FWIW, a Slackware-experienced SysAdmin duplicated my problems on a virtual
machine on which he installed -12.2 (his servers are still running -11.0),
but his solution didn't apply to my situation.

   Regardless, I'm up and running and trying to figure out why wxGTK cannot
find the installed gtk+2.

   What information can I provide? 'uname -a' reports: Linux salmo
2.6.27.7-smp #1 SMP Thu Nov 20 22:18:02 CST 2008 i686 AMD Athlon(tm) 64 X2
Dual Core Processor 4800+ AuthenticAMD GNU/Linux. This particular system has
run Slackware since September 2007 when it replaced my former
server/workstation.

   I would like to get wxGTK and tinyerp-client built today so I can actually
use the application this week.

Thanks,

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

From rw at rlworkman.net  Sun Feb  1 23:41:57 2009
From: rw at rlworkman.net (Robby Workman)
Date: Sun, 1 Feb 2009 17:41:57 -0600
Subject: [Slackbuilds-users] Package Build Issues
In-Reply-To: <alpine.LNX.2.00.0902011507050.14901@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
	<20090201223430.GA3293@localhost>
	<alpine.LNX.2.00.0902011507050.14901@salmo.appl-ecosys.com>
Message-ID: <20090201174157.14fa53a5@liberty.rlwhome.lan>

Rich:

For future reference, if you're going to post to multiple lists, just
CC them; that way, all responses can stay together, and responders
won't suggest things that have already been suggested elsewhere...


On Sun, 1 Feb 2009 15:15:31 -0800 (PST) Rich Shepard
<rshepard at appl-ecosys.com> wrote:

> On Sun, 1 Feb 2009, Chess Griffin wrote:
> 
> > I can confirm that the wxGTK SlackBuild works fine on a full
> > install of Slackware 12.2 -- I just did it today.  :-)
> 
>    That's encouraging, Chess.


I can confirm that wxGTK builds just fine here as well.


> > Is this a full clean install of Slackware 12.2?  If not, what is not
> > installed?  And if it's an upgrade, what did you upgrade from?
> 
>    It's a clean installation with data and other applications
> restored from the backup tape. 


Based on the prior troubles you've had, I've noticed a common thread:
all of them involved restoring stuff from a backup tape.  This is going
to come across a bit "asshole-ish," and I'll go ahead and apologize in
advance for that, but...  I think you need to reconsider the way you're
doing things, as it's obviously not ideal.  


> I've had two weeks of the
> server/workstation being down; this past week because it just would
> not boot into any kernel I built. There was something in /etc that
> was overwritten by an earlier file on the tape, apparently because
> the mtime of the tape file was newer than that of the
> freshly-installed file. Friday night and Saturday morning I carefully
> did a file-by-file restore of /etc and the system now boots into the
> 2.6.27.7-generic-smp kernel. When I redid the full install Friday
> from the 12.2 distribution disks, I put everything from disks 1 and 2
> on, but only kdebase and kdelibs because I run Xfce, not KDE.
> 
>    The original attempt was an upgrade from a working 12.1 system to
> 12.2. FWIW, a Slackware-experienced SysAdmin duplicated my problems
> on a virtual machine on which he installed -12.2 (his servers are
> still running -11.0), but his solution didn't apply to my situation.
> 
>    Regardless, I'm up and running and trying to figure out why wxGTK
> cannot find the installed gtk+2.
> 
>    What information can I provide? 'uname -a' reports: Linux salmo
> 2.6.27.7-smp #1 SMP Thu Nov 20 22:18:02 CST 2008 i686 AMD Athlon(tm)
> 64 X2 Dual Core Processor 4800+ AuthenticAMD GNU/Linux. This
> particular system has run Slackware since September 2007 when it
> replaced my former server/workstation.
> 
>    I would like to get wxGTK and tinyerp-client built today so I can
> actually use the application this week.



I can only suggest two things:
1) upgradepkg --reinstall --install-new *everything*
2) if (1) fails, clean install

If (2) becomes necessary, DO NOT "restore" anything from a backup
tape.  Build what you need *on* the new system and install it there.
If you find that you often need the same stuff on multiple systems
(which seems to be the case), then either get a dedicated build box
with a package set that's common to *all* of your other machines, build
the stuff there, and save the packages somewhere for installation on
the other systems.  This will require you to keep all of your other
machines with the same package list, but that shouldn't be a problem --
regardless of whether you actually *need* $somepackage on a particular
system, it won't *hurt* anything by being installed, and you'll get to
greatly simplify your administration burden.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090201/8bcf4eb2/attachment.asc>

From rshepard at appl-ecosys.com  Mon Feb  2 00:23:26 2009
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 1 Feb 2009 16:23:26 -0800 (PST)
Subject: [Slackbuilds-users] Package Build Issues
In-Reply-To: <20090201174157.14fa53a5@liberty.rlwhome.lan>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
	<20090201223430.GA3293@localhost>
	<alpine.LNX.2.00.0902011507050.14901@salmo.appl-ecosys.com>
	<20090201174157.14fa53a5@liberty.rlwhome.lan>
Message-ID: <alpine.LNX.2.00.0902011613430.14901@salmo.appl-ecosys.com>

On Sun, 1 Feb 2009, Robby Workman wrote:

> Based on the prior troubles you've had, I've noticed a common thread: all
> of them involved restoring stuff from a backup tape.  This is going to
> come across a bit "asshole-ish," and I'll go ahead and apologize in
> advance for that, but...  I think you need to reconsider the way you're
> doing things, as it's obviously not ideal.

Robby,

   This has not been an issue from 8.0 through 11.0. Even the upgrades to
12.0 and 12.1 worked. So, if it's something I did on the upgrade to 12.2
then I really need to learn what is different. Over the years I have
restored from the backup tapes several times (new hard drives, change from
Red Hat-7.3 to Slackware-8.0) without any problems.

   How does restoring business applications from the backup tape affect
building libraries from souce? Am I supposed to rebuild LyX, PostgreSQL,
SQL-Ledger, and all the other applications I use for business because the
underlying distribution has been upgraded?

> I can only suggest two things:
> 1) upgradepkg --reinstall --install-new *everything*

   On both machines I ran
upgradepkg --install-new <everything>

> 2) if (1) fails, clean install

   I've done the latter at least 5 times.

> If (2) becomes necessary, DO NOT "restore" anything from a backup
> tape.

   Sorry. I cannot kill my business by not having applications and data
available.

> If you find that you often need the same stuff on multiple systems
> (which seems to be the case), then either get a dedicated build box
> with a package set that's common to *all* of your other machines, build
> the stuff there, and save the packages somewhere for installation on
> the other systems.

   I've always upgraded my notebook first since it's not as critical as the
desktop. The upgrade from 12.1 to 12.2 worked just fine on the notebook. I
could not anticipate why it wouldn't work as smoothly on the desktop ...
just as the prior upgrades went smoothly on both machines.

   And apologies for posting on both lists.

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

From rshepard at appl-ecosys.com  Mon Feb  2 01:17:21 2009
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 1 Feb 2009 17:17:21 -0800 (PST)
Subject: [Slackbuilds-users] Package Build Issues
In-Reply-To: <20090201174157.14fa53a5@liberty.rlwhome.lan>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
	<20090201223430.GA3293@localhost>
	<alpine.LNX.2.00.0902011507050.14901@salmo.appl-ecosys.com>
	<20090201174157.14fa53a5@liberty.rlwhome.lan>
Message-ID: <alpine.LNX.2.00.0902011651060.14901@salmo.appl-ecosys.com>

On Sun, 1 Feb 2009, Robby Workman wrote:

> Based on the prior troubles you've had, I've noticed a common thread: all
> of them involved restoring stuff from a backup tape.  This is going to
> come across a bit "asshole-ish," and I'll go ahead and apologize in
> advance for that, but...  I think you need to reconsider the way you're
> doing things, as it's obviously not ideal.

Robby,

   I apologize if my response came across as harsh. I did not mean to be
abrupt.

   I've basicly spend the past two weeks trying to determine what broke in
the -12.1 to -12.2 upgrade on my main machine. Even with the help of an
experienced SysAdmin who's been running Slackware for years we could not
figure out just what happened. During this time I got no business done, and
for a self-employed consultant that's very expensive.

   While I'm not a computer professional like you and many others on this
list (yes, you're a teacher, but spend a great deal of time learning linux
and Slackware inside out). I use it as a tool, and have run my business on
linux since mid-1997. I've also written code in FORTRAN, C, and now Python
so I'm not naive about issues. That's why I'm so frustrated that the upgrade
did not work as expected and that something in the /etc/ directory kept
getting in the way of a running system.

   If, with help of gurus such as yourself, I can identify why some
SlackBuild scripts bail out during the configure phase because they cannot
find libraries that were installed during the clean -12.2 installation, I'll
be well prepared in the future. I've found four such applications
(tinyerp-client, taskjuggler, wxGTK, apcupsd), while I've successfully built
29 apps over the past couple of days from SlackBuild scripts. It would be
very helpful to learn why those four fail.

Thanks,

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

From rshepard at appl-ecosys.com  Mon Feb  2 01:48:13 2009
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 1 Feb 2009 17:48:13 -0800 (PST)
Subject: [Slackbuilds-users] Package Build Issues -- Update
In-Reply-To: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
Message-ID: <alpine.LNX.2.00.0902011737280.14901@salmo.appl-ecosys.com>

On Sun, 1 Feb 2009, Rich Shepard wrote:

>   When I grep for gtk in /var/log/packages these are returned:
>
> gtk+2-2.12.12-i486-1

   I found one problem. When building tinyerp-client the configure phase
fails for the same reason: cannot find gtk+2. So, I tried importing the
module in interactive python (according to find it resides in
/usr/lib/python2.5/site-packages/gtk-2.0/gtk), but apparently it didn't make
it correctly:

[rshepard at salmo ~]$ python
Python 2.5.2 (r252:60911, Sep 11 2008, 13:43:31) 
[GCC 4.2.4] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import gtk
Traceback (most recent call last):
   File "<stdin>", line 1, in <module>
   File "/usr/lib/python2.5/site-packages/gtk-2.0/gtk/__init__.py", line 48,
in <module>
     from gtk import _gtk
ImportError: /usr/lib/libfontconfig.so.1: undefined symbol: FT_Select_Size
>>>

   Reinstalling the gtk+2 package didn't help. Wonder what's going on here
... it could well be my syntax.

   fontconfig-2.6.0-i486-2 is installed, and that's where libfontconfig.so.1
is found.

   If there is a more appropriate mail list to help me learn how to identify
what broke and how to fix it, please point me there.

Thanks,

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

From rw at rlworkman.net  Mon Feb  2 02:04:44 2009
From: rw at rlworkman.net (Robby Workman)
Date: Sun, 1 Feb 2009 20:04:44 -0600
Subject: [Slackbuilds-users] Package Build Issues
In-Reply-To: <alpine.LNX.2.00.0902011613430.14901@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
	<20090201223430.GA3293@localhost>
	<alpine.LNX.2.00.0902011507050.14901@salmo.appl-ecosys.com>
	<20090201174157.14fa53a5@liberty.rlwhome.lan>
	<alpine.LNX.2.00.0902011613430.14901@salmo.appl-ecosys.com>
Message-ID: <20090201200444.67ad5775@liberty.rlwhome.lan>

On Sun, 1 Feb 2009 16:23:26 -0800 (PST)
Rich Shepard <rshepard at appl-ecosys.com> wrote:

>    How does restoring business applications from the backup tape
> affect building libraries from souce? Am I supposed to rebuild LyX,
> PostgreSQL, SQL-Ledger, and all the other applications I use for
> business because the underlying distribution has been upgraded?


Yes.  While a app built on a 12.0 or 12.1 system will often still work
on 12.2, there's no guarantee.  I can think of *several* situations
where this would have complications, but unless you *really* want to
hear them, I'll spare the details (because I *really* don't want to
type it all out).


> > I can only suggest two things:
> > 1) upgradepkg --reinstall --install-new *everything*
> 
>    On both machines I ran
> upgradepkg --install-new <everything>
> 
> > 2) if (1) fails, clean install
> 
>    I've done the latter at least 5 times.


...and yet the same or similar problems keep occurring.  That's
ultimately my point - I don't know what it is, but *something* you're
doing is causing these problems.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090201/353a7d25/attachment.asc>

From harmon at ksu.edu  Mon Feb  2 02:11:23 2009
From: harmon at ksu.edu (Scott Harmon)
Date: Sun, 1 Feb 2009 20:11:23 -0600
Subject: [Slackbuilds-users] Package Build Issues -- Update
In-Reply-To: <alpine.LNX.2.00.0902011737280.14901@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
	<alpine.LNX.2.00.0902011737280.14901@salmo.appl-ecosys.com>
Message-ID: <77E52B8E-86C7-4148-A774-B91DD1D5AF49@ksu.edu>

On Feb 1, 2009, at 7:48 PM, Rich Shepard wrote:

> On Sun, 1 Feb 2009, Rich Shepard wrote:
>
>>  When I grep for gtk in /var/log/packages these are returned:
>>
>> gtk+2-2.12.12-i486-1
>
>  I found one problem. When building tinyerp-client the configure phase
> fails for the same reason: cannot find gtk+2. So, I tried importing  
> the
> module in interactive python (according to find it resides in
> /usr/lib/python2.5/site-packages/gtk-2.0/gtk), but apparently it  
> didn't make
> it correctly:
>
> [rshepard at salmo ~]$ python
> Python 2.5.2 (r252:60911, Sep 11 2008, 13:43:31) [GCC 4.2.4] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>>>> import gtk
> Traceback (most recent call last):
>  File "<stdin>", line 1, in <module>
>  File "/usr/lib/python2.5/site-packages/gtk-2.0/gtk/__init__.py",  
> line 48,
> in <module>
>    from gtk import _gtk
> ImportError: /usr/lib/libfontconfig.so.1: undefined symbol:  
> FT_Select_Size
>>>>
>
>  Reinstalling the gtk+2 package didn't help. Wonder what's going on  
> here
> ... it could well be my syntax.
>

Did you restore /usr/local/{lib,bin}... ?

>  fontconfig-2.6.0-i486-2 is installed, and that's where  
> libfontconfig.so.1
> is found.
>
>  If there is a more appropriate mail list to help me learn how to  
> identify
> what broke and how to fix it, please point me there.
>
> Thanks,
>
> Rich
>
> -- 
> Richard B. Shepard, Ph.D.               |  Integrity             
> Credibility
> Applied Ecosystem Services, Inc.        |            Innovation
> <http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax:  
> 503-667-8863
> _______________________________________________
> 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/
>

-- 
Scott J. Harmon
PhD Candidate
Kansas State University

"Computer Science is no more about computers than astronomy is about  
telescopes." - Edsger Dijkstra


From timp at timp.com.au  Mon Feb  2 02:12:10 2009
From: timp at timp.com.au (Timothy Pollard)
Date: Mon, 2 Feb 2009 12:12:10 +1000
Subject: [Slackbuilds-users] Package Build Issues -- Update
In-Reply-To: <alpine.LNX.2.00.0902011737280.14901@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
	<alpine.LNX.2.00.0902011737280.14901@salmo.appl-ecosys.com>
Message-ID: <20090202121210.329bc42f@shammah.timp.com.au>

Hi Rich,

On Sun, 1 Feb 2009 17:48:13 -0800 (PST)
Rich Shepard <rshepard at appl-ecosys.com> wrote:
> On Sun, 1 Feb 2009, Rich Shepard wrote:
> 
> >   When I grep for gtk in /var/log/packages these are returned:
> >
> > gtk+2-2.12.12-i486-1
> 
>    I found one problem. When building tinyerp-client the configure phase
> fails for the same reason: cannot find gtk+2. So, I tried importing the
> module in interactive python (according to find it resides in
> /usr/lib/python2.5/site-packages/gtk-2.0/gtk), but apparently it didn't make
> it correctly:
> 
> [rshepard at salmo ~]$ python
> Python 2.5.2 (r252:60911, Sep 11 2008, 13:43:31) [GCC 4.2.4] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import gtk
> Traceback (most recent call last):
>    File "<stdin>", line 1, in <module>
>    File "/usr/lib/python2.5/site-packages/gtk-2.0/gtk/__init__.py", line 48,
> in <module>
>      from gtk import _gtk
> ImportError: /usr/lib/libfontconfig.so.1: undefined symbol: FT_Select_Size
> >>>
> 
>    Reinstalling the gtk+2 package didn't help. Wonder what's going on here
> ... it could well be my syntax.
> 
>    fontconfig-2.6.0-i486-2 is installed, and that's where libfontconfig.so.1
> is found.
> 
>    If there is a more appropriate mail list to help me learn how to identify
> what broke and how to fix it, please point me there.
> 

A bit of a Google around notes this bug report in Debian:
http://www.mail-archive.com/debian-bugs-dist at lists.debian.org/msg525115.html
which basically says that this is probably caused by libfreetype issues.

The libfreetype.so.6 is contained in both the aaa_elflibs and libfreetype
packages:
$ grep libfreetype.so.6 /var/log/packages/*
/var/log/packages/aaa_elflibs-12.2.0-i486-1:usr/lib/libfreetype.so.6.3.18
/var/log/packages/freetype-2.3.7-i486-1:usr/lib/libfreetype.so.6.3.18

So, your restoring a libfreetype from your backups, or maybe you've got an old
version of one of those packages still lying around. I'd try doing a "$ locate
libfreetype" and see what you get.

-- 
TimP
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090202/8613c4b1/attachment.asc>

From rshepard at appl-ecosys.com  Mon Feb  2 02:18:43 2009
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 1 Feb 2009 18:18:43 -0800 (PST)
Subject: [Slackbuilds-users] Package Build Issues -- Update
In-Reply-To: <77E52B8E-86C7-4148-A774-B91DD1D5AF49@ksu.edu>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
	<alpine.LNX.2.00.0902011737280.14901@salmo.appl-ecosys.com>
	<77E52B8E-86C7-4148-A774-B91DD1D5AF49@ksu.edu>
Message-ID: <alpine.LNX.2.00.0902011814450.14901@salmo.appl-ecosys.com>

On Sun, 1 Feb 2009, Scott Harmon wrote:

> Did you restore /usr/local/{lib,bin}... ?

Scott,

   Yes. The restore default is to not overwrite disk files with the same or
newer mtimes. We suspect that somehow a file on tape had a newer time than
the one on disk. I did not pick specific applications because I did not have
a separate list of those.

   I can always re-install stock -12.2 apps that go in /usr/local/ if I can
identify which ones do so.

Thanks,

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

From rshepard at appl-ecosys.com  Mon Feb  2 02:27:00 2009
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 1 Feb 2009 18:27:00 -0800 (PST)
Subject: [Slackbuilds-users] Package Build Issues -- Update
In-Reply-To: <77E52B8E-86C7-4148-A774-B91DD1D5AF49@ksu.edu>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
	<alpine.LNX.2.00.0902011737280.14901@salmo.appl-ecosys.com>
	<77E52B8E-86C7-4148-A774-B91DD1D5AF49@ksu.edu>
Message-ID: <alpine.LNX.2.00.0902011824530.14901@salmo.appl-ecosys.com>

On Sun, 1 Feb 2009, Scott Harmon wrote:

> Did you restore /usr/local/{lib,bin}... ?

   Good question, Scott! I find a lot of broken links in /usr/local/bin and
/usr/local/lib that I'll fix right after dinner.

   I'll post results when I have some.

Thanks again,

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

From xgizzmo at slackbuilds.org  Mon Feb  2 02:34:17 2009
From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org)
Date: Sun, 1 Feb 2009 21:34:17 -0500
Subject: [Slackbuilds-users] Updates - 20090202
Message-ID: <200902012134.17974.xgizzmo@slackbuilds.org>

Mon Feb  2 01:42:33 UTC 2009
accessibility/unclutter: Added - unclutter is a tool designed to remove the
  clutter of a mouse pointer from a screen in use.
  Thanks to B. Watson.  -rworkman
audio/mp3splt: Updated for version 2.2.3.  Thanks to Roberto Neri.
audio/mp3splt-gtk: Updated for version 0.5.4.  Thanks to Roberto Neri.
development/autogen: Added - AutoGen is a tool designed to simplify the 
  creation and maintenance of programs that contain large amounts of 
  repetitious text.  Thanks to Andrzej Telszewski.  --rworkman
development/bzr: Updated for version 1.11. Thanks to Robby Workman.  --erik
games/epsxe: Added - ePSXe (enhanced PSX emulator) is an emulator of the Sony 
  PlayStation video game console.  Thanks to "soyalexman"  --rworkman
games/gnubg: Updated for version 20090125.  Thanks to Erik Hanson.  --rworkman
games/hatari: Added - Hatari is an Atari ST and STE emulator.
  Thanks to B. Watson.  --rworkman
games/hatari_tos_roms: Added - this contains TOS (Tramiel Operating System) 
  ROM images for use with hatari.  Thanks to B. Watson.  --rworkman
libraries/libmp3splt: Updated for version 0.5.4.  Thanks to Roberto Neri.
misc/clawsker: Updated for version 0.6.0.  Thanks to Erik Hanson. --rworkman
misc/cwiid: Added - CWiid is a collection of tools for interfacing with the
  Nintendo Wiimote.  Thanks to B. Watson.  --rworkman
network/d4x: Added - d4x (Downloader for X) is a download manager/accelerator
  for X.  Thanks to Larry Hajali.  --rworkman
network/elinks: Fixed some docs copying; thanks to Brian Muramatsu. --rworkman
network/conntrack-tools: Updated for version 0.9.10.
  Thanks to Robby Workman.  --erik
network/ndiswrapper: Updated with the *real* upstream 1.54 release.
  Thanks to Robby Workman.  --erik
system/hdapsd: Updated for version 20090129, and included some additions and
  fixups to the config file and init script.  If something is broken, blame
  me, as I tweaked it a bit :)  Thanks to alkos333.  --rworkman
system/lbzip2: Updated for version 0.12.  Thanks to Erik Hanson.  --rworkman
system/rdiff-backup: Updated for version 1.2.5.
  Thanks to javivf at alasombra.net and Paul Wisehart.  --rworkman
system/xbindkeys: Updated for version 1.8.3.  Thanks to Erik Hanson.

From rshepard at appl-ecosys.com  Mon Feb  2 02:34:51 2009
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 1 Feb 2009 18:34:51 -0800 (PST)
Subject: [Slackbuilds-users] Package Build Issues -- Update
In-Reply-To: <20090202121210.329bc42f@shammah.timp.com.au>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
	<alpine.LNX.2.00.0902011737280.14901@salmo.appl-ecosys.com>
	<20090202121210.329bc42f@shammah.timp.com.au>
Message-ID: <alpine.LNX.2.00.0902011829050.14901@salmo.appl-ecosys.com>

On Mon, 2 Feb 2009, Timothy Pollard wrote:

> A bit of a Google around notes this bug report in Debian:
> http://www.mail-archive.com/debian-bugs-dist at lists.debian.org/msg525115.html
> which basically says that this is probably caused by libfreetype issues.

Timothy,

   I didn't catch that; thank you.

> The libfreetype.so.6 is contained in both the aaa_elflibs and libfreetype
> packages:
> $ grep libfreetype.so.6 /var/log/packages/*
> /var/log/packages/aaa_elflibs-12.2.0-i486-1:usr/lib/libfreetype.so.6.3.18
> /var/log/packages/freetype-2.3.7-i486-1:usr/lib/libfreetype.so.6.3.18
>
> So, your restoring a libfreetype from your backups, or maybe you've got an old
> version of one of those packages still lying around. I'd try doing a "$ locate
> libfreetype" and see what you get.

   Here's what I had: /usr/lib/libfreetype-6.3.18 and /usr/local/lib/6.3.8
from 2005, with soft links from Friday. I've removed the earlier versions
and ran ldconfig.

   I'll fix the broken links before testing more.

Many thanks for the pointer!

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

From rw at rlworkman.net  Mon Feb  2 02:39:52 2009
From: rw at rlworkman.net (Robby Workman)
Date: Sun, 1 Feb 2009 20:39:52 -0600
Subject: [Slackbuilds-users] Package Build Issues -- Update
In-Reply-To: <alpine.LNX.2.00.0902011737280.14901@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
	<alpine.LNX.2.00.0902011737280.14901@salmo.appl-ecosys.com>
Message-ID: <20090201203952.46f72eb0@liberty.rlwhome.lan>

On Sun, 1 Feb 2009 17:48:13 -0800 (PST)
Rich Shepard <rshepard at appl-ecosys.com> wrote:

> On Sun, 1 Feb 2009, Rich Shepard wrote:
> 
> >   When I grep for gtk in /var/log/packages these are returned:
> >
> > gtk+2-2.12.12-i486-1
> 
>    I found one problem. When building tinyerp-client the configure
> phase fails for the same reason: cannot find gtk+2. So, I tried
> importing the module in interactive python (according to find it
> resides in /usr/lib/python2.5/site-packages/gtk-2.0/gtk), but
> apparently it didn't make it correctly:
> 
> [rshepard at salmo ~]$ python
> Python 2.5.2 (r252:60911, Sep 11 2008, 13:43:31) 
> [GCC 4.2.4] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import gtk
> Traceback (most recent call last):
>    File "<stdin>", line 1, in <module>
>    File "/usr/lib/python2.5/site-packages/gtk-2.0/gtk/__init__.py",
> line 48, in <module>
>      from gtk import _gtk
> ImportError: /usr/lib/libfontconfig.so.1: undefined symbol:
> FT_Select_Size
> >>>
> 
>    Reinstalling the gtk+2 package didn't help. Wonder what's going on
> here ... it could well be my syntax.
> 
>    fontconfig-2.6.0-i486-2 is installed, and that's where
> libfontconfig.so.1 is found.


This is why you don't reinstall *applications* and such from backup
tapes, at least when they were built on previous/different underlying
operating systems.  Looks like pygtk is expecting a different freetype
library than what you have on the system, and if pygtk and freetype are
the correct ones as installed with a 12.2 system, that can't happen.

-RW

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090201/9e7ed08f/attachment.asc>

From rw at rlworkman.net  Mon Feb  2 02:43:32 2009
From: rw at rlworkman.net (Robby Workman)
Date: Sun, 1 Feb 2009 20:43:32 -0600
Subject: [Slackbuilds-users] Package Build Issues -- Update
In-Reply-To: <alpine.LNX.2.00.0902011814450.14901@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
	<alpine.LNX.2.00.0902011737280.14901@salmo.appl-ecosys.com>
	<77E52B8E-86C7-4148-A774-B91DD1D5AF49@ksu.edu>
	<alpine.LNX.2.00.0902011814450.14901@salmo.appl-ecosys.com>
Message-ID: <20090201204332.1f025a90@liberty.rlwhome.lan>

On Sun, 1 Feb 2009 18:18:43 -0800 (PST)
Rich Shepard <rshepard at appl-ecosys.com> wrote:

> On Sun, 1 Feb 2009, Scott Harmon wrote:
> 
> > Did you restore /usr/local/{lib,bin}... ?
> 
> Scott,
> 
>    Yes. The restore default is to not overwrite disk files with the
> same or newer mtimes. We suspect that somehow a file on tape had a
> newer time than the one on disk. I did not pick specific applications
> because I did not have a separate list of those.
> 
>    I can always re-install stock -12.2 apps that go in /usr/local/ if
> I can identify which ones do so.


None.  /usr/local is for *local* system-specific software compiled by
the system admin and typically *not* packaged.  


>    Good question, Scott! I find a lot of broken links
> in /usr/local/bin and /usr/local/lib that I'll fix right after dinner.


NO, NO, NO.  

/usr/local is where *applications* go.  Don't restore them from backup
if they were built on an older version of Slackware.  Among the
problems you'll encounter are missing and unresolved symbols in
libraries.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090201/9c8c0dcf/attachment-0001.asc>

From rshepard at appl-ecosys.com  Mon Feb  2 03:14:49 2009
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 1 Feb 2009 19:14:49 -0800 (PST)
Subject: [Slackbuilds-users] [slackware] Package Build Issues -- Update
In-Reply-To: <20090201204332.1f025a90@liberty.rlwhome.lan>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
	<alpine.LNX.2.00.0902011737280.14901@salmo.appl-ecosys.com>
	<77E52B8E-86C7-4148-A774-B91DD1D5AF49@ksu.edu>
	<alpine.LNX.2.00.0902011814450.14901@salmo.appl-ecosys.com>
	<20090201204332.1f025a90@liberty.rlwhome.lan>
Message-ID: <alpine.LNX.2.00.0902011913290.14901@salmo.appl-ecosys.com>

On Sun, 1 Feb 2009, Robby Workman wrote:

> None.  /usr/local is for *local* system-specific software compiled by
> the system admin and typically *not* packaged.

   That's what I thought. And why I put applications there that are not part
of the distribution.

Thanks,

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

From rw at rlworkman.net  Mon Feb  2 03:27:50 2009
From: rw at rlworkman.net (Robby Workman)
Date: Sun, 1 Feb 2009 21:27:50 -0600
Subject: [Slackbuilds-users] [slackware] Package Build Issues -- Update
In-Reply-To: <alpine.LNX.2.00.0902011913290.14901@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
	<alpine.LNX.2.00.0902011737280.14901@salmo.appl-ecosys.com>
	<77E52B8E-86C7-4148-A774-B91DD1D5AF49@ksu.edu>
	<alpine.LNX.2.00.0902011814450.14901@salmo.appl-ecosys.com>
	<20090201204332.1f025a90@liberty.rlwhome.lan>
	<alpine.LNX.2.00.0902011913290.14901@salmo.appl-ecosys.com>
Message-ID: <20090201212750.4aa559f3@liberty.rlwhome.lan>

On Sun, 1 Feb 2009 19:14:49 -0800 (PST)
Rich Shepard <rshepard at appl-ecosys.com> wrote:

> On Sun, 1 Feb 2009, Robby Workman wrote:
> 
> > None.  /usr/local is for *local* system-specific software compiled
> > by the system admin and typically *not* packaged.
> 
>    That's what I thought. And why I put applications there that are
> not part of the distribution.


That's fine - exactly what you should do if you're installing them with
"configure && make && make install" as opposed to packaging them first
via a build script or otherwise.

Again though, I have to reiterate -- DO NOT restore /usr/local from one
Slackware version onto another version. 

Also, you mentioned a freetype or fontconfig (I don't recall
which) version in one of your /usr/local directories in another mail;
that should not be happening, as both of those are included with
Slackware.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090201/18f7c2b2/attachment.asc>

From rw at rlworkman.net  Mon Feb  2 03:37:21 2009
From: rw at rlworkman.net (Robby Workman)
Date: Sun, 1 Feb 2009 21:37:21 -0600
Subject: [Slackbuilds-users] Package Build Issues
In-Reply-To: <alpine.LNX.2.00.0902011651060.14901@salmo.appl-ecosys.com>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
	<20090201223430.GA3293@localhost>
	<alpine.LNX.2.00.0902011507050.14901@salmo.appl-ecosys.com>
	<20090201174157.14fa53a5@liberty.rlwhome.lan>
	<alpine.LNX.2.00.0902011651060.14901@salmo.appl-ecosys.com>
Message-ID: <20090201213721.5d6d050a@liberty.rlwhome.lan>

On Sun, 1 Feb 2009 17:17:21 -0800 (PST)
Rich Shepard <rshepard at appl-ecosys.com> wrote:

> On Sun, 1 Feb 2009, Robby Workman wrote:
> 
> > Based on the prior troubles you've had, I've noticed a common
> > thread: all of them involved restoring stuff from a backup tape.
> > This is going to come across a bit "asshole-ish," and I'll go ahead
> > and apologize in advance for that, but...  I think you need to
> > reconsider the way you're doing things, as it's obviously not ideal.
> 
> Robby,
> 
>    I apologize if my response came across as harsh. I did not mean to
> be abrupt.
> 
>    I've basicly spend the past two weeks trying to determine what
> broke in the -12.1 to -12.2 upgrade on my main machine. Even with the
> help of an experienced SysAdmin who's been running Slackware for
> years we could not figure out just what happened. During this time I
> got no business done, and for a self-employed consultant that's very
> expensive.


I didn't take any offense to anything you said, but even if I had,
there's no need to apologize to me - you're understandably under some
stress because of all this, and so long as a person doesn't delve into
personal attacks, I'll not get offended and/or hold grudges.

The biggest concern I have is trying to get you to see that your backup
and restore practice is a big part of the problem, and I just don't see
a good way to do that without *me* being, or at least coming across as,
harsh.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090201/459d6418/attachment.asc>

From rshepard at appl-ecosys.com  Mon Feb  2 04:06:17 2009
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 1 Feb 2009 20:06:17 -0800 (PST)
Subject: [Slackbuilds-users] Package Build Issues -- RESOLVED!!
In-Reply-To: <20090201213721.5d6d050a@liberty.rlwhome.lan>
References: <alpine.LNX.2.00.0902011422320.14714@salmo.appl-ecosys.com>
	<20090201223430.GA3293@localhost>
	<alpine.LNX.2.00.0902011507050.14901@salmo.appl-ecosys.com>
	<20090201174157.14fa53a5@liberty.rlwhome.lan>
	<alpine.LNX.2.00.0902011651060.14901@salmo.appl-ecosys.com>
	<20090201213721.5d6d050a@liberty.rlwhome.lan>
Message-ID: <alpine.LNX.2.00.0902011958060.14901@salmo.appl-ecosys.com>

On Sun, 1 Feb 2009, Robby Workman wrote:

> I didn't take any offense to anything you said, but even if I had, there's
> no need to apologize to me - you're understandably under some stress
> because of all this, and so long as a person doesn't delve into personal
> attacks, I'll not get offended and/or hold grudges.

   Thank you.

> The biggest concern I have is trying to get you to see that your backup
> and restore practice is a big part of the problem, and I just don't see a
> good way to do that without *me* being, or at least coming across as,
> harsh.

   This is the first time a Slackware upgrade caused me any problems at all.
Totally unexpected.

   It turns out that the /usr/local/lib restore from the backup tape placed
libfreetype-3.6.8 on the disk and that was in addition to the 3.6.18
installed with -12.2. As soon as I removed the earlier (vintage 2005)
libraries, everything built with the SlackBuild scripts.

   The first 4 days the system was down I tried re-installing 12.1 (the
distribution that worked), but there was still something broken because I
could not get that working at all. It was Friday a week ago that my SysAdmin
friend agreed that another 12.1 install was futile and I might as well go to
12.2. That booted with the huge kernel, but not the generic one. Then I
carelessly deleted some files from /etc/ and restoring from tape into that
directory was the cause of last week's problems. So I tried to restore to a
clean 12.1 distribution installation, but it just refused to work.

   Now everything is stable, current, and working with the
2.6.27.7-generic-smp kernel and I can focus on my business for a while.

   I greatly appreciate the help all of you offered. When I saw the two
library versions it brought back the memory of the same thing happening with
early Red Hat distribution upgrades. But, that was so long ago I had totally
forgotten about it.

Again, a heartfelt thank you to all of you,

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

From pc_warner at yahoo.com  Mon Feb  2 04:21:18 2009
From: pc_warner at yahoo.com (Phillip Warner)
Date: Sun, 1 Feb 2009 20:21:18 -0800 (PST)
Subject: [Slackbuilds-users] Package Build Issues
In-Reply-To: <20090201213721.5d6d050a@liberty.rlwhome.lan>
Message-ID: <393279.31046.qm@web57706.mail.re3.yahoo.com>

Rich,

It might be a good idea to compile some of your software to use static libraries in the future.  Maybe you can do that gradually over time.

Also, something like GoboLinux (www.gobolinux.org/) may be of interest to you.

--phillip


      

From pc_warner at yahoo.com  Mon Feb  2 05:37:16 2009
From: pc_warner at yahoo.com (Phillip Warner)
Date: Sun, 1 Feb 2009 21:37:16 -0800 (PST)
Subject: [Slackbuilds-users] Package Build Issues
In-Reply-To: <393279.31046.qm@web57706.mail.re3.yahoo.com>
Message-ID: <957713.48335.qm@web57704.mail.re3.yahoo.com>

--- On Sun, 2/1/09, Phillip Warner <pc_warner at yahoo.com> wrote:

> Also, something like GoboLinux (www.gobolinux.org/) may be
> of interest to you.

or this project to 'Convert Slackware packages into relocatable "AppDirs"' listed at LQ at 
  http://tinyurl.com/b3lbf7

--phillip


      

From banderols at gmail.com  Mon Feb  2 17:59:21 2009
From: banderols at gmail.com (Murat D. Kadirov)
Date: Mon, 2 Feb 2009 22:59:21 +0500
Subject: [Slackbuilds-users] Can't upload slackbuilds
Message-ID: <20090202175921.GA6896@darkstar>

I can't upload my updated slackbuilds. I get error: "Upload failed,
could not find: hostapd/hostapd.info". But:

murat at laptop[~]$ less hostapd.tar.gz
drwxr-xr-x murat/users       0 2009-02-02 22:15 hostapd/
-rw-r--r-- murat/users    2569 2009-02-02 21:50 hostapd/config
-rw-r--r-- murat/users     907 2008-08-10 10:10 hostapd/slack-desc
-rw-r--r-- murat/users     597 2009-01-29 23:15 hostapd/README
-rw-r--r-- murat/users     246 2009-01-29 23:24 hostapd/hostapd.info
-rwxr-xr-x murat/users    3255 2009-01-30 02:32
hostapd/hostapd.SlackBuild
-rw-r--r-- murat/users     653 2009-01-30 02:31 hostapd/doinst.sh
-rw-r--r-- murat/users     730 2009-01-30 01:01 hostapd/rc.hostapd.new

p.s. I can't upload slackbuild "John the Ripper" (size 136 kb) too.
Robby, can I email it to you again? :)

-- 
Murat D. Kadirov
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090202/dba52dfc/attachment.sig>

From erik at slackbuilds.org  Mon Feb  2 19:18:26 2009
From: erik at slackbuilds.org (Erik Hanson)
Date: Mon, 2 Feb 2009 13:18:26 -0600
Subject: [Slackbuilds-users] Can't upload slackbuilds
In-Reply-To: <20090202175921.GA6896@darkstar>
References: <20090202175921.GA6896@darkstar>
Message-ID: <20090202131826.3403e68b@shaggy.scooby>

On Feb 02, 2009, at 10:59 PM, Murat D. Kadirov wrote:

> I can't upload my updated slackbuilds. I get error: "Upload failed,
> could not find: hostapd/hostapd.info". But:

It doesn't look like it should have failed.. I just cleaned out our tmp dir
so give it another try. be sure to tar zcvf hostapd.tar.gz hostapd/
If that fails I will take a closer look.

-- 
Erik Hanson
http://slackbuilds.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090202/d6f6bb49/attachment.asc>

From banderols at gmail.com  Mon Feb  2 20:16:41 2009
From: banderols at gmail.com (Murat D. Kadirov)
Date: Tue, 3 Feb 2009 01:16:41 +0500
Subject: [Slackbuilds-users] Can't upload slackbuilds
In-Reply-To: <20090202131826.3403e68b@shaggy.scooby>
References: <20090202175921.GA6896@darkstar>
	<20090202131826.3403e68b@shaggy.scooby>
Message-ID: <20090202201641.GA7090@darkstar>

13:18 Mon 02 Feb, Erik Hanson wrote:
> On Feb 02, 2009, at 10:59 PM, Murat D. Kadirov wrote:
> 
> > I can't upload my updated slackbuilds. I get error: "Upload failed,
> > could not find: hostapd/hostapd.info". But:
> 
> It doesn't look like it should have failed.. I just cleaned out our tmp dir
> so give it another try. be sure to tar zcvf hostapd.tar.gz hostapd/

Thanks, now it work.

-- 
Murat D. Kadirov
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090203/8ae4d651/attachment.sig>

From xma at gnu.org  Mon Feb  2 19:01:14 2009
From: xma at gnu.org (xma at gnu.org)
Date: Mon, 02 Feb 2009 20:01:14 +0100
Subject: [Slackbuilds-users] awesome 3.1.1 ?
Message-ID: <22286.1233601274@zogzog.maillard.mobi>

Hi,

I tried to modify sbo awesome slackbuild script but it miserably
failed due to missing symbols in the cairo library shipped with
default slackware distribution.

To correctly build awesome3, we need cairo compiled with XCB
backend. I know how to build it but I want to know how I can
update awesome3 in SBo (knowing that without xcb-aware cairo
library) won't work.

Regards
-- 
Xavier Maillard

From chess at chessgriffin.com  Mon Feb  2 21:26:14 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Mon, 2 Feb 2009 16:26:14 -0500
Subject: [Slackbuilds-users] awesome 3.1.1 ?
In-Reply-To: <22286.1233601274@zogzog.maillard.mobi>
References: <22286.1233601274@zogzog.maillard.mobi>
Message-ID: <20090202212614.GA16445@localhost>

* xma at gnu.org <xma at gnu.org> [2009-02-02 20:01:14]:

> Hi,
> 
> I tried to modify sbo awesome slackbuild script but it miserably
> failed due to missing symbols in the cairo library shipped with
> default slackware distribution.
> 
> To correctly build awesome3, we need cairo compiled with XCB
> backend. I know how to build it but I want to know how I can
> update awesome3 in SBo (knowing that without xcb-aware cairo
> library) won't work.
> 

As the maintainer of the awesome SlackBuild I have not investigated this
and do not plan to (and do not plan to update the awesome SlackBuild)
because of all the changes between awesome2 and awesome3.  You probably
know this, but awesome3 is completely different than awesome2.  Awesome3
is based on lua, has a completely different configuration file, and, as
you discovered, different dependencies (some of which cannot be
satisfied without replacing stock Slackware packages which I will not do
on my systems).

If you or someone else wants to create and submit an awesome3 SlackBuild
to SBo that would cool -- I imagine the SBo admins would be OK with
keeping both in the repo since they are really very different
applications, but since I am not an admin that's not my call.  I would
support adding awesome3, FWIW since you are not the first to ask about
this -- search the ML archives.

Anyway, the way to adapt the current awesome2 SlackBuild is the same as
any -- figure out what needs to be changed and change it.  Get the
source, and unpack it.  Run ./configure --help and see what options are
available.  Edit the SlackBuild as needed.  Edit the .info file as
needed.  You may want to read some of the information on slackbuilds.org
about creating SlackBuild scripts since that's basically what you would
be doing, only with a template that is more complete than the basic SBo
template.

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090202/4d5699ce/attachment.sig>

From rworkman at slackbuilds.org  Mon Feb  2 21:27:56 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 2 Feb 2009 15:27:56 -0600
Subject: [Slackbuilds-users] awesome 3.1.1 ?
In-Reply-To: <20090202212614.GA16445@localhost>
References: <22286.1233601274@zogzog.maillard.mobi>
	<20090202212614.GA16445@localhost>
Message-ID: <20090202152756.386eb1c6@liberty.rlwhome.lan>

On Mon, 2 Feb 2009 16:26:14 -0500
Chess Griffin <chess at chessgriffin.com> wrote:

> As the maintainer of the awesome SlackBuild I have not investigated
> this and do not plan to (and do not plan to update the awesome
> SlackBuild) because of all the changes between awesome2 and
> awesome3.  You probably know this, but awesome3 is completely
> different than awesome2.  Awesome3 is based on lua, has a completely
> different configuration file, and, as you discovered, different
> dependencies (some of which cannot be satisfied without replacing
> stock Slackware packages which I will not do on my systems).


and for this reason, an awesome3 build script is not welcome at this
time.  Maybe for the next Slackware release, which should (assuming
gtk+2 and friends are updated) have a newer cairo version.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090202/56961630/attachment.asc>

From chess at chessgriffin.com  Mon Feb  2 22:28:19 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Mon, 2 Feb 2009 17:28:19 -0500
Subject: [Slackbuilds-users] awesome 3.1.1 ?
In-Reply-To: <20090202152756.386eb1c6@liberty.rlwhome.lan>
References: <22286.1233601274@zogzog.maillard.mobi>
	<20090202212614.GA16445@localhost>
	<20090202152756.386eb1c6@liberty.rlwhome.lan>
Message-ID: <20090202222819.GB18207@localhost>

* Robby Workman <rworkman at slackbuilds.org> [2009-02-02 15:27:56]:

> On Mon, 2 Feb 2009 16:26:14 -0500
> Chess Griffin <chess at chessgriffin.com> wrote:
> 
> > As the maintainer of the awesome SlackBuild I have not investigated
> > this and do not plan to (and do not plan to update the awesome
> > SlackBuild) because of all the changes between awesome2 and
> > awesome3.  You probably know this, but awesome3 is completely
> > different than awesome2.  Awesome3 is based on lua, has a completely
> > different configuration file, and, as you discovered, different
> > dependencies (some of which cannot be satisfied without replacing
> > stock Slackware packages which I will not do on my systems).
> 
> 
> and for this reason, an awesome3 build script is not welcome at this
> time.  Maybe for the next Slackware release, which should (assuming
> gtk+2 and friends are updated) have a newer cairo version.
> 

Makes sense, of course.  Still the OP can modify the SlackBuild for his
personal use in the meantime and then have it ready to go if/when those
changes are made in Slackware proper.

And to the OP, sorry if I seemed gruff.  I'm just annoyed that awesome3
made all those changes when IMHO, awesome2 was pretty darn awesome.
Using a deprecated window manager (that I like) sucks.  Having said
that, there is an update to awesome2 (2.3.5) that I will submit soon.

One last tidbit for the OP - did you see this in the awesome wiki:

http://awesome.naquadah.org/wiki/index.php?title=Awesome-3-Slackware

I think that has the answers you are seeking.  :-)

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090202/e7ae738f/attachment.sig>

From mjjzf at syntaktisk.dk  Tue Feb  3 10:27:15 2009
From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=)
Date: Tue, 3 Feb 2009 11:27:15 +0100
Subject: [Slackbuilds-users] Slackbuild RSS
Message-ID: <20090203112715.23063cf3@espero.syntaktisk.dk>

Just curious:
Is there an RSS feed of newly added/updated Slackbuilds?

Yours,
Morten
__
Morten Juhl-Johansen Z?lde-Fej?r
http://syntaktisk.dk * mjjzf at syntaktisk.dk

From mark-sbo at markwalling.org  Tue Feb  3 11:39:09 2009
From: mark-sbo at markwalling.org (Mark Walling)
Date: Tue, 3 Feb 2009 06:39:09 -0500
Subject: [Slackbuilds-users] Slackbuild RSS
In-Reply-To: <20090203112715.23063cf3@espero.syntaktisk.dk>
References: <20090203112715.23063cf3@espero.syntaktisk.dk>
Message-ID: <20090203113909.GA9378@you>

On 02/03/09, Morten Juhl-Johansen Z?lde-Fej?r wrote:
> Just curious:
> Is there an RSS feed of newly added/updated Slackbuilds?
> 
> Yours,
> Morten
http://slackbuilds.org/rss/ChangeLog.rss

Linked from the footer of every page.

-- 
Mark
http://markwalling.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090203/2f5f40c0/attachment.sig>

From mjjzf at syntaktisk.dk  Tue Feb  3 12:09:06 2009
From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=)
Date: Tue, 3 Feb 2009 13:09:06 +0100
Subject: [Slackbuilds-users] Slackbuild RSS
In-Reply-To: <20090203113909.GA9378@you>
References: <20090203112715.23063cf3@espero.syntaktisk.dk>
	<20090203113909.GA9378@you>
Message-ID: <20090203130906.4eed4742@espero.syntaktisk.dk>

On Tue, 3 Feb 2009 06:39:09 -0500
Mark Walling <mark-sbo at markwalling.org> wrote:

> On 02/03/09, Morten Juhl-Johansen Z?lde-Fej?r wrote:
> > Just curious:
> > Is there an RSS feed of newly added/updated Slackbuilds?
> > 
> > Yours,
> > Morten
> http://slackbuilds.org/rss/ChangeLog.rss
> 
> Linked from the footer of every page.
> 

Wow, that was exceptionally unimpressive of me.
It seems I have become a little too used to Firefox picking it up
automagically. Thank you!

Yours.
Morten
__
Morten Juhl-Johansen Z?lde-Fej?r
http://syntaktisk.dk * mjjzf at syntaktisk.dk

From larryhaja at gmail.com  Tue Feb  3 20:44:56 2009
From: larryhaja at gmail.com (Larry Hajali)
Date: Tue, 3 Feb 2009 12:44:56 -0800
Subject: [Slackbuilds-users] libmusicbrainz version number mismatch
Message-ID: <8ba30f850902031244s252dd7c0x8e90e9c5e46226ba@mail.gmail.com>

I noticed that the there is a mismatch in version numbers for
libmusicbrainz.  On the webpage and inside the libmusicbrainz.info file it
says "3.0.2", however, all other version numbers including the
libmusicbrainz download link point to "2.1.5".

Larry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090203/0dc7fdd3/attachment.htm>

From rworkman at slackbuilds.org  Tue Feb  3 21:26:46 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 3 Feb 2009 15:26:46 -0600
Subject: [Slackbuilds-users] libmusicbrainz version number mismatch
In-Reply-To: <8ba30f850902031244s252dd7c0x8e90e9c5e46226ba@mail.gmail.com>
References: <8ba30f850902031244s252dd7c0x8e90e9c5e46226ba@mail.gmail.com>
Message-ID: <20090203152646.31d7e940@liberty.rlwhome.lan>

On Tue, 3 Feb 2009 12:44:56 -0800
Larry Hajali <larryhaja at gmail.com> wrote:

> I noticed that the there is a mismatch in version numbers for
> libmusicbrainz.  On the webpage and inside the libmusicbrainz.info
> file it says "3.0.2", however, all other version numbers including the
> libmusicbrainz download link point to "2.1.5".


Fixed; thanks!

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090203/d8d728a4/attachment.asc>

From larryhaja at gmail.com  Wed Feb  4 16:21:08 2009
From: larryhaja at gmail.com (Larry Hajali)
Date: Wed, 4 Feb 2009 08:21:08 -0800
Subject: [Slackbuilds-users] Deluge
Message-ID: <8ba30f850902040821v1965be34pd988dae291d497d8@mail.gmail.com>

There are two entries for Deluge on slackbuilds.org as well as links to two
versions of the program.  Version 1.0.7 and 1.1.0.

Larry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090204/592474da/attachment.htm>

From rworkman at slackbuilds.org  Wed Feb  4 16:31:24 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 4 Feb 2009 10:31:24 -0600
Subject: [Slackbuilds-users] Deluge
In-Reply-To: <8ba30f850902040821v1965be34pd988dae291d497d8@mail.gmail.com>
References: <8ba30f850902040821v1965be34pd988dae291d497d8@mail.gmail.com>
Message-ID: <20090204103124.246a1c6a@liberty.rlwhome.lan>

On Wed, 4 Feb 2009 08:21:08 -0800
Larry Hajali <larryhaja at gmail.com> wrote:

> There are two entries for Deluge on slackbuilds.org as well as links
> to two versions of the program.  Version 1.0.7 and 1.1.0.


Not anymore :-)   Thanks...

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090204/d08ee5ec/attachment-0001.asc>

From michiel at slackbuilds.org  Wed Feb  4 16:32:29 2009
From: michiel at slackbuilds.org (Michiel van Wessem)
Date: Wed, 4 Feb 2009 16:32:29 +0000
Subject: [Slackbuilds-users] Deluge
In-Reply-To: <8ba30f850902040821v1965be34pd988dae291d497d8@mail.gmail.com>
References: <8ba30f850902040821v1965be34pd988dae291d497d8@mail.gmail.com>
Message-ID: <200902041632.33535.michiel@slackbuilds.org>

On Wednesday 04 February 2009 16:21:08 Larry Hajali wrote:
> There are two entries for Deluge on slackbuilds.org as well as links to two
> versions of the program.  Version 1.0.7 and 1.1.0.
>
Fixed. Thanks.

-M
-- 
http://slackbuilds.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090204/d5848152/attachment.sig>

From xma at gnu.org  Wed Feb  4 23:31:41 2009
From: xma at gnu.org (xma at gnu.org)
Date: Thu, 05 Feb 2009 00:31:41 +0100
Subject: [Slackbuilds-users] awesome 3.1.1 ?
In-Reply-To: <20090202222819.GB18207@localhost>
References: <22286.1233601274@zogzog.maillard.mobi>
	<20090202212614.GA16445@localhost>
	<20090202152756.386eb1c6@liberty.rlwhome.lan>
	<20090202222819.GB18207@localhost>
Message-ID: <16802.1233790301@zogzog.maillard.mobi>

Hi,

Chess Griffin <chess at chessgriffin.com> wrote:

> * Robby Workman <rworkman at slackbuilds.org> [2009-02-02 15:27:56]:
> 
> > On Mon, 2 Feb 2009 16:26:14 -0500
> > Chess Griffin <chess at chessgriffin.com> wrote:
> > 
> > > As the maintainer of the awesome SlackBuild I have not investigated
> > > this and do not plan to (and do not plan to update the awesome
> > > SlackBuild) because of all the changes between awesome2 and
> > > awesome3.  You probably know this, but awesome3 is completely
> > > different than awesome2.  Awesome3 is based on lua, has a completely
> > > different configuration file, and, as you discovered, different
> > > dependencies (some of which cannot be satisfied without replacing
> > > stock Slackware packages which I will not do on my systems).

Here my "modified cairo installation" does not replace the stock
cairo since I installed it in /usr/local which awesome was kind
to use as the prefered cairo library :)

> > and for this reason, an awesome3 build script is not welcome at this
> > time.  Maybe for the next Slackware release, which should (assuming
> > gtk+2 and friends are updated) have a newer cairo version.
> > 
> Makes sense, of course.  Still the OP can modify the SlackBuild for his
> personal use in the meantime and then have it ready to go if/when those
> changes are made in Slackware proper.

If ever made :)
 
> And to the OP, sorry if I seemed gruff.  I'm just annoyed that awesome3
> made all those changes when IMHO, awesome2 was pretty darn awesome.
> Using a deprecated window manager (that I like) sucks.  Having said
> that, there is an update to awesome2 (2.3.5) that I will submit soon.
> 
> One last tidbit for the OP - did you see this in the awesome wiki:
> 
> http://awesome.naquadah.org/wiki/index.php?title=Awesome-3-Slackware

Checked it and I only needed to make my own slackbuild for cairo
with xcb support. It works like a charm.
 
> I think that has the answers you are seeking.  :-)

Yup.

Thank you all for your time and support.

From joesplace100 at hotmail.com  Fri Feb  6 01:16:39 2009
From: joesplace100 at hotmail.com (Joe S)
Date: Thu, 5 Feb 2009 18:16:39 -0700
Subject: [Slackbuilds-users] Problem with nvidia-legacy173 slackbuild
Message-ID: <BAY131-W20A1D62ECD641D4FB49BDA96C10@phx.gbl>


I installed the nvidia-legacy173 series from slackbuilds.org.
When I try to run startx I get the following message:
The nvidia kernel module has version 71.86.06, but
the nvidia driver component has version 173.14.12
I can't get graphics.
This is the output from lspci:
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5500] (rev a1)

I used the slackbuild for the nvidia-legacy71 and it works OK for the GeForce FX
5500
According to the nvidia website the 173 series should be the one to work for
this card. This slackbuild also works for the following card which it is supposed to work for:
01:00.0 VGA compatible controller: nVidia Corporation NV6 [Vanta/Vanta LT] (rev 15)

Thanks.


_________________________________________________________________
Windows Live Messenger. Multitasking at its finest.
http://www.microsoft.com/windows/windowslive/messenger.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090205/c44c17c0/attachment.htm>

From cnguyenminhtan at free.fr  Fri Feb  6 10:05:53 2009
From: cnguyenminhtan at free.fr (cnguyenminhtan at free.fr)
Date: Fri, 6 Feb 2009 11:05:53 +0100 (CET)
Subject: [Slackbuilds-users] Problem with nvidia-legacy173 slackbuild
In-Reply-To: <BAY131-W20A1D62ECD641D4FB49BDA96C10@phx.gbl>
Message-ID: <1992449762.199361233914753368.JavaMail.root@zimbra10-e2.priv.proxad.net>

Hello,

I'm not sure if I understand the steps you took but you need to build both the kernel module and the driver using the slackbuilds from the same Nvidia series.

So if the card is supported by the 173 series, you need to use following slackbuilds:

nvidia-legacy173-kernel
nvidia-legacy173-driver

If seems that you have used the slackbuilds:

nvidia-legacy71-kernel
nvidia-legacy173-driver

did I understand correctly?

KR,

Christophe

----- Mail Original -----
De: "Joe S" <joesplace100 at hotmail.com>
?: slackbuilds-users at slackbuilds.org
Envoy?: Vendredi 6 F?vrier 2009 02:16:39 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: [Slackbuilds-users] Problem with nvidia-legacy173 slackbuild


I installed the nvidia-legacy173 series from slackbuilds.org. 
When I try to run startx I get the following message: 
The nvidia kernel module has version 71.86.06, but 
the nvidia driver component has version 173.14.12 
I can't get graphics. 
This is the output from lspci: 
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5500] (rev a1) 

I used the slackbuild for the nvidia-legacy71 and it works OK for the GeForce FX 
5500 
According to the nvidia website the 173 series should be the one to work for 
this card. This slackbuild also works for the following card which it is supposed to work for: 
01:00.0 VGA compatible controller: nVidia Corporation NV6 [Vanta/Vanta LT] (rev 15) 

Thanks. 



Windows Live Messenger. Multitasking at its finest. 
_______________________________________________
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 xgizzmo at slackbuilds.org  Sat Feb  7 15:12:20 2009
From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org)
Date: Sat, 7 Feb 2009 10:12:20 -0500
Subject: [Slackbuilds-users] Updates - 20090207
Message-ID: <200902071012.20555.xgizzmo@slackbuilds.org>

Sat Feb  7 14:13:24 UTC 2009
desktop/QtCurve-Gtk2: Updated for version 0.60.0.
  Thanks to Michiel van Wessem.  --rworkman
desktop/QtCurve-KDE3: Updated for version 0.60.0.
  Thanks to Michiel van Wessem.  --rworkman
desktop/SystemPreferences: Added - System Preferences is a clone of the 
  Apple OS X System Preferences application for GNUstep.
  Thanks to Stefan Bidigaray.  --rworkman
desktop/gtk-nodoka-engine: Added - Nodoka is the new Fedora default theme 
  for Gnome.  Thanks to Erik Hanson.  --rworkman
development/Amaya: Updated for version 11.0.
  Thanks to Kai Schreyer.  --dsomero
development/ProjectCenter: Added - ProjectCenter is GNUstep's integrated
  development environment.  Thanks to Stefan Bidigaray.  --rworkman
development/acpica: Updated for version 20090123.
  Thanks to Heinz Wiesinger.  --dsomero
development/gorm: Added - Gorm is the GNUstep counterpart to NeXT's Interface 
  Builder.  Thanks to Stefan Bidigaray.  --rworkman
development/psyco: Added - Psyco is a Python extension module which can 
  massively speed up the execution of any Python code.
  Thanks to xroberx.  --rworkman
development/rarian: Added - Rarian is a documentation metadata library and
  a drop in replacement for scrollkeeper.
  Thanks to Andrzej Telszewsk.  --dsomero
games/einstein: Added - Einstein puzzle is a remake of the old DOS game 
  Sherlock, which was inspired by Albert Einstein's puzzle.
  Thanks to Erik Hanson.  --rworkman
games/fortune_firefly: Added - fortune_firefly is fortunes from the TV series
  "Firefly".  Thanks to B. Watson.  --dsomero
games/tmw: Updated for version 0.0.28.  Thanks to Erik Hanson.  --dsomero
games/tmwmusic: Added - tmwmusic is add-on music for The Mana World.
  Thanks to Erik Hanson.  --dsomero
games/wesnoth: Updated for version 1.4.7.
  Thanks to Michiel van Wessem.  --rworkman
graphics/plotutils: Added - plotutils includes libplot (a function to export
  graphics to various formats) and some command line programs for plotting 
  scientific data.  Thanks to Luis Henrique.  --rworkman
graphics/tesseract: Updated for version 2.03 with some script cleanup.
  Thanks to Pierre Cazenave.  --rworkman
libraries/icu4c: Updated for version 4.0.1.
  Thanks to Heinz Wiesinger.  --rworkman
misc/gramps: Added - GRAMPS is a genealogy program for Linux and other
  UNIX-like systems.  Thanks to Bill Kirkpatrick.  --dsomero
misc/heyu: Added - heyu operates an X10 module via a CM11A computer interface.
  Thanks to B. Watson.  --rworkman
multimedia/GoogleEarth: Updated for version 5.0.11337.1968.
  Thanks to Michiel van Wessem.  --rworkman
network/airoscript: Added - Airoscript is a companion tool for aircrack-ng.
  Thanks to Larry Hajali.  --dsomero
network/naim: Added - naim is a console client for AIM, ICQ, IRC, and Lily CMC.
  Thanks to "Nai"  --rworkman
office/broffice.org: Updated for version 3.0.1.  
  Thanks to Eduarda Oda.  --rworkman
office/homebank: Updated for version 4.0.2.  Thanks to Erik Hanson.  --dsomero
system/sleuthkit: Updated for version 3.0.1.
  Thanks to Barry J. Grundy.  --dsomero
system/virtualbox-kernel: Updated for version 2.1.2.
  Thanks to Heinz Wiesinger.  --rworkman
system/virtualbox-kernel-addons: Updated for version 2.1.2.
  Thanks to Heinz Wiesinger.  --rworkman
system/virtualbox-ose: Updated for version 2.1.2.
  Thanks to Heinz Wiesinger.  --rworkman
system/virtualbox-ose-addons: Updated for version 2.1.2.
  Thanks to Heinz Wiesinger.  --rworkman


From xma at gnu.org  Sat Feb  7 23:10:32 2009
From: xma at gnu.org (xma at gnu.org)
Date: Sun, 08 Feb 2009 00:10:32 +0100
Subject: [Slackbuilds-users] gmusicbrowser slackbuild update
Message-ID: <8612.1234048232@zogzog.maillard.mobi>

Hi,

I just uploaded (via upload form) the updated slackbuild script
for gmusicbrowser 1.0.1.

I only changed MD5SUM and version references.

Regards
-- 
Xavier Maillard

From pprkut at liwjatan.at  Mon Feb  9 19:54:31 2009
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Mon, 9 Feb 2009 20:54:31 +0100
Subject: [Slackbuilds-users] desmume problems with nvidia-driver
Message-ID: <200902092054.37119.pprkut@liwjatan.at>

Hi!

I just found out that desmume does not compile on systems where nvidia-driver 
is installed. There's currently no note about this in the README.
I found some information about this here: 
http://forums.desmume.org/viewtopic.php?pid=3175
What users affected by this would need to do is:

nvidia-switch --xorg
./desmume.SlackBuild
nvidia-switch --nvidia

Can something like this be added to the README?

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090209/2512026f/attachment.sig>

From larryhaja at gmail.com  Mon Feb  9 23:04:34 2009
From: larryhaja at gmail.com (Larry Hajali)
Date: Mon, 9 Feb 2009 15:04:34 -0800
Subject: [Slackbuilds-users] desmume problems with nvidia-driver
In-Reply-To: <200902092054.37119.pprkut@liwjatan.at>
References: <200902092054.37119.pprkut@liwjatan.at>
Message-ID: <8ba30f850902091504s4fcf7e62y10da23075b3d176c@mail.gmail.com>

Hello Heinz,

Thanks for bringing this to my attention.  I'm the SBo maintainer of
desmume.

I was unaware of this problem as I don't have an Nvidia card.  I read the
forum post you linked too and I see your suggestion is similar to the one
Ice posted near the end.  The file in question from the post "OGLRender.cpp"
that seems to be causing this has been updated many times in the subversion
directory since version 0.9 was released.  None of the changes say that it
addresses Nvidia drivers.  There is, however, a new version on sourceforge
that was released yestereday.  I've successfully compiled the 0.9.1 version
on a "non-vanilla" Slackware 12.2 w/ATI drivers and a "vanilla" Slackware
12.2 by just changing the version number in the slackbuild.  This doesn't
rectify the issue as I don't have an Nvidia card to test it on.  But it
would be great if you could test out the new release and see if it compiles
on your system with Nvidia drivers?  The new source package can be
downloaded from here:
http://downloads.sourceforge.net/desmume/desmume-0.9.1.tar.gz

I will try to play around with it over the next couple of days and see if I
can find a computer with Nvidia drivers so I can reproduce the error.  Can
you give me more information about your system?  eg. Nvidia Driver version?
is the driver compiled from a slackbuild from slackbuilds.org?  Any other
relevant information?

If nothing has changed since the new release then I will update the
slackbuild with the new version number and the appropriate information in
the README.  Or any other suggestions that slackbuilds.org members would
recommend.

Thanks,
Larry


On Mon, Feb 9, 2009 at 11:54 AM, Heinz Wiesinger <pprkut at liwjatan.at> wrote:

> Hi!
>
> I just found out that desmume does not compile on systems where
> nvidia-driver
> is installed. There's currently no note about this in the README.
> I found some information about this here:
> http://forums.desmume.org/viewtopic.php?pid=3175
> What users affected by this would need to do is:
>
> nvidia-switch --xorg
> ./desmume.SlackBuild
> nvidia-switch --nvidia
>
> Can something like this be added to the README?
>
> Grs,
> Heinz
>
> _______________________________________________
> 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: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090209/f3942760/attachment-0001.htm>

From pprkut at liwjatan.at  Tue Feb 10 11:22:47 2009
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Tue, 10 Feb 2009 12:22:47 +0100
Subject: [Slackbuilds-users] desmume problems with nvidia-driver
In-Reply-To: <8ba30f850902091504s4fcf7e62y10da23075b3d176c@mail.gmail.com>
References: <200902092054.37119.pprkut@liwjatan.at>
	<8ba30f850902091504s4fcf7e62y10da23075b3d176c@mail.gmail.com>
Message-ID: <200902101222.51601.pprkut@liwjatan.at>

Larry Hajali wrote:
> Hello Heinz,
>
> Thanks for bringing this to my attention.  I'm the SBo maintainer of
> desmume.
>
> I was unaware of this problem as I don't have an Nvidia card.  I read the
> forum post you linked too and I see your suggestion is similar to the one
> Ice posted near the end.  The file in question from the post
> "OGLRender.cpp" that seems to be causing this has been updated many times
> in the subversion directory since version 0.9 was released.  None of the
> changes say that it addresses Nvidia drivers.  There is, however, a new
> version on sourceforge that was released yestereday.  I've successfully
> compiled the 0.9.1 version on a "non-vanilla" Slackware 12.2 w/ATI drivers
> and a "vanilla" Slackware 12.2 by just changing the version number in the
> slackbuild.  This doesn't rectify the issue as I don't have an Nvidia card
> to test it on.  But it would be great if you could test out the new release
> and see if it compiles on your system with Nvidia drivers?  The new source
> package can be downloaded from here:
> http://downloads.sourceforge.net/desmume/desmume-0.9.1.tar.gz

Tried it, still the same. No successful build with nvidia-driver active.

> I will try to play around with it over the next couple of days and see if I
> can find a computer with Nvidia drivers so I can reproduce the error.  Can
> you give me more information about your system?  eg. Nvidia Driver version?
> is the driver compiled from a slackbuild from slackbuilds.org?  Any other
> relevant information?

You actually do not need to have nvidia-driver installed to reproduce the 
problem. It seems as if having nvidia's headers is enough. I put a tarball of 
them up on my server 
(http://www.liwjatan.at/files/src/nvidia-headers.tar.gz).
You just have to replace the system headers with those and run the SlackBuild. 
(backup the original ones!)

> If nothing has changed since the new release then I will update the
> slackbuild with the new version number and the appropriate information in
> the README.  Or any other suggestions that slackbuilds.org members would
> recommend.

Thanks!

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090210/73bce8a3/attachment.sig>

From larryhaja at gmail.com  Tue Feb 10 18:21:37 2009
From: larryhaja at gmail.com (Larry Hajali)
Date: Tue, 10 Feb 2009 10:21:37 -0800
Subject: [Slackbuilds-users] desmume problems with nvidia-driver
In-Reply-To: <200902101222.51601.pprkut@liwjatan.at>
References: <200902092054.37119.pprkut@liwjatan.at>
	<8ba30f850902091504s4fcf7e62y10da23075b3d176c@mail.gmail.com>
	<200902101222.51601.pprkut@liwjatan.at>
Message-ID: <8ba30f850902101021t5864dea8i3025c1e12c4a31b1@mail.gmail.com>

>
> Tried it, still the same. No successful build with nvidia-driver active.
>
Yes, I tried it as well with same results.  Using the nvidia-switch --xorg
fixed the issue.


> You actually do not need to have nvidia-driver installed to reproduce the
> problem. It seems as if having nvidia's headers is enough. I put a tarball
> of
> them up on my server
> (http://www.liwjatan.at/files/src/nvidia-headers.tar.gz).
> You just have to replace the system headers with those and run the
> SlackBuild.
> (backup the original ones!)
>
I'll submit a new version update with a note about Nvidia drivers in the
README.

Thanks,
Larry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090210/5e0afa36/attachment.htm>

From me at alkos333.net  Tue Feb 10 18:55:17 2009
From: me at alkos333.net (alkos333)
Date: Tue, 10 Feb 2009 12:55:17 -0600
Subject: [Slackbuilds-users] kvm 78 doesn't compile
Message-ID: <a6f13f000902101055kfee675fuea00a0f51e266498@mail.gmail.com>

there's not such folder created as  $PKG/usr/share/man  anymore
apparently.  That manpage fix appaars to be obsolete

-- 

Doug Larson  - "Instead of giving a politician the keys to the city,
it might be better to change the locks."

From rworkman at slackbuilds.org  Tue Feb 10 19:16:00 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 10 Feb 2009 13:16:00 -0600
Subject: [Slackbuilds-users] kvm 78 doesn't compile
In-Reply-To: <a6f13f000902101055kfee675fuea00a0f51e266498@mail.gmail.com>
References: <a6f13f000902101055kfee675fuea00a0f51e266498@mail.gmail.com>
Message-ID: <20090210131600.64f3e766@liberty.rlwhome.lan>

On Tue, 10 Feb 2009 12:55:17 -0600
alkos333 <me at alkos333.net> wrote:

> there's not such folder created as  $PKG/usr/share/man  anymore
> apparently.  That manpage fix appaars to be obsolete


We've got this handled and ready to push out; it's just a matter of
someone finding time to do the push now...

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090210/11b3cd42/attachment.asc>

From me at alkos333.net  Tue Feb 10 19:21:53 2009
From: me at alkos333.net (alkos333)
Date: Tue, 10 Feb 2009 13:21:53 -0600
Subject: [Slackbuilds-users] kvm 78 doesn't compile
In-Reply-To: <20090210131600.64f3e766@liberty.rlwhome.lan>
References: <a6f13f000902101055kfee675fuea00a0f51e266498@mail.gmail.com>
	<20090210131600.64f3e766@liberty.rlwhome.lan>
Message-ID: <a6f13f000902101121y66eb99a3p6b61759423994aca@mail.gmail.com>

On Tue, Feb 10, 2009 at 1:16 PM, Robby Workman <rworkman at slackbuilds.org> wrote:
> On Tue, 10 Feb 2009 12:55:17 -0600
> alkos333 <me at alkos333.net> wrote:
>
>> there's not such folder created as  $PKG/usr/share/man  anymore
>> apparently.  That manpage fix appaars to be obsolete
>
>
> We've got this handled and ready to push out; it's just a matter of
> someone finding time to do the push now...
>
> -RW
>
> _______________________________________________
> 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/
>
>
>

Robby,

could you bump it up to 83 as well?  I just compiled it and no other
modifications are required really.


Thanks,
Alex


-- 

Marlene Dietrich  - "Most women set out to try to change a man, and
when they have changed him they do not like h...

From me at alkos333.net  Tue Feb 10 19:27:48 2009
From: me at alkos333.net (alkos333)
Date: Tue, 10 Feb 2009 13:27:48 -0600
Subject: [Slackbuilds-users] kvm 78 doesn't compile
In-Reply-To: <a6f13f000902101121y66eb99a3p6b61759423994aca@mail.gmail.com>
References: <a6f13f000902101055kfee675fuea00a0f51e266498@mail.gmail.com>
	<20090210131600.64f3e766@liberty.rlwhome.lan>
	<a6f13f000902101121y66eb99a3p6b61759423994aca@mail.gmail.com>
Message-ID: <a6f13f000902101127w7f64fffcj39573b3378eb663d@mail.gmail.com>

On Tue, Feb 10, 2009 at 1:21 PM, alkos333 <me at alkos333.net> wrote:
> On Tue, Feb 10, 2009 at 1:16 PM, Robby Workman <rworkman at slackbuilds.org> wrote:
>> On Tue, 10 Feb 2009 12:55:17 -0600
>> alkos333 <me at alkos333.net> wrote:
>>
>>> there's not such folder created as  $PKG/usr/share/man  anymore
>>> apparently.  That manpage fix appaars to be obsolete
>>
>>
>> We've got this handled and ready to push out; it's just a matter of
>> someone finding time to do the push now...
>>
>> -RW
>>
>> _______________________________________________
>> 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/
>>
>>
>>
>
> Robby,
>
> could you bump it up to 83 as well?  I just compiled it and no other
> modifications are required really.
>
>
> Thanks,
> Alex
>
>
> --
>
> Marlene Dietrich  - "Most women set out to try to change a man, and
> when they have changed him they do not like h...
>

Also,

kvm's README says to do "/etc/rc.d/rc.udev reload," but I get the following:



root at tpt60:/etc/rc.d# /etc/rc.d/rc.udev reload
Reloading udev rules
udevadm control commands requires the --<command> format, this will
stop working in a future release


It looks like rc.udev needs modification.

-- 

Marlene Dietrich  - "Most women set out to try to change a man, and
when they have changed him they do not like h...

From nille.kungen at gmail.com  Tue Feb 10 19:45:46 2009
From: nille.kungen at gmail.com (=?ISO-8859-1?Q?Niklas_=27Nille=27_=C5kerstr=F6m?=)
Date: Tue, 10 Feb 2009 20:45:46 +0100
Subject: [Slackbuilds-users] kvm 78 doesn't compile
In-Reply-To: <a6f13f000902101127w7f64fffcj39573b3378eb663d@mail.gmail.com>
References: <a6f13f000902101055kfee675fuea00a0f51e266498@mail.gmail.com>	<20090210131600.64f3e766@liberty.rlwhome.lan>	<a6f13f000902101121y66eb99a3p6b61759423994aca@mail.gmail.com>
	<a6f13f000902101127w7f64fffcj39573b3378eb663d@mail.gmail.com>
Message-ID: <4991D96A.40209@gmail.com>

alkos333 wrote:
> Also,
>
> kvm's README says to do "/etc/rc.d/rc.udev reload," but I get the following:
>
>
>
> root at tpt60:/etc/rc.d# /etc/rc.d/rc.udev reload
> Reloading udev rules
> udevadm control commands requires the --<command> format, this will
> stop working in a future release
>
>
> It looks like rc.udev needs modification
I sent pat an patch for that after the 12.2 release. (2008-12-25)
But i might need to send it again.


From rworkman at slackbuilds.org  Tue Feb 10 21:03:25 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 10 Feb 2009 15:03:25 -0600
Subject: [Slackbuilds-users] kvm 78 doesn't compile
In-Reply-To: <a6f13f000902101121y66eb99a3p6b61759423994aca@mail.gmail.com>
References: <a6f13f000902101055kfee675fuea00a0f51e266498@mail.gmail.com>
	<20090210131600.64f3e766@liberty.rlwhome.lan>
	<a6f13f000902101121y66eb99a3p6b61759423994aca@mail.gmail.com>
Message-ID: <20090210150325.7577331f@liberty.rlwhome.lan>

On Tue, 10 Feb 2009 13:21:53 -0600
alkos333 <me at alkos333.net> wrote:

> Robby,
> 
> could you bump it up to 83 as well?  I just compiled it and no other
> modifications are required really.


It's already at 83 in READY. :)

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090210/50e54b0f/attachment.asc>

From rworkman at slackbuilds.org  Tue Feb 10 21:08:44 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 10 Feb 2009 15:08:44 -0600
Subject: [Slackbuilds-users] kvm 78 doesn't compile
In-Reply-To: <a6f13f000902101127w7f64fffcj39573b3378eb663d@mail.gmail.com>
References: <a6f13f000902101055kfee675fuea00a0f51e266498@mail.gmail.com>
	<20090210131600.64f3e766@liberty.rlwhome.lan>
	<a6f13f000902101121y66eb99a3p6b61759423994aca@mail.gmail.com>
	<a6f13f000902101127w7f64fffcj39573b3378eb663d@mail.gmail.com>
Message-ID: <20090210150844.0bb027b2@liberty.rlwhome.lan>

On Tue, 10 Feb 2009 13:27:48 -0600
alkos333 <me at alkos333.net> wrote:

> root at tpt60:/etc/rc.d# /etc/rc.d/rc.udev reload
> Reloading udev rules
> udevadm control commands requires the --<command> format, this will
> stop working in a future release
> 
> It looks like rc.udev needs modification.


I've got this addressed in my staging tree, along with some other udev
changes.  Thanks for the reminder.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090210/ac97ab0a/attachment-0001.asc>

From chess at chessgriffin.com  Wed Feb 11 01:13:01 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Tue, 10 Feb 2009 20:13:01 -0500
Subject: [Slackbuilds-users] Moving sbopkg to /usr/sbin and require root
Message-ID: <20090211011300.GA13725@localhost>

Sorry for the cross-post to sbopkg and slackbuilds.org mailing lists but
I want to get as much feedback as possible.

Currently, sbopkg can be run by root or a non-root user.  Certain
functions or features can only be done by a root user, of course, like
building and installing packages.  However, trying to maintain this dual
permission standard is becoming very problematic.  More than once I have
considered removing the 'user-mode' from sbopkg, move sbopkg to
/usr/sbin, and require sbopkg be run only by the root user, like
pkgtool, slackpkg, and other similar tools require.  Several unrelated
issues have brought this to the forefront again and I am now very much
leaning towards making this change.

So, the question is:  how many people feel strongly about keeping the
ability to run sbopkg as a non-root user?  Could folks adapt to using
sbopkg only as root?

Feel free to respond on the list or privately.

Thank you in advance for your feedback.

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090210/ca7ff437/attachment.sig>

From me at alkos333.net  Wed Feb 11 01:26:48 2009
From: me at alkos333.net (alkos333)
Date: Tue, 10 Feb 2009 19:26:48 -0600
Subject: [Slackbuilds-users] Moving sbopkg to /usr/sbin and require root
In-Reply-To: <20090211011300.GA13725@localhost>
References: <20090211011300.GA13725@localhost>
Message-ID: <a6f13f000902101726j4a2e1c08hd61ca83ff6562762@mail.gmail.com>

On Tue, Feb 10, 2009 at 7:13 PM, Chess Griffin <chess at chessgriffin.com> wrote:
> Sorry for the cross-post to sbopkg and slackbuilds.org mailing lists but
> I want to get as much feedback as possible.
>
> Currently, sbopkg can be run by root or a non-root user.  Certain
> functions or features can only be done by a root user, of course, like
> building and installing packages.  However, trying to maintain this dual
> permission standard is becoming very problematic.  More than once I have
> considered removing the 'user-mode' from sbopkg, move sbopkg to
> /usr/sbin, and require sbopkg be run only by the root user, like
> pkgtool, slackpkg, and other similar tools require.  Several unrelated
> issues have brought this to the forefront again and I am now very much
> leaning towards making this change.
>
> So, the question is:  how many people feel strongly about keeping the
> ability to run sbopkg as a non-root user?  Could folks adapt to using
> sbopkg only as root?
>
> Feel free to respond on the list or privately.
>
> Thank you in advance for your feedback.
>

root only - keep the code simple

From ricardsonwilliams at gmail.com  Wed Feb 11 01:55:58 2009
From: ricardsonwilliams at gmail.com (Ricardson Williams)
Date: Wed, 11 Feb 2009 09:55:58 +0800
Subject: [Slackbuilds-users] Moving sbopkg to /usr/sbin and require root
In-Reply-To: <a6f13f000902101726j4a2e1c08hd61ca83ff6562762@mail.gmail.com>
References: <20090211011300.GA13725@localhost>
	<a6f13f000902101726j4a2e1c08hd61ca83ff6562762@mail.gmail.com>
Message-ID: <5eb6ff2c0902101755i352d1862t3fd25dcbf3e75481@mail.gmail.com>

I use only by root....

On Wed, Feb 11, 2009 at 9:26 AM, alkos333 <me at alkos333.net> wrote:

> On Tue, Feb 10, 2009 at 7:13 PM, Chess Griffin <chess at chessgriffin.com>
> wrote:
> > Sorry for the cross-post to sbopkg and slackbuilds.org mailing lists but
> > I want to get as much feedback as possible.
> >
> > Currently, sbopkg can be run by root or a non-root user.  Certain
> > functions or features can only be done by a root user, of course, like
> > building and installing packages.  However, trying to maintain this dual
> > permission standard is becoming very problematic.  More than once I have
> > considered removing the 'user-mode' from sbopkg, move sbopkg to
> > /usr/sbin, and require sbopkg be run only by the root user, like
> > pkgtool, slackpkg, and other similar tools require.  Several unrelated
> > issues have brought this to the forefront again and I am now very much
> > leaning towards making this change.
> >
> > So, the question is:  how many people feel strongly about keeping the
> > ability to run sbopkg as a non-root user?  Could folks adapt to using
> > sbopkg only as root?
> >
> > Feel free to respond on the list or privately.
> >
> > Thank you in advance for your feedback.
> >
>
> root only - keep the code simple
> _______________________________________________
> 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/
>
>


-- 
[],
Ricardson Williams
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090211/1d9bee58/attachment.htm>

From pc_warner at yahoo.com  Wed Feb 11 02:59:20 2009
From: pc_warner at yahoo.com (Phillip Warner)
Date: Tue, 10 Feb 2009 18:59:20 -0800 (PST)
Subject: [Slackbuilds-users] Moving sbopkg to /usr/sbin and require root
In-Reply-To: <20090211011300.GA13725@localhost>
Message-ID: <555619.37204.qm@web57708.mail.re3.yahoo.com>

--- On Tue, 2/10/09, Chess Griffin <chess at chessgriffin.com> wrote:

> So, the question is:  how many people feel strongly about
> keeping the
> ability to run sbopkg as a non-root user?  Could folks
> adapt to using
> sbopkg only as root?

ROOT-only sounds fine to me.  The main use of a non-root user for me would be for testing SlackBuilds, and I don't have to use sbopkg for this (though root could drop perms as mentioned in a feature request).

Non-root users really only need to view the Changelog and search/browse the repo.  Non-admins could just use links/lynx on SBo if they need this from their console ;)

--phillip


      

From mannyslack at ver.megared.net.mx  Wed Feb 11 03:33:53 2009
From: mannyslack at ver.megared.net.mx (mannyslack)
Date: Tue, 10 Feb 2009 21:33:53 -0600
Subject: [Slackbuilds-users] Moving sbopkg to /usr/sbin and require root
In-Reply-To: <20090211011300.GA13725@localhost>
References: <20090211011300.GA13725@localhost>
Message-ID: <49924721.8060601@ver.megared.net.mx>

Chess Griffin wrote:
> ..Could folks adapt to using
> sbopkg only as root?
>   
Yes, root only sounds good.
Greetings :)

From chris.abela at maltats.com  Wed Feb 11 08:33:08 2009
From: chris.abela at maltats.com (Chris Abela)
Date: Wed, 11 Feb 2009 09:33:08 +0100
Subject: [Slackbuilds-users] rc-script permissions
Message-ID: <E1LXAWx-00030w-3x@fender50.maltanet.net>


Further to a discussion that ensued on a linuxquestions.org thread:
http://www.linuxquestions.org/questions/slackware-14/virtualbox-2.1.2-slackb
uild-699309/
I noted that the permissions on rc-scripts installed by Slackbuild packages
are not consistent. Moreover the default permissions are not documented by
the specific slackbuilds README files. A solution might be one of the
following:
1. Specify the default permissions on rc-scripts for all slackbuilds (say
7xx)
2. Specify that README files shall declare the default rc-scripts
permissions.
3. Warn users that there are no rules in this regard and they should check
them out themselves (if they exist).

Chris


From mauro.giachero at gmail.com  Wed Feb 11 09:38:42 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Wed, 11 Feb 2009 10:38:42 +0100
Subject: [Slackbuilds-users] [sbopkg-discuss] Moving sbopkg to /usr/sbin
	and require root
In-Reply-To: <20090211011300.GA13725@localhost>
References: <20090211011300.GA13725@localhost>
Message-ID: <da3e877f0902110138n55b6c29eme3d49f8232df1bde@mail.gmail.com>

I also think that user-mode support should be tossed.

-- 
Mauro Giachero
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090211/c5f94dd7/attachment.htm>

From serban.udrea at skmail.ikp.physik.tu-darmstadt.de  Wed Feb 11 10:39:15 2009
From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea)
Date: Wed, 11 Feb 2009 11:39:15 +0100
Subject: [Slackbuilds-users] Moving sbopkg to /usr/sbin and require root
In-Reply-To: <20090211011300.GA13725@localhost>
References: <20090211011300.GA13725@localhost>
Message-ID: <4992AAD3.5070202@skmail.ikp.physik.tu-darmstadt.de>

Chess Griffin wrote:
> Sorry for the cross-post to sbopkg and slackbuilds.org mailing lists but
> I want to get as much feedback as possible.
 >

Hello!

I dare to disagree with other posters. I actually do not understand why 
anything else but installing the final package needs root rights. I am 
(still) working on some packages I hope to submit soon and I do 
everything but package installation/removal as a normal user without 
problems.  Thus I would actually drop root for anything but final 
installation/removal. In my opinion it is always good to use root rights 
as sparingly as possible.

I do not know how big a problem is to change sbopkg, such that just the 
last step needs root rights, but I would say that a first change would 
be to have sbopkg default directories with access rights like /tmp.

Another possibility would be to have a sbopkg group and just users 
belonging to this group would be allowed to use sbopkg, which may be 
achieved by the default access rights to sbopkg's directories.

Another point is that all the SlackBuilds I looked at have

chown -R root:root .

which doesn't work if you are a normal user (at least on my machine).

At the moment I use

chown -R $UID:$GROUPS .

which seems to work OK but I do not know if it is acceptable, because I 
didn't submit any SlackBuild until now.

Finally, I wouldn't compare sbopkg with other tools which work just with 
ready-made packages, since those tools just need to do what is to be 
done as root.

Best regards,

Serban Udrea

From chaos.proton at gmail.com  Wed Feb 11 10:47:32 2009
From: chaos.proton at gmail.com (Grissiom)
Date: Wed, 11 Feb 2009 18:47:32 +0800
Subject: [Slackbuilds-users] Moving sbopkg to /usr/sbin and require root
In-Reply-To: <555619.37204.qm@web57708.mail.re3.yahoo.com>
References: <20090211011300.GA13725@localhost>
	<555619.37204.qm@web57708.mail.re3.yahoo.com>
Message-ID: <a0adeea50902110247g5ae7f30bh7df20afb45643de9@mail.gmail.com>

On Wed, Feb 11, 2009 at 10:59, Phillip Warner <pc_warner at yahoo.com> wrote:

> --- On Tue, 2/10/09, Chess Griffin <chess at chessgriffin.com> wrote:
>
> > So, the question is:  how many people feel strongly about
> > keeping the
> > ability to run sbopkg as a non-root user?  Could folks
> > adapt to using
> > sbopkg only as root?
>
> ROOT-only sounds fine to me.  The main use of a non-root user for me would
> be for testing SlackBuilds, and I don't have to use sbopkg for this (though
> root could drop perms as mentioned in a feature request).
>
> Non-root users really only need to view the Changelog and search/browse the
> repo.  Non-admins could just use links/lynx on SBo if they need this from
> their console ;)
>

So, is there any possiblity that seperate the script into two, one requered
root permission(install/upgrade/remove pkg etc.), one doesn't need(rsync
local repository, search/brows installed pkg etc.). This way can avoid a
root own huge local repository and convienent for daily use.

-- 
Cheers,
Grissiom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090211/182f2c6e/attachment-0001.htm>

From marco.bonetti at slackware.it  Wed Feb 11 10:53:02 2009
From: marco.bonetti at slackware.it (Marco Bonetti)
Date: Wed, 11 Feb 2009 11:53:02 +0100 (CET)
Subject: [Slackbuilds-users] Moving sbopkg to /usr/sbin and require root
In-Reply-To: <4992AAD3.5070202@skmail.ikp.physik.tu-darmstadt.de>
References: <20090211011300.GA13725@localhost>
	<4992AAD3.5070202@skmail.ikp.physik.tu-darmstadt.de>
Message-ID: <37086.212.48.3.167.1234349582.squirrel@webmail.slackware.it>

On Wed, February 11, 2009 11:39, Serban Udrea wrote:
> Another point is that all the SlackBuilds I looked at have
>
> chown -R root:root .
>
> which doesn't work if you are a normal user (at least on my machine).
>
> At the moment I use
>
> chown -R $UID:$GROUPS .
>
> which seems to work OK but I do not know if it is acceptable, because I
> didn't submit any SlackBuild until now.
(note: I'm not a slackbuilds.org core developer)
It's wrong, since the standard is to have executables owned as root:root.
Slackware itself changed its own root:bin in favor of root:root some
version ago so, for simplicity sake, just stick with the standards :)
I use sbopkg as a tool like Gentoo emerge in order to fetch, build and
install programs system wide and I like this way. If you're worried about
building packages as root, use a separate (virtual, maybe) machine and
lock it down: build packages on that machine and install them on yours.

ciao

-- 
Marco Bonetti
BT3 EeePC enhancing module: http://sid77.slackware.it/bt3/
Slackintosh Linux Project Developer: http://workaround.ch/
Linux-live for powerpc: http://workaround.ch/pub/rsync/mb/linux-live/
My webstuff: http://sidbox.homelinux.org/

My GnuPG key id: 0x86A91047


From pc_warner at yahoo.com  Wed Feb 11 11:51:35 2009
From: pc_warner at yahoo.com (Phillip Warner)
Date: Wed, 11 Feb 2009 03:51:35 -0800 (PST)
Subject: [Slackbuilds-users] WINE SlackBuild - #chown ...
In-Reply-To: <37086.212.48.3.167.1234349582.squirrel@webmail.slackware.it>
Message-ID: <704316.48610.qm@web57702.mail.re3.yahoo.com>

Just noticed this in the WINE SlackBuild

  #chown -R root:root .

--phillip


      

From serban.udrea at skmail.ikp.physik.tu-darmstadt.de  Wed Feb 11 15:14:11 2009
From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea)
Date: Wed, 11 Feb 2009 16:14:11 +0100
Subject: [Slackbuilds-users] Moving sbopkg to /usr/sbin and require root
In-Reply-To: <37086.212.48.3.167.1234349582.squirrel@webmail.slackware.it>
References: <20090211011300.GA13725@localhost>
	<4992AAD3.5070202@skmail.ikp.physik.tu-darmstadt.de>
	<37086.212.48.3.167.1234349582.squirrel@webmail.slackware.it>
Message-ID: <4992EB43.2030701@skmail.ikp.physik.tu-darmstadt.de>

Marco Bonetti wrote:
> On Wed, February 11, 2009 11:39, Serban Udrea wrote:
>> Another point is that all the SlackBuilds I looked at have
>>
>> chown -R root:root .
>>
>> which doesn't work if you are a normal user (at least on my machine).
>>
>> At the moment I use
>>
>> chown -R $UID:$GROUPS .
>>
>> which seems to work OK but I do not know if it is acceptable, because I
>> didn't submit any SlackBuild until now.
> (note: I'm not a slackbuilds.org core developer)

Neither I.

> It's wrong, since the standard is to have executables owned as root:root.

Not necessarily wrong, if you run the script as root you get the right 
ownership. Moreover "chown root:root" can be applied in the post-install 
script to what got installed, it's not necessary to have it in the 
SlackBuild.

An alternative to what I'm doing now may be to define two variables in 
the SlackBuild, say USR and GRP, which both default to root but may be 
redefined when running the script.

> I use sbopkg as a tool like Gentoo emerge in order to fetch, build and
> install programs system wide and I like this way.

Your choice.

> If you're worried about
> building packages as root, use a separate (virtual, maybe) machine and
> lock it down: build packages on that machine and install them on yours.

Not everybody has a spare machine or the skill and/or time of playing 
around with virtualisation. I miss at least the machine and the time.

Best regards,

Serban Udrea

From eha at sox.homeip.net  Wed Feb 11 15:29:58 2009
From: eha at sox.homeip.net (Eric Hameleers)
Date: Wed, 11 Feb 2009 16:29:58 +0100 (CET)
Subject: [Slackbuilds-users] Moving sbopkg to /usr/sbin and require root
In-Reply-To: <4992EB43.2030701@skmail.ikp.physik.tu-darmstadt.de>
References: <20090211011300.GA13725@localhost>
	<4992AAD3.5070202@skmail.ikp.physik.tu-darmstadt.de>
	<37086.212.48.3.167.1234349582.squirrel@webmail.slackware.it>
	<4992EB43.2030701@skmail.ikp.physik.tu-darmstadt.de>
Message-ID: <Pine.LNX.4.61.0902111624110.29698@door.barrier.lan>

On Wed, 11 Feb 2009, Serban Udrea wrote:

> Marco Bonetti wrote:
>> On Wed, February 11, 2009 11:39, Serban Udrea wrote:
>>> Another point is that all the SlackBuilds I looked at have
>>> 
>>> chown -R root:root .
>>> 
>>> which doesn't work if you are a normal user (at least on my machine).
>>> 
>>> At the moment I use
>>> 
>>> chown -R $UID:$GROUPS .
>>> 
>>> which seems to work OK but I do not know if it is acceptable, because I
>>> didn't submit any SlackBuild until now.
>> (note: I'm not a slackbuilds.org core developer)
>
> Neither I.
>
>> It's wrong, since the standard is to have executables owned as root:root.
>
> Not necessarily wrong, if you run the script as root you get the right 
> ownership. Moreover "chown root:root" can be applied in the post-install 
> script to what got installed, it's not necessary to have it in the 
> SlackBuild.
>
> An alternative to what I'm doing now may be to define two variables in the 
> SlackBuild, say USR and GRP, which both default to root but may be redefined 
> when running the script.
>
>> I use sbopkg as a tool like Gentoo emerge in order to fetch, build and
>> install programs system wide and I like this way.
>
> Your choice.
>
>> If you're worried about
>> building packages as root, use a separate (virtual, maybe) machine and
>> lock it down: build packages on that machine and install them on yours.
>
> Not everybody has a spare machine or the skill and/or time of playing around 
> with virtualisation. I miss at least the machine and the time.

At slackbuilds.org we will only accept submissions that should be run as 
the root user. This is a policy decision we took when we setup the site, 
we want our SlackBuilds to behave the same as the SlackBuild scripts you 
find in Slackware itself. Yes, running a script as root has it's dangers, 
but that is exactly why we (admins) do the QA checks and add a GPG 
signature to all our published tarballs: we want to guarantee the users of 
our scripts that they are safe to run, even as root.

Please keep this in mind when you submit the scripts you are developing. 
Use the template.SlackBuild at http://slackbuilds.org/template.SlackBuild 
as an example if you are not sure of how to create a script that will be 
accepted by us.

Eric

-- 
Eric Hameleers
Email: alien at slackware.com
Jabber: alien at jabber.xs4all.nl
Gpg fingerprint: F2CE 1B92 EE1F 2C0C E97E  581E 5E56 AAAF A75C BDA0

From arthurfontolan at gmail.com  Wed Feb 11 14:59:24 2009
From: arthurfontolan at gmail.com (Arthur Fontolan)
Date: Wed, 11 Feb 2009 11:59:24 -0300
Subject: [Slackbuilds-users] Slackbuilds adesklets
Message-ID: <285d558c0902110659l316209efx3f5895cb686ed801@mail.gmail.com>

Hello,

I sent a patch and the modified file adesklets.Slackbuild.

The changes that made the original slackbuild was the removal of the lines
below as an option to configure. They do not exist in the configure (. /
configure --help) of adesklets. They are:

- with-perl = /usr /bin /perl \
- enable-eps \
- enable-gif \
- enable-png \

And the inclusion of the lines below, which apply the patch file
adesklets.diff, correcting the error with fontconfig> = 2.4

# Copy patch file to the src path
cp $ CWD / adesklets.diff $ TMP / $ PRGNAM-$ VERSION

# apply the patch
patch-p1 <adesklets.diff

# regen. configure script
autoreconf

# Fix compile error in man docs
sed-i 's: / bin / sh $ (SHELL) / bin / sh: g' doc / Makefile

I am sending the attached slackbuild with the changes and the patch file.

The corrections were based on instructions contained in the sites
http://adesklets.sourceforge.net,
http://manualinux.my-place.us/adesklets.html.

The patch can be found in repositories of ArchLinux AUR in the Gentoo
repositories in the GIT repository adesklets or on-site manualinux.my-
place.us.

Thanks

Arthur Fontolan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090211/8a318664/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: adesklets.SlackBuild
Type: application/octet-stream
Size: 3485 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090211/8a318664/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: adesklets.diff
Type: application/octet-stream
Size: 2008 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090211/8a318664/attachment-0001.obj>

From rworkman at slackbuilds.org  Wed Feb 11 15:47:40 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 11 Feb 2009 09:47:40 -0600
Subject: [Slackbuilds-users] WINE SlackBuild - #chown ...
In-Reply-To: <704316.48610.qm@web57702.mail.re3.yahoo.com>
References: <37086.212.48.3.167.1234349582.squirrel@webmail.slackware.it>
	<704316.48610.qm@web57702.mail.re3.yahoo.com>
Message-ID: <20090211094740.0c79fb4d@liberty.rlwhome.lan>

On Wed, 11 Feb 2009 03:51:35 -0800 (PST)
Phillip Warner <pc_warner at yahoo.com> wrote:

> Just noticed this in the WINE SlackBuild
> 
>   #chown -R root:root .


I don't know who fixed it, but someone beat me to it.
Thanks for the heads-up.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090211/9337cefe/attachment-0001.asc>

From mauro.giachero at gmail.com  Wed Feb 11 16:00:49 2009
From: mauro.giachero at gmail.com (Mauro Giachero)
Date: Wed, 11 Feb 2009 17:00:49 +0100
Subject: [Slackbuilds-users]  Moving sbopkg to /usr/sbin and require root
In-Reply-To: <4992AAD3.5070202@skmail.ikp.physik.tu-darmstadt.de>
References: <20090211011300.GA13725@localhost>
	<4992AAD3.5070202@skmail.ikp.physik.tu-darmstadt.de>
Message-ID: <da3e877f0902110800u43d5f6fap73ca7ebda53e2859@mail.gmail.com>

On Wed, Feb 11, 2009 at 11:39 AM, Serban Udrea <
serban.udrea at skmail.ikp.physik.tu-darmstadt.de> wrote:

> Hello!


Hello!

I dare to disagree with other posters.I actually do not understand why
> anything else but installing the final package needs root rights. I am
> (still) working on some packages I hope to submit soon and I do everything
> but package installation/removal as a normal user without problems.  Thus I
> would actually drop root for anything but final installation/removal. In my
> opinion it is always good to use root rights as sparingly as possible.
>
> I do not know how big a problem is to change sbopkg, such that just the
> last step needs root rights, but I would say that a first change would be to
> have sbopkg default directories with access rights like /tmp.


There are two ways of thinking "user-mode" support:
- one is to allow normal users to do what a normal user can (like browsing
the package repository), but not allowing root-only operations (e.g.
removing some options from the menus) -- this is what we currently have in
sbopkg;
- the other is to always show all the operations, asking the root password
for those which are admin-only -- this is what you're talking about.

The first option is something that clutters the code and brings very little
advantages, thus Chess' proposal to remove it.

Your approach would need to be implemented from scratch, as there's
currently nothing like that in sbopkg. That would require at least the usage
of fakeroot (which is unsupported by the SBo admins and therefore a possible
source of problems) and the admin should set up sudo and use directories
with proper access permissions (the security-aware defaults aren't likely to
change).
This can happen at some point in the future. But don't expect it to happen
tomorrow ;-)

Thank you for daring to disagree!

>
Regards
-- 
Mauro Giachero
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090211/968a4f2a/attachment.htm>

From rworkman at slackbuilds.org  Wed Feb 11 16:40:46 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 11 Feb 2009 16:40:46 +0000
Subject: [Slackbuilds-users] Updates - 20090211
Message-ID: <20090211164046.GA21575@slackbuilds.org>

Wed Feb 11 16:38:56 UTC 2009
academic/ent: Added - ent is a pseudorandom number sequence test program.
  Thanks to B. Watson.  --rworkman
academic/speedcrunch: Added - SpeedCrunch is a fast, high precision and 
  powerful desktop calculator.  Thanks to Larry Hajali.  --rworkman
desktop/crystal: Updated for version 1.0.7.
  Thanks to Michiel van Wessem.  --dsomero
development/kdbg: Updated for version 2.1.1.
  Thanks to Michiel van Wessem.  --rworkman
development/monotone: Added - Monotone is a distributed version control system.
  Thanks to Joao Felipe Santos.  --rworkman
development/openmpi: Updated for version 1.3.
  Thanks to Aleksandar Samardzic.  --dsomero
games/frotz: Added - Frotz is an interpreter for Infocom games and other 
  Z-machine games.  Thanks to Beej Jorgensen.  --rworkman
graphics/raw-thumbnailer: Updated for version 0.2.
  Thanks to Michiel van Wessem.  --dsomero
libraries/SDL_gfx: Updated for version 2.0.18.
  Thanks to Michiel van Wessem.  --dsomero
libraries/exempi: Updated for version 2.1.0.
  Thanks to Michiel van Wessem.  --dsomero
libraries/gtksourceview: Updated for version 2.4.2.
  Thanks to Michiel van Wessem.  --dsomero
libraries/libopenraw: Updated for version 0.0.5.
  Thanks to Michiel van Wessem.  --dsomero
libraries/slib: Fixed a problem with the /usr/bin/slib script having some
  references to the $PKG directory; the upstream Makefile is quite, um, bad.
  Thanks to Old_Fogie for the report.  --rworkman
libraries/yaz: Updated for version 3.0.42.
  Thanks to Michiel van Wessem.  --dsomero
misc/bchunk: Added - bchunk (bin chunker) is used for converting bin/cue 
  images to ISO images.  Thanks to Vincent Batts.  --rworkman
misc/kvm: Updated for version 83.  Thanks to Murat D. Kadirov.  --rworkman
multimedia/gst-plugins-good: Updated for version 0.10.13.
  Thanks to Michiel van Wessem.  --dsomero
network/GhostInTheMail: Added - Ghost In The Mail is a very basic mail client.
  Thanks to majk.  --rworkman
network/gns3: Added - GNS3 is a graphical network simulator for Cisco networks.
  Thanks to Alam Guntur Nugroho.  --rworkman
network/hostapd: Updated for version 0.5.11.
  Thanks to Murat D. Kadirov.  --rworkman
network/js: Updated for version 1.7.0.  Thanks to David Woodfall.  --rworkman
network/shorewall-{common,perl,shell}: Added - the Shoreline Firewall, more 
  commonly known as Shorewall, is a frontend to netfilter/iptables.
  Thanks to "ArTourter"  --rworkman
network/squid: Updated for version 3.0STABLE13.  Thanks to David Somero.
network/wireshark: Updated for version 1.0.6.
  Thanks to Michiel van Wessem.  --dsomero
network/xtables-addons: Fixed the build script to not include the make-generated
  module metadata inside the package.  --rworkman
office/calcurse: Updated for version 2.5.
  Thanks to Michiel van Wessem.  --dsomero
office/openoffice.org: Fixed a bug in the build script caused by removing the
  fonts from the package (yeah, I should have known).  We're now only removing
  the DejaVu and Liberation fonts, leaving the opens___.ttf (which is used by
  some formulas) there.  Thanks to Mauro Giachero for the bug report, analysis,
  and patch.  --rworkman
office/kile: Updated for version 2.0.3.
  Thanks to Michiel van Wessem.  --dsomero
system/clex: Added - CLEX is a file manager with a full-screen user interface 
  written in C with the curses library.  Thanks to majk.  --rworkman
system/gparted: Updated for version 0.4.2.  Thanks to Erik Hanson.  --dsomero
system/postgresql: Updated for version 8.3.6.  Thanks to Adis Nezirovic.
system/webmin: Updated for version 1.450.  Thanks to David Somero.  --rworkman


From fullofdaylight at no-log.org  Wed Feb 11 21:00:59 2009
From: fullofdaylight at no-log.org (fullofdaylight at no-log.org)
Date: Wed, 11 Feb 2009 22:00:59 +0100 (CET)
Subject: [Slackbuilds-users] [xmoto] Can't compile 0.5.0 due to sqlite?
Message-ID: <60699.AVAGD19SXH8=.1234386059.squirrel@webmail.no-log.org>

Hello,

I'm trying to update the xmoto SlackBuild (still at 0.2.4 when 0.5.0 has
been out for some time), but can't get the program to compile.
Independently from the options passed, the configure step fails at :
"""
checking sqlite3.h usability... yes
checking sqlite3.h presence... yes
checking for sqlite3.h... yes
checking for main in -lsqlite3... no
configure: error: "Linking against sqlite3 failed."
"""
I'm using the unmodified sqlite3 from the stock Slackware 12.2.

I'd like to know if others are getting the same result, and if so if it's
a Slackware related problem or an xmoto one.

Thanks!

From hba.nihilismus at gmail.com  Thu Feb 12 06:03:28 2009
From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=)
Date: Thu, 12 Feb 2009 00:03:28 -0600
Subject: [Slackbuilds-users] Typo in gnustep-base's slack-desc.
Message-ID: <39be090902112203x1250fbe0i8568cf4341815f1a@mail.gmail.com>

In http://slackbuilds.org/slackbuilds/12.2/libraries/gnustep-base/slack-desc
there's this line:
gnustep-make: Homepage: http://www.gnustep.org

It should be:
gnustep-base: Homepage: http://www.gnustep.org

All the others gnustep-* slack-descs are correct.

-hba

From kackmail at yahoo.de  Thu Feb 12 13:16:00 2009
From: kackmail at yahoo.de (Sepp Meier)
Date: Thu, 12 Feb 2009 13:16:00 +0000 (GMT)
Subject: [Slackbuilds-users] Request for Miro 2.0
Message-ID: <415881.93651.qm@web24202.mail.ird.yahoo.com>

Hello,

I didn't find anything about requests for Slackbuilds in the FAQ, so I simply ask here and hope, this is the right place to do.
I would like to have a Slackbuild Miro 2.0, but I don't have any Phyton expierience, and do absolutely not understand how it installs. Maybe someone of the Slackbuild team or a contributor is also interested in Miro 2.0 and has the required knowledge to do a Slackbuild, this would be great.

Thanks,

Joe



      

From alkos333 at gmail.com  Thu Feb 12 15:45:12 2009
From: alkos333 at gmail.com (alkos333)
Date: Thu, 12 Feb 2009 09:45:12 -0600
Subject: [Slackbuilds-users] Updates - 20090211
In-Reply-To: <20090211164046.GA21575@slackbuilds.org>
References: <20090211164046.GA21575@slackbuilds.org>
Message-ID: <a6f13f000902120745k17e9811cqb2e995ed71e6bae@mail.gmail.com>

2009/2/11 Robby Workman <rworkman at slackbuilds.org>:
> misc/kvm: Updated for version 83.  Thanks to Murat D. Kadirov.  --rworkman

Still getting the error when it gets to the mv command for the usr/man

From rworkman at slackbuilds.org  Thu Feb 12 18:22:25 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 12 Feb 2009 12:22:25 -0600
Subject: [Slackbuilds-users] Updates - 20090211
In-Reply-To: <a6f13f000902120745k17e9811cqb2e995ed71e6bae@mail.gmail.com>
References: <20090211164046.GA21575@slackbuilds.org>
	<a6f13f000902120745k17e9811cqb2e995ed71e6bae@mail.gmail.com>
Message-ID: <20090212122225.05c9e0cf@liberty.rlwhome.lan>

On Thu, 12 Feb 2009 09:45:12 -0600
alkos333 <alkos333 at gmail.com> wrote:

> 2009/2/11 Robby Workman <rworkman at slackbuilds.org>:
> > misc/kvm: Updated for version 83.  Thanks to Murat D. Kadirov.
> > --rworkman
> 
> Still getting the error when it gets to the mv command for the usr/man


Check again - it works fine here.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090212/a34d833b/attachment.asc>

From burningc at sdf.lonestar.org  Thu Feb 12 19:47:44 2009
From: burningc at sdf.lonestar.org (Glenn Becker)
Date: Thu, 12 Feb 2009 19:47:44 +0000 (UTC)
Subject: [Slackbuilds-users] Request for Miro 2.0
In-Reply-To: <415881.93651.qm@web24202.mail.ird.yahoo.com>
References: <415881.93651.qm@web24202.mail.ird.yahoo.com>
Message-ID: <Pine.NEB.4.64.0902121945080.27158@sdf.lonestar.org>


> I didn't find anything about requests for Slackbuilds in the FAQ, so I 
> simply ask here and hope, this is the right place to do.
> I would like to have a Slackbuild Miro 2.0, but I don't have any Phyton 
> expierience, and do absolutely not understand how it installs. Maybe 
> someone of the Slackbuild team or a contributor is also interested in 
> Miro 2.0 and has the required knowledge to do a Slackbuild, this would 
> be great.

I don't know whether there is such a thing but I'd like to see something 
like it. I was sitting down to write my first - ever SlackBuild last night 
and came away thinking the package I had in mind might not be the best for 
a first shot ... and now I don't know what to replace it with! If there 
was a 'wish list' I could look it over and pick something. :)

Just my 2 pfennigs.

+-----------------------------------------------------+
Glenn Becker - burningc at sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
+-----------------------------------------------------+

From banderols at gmail.com  Fri Feb 13 08:24:13 2009
From: banderols at gmail.com (Murat D. Kadirov)
Date: Fri, 13 Feb 2009 13:24:13 +0500
Subject: [Slackbuilds-users] Updates - 20090211
In-Reply-To: <a6f13f000902120745k17e9811cqb2e995ed71e6bae@mail.gmail.com>
References: <20090211164046.GA21575@slackbuilds.org>
	<a6f13f000902120745k17e9811cqb2e995ed71e6bae@mail.gmail.com>
Message-ID: <20090213082413.GA3827@darkstar>

09:45 Thu 12 Feb, alkos333 wrote:
> 2009/2/11 Robby Workman <rworkman at slackbuilds.org>:
> > misc/kvm: Updated for version 83.  Thanks to Murat D. Kadirov.  --rworkman
> 
> Still getting the error when it gets to the mv command for the usr/man

tetex is installed?

-- 
Murat D. Kadirov
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090213/12e1ec3e/attachment-0001.sig>

From me at alkos333.net  Fri Feb 13 14:25:14 2009
From: me at alkos333.net (alkos333)
Date: Fri, 13 Feb 2009 08:25:14 -0600
Subject: [Slackbuilds-users] Updates - 20090211
In-Reply-To: <20090213082413.GA3827@darkstar>
References: <20090211164046.GA21575@slackbuilds.org>
	<a6f13f000902120745k17e9811cqb2e995ed71e6bae@mail.gmail.com>
	<20090213082413.GA3827@darkstar>
Message-ID: <a6f13f000902130625v4aeb4729m9f3f4b4b1b5eb436@mail.gmail.com>

On Fri, Feb 13, 2009 at 2:24 AM, Murat D. Kadirov <banderols at gmail.com> wrote:
> tetex is installed?

Nope, that was the problem.  Thank you!


-- 

Sent from: DeKalb Illinois United States.
Jay London  - "My father would take me to the playground, and put me
on mood swings."

From alan at lizella.net  Fri Feb 13 14:48:41 2009
From: alan at lizella.net (Alan Hicks)
Date: Fri, 13 Feb 2009 09:48:41 -0500
Subject: [Slackbuilds-users] Moving sbopkg to /usr/sbin and require root
In-Reply-To: <4992EB43.2030701@skmail.ikp.physik.tu-darmstadt.de>
References: <20090211011300.GA13725@localhost>
	<4992AAD3.5070202@skmail.ikp.physik.tu-darmstadt.de>
	<37086.212.48.3.167.1234349582.squirrel@webmail.slackware.it>
	<4992EB43.2030701@skmail.ikp.physik.tu-darmstadt.de>
Message-ID: <20090213094841.3252948e@raven.lizella.net>

On Wed, 11 Feb 2009 16:14:11 +0100
Serban Udrea <serban.udrea at skmail.ikp.physik.tu-darmstadt.de> wrote:

> >> At the moment I use
> >>
> >> chown -R $UID:$GROUPS .
> 
> > It's wrong, since the standard is to have executables owned as
> > root:root.
> 
> Not necessarily wrong, if you run the script as root you get the
> right ownership. Moreover "chown root:root" can be applied in the
> post-install script to what got installed, it's not necessary to have
> it in the SlackBuild.

Generally speaking, chown/chmod statements in the doinst.sh script are
begging for trouble and should almost never be done. Any large package
could have thousands, even tens of thousands of these files, and you'd
either have to wildcard match them, or list them individually. Then we
get to permissions problems on directories.  Imagine some one doing
this.

chown -R /usr root:root
chmod -R 755 /usr

Instant broken box.

There's one reason we don't accept things like that as "solutions", but
there are others as well.

-- 
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090213/5039e0ce/attachment.asc>

From joao.eel at gmail.com  Fri Feb 13 23:17:58 2009
From: joao.eel at gmail.com (=?ISO-8859-1?Q?Jo=E3o_Felipe_Santos?=)
Date: Fri, 13 Feb 2009 21:17:58 -0200
Subject: [Slackbuilds-users] Neverball URL and download location changed
Message-ID: <ecb28420902131517i42a26c86u56a29b3658ea772d@mail.gmail.com>

Hello,

I tried to run the Neverball SlackBuild but the download fails. I
googled and found that the new homepage for this project is
http://www.neverball.org and the download location is
http://www.neverball.org/neverball-1.5.0.tar.gz. md5sum here is
c170b502e2c5507846e946cdddd8a0ad. Some changes to the SlackBuild will
be necessary for it to work - the patch included does not work anymore
and the icons were moved to the dist/ directory. I can try to fix my
script and submit it if the maintainer does not have the time to fix
his one :)

-- Jo?o

From melmothx at gmail.com  Sun Feb 15 12:16:11 2009
From: melmothx at gmail.com (Marco Pessotto)
Date: Sun, 15 Feb 2009 13:16:11 +0100
Subject: [Slackbuilds-users] rxvt-unicode: TERMINFO entry installed in /
Message-ID: <87k57rj3p0.fsf@gmail.com>


Hi all. 

The rxvt-unicode Slackbuild install the TERMINFO entry in the / and not
in $PKG. This issue is not a problem if the package is installed in the
same machine, but *is* an issue if the package are reused or
redistributed or if the package generation is made by a regular user:

Solution:

make
mkdir -p $PKG/usr/share/terminfo
TERMINFO=$PKG/usr/share/terminfo make install DESTDIR=$PKG

And seems to works. (thanks to Corrado Franco)

Bests

Marco Pessotto


From xgizzmo at slackbuilds.org  Mon Feb 16 00:36:26 2009
From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org)
Date: Sun, 15 Feb 2009 19:36:26 -0500
Subject: [Slackbuilds-users] Updates - 20090215
Message-ID: <200902151936.27027.xgizzmo@slackbuilds.org>

Sun Feb 15 22:47:54 UTC 2009
academic/genius: Added - genius is a super cool math computation program
  similar to matlab and maple.  Thanks to Vincent Batts.  --dsomero
academic/gwyddion: Updated for version 2.13.
  Thanks to Daniil Bratashov.  --dsomero
audio/aacgain: Updated for version 1.8.  Thanks to Heinz Wiesinger.  --dsomero
audio/faac: Updated for version 1.28.  Thanks to Nille Akerstrom.  --rworkman
audio/faad2: Updated for version 2.7.  Thanks to Nille Akerstrom.  --rworkman
audio/gmusicbrowser: Updated for version 1.0.1.
  Thanks to Michael Wagner.  --dsomero
audio/jack-audio-connection-kit: Updated for version 0.116.2.
  Thanks to Heinz Wiesinger.  --dsomero
audio/mpd: Updated for version 0.14.2.  Thanks to Andrew Brouwers.  --dsomero
desktop/awesome: Updated for version 2.3.5.
  Thanks to Chess Griffin.  --dsomero
development/Quarter: Updated for version 1.0.0. 
  Thanks to Aleksandar Samardzic. --Michiel
development/gputils: Added - gputils is a collection of tools for the
  Microchip (TM) PIC microcontrollers.  Thanks to "GPLeo".  --dsomero
development/piklab: Added - piklab is an integrated development environment
  for applications based on PIC and dsPIC microcontrollers.
  Thanks to "GPLeo".  --dsomero
development/python3: Updated for version 3.0.1.
  Thanks to Audrius Kazukauskas.  --dsomero
games/prboom: Updated for version 2.5.0.
  Thanks to Manuel Mantilla.  --dsomero
games/transfusion: Added - transfusion is a port of the game Blood to the
  DarkPlaces Quake engine.  Thanks to B. Watson.  --dsomero
graphics/Opcion: Added - Opcion is a font viewer app written in java.
  Thanks to Robby Workman.  --dsomero
graphics/dcraw: Updated for version 8.91.
  Thanks to Nishant Limbachia. --Michiel
graphics/svp: Added - svp is a ghostscript front end for svgalib.
  Thanks to Luis Henrique.  --dsomero
libraries/c-ares: Added - c-ares is a C library that performs DNS requests and
  name resolves asynchronously.  Thanks to Larry Hajali.  --dsomero
libraries/libofx: Updated for version 0.9.1.
  Thanks to Erik Hanson.  --dsomero
libraries/libsamplerate: Miscellaneous build script cleanups.
  Thanks to Paul Wisehart.  --rworkman
libraries/libsndfile: Updated for version 1.0.18.  
  Thanks to Paul Wisehart.  --rworkman
misc/lxappearance: Added - lxappearance is the standard theme switcher of LXDE.
  Thanks to "majk".  --dsomero
multimedia/dvgrab: Updated for version 3.3.  
  Thanks to Murat D. Kadirov.  --rworkman
multimedia/gpodder: Updated for version 0.14.1.
  Thanks to Chess Griffin.  --dsomero
network/ddclient: Updated for version 3.8.0.  Thanks to Iskar Enev.  --dsomero
network/iw: Updated for version 0.9.9.  Thanks to nullboy.  --rworkman
network/lostirc: Added - lostirc is a simple yet very useful IRC client.
  Thanks to "majk".  --dsomero
network/netkit-filesystem: Updated for version F5.0.
  Thanks to Murat D. Kadirov.  --rworkman
network/netkit-kernel: Updated for version K2.6.
  Thanks to Murat D. Kadirov.  --rworkman
network/proxychains: Added - proxychains is a tool that forces any TCP
  connection made by any given application to follow through proxy like TOR or
  any other SOCKS4, SOCKS5 or HTTP(S) proxy.  Thanks to "GPLeo".  --dsomero
network/sylpheed: Added - Sylpheed is a simple, lightweight but featureful,
  and easy-to-use e-mail client.  Thanks to "GPLeo".  --dsomero
office/latex2html: Added - latex2html is a convertor written in Perl that
  converts LATEX documents to HTML.  Thanks to Luis Henrique.  --dsomero
system/chmsee: Updated for version 1.0.3.  Thanks to "Devdatta".  --dsomero
system/curlftpfs: Updated for version 0.9.2
  Thanks to Heinz Wiesinger. --Michiel
system/dc3dd: Updated for version 6.12.2.  Thanks to Barry Grundy.  --dsomero
system/gparted Updated for version 0.4.3.  Thanks to Erik Hanson.  --dsomero
system/lxtask: Added - lxtask is a lightweight and desktop-independent task
  manager derived from xfce4-taskmanager.  Thanks to "majk".  --dsomero
system/lzip: Updated for version 1.4.  Thanks to Barry Grundy.  --dsomero
system/vhba-module: Updated for version 1.2.1.
  Thanks to  Niklas "Nille" ?kerstr?m.  --dsomero

From pc_warner at yahoo.com  Mon Feb 16 09:02:00 2009
From: pc_warner at yahoo.com (Phillip Warner)
Date: Mon, 16 Feb 2009 01:02:00 -0800 (PST)
Subject: [Slackbuilds-users] rxvt-unicode: TERMINFO entry installed in /
In-Reply-To: <87k57rj3p0.fsf@gmail.com>
Message-ID: <617855.27010.qm@web57704.mail.re3.yahoo.com>

--- On Sun, 2/15/09, Marco Pessotto <melmothx at gmail.com> wrote:

> From: Marco Pessotto <melmothx at gmail.com>
> Subject: [Slackbuilds-users] rxvt-unicode: TERMINFO entry installed in /
> To: slackbuilds-users at slackbuilds.org
> Date: Sunday, February 15, 2009, 4:16 AM
> Hi all. 
> 
> The rxvt-unicode Slackbuild install the TERMINFO entry in
> the / and not
> in $PKG. This issue is not a problem if the package is
> installed in the
> same machine, but *is* an issue if the package are reused
> or
> redistributed or if the package generation is made by a
> regular user:
> 
> Solution:
> 
> make
> mkdir -p $PKG/usr/share/terminfo
> TERMINFO=$PKG/usr/share/terminfo make install DESTDIR=$PKG
> 
> And seems to works. (thanks to Corrado Franco)
> 
> Bests
> 
> Marco Pessotto

I have verified the problem, but not the solution.

--phillip


      

From joao.eel at gmail.com  Tue Feb 17 00:47:11 2009
From: joao.eel at gmail.com (=?ISO-8859-1?Q?Jo=E3o_Felipe_Santos?=)
Date: Mon, 16 Feb 2009 21:47:11 -0300
Subject: [Slackbuilds-users] Trouble with mpd after faad2 update
Message-ID: <ecb28420902161647m5690a15fue886db15eacba787@mail.gmail.com>

Hello,

I've just updated faad2 and mpd through the new versions from
SlackBuilds.org and now when I run mpd I get this:

    mpd: error while loading shared libraries: libfaad.so.0: cannot
open shared object file: No such file or directory

A symlink from libfaad.so.2.0.0 to libfaad.so.0 fixes it, but it would
be nicer if mpd could be configured to point to the right file. Does
anybody know a better fix to this issue?

-- Jo?o

From erik at slackbuilds.org  Tue Feb 17 01:50:28 2009
From: erik at slackbuilds.org (Erik Hanson)
Date: Mon, 16 Feb 2009 19:50:28 -0600
Subject: [Slackbuilds-users] Trouble with mpd after faad2 update
In-Reply-To: <ecb28420902161647m5690a15fue886db15eacba787@mail.gmail.com>
References: <ecb28420902161647m5690a15fue886db15eacba787@mail.gmail.com>
Message-ID: <20090216195028.66db580c@shaggy.scooby>

On Feb 16, 2009, at  9:47 PM, Jo?o Felipe Santos wrote:

> Hello,

Hi, 

> I've just updated faad2 and mpd through the new versions from
> SlackBuilds.org and now when I run mpd I get this:
> 
>     mpd: error while loading shared libraries: libfaad.so.0: cannot
> open shared object file: No such file or directory

I ran into the same problem, you need to recompile ffmpeg. You can see
the error in the output of mpd's configure.

-- 
Erik Hanson
http://slackbuilds.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090216/121af0cc/attachment.asc>

From joao.eel at gmail.com  Tue Feb 17 02:10:26 2009
From: joao.eel at gmail.com (=?ISO-8859-1?Q?Jo=E3o_Felipe_Santos?=)
Date: Mon, 16 Feb 2009 23:10:26 -0300
Subject: [Slackbuilds-users] Trouble with mpd after faad2 update
In-Reply-To: <20090216195028.66db580c@shaggy.scooby>
References: <ecb28420902161647m5690a15fue886db15eacba787@mail.gmail.com>
	<20090216195028.66db580c@shaggy.scooby>
Message-ID: <ecb28420902161810sd8d206dg76cb665343eca90c@mail.gmail.com>

On Mon, Feb 16, 2009 at 10:50 PM, Erik Hanson <erik at slackbuilds.org> wrote:
> On Feb 16, 2009, at  9:47 PM, Jo?o Felipe Santos wrote:
>
>
> Hi,
>
> I ran into the same problem, you need to recompile ffmpeg. You can see
> the error in the output of mpd's configure.
>
> --
> Erik Hanson

Hello Erik,

thanks for your reply. I had read the logfile but I think my brain's
log parser has a bug ;) Everything is working as expected now.

-- Jo?o

From xma at gnu.org  Wed Feb 18 21:25:05 2009
From: xma at gnu.org (Xavier Maillard)
Date: Wed, 18 Feb 2009 22:25:05 +0100
Subject: [Slackbuilds-users] emacs section ?
In-Reply-To: "adamsonj@email.unc.edu"'s message of Wed, 21 Jan 2009 11:03:33
	-0500
Message-ID: <200902182125.n1ILP5Np002788@zogzog.maillard.mobi>

[catching up my mail]

       > Probably they should go to the relevant category if it's clear --

   E.g. AUCTeX  is in the "Office" section.  I will say that I didn't look
   there and overlooked this SlackBuild ;)

   I also have one for bbdb and a few others --- I will submit them.

What do you have in your list ? :)

	Xavier
-- 
http://www.gnu.org
http://www.april.org
http://www.lolica.org

From xma at gnu.org  Wed Feb 18 21:25:07 2009
From: xma at gnu.org (Xavier Maillard)
Date: Wed, 18 Feb 2009 22:25:07 +0100
Subject: [Slackbuilds-users] Updates - 20090215
In-Reply-To: "xgizzmo@slackbuilds.org"'s message of Sun, 15 Feb 2009 19:36:26
	-0500
Message-ID: <200902182125.n1ILP7Sh002797@zogzog.maillard.mobi>

Hi,

   audio/gmusicbrowser: Updated for version 1.0.1.
     Thanks to Michael Wagner.  --dsomero

I am pretty sure Michael Wagner did not push this update but *I*
;) I did not change the MAINTAINER entry in the info file (is it
bad ?). If anything breaks, it is not Michael's fault but mine.
Sorry to bother.

	Xavier
-- 
http://www.gnu.org
http://www.april.org
http://www.lolica.org

From rworkman at slackbuilds.org  Wed Feb 18 21:30:59 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 18 Feb 2009 15:30:59 -0600
Subject: [Slackbuilds-users] Updates - 20090215
In-Reply-To: <200902182125.n1ILP7Sh002797@zogzog.maillard.mobi>
References: <200902182125.n1ILP7Sh002797@zogzog.maillard.mobi>
Message-ID: <20090218153059.791f3373@liberty.rlwhome.lan>

On Wed, 18 Feb 2009 22:25:07 +0100
Xavier Maillard <xma at gnu.org> wrote:

> Hi,
> 
>    audio/gmusicbrowser: Updated for version 1.0.1.
>      Thanks to Michael Wagner.  --dsomero
> 
> I am pretty sure Michael Wagner did not push this update but *I*
> ;) I did not change the MAINTAINER entry in the info file (is it
> bad ?). If anything breaks, it is not Michael's fault but mine.
> Sorry to bother.


Aha!  Sorry about that, but there's no way for us to know that unless a
note is in the "Comments" section.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090218/ee294dc9/attachment.asc>

From fullofdaylight at no-log.org  Thu Feb 19 22:38:51 2009
From: fullofdaylight at no-log.org (fullofdaylight at no-log.org)
Date: Thu, 19 Feb 2009 23:38:51 +0100 (CET)
Subject: [Slackbuilds-users] Use for a package repository?
Message-ID: <39617.AVAGD19QC3s=.1235083131.squirrel@webmail.no-log.org>

Hello,

This is slightly off-topic since it doesn't deal with SlackBuilds, but I'd
like to know your opinion on a SBo package repository (read "third
party").

- Given SBo is the top quality source for additional software under
Slackware,
- given most of the proposed software is under an OSS license,
- given users will customize SlackBuilds only when needed and otherwise
use the default settings,
- given compilation can take a while (Battle for Wesnoth anyone?),
would it be a good thing if someone creates a repository containing
packages (properly) compiled from SBo SlackBuilds with default settings?

Some programs couldn't be redistributed as packages due to licensing
issues, and some would need the user to choose compilation options, but
the vast majority would work.

Are there issues that would make it a bad idea? Or in the contrary would
it be a useful, convenient way to get quality packages?

Thanks!

From pprkut at liwjatan.at  Thu Feb 19 23:34:50 2009
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Fri, 20 Feb 2009 00:34:50 +0100
Subject: [Slackbuilds-users] Use for a package repository?
In-Reply-To: <39617.AVAGD19QC3s=.1235083131.squirrel@webmail.no-log.org>
References: <39617.AVAGD19QC3s=.1235083131.squirrel@webmail.no-log.org>
Message-ID: <200902200034.53308.pprkut@liwjatan.at>

fullofdaylight at no-log.org wrote:
> Hello,
>
> This is slightly off-topic since it doesn't deal with SlackBuilds, but I'd
> like to know your opinion on a SBo package repository (read "third
> party").

Ok, so my opinion: just don't.

Reasons:

> - Given SBo is the top quality source for additional software under
> Slackware,

Agreed. So any other repository, and especially package repository would be 
not as "top". So why bother if there's something better....

>[...]
> - given compilation can take a while (Battle for Wesnoth anyone?),
> would it be a good thing if someone creates a repository containing
> packages (properly) compiled from SBo SlackBuilds with default settings?

"properly" has a very loose definition. When is a package "properly" compiled? 
When it doesn't include unnecessary stuff? What exactly is "unnecessary"?
You see, some scripts have options to be chosen to extend it or cut it down 
(as you said elsewhere), but some don't. And you still can make them not use 
stuff by just not having the required deps installed.
For me, "properly" means "as I want it to be" combined with "it should work", 
which... doesn't always work out......but you hopefully get the point.

> Are there issues that would make it a bad idea? Or in the contrary would
> it be a useful, convenient way to get quality packages?

In the end I think this is about compiling vs. not compiling. Is this really 
an issue? It's not like we're gentoo....

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090220/3a418bda/attachment.sig>

From nille.kungen at gmail.com  Fri Feb 20 01:50:55 2009
From: nille.kungen at gmail.com (=?ISO-8859-1?Q?Niklas_=27Nille=27_=C5kerstr=F6m?=)
Date: Fri, 20 Feb 2009 02:50:55 +0100
Subject: [Slackbuilds-users] Use for a package repository?
In-Reply-To: <39617.AVAGD19QC3s=.1235083131.squirrel@webmail.no-log.org>
References: <39617.AVAGD19QC3s=.1235083131.squirrel@webmail.no-log.org>
Message-ID: <499E0C7F.2000609@gmail.com>

fullofdaylight at no-log.org skrev:
> - Given SBo is the top quality source for additional software under
> Slackware,
> - given most of the proposed software is under an OSS license,
> - given users will customize SlackBuilds only when needed and otherwise
> use the default settings,
>   
I think it's because slackbuild only ship slackbuilds that makes it so good and it's so easy to customize and make packages that suits your needs

> - given compilation can take a while (Battle for Wesnoth anyone?),
> would it be a good thing if someone creates a repository containing
> packages (properly) compiled from SBo SlackBuilds with default settings?
>   
You are free to do what ever you want but i can't see how third party packages would be needed.
The good thing would be that the *.SlackBuild would be included in the docs dir.

How could anyone know how an properly compiled package that suits your needs or system would look like?
And is it needed? because some maintainers already have there own websites where they do have packages.


/Nille

From mikedawg at gmail.com  Fri Feb 20 04:01:40 2009
From: mikedawg at gmail.com (Mike Harris)
Date: Thu, 19 Feb 2009 20:01:40 -0800
Subject: [Slackbuilds-users] Request: Cyrus-IMAPd
Message-ID: <5268af340902192001o15e23f5o638a9675db3db28d@mail.gmail.com>

Hi guys,

First I want to tell you how great your site and repository is.
Unfortunately I haven't heard of it until recently, I'm used to the
"old-school" compiling.

After chatting on some other forums, I chatted with an administrator,
from this site, and figured I'd give it a shot.  Anyways, I'm looking
for a slackbuild of cyrus-imapd.  I've been having such a tough time
building it on my system, I turned to look for a slackbuild.  I know
the user I spoke with was running the cyrus-imapd server, and wanted
to see if I could convince someone to throw a slackbuild together.

Anyways, keep up the good work, and now that I've found this site,
I'll contribute some code of my own that I have built for my previous
slackware setups.

Thanks

-- 
Mike

From eha at sox.homeip.net  Fri Feb 20 08:42:58 2009
From: eha at sox.homeip.net (Eric Hameleers)
Date: Fri, 20 Feb 2009 09:42:58 +0100 (CET)
Subject: [Slackbuilds-users] Use for a package repository?
In-Reply-To: <39617.AVAGD19QC3s=.1235083131.squirrel@webmail.no-log.org>
References: <39617.AVAGD19QC3s=.1235083131.squirrel@webmail.no-log.org>
Message-ID: <Pine.LNX.4.61.0902200928210.26026@door.barrier.lan>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 19 Feb 2009 fullofdaylight at no-log.org wrote:

> would it be a good thing if someone creates a repository containing
> packages (properly) compiled from SBo SlackBuilds with default settings?

I am not going to tell you whether or not you should create such a 
repository. I know there are several package repositories that are 
basically using the SlackBuild scripts we provide at SBo to create the 
packages.

However, there is a good reason you never see the phrase "based on SBo 
scripts" on these repositories' home pages. The slackbuilds.org team does 
not want to be affiliated to any 3rd package repository.

The reason? We provide QA-tested SlackBuild scripts submitted by a large 
community of Slackware enthousiasts. The admin team tests these scripts.

By creating a GPG signature file (the .asc file) for an approved tarball 
we say "this script works as advertised, and running it as root will not 
harm your computer". Being able to verify the tarball's GPG signature 
means that you can be sure the script you are going to use is _exactly_ 
the one that we tested.

Now, with pre-built packages based on SBo scripts you are _never_ going to 
be certain that the SlackBuild used to produce the package was identical 
to the one that got a stamp of approval from the SBo admins. This means, 
that we do not want to see someone advertising that he is providing 
packages based on slackbuilds.org scripts. We do not have control over the 
end product, so we do not assume any responsibility for it.

Eric

- -- 
Eric Hameleers
Email: alien at slackware.com
Jabber: alien at jabber.xs4all.nl
Gpg fingerprint: F2CE 1B92 EE1F 2C0C E97E  581E 5E56 AAAF A75C BDA0
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQFJnm0XXlaqr6dcvaARAsMrAKCJxxhDQwS5n3brqA4acJj3Oa6M2gCgi/FI
/5+7o7a2XqHUGF2Qn2hm06g=
=YfXl
-----END PGP SIGNATURE-----

From yallaone at gmail.com  Fri Feb 20 13:40:11 2009
From: yallaone at gmail.com (Halim Issa)
Date: Fri, 20 Feb 2009 14:40:11 +0100
Subject: [Slackbuilds-users] Put a security warning in Adobe Reader
	SlackBuild?
Message-ID: <200902201440.12184.yallaone@gmail.com>

Hi,

Seems like there's a critical vulnerability identified in Adobe Reader, also 
applicable to Linux.. Since Adobe apparently doesn't have any plans to fix this 
for another three weeks, would it be an idea to put a warning in the acroread 
SlackBuild in the meantime?

http://www.adobe.com/support/security/advisories/apsa09-01.html

Which also brings up a related question, if there perhaps is a need for a 
slackbuilds-security mailing list to warn against possible vulnerabilities in 
a SlackBuild. It's a more-than-dual-egged-sword challenge, since keeping that 
up-to-date would be a nightmare and warning on some programs might give false 
sense of security of others... 
Still perhaps worth a debate?

Just my $.02

From pprkut at liwjatan.at  Fri Feb 20 13:54:16 2009
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Fri, 20 Feb 2009 14:54:16 +0100
Subject: [Slackbuilds-users] Put a security warning in Adobe Reader
	SlackBuild?
In-Reply-To: <200902201440.12184.yallaone@gmail.com>
References: <200902201440.12184.yallaone@gmail.com>
Message-ID: <200902201454.24164.pprkut@liwjatan.at>

Halim Issa wrote:
> Hi,
>
> Seems like there's a critical vulnerability identified in Adobe Reader,
> also applicable to Linux.. Since Adobe apparently doesn't have any plans to
> fix this for another three weeks, would it be an idea to put a warning in
> the acroread SlackBuild in the meantime?
>
> http://www.adobe.com/support/security/advisories/apsa09-01.html

Seems reasonable, although I would prefer to have that information in the 
README. Can an admin take care of this please?

I will update the script as soon as a new version is available.

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090220/c174fcf5/attachment.sig>

From fullofdaylight at no-log.org  Fri Feb 20 14:09:10 2009
From: fullofdaylight at no-log.org (fullofdaylight at no-log.org)
Date: Fri, 20 Feb 2009 15:09:10 +0100 (CET)
Subject: [Slackbuilds-users] Use for a package repository?
In-Reply-To: <Pine.LNX.4.61.0902200928210.26026@door.barrier.lan>
References: <39617.AVAGD19QC3s=.1235083131.squirrel@webmail.no-log.org>
	<Pine.LNX.4.61.0902200928210.26026@door.barrier.lan>
Message-ID: <23724.B1cEDV8DXi0=.1235138950.squirrel@webmail.no-log.org>

Thank you all, and especially Eric, for your insightful comments. It makes
it clearer for me.

I agree that if I am to create such a repository it has not to be
affiliated with SBo (although I think SBo _has_ to be cited as the
SlackBuilds' source), and that one has to be well-informed one can't give
it the same level of trust.

The rationale behind my idea is that it is convenient to have only one
source for additional packages instead of cherry-picking between several
ones. Additionally I don't trust other packages/SlackBuild sources
(LinuxPackages, Slacky, any individual repository, etc) as much as I trust
SBo.

While there are SlackBuilds that need customization before being compiled,
there are numerous ones where simply executing the unmodified SlackBuild
is fine, and where the result doesn't heavily depends on which other
programs are already installed.

If I have time maybe I'll try to set up something, and see if people are
interested in the project or if they generally prefer to compile programs
themselves.

Cheers!


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thu, 19 Feb 2009 fullofdaylight at no-log.org wrote:
>
>> would it be a good thing if someone creates a repository containing
>> packages (properly) compiled from SBo SlackBuilds with default settings?
>
> I am not going to tell you whether or not you should create such a
> repository. I know there are several package repositories that are
> basically using the SlackBuild scripts we provide at SBo to create the
> packages.
>
> However, there is a good reason you never see the phrase "based on SBo
> scripts" on these repositories' home pages. The slackbuilds.org team does
> not want to be affiliated to any 3rd package repository.
>
> The reason? We provide QA-tested SlackBuild scripts submitted by a large
> community of Slackware enthousiasts. The admin team tests these scripts.
>
> By creating a GPG signature file (the .asc file) for an approved tarball
> we say "this script works as advertised, and running it as root will not
> harm your computer". Being able to verify the tarball's GPG signature
> means that you can be sure the script you are going to use is _exactly_
> the one that we tested.
>
> Now, with pre-built packages based on SBo scripts you are _never_ going to
> be certain that the SlackBuild used to produce the package was identical
> to the one that got a stamp of approval from the SBo admins. This means,
> that we do not want to see someone advertising that he is providing
> packages based on slackbuilds.org scripts. We do not have control over the
> end product, so we do not assume any responsibility for it.
>
> Eric
>
> - --
> Eric Hameleers
> Email: alien at slackware.com
> Jabber: alien at jabber.xs4all.nl
> Gpg fingerprint: F2CE 1B92 EE1F 2C0C E97E  581E 5E56 AAAF A75C BDA0
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> Comment: For info see http://quantumlab.net/pine_privacy_guard/
>
> iD8DBQFJnm0XXlaqr6dcvaARAsMrAKCJxxhDQwS5n3brqA4acJj3Oa6M2gCgi/FI
> /5+7o7a2XqHUGF2Qn2hm06g=
> =YfXl
> -----END PGP SIGNATURE-----
> _______________________________________________
> 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  Fri Feb 20 14:55:24 2009
From: pc_warner at yahoo.com (Phillip Warner)
Date: Fri, 20 Feb 2009 06:55:24 -0800 (PST)
Subject: [Slackbuilds-users] Put a security warning in Adobe Reader
	SlackBuild?
In-Reply-To: <200902201440.12184.yallaone@gmail.com>
Message-ID: <586537.25461.qm@web57707.mail.re3.yahoo.com>

--- On Fri, 2/20/09, Halim Issa <yallaone at gmail.com> wrote:

> Seems like there's a critical vulnerability identified
> in Adobe Reader, also 
> applicable to Linux.. Since Adobe apparently doesn't
> have any plans to fix this 
> for another three weeks, would it be an idea to put a
> warning in the acroread 
> SlackBuild in the meantime?
> 
> http://www.adobe.com/support/security/advisories/apsa09-01.html

>From what I understand disabling js in acroread will protect you from this for now.

> Which also brings up a related question, if there perhaps
> is a need for a 
> slackbuilds-security mailing list to warn against possible
> vulnerabilities in 
> a SlackBuild. It's a more-than-dual-egged-sword
> challenge, since keeping that 
> up-to-date would be a nightmare and warning on some
> programs might give false 
> sense of security of others... 
> Still perhaps worth a debate?
I like the idea, but for now I get all of that info from this list and the Changelog.  A simple grep for security in the Changelog usually shows all of the important updates.  If the admins don't mind the extra work though...

--phillip


      

From rworkman at slackbuilds.org  Fri Feb 20 16:02:23 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 20 Feb 2009 10:02:23 -0600
Subject: [Slackbuilds-users] rxvt-unicode: TERMINFO entry installed in /
In-Reply-To: <617855.27010.qm@web57704.mail.re3.yahoo.com>
References: <87k57rj3p0.fsf@gmail.com>
	<617855.27010.qm@web57704.mail.re3.yahoo.com>
Message-ID: <20090220100223.7a05dbfd@liberty.rlwhome.lan>

On Mon, 16 Feb 2009 01:02:00 -0800 (PST)
Phillip Warner <pc_warner at yahoo.com> wrote:

> --- On Sun, 2/15/09, Marco Pessotto <melmothx at gmail.com> wrote:
> > The rxvt-unicode Slackbuild install the TERMINFO entry in
> > the / and not
> > in $PKG. This issue is not a problem if the package is
> > installed in the
> > same machine, but *is* an issue if the package are reused
> > or
> > redistributed or if the package generation is made by a
> > regular user:
> > 
> > Solution:
> > 
> > make
> > mkdir -p $PKG/usr/share/terminfo
> > TERMINFO=$PKG/usr/share/terminfo make install DESTDIR=$PKG
> > 
> > And seems to works. (thanks to Corrado Franco)
> > 
> 
> I have verified the problem, but not the solution.


The terminfo file is getting installed from ./doc/Makefile via the
tic(1) command.   Based on tic(1), this does appear to be the correct
solution, so I'll get that fixed on this end and merged with the next
update.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090220/37cfaa40/attachment.asc>

From erik at slackbuilds.org  Fri Feb 20 18:19:15 2009
From: erik at slackbuilds.org (Erik Hanson)
Date: Fri, 20 Feb 2009 12:19:15 -0600
Subject: [Slackbuilds-users] Use for a package repository?
In-Reply-To: <23724.B1cEDV8DXi0=.1235138950.squirrel@webmail.no-log.org>
References: <39617.AVAGD19QC3s=.1235083131.squirrel@webmail.no-log.org>
	<Pine.LNX.4.61.0902200928210.26026@door.barrier.lan>
	<23724.B1cEDV8DXi0=.1235138950.squirrel@webmail.no-log.org>
Message-ID: <20090220121915.7c21e3c3@shaggy.scooby>

On Feb 20, 2009, at  3:09 PM, fullofdaylight at no-log.org wrote:

> I agree that if I am to create such a repository it has not to be
> affiliated with SBo (although I think SBo _has_ to be cited as the
> SlackBuilds' source), and that one has to be well-informed one can't give
> it the same level of trust.

We will not put our name behind this. It has come up in the past, we have
discussed it, and it will not happen.

> The rationale behind my idea is that it is convenient to have only one
> source for additional packages instead of cherry-picking between several
> ones. Additionally I don't trust other packages/SlackBuild sources
> (LinuxPackages, Slacky, any individual repository, etc) as much as I trust
> SBo.

These other repositories already exist. You can't take them away by making
an SBo repository. I don't think any of us admins would even want that. We
didn't set out to take away choice.

> While there are SlackBuilds that need customization before being compiled,
> there are numerous ones where simply executing the unmodified SlackBuild
> is fine, and where the result doesn't heavily depends on which other
> programs are already installed.

That's actually sort of the point, in an indirect way. People don't
necessarily run a stock 12.2 system (I sure as hell don't). While all we
can do is test against a full 12.2 install, the scripts can be used in
any number of situations. Packages, maybe not so much.

> If I have time maybe I'll try to set up something, and see if people are
> interested in the project or if they generally prefer to compile programs
> themselves.

While I don't doubt that some people would find a pre-compiled package
repository useful, I just don't want to be on the hook for support. And
that's basically why we have to draw a line.

-- 
Erik Hanson
http://slackbuilds.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090220/12dfb5e1/attachment.asc>

From rworkman at slackbuilds.org  Fri Feb 20 21:12:14 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Fri, 20 Feb 2009 21:12:14 +0000
Subject: [Slackbuilds-users] Updates - 20090220
Message-ID: <20090220211214.GA27526@slackbuilds.org>

Fri Feb 20 21:04:19 UTC 2009
development/boost: Updated for version 1.38.0. 
  Thanks to Heinz Wiesinger. --michiel
development/scons: Updated for version 1.2.0
  Thanks to Kyle Guinn. --michiel
development/saxonb: Added - Saxonb-B is the open source version of Saxonica's 
  Saxon-SA schema aware XSLT processor.  Thanks to Robert Allen.  --rworkman
development/xalan-j: Added - Xalan-J is a java XSLT 1.0 processor.
  Thanks to Robert Allen.  --rworkman
games/desmume: Updated for version 0.9.1 and added some notes to the README
  about compile problems with the nvidia driver installed.
  Thanks to Larry Hajali and Heinz Wiesinger.  --rworkman
libraries/fftw: Updated for version 3.2.1 along with some script cleanup.
  Thanks to Kyle Guinn.  --rworkman
libraries/libarchive: Updated for version 2.6.1.
  Thanks to Heinz Wiesinger. --michiel
libraries/libical: Updated for version 0.43.
  Thanks to Heinz Wiesinger. --michiel
libraries/libkate: Updated for version 0.30.
  Thanks to Nishant Limbachia. --michiel
libraries/mmpython: Added - MMPython is a Media Meta Data retrieval framework
  written in python. Thanks to Larry Hajali. --michiel
libraries/mysql++: Added - MySQL++ is a C++ wrapper for the MySQL C API.
  Thanks to Lorenzo Stramaccia. --michiel
libraries/qwt: Added - Qwt is a GUI Components and utility for programs with 
  technical background. Thanks to Zordrak. --rworkman,michiel
misc/pinfo: Added - Pinfo is an info file viewer.
  Thanks to Arun Prasannan.  --rworkman
network/mz: Updated for version 0.34.6
  Thanks to Heinz Wiesinger. --michiel
network/tork: Updated for version 0.31.
  Thanks to Heinz Wiesinger. --michiel
network/udpcast: Updated for version 20081213.
  Thanks to Heinz Wiesinger. --michiel
system/fsarchiver: Updated for version 0.4.1.
  Thanks to Nishant Limbachia. --michiel
system/rxvt-unicode: Fixed a bug with installation of terminfo data.
  Thanks to Corrado Franco and Marco Pessotto.  --rworkman
system/virtualbox-{kernel,ose}{,-addons}: Updated for version 2.1.4.  
  Thanks to Heinz Wiesinger.  --rworkman


From cnguyenminhtan at free.fr  Sat Feb 21 20:36:00 2009
From: cnguyenminhtan at free.fr (cnguyenminhtan at free.fr)
Date: Sat, 21 Feb 2009 21:36:00 +0100 (CET)
Subject: [Slackbuilds-users] Use for a package repository?
In-Reply-To: <Pine.LNX.4.61.0902200928210.26026@door.barrier.lan>
Message-ID: <1055821995.2042191235248560515.JavaMail.root@zimbra10-e2.priv.proxad.net>

Hello Eric,

You said:

***************
This means, that we do not want to see someone advertising that he is providing 
packages based on slackbuilds.org scripts.
**************

Oops, does it mean that I should modify my home page where I put my extra packages:

http://cnguyenminhtan.free.fr/

KR,

Christophe

----- Mail Original -----
De: "Eric Hameleers" <eha at sox.homeip.net>
?: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
Envoy?: Vendredi 20 F?vrier 2009 09:42:58 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: [Slackbuilds-users] Use for a package repository?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 19 Feb 2009 fullofdaylight at no-log.org wrote:

> would it be a good thing if someone creates a repository containing
> packages (properly) compiled from SBo SlackBuilds with default settings?

I am not going to tell you whether or not you should create such a 
repository. I know there are several package repositories that are 
basically using the SlackBuild scripts we provide at SBo to create the 
packages.

However, there is a good reason you never see the phrase "based on SBo 
scripts" on these repositories' home pages. The slackbuilds.org team does 
not want to be affiliated to any 3rd package repository.

The reason? We provide QA-tested SlackBuild scripts submitted by a large 
community of Slackware enthousiasts. The admin team tests these scripts.

By creating a GPG signature file (the .asc file) for an approved tarball 
we say "this script works as advertised, and running it as root will not 
harm your computer". Being able to verify the tarball's GPG signature 
means that you can be sure the script you are going to use is _exactly_ 
the one that we tested.

Now, with pre-built packages based on SBo scripts you are _never_ going to 
be certain that the SlackBuild used to produce the package was identical 
to the one that got a stamp of approval from the SBo admins. This means, 
that we do not want to see someone advertising that he is providing 
packages based on slackbuilds.org scripts. We do not have control over the 
end product, so we do not assume any responsibility for it.

Eric

- -- 
Eric Hameleers
Email: alien at slackware.com
Jabber: alien at jabber.xs4all.nl
Gpg fingerprint: F2CE 1B92 EE1F 2C0C E97E  581E 5E56 AAAF A75C BDA0
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQFJnm0XXlaqr6dcvaARAsMrAKCJxxhDQwS5n3brqA4acJj3Oa6M2gCgi/FI
/5+7o7a2XqHUGF2Qn2hm06g=
=YfXl
-----END PGP SIGNATURE-----
_______________________________________________
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 xma at gnu.org  Sun Feb 22 09:25:03 2009
From: xma at gnu.org (Xavier Maillard)
Date: Sun, 22 Feb 2009 10:25:03 +0100
Subject: [Slackbuilds-users] Updates - 20090215
In-Reply-To: message from Robby Workman on Wed, 18 Feb 2009 15:30:59 -0600
Message-ID: <200902220925.n1M9P3KY021280@zogzog.maillard.mobi>

Hi,

   >    audio/gmusicbrowser: Updated for version 1.0.1.
   >      Thanks to Michael Wagner.  --dsomero
   >=20
   > I am pretty sure Michael Wagner did not push this update but *I*
   > ;) I did not change the MAINTAINER entry in the info file (is it
   > bad ?). If anything breaks, it is not Michael's fault but mine.
   > Sorry to bother.


   Aha!  Sorry about that, but there's no way for us to know that unless a
   note is in the "Comments" section.

Not a problem, just a warning to be sure Michael won't be
injuried if something wrong happens :)

	Xavier
-- 
http://www.gnu.org
http://www.april.org
http://www.lolica.org

From rworkman at slackbuilds.org  Sun Feb 22 19:29:24 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 22 Feb 2009 19:29:24 +0000
Subject: [Slackbuilds-users] Updates - 20090222
Message-ID: <20090222192924.GA11805@slackbuilds.org>

Sun Feb 22 19:15:20 UTC 2009
audio/ardour: Updated for version 2.7.1.
  Thanks to Heinz Wiesinger.  --rworkman
audio/lmms: Added - LMMS is a free cross-platform alternative to commercial 
  programs like FL Studio (r) which allow you to produce music with your 
  computer.  Thanks to "hackedhead"  --rworkman
audio/rosegarden: Updated for version 1.7.3.
  Thanks to Heinz Wiesinger.  --rworkman
games/spring: Updated for version 0.78.2.1.
  Thanks to Erik Hanson.  --rworkman
games/springlobby: Updated for version 0.0.1.10420.
  Thanks to Erik Hanson.  --rworkman
graphics/tesseract: Edited to reflect changes to the language packs.
  Thanks to Pierre Cazenave.  --rworkman
libraries/slv2: Updated for version 0.6.2.
  Thanks to Heinz Wiesinger.  --rworkman
multimedia/dvdrip: Added - dvd::rip is a full featured DVD copy program 
  written in Perl.  Thanks to Luis Henrique.  --rworkman
network/shorewall-{common,perl,shell}: Updated for version 4.2.6.
  Thanks to Gregory J. L. Tourte.  --rworkman
network/shorewall6: Added - this package adds ipv6 support to shorewall.
  Note that neither the submitter nor the approver :) has access to ipv6 for
  testing, so success/failure reports are encouraged (especially success).
  Thanks to Gregory J. L. Tourte.  --rworkman
system/splix: Updated for version 2.0.0.  Thanks to Iskar Enev.  --rworkman


From adamsonj at email.unc.edu  Mon Feb 23 15:54:25 2009
From: adamsonj at email.unc.edu (Joel J. Adamson <adamsonj@email.unc.edu>)
Date: Mon, 23 Feb 2009 10:54:25 -0500
Subject: [Slackbuilds-users] Emacs Snapshot Demand?
In-Reply-To: <mailman.11.1235303820.3297.slackbuilds-users@slackbuilds.org>
References: <mailman.11.1235303820.3297.slackbuilds-users@slackbuilds.org>
Message-ID: <21258.1235404465@email.unc.edu>

Dear SlackBuild Users,

I have a SlackBuild that builds GNU Emacs from CVS; I could quickly
conform it to SlackBuild.org standards.  Two questions are in order:

1. Is there demand for this?  I have discussed it with Xavier, so I know
there is at least one other person who might be interested.
2. Is this the kind of package that is appropriate for SlackBuilds.org?
It is a development version of an official package.

Let me know,
Joel

-- 
Joel J. Adamson	-- http://www.unc.edu/~adamsonj
University of North Carolina at Chapel Hill
CB #3280, Coker Hall
Chapel Hill, NC 27599-3280

From xgizzmo at slackbuilds.org  Mon Feb 23 23:06:49 2009
From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org)
Date: Mon, 23 Feb 2009 18:06:49 -0500
Subject: [Slackbuilds-users] Emacs Snapshot Demand?
In-Reply-To: <21258.1235404465@email.unc.edu>
References: <mailman.11.1235303820.3297.slackbuilds-users@slackbuilds.org>
	<21258.1235404465@email.unc.edu>
Message-ID: <200902231806.50160.xgizzmo@slackbuilds.org>

On Monday 23 February 2009 10:54:25 Joel J. Adamson <adamsonj at email.unc.edu> wrote:
> Dear SlackBuild Users,
> 
> I have a SlackBuild that builds GNU Emacs from CVS; I could quickly
> conform it to SlackBuild.org standards.  Two questions are in order:
> 
> 1. Is there demand for this?  I have discussed it with Xavier, so I know
> there is at least one other person who might be interested.
> 2. Is this the kind of package that is appropriate for SlackBuilds.org?
> It is a development version of an official package.
> 
> Let me know,
> Joel
> 

Slackbuilds.org normally will not accept SlackBuilds for official packages.

Quote from http://www.slackbuilds.org/guidelines

  "As a general rule, we do not accept SlackBuild scripts of software that is
   included as part of Slackware; however, exceptions may be made by the admin
   staff on a case-by-case basis.

--dsomero

From kmuerlen83 at gmail.com  Tue Feb 24 04:40:52 2009
From: kmuerlen83 at gmail.com (Kevin Muerlen)
Date: Mon, 23 Feb 2009 22:40:52 -0600
Subject: [Slackbuilds-users] VLC package?
Message-ID: <11d696810902232040v114f0671p4bd9892361cc1740@mail.gmail.com>

Hello list,

I don't see a VLC package on SBo...  Any chance of getting one?

Thanks,
Kevin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090223/a5434f2f/attachment.htm>

From didier.spaier at epsm.fr  Tue Feb 24 15:15:34 2009
From: didier.spaier at epsm.fr (Didier Spaier)
Date: Tue, 24 Feb 2009 16:15:34 +0100
Subject: [Slackbuilds-users] VLC package?
In-Reply-To: <11d696810902232040v114f0671p4bd9892361cc1740@mail.gmail.com>
References: <11d696810902232040v114f0671p4bd9892361cc1740@mail.gmail.com>
Message-ID: <200902241615.34834.didier.spaier@epsm.fr>

Le Tuesday 24 February 2009 05:40:52 Kevin Muerlen, vous avez ?crit?:
> Hello list,
> 
> I don't see a VLC package on SBo...  Any chance of getting one?
> 
> Thanks,
> Kevin
> 

Hello poster,

I do not know, but you can find packages & SlackBuilds in Alien Bob's repositories, see http://www.slackware.com/~alien/slackbuilds/

Cheers,

Didier

From joshuakwood at gmail.com  Tue Feb 24 16:48:50 2009
From: joshuakwood at gmail.com (JK Wood)
Date: Tue, 24 Feb 2009 10:48:50 -0600
Subject: [Slackbuilds-users] VLC package?
In-Reply-To: <200902241615.34834.didier.spaier@epsm.fr>
References: <11d696810902232040v114f0671p4bd9892361cc1740@mail.gmail.com>
	<200902241615.34834.didier.spaier@epsm.fr>
Message-ID: <6b6812630902240848k656b382ahc901ff7b08b6cc84@mail.gmail.com>

On Tue, Feb 24, 2009 at 9:15 AM, Didier Spaier <didier.spaier at epsm.fr>wrote:

> Le Tuesday 24 February 2009 05:40:52 Kevin Muerlen, vous avez ?crit :
> > Hello list,
> >
> > I don't see a VLC package on SBo...  Any chance of getting one?
> >
> > Thanks,
> > Kevin
> >
>
> Hello poster,
>
> I do not know, but you can find packages & SlackBuilds in Alien Bob's
> repositories, see http://www.slackware.com/~alien/slackbuilds/<http://www.slackware.com/%7Ealien/slackbuilds/>
>
> Cheers,
>
> Didier
> _______________________________________________
> 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/
>
>
VLC is an utter monster to build on Slackware, with a horrid dependency
chain and a rather low chance of success.  Which is why alienBOB's build is
so important.  That's one of the few things that I'd rather go to him for
than SBo.  Read his SlackBuild to find out why.

--JK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090224/db4f4a60/attachment.htm>

From mjjzf at syntaktisk.dk  Tue Feb 24 17:09:40 2009
From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=)
Date: Tue, 24 Feb 2009 18:09:40 +0100
Subject: [Slackbuilds-users] VLC package?
In-Reply-To: <6b6812630902240848k656b382ahc901ff7b08b6cc84@mail.gmail.com>
References: <11d696810902232040v114f0671p4bd9892361cc1740@mail.gmail.com>
	<200902241615.34834.didier.spaier@epsm.fr>
	<6b6812630902240848k656b382ahc901ff7b08b6cc84@mail.gmail.com>
Message-ID: <20090224180940.09ef4b81@espero.syntaktisk.dk>

On Tue, 24 Feb 2009 10:48:50 -0600
JK Wood <joshuakwood at gmail.com> wrote:

> VLC is an utter monster to build on Slackware, with a horrid
> dependency chain and a rather low chance of success.  Which is why
> alienBOB's build is so important.  That's one of the few things that
> I'd rather go to him for than SBo.  Read his SlackBuild to find out
> why.
> 
> --JK

Agree.
I use aBOB's build - works as it should.

Yours,
Morten
__
Morten Juhl-Johansen Z?lde-Fej?r
http://syntaktisk.dk * mjjzf at syntaktisk.dk

From rworkman at slackbuilds.org  Tue Feb 24 17:15:45 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 24 Feb 2009 11:15:45 -0600
Subject: [Slackbuilds-users] VLC package?
In-Reply-To: <6b6812630902240848k656b382ahc901ff7b08b6cc84@mail.gmail.com>
References: <11d696810902232040v114f0671p4bd9892361cc1740@mail.gmail.com>
	<200902241615.34834.didier.spaier@epsm.fr>
	<6b6812630902240848k656b382ahc901ff7b08b6cc84@mail.gmail.com>
Message-ID: <20090224111545.1e311bdb@liberty.rlwhome.lan>

On Tue, 24 Feb 2009 10:48:50 -0600
JK Wood <joshuakwood at gmail.com> wrote:

> On Tue, Feb 24, 2009 at 9:15 AM, Didier Spaier
> <didier.spaier at epsm.fr>wrote:
> 
> > Le Tuesday 24 February 2009 05:40:52 Kevin Muerlen, vous avez
> > ?crit :
> > > Hello list,
> > >
> > > I don't see a VLC package on SBo...  Any chance of getting one?
> > >
> > I do not know, but you can find packages & SlackBuilds in Alien
> > Bob's repositories, see
> > http://www.slackware.com/~alien/slackbuilds/<http://www.slackware.com/%7Ealien/slackbuilds/>
> >
> VLC is an utter monster to build on Slackware, with a horrid
> dependency chain and a rather low chance of success.  Which is why
> alienBOB's build is so important.  That's one of the few things that
> I'd rather go to him for than SBo.  Read his SlackBuild to find out
> why.


I'm just replying to CC the original poster, as he's not subscribed to
the list.  

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090224/1c82eadf/attachment.asc>

From nille.kungen at gmail.com  Tue Feb 24 23:08:25 2009
From: nille.kungen at gmail.com (=?UTF-8?B?TmlrbGFzICdOaWxsZScgw4VrZXJzdHLDtm0=?=)
Date: Wed, 25 Feb 2009 00:08:25 +0100
Subject: [Slackbuilds-users] VLC package?
In-Reply-To: <20090224111545.1e311bdb@liberty.rlwhome.lan>
References: <11d696810902232040v114f0671p4bd9892361cc1740@mail.gmail.com>	<200902241615.34834.didier.spaier@epsm.fr>	<6b6812630902240848k656b382ahc901ff7b08b6cc84@mail.gmail.com>
	<20090224111545.1e311bdb@liberty.rlwhome.lan>
Message-ID: <49A47DE9.7020001@gmail.com>


> On Tue, 24 Feb 2009 10:48:50 -0600
> JK Wood <joshuakwood at gmail.com> wrote:
>
>   
>> On Tue, Feb 24, 2009 at 9:15 AM, Didier Spaier
>> <didier.spaier at epsm.fr>wrote:
>>
>>     
>>> Le Tuesday 24 February 2009 05:40:52 Kevin Muerlen, vous avez
>>> ?crit :
>>>       
>>>> Hello list,
>>>>
>>>> I don't see a VLC package on SBo...  Any chance of getting one?
>>>>
>>>>         
>>> I do not know, but you can find packages & SlackBuilds in Alien
>>> Bob's repositories, see
>>> http://www.slackware.com/~alien/slackbuilds/<http://www.slackware.com/%7Ealien/slackbuilds/>
>>>
>>>       
>> VLC is an utter monster to build on Slackware, with a horrid
>> dependency chain and a rather low chance of success.  Which is why
>> alienBOB's build is so important.  That's one of the few things that
>> I'd rather go to him for than SBo.  Read his SlackBuild to find out
>> why.
>>     
I was *actually thinking of making one when i made my first slackbuilds thats why i maintain allot of **dependicies** for  multimedia.
But since the dependicies are only needed at build time then an SBo slackbuild ain't the best way to build vlc and thats why i didn't upload my vlc.SlackBuild
AlienBOB's SlackBuild is far the best vlc build script for slackware and i recommend it, and you can't make an slackbuild like that on SBo.
So as i see it there is not need for an build on SBo since it can't be as good as AlienBOB's.

/Nille
//*//

*
*

From xma at gnu.org  Tue Feb 24 23:25:03 2009
From: xma at gnu.org (Xavier Maillard)
Date: Wed, 25 Feb 2009 00:25:03 +0100
Subject: [Slackbuilds-users] Emacs Snapshot Demand?
In-Reply-To: "xgizzmo@slackbuilds.org"'s message of Mon, 23 Feb 2009 18:06:49
	-0500
Message-ID: <200902242325.n1ONP3HG023671@zogzog.maillard.mobi>

Hi,

   On Monday 23 February 2009 10:54:25 Joel J. Adamson <adamsonj at email.unc.edu> wrote:

   > 2. Is this the kind of package that is appropriate for SlackBuilds.org?
   > It is a development version of an official package.

   Slackbuilds.org normally will not accept SlackBuilds for official packages.

   Quote from http://www.slackbuilds.org/guidelines

     "As a general rule, we do not accept SlackBuild scripts of software that is
      included as part of Slackware; however, exceptions may be made by the admin
      staff on a case-by-case basis.

Fair enough but how do you fix bugs (if any) on official packages
? Or even simpler, how do you send patch to bump package version
? Reading through Slackware ChangeLog reveals it can happen
sometimes. I thought SBo was sort of "Slackware Labs".

Regards,
	Xavier
-- 
http://www.gnu.org
http://www.april.org
http://www.lolica.org

From xgizzmo at slackbuilds.org  Wed Feb 25 00:25:06 2009
From: xgizzmo at slackbuilds.org (xgizzmo at slackbuilds.org)
Date: Tue, 24 Feb 2009 19:25:06 -0500
Subject: [Slackbuilds-users] Emacs Snapshot Demand?
In-Reply-To: <200902242325.n1ONP3HG023671@zogzog.maillard.mobi>
References: <200902242325.n1ONP3HG023671@zogzog.maillard.mobi>
Message-ID: <200902241925.07093.xgizzmo@slackbuilds.org>

On Tuesday 24 February 2009 18:25:03 Xavier Maillard wrote:
> Fair enough but how do you fix bugs (if any) on official packages
> ? Or even simpler, how do you send patch to bump package version
> ? Reading through Slackware ChangeLog reveals it can happen
> sometimes. I thought SBo was sort of "Slackware Labs".
> 

Slackware is Slackware and SlackBuilds.org is SlackBuilds.org.
Bugs/feature request/etc... for official Slackware packages 
should go to <volkerdi at slackware dot com>.

http://www.slackbuilds.org/faq/#affiliation
# Are you affiliated with and/or endorsed by Slackware?
* No. We are not affiliated with or officially endorsed by either Patrick Volkerding or Slackware Linux, Inc.
  This project is maintained by volunteers who wish to contribute something useful to the Slackware user community.
  Furthermore, for clarity's sake, the concept of a SlackBuild script came from Slackware itself, not from us.



From kmuerlen83 at gmail.com  Wed Feb 25 00:52:09 2009
From: kmuerlen83 at gmail.com (Kevin Muerlen)
Date: Tue, 24 Feb 2009 18:52:09 -0600
Subject: [Slackbuilds-users] VLC package?
In-Reply-To: <49A47DE9.7020001@gmail.com>
References: <11d696810902232040v114f0671p4bd9892361cc1740@mail.gmail.com>
	<200902241615.34834.didier.spaier@epsm.fr>
	<6b6812630902240848k656b382ahc901ff7b08b6cc84@mail.gmail.com>
	<20090224111545.1e311bdb@liberty.rlwhome.lan>
	<49A47DE9.7020001@gmail.com>
Message-ID: <11d696810902241652p3b1c44c0v5eb177871ce39a6f@mail.gmail.com>

On Tue, Feb 24, 2009 at 5:08 PM, Niklas 'Nille' ?kerstr?m <
nille.kungen at gmail.com> wrote:

>
>  On Tue, 24 Feb 2009 10:48:50 -0600
>> JK Wood <joshuakwood at gmail.com> wrote:
>>
>>
>>
>>> On Tue, Feb 24, 2009 at 9:15 AM, Didier Spaier
>>> <didier.spaier at epsm.fr>wrote:
>>>
>>>
>>>
>>>> Le Tuesday 24 February 2009 05:40:52 Kevin Muerlen, vous avez
>>>> ?crit :
>>>>
>>>>
>>>>> Hello list,
>>>>>
>>>>> I don't see a VLC package on SBo...  Any chance of getting one?
>>>>>
>>>>>
>>>>>
>>>> I do not know, but you can find packages & SlackBuilds in Alien
>>>> Bob's repositories, see
>>>> http://www.slackware.com/~alien/slackbuilds/<http://www.slackware.com/%7Ealien/slackbuilds/>
>>>> <http://www.slackware.com/%7Ealien/slackbuilds/>
>>>>
>>>>
>>>>
>>> VLC is an utter monster to build on Slackware, with a horrid
>>> dependency chain and a rather low chance of success.  Which is why
>>> alienBOB's build is so important.  That's one of the few things that
>>> I'd rather go to him for than SBo.  Read his SlackBuild to find out
>>> why.
>>>
>>>
>> I was *actually thinking of making one when i made my first slackbuilds
> thats why i maintain allot of **dependicies** for  multimedia.
> But since the dependicies are only needed at build time then an SBo
> slackbuild ain't the best way to build vlc and thats why i didn't upload my
> vlc.SlackBuild
> AlienBOB's SlackBuild is far the best vlc build script for slackware and i
> recommend it, and you can't make an slackbuild like that on SBo.
> So as i see it there is not need for an build on SBo since it can't be as
> good as AlienBOB's.
>
> /Nille
> //*//
>
> *
> *
>

Thank you Nille, and to all the others who replied.  I will try the build at
AlienBob's.
Thanks!
Kevin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090224/6809e506/attachment.htm>

From pc_warner at yahoo.com  Thu Feb 26 01:55:18 2009
From: pc_warner at yahoo.com (Phillip Warner)
Date: Wed, 25 Feb 2009 17:55:18 -0800 (PST)
Subject: [Slackbuilds-users] docker dl location not working
In-Reply-To: <11d696810902241652p3b1c44c0v5eb177871ce39a6f@mail.gmail.com>
Message-ID: <668739.58185.qm@web57706.mail.re3.yahoo.com>


docker does not seem to be available in the location in the .info file.

Try http://dockapps.org/download.php/id/510/docker-1.5.tar.gz

md5sum checks out for me.

--phillip


      

From timp at timp.com.au  Thu Feb 26 02:44:32 2009
From: timp at timp.com.au (Timothy Pollard)
Date: Thu, 26 Feb 2009 12:44:32 +1000
Subject: [Slackbuilds-users] docker dl location not working
In-Reply-To: <668739.58185.qm@web57706.mail.re3.yahoo.com>
References: <11d696810902241652p3b1c44c0v5eb177871ce39a6f@mail.gmail.com>
	<668739.58185.qm@web57706.mail.re3.yahoo.com>
Message-ID: <20090226124432.438aca46@shammah.timp.com.au>

On Wed, 25 Feb 2009 17:55:18 -0800 (PST)
Phillip Warner <pc_warner at yahoo.com> wrote:
> 
> docker does not seem to be available in the location in the .info file.
> 
> Try http://dockapps.org/download.php/id/510/docker-1.5.tar.gz
> 
> md5sum checks out for me.
> 
> --phillip
> 

The icculus.org (http://icculus.org/openbox/2/docker/docker-1.5.tar.gz) link
works OK for me, though dockapps.org seems to be fine as well.

-- 
TimP
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090226/ff1af13b/attachment.asc>

From chess at chessgriffin.com  Thu Feb 26 15:21:40 2009
From: chess at chessgriffin.com (Chess Griffin)
Date: Thu, 26 Feb 2009 10:21:40 -0500
Subject: [Slackbuilds-users] Sbopkg 0.27.0 released
Message-ID: <20090226152140.GA18127@localhost>

A new version 0.27.0 of sbopkg has been released.  Once again, I have
had great assistance from several contributors in the form of feature
requests, bug reports, and patches.  I would like to especially thank
Mauro Giachero and slakmagik for their hard work in reviewing code,
providing patches, and offering excellent advice and suggestions.

This release brings many bug fixes and new features.  Please be aware
that there are some new variables for sbopkg.conf, so if you are
upgrading, be sure to check out the sbopkg.conf.new and merge the
changes.

Here are a few of the notable items from the ChangeLog.txt:

  * Commit a patch that adds a new sbopkg.conf configuration variable,
    QUEUEDIR, where users can define where saved queues are stored; also, when
    the user wants to load a saved queue, show a list of available saved
    queues; thanks to slakmagik for the patch.
  * Add ability to search for keywords in the README files using regular
    expressions; this new 'string search' can also be narrowed to only search
    installed packages; thanks to slakmagik for the original patch and
    implementation and thanks to both slakmagik and Mauro Giachero for
    cleaning it up and addressing minor issues before the commit.
  * Add ability to view a diff of an edited .info or SlackBuild file before
    choosing which one to use; this feature adds two configuration variables
    to the sbopkg.conf file: DIFF and DIFFOPTS; thanks to Phillip Warner for
    the suggestion and thanks to Mauro Giachero for helping debug/improve my
    original implemenation.
  * Add ability to view more files in each application's folder, i.e.
    doinst.sh, or *.desktop files; thanks to Phillip Warner for the suggestion
    and thanks to slakmagik for the patch implementing this feature.
  * Rework the check for root:root permissions when installing packages; now,
    if the package does not have root:root permissions, sbopkg will display
    the output of ls -l <packagename> and ask if the user wishes to install or
    abort, rather than only aborting.
  * Move the -q option to -g (general search) in order to make way for -q,
    'quiet mode' where the output of some of the command line options (i.e.
    the command line progressbar) can be minimized.  More quieting will likely
    occur in future releases.  Thanks to alkos333 for the feature request.
  * Implement a workaround so that the dialog interface now works better with
    GNU Screen and rxvt-based terminals. Thanks to Phillip Warner for raising
    the issue and thanks to Mauro Giachero for working on the implementation.
  * Include a French translation of the two sbopkg man pages.  For now, these
    man pages will be included in the /doc directory until I have time to
    figure out whether they can be automatically installed in place of the
    English ones depending on a locale setting.  In any event, I would like to
    extend my thanks to Marie-Claude Collilieux for providing this first
    translation for sbopkg.  I am sure folks will appreciate the work she put
    into it.  If anyone else wants to follow her lead and provide some other
    translations, I would be happy to include them.  Thanks Marie-Claude!
  * Add in several patches from slakmagik that lets the user choose from saved
    queues, modifies how the saved queues and backup queues work, and modifies
    several other queue-related functions and menus.  Many thanks to slakmagik
    for his continually excellent contributions.
  * Implement an 'autoqueue' by allowing the user to specify queue names to
    '-b' and '-i' and by adding a -e option whereby the user can specify what
    to do on errors (stop, ask, or continue).  Thanks to Alan Hicks for
    suggesting this feature and thanks to Mauro Giachero for the
    implementation.

The full ChangeLog.txt can be read here:
http://www.sbopkg.org/files/ChangeLog.txt

So, to recap, there are three new variables for sbopkg.conf:
QUEUEDIR, DIFF, and DIFFOPTS.  These are explained in the sbopkg.conf(5)
man page and need to be added to your current sbopkg.conf if you are
upgrading.

A noarch package and source tarball for version 0.27.0 can be found at
the sbopkg project website:

http://www.sbopkg.org

I would also like to make an important announcement about upcoming
versions of sbopkg.  Now that 0.27.0 is out the door, we are going to
take some time off, and then turn our attention to an overall code
review/audit with an eye towards making the code more efficient with
less bugs.  It is unlikely that new features will be implemented.  Along
with this review, we will be removing the 'user mode' support from
sbopkg and changing the codebase so sbopkg runs out of /usr/sbin and
requires root privileges, just like several other similar Slackware
package tools.  Additionally, we will be reviewing the file and
directory layout for sbopkg-related items to consider whether things
need to be moved.  Personally, I am leaning towards moving everything
into /var/lib/sbopkg, so there would be
/var/lib/sbopkg/{repo,tmp,cache,queues} etc., but we have not spent much
time discussing this.  If you have any thoughts on what would be a set
of sensible defaults in this area, please feel free to speak up.
Obviously, if the directory structure is moved, this will require future
user intervention in the form of moving your local repo, or adjusting
the sbopkg.conf back to where you want things to be stored.

Anyway, the point here is simply to let folks know what is on the
horizon for future releases.  There is no timetable for when the post
0.27.0 release will occur, but this next major release will probably
take longer than past releases.  I have created a 0.27.0-stable branch
in SVN so we can backport fixes and address issues in the 0.27.0
release as they come up.

Again, I would like to thank all the contributors to sbopkg.  This
utility is greatly benefiting from the feedback and assistance of many
individuals.

Enjoy!

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090226/791e88d4/attachment.sig>

From rw at rlworkman.net  Thu Feb 26 16:45:49 2009
From: rw at rlworkman.net (Robby Workman)
Date: Thu, 26 Feb 2009 10:45:49 -0600
Subject: [Slackbuilds-users] [sbopkg-users] Sbopkg 0.27.0 released
In-Reply-To: <20090226152140.GA18127@localhost>
References: <20090226152140.GA18127@localhost>
Message-ID: <20090226104549.5d675767@liberty.rlwhome.lan>

On Thu, 26 Feb 2009 10:21:40 -0500
Chess Griffin <chess at chessgriffin.com> wrote:

>   * Include a French translation of the two sbopkg man pages.  For
> now, these man pages will be included in the /doc directory until I
> have time to figure out whether they can be automatically installed
> in place of the English ones depending on a locale setting. 


Install them to /usr/man/fr/man?/

See attached patch.


> /var/lib/sbopkg/{repo,tmp,cache,queues} etc., but we have not spent
> much time discussing this.  If you have any thoughts on what would be
> a set of sensible defaults in this area, please feel free to speak up.


Unless moving to a more self-contained layout simplifies things for
you, I wouldn't do it that way.  I'd lean more toward using these:
  /var/tmp/sbopkg
  /var/cache/sbopkg
  /var/lib/sbopkg/{queues,repo}
  Other things might belong in subdirs of /var/{tmp,cache}/sbopkg as
  appopriate, and probably other things (stuff you want to keep around
  no matter what) will go in /var/lib/sbopkg.  Anyway, hopefully that
  made a little bit of sense... :-)

-RW
  
-------------- next part --------------
A non-text attachment was scrubbed...
Name: install_fr_manpages.diff
Type: text/x-patch
Size: 14937 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090226/ea20bbb6/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090226/ea20bbb6/attachment-0001.asc>

From me at alkos333.net  Thu Feb 26 16:59:37 2009
From: me at alkos333.net (alkos333)
Date: Thu, 26 Feb 2009 10:59:37 -0600
Subject: [Slackbuilds-users] [sbopkg-users] Sbopkg 0.27.0 released
In-Reply-To: <20090226104549.5d675767@liberty.rlwhome.lan>
References: <20090226152140.GA18127@localhost>
	<20090226104549.5d675767@liberty.rlwhome.lan>
Message-ID: <a6f13f000902260859t31834e2bi1ab113e71cc8fdda@mail.gmail.com>

2009/2/26 Robby Workman <rw at rlworkman.net>:
> On Thu, 26 Feb 2009 10:21:40 -0500
> Chess Griffin <chess at chessgriffin.com> wrote:
>
>> ? * Include a French translation of the two sbopkg man pages. ?For
>> now, these man pages will be included in the /doc directory until I
>> have time to figure out whether they can be automatically installed
>> in place of the English ones depending on a locale setting.
>
>
> Install them to /usr/man/fr/man?/
>
> See attached patch.
>
>
>> /var/lib/sbopkg/{repo,tmp,cache,queues} etc., but we have not spent
>> much time discussing this. ?If you have any thoughts on what would be
>> a set of sensible defaults in this area, please feel free to speak up.
>
>
> Unless moving to a more self-contained layout simplifies things for
> you, I wouldn't do it that way. ?I'd lean more toward using these:
> ?/var/tmp/sbopkg
> ?/var/cache/sbopkg
> ?/var/lib/sbopkg/{queues,repo}
> ?Other things might belong in subdirs of /var/{tmp,cache}/sbopkg as
> ?appopriate, and probably other things (stuff you want to keep around
> ?no matter what) will go in /var/lib/sbopkg. ?Anyway, hopefully that
> ?made a little bit of sense... :-)

I've always used the following layout:

root at tpt60:~# ls -l /var/cache/sbopkg/
total 7
drwxr-xr-x 2 root root 5160 2009-02-26 10:01 packages/
drwxr-xr-x 2 root root  104 2009-02-26 10:01 queues/
drwxr-xr-x 3 root root   72 2008-12-12 13:16 slackbuilds/
drwxr-xr-x 2 root root 1688 2009-02-26 10:01 source/

and  /var/log/sbopkg/sbopkg-build-log   for the permanent log

From thomditom at aktiivi.ath.cx  Thu Feb 26 22:21:06 2009
From: thomditom at aktiivi.ath.cx (Thomas Morper)
Date: Thu, 26 Feb 2009 23:21:06 +0100
Subject: [Slackbuilds-users] Flash Player security update
Message-ID: <200902262321.06709.thomditom@aktiivi.ath.cx>

Just in case this hasn't been addressed yet and is already in the queue 
waiting for a push...

Adobe has fixed a vulnerability in the Flash Player:

  http://www.adobe.com/support/security/bulletins/apsb09-01.html

The download-link from the .info-File now points to version 10.0r22,
md5sum is 23e4c2b844db0f87ff62084178aa2b1f.

-- 

From pc_warner at yahoo.com  Thu Feb 26 23:52:57 2009
From: pc_warner at yahoo.com (Phillip Warner)
Date: Thu, 26 Feb 2009 15:52:57 -0800 (PST)
Subject: [Slackbuilds-users] Flash Player security update
In-Reply-To: <200902262321.06709.thomditom@aktiivi.ath.cx>
Message-ID: <625354.25235.qm@web57705.mail.re3.yahoo.com>


thank you, Thomas

--- On Thu, 2/26/09, Thomas Morper <thomditom at aktiivi.ath.cx> wrote:

> From: Thomas Morper <thomditom at aktiivi.ath.cx>
> Subject: [Slackbuilds-users] Flash Player security update
> To: slackbuilds-users at slackbuilds.org
> Date: Thursday, February 26, 2009, 2:21 PM
> Just in case this hasn't been addressed yet and is
> already in the queue 
> waiting for a push...
> 
> Adobe has fixed a vulnerability in the Flash Player:
> 
>  
> http://www.adobe.com/support/security/bulletins/apsb09-01.html
> 
> The download-link from the .info-File now points to version
> 10.0r22,
> md5sum is 23e4c2b844db0f87ff62084178aa2b1f.
> 
> -- 
> _______________________________________________
> 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 vbatts at hashbangbash.com  Fri Feb 27 04:52:58 2009
From: vbatts at hashbangbash.com (Vincent Batts)
Date: Thu, 26 Feb 2009 22:52:58 -0600
Subject: [Slackbuilds-users] Proposal of SBU marker in README's
Message-ID: <2015330f0902262052g6b66bbc2od65a5179c1762729@mail.gmail.com>

In the same fashion of the Linux-From-Scratch guide, what are everyone's
idea on having a baseline package build time marked as the Single Build Unit
(SBU). some package of consensus, and included in the README's could have in
SBU's the relative build time of their SlackBuild. for example if libsndfile
takes 4 minutes to build on your machine, that would be 1 SBU for you.
therefore qt4 would be 45 SBU's and ipcalc would be < 1 SBU

this is an idea that would provide more foresight to the prospective
builders of any given SBo.

vb

http://hashbangbash.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090226/72a83cf9/attachment.htm>

From rworkman at slackbuilds.org  Fri Feb 27 05:06:26 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 26 Feb 2009 23:06:26 -0600
Subject: [Slackbuilds-users] Flash Player security update
In-Reply-To: <200902262321.06709.thomditom@aktiivi.ath.cx>
References: <200902262321.06709.thomditom@aktiivi.ath.cx>
Message-ID: <20090226230626.253c5999@liberty.rlwhome.lan>

On Thu, 26 Feb 2009 23:21:06 +0100
Thomas Morper <thomditom at aktiivi.ath.cx> wrote:

> Just in case this hasn't been addressed yet and is already in the
> queue waiting for a push...
> 
> Adobe has fixed a vulnerability in the Flash Player:
> 
>   http://www.adobe.com/support/security/bulletins/apsb09-01.html
> 
> The download-link from the .info-File now points to version 10.0r22,
> md5sum is 23e4c2b844db0f87ff62084178aa2b1f.
> 

I've got this in pending now.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090226/48a24c10/attachment.asc>

From rworkman at slackbuilds.org  Fri Feb 27 05:11:45 2009
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 26 Feb 2009 23:11:45 -0600
Subject: [Slackbuilds-users] Proposal of SBU marker in README's
In-Reply-To: <2015330f0902262052g6b66bbc2od65a5179c1762729@mail.gmail.com>
References: <2015330f0902262052g6b66bbc2od65a5179c1762729@mail.gmail.com>
Message-ID: <20090226231145.364546ec@liberty.rlwhome.lan>

On Thu, 26 Feb 2009 22:52:58 -0600
Vincent Batts <vbatts at hashbangbash.com> wrote:

> In the same fashion of the Linux-From-Scratch guide, what are
> everyone's idea on having a baseline package build time marked as the
> Single Build Unit (SBU). some package of consensus, and included in
> the README's could have in SBU's the relative build time of their
> SlackBuild. for example if libsndfile takes 4 minutes to build on
> your machine, that would be 1 SBU for you. therefore qt4 would be 45
> SBU's and ipcalc would be < 1 SBU
> 
> this is an idea that would provide more foresight to the prospective
> builders of any given SBo.


Hrm, I don't know.  

On one hand, it would certainly be useful information to have, but at
the same time, it's error prone -- either the data is very subjective
(i.e. "that took forever") or it requires the submitter to time every
build they run and compare it against some "standard" build.

Besides, something like this would take all the fun out of comparing
build times -- there would be this boring "<1SBU" or "10SBU" or
"400SBU" instead of "faster than a fifteen year old boy's first time
with Eliza Dushku" or "this thing takes a metric assload of time to
build"

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090226/edf8951e/attachment.asc>

From joshuakwood at gmail.com  Fri Feb 27 05:43:38 2009
From: joshuakwood at gmail.com (JK Wood)
Date: Thu, 26 Feb 2009 23:43:38 -0600
Subject: [Slackbuilds-users] Proposal of SBU marker in README's
In-Reply-To: <20090226231145.364546ec@liberty.rlwhome.lan>
References: <2015330f0902262052g6b66bbc2od65a5179c1762729@mail.gmail.com>
	<20090226231145.364546ec@liberty.rlwhome.lan>
Message-ID: <6b6812630902262143o786c2d48q332c6c1bbfa666b8@mail.gmail.com>

On Thu, Feb 26, 2009 at 11:11 PM, Robby Workman <rworkman at slackbuilds.org>wrote:

> On Thu, 26 Feb 2009 22:52:58 -0600
> Vincent Batts <vbatts at hashbangbash.com> wrote:
>
> > In the same fashion of the Linux-From-Scratch guide, what are
> > everyone's idea on having a baseline package build time marked as the
> > Single Build Unit (SBU). some package of consensus, and included in
> > the README's could have in SBU's the relative build time of their
> > SlackBuild. for example if libsndfile takes 4 minutes to build on
> > your machine, that would be 1 SBU for you. therefore qt4 would be 45
> > SBU's and ipcalc would be < 1 SBU
> >
> > this is an idea that would provide more foresight to the prospective
> > builders of any given SBo.
>
>
> Hrm, I don't know.
>
> On one hand, it would certainly be useful information to have, but at
> the same time, it's error prone -- either the data is very subjective
> (i.e. "that took forever") or it requires the submitter to time every
> build they run and compare it against some "standard" build.
>
> Besides, something like this would take all the fun out of comparing
> build times -- there would be this boring "<1SBU" or "10SBU" or
> "400SBU" instead of "faster than a fifteen year old boy's first time
> with Eliza Dushku" or "this thing takes a metric assload of time to
> build"
>
> -RW
>
> _______________________________________________
> 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/
>
>
>
I think that the metric buttload is a very useful unit of time when
expressing things like these.

--JK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090226/78c3ef64/attachment.htm>

From chaos.proton at gmail.com  Fri Feb 27 06:39:17 2009
From: chaos.proton at gmail.com (Grissiom)
Date: Fri, 27 Feb 2009 14:39:17 +0800
Subject: [Slackbuilds-users] Bug in submit page?
In-Reply-To: <a0adeea50902260658w605e45e3se059e3f07c892c58@mail.gmail.com>
References: <a0adeea50902260658w605e45e3se059e3f07c892c58@mail.gmail.com>
Message-ID: <a0adeea50902262239s7b05be4fh8dbc6ec00537e656@mail.gmail.com>

Hi, all,

It's not a bug of slackbuilds but slackbuilds.org. When I submitting a
package, I noticed the submission page rendered weird in firefox. Here is
the screen shot:

http://picasaweb.google.com/lh/photo/q8NlYX9sQWJSsD8c5eg1OQ?feat=directlink


-- 
Cheers,
Grissiom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090227/ead7380c/attachment-0001.htm>

From elyk03 at gmail.com  Fri Feb 27 07:01:44 2009
From: elyk03 at gmail.com (Kyle Guinn)
Date: Fri, 27 Feb 2009 01:01:44 -0600
Subject: [Slackbuilds-users] Proposal of SBU marker in README's
In-Reply-To: <6b6812630902262143o786c2d48q332c6c1bbfa666b8@mail.gmail.com>
References: <2015330f0902262052g6b66bbc2od65a5179c1762729@mail.gmail.com>
	<20090226231145.364546ec@liberty.rlwhome.lan>
	<6b6812630902262143o786c2d48q332c6c1bbfa666b8@mail.gmail.com>
Message-ID: <2dcaacad0902262301l27c6a67fmc15d6c89c3f03c0e@mail.gmail.com>

On 2/26/09, JK Wood <joshuakwood at gmail.com> wrote:
> On Thu, Feb 26, 2009 at 11:11 PM, Robby Workman <rworkman at slackbuilds.org>
> wrote:
> > Besides, something like this would take all the fun out of comparing
> > build times -- there would be this boring "<1SBU" or "10SBU" or
> > "400SBU" instead of "faster than a fifteen year old boy's first time
> > with Eliza Dushku" or "this thing takes a metric assload of time to
> > build"
> >
>
> I think that the metric buttload is a very useful unit of time when
> expressing things like these.
>

Yes, we should all use the metric system for this.  It's well suited
for those types of unit conversions.

-Kyle

From me at alkos333.net  Fri Feb 27 14:14:03 2009
From: me at alkos333.net (alkos333)
Date: Fri, 27 Feb 2009 08:14:03 -0600
Subject: [Slackbuilds-users] Proposal of SBU marker in README's
In-Reply-To: <2dcaacad0902262301l27c6a67fmc15d6c89c3f03c0e@mail.gmail.com>
References: <2015330f0902262052g6b66bbc2od65a5179c1762729@mail.gmail.com>
	<20090226231145.364546ec@liberty.rlwhome.lan>
	<6b6812630902262143o786c2d48q332c6c1bbfa666b8@mail.gmail.com>
	<2dcaacad0902262301l27c6a67fmc15d6c89c3f03c0e@mail.gmail.com>
Message-ID: <a6f13f000902270614m60e5f973mfde0dc293f50e1c3@mail.gmail.com>

On Fri, Feb 27, 2009 at 1:01 AM, Kyle Guinn <elyk03 at gmail.com> wrote:
> Yes, we should all use the metric system for this. ?It's well suited
> for those types of unit conversions.

SlackBuilds.org - teaching the metric system in U.S. :P

-- 

Fran Lebowitz  - "You're only has good as your last haircut."

From erik at slackbuilds.org  Fri Feb 27 15:09:23 2009
From: erik at slackbuilds.org (Erik Hanson)
Date: Fri, 27 Feb 2009 09:09:23 -0600
Subject: [Slackbuilds-users] Bug in submit page?
In-Reply-To: <a0adeea50902262239s7b05be4fh8dbc6ec00537e656@mail.gmail.com>
References: <a0adeea50902260658w605e45e3se059e3f07c892c58@mail.gmail.com>
	<a0adeea50902262239s7b05be4fh8dbc6ec00537e656@mail.gmail.com>
Message-ID: <20090227090923.6b605816@shaggy.scooby>

On Feb 27, 2009, at  2:39 PM, Grissiom wrote:

> Hi, all,
> 
> It's not a bug of slackbuilds but slackbuilds.org. When I submitting a
> package, I noticed the submission page rendered weird in firefox. Here is
> the screen shot:
> 
> http://picasaweb.google.com/lh/photo/q8NlYX9sQWJSsD8c5eg1OQ?feat=directlink

I can't reproduce this and have had no other complaints. It looks like a font
size issue. Possibly you need to reset the zoom (View> Zoom> Reset) in FF or
turn down the minimum font size.

-- 
Erik Hanson
http://slackbuilds.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090227/2bf43955/attachment.asc>