Re: BIND -- Problems with Linux capabilties

2008-07-25 Thread Bill Campbell
On Fri, Jul 25, 2008, Ralf S. Engelschall wrote: >On Thu, Jul 24, 2008, Bill Campbell wrote: > >> I ran into a problem today attempting to build the current version of bind, >> bind-9.5.0p1-20080709.src.rpm, on a SuSE Linux Enterprise 9 PL3 >> system with the following error: >> >> /csrel25/bin/cc

Re: BIND -- Problems with Linux capabilties

2008-07-25 Thread Bill Campbell
running the command through cpp only to get everything expanded, it looks as though the ``caps |= ...'' is operating on a structure, which really is not a very sensible thing to do if one expects portability. Then again diddling bits like this has portability issues in any case as it could run

Re: BIND -- Problems with Linux capabilties

2008-07-24 Thread Ralf S. Engelschall
On Thu, Jul 24, 2008, Bill Campbell wrote: > I ran into a problem today attempting to build the current version of bind, > bind-9.5.0p1-20080709.src.rpm, on a SuSE Linux Enterprise 9 PL3 > system with the following error: > > /csrel25/bin/cc -I/csrel25/RPM/TMP/bind-9.5.0-P1 -I./include -I./../incl

BIND -- Problems with Linux capabilties

2008-07-24 Thread Bill Campbell
I ran into a problem today attempting to build the current version of bind, bind-9.5.0p1-20080709.src.rpm, on a SuSE Linux Enterprise 9 PL3 system with the following error: /csrel25/bin/cc -I/csrel25/RPM/TMP/bind-9.5.0-P1 -I./include -I./../include -I/csrel25/RPM/TMP/bind-9.5.0-P1/lib/dns/include

Re: Problems with openpkg rc --eval all env

2008-03-09 Thread Steffen Weinreich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Olivier Kaloudoff schrieb: | I would suggest that you create the corresponding sudo entry in /etc/sudoers and use /usr/bin/sudo . The command dont need no special privileges. It outputs a shell sniptlet to set ENV-vars for the openpkg instance. |

Re: Problems with openpkg rc --eval all env

2008-03-09 Thread Olivier Kaloudoff
Hi! Hello Steffen, I'm using ~eval `openpkg rc --eval all env` to setup the paths for a openpkg instance in the system login script. This works fine except that the directory which is created under /tmp could not be deleteted since the owner of the dir is the management user and theref

Re: Problems with openpkg rc --eval all env

2008-03-09 Thread Ralf S. Engelschall
On Sun, Mar 09, 2008, Steffen Weinreich wrote: > ~eval `openpkg rc --eval all env` > > to setup the paths for a openpkg instance in the system login script. This > works fine except that the directory which is created under /tmp could not > be deleteted since the owner of the dir is the manage

Problems with openpkg rc --eval all env

2008-03-09 Thread Steffen Weinreich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! I'm using ~eval `openpkg rc --eval all env` to setup the paths for a openpkg instance in the system login script. This works fine except that the directory which is created under /tmp could not be deleteted since the owner of the dir is t

Problems building cyrus-imapd on FreeBSD as packaged with Kolab.

2007-12-18 Thread viq
I created a bug report with Kolab, but I was advised to contact you too. The problem is described in detail at https://intevation.de/roundup/kolab/issue2349 and in short is that cyrus when built on the FreeBSD box in the OpenPKG environment fails to pick up pcre. Please contact me if any further d

Re: Milter build problems again.

2007-07-23 Thread Mark Keller
On Monday 23 July 2007 10:17:46 Mark Keller wrote: > I understand that the sendmail people made a poor choice in using > include/libmiter/*.h, but they did. Since enough packages do rely on the > include files, I think that changing the location seems to make a lot of > extra work. Now all other p

Re: Milter build problems again.

2007-07-23 Thread Mark Keller
On Monday 23 July 2007 03:17:40 Ralf S. Engelschall wrote: > If we would just have the "milter" package I also would vote for > renaming it to "libmilter" immediately. But what about the "milter-xxx" > packages? They use the "milter" prefix to show their correlation to the > "milter" package. Unti

Re: Milter build problems again.

2007-07-23 Thread Ralf S. Engelschall
On Mon, Jul 23, 2007, Birger Krägelin wrote: > > > Anyhow, I am wondering why the decision was made to move the milter > > include > > > files to milter/*.h instead of the default libmilter/*.h? If > > something really > > > needs the includes in milter/*.h maybe a symbolic link should be made > >

AW: Milter build problems again.

2007-07-23 Thread Birger Krägelin
> > Anyhow, I am wondering why the decision was made to move the milter > include > > files to milter/*.h instead of the default libmilter/*.h? If > something really > > needs the includes in milter/*.h maybe a symbolic link should be made > so it > > works for both locations. > > Maybe I am just m

Re: Milter build problems again.

2007-07-20 Thread Ralf S. Engelschall
On Fri, Jul 20, 2007, Mark Keller wrote: > I had discussed a milter problem before in a previous request to the > openpkg-dev list. > > http://marc.info/?l=openpkg-dev&m=117147128624622&w=2 > > It turns out I have the problem again now that I am trying to uprade our > packages. The mimedefang pack

Milter build problems again.

2007-07-20 Thread Mark Keller
I had discussed a milter problem before in a previous request to the openpkg-dev list. http://marc.info/?l=openpkg-dev&m=117147128624622&w=2 It turns out I have the problem again now that I am trying to uprade our packages. The mimedefang package fails to build because it is looking for the mi

Re: openpkg-20070603-20070603 build problems

2007-06-03 Thread Ralf S. Engelschall
On Sun, Jun 03, 2007, Thomas Arendsen Hein wrote: > When building openpkg-20070603-20070603.src.sh on Debian etch on x86 > I get the following error while 20070520 compiles fine on that box. My fault. During upgrade of openssl.patch I've overlooked that there were bootstrap specific parts in it.

openpkg-20070603-20070603 build problems

2007-06-03 Thread Thomas Arendsen Hein
Hi! When building openpkg-20070603-20070603.src.sh on Debian etch on x86 I get the following error while 20070520 compiles fine on that box. Thomas +-+ | BUILD: Build OpenSSL (Crypography and SSL/TLS Toolkit)

perl-dbi submission: problems with DBD_Oracle

2006-10-06 Thread Dennis McRitchie
I just uploaded perl-dbi-5.8.8-20060929pu1_cses.src.rpm. There were two problems when "with_dbd_oracle = yes": 1) DBD_Oracle would not build. This turned out to be a naming problem. The version provided in the rpm is 1.18, but it was named 1.18a. It unpacked into a directory with a &quo

Re: Problems with Apache

2006-01-16 Thread Ralf S. Engelschall
On Mon, Jan 16, 2006, Peter Zimmer wrote: > we are experiencing some problems with the apache web server in > openpkg-2.5. > > On some accesses to the web page we get an error in the apache error log > file: > > [Thu Jan 12 08:39:46 2006] [notice] child pid 26680 exit s

Problems with Apache

2006-01-16 Thread Peter Zimmer
Hi all, we are experiencing some problems with the apache web server in openpkg-2.5. On some accesses to the web page we get an error in the apache error log file: [Thu Jan 12 08:39:46 2006] [notice] child pid 26680 exit signal Bus Error (10) The web page is the assist enterprise help desk

Problems with apache-1.3.33 and mod_dav on Linux

2006-01-01 Thread Bill Campbell
FWIW, a slightly older version of apache, apache-1.3.31, with similar options and mod_dav enabled is working on a FreeBSD 4.8 system here that's running OpenPKG Release 2.2 (mostly). Has anybody here seen similar problems? Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Softwa

Re: openpkg/IRIX: bootstrap problems

2005-09-22 Thread Matthias Kurz
On Thu, Sep 22, 2005, Stuart Shelton wrote: > > Using openpkg-20050920, curl fails with: > > cc: ERROR File = /usr/include/openssl/kssl.h, Line = 72 This should not be included at all. The system supplied openssl should not be used. > The source file "krb5.h" is unavailable. > > #include

openpkg/IRIX: bootstrap problems

2005-09-22 Thread Stuart Shelton
Using openpkg-20050920, curl fails with: cc: ERROR File = /usr/include/openssl/kssl.h, Line = 72 The source file "krb5.h" is unavailable. #include ^ 1 catastrophic error detected in the compilation of "file.c". Compilation terminated. make[3]: *** [file.lo] Error 1 make

Re: GTK2 problems

2005-09-03 Thread Matthias Kurz
On Sat, Sep 03, 2005, Matthias Kurz wrote: [...] > It may be possible that the modules need to "communicate" together and > with the main part of pango (e.g. by registering common identifiers with > glib routines). This will not work when everyone has its "private" > instance of glib2. Well, ther

GTK2 problems

2005-09-03 Thread Matthias Kurz
Hi. After the upgrade to the latest gtk2 stuff, everything is broken. To get things fixed, i recommend we use "xchat" as the sample and make it going again. I use it and it does not have much dependencies. The main source of problems[1] seems to be the "pango" package, cu

Re: Dependency problems, apache and with_mod_php_dom

2005-06-18 Thread Bill Campbell
On Sat, Jun 18, 2005, Ralf S. Engelschall wrote: >On Fri, Jun 17, 2005, Bill Campbell wrote: > >> I ran into a problem today building UPD/apache-1.3.33-2.3.3.src.rpm on a >> SuSE 9.2 Professional system where it wasn't finding necessary libraries >> which turned out to have been found in the SuSE g

Re: Dependency problems, apache and with_mod_php_dom

2005-06-18 Thread Ralf S. Engelschall
On Fri, Jun 17, 2005, Bill Campbell wrote: > I ran into a problem today building UPD/apache-1.3.33-2.3.3.src.rpm on a > SuSE 9.2 Professional system where it wasn't finding necessary libraries > which turned out to have been found in the SuSE gcrypt package. > > This had been building on our in-ho

Re: Any known problems with cvs-1.12.11 ?

2005-05-04 Thread Matthias Kurz
On Wed, May 04, 2005, Michael Schloh wrote: > On Tue, May 03, 2005, Matthias Kurz wrote: > > When i try e.g. 'cvs status' with a CVSROOT of ":ext:..." and > > CVS_RSH=ssh, i get an output like: > > > Yes, cvs 1.12.11 is flawed. I believe it is not a packaging issue, but > then again I've not looke

Re: Any known problems with cvs-1.12.11 ?

2005-05-04 Thread Michael Schloh
mends > to use --with-external-zlib, because i have 1.2.2 from CURRENT installed. > Should this be the default (and cvs depend on zlib) ? > Good idea, that way we can control CVS's compression and security problems from one source. Packages since today have the feature you mention:

Any known problems with cvs-1.12.11 ?

2005-05-03 Thread Matthias Kurz
Hi. When i try e.g. 'cvs status' with a CVSROOT of ":ext:..." and CVS_RSH=ssh, i get an output like: cvs status: nothing known about `cvs server' === File: no file cvs serverStatus: Unknown Working revision:No en

Re: Problems with '+' in package names ?

2005-02-22 Thread Matthias Kurz
On Mon, Feb 21, 2005, Thomas Lotterer wrote: [...] > ... Along with this issue we learned about the > interesting --allmatches [3] option which makes RPM erase all packages > matching all packages sharing a common prefix. Well suited to remove all subpackages together with

Re: Problems with '+' in package names ?

2005-02-22 Thread Matthias Kurz
On Mon, Feb 21, 2005, Ralf S. Engelschall wrote: > On Mon, Feb 21, 2005, Matthias Kurz wrote: > > > Are there problems with '+' in package names ? > > Yes, RPM has problems with it (or at least does strange interpretations) > so we avoided it at all in the past.

Re: Problems with '+' in package names ?

2005-02-21 Thread Thomas Lotterer
On Mon, Feb 21, 2005, Matthias Kurz wrote: > Hi. > Are there problems with '+' in package names ? > When we introduced RPM 4.2.1 in OpenPKG 2.0 we encountered occasional strange behavior where RPM allowed two packages whose name-version-release combination contained a 

Re: Problems with '+' in package names ?

2005-02-21 Thread Ralf S. Engelschall
On Mon, Feb 21, 2005, Matthias Kurz wrote: > Are there problems with '+' in package names ? Yes, RPM has problems with it (or at least does strange interpretations) so we avoided it at all in the past. Ralf S

Problems with '+' in package names ?

2005-02-21 Thread Matthias Kurz
Hi. Are there problems with '+' in package names ? (mk) -- Matthias Kurz; Fuldastr. 3; D-28199 Bremen; VOICE +49 421 53 600 47 >> Im prämotorischen Cortex kann jeder ein Held sein. (bdw) <<

Re: Problems compiling netpbm

2005-02-10 Thread Ralf S. Engelschall
On Wed, Feb 09, 2005, Matthias Kurz wrote: > There seems to be a typo in netpbm.spec that causes a compile of the > included jasper sources. This fails under Solaris 10. > > In netpbm.spec > echo "JASPERLIB_HDR = %{l_prefix}/include" > should read > echo "JASPERHDR_DIR = %{l_prefix}/in

Problems compiling netpbm

2005-02-09 Thread Matthias Kurz
Hi. There seems to be a typo in netpbm.spec that causes a compile of the included jasper sources. This fails under Solaris 10. In netpbm.spec echo "JASPERLIB_HDR = %{l_prefix}/include" should read echo "JASPERHDR_DIR = %{l_prefix}/include" (mk) -- Matthias Kurz; Fuldastr. 3; D

Re: problems with the OpenPKG build process

2004-12-13 Thread Michael van Elst
On Mon, Dec 13, 2004 at 10:20:49PM +0100, Martin Konold wrote: > When compiling php from OpenPKG 2.2 the resulting binary is linked to the > _system _ library libgcrypt dynamically. (This is new behavior in 2.2 and was > not present before) There are two problems. One is that of

problems with the OpenPKG build process

2004-12-13 Thread Martin Konold
Hi, Sofar several times we got hit by the very same OpenPKG specific issue of lack of separation of the system libraries and the OpenPKG environment. An illustration: When compiling php from OpenPKG 2.2 the resulting binary is linked to the _system _ library libgcrypt dynamically. (This is ne

Re: PHP and Apache php.ini problems, Release 2.2

2004-11-30 Thread Steffen Hansen
On Tuesday 30 November 2004 22:08, Ralf S. Engelschall wrote: > On Tue, Nov 30, 2004, Bill Campbell wrote: > > I just spent a fair amount of time figuring out why horde and imp > > weren't working on a system where I had recently updated them from > > OpenPKG Release 2.1 to Release 2.2, and finally

Re: PHP and Apache php.ini problems, Release 2.2

2004-11-30 Thread Bill Campbell
On Tue, Nov 30, 2004, Ralf S. Engelschall wrote: >On Tue, Nov 30, 2004, Bill Campbell wrote: > >> I just spent a fair amount of time figuring out why horde and imp weren't >> working on a system where I had recently updated them from OpenPKG Release >> 2.1 to Release 2.2, and finally tracked it dow

Re: PHP and Apache php.ini problems, Release 2.2

2004-11-30 Thread Ralf S. Engelschall
On Tue, Nov 30, 2004, Bill Campbell wrote: > I just spent a fair amount of time figuring out why horde and imp weren't > working on a system where I had recently updated them from OpenPKG Release > 2.1 to Release 2.2, and finally tracked it down to two things which I was > able to fix by fiddling

PHP and Apache php.ini problems, Release 2.2

2004-11-30 Thread Bill Campbell
I just spent a fair amount of time figuring out why horde and imp weren't working on a system where I had recently updated them from OpenPKG Release 2.1 to Release 2.2, and finally tracked it down to two things which I was able to fix by fiddling the etc/apache/php.ini and etc/php/php.ini files.

Re: pdksh build problems, Release 2.2 on SuSE 9.2 Professional

2004-11-09 Thread Ralf S. Engelschall
On Mon, Nov 08, 2004, Bill Campbell wrote: > The build of pdksh-5.2.14-2.2.0.src.rpm fails on SuSE 9.2 Professional > because of a syntax error in the siglist.sh script's rather complex trap > statement. My CBE (Crude But Effective) fix is to change the #!/bin/sh > line in the script to use the O

pdksh build problems, Release 2.2 on SuSE 9.2 Professional

2004-11-08 Thread Bill Campbell
The build of pdksh-5.2.14-2.2.0.src.rpm fails on SuSE 9.2 Professional because of a syntax error in the siglist.sh script's rather complex trap statement. My CBE (Crude But Effective) fix is to change the #!/bin/sh line in the script to use the OpenPKG version of bash. The attached patch is again

Aspell build problems, Release 2.2

2004-11-08 Thread Bill Campbell
I've run into problems building aspell under OpenPKG Release 2.2 This same error occured on SuSE 8.2 and SuSE 9.2 Professional. The problem seems to be related to the gettext package, but I'm not very familiar with c++, and haven't been able to figure out why this isn't wor

Minor problems with oracle-barebone-9.2.0-20040818

2004-09-15 Thread Dennis McRitchie
Hi Ralf, Nice job on OpenPKG 2.x. I finally upgraded from 1.3+ and it generally went quite smoothly. Just a few problems with oracle-barebone this time around. 1) I believe oracle-barebone.pl should list "network/admin/samples" in addition to "network/admin" since the spec

Re: Package Upgrade Problems

2004-09-09 Thread David M. Fetter
Looks like our mail system cut out my shell script based on it's extension. I gzip'ed it instead here. On Thu, 2004-09-09 at 10:03, David M. Fetter wrote: > On Wed, 2004-09-08 at 22:27, Ralf S. Engelschall wrote: > > > Shouldn't the newer version of the software and the openpkg revision > > > mak

Re: Package Upgrade Problems

2004-09-09 Thread David M. Fetter
WARNING: This e-mail has been altered by the PSU Mail System. An attachment of type text/x-sh, named "opkg-update.sh" was removed from this e-mail message as it constituted a potential security hazard. Various attachment types are used by viruses and/or spammers in an attempt to compromise your c

Re: Package Upgrade Problems

2004-09-08 Thread Ralf S. Engelschall
On Wed, Sep 08, 2004, David M. Fetter wrote: > I manually upgraded a couple packages out of the UPD directory for 2.1, > however, when I run my auto update script it wants to update them. See > here: > > lynx-2.8.5-2.1.1UPDATE lynx-2.8.5-2.1.0 > openpkg-tools-0.8.18-2.1.3

Package Upgrade Problems

2004-09-08 Thread David M. Fetter
I manually upgraded a couple packages out of the UPD directory for 2.1, however, when I run my auto update script it wants to update them. See here: lynx-2.8.5-2.1.1UPDATE lynx-2.8.5-2.1.0 openpkg-tools-0.8.18-2.1.3 UPDATE openpkg-tools-0.8.15-2.1.0 Shouldn't the

RE: [tru64] fsl build problems

2004-04-23 Thread Karl Vogel
> > That fixes the first 2 errors (socklen_t & addrinfo), but > the modf() in > > lib_cfg is still present: > > > > So http://cvs.ossp.org/chngview?cn=4512 should also be put > into the cfg lib. > > > Did it. Examined other OSSP libraries cfg, ex, l2, pcre, popt, > sa, str, tai, val and var as

Re: [tru64] fsl build problems

2004-04-23 Thread Thomas Lotterer
On Fri, Apr 23, 2004, Karl Vogel wrote: > That fixes the first 2 errors (socklen_t & addrinfo), but the modf() in > lib_cfg is still present: > > So http://cvs.ossp.org/chngview?cn=4512 should also be put into the cfg lib. > Did it. Examined other OSSP libraries cfg, ex, l2, pcre, popt, sa, str,

RE: [tru64] fsl build problems

2004-04-23 Thread Karl Vogel
> > > You are very close to getting access to Tru64 using OpenPKG > > > OpenSSH :-) > > > > What's that saying again: "1 step forward, 2 steps back.." > > :-( > > > Well, that's where the term development *cycle* comes from :-) Let's > spin the wheel again. I hit that problem myself on Solaris

Re: [tru64] fsl build problems

2004-04-23 Thread Thomas Lotterer
On Fri, Apr 23, 2004, Karl Vogel wrote: > > You are very close to getting access to Tru64 using OpenPKG > > OpenSSH :-) > > What's that saying again: "1 step forward, 2 steps back.." > :-( > Well, that's where the term development *cycle* comes from :-) Let's spin the wheel again. I hit that pr

RE: [tru64] fsl build problems

2004-04-23 Thread Karl Vogel
> > The vsyslog() call [in fsl] is used in the syslog() > function, which is > > BEFORE the vsyslog() function and since there is no > function prototype > > at the start of the source, the compiler implicitly declares the > > vsyslog() function The fix is easy... put the vsyslog() function > > b

Re: [tru64] fsl build problems

2004-04-22 Thread Thomas Lotterer
On Thu, Apr 22, 2004, Karl Vogel wrote: Karl, thanks again for the feedback. > The vsyslog() call [in fsl] is used in the syslog() function, which is > BEFORE the vsyslog() function and since there is no function prototype > at the start of the source, the compiler implicitly declares the > vsysl

Re: [tru64] fsl build problems

2004-04-22 Thread Thomas Lotterer
On Thu, Apr 22, 2004, Karl Vogel wrote: Karl, > The fsl build is failing: [... > OSSP l2 requires -lm on Tru64 and QNX to get modf(3)] > we just fixed this in OSSP l2 [1] and OSSP fsl will pick this up in a few hours along with other unrelated changes. [1] http://cvs.ossp.org/chngview?cn=4512

RE: [tru64] fsl build problems

2004-04-22 Thread Karl Vogel
After adding the necessary -lm to LIBS in the Makefiles, I hit the following error: --- make[1]: Leaving directory `/cluster/members/member0/tmp/openpkg/RPM/TMP/fsl-1.4.0' /tmp/openpkg/bin/cc -D_XOPEN_SOURCE_EXTENDED -Ilib_l2 -Ilib_cfg -Ilib_pcre -DHAVE_CONFIG_H -O -Ilib_l2 -Ilib_cfg -Ilib_pcre -

[tru64] fsl build problems

2004-04-22 Thread Karl Vogel
The fsl build is failing: --- ./libtool --mode=link --quiet /tmp/openpkg/bin/cc -L. -o l2tool l2tool.o libl2.la modf collect2: ld returned 1 exit status make: *** [l2tool] Error 1 --- This looks familiar.. seems like the math lib is missing, adding -lm to the link line fixes this. $ grep modf *

[OpenPKG #18013] Solution for Problems building xemacs on Solaris

2004-04-21 Thread Ralf S. Engelschall via RT
Request 18013 was acted upon. _ URL: https://rt.openpkg.org/id/18013 Ticket: [OpenPKG #18013] Subject: Solution for Problems building xemacs on Solaris Requestors: [EMAIL PROTECTED] Queue: openpkg

Re: [PATCH]: Tru64 V5.1 gcc34 build problems

2004-04-21 Thread Ralf S. Engelschall
On Wed, Apr 21, 2004, Karl Vogel wrote: > [...] > It can be a problem if gcc is already installed, as gcc doesn't understand > the -ieee parameter and thus the build will fail in that case. > > I noticed that you put a check for gcc in the .spec file > (in the with_profile part). Can this also be

RE: [PATCH]: Tru64 V5.1 gcc34 build problems

2004-04-21 Thread Karl Vogel
> > * compile error: > > > > cc: Error: > /tmp/openpkg/RPM/TMP/gcc-3.4-20040414/libiberty/floatformat.c, > > line 319: In this statement, the libraries on this platform > do not yet > > support compile-time evaluation of the constant expression > "0.0/0.0". > > (constfoldns) > >dto = NA

Re: [PATCH]: Tru64 V5.1 gcc34 build problems

2004-04-21 Thread Ralf S. Engelschall
> * install-sh not found > > To resolve the install-sh problem, I've added --srcdir to the configure > options, that way the path to the install-sh script is an absolute path. > [...] That's a good workaround which doesn't hurt on any platform, so I've taken over this. > * compile error: > > c

[OpenPKG #18013] Solution for Problems building xemacs on Solaris

2004-04-20 Thread Warnes, Gregory R via RT
Request 18013 was acted upon. _ URL: https://rt.openpkg.org/id/18013 Ticket: [OpenPKG #18013] Subject: Solution for Problems building xemacs on Solaris Requestors: [EMAIL PROTECTED] Queue: openpkg

[PATCH]: Tru64 V5.1 gcc34 build problems

2004-04-19 Thread Karl Vogel
Here is a patch to correct the problems on Tru64. This corrects: * install-sh not found To resolve the install-sh problem, I've added --srcdir to the configure options, that way the path to the install-sh script is an absolute path. * compile error: cc: Error: /tmp/openpkg/RPM/TMP/gc

Re: Tru64 V5.1 --gcc34 build problems/resolutions

2004-04-18 Thread Karl Vogel
using the Compaq C compiler (not when you already have a gcc build). * Tru64 has no GNU as/ld. So I had to set with_binutils=no. Using a platform check in the spec would be cleaner I guess. This got me until the install phase, where I bumped into problems with install-sh again. Apparently the Mak

Re: Problems with openpkg-CURRENT

2004-04-14 Thread Ralf S. Engelschall
On Wed, Apr 14, 2004, Matthias Kurz wrote: > "openpkg" does not build since upgrade to tar-1.13.94. The build of > tar fails, because "ICONV_CONST" is not defined. > Well, the easy solution is to take over the config.cache munging from > the "regular" tar package to openpkg.spec. > > ( echo 'a

Problems with openpkg-CURRENT

2004-04-14 Thread Matthias Kurz
Hi. "openpkg" does not build since upgrade to tar-1.13.94. The build of tar fails, because "ICONV_CONST" is not defined. Well, the easy solution is to take over the config.cache munging from the "regular" tar package to openpkg.spec. ( echo 'am_cv_func_iconv=no' echo 'am_cv_lib_iconv=n

Re: Problems with rsync

2004-04-02 Thread Ralf S. Engelschall
On Fri, Apr 02, 2004, Matthias Kurz wrote: > rsync: failed to connect to rsync.openpkg.org: Connection refused > rsync error: error in socket IO (code 10) at clientserver.c(83) > > Looks like the rsync server is cacked off. Well, yes, this beast segfaults from time to time and no one until now ha

Problems with rsync

2004-04-02 Thread Matthias Kurz
Hi. I get this: rsync: failed to connect to rsync.openpkg.org: Connection refused rsync error: error in socket IO (code 10) at clientserver.c(83) Looks like the rsync server is cacked off. (mk) -- Matthias Kurz; Fuldastr. 3; D-28199 Bremen; VOICE +49 421 53 600 47 >> Im prämotorischen

Re: CVS problems

2004-02-28 Thread Ralf S. Engelschall
On Sat, Feb 28, 2004, Matthias Kurz wrote: > Looks like the CVS server is not running. Is this intended ? > cvs [checkout aborted]: connect to cvs.openpkg.org(195.27.176.150):2401 failed: > Connection refused No, it isn't intended, but this "cvs pserverd" is crashing from time to time. Ok, perha

CVS problems

2004-02-28 Thread Matthias Kurz
Hi. Looks like the CVS server is not running. Is this intended ? cvs [checkout aborted]: connect to cvs.openpkg.org(195.27.176.150):2401 failed: Connection refused (mk) -- Matthias Kurz; Fuldastr. 3; D-28199 Bremen; VOICE +49 421 53 600 47 >> Im prämotorischen Cortex kann jeder ein He

Re: Darwin problems with cpio in rpm.

2004-01-02 Thread Bill Campbell
e, into a small test program which worked >> fine). >> >> I've been running a non OpenPKG version of rpm-4.0.2 on OS X with no >> problems using these patches (which don't seem to do anything to cpio >> related code except possibly the LIBMISC additions in

[OpenPKG #302] Continuing problems building perl-tk

2003-12-09 Thread Dennis McRitchie via RT
Request 302 was acted upon. _ URL: https://rt.openpkg.org/id/302 Ticket: [OpenPKG #302] Subject: Continuing problems building perl-tk Requestors: [EMAIL PROTECTED] Queue: openpkg Owner

Re: problems [coreutils]

2003-11-01 Thread Thomas Lotterer
On Tue, Oct 28, 2003, Matthias Kurz wrote: > On Thu, Oct 23, 2003, Thomas Lotterer wrote: > > > On Thu, Oct 23, 2003, Matthias Kurz wrote: > > > > > [...] > > > coreutils > > > - > > > Making all in man > > > Updating man page nice.1 > > > Updating man page stat.1 > > > Updating man page

Re: problems

2003-10-27 Thread Matthias Kurz
On Thu, Oct 23, 2003, Ralf S. Engelschall wrote: > On Thu, Oct 23, 2003, Matthias Kurz wrote: > [...] > > gimp > > > > configure: WARNING: *** AA plug-in will not be built (AA library not found) *** > > configure: WARNING: *** MPEG plug-in will not be built (MPEG library not found) > > confi

Re: problems [coreutils]

2003-10-27 Thread Matthias Kurz
On Thu, Oct 23, 2003, Thomas Lotterer wrote: > On Thu, Oct 23, 2003, Matthias Kurz wrote: > > > [...] > > coreutils > > - > > Making all in man > > Updating man page nice.1 > > Updating man page stat.1 > > Updating man page test.1 > > chmod: WARNING: can't access stat.1 > > chmod: WARNING

Re: nn (was: problems)

2003-10-27 Thread Matthias Kurz
On Thu, Oct 23, 2003, Matthias Kurz wrote: > On Thu, Oct 23, 2003 at 04:41:12PM +0200, Matthias Kurz wrote: > [...] > > nn > > -- > > Uses 'uname' to get hostname. This does not work, when the result > > of 'uname' is not a fully qualified domain name. > > hostname=baerlap, You need a fully qualif

Re: problems

2003-10-23 Thread Ralf S. Engelschall
On Thu, Oct 23, 2003, Matthias Kurz wrote: > [...] > tcpdump > --- > Adds -I/usr/local/include and -L/usr/local/lib to the link line, which > causes the link to fail because it takes libraries from /usr/local/lib. > Added > %{l_shtool} subst -e 's;-I/usr/local/include;;' -e 's;-L/usr/local

Re: problems [coreutils]

2003-10-23 Thread Thomas Lotterer
On Thu, Oct 23, 2003, Matthias Kurz wrote: > [...] > coreutils > - > Making all in man > Updating man page nice.1 > Updating man page stat.1 > Updating man page test.1 > chmod: WARNING: can't access stat.1 > chmod: WARNING: can't access test.1 > make[2]: *** [test.1] Error 1 > make[2]: ***

Re: nn (was: problems)

2003-10-23 Thread Ralf S. Engelschall
On Thu, Oct 23, 2003, Matthias Kurz wrote: > > Uses 'uname' to get hostname. This does not work, when the result > > of 'uname' is not a fully qualified domain name. > > hostname=baerlap, You need a fully qualified domain name > > This will probably not work for Solaris-x86: > > + M=sparc > > + /o

nn (was: problems)

2003-10-23 Thread Matthias Kurz
On Thu, Oct 23, 2003 at 04:41:12PM +0200, Matthias Kurz wrote: [...] > nn > -- > Uses 'uname' to get hostname. This does not work, when the result > of 'uname' is not a fully qualified domain name. > hostname=baerlap, You need a fully qualified domain name > This will probably not work for Solaris-

Release engineering; unresolved package problems

2003-10-23 Thread Matt Hoosier
There are still problems with the filenaming conventions on the 'apt' package. Ticket #270 that I submitted a while ago in RT is still sitting out there, and describes the problem in a fair amount of detail. In a nutshell, the OpenPKG patches to apt have inconsistently altered the n

problems

2003-10-23 Thread Matthias Kurz
Hi. http://www.mail-archive.com/openpkg-dev%40openpkg.org/msg10767.html Here my list of current problems with some solutions. I'm mainly using Solaris-x86. gcc --- When configured with with_binutils=no, "-z text" should be removed from the specs (s/-z text//g). Else it canno

[OpenPKG #254] [bootstrap] file locking problems

2003-09-14 Thread Ralf S. Engelschall via RT
Request 254 was acted upon. _ URL: https://rt.openpkg.org/id/254 Ticket: [OpenPKG #254] Subject: [bootstrap] file locking problems Requestors: [EMAIL PROTECTED] Queue: openpkg Owner: Nobody

[OpenPKG #254] [bootstrap] file locking problems

2003-09-14 Thread Ralf S. Engelschall via RT
Request 254 was acted upon. _ URL: https://rt.openpkg.org/id/254 Ticket: [OpenPKG #254] Subject: [bootstrap] file locking problems Requestors: [EMAIL PROTECTED] Queue: openpkg Owner: Nobody

[OpenPKG #254] [bootstrap] file locking problems

2003-09-13 Thread [EMAIL PROTECTED] via RT
Request 254 was acted upon. _ URL: https://rt.openpkg.org/id/254 Ticket: [OpenPKG #254] Subject: [bootstrap] file locking problems Requestors: [EMAIL PROTECTED] Queue: openpkg Owner: Nobody

Re: Darwin problems with cpio in rpm.

2003-09-13 Thread Bill Campbell
On Fri, Sep 12, 2003, Ralf S. Engelschall wrote: >On Thu, Sep 11, 2003, Bill Campbell wrote: > >> I'm attempting to build OpenPKG release 1.3 on OS X/Darwin, and it builds >> with one minor hack in gzip to keep it from trying to use the assembler. >> Unfortunately once it's built, rpm fails when at

Re: Darwin problems with cpio in rpm.

2003-09-12 Thread Ralf S. Engelschall
e anything that just jumps out at me. I thought it might be an endian > problem, but it doesn't appear that's the problem (I pulled the ENDIAN > tests out of the verify.c routine, into a small test program which worked > fine). > > I've been running a non OpenPKG v

Darwin problems with cpio in rpm.

2003-09-11 Thread Bill Campbell
sn't appear that's the problem (I pulled the ENDIAN tests out of the verify.c routine, into a small test program which worked fine). I've been running a non OpenPKG version of rpm-4.0.2 on OS X with no problems using these patches (which don't seem to do anything to cpio relat

Re: Solaris bootstrap problems (was: Re: bashisms in openpkg.boot)

2003-09-01 Thread Ralf S. Engelschall
inker commands during build? > > 2.6: The installation of rpm runs a script "installplatform". This has > a "#!/usr/bin/env bash" in the beginning. There is no bash on 2.6. > This did not cause problems on Solaris 8, because there is a > /bin/bash in

Solaris bootstrap problems (was: Re: bashisms in openpkg.boot)

2003-09-01 Thread Matthias Kurz
exist - using root I also saw something like -L/usr/ucblib -R/usr/ucblib - that is ugly :) 2.6: The installation of rpm runs a script "installplatform". This has a "#!/usr/bin/env bash" in the beginning. There is no bash on 2.6. This did not cause problems on So

Re: CVS problems

2003-08-14 Thread Michael van Elst
On Thu, Aug 14, 2003, Matthias Kurz wrote: Matthias, > All i get is: > > cvs [update aborted]: connect to cvs.openpkg.org:2401 failed: Connection refused the CVS pserver is running again. Greetings, -- ,eM""=.a"-. Michael van Elst dWWMWM" -

CVS problems

2003-08-14 Thread Matthias Kurz
Hi. All i get is: cvs [update aborted]: connect to cvs.openpkg.org:2401 failed: Connection refused (mk) -- Matthias Kurz; Fuldastr. 3; D-28199 Bremen; VOICE +49 421 53 600 47 >> Im prämotorischen Cortex kann jeder ein Held sein. (bdw) <<

Re: CVS problems

2003-08-14 Thread Ralf S. Engelschall
On Thu, Aug 14, 2003, Matthias Kurz wrote: > All i get is: > cvs [update aborted]: connect to cvs.openpkg.org:2401 failed: Connection refused Fixed, now works again: | $ cvs -d :pserver:[EMAIL PROTECTED]:/e/openpkg/cvs co openpkg-src/bind | cvs server: Updating openpkg-src/bind | U openpkg-src/b

[OpenPKG #171] python package fully broken: linkchecker shows problems

2003-07-14 Thread Michael van Elst via RT
Request 171 was acted upon. This is an automatically generated message. URL: https://rt.openpkg.org/id/171 Ticket: [OpenPKG #171] Subject: python package fully broken: linkchecker shows problems

[OpenPKG #171] python package fully broken: linkchecker shows problems

2003-07-14 Thread Michael van Elst via RT
Request 171 was acted upon. _ URL: https://rt.openpkg.org/id/171 Ticket: [OpenPKG #171] Subject: python package fully broken: linkchecker shows problems Requestors: [EMAIL PROTECTED] Queue

[OpenPKG #171] python package fully broken: linkchecker shows problems

2003-07-04 Thread Ralf S. Engelschall via RT
Request 171 was acted upon. _ URL: https://rt.openpkg.org/id/171 Ticket: [OpenPKG #171] Subject: python package fully broken: linkchecker shows problems Requestors: [EMAIL PROTECTED] Queue

[OpenPKG #20] Problems with IMAPD-Package

2003-06-04 Thread Ralf S. Engelschall via RT
Request 20 was acted upon. This is an automatically generated message. URL: https://rt.openpkg.org/id/20 Ticket: [OpenPKG #20] Subject: Problems with IMAPD-Package Requestors: Queue: openpkg

  1   2   >