perl error in openpkg build -Ua
I'm suddenly getting a perl error executing openpkg build -Ua. I don't recall making any changes that might have caused this. I was playing w/ ImageMagick awhile back the last time I had some free time, but I only recall adding packages of all sorts, not removing any. Here is the error I'm getting: [EMAIL PROTECTED] openpkg build -Ua update.sh no element found at line 1, column 0, byte 0 at /cw/lib/perl/vendor_perl/5.8.4/i386-freebsd/XML/Parser.pm line 187 ...any help would be appreciated. Thanks, Frank __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: perl error in openpkg build -Ua
On Fri, Oct 15, 2004 at 02:18:17AM -0500, F. Even wrote: [EMAIL PROTECTED] openpkg build -Ua update.sh no element found at line 1, column 0, byte 0 at /cw/lib/perl/vendor_perl/5.8.4/i386-freebsd/XML/Parser.pm line 187 The XML parser cannot decode the index, probably because you cannot fetch it correctly (firewalls? NAT?) or because the index is defective. Greetings, -- Michael van Elst Internet: [EMAIL PROTECTED] A potential Snark may lurk in every tree. __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: perl error in openpkg build -Ua
F. Even wrote: I'm suddenly getting a perl error executing openpkg build -Ua. I don't recall making any changes that might have caused this. I was playing w/ ImageMagick awhile back the last time I had some free time, but I only recall adding packages of all sorts, not removing any. Here is the error I'm getting: [EMAIL PROTECTED] openpkg build -Ua update.sh no element found at line 1, column 0, byte 0 at /cw/lib/perl/vendor_perl/5.8.4/i386-freebsd/XML/Parser.pm line 187 OKI've tried it a couple more timesand now it is suddenly working. Not sure I understand why...I have not changed anything. Could the error have come if ftp.openpkg.org was unavailable to me for some odd reason? That's the only thing I can think of. Thanks! __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: kolab on openpkg for amd64
On October 14, 2004 03:05 pm, Steffen Hansen wrote:
That sounds like rebuilding never even started. I guess the
corresponding .install.log files are 0 bytes too or maybe not even
created.
So something is quite wrong. What about the inital bootstrap .sh
package. Are /tmp/obmtool-openpkg-2.1.2-2.1.2.{rebuild|install}.log
also empty?
regards
The /tmp/obmtool-openpkg-2.1.2-2.1.2.{rebuild|install}.log files are not
empty. They seem to indicate that the bootstrap completed successfully.
If you'd like I can send you copies of them.
Jason
__
The OpenPKG Projectwww.openpkg.org
User Communication List [EMAIL PROTECTED]
SpamAssassin final
I'd like to know if it is possible to update to the final 3.0.0 version, as I need a future corrected in this version. Thanks, Alex -- ATIX Tecnologia e Com Ltda Tel.: +55-(11) 4667-5900 This message was sent using IMP, the Internet Messaging Program. __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: SpamAssassin final
On Fri, Oct 15, 2004, Alexander Belck wrote: I'd like to know if it is possible to update to the final 3.0.0 version, as I need a future corrected in this version. Well, in OpenPKG 2.1 there cannot be 3.0.0 because at the time of OpenPKG 2.1 there existed only a 3.0.0pre2 and by policy we do not perform any vendor version upgrades within a release. But either use OpenPKG CURRENT today (which already has Spamassassin 3.0.0 final) or wait until next week after OpenPKG 2.2 is available (which then also contains Spamassassin 3.0.0). Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Updating rpm should preserve /opkg/etc/rc.d/rc.server
Today I updated apache following security advise. It happens that the instalation overides rc.apache that should be treated as a configuration file, since there ara options that could be set previously (and in this specific case, I needed to implement the graceful action). In general form I think that the rpm install script should at least rename the old version to .rpmsave or make the new a .rpmnew if files differ and display a warning. Thanks, Alex -- ATIX Tecnologia e Com Ltda Tel.: +55-(11) 4667-5900 This message was sent using IMP, the Internet Messaging Program. __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: perl-net
On Thu, Oct 14, 2004, Ralf S. Engelschall wrote: On Thu, Oct 14, 2004, Aaron Bostick wrote: I would like to be able to use a cpan module called Net::Jabber but the perl-net src rpm does not provide for this particular. I realize there are tons of cpan Net modules, so I am wondering if the ones included with openpkg are chosen specifically or can new modules be added to the rpm on request? The spec file looks straightforward to modify. If the module looks reasonable programmed enough and doesn't have much external dependencies, we can easy add it, of course. I'll look at this if time permits. And if not, is it common practice to just install modules from the cpan shell. I know if I do it that way, those files will not be under rpm control. Any bad side effects from this? Since OpenPKG 2.0 you can use the CPAN shell for installing arbitrary modules yourself side-by-side to the packaged ones. Except that they are not known by RPM and this have to be upgraded manually, there are no known side-effects. Net::Jabber is now part of OpenPKG CURRENT's perl-net-5.8.5-20041015 and higher. It will not become part of OpenPKG 2.2 because the 2.2 brach is already frozen. But it will be part of OpenPKG 2.3, of course. In the meantime you have to use CURRENT if you need Net::Jabber. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: Updating rpm should preserve /opkg/etc/rc.d/rc.server
On Fri, Oct 15, 2004, Alexander Belck wrote: Today I updated apache following security advise. It happens that the instalation overides rc.apache that should be treated as a configuration file, since there ara options that could be set previously (and in this specific case, I needed to implement the graceful action). No, rc.xxx are *not* configuration files! If you want to change some of its settings write them to rc.conf, please. In general form I think that the rpm install script should at least rename the old version to .rpmsave or make the new a .rpmnew if files differ and display a warning. .rpmsave are only created for config files. rc.xxx are not config files, hence no .rpmsave files. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: SpamAssassin final
To prepare my waries :-)) How do I upgrade a production instalation of OpenPKG from ver 2.1 to 2.2. Today I have allmost all (just miss freeradius-1.0.0_with-ldap and courier) OpenPKG I need from ver 2.1 build at my host and running from an instalation at /opkg. How should I proceed to get the new 2.2 release with all the same build option running ? Is it possible to have it at the same /opkg root without an spare Host with same underlaying OS (and same hardware??) to build the new pakages ? Temporarly, is it possible to instruct `openpkg build package` to get the lates package from CURRENT Release ? Thanks, Alex Citando Ralf S. Engelschall [EMAIL PROTECTED]: On Fri, Oct 15, 2004, Alexander Belck wrote: I'd like to know if it is possible to update to the final 3.0.0 version, as I need a future corrected in this version. Well, in OpenPKG 2.1 there cannot be 3.0.0 because at the time of OpenPKG 2.1 there existed only a 3.0.0pre2 and by policy we do not perform any vendor version upgrades within a release. But either use OpenPKG CURRENT today (which already has Spamassassin 3.0.0 final) or wait until next week after OpenPKG 2.2 is available (which then also contains Spamassassin 3.0.0). Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED] -- ATIX Tecnologia e Com Ltda Tel.: +55-(11) 4667-5900 This message was sent using IMP, the Internet Messaging Program. __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: Updating rpm should preserve /opkg/etc/rc.d/rc.server
Two questions 1) specificaly for apache I need the action graceful. Particulary I would prefer the way other distros handle apache using apachectl, that in some cases make extra check to avoid killing apache at all when reloading with a new miss-configuret apache.conf But at least could be the graceful action added to the standart rc.apache ? 2) My lake of knowlege. How should I use rc.conf ? I'm not used with that kind of startup, I guess its similar to debian ?? All I found is that all the rc.xxx files from OpenPKG have a %config section that could change the way a server starts. Should I repead the configuration settings I whant to change from rc.xxx in rc.conf with my setting ? Thanks, Alex Citando Ralf S. Engelschall [EMAIL PROTECTED]: On Fri, Oct 15, 2004, Alexander Belck wrote: Today I updated apache following security advise. It happens that the instalation overides rc.apache that should be treated as a configuration file, since there ara options that could be set previously (and in this specific case, I needed to implement the graceful action). No, rc.xxx are *not* configuration files! If you want to change some of its settings write them to rc.conf, please. In general form I think that the rpm install script should at least rename the old version to .rpmsave or make the new a .rpmnew if files differ and display a warning. .rpmsave are only created for config files. rc.xxx are not config files, hence no .rpmsave files. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED] -- ATIX Tecnologia e Com Ltda Tel.: +55-(11) 4667-5900 This message was sent using IMP, the Internet Messaging Program. __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
