From glen at delfi.ee  Mon Aug  1 00:38:35 2005
From: glen at delfi.ee (Elan =?iso-8859-2?q?Ruusam=E4e?=)
Date: Mon, 1 Aug 2005 01:38:35 +0300
Subject: error: syslog-ng:68 duplicate log entry for /var/log/xferlog
In-Reply-To: <20050319081335.GA6680@os>
References: <20050319081335.GA6680@os>
Message-ID: <200508010138.36206.glen@delfi.ee>

how this got resolved? because i seem to have same conflict between syslog and 
proftpd.

# grep xferlog /etc/logrotate.d/*
/etc/logrotate.d/ftpd:/var/log/xferlog {
/etc/logrotate.d/syslog:/var/log/xferlog {
# rpm -qf ftpd syslog
proftpd-common-1.2.10-5
syslog-1.4.1-13.2


On Saturday 19 March 2005 10:13, Tomasz Pala wrote:
> Has appeared after:
>
> SOURCES/syslog-ng.logrotate
>
> 1.9 Sun Nov 7 13:57:37 2004 by blues
> - added xferlog
>
> Please take a look at /etc/logrotate.d/ftpd from proftpd-common
> (SOURCES/proftpd.logrotate) and remove one of these two (I suppose
> you've got some reason in adding it to syslog itself).

-- 
glen


From blues at pld-linux.org  Mon Aug  1 11:45:45 2005
From: blues at pld-linux.org (=?ISO-8859-2?Q?Pawe=B3_Go=B3aszewski?=)
Date: Mon, 1 Aug 2005 11:45:45 +0200 (CEST)
Subject: error: syslog-ng:68 duplicate log entry for /var/log/xferlog
In-Reply-To: <200508010138.36206.glen@delfi.ee>
References: <20050319081335.GA6680@os> <200508010138.36206.glen@delfi.ee>
Message-ID: <Pine.LNX.4.61L.0508011144530.1728@wby.gnfx.tqn.cy>

On Mon, 1 Aug 2005, Elan Ruusam?e wrote:
> how this got resolved? because i seem to have same conflict between syslog and 
> proftpd.
> 
> # grep xferlog /etc/logrotate.d/*
> /etc/logrotate.d/ftpd:/var/log/xferlog {
> /etc/logrotate.d/syslog:/var/log/xferlog {
> # rpm -qf ftpd syslog
> proftpd-common-1.2.10-5
> syslog-1.4.1-13.2

Should be removed from proftpd, IMO.
xferlog i a common thing.

> > Has appeared after:
> >
> > SOURCES/syslog-ng.logrotate
> >
> > 1.9 Sun Nov 7 13:57:37 2004 by blues
> > - added xferlog
> >
> > Please take a look at /etc/logrotate.d/ftpd from proftpd-common 
> > (SOURCES/proftpd.logrotate) and remove one of these two (I suppose 
> > you've got some reason in adding it to syslog itself).
> 

-- 
pozdr.  Pawe? Go?aszewski          jid:blues<at>jabber<dot>gda<dot>pl
--------------------------------------------------------------------------
If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby
Pro-Logic Surround Sound with Bass Boost and all the music is free.

From glen at delfi.ee  Mon Aug  1 13:27:13 2005
From: glen at delfi.ee (Elan =?iso-8859-13?q?Ruusam=E4e?=)
Date: Mon, 1 Aug 2005 14:27:13 +0300
Subject: error: syslog-ng:68 duplicate log entry for /var/log/xferlog
In-Reply-To: <Pine.LNX.4.61L.0508011144530.1728@wby.gnfx.tqn.cy>
References: <20050319081335.GA6680@os> <200508010138.36206.glen@delfi.ee>
	<Pine.LNX.4.61L.0508011144530.1728@wby.gnfx.tqn.cy>
Message-ID: <200508011427.13723.glen@delfi.ee>

On Monday 01 August 2005 12:45, Pawe? Go?aszewski wrote:
> On Mon, 1 Aug 2005, Elan Ruusam?e wrote:
> > how this got resolved? because i seem to have same conflict between
> > syslog and proftpd.
> >
> > # grep xferlog /etc/logrotate.d/*
> > /etc/logrotate.d/ftpd:/var/log/xferlog {
> > /etc/logrotate.d/syslog:/var/log/xferlog {
> > # rpm -qf ftpd syslog
> > proftpd-common-1.2.10-5
> > syslog-1.4.1-13.2
>
> Should be removed from proftpd, IMO.
> xferlog i a common thing.
although the question remains, who writes the log? syslog? or proftpd?
if it's syslogd, then yes, rotation should be in syslog package
but if it's proftpd writing it directly, then it should be in proftpd package.

but in latter case i believe proftpd should be reconfigured to use differeng 
logfile.

>
> > > Has appeared after:
> > >
> > > SOURCES/syslog-ng.logrotate
> > >
> > > 1.9 Sun Nov 7 13:57:37 2004 by blues
> > > - added xferlog
> > >
> > > Please take a look at /etc/logrotate.d/ftpd from proftpd-common
> > > (SOURCES/proftpd.logrotate) and remove one of these two (I suppose
> > > you've got some reason in adding it to syslog itself).

-- 
glen


From glen at delfi.ee  Mon Aug  1 17:39:34 2005
From: glen at delfi.ee (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Mon, 1 Aug 2005 18:39:34 +0300
Subject: syslog as non-root
Message-ID: <200508011839.34844.glen@delfi.ee>

hi

is there any reason why sysklogd runs as root? i see it possible to switch 
user with -u switch with both daemons (syslogd/klogd). only thing needed to 
assure is that the logs in /var/log are owned by syslog uid and that 
logrotation scripts create the files with same permissions.


-- 
glen


From qboosh at pld-linux.org  Mon Aug  1 20:22:38 2005
From: qboosh at pld-linux.org (Jakub Bogusz)
Date: Mon, 1 Aug 2005 20:22:38 +0200
Subject: ooo2 @ ac-amd64
Message-ID: <20050801182238.GA8551@fngna.oyu>

19123 builder   39  19  408m 393m 3788 R 99.9 19.6   2477:44 cc1plus
                                                     ^^^^^^^

I doubt if it makes sense to wait longer... any objections against
killing?


Offending file/command line:

Making: ../../unxlngx4.pro/slo/smilfunctionparser.obj
amd64-pld-linux-g++ -fmessage-length=0 -c -I.  -I. -I../inc -I../../inc -I../../unx/inc -I../../unxlngx4.pro/inc -I. -I/home/users/builder/rpm/BUILD/ooo-build-1.9.118/build/src680-m118/solver/680/unxlngx4.pro/inc/stl -I/home/users/builder/rpm/BUILD/ooo-build-1.9.118/build/src680-m118/solver/680/unxlngx4.pro/inc/external -I/home/users/builder/rpm/BUILD/ooo-build-1.9.118/build/src680-m118/solver/680/unxlngx4.pro/inc -I/home/users/builder/rpm/BUILD/ooo-build-1.9.118/build/src680-m118/solenv/unxlngx4/inc -I/home/users/builder/rpm/BUILD/ooo-build-1.9.118/build/src680-m118/solenv/inc -I/home/users/builder/rpm/BUILD/ooo-build-1.9.118/build/src680-m118/res -I/usr/stlport -I/usr/include/stlport -I/usr/include/stlport -I/home/users/builder/rpm/BUILD/ooo-build-1.9.118/build/src680-m118/solenv/inc/Xp31 -INO_JAVA_HOME/include -INO_JAVA_HOME/include/linux -INO_JAVA_HOME/include/native_threads/include
-I/usr/X11R6/include     -I. -I../../res -I. -O -fno-strict-aliasing  -O2 -fno-strict-aliasing -pipe -fno-use-cxa-atexit  -Wno-ctor-dtor-privacy -include preinclude.h -fexceptions -fno-enforce-eh-specs -O2 -fno-strict-aliasing  -fPIC -DLINUX -DUNX -DVCL -DGCC -DC300 -DX86_64 -DGXX_INCLUDE_PATH=/usr/include/c++/3.3.6 -DCVER=C300 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86_64 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR -D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -D__DMAKE -DUNIX -DCPPU_ENV=gcc3 -DSUPD=680 -DPRODUCT -DNDEBUG -DPRODUCT_FULL -DOSL_DEBUG_LEVEL=0 -DOPTIMIZE -DEXCEPTIONS_ON -DCUI -DSRC680   -DSHAREDLIB -D_DLL_  -DMULTITHREAD -w -o ../../unxlngx4.pro/slo/smilfunctionparser.o /home/users/builder/rpm/BUILD/ooo-build-1.9.118/build/src680-m118/slideshow/source/engine/smilfunctionparser.cxx


-- 
Jakub Bogusz    http://qboosh.cs.net.pl/


From glen at delfi.ee  Mon Aug  1 21:02:38 2005
From: glen at delfi.ee (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Mon, 1 Aug 2005 22:02:38 +0300
Subject: ooo2 @ ac-amd64
In-Reply-To: <20050801182238.GA8551@fngna.oyu>
References: <20050801182238.GA8551@fngna.oyu>
Message-ID: <200508012202.38776.glen@delfi.ee>

On Monday 01 August 2005 21:22, Jakub Bogusz wrote:
> 19123 builder   39  19  408m 393m 3788 R 99.9 19.6   2477:44 cc1plus
>                                                      ^^^^^^^
>
> I doubt if it makes sense to wait longer... any objections against
> killing?
yeah. kill it.
same happens on my home pc (also amd64) with gcc-3.3.5-2

and when i tried to compile it with gcc4 from th 
(gcc-4.1.0-0.20050726T1627UTC.1), then it died there:
http://glen.pastebin.com/327014

altho i can't find my older lines from gcc 3.3 build as bastebin has nuked 
these by now.

>
> Offending file/command line:
>
> Making: ../../unxlngx4.pro/slo/smilfunctionparser.obj
> amd64-pld-linux-g++ -fmessage-length=0 -c -I.  -I. -I../inc -I../../inc
> -I../../unx/inc -I../../unxlngx4.pro/inc -I.
> -I/home/users/builder/rpm/BUILD/ooo-build-1.9.118/build/src680-m118/solver/
>680/unxlngx4.pro/inc/stl
> -I/home/users/builder/rpm/BUILD/ooo-build-1.9.118/build/src680-m118/solver/
>680/unxlngx4.pro/inc/external
> -I/home/users/builder/rpm/BUILD/ooo-build-1.9.118/build/src680-m118/solver/
>680/unxlngx4.pro/inc
> -I/home/users/builder/rpm/BUILD/ooo-build-1.9.118/build/src680-m118/solenv/
>unxlngx4/inc
> -I/home/users/builder/rpm/BUILD/ooo-build-1.9.118/build/src680-m118/solenv/
>inc -I/home/users/builder/rpm/BUILD/ooo-build-1.9.118/build/src680-m118/res
> -I/usr/stlport -I/usr/include/stlport -I/usr/include/stlport
> -I/home/users/builder/rpm/BUILD/ooo-build-1.9.118/build/src680-m118/solenv/
>inc/Xp31 -INO_JAVA_HOME/include -INO_JAVA_HOME/include/linux
> -INO_JAVA_HOME/include/native_threads/include -I/usr/X11R6/include     -I.
> -I../../res -I. -O -fno-strict-aliasing  -O2 -fno-strict-aliasing -pipe
> -fno-use-cxa-atexit  -Wno-ctor-dtor-privacy -include preinclude.h
> -fexceptions -fno-enforce-eh-specs -O2 -fno-strict-aliasing  -fPIC -DLINUX
> -DUNX -DVCL -DGCC -DC300 -DX86_64 -DGXX_INCLUDE_PATH=/usr/include/c++/3.3.6
> -DCVER=C300 -D_USE_NAMESPACE -DNPTL -DGLIBC=2 -DX86_64 -D_PTHREADS
> -D_REENTRANT -DNEW_SOLAR -D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -D__DMAKE
> -DUNIX -DCPPU_ENV=gcc3 -DSUPD=680 -DPRODUCT -DNDEBUG -DPRODUCT_FULL
> -DOSL_DEBUG_LEVEL=0 -DOPTIMIZE -DEXCEPTIONS_ON -DCUI -DSRC680   -DSHAREDLIB
> -D_DLL_  -DMULTITHREAD -w -o ../../unxlngx4.pro/slo/smilfunctionparser.o
> /home/users/builder/rpm/BUILD/ooo-build-1.9.118/build/src680-m118/slideshow
>/source/engine/smilfunctionparser.cxx

-- 
glen


From pluto at agmk.net  Mon Aug  1 21:11:56 2005
From: pluto at agmk.net (Pawel Sikora)
Date: Mon, 1 Aug 2005 21:11:56 +0200
Subject: ooo2 @ ac-amd64
In-Reply-To: <200508012202.38776.glen@delfi.ee>
References: <20050801182238.GA8551@fngna.oyu>
	<200508012202.38776.glen@delfi.ee>
Message-ID: <200508012111.56589.pluto@agmk.net>

On Monday 01 of August 2005 21:02, Elan Ruusam?e wrote:
> On Monday 01 August 2005 21:22, Jakub Bogusz wrote:
> > 19123 builder   39  19  408m 393m 3788 R 99.9 19.6   2477:44 cc1plus
> >                                                      ^^^^^^^
> >
> > I doubt if it makes sense to wait longer... any objections against
> > killing?
>
> yeah. kill it.
> same happens on my home pc (also amd64) with gcc-3.3.5-2

please add -save-temps to c(xx)flags and run incremental OO build.
with preprocesed source you can report gcc time/memory-hog bug.

> and when i tried to compile it with gcc4 from th
> (gcc-4.1.0-0.20050726T1627UTC.1), then it died there:
> http://glen.pastebin.com/327014

OO needs gcc34+ patch. iirc the 1.1.x version contains it
but not applies by default. (OO2/gcc34+ status is unknown for me).

-- 
The only thing necessary for the triumph of evil
  is for good men to do nothing.
                                           - Edmund Burke


From qboosh at pld-linux.org  Mon Aug  1 21:57:56 2005
From: qboosh at pld-linux.org (Jakub Bogusz)
Date: Mon, 1 Aug 2005 21:57:56 +0200
Subject: ooo2 @ ac-amd64
In-Reply-To: <200508012111.56589.pluto@agmk.net>
References: <20050801182238.GA8551@fngna.oyu>
	<200508012202.38776.glen@delfi.ee>
	<200508012111.56589.pluto@agmk.net>
Message-ID: <20050801195756.GA9975@fngna.oyu>

On Mon, Aug 01, 2005 at 09:11:56PM +0200, Pawel Sikora wrote:
> On Monday 01 of August 2005 21:02, Elan Ruusam?e wrote:
> > On Monday 01 August 2005 21:22, Jakub Bogusz wrote:
> > > 19123 builder   39  19  408m 393m 3788 R 99.9 19.6   2477:44 cc1plus
> > >                                                      ^^^^^^^
> > >
> > > I doubt if it makes sense to wait longer... any objections against
> > > killing?
> >
> > yeah. kill it.

Done.

> > same happens on my home pc (also amd64) with gcc-3.3.5-2
> 
> please add -save-temps to c(xx)flags and run incremental OO build.
> with preprocesed source you can report gcc time/memory-hog bug.

Not for 3.3.x as this branch has been closed.


-- 
Jakub Bogusz    http://qboosh.cs.net.pl/


From lukaszmach at gmail.com  Wed Aug  3 13:06:38 2005
From: lukaszmach at gmail.com (maHo)
Date: Wed, 3 Aug 2005 13:06:38 +0200
Subject: passwdgen
Message-ID: <52799c7005080304062128136d@mail.gmail.com>

Hello

#v+
$ passwdgen -1p@ --min=4 --max=6
#v-

and it hangs. 

Could someone check if you have similar functionality of passwdgen?

regards

maHo


From saq at pld-linux.org  Wed Aug  3 17:07:33 2005
From: saq at pld-linux.org (=?iso-8859-2?Q?Pawe=B3?= Sakowski)
Date: Wed, 03 Aug 2005 17:07:33 +0200
Subject: SPECS: vte.spec - broken, rel. down to 0.1
In-Reply-To: <SPECS_vte.spec.1.77@pld-linux.org>
References: <SPECS_vte.spec.1.76@pld-linux.org>
	<SPECS_vte.spec.1.77@pld-linux.org>
Message-ID: <1123081653.5438.11.camel@neptune.sakowski.pl>

On Wed, 2005-08-03 at 16:19 +0200, freetz wrote:
>  $Log$
> +Revision 1.77  2005/08/03 14:19:04  freetz
> +- broken, rel. down to 0.1
> +
>  Revision 1.76  2005/08/03 08:53:52  aflinta
>  - up to version 0.11.14

If you elaborate what it is that you find broken, there's a chance that
someone will fix it.

-- 
Pawe? Sakowski <saq at pld-linux.org>
PLD Linux Distribution



From freetz at gmx.net  Wed Aug  3 18:03:15 2005
From: freetz at gmx.net (Fryderyk Dziarmagowski)
Date: Wed, 3 Aug 2005 18:03:15 +0200
Subject: SPECS: vte.spec - broken, rel. down to 0.1
In-Reply-To: <1123081653.5438.11.camel@neptune.sakowski.pl>
References: <SPECS_vte.spec.1.76@pld-linux.org>
	<SPECS_vte.spec.1.77@pld-linux.org>
	<1123081653.5438.11.camel@neptune.sakowski.pl>
Message-ID: <20050803180315.56be8c82.freetz@gmx.net>

 --- Pawe? Sakowski <saq at pld-linux.org> wrote:

> On Wed, 2005-08-03 at 16:19 +0200, freetz wrote:
> >  $Log$
> > +Revision 1.77  2005/08/03 14:19:04  freetz
> > +- broken, rel. down to 0.1
> > +
> >  Revision 1.76  2005/08/03 08:53:52  aflinta
> >  - up to version 0.11.14
> 
> If you elaborate what it is that you find broken, there's a chance that
> someone will fix it.

sending a problem description to authors it's not sufficient? should I
cc you with every problem I've found? and I don't belive that "someone"
will fix it. chances are very, very small (as usual).

-- 
Fryderyk Dziarmagowski


From wolf.pld at gmail.com  Wed Aug  3 18:14:14 2005
From: wolf.pld at gmail.com (Bartosz Taudul)
Date: Wed, 3 Aug 2005 18:14:14 +0200
Subject: SPECS: vte.spec - broken, rel. down to 0.1
In-Reply-To: <20050803180315.56be8c82.freetz@gmx.net>
References: <SPECS_vte.spec.1.76@pld-linux.org>
	<SPECS_vte.spec.1.77@pld-linux.org>
	<1123081653.5438.11.camel@neptune.sakowski.pl>
	<20050803180315.56be8c82.freetz@gmx.net>
Message-ID: <20050803161414.GA25045@bajzel>

On Wed, Aug 03, 2005 at 06:03:15PM +0200, Fryderyk Dziarmagowski wrote:
> > > +Revision 1.77  2005/08/03 14:19:04  freetz
> > > +- broken, rel. down to 0.1
> > If you elaborate what it is that you find broken, there's a chance that
> > someone will fix it.
> sending a problem description to authors it's not sufficient? should I
In case you didn't noticed, you commited into PLD cvs, not vte author's
one.

wolf
-- 
  Bartek   .  - Pami?tajmy, ?e ?ciany maj? uszy, a czasami uszy s? ko?o drzwi.
  Taudul   :  
          .:....................................................................
w o l f @ p l d - l i n u x . o r g            .:. http://wolf.valkyrie.one.pl/


From wrobell at pld-linux.org  Wed Aug  3 18:20:16 2005
From: wrobell at pld-linux.org (wrobell)
Date: Wed, 03 Aug 2005 17:20:16 +0100
Subject: SPECS: vte.spec - broken, rel. down to 0.1
In-Reply-To: <20050803180315.56be8c82.freetz@gmx.net>
References: <SPECS_vte.spec.1.76@pld-linux.org>
	<SPECS_vte.spec.1.77@pld-linux.org>
	<1123081653.5438.11.camel@neptune.sakowski.pl>
	<20050803180315.56be8c82.freetz@gmx.net>
Message-ID: <1123086016.32751.74.camel@RECENT-CONVERT>

On Wed, 2005-08-03 at 18:03 +0200, Fryderyk Dziarmagowski wrote:
>  --- Pawe? Sakowski <saq at pld-linux.org> wrote:
> 
> > On Wed, 2005-08-03 at 16:19 +0200, freetz wrote:
> > >  $Log$
> > > +Revision 1.77  2005/08/03 14:19:04  freetz
> > > +- broken, rel. down to 0.1
> > > +
> > >  Revision 1.76  2005/08/03 08:53:52  aflinta
> > >  - up to version 0.11.14
> > 
> > If you elaborate what it is that you find broken, there's a chance that
> > someone will fix it.
> 
> sending a problem description to authors it's not sufficient? should I
> cc you with every problem I've found? and I don't belive that "someone"
> will fix it. chances are very, very small (as usual).

still we don't know what the problem is. maybe we should downgrade?
so... what's the problem?

   wrobell <wrobell at pld-linux.org>



From freetz at gmx.net  Wed Aug  3 18:45:59 2005
From: freetz at gmx.net (Fryderyk Dziarmagowski)
Date: Wed, 3 Aug 2005 18:45:59 +0200
Subject: SPECS: vte.spec - broken, rel. down to 0.1
In-Reply-To: <20050803161414.GA25045@bajzel>
References: <SPECS_vte.spec.1.76@pld-linux.org>
	<SPECS_vte.spec.1.77@pld-linux.org>
	<1123081653.5438.11.camel@neptune.sakowski.pl>
	<20050803180315.56be8c82.freetz@gmx.net>
	<20050803161414.GA25045@bajzel>
Message-ID: <20050803184559.721710bf.freetz@gmx.net>

 --- Bartosz Taudul <wolf.pld at gmail.com> wrote:

> > > > +Revision 1.77  2005/08/03 14:19:04  freetz
> > > > +- broken, rel. down to 0.1
> > > If you elaborate what it is that you find broken, there's a chance that
> > > someone will fix it.
> > sending a problem description to authors it's not sufficient? should I
> In case you didn't noticed, you commited into PLD cvs, not vte author's
> one.

don't like my commits? feel free to report a abuse to PLD CDG.

-- 
Fryderyk Dziarmagowski


From freetz at gmx.net  Wed Aug  3 18:48:08 2005
From: freetz at gmx.net (Fryderyk Dziarmagowski)
Date: Wed, 3 Aug 2005 18:48:08 +0200
Subject: SPECS: vte.spec - broken, rel. down to 0.1
In-Reply-To: <1123086016.32751.74.camel@RECENT-CONVERT>
References: <SPECS_vte.spec.1.76@pld-linux.org>
	<SPECS_vte.spec.1.77@pld-linux.org>
	<1123081653.5438.11.camel@neptune.sakowski.pl>
	<20050803180315.56be8c82.freetz@gmx.net>
	<1123086016.32751.74.camel@RECENT-CONVERT>
Message-ID: <20050803184808.5472a014.freetz@gmx.net>

 --- wrobell <wrobell at pld-linux.org> wrote:

> > > > +Revision 1.77  2005/08/03 14:19:04  freetz
> > > > +- broken, rel. down to 0.1
> > > > +
> > > >  Revision 1.76  2005/08/03 08:53:52  aflinta
> > > >  - up to version 0.11.14
> > > 
> > > If you elaborate what it is that you find broken, there's a chance that
> > > someone will fix it.
> > 
> > sending a problem description to authors it's not sufficient? should I
> > cc you with every problem I've found? and I don't belive that "someone"
> > will fix it. chances are very, very small (as usual).
> 
> still we don't know what the problem is. maybe we should downgrade?

in case you're using glib2-2.6.x the answer is no.

> so... what's the problem?

it's already fixed.

-- 
Fryderyk Dziarmagowski


From wrobell at pld-linux.org  Wed Aug  3 18:52:14 2005
From: wrobell at pld-linux.org (wrobell)
Date: Wed, 03 Aug 2005 17:52:14 +0100
Subject: SPECS: vte.spec - broken, rel. down to 0.1
In-Reply-To: <20050803184559.721710bf.freetz@gmx.net>
References: <SPECS_vte.spec.1.76@pld-linux.org>
	<SPECS_vte.spec.1.77@pld-linux.org>
	<1123081653.5438.11.camel@neptune.sakowski.pl>
	<20050803180315.56be8c82.freetz@gmx.net>
	<20050803161414.GA25045@bajzel>
	<20050803184559.721710bf.freetz@gmx.net>
Message-ID: <1123087934.32751.77.camel@RECENT-CONVERT>

On Wed, 2005-08-03 at 18:45 +0200, Fryderyk Dziarmagowski wrote:
>  --- Bartosz Taudul <wolf.pld at gmail.com> wrote:
> 
> > > > > +Revision 1.77  2005/08/03 14:19:04  freetz
> > > > > +- broken, rel. down to 0.1
> > > > If you elaborate what it is that you find broken, there's a chance that
> > > > someone will fix it.
> > > sending a problem description to authors it's not sufficient? should I
> > In case you didn't noticed, you commited into PLD cvs, not vte author's
> > one.
> 
> don't like my commits? feel free to report a abuse to PLD CDG.

come on.. fuck the system. we just want to know the problem :)

    wrobell <wrobell at pld-linux.org>



From wolf.pld at gmail.com  Wed Aug  3 18:56:45 2005
From: wolf.pld at gmail.com (Bartosz Taudul)
Date: Wed, 3 Aug 2005 18:56:45 +0200
Subject: SPECS: vte.spec - broken, rel. down to 0.1
In-Reply-To: <20050803184559.721710bf.freetz@gmx.net>
References: <SPECS_vte.spec.1.76@pld-linux.org>
	<SPECS_vte.spec.1.77@pld-linux.org>
	<1123081653.5438.11.camel@neptune.sakowski.pl>
	<20050803180315.56be8c82.freetz@gmx.net>
	<20050803161414.GA25045@bajzel>
	<20050803184559.721710bf.freetz@gmx.net>
Message-ID: <20050803165645.GA26551@bajzel>

On Wed, Aug 03, 2005 at 06:45:59PM +0200, Fryderyk Dziarmagowski wrote:
> don't like my commits? feel free to report a abuse to PLD CDG.
Not yet.

wolf
-- 
  Bartek   .  - B?dzie was obowi?zywa?o (...) Nie na jutro bro? bo?e, tylko
  Taudul   :    na pojutrze.
          .:....................................................................
w o l f @ p l d - l i n u x . o r g            .:. http://wolf.valkyrie.one.pl/


From saq at pld-linux.org  Thu Aug  4 11:05:24 2005
From: saq at pld-linux.org (=?iso-8859-2?Q?Pawe=B3?= Sakowski)
Date: Thu, 04 Aug 2005 11:05:24 +0200
Subject: SPECS: vte.spec - broken, rel. down to 0.1
In-Reply-To: <20050803180315.56be8c82.freetz@gmx.net>
References: <SPECS_vte.spec.1.76@pld-linux.org>
	<SPECS_vte.spec.1.77@pld-linux.org>
	<1123081653.5438.11.camel@neptune.sakowski.pl>
	<20050803180315.56be8c82.freetz@gmx.net>
Message-ID: <1123146324.13648.6.camel@neptune.sakowski.pl>

On Wed, 2005-08-03 at 18:03 +0200, Fryderyk Dziarmagowski wrote:
> > If you elaborate what it is that you find broken, there's a chance that
> > someone will fix it.
> 
> sending a problem description to authors it's not sufficient? should I
> cc you with every problem I've found? and I don't belive that "someone"
> will fix it. chances are very, very small (as usual).

One of "previous commiter screwed up the upgrade", "doesn't build",
"this version crashes" in the commit log would have made me happy.

-- 
Pawe? Sakowski <saq at pld-linux.org>
PLD Linux Distribution



From aflinta at at.kernel.pl  Thu Aug  4 11:23:51 2005
From: aflinta at at.kernel.pl (Artur Flinta)
Date: Thu, 04 Aug 2005 11:23:51 +0200
Subject: SPECS: vte.spec - broken, rel. down to 0.1
In-Reply-To: <1123146324.13648.6.camel@neptune.sakowski.pl>
References: <SPECS_vte.spec.1.76@pld-linux.org>
	<SPECS_vte.spec.1.77@pld-linux.org>
	<1123081653.5438.11.camel@neptune.sakowski.pl>
	<20050803180315.56be8c82.freetz@gmx.net>
	<1123146324.13648.6.camel@neptune.sakowski.pl>
Message-ID: <1123147431.24549.30.camel@localhost>

Dnia 04-08-2005, czw o godzinie 11:05 +0200, Pawe? Sakowski napisa?(a):

> One of "previous commiter screwed up the upgrade", "doesn't build",
> "this version crashes" in the commit log would have made me happy.

But glib was broken, not vte.

Artur

-- 
Ka?dy problem ma swoje rozwi?zanie, 
je?eli nie ma rozwi?zania to nie ma problemu.



From tomasz at grobelny.oswiecenia.net  Sat Aug  6 17:23:50 2005
From: tomasz at grobelny.oswiecenia.net (Tomasz Grobelny)
Date: Sat, 6 Aug 2005 17:23:50 +0200
Subject: passwdgen
In-Reply-To: <52799c7005080304062128136d@mail.gmail.com>
References: <52799c7005080304062128136d@mail.gmail.com>
Message-ID: <200508061723.50942.tomasz@grobelny.oswiecenia.net>

Dnia ?roda 03 sierpnia 2005 13:06, maHo napisa?:
> Hello
>
> #v+
> $ passwdgen -1p@ --min=4 --max=6
> #v-
>
> and it hangs.
>
Because it uses /dev/random which is not very efficient (see strace). Would it 
be correct to use /dev/urandom? Does it contain the same amount of entropy or 
is it somehow simpler (and possibly less secure)?
-- 
Regards,
Tomasz Grobelny


From michal.moskal at gmail.com  Sat Aug  6 17:50:44 2005
From: michal.moskal at gmail.com (Michal Moskal)
Date: Sat, 6 Aug 2005 17:50:44 +0200
Subject: passwdgen
In-Reply-To: <200508061723.50942.tomasz@grobelny.oswiecenia.net>
References: <52799c7005080304062128136d@mail.gmail.com>
	<200508061723.50942.tomasz@grobelny.oswiecenia.net>
Message-ID: <b323bb98050806085035c7e80e@mail.gmail.com>

On 8/6/05, Tomasz Grobelny <tomasz at grobelny.oswiecenia.net> wrote:
> Dnia \u015broda 03 sierpnia 2005 13:06, maHo wrote:
> > Hello
> >
> > #v+
> > $ passwdgen -1p@ --min=4 --max=6
> > #v-
> >
> > and it hangs.
> >
> Because it uses /dev/random which is not very efficient (see strace). Would it
> be correct to use /dev/urandom? Does it contain the same amount of entropy or
> is it somehow simpler (and possibly less secure)?

It depends on how paranoid you are. If you believe NSA, FSB or some
other kind of highly intelligent aliens are going to reverse SHA-1, so
they can guess next password based of the previous one then you should
definitely use /dev/random. OTOH if you believe it you should be also
aware they could be controlling you from space using one of these 
satellites...

/dev/random makes sure it doesn't leak more entropy than it gets, so it
is impossible to guess anything without knowing the entropy (sic!). Which
isn't entropy anyway, so CIA/KGB/etc can intercept it.

-- 
   Michal Moskal,
   http://nemerle.org/~malekith/


From tomasz at grobelny.oswiecenia.net  Sat Aug  6 18:42:28 2005
From: tomasz at grobelny.oswiecenia.net (Tomasz Grobelny)
Date: Sat, 6 Aug 2005 18:42:28 +0200
Subject: passwdgen
In-Reply-To: <b323bb98050806085035c7e80e@mail.gmail.com>
References: <52799c7005080304062128136d@mail.gmail.com>
	<200508061723.50942.tomasz@grobelny.oswiecenia.net>
	<b323bb98050806085035c7e80e@mail.gmail.com>
Message-ID: <200508061842.30239.tomasz@grobelny.oswiecenia.net>

Dnia sobota 06 sierpnia 2005 17:50, Michal Moskal napisa?:
> On 8/6/05, Tomasz Grobelny <tomasz at grobelny.oswiecenia.net> wrote:
> > Dnia \u015broda 03 sierpnia 2005 13:06, maHo wrote:
> > > Hello
> > >
> > > #v+
> > > $ passwdgen -1p@ --min=4 --max=6
> > > #v-
> > >
> > > and it hangs.
> >
> > Because it uses /dev/random which is not very efficient (see strace).
> > Would it be correct to use /dev/urandom? Does it contain the same amount
> > of entropy or is it somehow simpler (and possibly less secure)?
>
> It depends on how paranoid you are. If you believe NSA, FSB or some
> other kind of highly intelligent aliens are going to reverse SHA-1, so
> they can guess next password based of the previous one then you should
> definitely use /dev/random. OTOH if you believe it you should be also
Ok, but would you trust a password generator that is based on rand function 
from glibc (which in turn returns values based only on system time)? If 
somebody knew you use this password generator he would have to check only 
several hundred thousands passwords to hit the right one. That would be a 
major security flaw.
Thus the questions are:
1. How secure is /dev/urandom? Is is closer to /dev/random or to rand()?
2. Should (according to specs) /dev/random be more secure than /dev/urandom?
3. If /dev/urandom is supposed to be less secure but it is secure enough (in 
current kernel implementation) should passwdgen use it? Yes, because it 
works. No, because it could be insecure if kernel behaviour changes. Other 
opinions?

> aware they could be controlling you from space using one of these
> satellites...
>
:D

-- 
Regards,
Tomasz Grobelny


From michal.moskal at gmail.com  Sat Aug  6 18:49:16 2005
From: michal.moskal at gmail.com (Michal Moskal)
Date: Sat, 6 Aug 2005 18:49:16 +0200
Subject: passwdgen
In-Reply-To: <200508061842.30239.tomasz@grobelny.oswiecenia.net>
References: <52799c7005080304062128136d@mail.gmail.com>
	<200508061723.50942.tomasz@grobelny.oswiecenia.net>
	<b323bb98050806085035c7e80e@mail.gmail.com>
	<200508061842.30239.tomasz@grobelny.oswiecenia.net>
Message-ID: <b323bb9805080609497247c11a@mail.gmail.com>

On 8/6/05, Tomasz Grobelny <tomasz at grobelny.oswiecenia.net> wrote:
> Dnia sobota 06 sierpnia 2005 17:50, Michal Moskal napisa\u0142:
> > On 8/6/05, Tomasz Grobelny <tomasz at grobelny.oswiecenia.net> wrote:
> > > Dnia \u015broda 03 sierpnia 2005 13:06, maHo wrote:
> > > > Hello
> > > >
> > > > #v+
> > > > $ passwdgen -1p@ --min=4 --max=6
> > > > #v-
> > > >
> > > > and it hangs.
> > >
> > > Because it uses /dev/random which is not very efficient (see strace).
> > > Would it be correct to use /dev/urandom? Does it contain the same amount
> > > of entropy or is it somehow simpler (and possibly less secure)?
> >
> > It depends on how paranoid you are. If you believe NSA, FSB or some
> > other kind of highly intelligent aliens are going to reverse SHA-1, so
> > they can guess next password based of the previous one then you should
> > definitely use /dev/random. OTOH if you believe it you should be also
> Ok, but would you trust a password generator that is based on rand function
> from glibc (which in turn returns values based only on system time)? If
> somebody knew you use this password generator he would have to check only
> several hundred thousands passwords to hit the right one. That would be a
> major security flaw.
> Thus the questions are:
> 1. How secure is /dev/urandom? Is is closer to /dev/random or to rand()?

It's far closer to /dev/random.

In the second paragraph I explained it -- /dev/urandom is the same as
/dev/random except it doesn't enforce that you read only as much as
you (well, the kernel) write to it. So if it lacks new random data, it
will generate it based on what's in the pool.

> 2. Should (according to specs) /dev/random be more secure than /dev/urandom?

Yes, because it doesn't require SHA-1 function to be irreversible. This
is however quite a good assumption.

> 3. If /dev/urandom is supposed to be less secure but it is secure enough (in
> current kernel implementation) should passwdgen use it? Yes, because it
> works. No, because it could be insecure if kernel behaviour changes. Other
> opinions?

It cannot change to be less secure. It's part of the kernel API.

-- 
   Michal Moskal,
   http://nemerle.org/~malekith/


From tomasz at grobelny.oswiecenia.net  Sat Aug  6 19:05:57 2005
From: tomasz at grobelny.oswiecenia.net (Tomasz Grobelny)
Date: Sat, 6 Aug 2005 19:05:57 +0200
Subject: passwdgen
In-Reply-To: <b323bb9805080609497247c11a@mail.gmail.com>
References: <52799c7005080304062128136d@mail.gmail.com>
	<200508061842.30239.tomasz@grobelny.oswiecenia.net>
	<b323bb9805080609497247c11a@mail.gmail.com>
Message-ID: <200508061905.58564.tomasz@grobelny.oswiecenia.net>

Dnia sobota 06 sierpnia 2005 18:49, Michal Moskal napisa?:
> On 8/6/05, Tomasz Grobelny <tomasz at grobelny.oswiecenia.net> wrote:
> > 1. How secure is /dev/urandom? Is is closer to /dev/random or to rand()?
>
> It's far closer to /dev/random.
>
> In the second paragraph I explained it -- /dev/urandom is the same as
> /dev/random except it doesn't enforce that you read only as much as
> you (well, the kernel) write to it. So if it lacks new random data, it
> will generate it based on what's in the pool.
>
So it is hard enough to predict data that was read from /dev/urandom in the 
past? If so, maybe a patch for passwdgen to use /dev/urandom should be 
created?

> > 3. If /dev/urandom is supposed to be less secure but it is secure enough
> > (in current kernel implementation) should passwdgen use it? Yes, because
> > it works. No, because it could be insecure if kernel behaviour changes.
> > Other opinions?
>
> It cannot change to be less secure. It's part of the kernel API.
Does the API define how data coming from /dev/urandom is generated?
-- 
Regards,
Tomasz Grobelny


From michal.moskal at gmail.com  Sat Aug  6 19:26:12 2005
From: michal.moskal at gmail.com (Michal Moskal)
Date: Sat, 6 Aug 2005 19:26:12 +0200
Subject: passwdgen
In-Reply-To: <200508061905.58564.tomasz@grobelny.oswiecenia.net>
References: <52799c7005080304062128136d@mail.gmail.com>
	<200508061842.30239.tomasz@grobelny.oswiecenia.net>
	<b323bb9805080609497247c11a@mail.gmail.com>
	<200508061905.58564.tomasz@grobelny.oswiecenia.net>
Message-ID: <b323bb98050806102656b3ab13@mail.gmail.com>

On 8/6/05, Tomasz Grobelny <tomasz at grobelny.oswiecenia.net> wrote:
> Dnia sobota 06 sierpnia 2005 18:49, Michal Moskal napisa?:
> > On 8/6/05, Tomasz Grobelny <tomasz at grobelny.oswiecenia.net> wrote:
> > > 1. How secure is /dev/urandom? Is is closer to /dev/random or to rand()?
> >
> > It's far closer to /dev/random.
> >
> > In the second paragraph I explained it -- /dev/urandom is the same as
> > /dev/random except it doesn't enforce that you read only as much as
> > you (well, the kernel) write to it. So if it lacks new random data, it
> > will generate it based on what's in the pool.
> >
> So it is hard enough to predict data that was read from /dev/urandom in the
> past? 

I would say so. But maybe I'm not paranoid ENOUGH.

> If so, maybe a patch for passwdgen to use /dev/urandom should be
> created?

Maybe a flag?

> > > 3. If /dev/urandom is supposed to be less secure but it is secure enough
> > > (in current kernel implementation) should passwdgen use it? Yes, because
> > > it works. No, because it could be insecure if kernel behaviour changes.
> > > Other opinions?
> >
> > It cannot change to be less secure. It's part of the kernel API.
> Does the API define how data coming from /dev/urandom is generated?

man urandom:

       When  read,  /dev/urandom  device  will  return  as  many  bytes as are
       requested.  As a result, if there is  not  sufficient  entropy  in  the
       entropy  pool,  the  returned  values are theoretically vulnerable to a
       cryptographic attack on the algorithms used by the  driver.   Knowledge
       of how to do this is not available in the current non-classified liter-
       ature, but it is theoretically possible that such an attack may  exist.
       If this is a concern in your application, use /dev/random instead.

-- 
   Michal Moskal,
   http://nemerle.org/~malekith/

From tomasz at grobelny.oswiecenia.net  Sat Aug  6 19:57:37 2005
From: tomasz at grobelny.oswiecenia.net (Tomasz Grobelny)
Date: Sat, 6 Aug 2005 19:57:37 +0200
Subject: passwdgen
In-Reply-To: <b323bb98050806102656b3ab13@mail.gmail.com>
References: <52799c7005080304062128136d@mail.gmail.com>
	<200508061905.58564.tomasz@grobelny.oswiecenia.net>
	<b323bb98050806102656b3ab13@mail.gmail.com>
Message-ID: <200508061957.41700.tomasz@grobelny.oswiecenia.net>

Dnia sobota 06 sierpnia 2005 19:26, Michal Moskal napisa?:
> On 8/6/05, Tomasz Grobelny <tomasz at grobelny.oswiecenia.net> wrote:
> > Dnia sobota 06 sierpnia 2005 18:49, Michal Moskal napisa?:
> > > On 8/6/05, Tomasz Grobelny <tomasz at grobelny.oswiecenia.net> wrote:
> > > > 1. How secure is /dev/urandom? Is is closer to /dev/random or to
> > > > rand()?
> > >
> > > It's far closer to /dev/random.
> > >
> > > In the second paragraph I explained it -- /dev/urandom is the same as
> > > /dev/random except it doesn't enforce that you read only as much as
> > > you (well, the kernel) write to it. So if it lacks new random data, it
> > > will generate it based on what's in the pool.
> >
> > So it is hard enough to predict data that was read from /dev/urandom in
> > the past?
>
> I would say so. But maybe I'm not paranoid ENOUGH.
>
Other opinions?

> > If so, maybe a patch for passwdgen to use /dev/urandom should be
> > created?
>
> Maybe a flag?
>
System wide? Or command line switch?

> > > > 3. If /dev/urandom is supposed to be less secure but it is secure
> > > > enough (in current kernel implementation) should passwdgen use it?
> > > > Yes, because it works. No, because it could be insecure if kernel
> > > > behaviour changes. Other opinions?
> > >
> > > It cannot change to be less secure. It's part of the kernel API.
> >
> > Does the API define how data coming from /dev/urandom is generated?
>
> man urandom:
>
>        When  read,  /dev/urandom  device  will  return  as  many  bytes as
> are requested.  As a result, if there is  not  sufficient  entropy  in  the
> entropy  pool,  the  returned  values are theoretically vulnerable to a
> cryptographic attack on the algorithms used by the  driver.   Knowledge of
> how to do this is not available in the current non-classified liter- ature,
> but it is theoretically possible that such an attack may  exist. If this is
> a concern in your application, use /dev/random instead.
But it doesn't say how data is generated. It just says that in some 
circumstances it may be of lower security. But still we don't know how often 
it can happen, how much lower the security will be and so on. It is up to 
implementation, not API.
Another question is: does /dev/random have to be so slow? Are any patches 
applied to it's code in PLD kernel that could slow it down? It's just I don't 
believe that author of passwdgen wrote a program that needs hours to produce 
a 10 character password on average system...
-- 
Regards,
Tomasz Grobelny


From loc at toya.net.pl  Sat Aug  6 21:21:07 2005
From: loc at toya.net.pl (=?UTF-8?B?SmFrdWIgUGlvdHIgQ8WCYXBh?=)
Date: Sat, 06 Aug 2005 21:21:07 +0200
Subject: passwdgen
In-Reply-To: <200508061957.41700.tomasz@grobelny.oswiecenia.net>
References: <52799c7005080304062128136d@mail.gmail.com>	<200508061905.58564.tomasz@grobelny.oswiecenia.net>	<b323bb98050806102656b3ab13@mail.gmail.com>
	<200508061957.41700.tomasz@grobelny.oswiecenia.net>
Message-ID: <42F50DA3.1000705@toya.net.pl>

Tomasz Grobelny wrote:
> Dnia sobota 06 sierpnia 2005 19:26, Michal Moskal napisa?:
> 
>>On 8/6/05, Tomasz Grobelny <tomasz at grobelny.oswiecenia.net> wrote:
>>
>>>Dnia sobota 06 sierpnia 2005 18:49, Michal Moskal napisa?:
>>>
>>>>On 8/6/05, Tomasz Grobelny <tomasz at grobelny.oswiecenia.net> wrote:
>>>>
>>>>>3. If /dev/urandom is supposed to be less secure but it is secure
>>>>>enough (in current kernel implementation) should passwdgen use it?
>>>>>Yes, because it works. No, because it could be insecure if kernel
>>>>>behaviour changes. Other opinions?
>>>>
>>>>It cannot change to be less secure. It's part of the kernel API.
>>>
>>>Does the API define how data coming from /dev/urandom is generated?
>>
>>man urandom:
>>
>>       When  read,  /dev/urandom  device  will  return  as  many  bytes as
>>are requested.  As a result, if there is  not  sufficient  entropy  in  the
>>entropy  pool,  the  returned  values are theoretically vulnerable to a
>>cryptographic attack on the algorithms used by the  driver.   Knowledge of
>>how to do this is not available in the current non-classified liter- ature,
>>but it is theoretically possible that such an attack may  exist. If this is
>>a concern in your application, use /dev/random instead.
> 
> But it doesn't say how data is generated. It just says that in some 
> circumstances it may be of lower security. But still we don't know how often 
> it can happen, how much lower the security will be and so on. It is up to 
> implementation, not API.
> Another question is: does /dev/random have to be so slow? Are any patches 
> applied to it's code in PLD kernel that could slow it down? It's just I don't 
> believe that author of passwdgen wrote a program that needs hours to produce 
> a 10 character password on average system...

You can feed it and it will produce much more. Generating entropy based 
only on normal computer usage is not so easy.

There were two programs which could feed the kernel with entropy from a 
v4l source or from a soundcard maybe try these?...

-- 
Regards,
Jakub Piotr C?apa


From jajcus at bnet.pl  Sun Aug  7 10:56:19 2005
From: jajcus at bnet.pl (Jacek Konieczny)
Date: Sun, 7 Aug 2005 10:56:19 +0200
Subject: passwdgen
In-Reply-To: <42F50DA3.1000705@toya.net.pl>
References: <52799c7005080304062128136d@mail.gmail.com>
	<200508061905.58564.tomasz@grobelny.oswiecenia.net>
	<b323bb98050806102656b3ab13@mail.gmail.com>
	<200508061957.41700.tomasz@grobelny.oswiecenia.net>
	<42F50DA3.1000705@toya.net.pl>
Message-ID: <20050807085619.GA23577@nic.nigdzie>

On Sat, Aug 06, 2005 at 09:21:07PM +0200, Jakub Piotr C?apa wrote:
> > Another question is: does /dev/random have to be so slow? Are any patches 
> > applied to it's code in PLD kernel that could slow it down? It's just I don't 
> > believe that author of passwdgen wrote a program that needs hours to produce 
> > a 10 character password on average system...
> 
> You can feed it and it will produce much more. Generating entropy based 
> only on normal computer usage is not so easy.
> 
> There were two programs which could feed the kernel with entropy from a 
> v4l source or from a soundcard maybe try these?...

Some of modern computer systems (including modern PC machines) have
integrated hardware entropy sources. Unfortunately those drivers don't
add the entropy to /dev/random, but provide other device. When I tried
/dev/amd768_rng on my server, lacking entropy and running 2.4.x kernel,
I found out, that its interface is slightly incompatible with
/dev/random, so some applications worked with that and some did not. And
the kernel internals (like "random" match of netfilter) did not get the
entropy either.

In 2.6 kernel there is a generic /dev/hwrandom device for all of the
drivers, but it doesn't seem to be connected with /dev/random either.

Greets,
        Jacek


From lukaszmach at gmail.com  Sun Aug  7 12:42:19 2005
From: lukaszmach at gmail.com (maHo)
Date: Sun, 7 Aug 2005 12:42:19 +0200
Subject: passwdgen
In-Reply-To: <20050807085619.GA23577@nic.nigdzie>
References: <52799c7005080304062128136d@mail.gmail.com>
	<200508061905.58564.tomasz@grobelny.oswiecenia.net>
	<b323bb98050806102656b3ab13@mail.gmail.com>
	<200508061957.41700.tomasz@grobelny.oswiecenia.net>
	<42F50DA3.1000705@toya.net.pl> <20050807085619.GA23577@nic.nigdzie>
Message-ID: <52799c700508070342fbb9423@mail.gmail.com>

On 8/7/05, Jacek Konieczny <jajcus at bnet.pl> wrote:
[ciach]

So, what should I do to use passwdgen (I don't understand that
enthropy things in our discussion). Should I feed /dev/random with
some data? (cat somefile >/dev/random ?) or should I use another
password generator?

regards

maHo


From loc at toya.net.pl  Sun Aug  7 12:48:18 2005
From: loc at toya.net.pl (=?UTF-8?B?SmFrdWIgUGlvdHIgQ8WCYXBh?=)
Date: Sun, 07 Aug 2005 12:48:18 +0200
Subject: passwdgen
In-Reply-To: <20050807085619.GA23577@nic.nigdzie>
References: <52799c7005080304062128136d@mail.gmail.com>	<200508061905.58564.tomasz@grobelny.oswiecenia.net>	<b323bb98050806102656b3ab13@mail.gmail.com>	<200508061957.41700.tomasz@grobelny.oswiecenia.net>	<42F50DA3.1000705@toya.net.pl>
	<20050807085619.GA23577@nic.nigdzie>
Message-ID: <42F5E6F2.1020908@toya.net.pl>

Jacek Konieczny wrote:
> On Sat, Aug 06, 2005 at 09:21:07PM +0200, Jakub Piotr C?apa wrote:
> 
>>>Another question is: does /dev/random have to be so slow? Are any patches 
>>>applied to it's code in PLD kernel that could slow it down? It's just I don't 
>>>believe that author of passwdgen wrote a program that needs hours to produce 
>>>a 10 character password on average system...
>>
>>You can feed it and it will produce much more. Generating entropy based 
>>only on normal computer usage is not so easy.
>>
>>There were two programs which could feed the kernel with entropy from a 
>>v4l source or from a soundcard maybe try these?...
> 
> 
> Some of modern computer systems (including modern PC machines) have
> integrated hardware entropy sources. Unfortunately those drivers don't
> add the entropy to /dev/random, but provide other device.

And maybe you could cat this data into /dev/random?

-- 
Regards,
Jakub Piotr C?apa


From adamg at biomerieux.pl  Sun Aug  7 15:15:26 2005
From: adamg at biomerieux.pl (Adam =?iso-8859-2?Q?Go=B3=EAbiowski?=)
Date: Sun, 7 Aug 2005 15:15:26 +0200
Subject: passwdgen
In-Reply-To: <52799c700508070342fbb9423@mail.gmail.com>
References: <52799c7005080304062128136d@mail.gmail.com>
	<200508061905.58564.tomasz@grobelny.oswiecenia.net>
	<b323bb98050806102656b3ab13@mail.gmail.com>
	<200508061957.41700.tomasz@grobelny.oswiecenia.net>
	<42F50DA3.1000705@toya.net.pl> <20050807085619.GA23577@nic.nigdzie>
	<52799c700508070342fbb9423@mail.gmail.com>
Message-ID: <20050807131526.GA6191@mysza.eu.org>

On Sun, Aug 07, 2005 at 12:42:19PM +0200, maHo wrote:
> On 8/7/05, Jacek Konieczny <jajcus at bnet.pl> wrote:
> [ciach]
> 
> So, what should I do to use passwdgen (I don't understand that
> enthropy things in our discussion). Should I feed /dev/random with
> some data? (cat somefile >/dev/random ?) 

> or should I use another password generator?

For all those who are not paranoid enough (including me) - passwdgen-2.2-4
(should be available on your favourite ftp mirror soon) was patched to
allow usage of /dev/urandom instead of /dev/random. Just use -u switch:

$ time ./passwdgen -u -a
Your password is: dumuoix

real    0m0.011s
user    0m0.005s
sys     0m0.006s
$

-- 
http://www.mysza.eu.org/ | Everybody needs someone sure, someone true,
   PLD Linux developer   | Everybody needs some solid rock, I know I do.


From glen at delfi.ee  Mon Aug  8 11:45:13 2005
From: glen at delfi.ee (Elan =?iso-8859-2?q?Ruusam=E4e?=)
Date: Mon, 8 Aug 2005 12:45:13 +0300
Subject: SPECS: openclipart.spec - up to 0.16;
	drop almost all (why it was ...
In-Reply-To: <SPECS_openclipart.spec.1.4@pld-linux.org>
References: <SPECS_openclipart.spec.1.3@pld-linux.org>
	<SPECS_openclipart.spec.1.4@pld-linux.org>
Message-ID: <200508081245.13857.glen@delfi.ee>

shouldn't you obsolete the dropped packages?

On Monday 08 August 2005 01:12, arekm wrote:
> Author: arekm                        Date: Sun Aug  7 22:12:48 2005 GMT
> Module: SPECS                         Tag: HEAD
> ---- Log message:
> - up to 0.16; drop almost all (why it was splitted at all?) subpackages
>
> ---- Files affected:
> SPECS:
>    openclipart.spec (1.3 -> 1.4)
>
> ---- Diffs:
>
> ================================================================
> Index: SPECS/openclipart.spec
> diff -u SPECS/openclipart.spec:1.3 SPECS/openclipart.spec:1.4
> --- SPECS/openclipart.spec:1.3	Sun Feb 27 19:11:22 2005
> +++ SPECS/openclipart.spec	Mon Aug  8 00:12:42 2005
> @@ -2,15 +2,17 @@
>  Summary:	Archive of clip art that can be used for free for any use
>  Summary(pl):	Archiwum klipart?w, kt?re mo?na u?ywa? w dowolny spos?b za
> darmo Name:		openclipart
> -Version:	0.07
> +Version:	0.16
>  Release:	0.1
>  Epoch:		0
>  License:	Creative Commons and/or Public Domain
>  Group:		Applications/Graphics
> -Source0:	http://www.openclipart.org/downloads/%{name}-%{version}.tgz
> -# Source0-md5:  dd92d04305efc8bdb8f7f77219a05bdc
> +Source0:	http://www.openclipart.org/downloads/%{version}/%{name}-%{version
>}-full.tar.bz2 +# Source0-md5:	12ec606fa419f11c1d034ef3a4861fff
>  URL:		http://www.openclipart.org/
> +BuildRequires:	findutils
>  BuildArch:	noarch
> +Requires:       %{name}-AUTHORS = %{epoch}:%{version}-%{release}
>  BuildRoot:	%{tmpdir}/%{name}-%{version}-root-%(id -u -n)
>
>  %description
> @@ -20,9 +22,6 @@
>  Creative Commons. If you'd like to help out, please join the mailing
>  list. Also, browse the archives to review the project's history.
>
> -This package contains README and Examples files. For really clipart
> -please install openclipart-[type] package.
> -
>  %description -l pl
>  Celem tego projektu jest stworzenie archiwum klipart?w, kt?re mo?na
>  u?ywa? w dowolny spos?b za darmo. Wszystkie grafiki przekazane do
> @@ -31,976 +30,69 @@
>  powinien zapisa? si? na list?. Mo?e tak?e przejrze? archiwum, aby
>  pozna? histori? projektu.
>
> -Ten pakiet zawiera pliki README i Examples. W?a?ciwe kliparty znajduj?
> -si? w pakietach openclipart-[typ].
> -
>  %package AUTHORS
> -Summary:	Authors List of all cliparts
> -Summary(pl):	Lista autor?w wszystkich klipart?w
> -Group:		Applications/Graphics
> -Requires:	%{name} = %{epoch}:%{version}-%{release}
> +Summary:        Authors List of all cliparts
> +Summary(pl):    Lista autor?w wszystkich klipart?w
> +Group:          Applications/Graphics
>
>  %description AUTHORS
> -Authors List of all cliparts from all openclipart-* packages.
> +Authors List of all cliparts from all openclipart packages.
>
>  %description AUTHORS -l pl
> -Lista autor?w wszystkich klipart?w z pakiet?w openclipart-*.
> +Lista autor?w wszystkich klipart?w z pakiet?w openclipart.
>
> -%package MISC
> -Summary:	Misc cliparts
> -Summary(pl):	R??ne kliparty
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> +%package png
> +Summary:        PNG Openclipart
> +Summary(pl):    Kliparty w wersji PNG
> +Group:          Applications/Graphics
> +Requires:       %{name}-AUTHORS = %{epoch}:%{version}-%{release}
>
> -%description MISC
> -Clipart categories: activities africa america animal Animal appicon
> -apple aqua Aqua architecture armoiries arrow asia automobiles baby
> -bacon ball beach beverages bicycle Biohazard bird book bouquet bowl
> -breizh britain BSD building business button Button callout candy
> -cartoon celebrity celtic che chicken Chicken clipboard clock coffe
> -communication countires cute daemon decorations devices eagle ecus
> -education emblems entertainment envelope europe face fanart farm Farm
> -festive fish flag Flag flight flourish flower fly french friends fruit
> -Galette game geography geometry glass grape great GTP guevara
> -handshake hen Hen historic icon improvisedkeywordparse insect insects
> -interface ladybug library linux Linux logo Logo logos magnifying mail
> -mammal mammals man map maps mascot meat meeting money music musicsym
> -navigation nicu northamerica note oceania office openclipart park pear
> -penguin pig place plane plant postage presentation scissors Scotland
> -shape shapes sign slides smiley soccer Software soup sports stamp star
> -steaming study summer sun symbol tea technical telephone tools toy
> -toys transport transportation tux Tux usmail vase vgcats vietnam
> -warning water weather wildlife wine work
> -
> -%description MISC -l pl
> -Kategorie klipart?w: activities africa america animal Animal appicon
> -apple aqua Aqua architecture armoiries arrow asia automobiles baby
> -bacon ball beach beverages bicycle Biohazard bird book bouquet bowl
> -breizh britain BSD building business button Button callout candy
> -cartoon celebrity celtic che chicken Chicken clipboard clock coffe
> -communication countires cute daemon decorations devices eagle ecus
> -education emblems entertainment envelope europe face fanart farm Farm
> -festive fish flag Flag flight flourish flower fly french friends fruit
> -Galette game geography geometry glass grape great GTP guevara
> -handshake hen Hen historic icon improvisedkeywordparse insect insects
> -interface ladybug library linux Linux logo Logo logos magnifying mail
> -mammal mammals man map maps mascot meat meeting money music musicsym
> -navigation nicu northamerica note oceania office openclipart park pear
> -penguin pig place plane plant postage presentation scissors Scotland
> -shape shapes sign slides smiley soccer Software soup sports stamp star
> -steaming study summer sun symbol tea technical telephone tools toy
> -toys transport transportation tux Tux usmail vase vgcats vietnam
> -warning water weather wildlife wine work
> -
> -%package icons
> -Summary:	icons cliparts
> -Summary(pl):	Kliparty "icons"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description icons
> -74 cliparts from icons category.
> -
> -%description icons -l pl
> -74 klipart?w z kategorii "icons".
> -
> -%package people
> -Summary:	people cliparts
> -Summary(pl):	Kliparty "people"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description people
> -11 cliparts from people category.
> -
> -%description people -l pl
> -11 klipart?w z kategorii "people".
> -
> -%package ocal_logo
> -Summary:	ocal_logo cliparts
> -Summary(pl):	Kliparty "ocal_logo"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description ocal_logo
> -26 cliparts from ocal_logo category.
> -
> -%description ocal_logo -l pl
> -26 klipart?w z kategorii "ocal_logo".
> -
> -%package gradients
> -Summary:	gradients cliparts
> -Summary(pl):	Kliparty "gradients"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description gradients
> -118 cliparts from gradients category.
> -
> -%description gradients -l pl
> -118 klipart?w z kategorii "gradients".
> -
> -%package food
> -Summary:	food cliparts
> -Summary(pl):	Kliparty "food"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description food
> -19 cliparts from food category.
> -
> -%description food -l pl
> -19 klipart?w z kategorii "food".
> -
> -%package mime-types
> -Summary:	mime-types cliparts
> -Summary(pl):	Kliparty "mime-types"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description mime-types
> -22 cliparts from mime-types category.
> -
> -%description mime-types -l pl
> -22 klipart?w z kategorii "mime-types".
> -
> -%package actions
> -Summary:	actions cliparts
> -Summary(pl):	Kliparty "actions"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description actions
> -14 cliparts from actions category.
> -
> -%description actions -l pl
> -14 klipart?w z kategorii "actions".
> -
> -%package computer
> -Summary:	computer cliparts
> -Summary(pl):	Kliparty "computer"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description computer
> -81 cliparts from computer category.
> -
> -%description computer -l pl
> -81 klipart?w z kategorii "computer".
> -
> -%package filetype
> -Summary:	filetype cliparts
> -Summary(pl):	Kliparty "filetype"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description filetype
> -13 cliparts from filetype category.
> -
> -%description filetype -l pl
> -13 klipart?w z kategorii "filetype".
> -
> -%package homes
> -Summary:	homes cliparts
> -Summary(pl):	Kliparty "homes"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description homes
> -20 cliparts from homes category.
> -
> -%description homes -l pl
> -20 klipart?w z kategorii "homes".
> -
> -%package device
> -Summary:	device cliparts
> -Summary(pl):	Kliparty "device"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description device
> -30 cliparts from device category.
> -
> -%description device -l pl
> -30 klipart?w z kategorii "device".
> -
> -%package application
> -Summary:	application cliparts
> -Summary(pl):	Kliparty "application"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description application
> -278 cliparts from application category.
> -
> -%description application -l pl
> -278 klipart?w z kategorii "application".
> -
> -%package filesystems
> -Summary:	filesystems cliparts
> -Summary(pl):	Kliparty "filesystems"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description filesystems
> -10 cliparts from filesystems category.
> -
> -%description filesystems -l pl
> -10 klipart?w z kategorii "filesystems".
> -
> -%package action
> -Summary:	action cliparts
> -Summary(pl):	Kliparty "action"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description action
> -599 cliparts from action category.
> -
> -%description action -l pl
> -599 klipart?w z kategorii "action".
> -
> -%package apps
> -Summary:	apps cliparts
> -Summary(pl):	Kliparty "apps"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description apps
> -16 cliparts from apps category.
> -
> -%description apps -l pl
> -16 klipart?w z kategorii "apps".
> -
> -%package map_symbols
> -Summary:	map_symbols cliparts
> -Summary(pl):	Kliparty "map_symbols"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> +%description png
> +PNG version of Openclipart.
>
> -%description map_symbols
> -21 cliparts from map_symbols category.
> -
> -%description map_symbols -l pl
> -21 klipart?w z kategorii "map_symbols".
> -
> -%package images
> -Summary:	images cliparts
> -Summary(pl):	Kliparty "images"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description images
> -13 cliparts from images category.
> -
> -%description images -l pl
> -13 klipart?w z kategorii "images".
> -
> -%package animals
> -Summary:	animals cliparts
> -Summary(pl):	Kliparty "animals"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description animals
> -7 cliparts from animals category.
> -
> -%description animals -l pl
> -7 klipart?w z kategorii "animals".
> -
> -%package signs
> -Summary:	signs cliparts
> -Summary(pl):	Kliparty "signs"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description signs
> -22 cliparts from signs category.
> -
> -%description signs -l pl
> -22 klipart?w z kategorii "signs".
> -
> -%package unsorted
> -Summary:	unsorted cliparts
> -Summary(pl):	Kliparty "unsorted"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description unsorted
> -456 cliparts from unsorted category.
> -
> -%description unsorted -l pl
> -456 klipart?w z kategorii "unsorted".
> -
> -%package filesystem
> -Summary:	filesystem cliparts
> -Summary(pl):	Kliparty "filesystem"
> -Group:		Applications/Graphics
> -Requires:	%{name}-AUTHORS = %{epoch}:%{version}-%{release}
> -
> -%description filesystem
> -44 cliparts from filesystem category.
> -
> -%description filesystem -l pl
> -44 klipart?w z kategorii "filesystem".
> +%description png -l pl
> +Kliparty w wersji PNG.
>
>  %prep
>  %setup -q
>
> +%build
> +find . -empty -type d -exec rmdir "{}" ";" || :
> +
>  %install
>  rm -rf $RPM_BUILD_ROOT
> -install -d
> $RPM_BUILD_ROOT%{_datadir}/%{name}/{activities,africa,america,animal,Animal
>,appicon,apple,aqua,Aqua,architecture,armoiries,arrow,asia,automobiles,baby,
>bacon,ball,beach,beverages,bicycle,Biohazard,bird,book,bouquet,bowl,breizh,b
>ritain,BSD,building,business,button,Button,callout,candy,cartoon,celebrity,c
>eltic,che,chicken,Chicken,clipboard,clock,coffe,communication,countires,cute
>,daemon,decorations,devices,eagle,ecus,education,emblems,entertainment,envel
>ope,europe,face,fanart,farm,Farm,festive,fish,flag,Flag,flight,flourish,flow
>er,fly,french,friends,fruit,Galette,game,geography,geometry,glass,grape,grea
>t,GTP,guevara,handshake,hen,Hen,historic,icon,improvisedkeywordparse,insect,
>insects,interface,ladybug,library,linux,Linux,logo,Logo,logos,magnifying,mai
>l,mammal,mammals,man,map,maps,mascot,meat,meeting,money,music,musicsym,navig
>ation,nicu,northamerica,note,oceania,office,openclipart,park,pear,penguin,pi
>g,place,plane,plant,postage,presentation,scissors,Scotland,shape,shapes,sign
>,slides,smiley,soccer,Software,soup,sports,stamp,star,steaming,study,summer,
>sun,symbol,tea,technical,telephone,tools,toy,toys,transport,transportation,t
>ux,Tux,usmail,vase,vgcats,vietnam,warning,water,weather,wildlife,wine,work,i
>cons,people,ocal_logo,gradients,food,mime-types,actions,computer,filetype,ho
>mes,device,application,filesystems,action,apps,map_symbols,images,animals,si
>gns,unsorted,filesystem}
>
> -install activities/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/activities
> -rm -rf activities/*[!tT]
> -install africa/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/africa
> -rm -rf africa/*[!tT]
> -install america/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/america
> -rm -rf america/*[!tT]
> -install animal/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/animal
> -rm -rf animal/*[!tT]
> -install Animal/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/Animal
> -rm -rf Animal/*[!tT]
> -install appicon/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/appicon
> -rm -rf appicon/*[!tT]
> -install apple/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/apple
> -rm -rf apple/*[!tT]
> -install aqua/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/aqua
> -rm -rf aqua/*[!tT]
> -install Aqua/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/Aqua
> -rm -rf Aqua/*[!tT]
> -install architecture/*[!tT]
> $RPM_BUILD_ROOT%{_datadir}/%{name}/architecture -rm -rf architecture/*[!tT]
> -install armoiries/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/armoiries
> -rm -rf armoiries/*[!tT]
> -install arrow/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/arrow
> -rm -rf arrow/*[!tT]
> -install asia/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/asia
> -rm -rf asia/*[!tT]
> -install automobiles/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/automobiles
> -rm -rf automobiles/*[!tT]
> -install baby/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/baby
> -rm -rf baby/*[!tT]
> -install bacon/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/bacon
> -rm -rf bacon/*[!tT]
> -install ball/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/ball
> -rm -rf ball/*[!tT]
> -install beach/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/beach
> -rm -rf beach/*[!tT]
> -install beverages/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/beverages
> -rm -rf beverages/*[!tT]
> -install bicycle/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/bicycle
> -rm -rf bicycle/*[!tT]
> -install Biohazard/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/Biohazard
> -rm -rf Biohazard/*[!tT]
> -install bird/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/bird
> -rm -rf bird/*[!tT]
> -install book/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/book
> -rm -rf book/*[!tT]
> -install bouquet/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/bouquet
> -rm -rf bouquet/*[!tT]
> -install bowl/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/bowl
> -rm -rf bowl/*[!tT]
> -install breizh/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/breizh
> -rm -rf breizh/*[!tT]
> -install britain/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/britain
> -rm -rf britain/*[!tT]
> -install BSD/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/BSD
> -rm -rf BSD/*[!tT]
> -install building/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/building
> -rm -rf building/*[!tT]
> -install business/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/business
> -rm -rf business/*[!tT]
> -install button/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/button
> -rm -rf button/*[!tT]
> -install Button/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/Button
> -rm -rf Button/*[!tT]
> -install callout/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/callout
> -rm -rf callout/*[!tT]
> -install candy/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/candy
> -rm -rf candy/*[!tT]
> -install cartoon/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/cartoon
> -rm -rf cartoon/*[!tT]
> -install celebrity/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/celebrity
> -rm -rf celebrity/*[!tT]
> -install celtic/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/celtic
> -rm -rf celtic/*[!tT]
> -install che/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/che
> -rm -rf che/*[!tT]
> -install chicken/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/chicken
> -rm -rf chicken/*[!tT]
> -install Chicken/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/Chicken
> -rm -rf Chicken/*[!tT]
> -install clipboard/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/clipboard
> -rm -rf clipboard/*[!tT]
> -install clock/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/clock
> -rm -rf clock/*[!tT]
> -install coffe/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/coffe
> -rm -rf coffe/*[!tT]
> -install communication/*[!tT]
> $RPM_BUILD_ROOT%{_datadir}/%{name}/communication -rm -rf
> communication/*[!tT]
> -install countires/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/countires
> -rm -rf countires/*[!tT]
> -install cute/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/cute
> -rm -rf cute/*[!tT]
> -install daemon/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/daemon
> -rm -rf daemon/*[!tT]
> -install decorations/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/decorations
> -rm -rf decorations/*[!tT]
> -install devices/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/devices
> -rm -rf devices/*[!tT]
> -install eagle/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/eagle
> -rm -rf eagle/*[!tT]
> -install ecus/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/ecus
> -rm -rf ecus/*[!tT]
> -install education/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/education
> -rm -rf education/*[!tT]
> -install emblems/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/emblems
> -rm -rf emblems/*[!tT]
> -install entertainment/*[!tT]
> $RPM_BUILD_ROOT%{_datadir}/%{name}/entertainment -rm -rf
> entertainment/*[!tT]
> -install envelope/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/envelope
> -rm -rf envelope/*[!tT]
> -install europe/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/europe
> -rm -rf europe/*[!tT]
> -install face/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/face
> -rm -rf face/*[!tT]
> -install fanart/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/fanart
> -rm -rf fanart/*[!tT]
> -install farm/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/farm
> -rm -rf farm/*[!tT]
> -install Farm/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/Farm
> -rm -rf Farm/*[!tT]
> -install festive/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/festive
> -rm -rf festive/*[!tT]
> -install fish/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/fish
> -rm -rf fish/*[!tT]
> -install flag/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/flag
> -rm -rf flag/*[!tT]
> -install Flag/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/Flag
> -rm -rf Flag/*[!tT]
> -install flight/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/flight
> -rm -rf flight/*[!tT]
> -install flourish/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/flourish
> -rm -rf flourish/*[!tT]
> -install flower/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/flower
> -rm -rf flower/*[!tT]
> -install fly/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/fly
> -rm -rf fly/*[!tT]
> -install french/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/french
> -rm -rf french/*[!tT]
> -install friends/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/friends
> -rm -rf friends/*[!tT]
> -install fruit/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/fruit
> -rm -rf fruit/*[!tT]
> -install Galette/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/Galette
> -rm -rf Galette/*[!tT]
> -install game/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/game
> -rm -rf game/*[!tT]
> -install geography/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/geography
> -rm -rf geography/*[!tT]
> -install geometry/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/geometry
> -rm -rf geometry/*[!tT]
> -install glass/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/glass
> -rm -rf glass/*[!tT]
> -install grape/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/grape
> -rm -rf grape/*[!tT]
> -install great/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/great
> -rm -rf great/*[!tT]
> -install GTP/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/GTP
> -rm -rf GTP/*[!tT]
> -install guevara/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/guevara
> -rm -rf guevara/*[!tT]
> -install handshake/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/handshake
> -rm -rf handshake/*[!tT]
> -install hen/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/hen
> -rm -rf hen/*[!tT]
> -install Hen/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/Hen
> -rm -rf Hen/*[!tT]
> -install historic/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/historic
> -rm -rf historic/*[!tT]
> -install icon/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/icon
> -rm -rf icon/*[!tT]
> -install improvisedkeywordparse/*[!tT]
> $RPM_BUILD_ROOT%{_datadir}/%{name}/improvisedkeywordparse -rm -rf
> improvisedkeywordparse/*[!tT]
> -install insect/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/insect
> -rm -rf insect/*[!tT]
> -install insects/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/insects
> -rm -rf insects/*[!tT]
> -install interface/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/interface
> -rm -rf interface/*[!tT]
> -install ladybug/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/ladybug
> -rm -rf ladybug/*[!tT]
> -install library/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/library
> -rm -rf library/*[!tT]
> -install linux/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/linux
> -rm -rf linux/*[!tT]
> -install Linux/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/Linux
> -rm -rf Linux/*[!tT]
> -install logo/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/logo
> -rm -rf logo/*[!tT]
> -install Logo/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/Logo
> -rm -rf Logo/*[!tT]
> -install logos/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/logos
> -rm -rf logos/*[!tT]
> -install magnifying/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/magnifying
> -rm -rf magnifying/*[!tT]
> -install mail/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/mail
> -rm -rf mail/*[!tT]
> -install mammal/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/mammal
> -rm -rf mammal/*[!tT]
> -install mammals/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/mammals
> -rm -rf mammals/*[!tT]
> -install man/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/man
> -rm -rf man/*[!tT]
> -install map/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/map
> -rm -rf map/*[!tT]
> -install maps/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/maps
> -rm -rf maps/*[!tT]
> -install mascot/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/mascot
> -rm -rf mascot/*[!tT]
> -install meat/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/meat
> -rm -rf meat/*[!tT]
> -install meeting/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/meeting
> -rm -rf meeting/*[!tT]
> -install money/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/money
> -rm -rf money/*[!tT]
> -install music/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/music
> -rm -rf music/*[!tT]
> -install musicsym/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/musicsym
> -rm -rf musicsym/*[!tT]
> -install navigation/*[!tT] $RPM_BUILD_ROOT%{_datadir}/%{name}/navigation
> -rm -rf navigation/*[!tT]
> <<Diff was trimmed, longer than 597 lines>>
>
> ---- CVS-web:
>     http://cvs.pld-linux.org/SPECS/openclipart.spec?r1=1.3&r2=1.4&f=u
>
> _______________________________________________
> pld-cvs-commit mailing list
> pld-cvs-commit at lists.pld-linux.org
> http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit

-- 
glen


From zswi at pers.pl  Mon Aug  8 11:56:44 2005
From: zswi at pers.pl (=?utf-8?q?Rafa=C5=82_Cygnarowski?=)
Date: Mon, 8 Aug 2005 11:56:44 +0200
Subject: What's AC status now?
Message-ID: <200508081156.44600.zswi@pers.pl>

Hi!

What's the AC status now? What's left to do for full release?

-- 
Rafa? Cygnarowski
rafi at pers.pl


From glen at delfi.ee  Mon Aug  8 16:39:35 2005
From: glen at delfi.ee (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Mon, 8 Aug 2005 17:39:35 +0300
Subject: SPECS: python.spec - The interpreter works fine without the
	readli...
In-Reply-To: <SPECS_python.spec.1.233@pld-linux.org>
References: <SPECS_python.spec.1.232@pld-linux.org>
	<SPECS_python.spec.1.233@pld-linux.org>
Message-ID: <200508081739.35692.glen@delfi.ee>

what about making python-modules being noarch for files which are 
in /usr/share, and separate package for files which are true arch-dependant, 
so i could install python-modules for i686 and amd64 arch? (so i could run 
32bit openoffice on amd64)?


On Monday 08 August 2005 16:17, saq wrote:
> Author: saq                          Date: Mon Aug  8 13:17:32 2005 GMT
> Module: SPECS                         Tag: HEAD
> ---- Log message:
> - The interpreter works fine without the readline module, so moving it to
>   -modules. It makes way more sense there.
>
> ---- Files affected:
> SPECS:
>    python.spec (1.232 -> 1.233)
>
> ---- Diffs:
>
> ================================================================
> Index: SPECS/python.spec
> diff -u SPECS/python.spec:1.232 SPECS/python.spec:1.233
> --- SPECS/python.spec:1.232	Wed May 11 04:55:04 2005
> +++ SPECS/python.spec	Mon Aug  8 15:17:26 2005
> @@ -554,9 +554,6 @@
>  %attr(755,root,root) %{_bindir}/python
>  %{_mandir}/man1/*
>
> -# readline support for python binary
> -%attr(755,root,root) %{py_dyndir}/readline.so
> -
>  %files modules
>  %defattr(644,root,root,755)
>  %exclude %{py_scriptdir}/UserDict.py[co]
> @@ -636,6 +633,7 @@
>  %attr(755,root,root) %{py_dyndir}/parser.so
>  %attr(755,root,root) %{py_dyndir}/pwd.so
>  %attr(755,root,root) %{py_dyndir}/pyexpat.so
> +%attr(755,root,root) %{py_dyndir}/readline.so
>  %attr(755,root,root) %{py_dyndir}/regex.so
>  %attr(755,root,root) %{py_dyndir}/resource.so
>  %attr(755,root,root) %{py_dyndir}/select.so
> @@ -818,6 +816,10 @@
>  All persons listed below can be reached at <cvs_login>@pld-linux.org
>
>  $Log$
> +Revision 1.233  2005/08/08 13:17:26  saq
> +- The interpreter works fine without the readline module, so moving it to
> +  -modules. It makes way more sense there.
> +
>  Revision 1.232  2005/05/11 02:55:04  pluto
>  - release 2 for rebuild for x86-64 target.
>
> ================================================================
>
> ---- CVS-web:
>     http://cvs.pld-linux.org/SPECS/python.spec?r1=1.232&r2=1.233&f=u
>
> _______________________________________________
> pld-cvs-commit mailing list
> pld-cvs-commit at lists.pld-linux.org
> http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit

-- 
glen


From saq at pld-linux.org  Mon Aug  8 15:23:01 2005
From: saq at pld-linux.org (=?iso-8859-2?Q?Pawe=B3?= Sakowski)
Date: Mon, 08 Aug 2005 15:23:01 +0200
Subject: SPECS: python.spec - The interpreter works fine without the
	readli...
In-Reply-To: <SPECS_python.spec.1.233@pld-linux.org>
References: <SPECS_python.spec.1.232@pld-linux.org>
	<SPECS_python.spec.1.233@pld-linux.org>
Message-ID: <1123507382.5383.7.camel@neptune.sakowski.pl>

On Mon, 2005-08-08 at 15:17 +0200, saq wrote:
> Author: saq                          Date: Mon Aug  8 13:17:32 2005 GMT
> Module: SPECS                         Tag: HEAD
> ---- Log message:
> - The interpreter works fine without the readline module, so moving it to
>   -modules. It makes way more sense there.

Does anybody have a strong feeling about merging the python{,-libs}
packages? Without readline, the python package contains nothing but

-rwxr-xr-x    1 root    root    3736 May  4 22:47 /usr/bin/python
-rw-r--r--    1 root    root    4777 May  4 22:47 /usr/share/man/man1/python.1.gz

the only big dependency being libstdc++.

-- 
Pawe? Sakowski <saq at pld-linux.org>
PLD Linux Distribution



From saq at pld-linux.org  Tue Aug  9 23:42:49 2005
From: saq at pld-linux.org (=?iso-8859-2?Q?Pawe=B3?= Sakowski)
Date: Tue, 09 Aug 2005 23:42:49 +0200
Subject: lyx vs texhash
Message-ID: <1123623769.5384.6.camel@neptune.sakowski.pl>

[saq at neptune SPECS]$ sudo poldek -u lyx
Retrieving ftp://ftp.athlon.ac.pld-linux.org/dists/ac/PLD/athlon/PLD/RPMS/lyx-1.3.5-5.athlon.rpm...
......................... 100.0% [4.0M (23.2K/s)]
Retrieving ftp://ftp.athlon.ac.pld-linux.org/dists/ac/PLD/athlon/PLD/RPMS/xdvi-2.0.2-7.athlon.rpm...
......................... 100.0% [151.1K (27.9K/s)]
Retrieving ftp://ftp.athlon.ac.pld-linux.org/dists/ac/PLD/athlon/PLD/RPMS/tetex-metafont-2.0.2-7.athlon.rpm...
......................... 100.0% [319.0K (20.3K/s)]
/var/tmp/rpm-tmp.73609[2]: /usr/bin/texhash: not found

Indeed, both %post and %postun unconditionally try to invoke texhash. Is
that optional (as in [ ! -x ...] || ...) or should the script require
texhash?

-- 
Pawe? Sakowski <saq at pld-linux.org>
PLD Linux Distribution



From glen at delfi.ee  Wed Aug 10 11:03:58 2005
From: glen at delfi.ee (Elan =?iso-8859-13?q?Ruusam=E4e?=)
Date: Wed, 10 Aug 2005 12:03:58 +0300
Subject: error: syslog-ng:68 duplicate log entry for /var/log/xferlog
In-Reply-To: <200508011427.13723.glen@delfi.ee>
References: <20050319081335.GA6680@os>
	<Pine.LNX.4.61L.0508011144530.1728@wby.gnfx.tqn.cy>
	<200508011427.13723.glen@delfi.ee>
Message-ID: <200508101203.58903.glen@delfi.ee>

ping?

On Monday 01 August 2005 14:27, Elan Ruusam?e wrote:
> On Monday 01 August 2005 12:45, Pawe? Go?aszewski wrote:
> > On Mon, 1 Aug 2005, Elan Ruusam?e wrote:
> > > how this got resolved? because i seem to have same conflict between
> > > syslog and proftpd.
> > >
> > > # grep xferlog /etc/logrotate.d/*
> > > /etc/logrotate.d/ftpd:/var/log/xferlog {
> > > /etc/logrotate.d/syslog:/var/log/xferlog {
> > > # rpm -qf ftpd syslog
> > > proftpd-common-1.2.10-5
> > > syslog-1.4.1-13.2
> >
> > Should be removed from proftpd, IMO.
> > xferlog i a common thing.
>
> although the question remains, who writes the log? syslog? or proftpd?
> if it's syslogd, then yes, rotation should be in syslog package
> but if it's proftpd writing it directly, then it should be in proftpd
> package.
>
> but in latter case i believe proftpd should be reconfigured to use
> differeng logfile.
>
> > > > Has appeared after:
> > > >
> > > > SOURCES/syslog-ng.logrotate
> > > >
> > > > 1.9 Sun Nov 7 13:57:37 2004 by blues
> > > > - added xferlog
> > > >
> > > > Please take a look at /etc/logrotate.d/ftpd from proftpd-common
> > > > (SOURCES/proftpd.logrotate) and remove one of these two (I suppose
> > > > you've got some reason in adding it to syslog itself).

-- 
glen


From blues at pld-linux.org  Wed Aug 10 11:18:08 2005
From: blues at pld-linux.org (=?ISO-8859-2?Q?Pawe=B3_Go=B3aszewski?=)
Date: Wed, 10 Aug 2005 11:18:08 +0200 (CEST)
Subject: error: syslog-ng:68 duplicate log entry for /var/log/xferlog
In-Reply-To: <200508011427.13723.glen@delfi.ee>
References: <20050319081335.GA6680@os> <200508010138.36206.glen@delfi.ee>
	<Pine.LNX.4.61L.0508011144530.1728@wby.gnfx.tqn.cy>
	<200508011427.13723.glen@delfi.ee>
Message-ID: <Pine.LNX.4.61L.0508101116530.21800@wby.gnfx.tqn.cy>

On Mon, 1 Aug 2005, Elan [iso-8859-13] Ruusam?e wrote:
> > > how this got resolved? because i seem to have same conflict between 
> > > syslog and proftpd.
> > >
> > > # grep xferlog /etc/logrotate.d/*
> > > /etc/logrotate.d/ftpd:/var/log/xferlog {
> > > /etc/logrotate.d/syslog:/var/log/xferlog {
> > > # rpm -qf ftpd syslog
> > > proftpd-common-1.2.10-5
> > > syslog-1.4.1-13.2
> > Should be removed from proftpd, IMO. xferlog i a common thing.
> although the question remains, who writes the log? syslog? or proftpd? 
> if it's syslogd, then yes, rotation should be in syslog package but if 
> it's proftpd writing it directly, then it should be in proftpd package. 
> but in latter case i believe proftpd should be reconfigured to use 
> differeng logfile.

IMO - every daemon should write to syslog.
You can then separate logs into files you want. And send to remote 
syslog...

-- 
pozdr.  Pawe? Go?aszewski jid:blues<at>jabber<dot>gda<dot>pl 
-------------------------------------------------------------------------- 
If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby 
Pro-Logic Surround Sound with Bass Boost and all the music is free.

From jajcus at jajcus.net  Wed Aug 10 12:29:28 2005
From: jajcus at jajcus.net (Jacek Konieczny)
Date: Wed, 10 Aug 2005 12:29:28 +0200
Subject: error: syslog-ng:68 duplicate log entry for /var/log/xferlog
In-Reply-To: <Pine.LNX.4.61L.0508101116530.21800@wby.gnfx.tqn.cy>
References: <20050319081335.GA6680@os> <200508010138.36206.glen@delfi.ee>
	<Pine.LNX.4.61L.0508011144530.1728@wby.gnfx.tqn.cy>
	<200508011427.13723.glen@delfi.ee>
	<Pine.LNX.4.61L.0508101116530.21800@wby.gnfx.tqn.cy>
Message-ID: <20050810102927.GB4340@serwis2.beta>

On Wed, Aug 10, 2005 at 11:18:08AM +0200, Pawe? Go?aszewski wrote:
> IMO - every daemon should write to syslog.
> You can then separate logs into files you want. And send to remote 
> syslog...

But we shoul keep an option of logging directly to a file, wherever
possible. Usuing syslog often less reliable and sometimes less secure
than writting directly to a file.

Greets,
        Jacek


From blues at pld-linux.org  Wed Aug 10 15:06:17 2005
From: blues at pld-linux.org (=?ISO-8859-2?Q?Pawe=B3_Go=B3aszewski?=)
Date: Wed, 10 Aug 2005 15:06:17 +0200 (CEST)
Subject: error: syslog-ng:68 duplicate log entry for /var/log/xferlog
In-Reply-To: <20050810102927.GB4340@serwis2.beta>
References: <20050319081335.GA6680@os> <200508010138.36206.glen@delfi.ee>
	<Pine.LNX.4.61L.0508011144530.1728@wby.gnfx.tqn.cy>
	<200508011427.13723.glen@delfi.ee>
	<Pine.LNX.4.61L.0508101116530.21800@wby.gnfx.tqn.cy>
	<20050810102927.GB4340@serwis2.beta>
Message-ID: <Pine.LNX.4.61L.0508101505440.3103@wby.gnfx.tqn.cy>

On Wed, 10 Aug 2005, Jacek Konieczny wrote:
> > IMO - every daemon should write to syslog. You can then separate logs 
> > into files you want. And send to remote syslog...
> But we shoul keep an option of logging directly to a file, wherever 
> possible. Usuing syslog often less reliable and sometimes less secure 
> than writting directly to a file.

sure, logging to file should be possible if program is capable to do 
that...

-- 
pozdr.  Pawe? Go?aszewski          jid:blues<at>jabber<dot>gda<dot>pl
--------------------------------------------------------------------------
If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby
Pro-Logic Surround Sound with Bass Boost and all the music is free.

From robert.wozny at gmail.com  Wed Aug 10 15:55:18 2005
From: robert.wozny at gmail.com (robert j. wozny)
Date: Wed, 10 Aug 2005 15:55:18 +0200
Subject: error: syslog-ng:68 duplicate log entry for /var/log/xferlog
References: <20050319081335.GA6680@os> <200508010138.36206.glen@delfi.ee>
	<Pine.LNX.4.61L.0508011144530.1728@wby.gnfx.tqn.cy>
	<200508011427.13723.glen@delfi.ee>
	<Pine.LNX.4.61L.0508101116530.21800@wby.gnfx.tqn.cy>
	<20050810102927.GB4340@serwis2.beta>
	<Pine.LNX.4.61L.0508101505440.3103@wby.gnfx.tqn.cy>
Message-ID: <gnus.x7hddxew1l.fsf@hell.ziew.org>

Quoting blues at pld-linux.org (Pawe? Go?aszewski):

>> But we shoul keep an option of logging directly to a file, wherever 
>> possible. Usuing syslog often less reliable and sometimes less secure 
>> than writting directly to a file.
> sure, logging to file should be possible if program is capable to do 
> that...

or we are using fsl library... 8-] 

-- 
robert j. wozny
... Zycie biegnie wahadlowym ruchem miedzy bolem i nuda, 
a sa to faktycznie jego ostateczne skladniki. (Artur Schopenhauer)


From glen at delfi.ee  Wed Aug 10 15:59:32 2005
From: glen at delfi.ee (Elan =?iso-8859-2?q?Ruusam=E4e?=)
Date: Wed, 10 Aug 2005 16:59:32 +0300
Subject: error: syslog-ng:68 duplicate log entry for /var/log/xferlog
In-Reply-To: <20050810102927.GB4340@serwis2.beta>
References: <20050319081335.GA6680@os>
	<Pine.LNX.4.61L.0508101116530.21800@wby.gnfx.tqn.cy>
	<20050810102927.GB4340@serwis2.beta>
Message-ID: <200508101659.32560.glen@delfi.ee>

On Wednesday 10 August 2005 13:29, Jacek Konieczny wrote:
> On Wed, Aug 10, 2005 at 11:18:08AM +0200, Pawe? Go?aszewski wrote:
> > IMO - every daemon should write to syslog.
> > You can then separate logs into files you want. And send to remote
> > syslog...
>
> But we shoul keep an option of logging directly to a file, wherever
> possible. Usuing syslog often less reliable and sometimes less secure
> than writting directly to a file.
anyway, as the default (proftpd) config logs to syslog, i'm removing the 
logrotate config from proftpd-common.


>
> Greets,
>         Jacek
> _______________________________________________
> pld-devel-en mailing list
> pld-devel-en at lists.pld-linux.org
> http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

-- 
glen


From twittner at o2.pl  Thu Aug 11 00:09:06 2005
From: twittner at o2.pl (Tomasz Wittner)
Date: Thu, 11 Aug 2005 00:09:06 +0200
Subject: rpm-find-spec-bcond is broken
Message-ID: <200508110009.07642.twittner@o2.pl>

Displaying in rpm-find-spec-bcond is broken. I'm talking about:
SOURCES]$ cvs status rpm-find-spec-bcond
===================================================================
File: rpm-find-spec-bcond       Status: Up-to-date

   Working revision:    1.8
   Repository revision: 1.8     /cvsroot/SOURCES/rpm-find-spec-bcond,v

It behaves different for old and new bconds - kernel-mosix.spec has oldfashion 
bconds, mc.spec - new:
SOURCES]$ ./rpm-find-spec-bcond ../SPECS/kernel-mosix.spec
_without_doc
_without_owl
_without_smp
_without_source
_without_up

I've intentionally added few blanks after %bcond_with
%bcond_with                     ext2undel     # with ext2 undelete fs
to mc.spec - here is result:
SOURCES]$ ./rpm-find-spec-bcond ../SPECS/mc.spec
_with
_____________
__ext2undel
_without
perl_vfs
_without
x
_with
samba
_with
utf8

Enclosed patch fixes this issue, but, probably, our builder scripts relies on 
such displaying bconds (in other words - my fix breaks builder). I'm not 
going to fix builder - sorry ;).

-- 
Tomasz Wittner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rpm-find-spec-bcond.patch
Type: text/x-diff
Size: 697 bytes
Desc: not available
URL: </mailman/pipermail/pld-devel-en/attachments/20050811/2366d1ca/attachment.bin>

From qboosh at pld-linux.org  Thu Aug 11 09:04:08 2005
From: qboosh at pld-linux.org (Jakub Bogusz)
Date: Thu, 11 Aug 2005 09:04:08 +0200
Subject: SPECS: proftpd.spec - no main package is built,
	moved %description...
In-Reply-To: <SPECS_proftpd.spec.1.211@pld-linux.org>
References: <SPECS_proftpd.spec.1.210@pld-linux.org>
	<SPECS_proftpd.spec.1.211@pld-linux.org>
Message-ID: <20050811070408.GA25409@gruby.cs.net.pl>

On Wed, Aug 10, 2005 at 10:46:48PM +0200, glen wrote:
> Author: glen                         Date: Wed Aug 10 20:46:48 2005 GMT
> Module: SPECS                         Tag: HEAD
> ---- Log message:
> - no main package is built, moved %descriptions to -common package
> - rel 7

> +# There is no main package.
>  %description
> +
> +%package common

But main Summary/%description is always used for .src.rpm package.


-- 
Jakub Bogusz    http://qboosh.cs.net.pl/


From glen at delfi.ee  Thu Aug 11 20:38:21 2005
From: glen at delfi.ee (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Thu, 11 Aug 2005 21:38:21 +0300
Subject: SPECS: mono.spec - handle rpm mono provides/requires - rel 2
In-Reply-To: <SPECS_mono.spec.1.131@pld-linux.org>
References: <SPECS_mono.spec.1.130@pld-linux.org>
	<SPECS_mono.spec.1.131@pld-linux.org>
Message-ID: <200508112138.21793.glen@delfi.ee>

why thse are in /usr/bin, while other similiar scripts are in /usr/lib/rpm?

$ l /usr/lib/rpm/find-*-{provides,requires}
-rwxr-xr-x  1 root root 514 Jul  7 02:12 /usr/lib/rpm/find-php-provides
-rwxr-xr-x  1 root root 871 Jul  7 02:12 /usr/lib/rpm/find-php-requires


On Thursday 11 August 2005 21:23, wolf wrote:
> Author: wolf                         Date: Thu Aug 11 18:23:30 2005 GMT
> Module: SPECS                         Tag: HEAD
> ---- Log message:
> - handle rpm mono provides/requires
> - rel 2
>
> ---- Files affected:
> SPECS:
>    mono.spec (1.130 -> 1.131)
>
> ---- Diffs:
>
> ================================================================
> Index: SPECS/mono.spec
> diff -u SPECS/mono.spec:1.130 SPECS/mono.spec:1.131
> --- SPECS/mono.spec:1.130	Thu Aug 11 19:52:36 2005
> +++ SPECS/mono.spec	Thu Aug 11 20:23:24 2005
> @@ -3,13 +3,20 @@
>  # Conditional build:
>  %bcond_without	nptl		# don't use TLS (which effectively requires NPTL
> libs) %bcond_without	static_libs	# don't build static libraries
> +%bcond_with	bootstrap	# don't require mono-devel to find req/prov
>  #
>  %define		_glibver	2.4
> +#
> +%if ! %{with bootstrap}
> +%define	__mono_provides	/usr/bin/mono-find-provides
> +%define	__mono_requires	/usr/bin/mono-find-requires
> +%endif
> +#
>  Summary:	Common Language Infrastructure implementation
>  Summary(pl):	Implementacja Common Language Infrastructure
>  Name:		mono
>  Version:	1.1.8.3
> -Release:	1
> +Release:	2
>  License:	GPL/LGPL/MIT
>  Group:		Development/Languages
>  #Source0Download: http://www.mono-project.com/Downloads
> @@ -27,7 +34,9 @@
>  BuildRequires:	glib2-devel >= %{_glibver}
>  BuildRequires:	libtool
>  BuildRequires:	pkgconfig
> +BuildRequires:	rpm-build >= 4.4.2-0.3
>  BuildRequires:	rpmbuild(macros) >= 1.213
> +%{!?with_bootstrap:BuildRequires:	mono-devel}
>  ExclusiveArch:	%{ix86} %{x8664} arm hppa ppc s390 s390x sparc sparcv9
> sparc64 # alpha still broken, mips/ia64/m68k disabled in configure
>  # note: plain i386 is not supported; mono uses cmpxchg/xadd which require
> i486 @@ -410,6 +419,10 @@
>  All persons listed below can be reached at <cvs_login>@pld-linux.org
>
>  $Log$
> +Revision 1.131  2005/08/11 18:23:24  wolf
> +- handle rpm mono provides/requires
> +- rel 2
> +
>  Revision 1.130  2005/08/11 17:52:36  wolf
>  - use bash for bash scripts
>
> ================================================================
>
> ---- CVS-web:
>     http://cvs.pld-linux.org/SPECS/mono.spec?r1=1.130&r2=1.131&f=u
>
> _______________________________________________
> pld-cvs-commit mailing list
> pld-cvs-commit at lists.pld-linux.org
> http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit

-- 
glen


From glen at delfi.ee  Thu Aug 11 20:40:17 2005
From: glen at delfi.ee (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Thu, 11 Aug 2005 21:40:17 +0300
Subject: Fwd: cvs move
Message-ID: <200508112140.18069.glen@delfi.ee>

move it dammit!

----------  Forwarded Message  ----------

Subject: cvs move
Date: Monday 08 August 2005 20:54
From: Elan Ruusam?e <glen at pld-linux.org>
To: cvsadmin at pld-linux.org

hi,

mv SPECS/Apache-FileManager.spec,v SPECS/perl-Apache-FileManager.spec,v

--
glen

-------------------------------------------------------

-- 
glen


From glen at delfi.ee  Thu Aug 11 21:42:24 2005
From: glen at delfi.ee (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Thu, 11 Aug 2005 22:42:24 +0300
Subject: SPECS: tao.spec - auto mono prov/req
In-Reply-To: <SPECS_tao.spec.1.3@pld-linux.org>
References: <SPECS_tao.spec.1.2@pld-linux.org>
	<SPECS_tao.spec.1.3@pld-linux.org>
Message-ID: <200508112242.25280.glen@delfi.ee>

i believe proper way of doing it is require some rpmbuild(macros) version 
(don't forget to document it in PLD-doc/BuildRequires.txt), in case someone 
backports it to ac-branch 4.4.1 version of rpm

On Thursday 11 August 2005 21:39, wolf wrote:
> Author: wolf                         Date: Thu Aug 11 18:39:22 2005 GMT
> Module: SPECS                         Tag: HEAD
> ---- Log message:
> - auto mono prov/req
>
> ---- Files affected:
> SPECS:
>    tao.spec (1.2 -> 1.3)
>
> ---- Diffs:
>
> ================================================================
> Index: SPECS/tao.spec
> diff -u SPECS/tao.spec:1.2 SPECS/tao.spec:1.3
> --- SPECS/tao.spec:1.2	Sat Jun 11 13:00:15 2005
> +++ SPECS/tao.spec	Thu Aug 11 20:39:17 2005
> @@ -1,4 +1,5 @@
>  # $Revision$, $Date$
> +%include	/usr/lib/rpm/macros.mono
>  Summary:	Tao Framework
>  Summary(pl):	Framework Tao
>  Name:		tao
> @@ -10,7 +11,7 @@
>  # Source0-md5:	170e143b8035644eb3c24db4cc7a2c3b
>  URL:		http://www.mono-project.com/Tao
>  BuildRequires:	mono >= 1.1.0
> -Requires:	mono >= 1.1.0
> +BuildRequires:	rpm-build >= 4.4.2-0.3
>  BuildRoot:	%{tmpdir}/%{name}-%{version}-root-%(id -u -n)
>
>  %description
> @@ -99,6 +100,9 @@
>  All persons listed below can be reached at <cvs_login>@pld-linux.org
>
>  $Log$
> +Revision 1.3  2005/08/11 18:39:17  wolf
> +- auto mono prov/req
> +
>  Revision 1.2  2005/06/11 11:00:15  qboosh
>  - cosmetics
>
> ================================================================
>
> ---- CVS-web:
>     http://cvs.pld-linux.org/SPECS/tao.spec?r1=1.2&r2=1.3&f=u
>
> _______________________________________________
> pld-cvs-commit mailing list
> pld-cvs-commit at lists.pld-linux.org
> http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit

-- 
glen


From wolf.pld at gmail.com  Thu Aug 11 21:42:06 2005
From: wolf.pld at gmail.com (Bartosz Taudul)
Date: Thu, 11 Aug 2005 21:42:06 +0200
Subject: SPECS: mono.spec - handle rpm mono provides/requires - rel 2
In-Reply-To: <200508112138.21793.glen@delfi.ee>
References: <SPECS_mono.spec.1.130@pld-linux.org>
	<SPECS_mono.spec.1.131@pld-linux.org>
	<200508112138.21793.glen@delfi.ee>
Message-ID: <20050811194206.GA24668@bajzel>

On Thu, Aug 11, 2005 at 09:38:21PM +0300, Elan Ruusam?e wrote:
> why thse are in /usr/bin, while other similiar scripts are in /usr/lib/rpm?
Mono places them there. If it's good or not is open to discussion.

wolf
-- 
  Bartek   .  - Przy drobnych przeliczeniach, kt?re zajm? ci stron?...
  Taudul   :  
          .:....................................................................
w o l f @ p l d - l i n u x . o r g            .:. http://wolf.valkyrie.one.pl/


From twittner at o2.pl  Thu Aug 11 22:21:15 2005
From: twittner at o2.pl (Tomasz Wittner)
Date: Thu, 11 Aug 2005 22:21:15 +0200
Subject: SPECS: mono.spec - handle rpm mono provides/requires - rel 2
In-Reply-To: <20050811194206.GA24668@bajzel>
References: <SPECS_mono.spec.1.130@pld-linux.org>
	<200508112138.21793.glen@delfi.ee> <20050811194206.GA24668@bajzel>
Message-ID: <200508112221.15929.twittner@o2.pl>

On Thu 11. of August 2005 21:42, Bartosz Taudul wrote:
> On Thu, Aug 11, 2005 at 09:38:21PM +0300, Elan Ruusam?e wrote:
> > why thse are in /usr/bin, while other similiar scripts are 
in /usr/lib/rpm?
> Mono places them there. If it's good or not is open to discussion.
I suppose that /usr/bin/mono-find-{provides,requires} are not called directly 
by admin or users but only from other programs (from rpm in this case). In 
such situation, in accordance with FHS 2.3 they should go to %{_libdir}/rpm/

http://www.pathname.com/fhs/pub/fhs-2.3.html#USRLIBLIBRARIESFORPROGRAMMINGANDPA
<quote>
/usr/lib : Libraries for programming and packages
Purpose

/usr/lib includes object files, libraries, and internal binaries that are not 
intended to be executed directly by users or shell scripts.
</quote>

> 
> wolf

-- 
Tomasz Wittner


From wolf.pld at gmail.com  Thu Aug 11 22:29:10 2005
From: wolf.pld at gmail.com (Bartosz Taudul)
Date: Thu, 11 Aug 2005 22:29:10 +0200
Subject: SPECS: tao.spec - auto mono prov/req
In-Reply-To: <200508112242.25280.glen@delfi.ee>
References: <SPECS_tao.spec.1.2@pld-linux.org>
	<SPECS_tao.spec.1.3@pld-linux.org>
	<200508112242.25280.glen@delfi.ee>
Message-ID: <20050811202910.GA26379@bajzel>

On Thu, Aug 11, 2005 at 10:42:24PM +0300, Elan Ruusam?e wrote:
> i believe proper way of doing it is require some rpmbuild(macros) version 
> (don't forget to document it in PLD-doc/BuildRequires.txt), in case someone 
> backports it to ac-branch 4.4.1 version of rpm
Almost all changes are in rpm's code, not in macros, so I don't see how
it could work. Maybe some BR: rpm(monodep) would be better?

wolf
-- 
  Bartek   .  - Wiecie o czym s? "Ch?opi" Reymonta?
  Taudul   :  - O ch?opach.
          .:....................................................................
w o l f @ p l d - l i n u x . o r g            .:. http://wolf.valkyrie.one.pl/


From glen at delfi.ee  Thu Aug 11 23:05:16 2005
From: glen at delfi.ee (Elan =?iso-8859-2?q?Ruusam=E4e?=)
Date: Fri, 12 Aug 2005 00:05:16 +0300
Subject: SPECS: tao.spec - auto mono prov/req
In-Reply-To: <20050811202910.GA26379@bajzel>
References: <SPECS_tao.spec.1.2@pld-linux.org>
	<200508112242.25280.glen@delfi.ee> <20050811202910.GA26379@bajzel>
Message-ID: <200508120005.16335.glen@delfi.ee>

On Thursday 11 August 2005 23:29, Bartosz Taudul wrote:
> On Thu, Aug 11, 2005 at 10:42:24PM +0300, Elan Ruusam?e wrote:
> > i believe proper way of doing it is require some rpmbuild(macros) version
> > (don't forget to document it in PLD-doc/BuildRequires.txt), in case
> > someone backports it to ac-branch 4.4.1 version of rpm
>
> Almost all changes are in rpm's code, not in macros, so I don't see how
> it could work. Maybe some BR: rpm(monodep) would be better?
...or fake revision for it:
$ cvs ci -f -m '- rev 1.234 for mono dep' rpm.macros

> wolf
glen


From wolf.pld at gmail.com  Thu Aug 11 23:17:00 2005
From: wolf.pld at gmail.com (Bartosz Taudul)
Date: Thu, 11 Aug 2005 23:17:00 +0200
Subject: SPECS: tao.spec - auto mono prov/req
In-Reply-To: <200508120005.16335.glen@delfi.ee>
References: <SPECS_tao.spec.1.2@pld-linux.org>
	<200508112242.25280.glen@delfi.ee> <20050811202910.GA26379@bajzel>
	<200508120005.16335.glen@delfi.ee>
Message-ID: <20050811211700.GA28101@bajzel>

On Fri, Aug 12, 2005 at 12:05:16AM +0300, Elan Ruusam?e wrote:
> > Almost all changes are in rpm's code, not in macros, so I don't see how
> > it could work. Maybe some BR: rpm(monodep) would be better?
> ...or fake revision for it:
> $ cvs ci -f -m '- rev 1.234 for mono dep' rpm.macros
There were some small changes in macros, so no need to fake. Will
bumping rpm_macros_rev in rpm.spec and changing BR: rpm-build to
BR: rpmbuild(macros) be sufficient? How does that work with backporting
to AC-branch?

wolf
-- 
  Bartek   .  - Matka jest potrzeb? wynalazku.
  Taudul   :  
          .:....................................................................
w o l f @ p l d - l i n u x . o r g            .:. http://wolf.valkyrie.one.pl/


From glen at delfi.ee  Thu Aug 11 23:25:23 2005
From: glen at delfi.ee (Elan =?iso-8859-2?q?Ruusam=E4e?=)
Date: Fri, 12 Aug 2005 00:25:23 +0300
Subject: SPECS: tao.spec - auto mono prov/req
In-Reply-To: <20050811211700.GA28101@bajzel>
References: <SPECS_tao.spec.1.2@pld-linux.org>
	<200508120005.16335.glen@delfi.ee> <20050811211700.GA28101@bajzel>
Message-ID: <200508120025.23753.glen@delfi.ee>

On Friday 12 August 2005 00:17, Bartosz Taudul wrote:
> On Fri, Aug 12, 2005 at 12:05:16AM +0300, Elan Ruusam?e wrote:
> > > Almost all changes are in rpm's code, not in macros, so I don't see how
> > > it could work. Maybe some BR: rpm(monodep) would be better?
> >
> > ...or fake revision for it:
> > $ cvs ci -f -m '- rev 1.234 for mono dep' rpm.macros
>
> There were some small changes in macros, so no need to fake. Will
> bumping rpm_macros_rev in rpm.spec and changing BR: rpm-build to
> BR: rpmbuild(macros) be sufficient? How does that work with backporting
> to AC-branch?
yes. true. it won't work until it's really backported. (ie the BR could be 
satisfied but the actual behaviour not)

so perhaps rpmbuild(monoautodeps) is the right choice.

> wolf

-- 
glen


From saq at pld-linux.org  Fri Aug 12 01:49:40 2005
From: saq at pld-linux.org (=?iso-8859-2?Q?Pawe=B3?= Sakowski)
Date: Fri, 12 Aug 2005 01:49:40 +0200
Subject: SPECS: tao.spec - auto mono prov/req
In-Reply-To: <200508120025.23753.glen@delfi.ee>
References: <SPECS_tao.spec.1.2@pld-linux.org>
	<200508120005.16335.glen@delfi.ee> <20050811211700.GA28101@bajzel>
	<200508120025.23753.glen@delfi.ee>
Message-ID: <1123804180.5457.29.camel@neptune.sakowski.pl>

On Fri, 2005-08-12 at 00:25 +0300, Elan Ruusam?e wrote:
> > There were some small changes in macros, so no need to fake. Will
> > bumping rpm_macros_rev in rpm.spec and changing BR: rpm-build to
> > BR: rpmbuild(macros) be sufficient? How does that work with backporting
> > to AC-branch?
> yes. true. it won't work until it's really backported. (ie the BR could be 
> satisfied but the actual behaviour not)
> 
> so perhaps rpmbuild(monoautodeps) is the right choice.

No need to introduce a Provides for every single new feature.
rpm_macros_rev high enough has always served that purpose. If you're
concerned that someone will bump macros rev on Ac again without
backporting the mono changes, mark that as a TODO in AC-branch spec.
Then again, if you're modifying it, you might port the change altogether
as well.

-- 
Pawe? Sakowski <saq at pld-linux.org>
PLD Linux Distribution



From saq at pld-linux.org  Fri Aug 12 01:51:28 2005
From: saq at pld-linux.org (=?iso-8859-2?Q?Pawe=B3?= Sakowski)
Date: Fri, 12 Aug 2005 01:51:28 +0200
Subject: SPECS: rpm.spec - rpm-build P: rpmbuild(monoautodeps)
In-Reply-To: <SPECS_rpm.spec.1.682@pld-linux.org>
References: <SPECS_rpm.spec.1.681@pld-linux.org>
	<SPECS_rpm.spec.1.682@pld-linux.org>
Message-ID: <1123804288.5457.31.camel@neptune.sakowski.pl>

On Fri, 2005-08-12 at 01:27 +0200, wolf wrote:
> Author: wolf                         Date: Thu Aug 11 23:27:10 2005 GMT
> Module: SPECS                         Tag: HEAD
> ---- Log message:
> - rpm-build P: rpmbuild(monoautodeps)

which doesn't really describe:

> -# because of -fvisibility... related fixes
> -Requires:	gcc >= 5:4.0.1-0.20050514.2

Was that on purpose?

-- 
Pawe? Sakowski <saq at pld-linux.org>
PLD Linux Distribution



From wolf.pld at gmail.com  Fri Aug 12 03:07:11 2005
From: wolf.pld at gmail.com (Bartosz Taudul)
Date: Fri, 12 Aug 2005 03:07:11 +0200
Subject: SPECS: rpm.spec - rpm-build P: rpmbuild(monoautodeps)
In-Reply-To: <1123804288.5457.31.camel@neptune.sakowski.pl>
References: <SPECS_rpm.spec.1.681@pld-linux.org>
	<SPECS_rpm.spec.1.682@pld-linux.org>
	<1123804288.5457.31.camel@neptune.sakowski.pl>
Message-ID: <20050812010711.GA13225@bajzel>

On Fri, Aug 12, 2005 at 01:51:28AM +0200, Pawe? Sakowski wrote:
> > -# because of -fvisibility... related fixes
> > -Requires:	gcc >= 5:4.0.1-0.20050514.2
> Was that on purpose?
I can't see anything related to -fvisibility in rpm on HEAD. Furthermore:

% cvs log rpm.macros
revision 1.227
date: 2005/07/07 19:23:35;  author: pluto;  state: Exp;  lines: +1 -1
- -fvisibility-inlines-hidden disabled.

wolf
-- 
  Bartek   .  - Zwr??my uwag? na wielorako?? i r??norodno?? tego ruchu.
  Taudul   :  
          .:....................................................................
w o l f @ p l d - l i n u x . o r g            .:. http://wolf.valkyrie.one.pl/


From qboosh at pld-linux.org  Fri Aug 12 07:31:00 2005
From: qboosh at pld-linux.org (Jakub Bogusz)
Date: Fri, 12 Aug 2005 07:31:00 +0200
Subject: SPECS: rpm.spec - rpm-build P: rpmbuild(monoautodeps)
In-Reply-To: <20050812010711.GA13225@bajzel>
References: <SPECS_rpm.spec.1.681@pld-linux.org>
	<SPECS_rpm.spec.1.682@pld-linux.org>
	<1123804288.5457.31.camel@neptune.sakowski.pl>
	<20050812010711.GA13225@bajzel>
Message-ID: <20050812053100.GA6392@fngna.oyu>

On Fri, Aug 12, 2005 at 03:07:11AM +0200, Bartosz Taudul wrote:
> On Fri, Aug 12, 2005 at 01:51:28AM +0200, Pawe? Sakowski wrote:
> > > -# because of -fvisibility... related fixes
> > > -Requires:	gcc >= 5:4.0.1-0.20050514.2
> > Was that on purpose?
> I can't see anything related to -fvisibility in rpm on HEAD. Furthermore:
> 
> % cvs log rpm.macros
> revision 1.227
> date: 2005/07/07 19:23:35;  author: pluto;  state: Exp;  lines: +1 -1
> - -fvisibility-inlines-hidden disabled.

But there is still -mtune= on i686, which requires gcc >= 5:3.4.


-- 
Jakub Bogusz    http://qboosh.cs.net.pl/


From arekm at pld-linux.org  Fri Aug 12 09:05:34 2005
From: arekm at pld-linux.org (Arkadiusz Miskiewicz)
Date: Fri, 12 Aug 2005 09:05:34 +0200
Subject: SOURCES: opensshd.init - use start-stop-daemon to stop *only*
	list...
In-Reply-To: <SOURCES_opensshd.init.1.26@pld-linux.org>
References: <SOURCES_opensshd.init.1.25@pld-linux.org>
	<SOURCES_opensshd.init.1.26@pld-linux.org>
Message-ID: <200508120905.35210.arekm@pld-linux.org>

On Thursday 11 of August 2005 22:43, glen wrote:
> Author: glen                         Date: Thu Aug 11 20:43:47 2005 GMT
> Module: SOURCES                       Tag: HEAD
> ---- Log message:
> - use start-stop-daemon to stop *only* listening sshd until somebody does
> it with rc-scripts tools
>

>  	if [ -f /var/lock/subsys/sshd ]; then
>  		msg_stopping OpenSSH
> -		killproc sshd
> -		rm -f /var/run/sshd.pid /var/lock/subsys/sshd >/dev/null 2>&1
> +		# we use start-stop-daemon to stop sshd, as it is unacceptable for such
> +		# critical service as sshd to kill it by procname, but unfortunately
> +		# rc-scripts does not provide way to kill *only* by pidfile
> +		start-stop-daemon --stop --quiet --pidfile /var/run/sshd.pid && ok ||
> fail +		rm -f /var/lock/subsys/sshd >/dev/null 2>&1

*PLEASE* fix / add new functionality to rc-scripts instead of messing with 
init script. What will happen if every developer will write own things in 
init scripts because he is too lazy to change rc-scripts?

Add --pidfileonly option to killproc for example.

-- 
Arkadiusz Mi?kiewicz                    PLD/Linux Team
http://www.t17.ds.pwr.wroc.pl/~misiek/  http://ftp.pld-linux.org/


From glen at delfi.ee  Fri Aug 12 09:25:52 2005
From: glen at delfi.ee (Elan =?iso-8859-2?q?Ruusam=E4e?=)
Date: Fri, 12 Aug 2005 10:25:52 +0300
Subject: SOURCES: opensshd.init - use start-stop-daemon to stop *only*
	list...
In-Reply-To: <200508120905.35210.arekm@pld-linux.org>
References: <SOURCES_opensshd.init.1.25@pld-linux.org>
	<SOURCES_opensshd.init.1.26@pld-linux.org>
	<200508120905.35210.arekm@pld-linux.org>
Message-ID: <200508121025.52242.glen@delfi.ee>

On Friday 12 August 2005 10:05, Arkadiusz Miskiewicz wrote:
> On Thursday 11 of August 2005 22:43, glen wrote:
> > Author: glen                         Date: Thu Aug 11 20:43:47 2005 GMT
> > Module: SOURCES                       Tag: HEAD
> > ---- Log message:
> > - use start-stop-daemon to stop *only* listening sshd until somebody does
> > it with rc-scripts tools
> >
> >
> >  	if [ -f /var/lock/subsys/sshd ]; then
> >  		msg_stopping OpenSSH
> > -		killproc sshd
> > -		rm -f /var/run/sshd.pid /var/lock/subsys/sshd >/dev/null 2>&1
> > +		# we use start-stop-daemon to stop sshd, as it is unacceptable for
> > such +		# critical service as sshd to kill it by procname, but
> > unfortunately +		# rc-scripts does not provide way to kill *only* by
> > pidfile
> > +		start-stop-daemon --stop --quiet --pidfile /var/run/sshd.pid && ok ||
> > fail +		rm -f /var/lock/subsys/sshd >/dev/null 2>&1
>
> *PLEASE* fix / add new functionality to rc-scripts instead of messing with
> init script.
i don't feel comfortable at all when killproc kills processes by name, if 
--pidfile option was specified. but that's the current behaviour, if 
--pidfile is specifed, it will kill by that file contents, but if that file 
*doesn't exist*, it will go kill by procname, regardless that --pidfile was 
specified. i think that behaviour is to be changed to "--pidfile kills only 
by pidfile, never by procname"

> What will happen if every developer will write own things in 
> init scripts because he is too lazy to change rc-scripts?
world will be a better place and maintainer of rc-scripts will take good 
features from initscripts and add it to rc-scripts :)

> Add --pidfileonly option to killproc for example.


-- 
glen


From glen at delfi.ee  Fri Aug 12 21:29:55 2005
From: glen at delfi.ee (Elan =?iso-8859-2?q?Ruusam=E4e?=)
Date: Fri, 12 Aug 2005 22:29:55 +0300
Subject: SPECS: tao.spec - auto mono prov/req
In-Reply-To: <1123804180.5457.29.camel@neptune.sakowski.pl>
References: <SPECS_tao.spec.1.2@pld-linux.org>
	<200508120025.23753.glen@delfi.ee>
	<1123804180.5457.29.camel@neptune.sakowski.pl>
Message-ID: <200508122229.55399.glen@delfi.ee>

On Friday 12 August 2005 02:49, Pawe? Sakowski wrote:
> On Fri, 2005-08-12 at 00:25 +0300, Elan Ruusam?e wrote:
> > > There were some small changes in macros, so no need to fake. Will
> > > bumping rpm_macros_rev in rpm.spec and changing BR: rpm-build to
> > > BR: rpmbuild(macros) be sufficient? How does that work with backporting
> > > to AC-branch?
> >
> > yes. true. it won't work until it's really backported. (ie the BR could
> > be satisfied but the actual behaviour not)
> >
> > so perhaps rpmbuild(monoautodeps) is the right choice.
>
> No need to introduce a Provides for every single new feature.
> rpm_macros_rev high enough has always served that purpose. If you're
> concerned that someone will bump macros rev on Ac again without
> backporting the mono changes, mark that as a TODO in AC-branch spec.
> Then again, if you're modifying it, you might port the change altogether
> as well.

hmm.

what about just creating new package rpm-monoprov and requiring that package 
on BR?

$ rpm -qa | grep prov
rpm-perlprov-4.4.1-5
rpm-pythonprov-4.4.1-5

-- 
glen


From wolf.pld at gmail.com  Fri Aug 12 22:24:20 2005
From: wolf.pld at gmail.com (Bartosz Taudul)
Date: Fri, 12 Aug 2005 22:24:20 +0200
Subject: SPECS: tao.spec - auto mono prov/req
In-Reply-To: <200508122229.55399.glen@delfi.ee>
References: <SPECS_tao.spec.1.2@pld-linux.org>
	<200508120025.23753.glen@delfi.ee>
	<1123804180.5457.29.camel@neptune.sakowski.pl>
	<200508122229.55399.glen@delfi.ee>
Message-ID: <20050812202420.GA16635@bajzel>

On Fri, Aug 12, 2005 at 10:29:55PM +0300, Elan Ruusam?e wrote:
> what about just creating new package rpm-monoprov and requiring that package 
> on BR?
What should be in that package? macros.* are provided by rpm-build and
mono-find-* are from mono.

wolf
-- 
  Bartek   .  - Kto tam ?pi?
  Taudul   :  
          .:....................................................................
w o l f @ p l d - l i n u x . o r g            .:. http://wolf.valkyrie.one.pl/


From glen at delfi.ee  Fri Aug 12 22:51:11 2005
From: glen at delfi.ee (Elan =?iso-8859-2?q?Ruusam=E4e?=)
Date: Fri, 12 Aug 2005 23:51:11 +0300
Subject: SPECS: tao.spec - auto mono prov/req
In-Reply-To: <20050812202420.GA16635@bajzel>
References: <SPECS_tao.spec.1.2@pld-linux.org>
	<200508122229.55399.glen@delfi.ee> <20050812202420.GA16635@bajzel>
Message-ID: <200508122351.12000.glen@delfi.ee>

On Friday 12 August 2005 23:24, Bartosz Taudul wrote:
> On Fri, Aug 12, 2005 at 10:29:55PM +0300, Elan Ruusam?e wrote:
> > what about just creating new package rpm-monoprov and requiring that
> > package on BR?
>
> What should be in that package? macros.* are provided by rpm-build and
> mono-find-* are from mono.
so move from mono to mono-find-*


> wolf

-- 
glen


From glen at delfi.ee  Tue Aug 16 18:06:48 2005
From: glen at delfi.ee (Elan =?iso-8859-2?q?Ruusam=E4e?=)
Date: Tue, 16 Aug 2005 19:06:48 +0300
Subject: SPECS: submount.spec - more pl - this rel macro is really needed ?
In-Reply-To: <SPECS_submount.spec.1.2@pld-linux.org>
References: <SPECS_submount.spec.1.1@pld-linux.org>
	<SPECS_submount.spec.1.2@pld-linux.org>
Message-ID: <200508161906.48187.glen@delfi.ee>

On Tuesday 16 August 2005 14:37, spider wrote:
> Author: spider                       Date: Tue Aug 16 11:37:55 2005 GMT
> Module: SPECS                         Tag: HEAD
> ---- Log message:
> - more pl
> - this rel macro is really needed ?

yes, of course! otherwise the Release will grow:

main package:
Release: 1
kernel-foo:
Release %{release}@{kernel_vers_str} 
kernel-foo-smp:
Release %{release}@{kernel_vers_str} 

and the result will be:
foo-1
foo-1 at 2.6.11
foo-smp-1 at 2.6.11@2.6.11


> ---- Files affected:
> SPECS:
>    submount.spec (1.1 -> 1.2)
>
> ---- Diffs:
>
> ================================================================
> Index: SPECS/submount.spec
> diff -u SPECS/submount.spec:1.1 SPECS/submount.spec:1.2
> --- SPECS/submount.spec:1.1	Mon Aug 15 04:28:27 2005
> +++ SPECS/submount.spec	Tue Aug 16 13:37:49 2005
> @@ -6,6 +6,7 @@
>  %bcond_with	verbose		# verbose build (V=1)
>  #
>  Summary:	Automatically mounts and unmounts removable media devices
> +Summary(pl):	Automatycznie montuje i odmontowuje wymienne no?niki danych
>  Name:		submount
>  Version:	0.9
>  %define		_rel	1
> @@ -26,8 +27,15 @@
>  with the Linux 2.6 kernel series. Once installed, it allows removable
>  media drives to be accessed as if they were permanently mounted.
>
> +%description -l pl
> +Submount jest systemem automatycznego montowanie i odmontowania
> +wymiennych no?nik?w danych, takich jak cdromy, dyskietki. Pracuje on
> +z kernelem Linuksa serio 2.6. Raz zainstalowany umo?liwia wyj?c
> +no?nik danych, je?li jest on zamontowany.
> +
>  %package -n kernel-misc-submount
> -Summary:	Submount kernel module
> +Summary:	Submount - kernel module
> +Summary(pl):	Submount - modu?y kernela
>  Release:	%{_rel}@%{_kernel_ver_str}
>  License:	GPL
>  Group:		Base/Kernel
> @@ -36,10 +44,14 @@
>  Provides:	submount(kernel)
>
>  %description -n kernel-misc-submount
> -Submount kernel module.
> +Submount -  kernel module.
> +
> +%description -n kernel-misc-submount -l pl
> +Submount - modu?y kernela
>
>  %package -n kernel-smp-misc-submount
> -Summary:	Submount kernel module
> +Summary:	Submount - smp-kernel module
> +Summary(pl):	Submount - modu?y kernela smp
>  Release:	%{_rel}@%{_kernel_ver_str}
>  License:	GPL
>  Group:		Base/Kernel
> @@ -48,7 +60,10 @@
>  Provides:	submount(kernel)
>
>  %description -n kernel-smp-misc-submount
> -Submount kernel module.
> +Submount - smp-kernel module.
> +
> +%description -n kernel-smp-misc-submount -l pl
> +Submount - modu?y kernela smp.
>
>  %prep
>  %setup -q
> @@ -139,6 +154,10 @@
>  All persons listed below can be reached at <cvs_login>@pld-linux.org
>
>  $Log$
> +Revision 1.2  2005/08/16 11:37:49  spider
> +- more pl
> +- this rel macro is really needed ?
> +
>  Revision 1.1  2005/08/15 02:28:27  charles
>  - initial PLD release
>
> ================================================================
>
> ---- CVS-web:
>     http://cvs.pld-linux.org/SPECS/submount.spec?r1=1.1&r2=1.2&f=u
>
> _______________________________________________
> pld-cvs-commit mailing list
> pld-cvs-commit at lists.pld-linux.org
> http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit

-- 
glen


From wrobell at pld-linux.org  Thu Aug 18 10:54:30 2005
From: wrobell at pld-linux.org (wrobell)
Date: Thu, 18 Aug 2005 09:54:30 +0100
Subject: SOURCES: evince-desktop.patch - show it!
In-Reply-To: <SOURCES_evince_desktop.patch.1.4@pld-linux.org>
References: <SOURCES_evince_desktop.patch.1.3@pld-linux.org>
	<SOURCES_evince_desktop.patch.1.4@pld-linux.org>
Message-ID: <1124355270.2175.9.camel@RECENT-CONVERT>

On Thu, 2005-08-18 at 10:37 +0200, paladine wrote:
> Author: paladine                     Date: Thu Aug 18 08:37:38 2005 GMT
> Module: SOURCES                       Tag: HEAD
> ---- Log message:
> - show it!
> 
> ---- Files affected:
> SOURCES:
>    evince-desktop.patch (1.3 -> 1.4) 
> 
> ---- Diffs:
> 
> ================================================================
> Index: SOURCES/evince-desktop.patch
> diff -u SOURCES/evince-desktop.patch:1.3 SOURCES/evince-desktop.patch:1.4
[...]
> +-NoDisplay=true
> + X-GNOME-DocPath=

from their news file

http://ftp.gnome.org/pub/GNOME/sources/evince/0.3/evince-0.3.3.news
------------------------
Interface Improvements:

    * HIG Fixes 
    * Hide menu entry in .desktop file
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    * Get the correct mime types in the open dialog
------------------------

no offence, but imho they know better.

  wrobell <wrobell at pld-linux.org>



From paladine at pld-dc.org  Thu Aug 18 11:57:47 2005
From: paladine at pld-dc.org (Kamil =?ISO-8859-2?Q?Kosi=F1ski?=)
Date: Thu, 18 Aug 2005 11:57:47 +0200
Subject: SOURCES: evince-desktop.patch - show it!
In-Reply-To: <1124355270.2175.9.camel@RECENT-CONVERT>
References: <SOURCES_evince_desktop.patch.1.3@pld-linux.org>
	<SOURCES_evince_desktop.patch.1.4@pld-linux.org>
	<1124355270.2175.9.camel@RECENT-CONVERT>
Message-ID: <20050818115747.e78cad14.paladine@pld-dc.org>

On Thu, 18 Aug 2005 09:54:30 +0100
wrobell <wrobell at pld-linux.org> wrote:

> from their news file
> 
> http://ftp.gnome.org/pub/GNOME/sources/evince/0.3/evince-0.3.3.news
> ------------------------
> Interface Improvements:
> 
>     * HIG Fixes 
>     * Hide menu entry in .desktop file
>     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>     * Get the correct mime types in the open dialog
> ------------------------
> >
> no offence, but imho they know better.

Probably You're right, but this is stupid! Let's hide gpdf, ggv, eog
and many more ;) Why? Maybe they want to hide it because few last
evince releases were really fucked up? ;) We change Categories,
Comment and even Name in desktop files, so why not change that?

-- 
Kamil (paladine) Kosi?ski
jid: paladine at chrome.pl   mail: paladine at pld-linux.org
PLD Linux developer           http://www.pld-linux.org


From freetz at gmx.net  Thu Aug 18 15:02:38 2005
From: freetz at gmx.net (Fryderyk Dziarmagowski)
Date: Thu, 18 Aug 2005 15:02:38 +0200
Subject: SOURCES: evince-desktop.patch - show it!
In-Reply-To: <1124355270.2175.9.camel@RECENT-CONVERT>
References: <SOURCES_evince_desktop.patch.1.3@pld-linux.org>
	<SOURCES_evince_desktop.patch.1.4@pld-linux.org>
	<1124355270.2175.9.camel@RECENT-CONVERT>
Message-ID: <20050818150238.2d49b67f.freetz@gmx.net>

 --- wrobell <wrobell at pld-linux.org> wrote:

> On Thu, 2005-08-18 at 10:37 +0200, paladine wrote:
> > Author: paladine                     Date: Thu Aug 18 08:37:38 2005 GMT
> > Module: SOURCES                       Tag: HEAD
> > ---- Log message:
> > - show it!
[...]
> from their news file
> 
> http://ftp.gnome.org/pub/GNOME/sources/evince/0.3/evince-0.3.3.news
> ------------------------
> Interface Improvements:
> 
>     * HIG Fixes 
>     * Hide menu entry in .desktop file
>     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>     * Get the correct mime types in the open dialog
> ------------------------
> 
> no offence, but imho they know better.

thinking this way, we don't need a menu. it's a _bug_ and it's
already fixed by Kamil.

http://bugzilla.gnome.org/show_bug.cgi?id=312399

-- 
Fryderyk Dziarmagowski


From wrobell at pld-linux.org  Thu Aug 18 15:07:48 2005
From: wrobell at pld-linux.org (wrobell)
Date: Thu, 18 Aug 2005 14:07:48 +0100
Subject: SOURCES: evince-desktop.patch - show it!
In-Reply-To: <20050818150238.2d49b67f.freetz@gmx.net>
References: <SOURCES_evince_desktop.patch.1.3@pld-linux.org>
	<SOURCES_evince_desktop.patch.1.4@pld-linux.org>
	<1124355270.2175.9.camel@RECENT-CONVERT>
	<20050818150238.2d49b67f.freetz@gmx.net>
Message-ID: <1124370468.2175.26.camel@RECENT-CONVERT>

On Thu, 2005-08-18 at 15:02 +0200, Fryderyk Dziarmagowski wrote:
>  --- wrobell <wrobell at pld-linux.org> wrote:
> 
> > On Thu, 2005-08-18 at 10:37 +0200, paladine wrote:
> > > Author: paladine                     Date: Thu Aug 18 08:37:38 2005 GMT
> > > Module: SOURCES                       Tag: HEAD
> > > ---- Log message:
> > > - show it!
> [...]
> > from their news file
> > 
> > http://ftp.gnome.org/pub/GNOME/sources/evince/0.3/evince-0.3.3.news
> > ------------------------
> > Interface Improvements:
> > 
> >     * HIG Fixes 
> >     * Hide menu entry in .desktop file
> >     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >     * Get the correct mime types in the open dialog
> > ------------------------
> > 
> > no offence, but imho they know better.
> 
> thinking this way, we don't need a menu. it's a _bug_ and it's
> already fixed by Kamil.
> 
> http://bugzilla.gnome.org/show_bug.cgi?id=312399

it could be removed from menu (gnome menu in gnome panel).
for me having viewer in menu does not make sense. of course,
according to bug 312399 it removes evince entry from everywhere,
so let's see how they will resolve this issue.

  wrobell <wrobell at pld-linux.org>



From wolf.pld at gmail.com  Thu Aug 18 18:12:49 2005
From: wolf.pld at gmail.com (Bartosz Taudul)
Date: Thu, 18 Aug 2005 18:12:49 +0200
Subject: SPECS: bluez-utils.spec - todo security
In-Reply-To: <200508181804.02561.pluto@agmk.net>
References: <SPECS_bluez_utils.spec.1.29@pld-linux.org>
	<SPECS_bluez_utils.spec.1.30@pld-linux.org>
	<200508181804.02561.pluto@agmk.net>
Message-ID: <20050818161249.GA15810@bajzel>

On Thu, Aug 18, 2005 at 06:04:02PM +0200, Pawel Sikora wrote:
> >  Revision 1.23  2004/11/11 19:48:18  saq
> > -- mass commit: using %%{epoch} without explicit Epoch: declaration
> > +- mass commit: using %{epoch} without explicit Epoch: declaration
> don't use macros in changelog.
Why? Macros are disabled in changelogs.

wolf
-- 
  Bartek   .  - O, ty! Przyjdziesz, czy mam rzuca??
  Taudul   :  
          .:....................................................................
w o l f @ p l d - l i n u x . o r g            .:. http://wolf.valkyrie.one.pl/


From adamg at biomerieux.pl  Thu Aug 18 19:00:17 2005
From: adamg at biomerieux.pl (Adam =?iso-8859-2?Q?Go=B3=EAbiowski?=)
Date: Thu, 18 Aug 2005 19:00:17 +0200
Subject: SPECS: bluez-utils.spec - todo security
In-Reply-To: <200508181804.02561.pluto@agmk.net>
References: <SPECS_bluez_utils.spec.1.29@pld-linux.org>
	<SPECS_bluez_utils.spec.1.30@pld-linux.org>
	<200508181804.02561.pluto@agmk.net>
Message-ID: <20050818170017.GA10161@mysza.eu.org>

On Thu, Aug 18, 2005 at 06:04:02PM +0200, Pawel Sikora wrote:
> On Thursday 18 of August 2005 17:59, glen wrote:
> > Author: glen                         Date: Thu Aug 18 15:59:28 2005 GMT
> 
> >  Revision 1.23  2004/11/11 19:48:18  saq
> > -- mass commit: using %%{epoch} without explicit Epoch: declaration
> > +- mass commit: using %{epoch} without explicit Epoch: declaration
> 
> don't use macros in changelog. %% comment is correct.

Actually it's quite ok for us:
[builder at agmk SPECS]$ cat test.spec
Name: test
Version: 1
Release: 1
Group: a
License: none
Summary: .
%description
%files
%changelog 
* %{date} PLD Team <feedback at pld-linux.org>
- %{name} %{epoch}
[builder at agmk SPECS]$ rpmbuild -bb test.spec
Processing files: test-1-1
Checking for unpackaged file(s): /usr/lib/rpm/check-files %{buildroot}
warning: Could not canonicalize hostname: agmk
Wrote: /home/users/builder/rpm/RPMS/test-1-1.i686.rpm
[builder at agmk SPECS]$ rpm -qp --changelog ../RPMS/test-1-1.i686.rpm 
* Thu Aug 18 2005 PLD Team <feedback at pld-linux.org>
- %{name} %{epoch}

[builder at agmk SPECS]$ 

-- 
http://www.mysza.eu.org/ | Everybody needs someone sure, someone true,
   PLD Linux developer   | Everybody needs some solid rock, I know I do.


From glen at delfi.ee  Thu Aug 18 22:15:35 2005
From: glen at delfi.ee (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Thu, 18 Aug 2005 23:15:35 +0300
Subject: SPECS: php-pear-HTML_AJAX.spec - BR: sed 4.0, use __sed macro
In-Reply-To: <SPECS_php_pear_HTML_AJAX.spec.1.2@pld-linux.org>
References: <SPECS_php_pear_HTML_AJAX.spec.1.1@pld-linux.org>
	<SPECS_php_pear_HTML_AJAX.spec.1.2@pld-linux.org>
Message-ID: <200508182315.36150.glen@delfi.ee>

On Thursday 18 August 2005 23:09, darekr wrote:
> Author: darekr                       Date: Thu Aug 18 20:09:42 2005 GMT
> Module: SPECS                         Tag: HEAD
> ---- Log message:
> - BR: sed 4.0, use __sed macro
what for?
there's a lot of sed usage without macros so far that i know.
put it into adapter.awk?

[...]
> -sed -i -e 's#@data-dir@#%{php_pear_dir}#g' -e "s#'HTML_AJAX'#'HTML'.DIRECTORY_SEPARATOR.'AJAX'#g" \
> +%{__sed} -i -e 's#@data-dir@#%{php_pear_dir}#g' -e "s#'HTML_AJAX'#'HTML'.DIRECTORY_SEPARATOR.'AJAX'#g" \
> ????????$RPM_BUILD_ROOT%{php_pear_dir}/%{_class}/AJAX/Server.php

-- 
glen


From twittner at o2.pl  Thu Aug 18 23:06:06 2005
From: twittner at o2.pl (Tomasz Wittner)
Date: Thu, 18 Aug 2005 23:06:06 +0200
Subject: SPECS: php-pear-HTML_AJAX.spec - BR: sed 4.0, use __sed macro
In-Reply-To: <200508182315.36150.glen@delfi.ee>
References: <SPECS_php_pear_HTML_AJAX.spec.1.1@pld-linux.org>
	<SPECS_php_pear_HTML_AJAX.spec.1.2@pld-linux.org>
	<200508182315.36150.glen@delfi.ee>
Message-ID: <200508182306.07135.twittner@o2.pl>

On Thu 18. of August 2005 22:15, Elan Ruusam?e wrote:
> On Thursday 18 August 2005 23:09, darekr wrote:
> > Author: darekr                       Date: Thu Aug 18 20:09:42 2005 GMT
> > Module: SPECS                         Tag: HEAD
> > ---- Log message:
> > - BR: sed 4.0, use __sed macro
> what for?
By what reasons We use %{__make}? - it is just /usr/bin/make .
I've found some justifications:
http://archive.netbsd.se/?ml=viewcvs-dev&a=2002-05&m=406158
https://www.redhat.com/archives/fedora-test-list/2003-August/msg01306.html
(PLD also is mentioned ;)
Personally, on my FreeBSD box I have %_sed definied as /usr/local/bin/gsed
because PLD relies on GNU sed which is differ from /bin/sed which comes with
fbsd base system so using macros instead plain commands invokation was more
convenient for me (I don't use fbsd at the moment).
> there's a lot of sed usage without macros so far that i know.
> put it into adapter.awk?
Do it, if you please, but mayby wait some time for other's people opinions.
> 
> [...]
> > -sed -i -e 's#@data-dir@#%{php_pear_dir}#g' -e "s#'HTML_AJAX'#'HTML'.DIRECTORY_SEPARATOR.'AJAX'#g" \
> > +%{__sed} -i -e 's#@data-dir@#%{php_pear_dir}#g' -e "s#'HTML_AJAX'#'HTML'DIRECTORY_SEPARATOR.'AJAX'#g" \
> > ????????$RPM_BUILD_ROOT%{php_pear_dir}/%{_class}/AJAX/Server.php
> 

-- 
Tomasz Wittner


From saq at pld-linux.org  Fri Aug 19 13:28:12 2005
From: saq at pld-linux.org (=?iso-8859-2?Q?Pawe=B3?= Sakowski)
Date: Fri, 19 Aug 2005 13:28:12 +0200
Subject: SPECS: php-pear-HTML_AJAX.spec - BR: sed 4.0, use __sed macro
In-Reply-To: <200508182306.07135.twittner@o2.pl>
References: <SPECS_php_pear_HTML_AJAX.spec.1.1@pld-linux.org>
	<SPECS_php_pear_HTML_AJAX.spec.1.2@pld-linux.org>
	<200508182315.36150.glen@delfi.ee> <200508182306.07135.twittner@o2.pl>
Message-ID: <1124450892.27254.0.camel@neptune.sakowski.pl>

On Thu, 2005-08-18 at 23:06 +0200, Tomasz Wittner wrote:
> By what reasons We use %{__make}? - it is just /usr/bin/make .

Until redefined as "/usr/bin/make -j2" for faster SMP builds.

-- 
Pawe? Sakowski <saq at pld-linux.org>
PLD Linux Distribution



From twittner at o2.pl  Fri Aug 19 18:10:45 2005
From: twittner at o2.pl (Tomasz Wittner)
Date: Fri, 19 Aug 2005 18:10:45 +0200
Subject: SPECS: php-pear-HTML_AJAX.spec - BR: sed 4.0, use __sed macro
In-Reply-To: <1124450892.27254.0.camel@neptune.sakowski.pl>
References: <SPECS_php_pear_HTML_AJAX.spec.1.1@pld-linux.org>
	<200508182306.07135.twittner@o2.pl>
	<1124450892.27254.0.camel@neptune.sakowski.pl>
Message-ID: <200508191810.46309.twittner@o2.pl>

On Fri 19. of August 2005 13:28, Pawe? Sakowski wrote:
> On Thu, 2005-08-18 at 23:06 +0200, Tomasz Wittner wrote:
> > By what reasons We use %{__make}? - it is just /usr/bin/make .
> 
> Until redefined as "/usr/bin/make -j2" for faster SMP builds.
> 
Thank you for make me aware of it. BTW `-jn' (when n > 1 of course) speed up 
builds on multiprocessor computers only? Quoting from:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
"
On a typical single-CPU machine you would run:

# make -j4 buildworld

make(1) will then have up to 4 processes running at any one time. Empirical 
evidence posted to the mailing lists shows this generally gives the best 
performance benefit.
"
Additionally I use ccache - I think I could take advantage of `make -jn' for 
some repeatitive builds.

-- 
Tomasz Wittner


From aredridel at nbtsc.org  Sat Aug 20 21:52:33 2005
From: aredridel at nbtsc.org (Aredridel)
Date: Sat, 20 Aug 2005 13:52:33 -0600
Subject: An Invitation
Message-ID: <20050820195233.GA10864@mail.nbtsc.org>

A friend and developer of Archlinux and I have been working on putting
together a site to discuss and work out distribution development issues
with people from all different distributions and perspectives.

Anyone working on PLD is welcome to join -- we need some thoughtful
posts to get the ball rolling, and since PLD was one of the inspirations
for Arch, it might even be a bit of fun.

The topics are not restricted -- thoughts about packaging certain kinds
of things, issues in dealing with certain common packages, thoughtful
ideas about different ways distributions and communities can be
structured, ideas to share the good ideas across distros, all are
welcome. 

The site is lightly moderated to help keep trolling down -- it's not to
be a forum to help users choose a distro. It's for developers to talk to
each other. Any reasonable content will make it onto the main page with
no trouble.

Anyway, please join and share your thoughts. Correct misunderstandngs in
what's there, and add your own. With luck, it can become a good resource
and improve everyone's processes.

Give it a look -- http://distrodev.org/

Aredridel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: </mailman/pipermail/pld-devel-en/attachments/20050820/457af58b/attachment.sig>

From michal.moskal at gmail.com  Sun Aug 21 14:20:47 2005
From: michal.moskal at gmail.com (Michal Moskal)
Date: Sun, 21 Aug 2005 14:20:47 +0200
Subject: cvs move
In-Reply-To: <200508112140.18069.glen@delfi.ee>
References: <200508112140.18069.glen@delfi.ee>
Message-ID: <b323bb980508210520a6e219e@mail.gmail.com>

On 8/11/05, Elan Ruusam?e <glen at delfi.ee> wrote:
> mv SPECS/Apache-FileManager.spec,v SPECS/perl-Apache-FileManager.spec,v

Done.

Sorry for the lag, I was in the Soviet Union.

-- 
   Michal Moskal,
   http://nemerle.org/~malekith/


From glen at delfi.ee  Tue Aug 23 12:35:16 2005
From: glen at delfi.ee (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Tue, 23 Aug 2005 13:35:16 +0300
Subject: horde packages
Message-ID: <200508231335.16364.glen@delfi.ee>

hi

anybody against of renaming all horde packages with horde- prefix?
as there are collisions without.

like passwd, nag already are packages in PLD.

-- 
glen


From twittner at o2.pl  Tue Aug 23 20:29:47 2005
From: twittner at o2.pl (Tomasz Wittner)
Date: Tue, 23 Aug 2005 20:29:47 +0200
Subject: SPECS: rpm-macros.spec (HEAD)
In-Reply-To: <rpm-macros.spec.1.19@cvs.pld-linux.org>
References: <rpm-macros.spec.1.18@cvs.pld-linux.org>
	<rpm-macros.spec.1.19@cvs.pld-linux.org>
Message-ID: <200508232029.47694.twittner@o2.pl>

On Tue 23. of August 2005 20:19, glen wrote:
> Module name:	SPECS
> Changes by:	glen	05/08/23 20:19:50
> 
> Modified files:
> 	rpm-macros.spec
> 
> Log message:
> - rpm macros 1.233
>
What's new in 1.233 ?

-- 
Tomasz Wittner


From glen at delfi.ee  Tue Aug 23 21:43:56 2005
From: glen at delfi.ee (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Tue, 23 Aug 2005 22:43:56 +0300
Subject: SPECS: rpm-macros.spec (HEAD)
In-Reply-To: <200508232029.47694.twittner@o2.pl>
References: <rpm-macros.spec.1.18@cvs.pld-linux.org>
	<rpm-macros.spec.1.19@cvs.pld-linux.org>
	<200508232029.47694.twittner@o2.pl>
Message-ID: <200508232243.56430.glen@delfi.ee>

On Tuesday 23 August 2005 21:29, Tomasz Wittner wrote:
> On Tue 23. of August 2005 20:19, glen wrote:
> > Module name:	SPECS
> > Changes by:	glen	05/08/23 20:19:50
> >
> > Modified files:
> > 	rpm-macros.spec
> >
> > Log message:
> > - rpm macros 1.233
>
> What's new in 1.233 ?
cvs log rpm.macros :)

i just synced it as rpm.spec already contained newer rpm macros revision.

-- 
glen


From glen at delfi.ee  Wed Aug 24 09:25:30 2005
From: glen at delfi.ee (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Wed, 24 Aug 2005 10:25:30 +0300
Subject: SPECS: horde-passwd.spec - added one more noautoreq - please do
	no...
In-Reply-To: <SPECS_horde_passwd.spec.1.20@pld-linux.org>
References: <SPECS_horde_passwd.spec.1.19@pld-linux.org>
	<SPECS_horde_passwd.spec.1.20@pld-linux.org>
Message-ID: <200508241025.31043.glen@delfi.ee>

On Wednesday 24 August 2005 00:51, paszczus wrote:
> Author: paszczus                     Date: Tue Aug 23 21:51:51 2005 GMT
> Module: SPECS                         Tag: HEAD
> ---- Log message:
> - added one more noautoreq - please do not remove it...

and what is the reason?
it is not fake dep, Crypt_CHAP is used to generate samba password hashes.

>
> ---- Files affected:
> SPECS:
>    horde-passwd.spec (1.19 -> 1.20)
>
> ---- Diffs:
>
> ================================================================
> Index: SPECS/horde-passwd.spec
> diff -u SPECS/horde-passwd.spec:1.19 SPECS/horde-passwd.spec:1.20
> --- SPECS/horde-passwd.spec:1.19	Tue Aug 23 23:22:27 2005
> +++ SPECS/horde-passwd.spec	Tue Aug 23 23:51:45 2005
> @@ -31,7 +31,7 @@
>
>  # horde accesses it directly in help->about
>  %define		_noautocompressdoc  CREDITS
> -%define		_noautoreq	'pear(Horde/.*)'
> +%define		_noautoreq	'pear(Horde/.*)' 'pear(Crypt/CHAP.php)'
>
>  %define		hordedir	/usr/share/horde
>  %define		_sysconfdir	/etc/horde.org
> @@ -142,6 +142,9 @@
>  All persons listed below can be reached at <cvs_login>@pld-linux.org
>
>  $Log$
> +Revision 1.20  2005/08/23 21:51:45  paszczus
> +- added one more noautoreq - please do not remove it...
> +
>  Revision 1.19  2005/08/23 21:22:27  glen
>  - don't package .htaccess
>
> ================================================================
>
> ---- CVS-web:
>     http://cvs.pld-linux.org/SPECS/horde-passwd.spec?r1=1.19&r2=1.20&f=u
>
> _______________________________________________
> pld-cvs-commit mailing list
> pld-cvs-commit at lists.pld-linux.org
> http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit

-- 
glen


From adamg at biomerieux.pl  Wed Aug 24 18:42:07 2005
From: adamg at biomerieux.pl (Adam =?iso-8859-2?Q?Go=B3=EAbiowski?=)
Date: Wed, 24 Aug 2005 18:42:07 +0200
Subject: [adamg@pld-linux.org: DISTFILES: ERRORS: lkcp-0.5.3.tar.bz2]
Message-ID: <20050824164207.GA10824@mysza.eu.org>

I was just about to commit a fix to cvs::admin/distfiles/file-fetcher.pl
but thought it was better to ask. So, do we want to add that
--no-check-certificate option? After all, it's the developer who should
verify given site.

----- Forwarded message from adamg <adamg at pld-linux.org> -----

From: adamg <adamg at pld-linux.org>
To: pld-cvs-commit at pld-linux.org
Cc: adamg at pld-linux.org
Subject: DISTFILES: ERRORS: lkcp-0.5.3.tar.bz2
Date: Wed, 24 Aug 2005 18:23:32 +0200

wget -nv -O ./tmp/29b9c60d-8565-4518-969e-95516b37d96e/020f788b8c9ac52636b357e8929f7e30/lkcp-0.5.3.tar.bz2 "http://webspace.utexas.edu/hyoussef/www/lkcp-0.5.3.tar.bz2":
ERROR: Certificate verification error for webspace.utexas.edu: unable to get local issuer certificate
To connect to webspace.utexas.edu insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.


FATAL: http://webspace.utexas.edu/hyoussef/www/lkcp-0.5.3.tar.bz2 (020f788b8c9ac52636b357e8929f7e30) was not fetched (wget -nv -O ./tmp/29b9c60d-8565-4518-969e-95516b37d96e/020f788b8c9ac52636b357e8929f7e30/lkcp-0.5.3.tar.bz2 "http://webspace.utexas.edu/hyoussef/www/lkcp-0.5.3.tar.bz2": ERROR: Certificate verification error for webspace.utexas.edu: unable to get local issuer certificate
To connect to webspace.utexas.edu insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.
)

Files fetched: 0



-- 
Virtually Yours: distfiles.


----- End forwarded message -----

-- 
http://www.mysza.eu.org/ | Everybody needs someone sure, someone true,
   PLD Linux developer   | Everybody needs some solid rock, I know I do.


From arekm at pld-linux.org  Thu Aug 25 10:34:26 2005
From: arekm at pld-linux.org (Arkadiusz Miskiewicz)
Date: Thu, 25 Aug 2005 10:34:26 +0200
Subject: [adamg@pld-linux.org: DISTFILES: ERRORS: lkcp-0.5.3.tar.bz2]
In-Reply-To: <20050824164207.GA10824@mysza.eu.org>
References: <20050824164207.GA10824@mysza.eu.org>
Message-ID: <200508251034.26311.arekm@pld-linux.org>

On Wednesday 24 of August 2005 18:42, Adam Go??biowski wrote:
> I was just about to commit a fix to cvs::admin/distfiles/file-fetcher.pl
> but thought it was better to ask. So, do we want to add that
> --no-check-certificate option? After all, it's the developer who should
> verify given site.
+1

-- 
Arkadiusz Mi?kiewicz                    PLD/Linux Team
http://www.t17.ds.pwr.wroc.pl/~misiek/  http://ftp.pld-linux.org/


From glen at delfi.ee  Thu Aug 25 17:43:49 2005
From: glen at delfi.ee (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Thu, 25 Aug 2005 18:43:49 +0300
Subject: SPECS: horde.spec - added GeoIP database
In-Reply-To: <SPECS_horde.spec.1.98@pld-linux.org>
References: <SPECS_horde.spec.1.97@pld-linux.org>
	<SPECS_horde.spec.1.98@pld-linux.org>
Message-ID: <200508251843.49481.glen@delfi.ee>

On Thursday 25 August 2005 18:35, paszczus wrote:
> Author: paszczus                     Date: Thu Aug 25 15:35:51 2005 GMT
> Module: SPECS                         Tag: HEAD
> ---- Log message:
> - added GeoIP database
is the database license same as horde.spec?
if not, must be added to License field


From gotar at polanet.pl  Fri Aug 26 02:43:18 2005
From: gotar at polanet.pl (Tomasz Pala)
Date: Fri, 26 Aug 2005 02:43:18 +0200
Subject: http://ftp.pld-linux.org/ via proxy
Message-ID: <20050826004318.GA3506@os>

Test Page for Apache Installation

If you can see this, it means that the installation of the Apache web
server software on this system was successful. You may now add content
to this directory and replace this page.
[...]


Any ideas what's messed up?

-- 
GoTaR <priv0.onet.pl->gotar>        http://vfmg.sourceforge.net/
                                    http://tccs.sourceforge.net/


From adamg at biomerieux.pl  Fri Aug 26 16:32:40 2005
From: adamg at biomerieux.pl (Adam =?iso-8859-2?Q?Go=B3=EAbiowski?=)
Date: Fri, 26 Aug 2005 16:32:40 +0200
Subject: http://ftp.pld-linux.org/ via proxy
In-Reply-To: <20050826004318.GA3506@os>
References: <20050826004318.GA3506@os>
Message-ID: <20050826143240.GB8222@mysza.eu.org>

On Fri, Aug 26, 2005 at 02:43:18AM +0200, Tomasz Pala wrote:
> If you can see this, it means that the installation of the Apache web
> server software on this system was successful. You may now add content
> to this directory and replace this page.
> [...]
> 
> 
> Any ideas what's messed up?

Yep, in your network, ftp.pld-linux.org points to something else than
ep09.pld-linux.org. I just checked and it's probably ftp mirror at
icpnet. If you'd like to use http based access to ftp, use
ftp1.pld-linux.org which allways points to ep09. 

Or bug ftp admins to configure their httpd ...

-- 
http://www.mysza.eu.org/ | Everybody needs someone sure, someone true,
   PLD Linux developer   | Everybody needs some solid rock, I know I do.


From robert.wozny at gmail.com  Fri Aug 26 16:40:02 2005
From: robert.wozny at gmail.com (robert j. wozny)
Date: Fri, 26 Aug 2005 16:40:02 +0200
Subject: http://ftp.pld-linux.org/ via proxy
References: <20050826004318.GA3506@os> <20050826143240.GB8222@mysza.eu.org>
Message-ID: <gnus.x7k6i8lq2l.fsf@hell.ziew.org>

adamg at biomerieux.pl (Adam Go??biowski):

[...]
> Or bug ftp admins to configure their httpd ...

so, adamg, please, fix it 8-] 

-- 
robert j. wozny
[far far away...]


From adamg at biomerieux.pl  Fri Aug 26 17:17:50 2005
From: adamg at biomerieux.pl (Adam =?iso-8859-2?Q?Go=B3=EAbiowski?=)
Date: Fri, 26 Aug 2005 17:17:50 +0200
Subject: http://ftp.pld-linux.org/ via proxy
In-Reply-To: <gnus.x7k6i8lq2l.fsf@hell.ziew.org>
References: <20050826004318.GA3506@os> <20050826143240.GB8222@mysza.eu.org>
	<gnus.x7k6i8lq2l.fsf@hell.ziew.org>
Message-ID: <20050826151750.GD8222@mysza.eu.org>

On Fri, Aug 26, 2005 at 04:40:02PM +0200, robert j. wozny wrote:
> adamg at biomerieux.pl (Adam Go??biowski):
> 
> [...]
> > Or bug ftp admins to configure their httpd ...
> 
> so, adamg, please, fix it 8-] 

-ENOTENOUGHMANA :)

-- 
http://www.mysza.eu.org/ | Everybody needs someone sure, someone true,
   PLD Linux developer   | Everybody needs some solid rock, I know I do.


From adamg at biomerieux.pl  Fri Aug 26 18:28:51 2005
From: adamg at biomerieux.pl (Adam =?iso-8859-2?Q?Go=B3=EAbiowski?=)
Date: Fri, 26 Aug 2005 18:28:51 +0200
Subject: [adamg@pld-linux.org: DISTFILES: ERRORS: lkcp-0.5.3.tar.bz2]
In-Reply-To: <200508251034.26311.arekm@pld-linux.org>
References: <20050824164207.GA10824@mysza.eu.org>
	<200508251034.26311.arekm@pld-linux.org>
Message-ID: <20050826162851.GE8222@mysza.eu.org>

On Thu, Aug 25, 2005 at 10:34:26AM +0200, Arkadiusz Miskiewicz wrote:
> On Wednesday 24 of August 2005 18:42, Adam Go??biowski wrote:
> > I was just about to commit a fix to cvs::admin/distfiles/file-fetcher.pl
> > but thought it was better to ask. So, do we want to add that
> > --no-check-certificate option? After all, it's the developer who should
> > verify given site.
> +1

Ok, done. 
Do we have distfiles admin? malekith (cc-ed)?

-- 
http://www.mysza.eu.org/ | Everybody needs someone sure, someone true,
   PLD Linux developer   | Everybody needs some solid rock, I know I do.


From gotar at polanet.pl  Fri Aug 26 17:06:05 2005
From: gotar at polanet.pl (Tomasz Pala)
Date: Fri, 26 Aug 2005 17:06:05 +0200
Subject: http://ftp.pld-linux.org/ via proxy
In-Reply-To: <20050826143240.GB8222@mysza.eu.org>
References: <20050826004318.GA3506@os> <20050826143240.GB8222@mysza.eu.org>
Message-ID: <20050826150605.GA1982@os>

On Fri, Aug 26, 2005 at 16:32:40 +0200, Adam Go??biowski wrote:

> > Any ideas what's messed up?
> 
> Yep, in your network,

In my 3 independent networks;) And I really have no idea how it is
possible that direct access works, but proxy fails to get it (in 2
cases), one machine cannot with nor without proxy and one works...

> ftp.pld-linux.org points to something else than
> ep09.pld-linux.org. I just checked and it's probably ftp mirror at
> icpnet. If you'd like to use http based access to ftp, use
> ftp1.pld-linux.org which allways points to ep09. 

Hey, I don't care what points where, anyway it changes too often (maybe
some ftp-current-dns-settings.rpm? ;P) and that's why DNS has been
invented. I-the-user just want to have http access (as poldek doesn't
work with proxy on ftp://) and it WAS working, now something was broken.

> Or bug ftp admins to configure their httpd ...

Now it's even better:

~:  wget -O - http://ftp.pld-linux.org
--17:05:26--  http://ftp.pld-linux.org/
           => `-'
Resolving ftp.pld-linux.org... 149.156.143.253
Connecting to ftp.pld-linux.org|149.156.143.253|:80... failed: No route to host.

~:  ping ftp.pld-linux.org
PING ftp.pld-linux.org (149.156.143.253) 56(84) bytes of data.
>From 149.156.6.33 icmp_seq=2 Packet filtered

;PPPP

-- 
GoTaR <priv0.onet.pl->gotar>        http://vfmg.sourceforge.net/
                                    http://tccs.sourceforge.net/


From michal.moskal at gmail.com  Sat Aug 27 13:13:32 2005
From: michal.moskal at gmail.com (Michal Moskal)
Date: Sat, 27 Aug 2005 13:13:32 +0200
Subject: [adamg@pld-linux.org: DISTFILES: ERRORS: lkcp-0.5.3.tar.bz2]
In-Reply-To: <20050826162851.GE8222@mysza.eu.org>
References: <20050824164207.GA10824@mysza.eu.org>
	<200508251034.26311.arekm@pld-linux.org>
	<20050826162851.GE8222@mysza.eu.org>
Message-ID: <b323bb9805082704132aec5857@mail.gmail.com>

On 8/26/05, Adam Go??biowski <adamg at biomerieux.pl> wrote:
> On Thu, Aug 25, 2005 at 10:34:26AM +0200, Arkadiusz Miskiewicz wrote:
> > On Wednesday 24 of August 2005 18:42, Adam Go??biowski wrote:
> > > I was just about to commit a fix to cvs::admin/distfiles/file-fetcher.pl
> > > but thought it was better to ask. So, do we want to add that
> > > --no-check-certificate option? After all, it's the developer who should
> > > verify given site.
> > +1
> 
> Ok, done.
> Do we have distfiles admin? malekith (cc-ed)?

cvs up done.

-- 
   Michal Moskal,
   http://nemerle.org/~malekith/

From gotar at polanet.pl  Sat Aug 27 12:38:51 2005
From: gotar at polanet.pl (Tomasz Pala)
Date: Sat, 27 Aug 2005 12:38:51 +0200
Subject: http://ftp.pld-linux.org/ via proxy
In-Reply-To: <20050826151750.GD8222@mysza.eu.org>
References: <20050826004318.GA3506@os> <20050826143240.GB8222@mysza.eu.org>
	<gnus.x7k6i8lq2l.fsf@hell.ziew.org>
	<20050826151750.GD8222@mysza.eu.org>
Message-ID: <20050827103851.GA188@os>

On Fri, Aug 26, 2005 at 17:17:50 +0200, Adam Go??biowski wrote:

> > so, adamg, please, fix it 8-] 
> 
> -ENOTENOUGHMANA :)

It worked for me without proxy because I'd got it in hosts file. Now,
is there any chance someone would fix it or sth?
Meanwhile I'll set static hosts for some of my proxy servers as it's
much easier to add 3 lines than changing 2*12 and refetching indexes or
renaming index directories...

Polpak:

~: host ftp.pld-linux.org
ftp.pld-linux.org is an alias for ftp1.pld-linux.org.
ftp1.pld-linux.org is an alias for ftp.sk.pld-linux.org.
ftp.sk.pld-linux.org has address 217.73.17.117
~: host 217.73.17.117    
117.17.73.217.in-addr.arpa domain name pointer ep09.pld-linux.org.

GTS:

~: host ftp.pld-linux.org
ftp.pld-linux.org is an alias for ftp5.pld-linux.org.
ftp5.pld-linux.org has address 62.21.96.15
ftp.pld-linux.org is an alias for ftp5.pld-linux.org.
ftp.pld-linux.org is an alias for ftp5.pld-linux.org.
~: host 62.21.96.15
15.96.21.62.in-addr.arpa domain name pointer ontario.icpnet.pl.

Futuro/Crowley/ceti:

~: host ftp.pld-linux.org
ftp.pld-linux.org is an alias for ftp5.pld-linux.org.
ftp5.pld-linux.org has address 62.21.96.15

-- 
GoTaR <priv0.onet.pl->gotar>        http://vfmg.sourceforge.net/
                                    http://tccs.sourceforge.net/


From adamg at biomerieux.pl  Mon Aug 29 09:16:28 2005
From: adamg at biomerieux.pl (Adam =?iso-8859-2?Q?Go=B3=EAbiowski?=)
Date: Mon, 29 Aug 2005 09:16:28 +0200
Subject: http://ftp.pld-linux.org/ via proxy
In-Reply-To: <20050826150605.GA1982@os>
References: <20050826004318.GA3506@os> <20050826143240.GB8222@mysza.eu.org>
	<20050826150605.GA1982@os>
Message-ID: <20050829071628.GB14590@mysza.eu.org>

On Fri, Aug 26, 2005 at 05:06:05PM +0200, Tomasz Pala wrote:
> > ftp.pld-linux.org points to something else than
> > ep09.pld-linux.org. I just checked and it's probably ftp mirror at
> > icpnet. If you'd like to use http based access to ftp, use
> > ftp1.pld-linux.org which allways points to ep09. 
> 
> Hey, I don't care what points where, anyway it changes too often (maybe
> some ftp-current-dns-settings.rpm? ;P) and that's why DNS has been
> invented. 

But DNS changes too, and the idea behind recent changes was to bring us
to the situation where querying for ftp.pld-linux.org gives us a server
that is theoretically best for us. 

> I-the-user just want to have http access (as poldek doesn't
> work with proxy on ftp://) and it WAS working, now something was broken.

fill a bug report :)
But you're right, http access should work on all of our official ftp
mirrors. And as I see, it works everywhere except ftp4, which currently
has problems with its hdds. 

> > Or bug ftp admins to configure their httpd ...
> 
> Now it's even better:
> 
> ~:  wget -O - http://ftp.pld-linux.org
> --17:05:26--  http://ftp.pld-linux.org/
> ~:  ping ftp.pld-linux.org
> PING ftp.pld-linux.org (149.156.143.253) 56(84) bytes of data.
> >From 149.156.6.33 icmp_seq=2 Packet filtered
> 

And I guess that's because tunnel between Cracow University of
Technology and ep09 was down for some reasons (temporary problems?)

Anyway http://ftp5.pld-linux.org/ is now working. 

-- 
http://www.mysza.eu.org/ | Everybody needs someone sure, someone true,
   PLD Linux developer   | Everybody needs some solid rock, I know I do.


From spider at linux.pl  Mon Aug 29 12:58:29 2005
From: spider at linux.pl (Piotr Skwarna)
Date: Mon, 29 Aug 2005 12:58:29 +0200
Subject: kernel building -bug report
Message-ID: <4312EA55.509@linux.pl>

spider at zero SPECS$ ./builder -bb -r LINUX_2_6 kernel.spec --without smp 
--without pcmcia --with grsecurity --target i686

[CUT]

+ cd linux-2.6.12.5
+ 
DOCDIR=/home/users/spider/tmp/kernel-grsecurity-2.6.12.5-root-spider/usr/share/doc/kernel-grsecurity-2.6.12.5
+ export DOCDIR
+ rm -rf 
/home/users/spider/tmp/kernel-grsecurity-2.6.12.5-root-spider/usr/share/doc/kernel-grsecurity-2.6.12.5
+ /bin/mkdir -p 
/home/users/spider/tmp/kernel-grsecurity-2.6.12.5-root-spider/usr/share/doc/kernel-grsecurity-2.6.12.5
+ cp -pr FAQ-pl 
/home/users/spider/tmp/kernel-grsecurity-2.6.12.5-root-spider/usr/share/doc/kernel-grsecurity-2.6.12.5
+ /usr/lib/rpm/compress-doc
Compressing documentation in 
/home/users/spider/tmp/kernel-grsecurity-2.6.12.5-root-spider/usr/share/doc/kernel-grsecurity-2.6.12.5...
./FAQ-pl
Documentation compressed.
+ exit 0
Parsing SELinux file contexts skipped: 
/etc/security/selinux/src/policy/file_contexts/file_contexts: No such 
file or directory
Processing files: kernel-grsecurity-drm-2.6.12.5-0.5
Parsing SELinux file contexts skipped: 
/etc/security/selinux/src/policy/file_contexts/file_contexts: No such 
file or directory
Processing files: kernel-grsecurity-sound-alsa-2.6.12.5-0.5
Parsing SELinux file contexts skipped: 
/etc/security/selinux/src/policy/file_contexts/file_contexts: No such 
file or directory
Processing files: kernel-grsecurity-sound-oss-2.6.12.5-0.5
Parsing SELinux file contexts skipped: 
/etc/security/selinux/src/policy/file_contexts/file_contexts: No such 
file or directory
Processing files: kernel-grsecurity-headers-2.6.12.5-0.5
Parsing SELinux file contexts skipped: 
/etc/security/selinux/src/policy/file_contexts/file_contexts: No such 
file or directory
Processing files: kernel-grsecurity-module-build-2.6.12.5-0.5
Parsing SELinux file contexts skipped: 
/etc/security/selinux/src/policy/file_contexts/file_contexts: No such 
file or directory
Processing files: kernel-grsecurity-source-2.6.12.5-0.5
error: File not found: 
/home/users/spider/tmp/kernel-grsecurity-2.6.12.5-root-spider/usr/src/linux-2.6.12.5/grsecurity
Processing files: kernel-grsecurity-doc-2.6.12.5-0.5
Parsing SELinux file contexts skipped: 
/etc/security/selinux/src/policy/file_contexts/file_contexts: No such 
file or directory


RPM build errors:
    File not found: 
/home/users/spider/tmp/kernel-grsecurity-2.6.12.5-root-spider/usr/src/linux-2.6.12.5/grsecurity
Error: package build failed. (no more info)


witout grsecurity builind is fine


From gotar at polanet.pl  Mon Aug 29 11:27:41 2005
From: gotar at polanet.pl (Tomasz Pala)
Date: Mon, 29 Aug 2005 11:27:41 +0200
Subject: http://ftp.pld-linux.org/ via proxy
In-Reply-To: <20050829071628.GB14590@mysza.eu.org>
References: <20050826004318.GA3506@os> <20050826143240.GB8222@mysza.eu.org>
	<20050826150605.GA1982@os> <20050829071628.GB14590@mysza.eu.org>
Message-ID: <20050829092741.GA351@os>

On Mon, Aug 29, 2005 at 09:16:28 +0200, Adam Go??biowski wrote:

> But DNS changes too, and the idea behind recent changes was to bring us
> to the situation where querying for ftp.pld-linux.org gives us a server
> that is theoretically best for us. 

I understand and support this idea.

> > I-the-user just want to have http access (as poldek doesn't
> > work with proxy on ftp://) and it WAS working, now something was broken.
> 
> fill a bug report :)

AFAIR I've written about it to mis. By the way:
http://www.polanet.pl/~gotar/flyspry.png

What are these fields? ;]

> Anyway http://ftp5.pld-linux.org/ is now working. 

Thanks:)

-- 
GoTaR <priv0.onet.pl->gotar>        http://vfmg.sourceforge.net/
                                    http://tccs.sourceforge.net/


From pilot at altlinux.ru  Mon Aug 29 16:05:24 2005
From: pilot at altlinux.ru (Denis Ovsienko)
Date: Mon, 29 Aug 2005 18:05:24 +0400
Subject: Q: PLD rc-scripts and /etc/net
Message-ID: <20050829180524.6c683247.pilot@altlinux.ru>

Hi
I want to try incorporating my project (http://etcnet.org/) into PLD. Whom can
I send patches/ideas to? 

-- 
    DO4-UANIC


From loc at toya.net.pl  Mon Aug 29 16:33:04 2005
From: loc at toya.net.pl (=?UTF-8?B?SmFrdWIgUGlvdHIgQ8WCYXBh?=)
Date: Mon, 29 Aug 2005 16:33:04 +0200
Subject: Q: PLD rc-scripts and /etc/net
In-Reply-To: <20050829180524.6c683247.pilot@altlinux.ru>
References: <20050829180524.6c683247.pilot@altlinux.ru>
Message-ID: <43131CA0.8000108@toya.net.pl>

Denis Ovsienko wrote:
> Hi
> I want to try incorporating my project (http://etcnet.org/) into PLD. Whom can
> I send patches/ideas to? 

It is probably a good idea to use this list. Our rc-scripts have a 
separate list <pld-rc-scripts at pld-linux.org> but I think there are more 
people interested in this than just the rc-scripts team.

Any objections?

-- 
Regards,
Jakub Piotr C?apa


From adamg at biomerieux.pl  Mon Aug 29 16:49:33 2005
From: adamg at biomerieux.pl (Adam =?iso-8859-2?Q?Go=B3=EAbiowski?=)
Date: Mon, 29 Aug 2005 16:49:33 +0200
Subject: Q: PLD rc-scripts and /etc/net
In-Reply-To: <20050829180524.6c683247.pilot@altlinux.ru>
References: <20050829180524.6c683247.pilot@altlinux.ru>
Message-ID: <20050829144933.GA8269@mysza.eu.org>

On Mon, Aug 29, 2005 at 06:05:24PM +0400, Denis Ovsienko wrote:
> I want to try incorporating my project (http://etcnet.org/) into PLD. Whom can
> I send patches/ideas to? 

Can we discuss (potential) advantages of etcnet over our network
configuration first?

-- 
http://www.mysza.eu.org/ | Everybody needs someone sure, someone true,
   PLD Linux developer   | Everybody needs some solid rock, I know I do.


From loc at toya.net.pl  Mon Aug 29 17:07:27 2005
From: loc at toya.net.pl (=?UTF-8?B?SmFrdWIgUGlvdHIgQ8WCYXBh?=)
Date: Mon, 29 Aug 2005 17:07:27 +0200
Subject: Q: PLD rc-scripts and /etc/net
In-Reply-To: <20050829144933.GA8269@mysza.eu.org>
References: <20050829180524.6c683247.pilot@altlinux.ru>
	<20050829144933.GA8269@mysza.eu.org>
Message-ID: <431324AF.7040407@toya.net.pl>

Adam Go??biowski wrote:
> On Mon, Aug 29, 2005 at 06:05:24PM +0400, Denis Ovsienko wrote:
> 
>>I want to try incorporating my project (http://etcnet.org/) into PLD. Whom can
>>I send patches/ideas to? 
> 
> Can we discuss (potential) advantages of etcnet over our network
> configuration first?

I think it's not necessary (only insightful) and could be done in 
parallel with the implementation.
PLD is about choice, isn't it? (and probably there are people who would 
like to use etcnet because e.g. they are already used to it, so why not?)

-- 
Regards,
Jakub Piotr C?apa


From adamg at biomerieux.pl  Mon Aug 29 19:54:30 2005
From: adamg at biomerieux.pl (Adam =?iso-8859-2?Q?Go=B3=EAbiowski?=)
Date: Mon, 29 Aug 2005 19:54:30 +0200
Subject: Q: PLD rc-scripts and /etc/net
In-Reply-To: <431324AF.7040407@toya.net.pl>
References: <20050829180524.6c683247.pilot@altlinux.ru>
	<20050829144933.GA8269@mysza.eu.org> <431324AF.7040407@toya.net.pl>
Message-ID: <20050829175430.GA8859@mysza.eu.org>

On Mon, Aug 29, 2005 at 05:07:27PM +0200, Jakub Piotr C?apa wrote:
> Adam Go??biowski wrote:
> > On Mon, Aug 29, 2005 at 06:05:24PM +0400, Denis Ovsienko wrote:
> > 
> >>I want to try incorporating my project (http://etcnet.org/) into PLD. Whom can
> >>I send patches/ideas to? 
> > 
> > Can we discuss (potential) advantages of etcnet over our network
> > configuration first?
> 
> I think it's not necessary (only insightful) and could be done in 
> parallel with the implementation.
> PLD is about choice, isn't it? (and probably there are people who would 
> like to use etcnet because e.g. they are already used to it, so why not?)

If etcnet can coexist with current implementation, I agree with you. 
I thought etcnet was to replace PLD's solution. 

-- 
http://www.mysza.eu.org/ | Everybody needs someone sure, someone true,
   PLD Linux developer   | Everybody needs some solid rock, I know I do.


From aredridel at nbtsc.org  Mon Aug 29 19:59:12 2005
From: aredridel at nbtsc.org (Aredridel)
Date: Mon, 29 Aug 2005 11:59:12 -0600
Subject: Q: PLD rc-scripts and /etc/net
In-Reply-To: <20050829175430.GA8859@mysza.eu.org>
References: <20050829180524.6c683247.pilot@altlinux.ru>
	<20050829144933.GA8269@mysza.eu.org> <431324AF.7040407@toya.net.pl>
	<20050829175430.GA8859@mysza.eu.org>
Message-ID: <1125338352.13698.7.camel@localhost>

> > I think it's not necessary (only insightful) and could be done in 
> > parallel with the implementation.
> > PLD is about choice, isn't it? (and probably there are people who would 
> > like to use etcnet because e.g. they are already used to it, so why not?)
> 
> If etcnet can coexist with current implementation, I agree with you. 
> I thought etcnet was to replace PLD's solution. 

I'd certainly like to try etcnet -- I read a bit about it a while ago,
and it looked interesting!

Here's to choice!

Ari



From pilot at altlinux.ru  Mon Aug 29 21:05:51 2005
From: pilot at altlinux.ru (Denis Ovsienko)
Date: Mon, 29 Aug 2005 22:05:51 +0300
Subject: Q: PLD rc-scripts and /etc/net
In-Reply-To: <20050829175430.GA8859@mysza.eu.org>
References: <20050829180524.6c683247.pilot@altlinux.ru>
	<20050829144933.GA8269@mysza.eu.org> <431324AF.7040407@toya.net.pl>
	<20050829175430.GA8859@mysza.eu.org>
Message-ID: <20050829220551.770f11bc.pilot@altlinux.ru>

> If etcnet can coexist with current implementation, I agree with you. 
> I thought etcnet was to replace PLD's solution. 
Currently in ALTLinux one can install either net-scripts (RH initscripts
fork) or /etc/net RPM. Other packages are made to detect which one is
installed where necessary.

-- 
    DO4-UANIC


From loc at toya.net.pl  Tue Aug 30 01:19:42 2005
From: loc at toya.net.pl (=?UTF-8?B?SmFrdWIgUGlvdHIgQ8WCYXBh?=)
Date: Tue, 30 Aug 2005 01:19:42 +0200
Subject: SOURCES: go7007-hotplug.patch (NEW) - a patch for the hotplug
	scri...
In-Reply-To: <SOURCES_go7007_hotplug.patch.1.1@pld-linux.org>
References: <SOURCES_go7007_hotplug.patch.NONE@pld-linux.org>
	<SOURCES_go7007_hotplug.patch.1.1@pld-linux.org>
Message-ID: <4313980E.5050208@toya.net.pl>

jpc wrote:
> Index: SOURCES/go7007-hotplug.patch
> diff -u /dev/null SOURCES/go7007-hotplug.patch:1.1
> --- /dev/null	Mon Aug 29 14:13:55 2005
> +++ SOURCES/go7007-hotplug.patch	Mon Aug 29 14:13:50 2005
> @@ -0,0 +1,16 @@
> +--- wis-go7007-linux-0.9.6/hotplug/wis-ezusb.in~	2005-08-04 04:04:01.000000000 +0200
> ++++ wis-go7007-linux-0.9.6/hotplug/wis-ezusb.in	2005-08-28 20:02:17.147394816 +0200
> +@@ -84,10 +84,11 @@
> + fi
> + 
> + $LOADER $FLAGS -I $FIRMWARE
> ++$RETVAL=$?
> + 
> +-if [ $? -gt 0 ]; then
> ++if [ $RETVAL -gt 0 ]; then
> +     if [ -x /usr/bin/logger ]; then
> +-        /usr/bin/logger -t $0 "error $? returned by $LOADER $FLAGS -I $FIRMWARE"
> ++        /usr/bin/logger -t $0 "error $RETVAL returned by $LOADER $FLAGS -I $FIRMWARE"
> +     fi
> +     exit 1
> + fi

Is this change needed or just cosmetic? (I'm the one who wrote this but 
I'm not really sure ;)

-- 
Regards,
Jakub Piotr C?apa


From patrys at pld-linux.org  Tue Aug 30 01:28:12 2005
From: patrys at pld-linux.org (Patrys :: Patryk Zawadzki)
Date: Tue, 30 Aug 2005 01:28:12 +0200
Subject: SOURCES: go7007-hotplug.patch (NEW) - a patch for the hotplug
	scri...
In-Reply-To: <4313980E.5050208@toya.net.pl>
References: <SOURCES_go7007_hotplug.patch.NONE@pld-linux.org>
	<SOURCES_go7007_hotplug.patch.1.1@pld-linux.org>
	<4313980E.5050208@toya.net.pl>
Message-ID: <1125358092.8545.20.camel@localhost>

Dnia 30-08-2005, wto o godzinie 01:19 +0200, Jakub Piotr C?apa
napisa?(a):
> jpc wrote:
> > Index: SOURCES/go7007-hotplug.patch
> > diff -u /dev/null SOURCES/go7007-hotplug.patch:1.1
> > --- /dev/null	Mon Aug 29 14:13:55 2005
> > +++ SOURCES/go7007-hotplug.patch	Mon Aug 29 14:13:50 2005
> > @@ -0,0 +1,16 @@
> > +--- wis-go7007-linux-0.9.6/hotplug/wis-ezusb.in~	2005-08-04 04:04:01.000000000 +0200
> > ++++ wis-go7007-linux-0.9.6/hotplug/wis-ezusb.in	2005-08-28 20:02:17.147394816 +0200
> > +@@ -84,10 +84,11 @@
> > + fi
> > + 
> > + $LOADER $FLAGS -I $FIRMWARE
> > ++$RETVAL=$?
> > + 
> > +-if [ $? -gt 0 ]; then
> > ++if [ $RETVAL -gt 0 ]; then
> > +     if [ -x /usr/bin/logger ]; then
> > +-        /usr/bin/logger -t $0 "error $? returned by $LOADER $FLAGS -I $FIRMWARE"
> > ++        /usr/bin/logger -t $0 "error $RETVAL returned by $LOADER $FLAGS -I $FIRMWARE"
> > +     fi
> > +     exit 1
> > + fi
> 
> Is this change needed or just cosmetic? (I'm the one who wrote this but 
> I'm not really sure ;)

Here it looks like pure cosmetics (no execution prior to testing $?) but
it is more convenient to save it so if one adds one more instruction in
the conditional block it continues to work.

-- 
Patrys :: Patryk Zawadzki <patrys at pld-linux.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: </mailman/pipermail/pld-devel-en/attachments/20050830/d7680e68/attachment.sig>

From loc at toya.net.pl  Tue Aug 30 01:37:41 2005
From: loc at toya.net.pl (=?UTF-8?B?SmFrdWIgUGlvdHIgQ8WCYXBh?=)
Date: Tue, 30 Aug 2005 01:37:41 +0200
Subject: SOURCES: go7007-hotplug.patch (NEW) - a patch for the hotplug
	scri...
In-Reply-To: <1125358092.8545.20.camel@localhost>
References: <SOURCES_go7007_hotplug.patch.NONE@pld-linux.org>	<SOURCES_go7007_hotplug.patch.1.1@pld-linux.org>	<4313980E.5050208@toya.net.pl>
	<1125358092.8545.20.camel@localhost>
Message-ID: <43139C45.5030803@toya.net.pl>

Patrys :: Patryk Zawadzki wrote:
> Here it looks like pure cosmetics (no execution prior to testing $?) but
> it is more convenient to save it so if one adds one more instruction in
> the conditional block it continues to work.

That's what I though (but OTOH I changed it after getting a syslog 
message that the loading failed with code 0).

The comparison ([) is not changing $? because it is builtin?
And what if a standalone version of [ was used?

-- 
Regards,
Jakub Piotr C?apa


From patrys at pld-linux.org  Tue Aug 30 02:53:36 2005
From: patrys at pld-linux.org (Patrys :: Patryk Zawadzki)
Date: Tue, 30 Aug 2005 02:53:36 +0200
Subject: SOURCES: go7007-hotplug.patch (NEW) - a patch for the hotplug
	scri...
In-Reply-To: <43139C45.5030803@toya.net.pl>
References: <SOURCES_go7007_hotplug.patch.NONE@pld-linux.org>
	<SOURCES_go7007_hotplug.patch.1.1@pld-linux.org>
	<4313980E.5050208@toya.net.pl> <1125358092.8545.20.camel@localhost>
	<43139C45.5030803@toya.net.pl>
Message-ID: <1125363216.8545.22.camel@localhost>

Dnia 30-08-2005, wto o godzinie 01:37 +0200, Jakub Piotr C?apa
napisa?(a):
> Patrys :: Patryk Zawadzki wrote:
> > Here it looks like pure cosmetics (no execution prior to testing $?) but
> > it is more convenient to save it so if one adds one more instruction in
> > the conditional block it continues to work.
> That's what I though (but OTOH I changed it after getting a syslog 
> message that the loading failed with code 0).
> 
> The comparison ([) is not changing $? because it is builtin?
> And what if a standalone version of [ was used?

Well I believe it depends on the shell used. Or maybe on the ammount of
coffee I am lacking at the moment.

-- 
Patrys :: Patryk Zawadzki <patrys at pld-linux.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: </mailman/pipermail/pld-devel-en/attachments/20050830/496d1e0d/attachment.sig>

From ankry at green.mif.pg.gda.pl  Tue Aug 30 08:02:17 2005
From: ankry at green.mif.pg.gda.pl (Andrzej Krzysztofowicz)
Date: Tue, 30 Aug 2005 08:02:17 +0200 (CEST)
Subject: SOURCES: go7007-hotplug.patch (NEW) - a patch for the hotplug
In-Reply-To: <1125363216.8545.22.camel@localhost> from "Patrys :: Patryk
	Zawadzki" at Aug 30, 2005 02:53:36 AM
Message-ID: <200508300602.j7U62HSj027044@green.mif.pg.gda.pl>

Patrys :: Patryk Zawadzki wrote:
> Dnia 30-08-2005, wto o godzinie 01:37 +0200, Jakub Piotr C=B3apa
> napisa=B3(a):
> > Patrys :: Patryk Zawadzki wrote:
> > > Here it looks like pure cosmetics (no execution prior to testing $?) bu=
> t
> > > it is more convenient to save it so if one adds one more instruction in
> > > the conditional block it continues to work.
> > That's what I though (but OTOH I changed it after getting a syslog=20
> > message that the loading failed with code 0).
> >=20
> > The comparison ([) is not changing $? because it is builtin?
> > And what if a standalone version of [ was used?
> 
> Well I believe it depends on the shell used. Or maybe on the ammount of
> coffee I am lacking at the moment.

The script is executed using /bin/sh. Our /bin/sh support built-in [.

-- 
=======================================================================
  Andrzej M. Krzysztofowicz               ankry at mif.pg.gda.pl
  phone (48)(58) 347 14 61
Faculty of Applied Phys. & Math.,   Gdansk University of Technology


From marek.guevara at atm.com.pl  Tue Aug 30 15:17:19 2005
From: marek.guevara at atm.com.pl (Marek Guevara Braun)
Date: Tue, 30 Aug 2005 15:17:19 +0200
Subject: kernel building -bug report
In-Reply-To: <4312EA55.509@linux.pl>
References: <4312EA55.509@linux.pl>
Message-ID: <43145C5F.3080709@atm.com.pl>

Piotr Skwarna wrote:
> spider at zero SPECS$ ./builder -bb -r LINUX_2_6 kernel.spec --without smp 
> --without pcmcia --with grsecurity --target i686
> 
> [CUT]
> witout grsecurity builind is fine

 From the kernel.spec:

# derived from
http://www.grsecurity.net/grsecurity-2.1.5-2.6.11.7-200504111924.patch.gz
                            Patch200:
grsecurity-2.1.5-2.6.11.7-200504111924.patch
[...]
%if %{with grsecurity}
echo Grsecurity not implemented
##patch200 -p1
%endif

BTW. There was no an official grsecurity/pax for 2.6.12 - there should
be one for 2.6.13.

Regards,
Marek