Re: [Cooker] gnupg: wrong http-proxy option

2002-05-06 Thread Todd Lyons

Matthias Debus wrote on Mon, May 06, 2002 at 09:05:45PM +0200 :
 hi all!
 
 each time I call gpg I get the following (translated):
 
 gpg: WARNING: --honor-http-proxy is a depreciated option.
 gpg: Please use instead --keyserver-option honor-http-proxy.
 this, for instance, causes gabber not to work with gpg anymore.

In your ~/.gnupg/options configuration file, change:
  honor-http-proxy
to
  keyserver-options honor-http-proxy

Blue skies...   Todd
-- 
  Todd Lyons -- MandrakeSoft, Inc.   http://www.mandrakesoft.com/
UNIX was not designed to stop you from doing stupid things, because 
  that would also stop you from doing clever things. -- Doug Gwyn
   Cooker Version mandrake-release-8.3-0.2mdk Kernel 2.4.18-13mdk



msg63791/pgp0.pgp
Description: PGP signature


Re: [Cooker] gnupg-1.0.4-1mdk

2000-10-24 Thread Vincent Danen

On Mon Oct 23, 2000 at 08:00:54PM +0200, Alexander Skwar wrote:

  You forget I can't use those macros on the older versions... =)  I'm
  kinda stuck with doing things the clumsy way.  =(
 
 Couldn't you make an update for RPM which basically only contains a recent
 set of macros?

I was thinking of taking the macros for 7.1 and stuffing them into the
old versions on our updates machine.  Making an update to use those
macros would be more work than it's worth, I think.  If anything,
you'd want to update rpm to a more recent version (actually, I think
you may have to) if you were going to make a full-blown update out of it.

-- 
[EMAIL PROTECTED], OpenPGP key available on www.keyserver.net
// Danen Consulting Serviceswww.danen.net, www.freezer-burn.org
// MandrakeSoft, Inc.   www.linux-mandrake.com
1024D/FE6F2AFD   88D8 0D23 8D4B 3407 5BD7  66F9 2043 D0E5 FE6F 2AFD

Current Linux uptime: 3 days 0 hours 43 minutes.




Re: [Cooker] gnupg-1.0.4-1mdk

2000-10-23 Thread Vincent Danen

On Sun Oct 22, 2000 at 02:45:52AM +0800, Geoffrey Lee wrote:

   After some tests with 2mdk I think it is safe to say that we are going to
   get this out to the masses for consumption.
  
  Well, I tried -2mdk on a P166 I have here and it installed fine and
  seems to work perfectly (test based on the fact that it runs).  -2mdk
  should be hitting the primary mirrors within the hour.  Note that you
  don't have to fix anything for 7.2beta or cooker... those were built
  fine, it's just the updates versions that were problematic (again, I
  had to backport your spec).
 
 Why not CFLAGS=$RPM_OPT_FLAGS ./configure (which was the standard before
 the macros) ?

I had to change a bunch of stuff in ./configure (ie. prefix, mandir,
etc.) to all be $RPM_BUILD_ROOT because make prefix=$RPM_BUILD_ROOT
install does not work in it...  Don't ask me why, but it's a good
thing I tried building it as a user because it didn't want to install
into buildroot but into the live system.  Without patching the
makefile, this was the easiest fix (and it works).

-- 
[EMAIL PROTECTED], OpenPGP key available on www.keyserver.net
// Danen Consulting Serviceswww.danen.net, www.freezer-burn.org
// MandrakeSoft, Inc.   www.linux-mandrake.com
1024D/FE6F2AFD   88D8 0D23 8D4B 3407 5BD7  66F9 2043 D0E5 FE6F 2AFD

Current Linux uptime: 2 days 15 hours 22 minutes.




Re: [Cooker] gnupg-1.0.4-1mdk

2000-10-23 Thread Geoffrey Lee

Yo,

On Mon, Oct 23, 2000 at 09:48:58AM -0600, Vincent Danen wrote:
 On Sun Oct 22, 2000 at 02:45:52AM +0800, Geoffrey Lee wrote:
 
After some tests with 2mdk I think it is safe to say that we are going to
get this out to the masses for consumption.
   
   Well, I tried -2mdk on a P166 I have here and it installed fine and
   seems to work perfectly (test based on the fact that it runs).  -2mdk
   should be hitting the primary mirrors within the hour.  Note that you
   don't have to fix anything for 7.2beta or cooker... those were built
   fine, it's just the updates versions that were problematic (again, I
   had to backport your spec).
  
  Why not CFLAGS=$RPM_OPT_FLAGS ./configure (which was the standard before
  the macros) ?
 
 I had to change a bunch of stuff in ./configure (ie. prefix, mandir,
 etc.) to all be $RPM_BUILD_ROOT because make prefix=$RPM_BUILD_ROOT
 install does not work in it...  Don't ask me why, but it's a good
 thing I tried building it as a user because it didn't want to install
 into buildroot but into the live system.  Without patching the
 makefile, this was the easiest fix (and it works).



Strange as %makeinstall only evaluate to make prefix=$RPM_BUILD_ROOT%{_prefix}
  mandir=$RPM_BUILD_ROOT/%{_mandir} ... [etc] install ..

Funny thing that it works for us now, but when we enter exactly the same
thing (i.e. the expanded macro) it doesn't want to work on the older system :/
  
-- 
Geoffrey Lee [EMAIL PROTECTED]
§õªø­·

~/.signature ¤¤¤åbig5 compliant.

http://www.mandrakesoft.com/~snailtalk
ftp://devel.mandrakesoft.com/pub/people/snailtalk


"7 days of honeymoon makes one whole week."




Re: [Cooker] gnupg-1.0.4-1mdk

2000-10-23 Thread Vincent Danen

On Tue Oct 24, 2000 at 12:45:50AM +0800, Geoffrey Lee wrote:

   Why not CFLAGS=$RPM_OPT_FLAGS ./configure (which was the standard before
   the macros) ?
  
  I had to change a bunch of stuff in ./configure (ie. prefix, mandir,
  etc.) to all be $RPM_BUILD_ROOT because make prefix=$RPM_BUILD_ROOT
  install does not work in it...  Don't ask me why, but it's a good
  thing I tried building it as a user because it didn't want to install
  into buildroot but into the live system.  Without patching the
  makefile, this was the easiest fix (and it works).
 
 Strange as %makeinstall only evaluate to make prefix=$RPM_BUILD_ROOT%{_prefix}
   mandir=$RPM_BUILD_ROOT/%{_mandir} ... [etc] install ..
 
 Funny thing that it works for us now, but when we enter exactly the same
 thing (i.e. the expanded macro) it doesn't want to work on the older system :/

You forget I can't use those macros on the older versions... =)  I'm
kinda stuck with doing things the clumsy way.  =(

-- 
[EMAIL PROTECTED], OpenPGP key available on www.keyserver.net
// Danen Consulting Serviceswww.danen.net, www.freezer-burn.org
// MandrakeSoft, Inc.   www.linux-mandrake.com
1024D/FE6F2AFD   88D8 0D23 8D4B 3407 5BD7  66F9 2043 D0E5 FE6F 2AFD

Current Linux uptime: 2 days 16 hours 51 minutes.




Re: [Cooker] gnupg-1.0.4-1mdk

2000-10-23 Thread Alexander Skwar

So sprach Vincent Danen am Mon, Oct 23, 2000 at 11:17:36AM -0600:
 You forget I can't use those macros on the older versions... =)  I'm
 kinda stuck with doing things the clumsy way.  =(

Couldn't you make an update for RPM which basically only contains a recent
set of macros?

Alexander Skwar
-- 
Homepage:   http://www.digitalprojects.com | http://www.dp.ath.cx
Sichere Mail?   Mail an [EMAIL PROTECTED] fuer GnuPG Keys
ICQ:7328191




Re: [Cooker] gnupg-1.0.4-1mdk

2000-10-21 Thread Anton Graham

Submitted 21-Oct-00 by Anton Graham:

 System is a P200 with 96MB RAM running a hybrid of 7.1 and 7.2beta

The problem is in the spec file which explicitly defines the CFLAGS,
CXXFLAGS, and FFLAGS with "-mcpu=pentiumpro -march=pentiumpro" which
generates i686 binaries which won't run on a Pentium class machine.

-- 
Anton GrahamGPG ID: 0x18F78541
[EMAIL PROTECTED] RSA key available upon request
 
Don't try to outweird me, three-eyes.  I get stranger things than you free
with my breakfast cereal." 
  -- Zaphod Beeblebrox [Douglas Adams, "Hithiker's Guide to the Galaxy"]





Re: [Cooker] gnupg-1.0.4-1mdk

2000-10-21 Thread Chmouel Boudjnah

On Sat, Oct 21, 2000 at 02:05:07AM -0700, Anton Graham wrote:
 Submitted 21-Oct-00 by Anton Graham:
 
  System is a P200 with 96MB RAM running a hybrid of 7.1 and 7.2beta
 
 The problem is in the spec file which explicitly defines the CFLAGS,
 CXXFLAGS, and FFLAGS with "-mcpu=pentiumpro -march=pentiumpro" which
 generates i686 binaries which won't run on a Pentium class machine.

not true, gnupg was compiled on a machine who are updated in frozen not in
cooker, where the CFLAGS is still :

(chmou@no)[~]-% rpm --eval %optflags
-O3 -fomit-frame-pointer -pipe -s -march=pentium -ffast-math -fexpensive-optimizations





Re: [Cooker] gnupg-1.0.4-1mdk

2000-10-21 Thread Alexander Skwar

So sprach Anton Graham am Sat, Oct 21, 2000 at 02:05:07AM -0700:
 The problem is in the spec file which explicitly defines the CFLAGS,
 CXXFLAGS, and FFLAGS with "-mcpu=pentiumpro -march=pentiumpro" which
 generates i686 binaries which won't run on a Pentium class machine.

Are you sure?  -mcpu=pentiumpro is long gone from %optflags, and because
that's a new package I would very much wonder if it were compiled with these
settings.

Alexander Skwar
-- 
Homepage:   http://www.digitalprojects.com | http://www.dp.ath.cx
Sichere Mail?   Mail an [EMAIL PROTECTED] fuer GnuPG Keys
ICQ:7328191




Re: [Cooker] gnupg-1.0.4-1mdk

2000-10-21 Thread Anton Graham

Submitted 21-Oct-00 by Chmouel Boudjnah:
 not true, gnupg was compiled on a machine who are updated in frozen not in
 cooker, where the CFLAGS is still :

 (chmou@no)[~]-% rpm --eval %optflags
 -O3 -fomit-frame-pointer -pipe -s -march=pentium -ffast-math 
-fexpensive-optimizations

The CFLAGS from RPM were right, but the incorrect CFLAGS are hardcoded in
the spec file:

. . .
%build
CFLAGS="${CFLAGS:--O3 -fomit-frame-pointer -pipe -s -mcpu=pentiumpro
-march=pentiumpro -ffast-math -fexpensive-optimizations}" ; export CFLAGS ;
CXXFLAGS="${CXXFLAGS:--O3 -fomit-frame-pointer -pipe -s -mcpu=pentiumpro
-march=pentiumpro -ffast-math -fexpensive-optimizations}" ; export CXXFLAGS ;
FFLAGS="${FFLAGS:--O3 -fomit-frame-pointer -pipe -s -mcpu=pentiumpro
-march=pentiumpro -ffast-math -fexpensive-optimizations}" ; export FFLAGS ;
#[ -f configure.in ]  libtoolize --copy --force ;
./configure i686-mandrake-linux \
. . .

-- 
Anton GrahamGPG ID: 0x18F78541
[EMAIL PROTECTED] RSA key available upon request
 
Asking a working writer what he thinks about critics is like asking a
lamp-post how it feels about dogs.  
  -- Christopher Hampton





Re: [Cooker] gnupg-1.0.4-1mdk

2000-10-21 Thread Chmouel Boudjnah

Anton Graham [EMAIL PROTECTED] writes:

 The CFLAGS from RPM were right, but the incorrect CFLAGS are hardcoded in
 the spec file:

in this case the maintenners should be blammed aka Guillaume..

-- 
MandrakeSoft Inc http://www.chmouel.org
Paris, France --Chmouel




Re: [Cooker] gnupg-1.0.4-1mdk

2000-10-21 Thread Geoffrey Lee

Yo,

On Sat, Oct 21, 2000 at 04:32:32AM -0700, Anton Graham wrote:
 Submitted 21-Oct-00 by Chmouel Boudjnah:
  not true, gnupg was compiled on a machine who are updated in frozen not in
  cooker, where the CFLAGS is still :
 
  (chmou@no)[~]-% rpm --eval %optflags
  -O3 -fomit-frame-pointer -pipe -s -march=pentium -ffast-math 
-fexpensive-optimizations
 
 The CFLAGS from RPM were right, but the incorrect CFLAGS are hardcoded in
 the spec file:

 . . .
 %build
 CFLAGS="${CFLAGS:--O3 -fomit-frame-pointer -pipe -s -mcpu=pentiumpro
 -march=pentiumpro -ffast-math -fexpensive-optimizations}" ; export CFLAGS ;
 CXXFLAGS="${CXXFLAGS:--O3 -fomit-frame-pointer -pipe -s -mcpu=pentiumpro
 -march=pentiumpro -ffast-math -fexpensive-optimizations}" ; export CXXFLAGS ;
 FFLAGS="${FFLAGS:--O3 -fomit-frame-pointer -pipe -s -mcpu=pentiumpro
 -march=pentiumpro -ffast-math -fexpensive-optimizations}" ; export FFLAGS ;
 #[ -f configure.in ]  libtoolize --copy --force ;
 ./configure i686-mandrake-linux \
 . . .
 


Not true, it only use %configure which is a macro taken from rpmrc, which
is in turn a global configuration on the buildhosts ..


-- 
Geoffrey Lee [EMAIL PROTECTED]
§õªø­·

~/.signature ¤¤¤åbig5 compliant.

http://www.mandrakesoft.com/~snailtalk
ftp://devel.mandrakesoft.com/pub/people/snailtalk


"7 days of honeymoon makes one whole week."




Re: [Cooker] gnupg-1.0.4-1mdk

2000-10-21 Thread Geoffrey Lee

Yo,

On Sat, Oct 21, 2000 at 04:40:50PM -0700, Chmouel Boudjnah wrote:
 Anton Graham [EMAIL PROTECTED] writes:
 
  The CFLAGS from RPM were right, but the incorrect CFLAGS are hardcoded in
  the spec file:
 
 in this case the maintenners should be blammed aka Guillaume..



You blamed the wrong guy, it was me who compiled it, seeing that there
is a security update, I thought it was important it is out ASAP ..

But, I could see no hardcoded values in the rpm. It is just a standard
%configure. If something is broke, it should be the buildhosts.

-- 
Geoffrey Lee [EMAIL PROTECTED]
§õªø­·

~/.signature ¤¤¤åbig5 compliant.

http://www.mandrakesoft.com/~snailtalk
ftp://devel.mandrakesoft.com/pub/people/snailtalk


"7 days of honeymoon makes one whole week."




Re: [Cooker] gnupg-1.0.4-1mdk

2000-10-21 Thread Vincent Danen

On Sat Oct 21, 2000 at 06:20:52AM -0500, Chmouel wrote:

   System is a P200 with 96MB RAM running a hybrid of 7.1 and 7.2beta
  
  The problem is in the spec file which explicitly defines the CFLAGS,
  CXXFLAGS, and FFLAGS with "-mcpu=pentiumpro -march=pentiumpro" which
  generates i686 binaries which won't run on a Pentium class machine.
 
 not true, gnupg was compiled on a machine who are updated in frozen not in
 cooker, where the CFLAGS is still :
 
 (chmou@no)[~]-% rpm --eval %optflags
 -O3 -fomit-frame-pointer -pipe -s -march=pentium -ffast-math 
-fexpensive-optimizations

Nope, he's right...  I did a big vincentsucks on this one...  I
couldn't get gpg to build properly so I basically copied the output of
%{optflags} into the spec (to build for 7.0) and I (stupidly) did this
on my machine which is a p2-350...  fixing it right now.  Expect a
-2mdk within the hour.

-- 
[EMAIL PROTECTED], OpenPGP key available on www.keyserver.net
// Danen Consulting Serviceswww.danen.net, www.freezer-burn.org
// MandrakeSoft, Inc.   www.linux-mandrake.com
1024D/FE6F2AFD   88D8 0D23 8D4B 3407 5BD7  66F9 2043 D0E5 FE6F 2AFD

Current Linux uptime: 17 hours 25 minutes.




Re: [Cooker] gnupg-1.0.4-1mdk

2000-10-21 Thread Vincent Danen

On Sat Oct 21, 2000 at 11:03:32PM +0800, Geoffrey Lee wrote:

  %build
  CFLAGS="${CFLAGS:--O3 -fomit-frame-pointer -pipe -s -mcpu=pentiumpro
  -march=pentiumpro -ffast-math -fexpensive-optimizations}" ; export CFLAGS ;
  CXXFLAGS="${CXXFLAGS:--O3 -fomit-frame-pointer -pipe -s -mcpu=pentiumpro
  -march=pentiumpro -ffast-math -fexpensive-optimizations}" ; export CXXFLAGS ;
  FFLAGS="${FFLAGS:--O3 -fomit-frame-pointer -pipe -s -mcpu=pentiumpro
  -march=pentiumpro -ffast-math -fexpensive-optimizations}" ; export FFLAGS ;
  #[ -f configure.in ]  libtoolize --copy --force ;
  ./configure i686-mandrake-linux \
  . . .
 
 Not true, it only use %configure which is a macro taken from rpmrc, which
 is in turn a global configuration on the buildhosts ..

No, it is true... see my other message.  Big vincesucks on this one.
=(  I have to modify the specs so they work on 7.0/7.1 (I hate
backporting!!) and this slipped in there so I could get it to build
properly.

Fixing it right now.

-- 
[EMAIL PROTECTED], OpenPGP key available on www.keyserver.net
// Danen Consulting Serviceswww.danen.net, www.freezer-burn.org
// MandrakeSoft, Inc.   www.linux-mandrake.com
1024D/FE6F2AFD   88D8 0D23 8D4B 3407 5BD7  66F9 2043 D0E5 FE6F 2AFD

Current Linux uptime: 17 hours 28 minutes.




Re: [Cooker] gnupg-1.0.4-1mdk

2000-10-21 Thread Geoffrey Lee

Yo,

On Sat, Oct 21, 2000 at 11:54:43AM -0600, Vincent Danen wrote:
 On Sat Oct 21, 2000 at 11:03:32PM +0800, Geoffrey Lee wrote:
 
   %build
   CFLAGS="${CFLAGS:--O3 -fomit-frame-pointer -pipe -s -mcpu=pentiumpro
   -march=pentiumpro -ffast-math -fexpensive-optimizations}" ; export CFLAGS ;
   CXXFLAGS="${CXXFLAGS:--O3 -fomit-frame-pointer -pipe -s -mcpu=pentiumpro
   -march=pentiumpro -ffast-math -fexpensive-optimizations}" ; export CXXFLAGS ;
   FFLAGS="${FFLAGS:--O3 -fomit-frame-pointer -pipe -s -mcpu=pentiumpro
   -march=pentiumpro -ffast-math -fexpensive-optimizations}" ; export FFLAGS ;
   #[ -f configure.in ]  libtoolize --copy --force ;
   ./configure i686-mandrake-linux \
   . . .
  
  Not true, it only use %configure which is a macro taken from rpmrc, which
  is in turn a global configuration on the buildhosts ..
 
 No, it is true... see my other message.  Big vincesucks on this one.
 =(  I have to modify the specs so they work on 7.0/7.1 (I hate
 backporting!!) and this slipped in there so I could get it to build
 properly.




Oh. So mine is OK. Yours suck.! :)

After some tests with 2mdk I think it is safe to say that we are going to
get this out to the masses for consumption.


-- 
Geoffrey Lee [EMAIL PROTECTED]
§õªø­·

~/.signature ¤¤¤åbig5 compliant.

http://www.mandrakesoft.com/~snailtalk
ftp://devel.mandrakesoft.com/pub/people/snailtalk


"7 days of honeymoon makes one whole week."




Re: [Cooker] gnupg-1.0.4-1mdk

2000-10-21 Thread Vincent Danen

On Sun Oct 22, 2000 at 02:05:24AM +0800, Geoffrey Lee wrote:

   Not true, it only use %configure which is a macro taken from rpmrc, which
   is in turn a global configuration on the buildhosts ..
  
  No, it is true... see my other message.  Big vincesucks on this one.
  =(  I have to modify the specs so they work on 7.0/7.1 (I hate
  backporting!!) and this slipped in there so I could get it to build
  properly.
 
 Oh. So mine is OK. Yours suck.! :)

Exactly.  =)

 After some tests with 2mdk I think it is safe to say that we are going to
 get this out to the masses for consumption.

Well, I tried -2mdk on a P166 I have here and it installed fine and
seems to work perfectly (test based on the fact that it runs).  -2mdk
should be hitting the primary mirrors within the hour.  Note that you
don't have to fix anything for 7.2beta or cooker... those were built
fine, it's just the updates versions that were problematic (again, I
had to backport your spec).

-- 
[EMAIL PROTECTED], OpenPGP key available on www.keyserver.net
// Danen Consulting Serviceswww.danen.net, www.freezer-burn.org
// MandrakeSoft, Inc.   www.linux-mandrake.com
1024D/FE6F2AFD   88D8 0D23 8D4B 3407 5BD7  66F9 2043 D0E5 FE6F 2AFD

Current Linux uptime: 18 hours 4 minutes.




Re: [Cooker] gnupg-1.0.4-1mdk

2000-10-21 Thread Geoffrey Lee

Yo,

 
  After some tests with 2mdk I think it is safe to say that we are going to
  get this out to the masses for consumption.
 
 Well, I tried -2mdk on a P166 I have here and it installed fine and
 seems to work perfectly (test based on the fact that it runs).  -2mdk
 should be hitting the primary mirrors within the hour.  Note that you
 don't have to fix anything for 7.2beta or cooker... those were built
 fine, it's just the updates versions that were problematic (again, I
 had to backport your spec).



Why not CFLAGS=$RPM_OPT_FLAGS ./configure (which was the standard before
the macros) ?




-- 
Geoffrey Lee [EMAIL PROTECTED]
§õªø­·

~/.signature ¤¤¤åbig5 compliant.

http://www.mandrakesoft.com/~snailtalk
ftp://devel.mandrakesoft.com/pub/people/snailtalk


"7 days of honeymoon makes one whole week."




Re: [Cooker] gnupg

2000-10-14 Thread Vincent Danen

On Sat Oct 14, 2000 at 05:44:34PM +0100, Taco Witte wrote:

 I encountered a (very) little problem with gnupg-1.0.3-1.i586.rpm. When I installed 
it using root, it made a ~/.gnupg directory,
 but if I start it the first time with a normal user account, it doesn't create a 
~/.gnupg directory, making it unable to be used.

This isn't a problem.  The only reason /root/.gnupg is created (if it
doesn't already exist) is to import the two Mandrake gpg keys to the
keyring so you can verify rpms that you are installing.

It doesn't do this for users because it would be silly to put those
two keys in every user's keyring.  You need to make your own
private/public key set as the user and gnupg will make the directory.
Normal behaviour of gpg is not to make that directory until you create
a keyring of your own (or copy your old keyrings to that directory).

If you really want, as root do "cp -av ~/.gnupg ~user/.gnupg" and
you'll get those mandrake keys in a default public keyring.

-- 
[EMAIL PROTECTED], OpenPGP key available on www.keyserver.net
// Danen Consulting Serviceswww.danen.net, www.freezer-burn.org
// MandrakeSoft, Inc.   www.linux-mandrake.com
1024D/FE6F2AFD   88D8 0D23 8D4B 3407 5BD7  66F9 2043 D0E5 FE6F 2AFD

Current Linux uptime: 1 day 13 hours 50 minutes.