Menu
▾
▴
libdbi-devel
|
From: Peter C. <cz...@ba...> - 2011-02-10 13:54:53
|
Hello, I wonder, when a new release of libdbi and libdbi-drivers could be done. I read in the archives, that there is a new testing framework and many work went in to make it happy. But now all tests are passing. Is there any chance for a release soon? Background: I help to maintain and upgrade syslog-ng in many different Linux distributions and BSDs. Recently many distributions enabled database (libdbi) support in their syslog-ng package/port. The problem is, that distributions feature the latest release, 0.8.3. Many of 0.8.3's problems are already fixed in the CVS version. The most notable example is sqlite: support in syslog-ng works only with the CVS version. See http://sourceforge.net/mailarchive/forum.php?thread_name=1217316368.7005.72.camel%40bzorp.balabit&forum_name=libdbi-drivers-devel Thank you for your help and your great software, -- Peter Czanik (CzP) <cz...@ba...> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/ |
|
From: <mar...@mh...> - 2011-02-10 21:57:30
|
Peter Czanik writes: > Hello, > > I wonder, when a new release of libdbi and libdbi-drivers could be done. > I read in the archives, that there is a new testing framework and many > work went in to make it happy. But now all tests are passing. Is there > any chance for a release soon? > > Background: I help to maintain and upgrade syslog-ng in many different > Linux distributions and BSDs. Recently many distributions enabled > database (libdbi) support in their syslog-ng package/port. The problem > is, that distributions feature the latest release, 0.8.3. Many of > 0.8.3's problems are already fixed in the CVS version. > The most notable example is sqlite: support in syslog-ng works only with > the CVS version. See > http://sourceforge.net/mailarchive/forum.php?thread_name=1217316368.7005.72.camel%40bzorp.balabit&forum_name=libdbi-drivers-devel > > Thank you for your help and your great software, Hi, I feel your pain, and I wish I could speed things up a bit. I had a few days off just when Sourceforge was hacked. As we have quite a list of patches and bugs to work on, I was reluctant to just go ahead without the ability to check them in one by one. CVS came back online just today, so I'll try to fix the remaining issues in the small amount of time that I can currently devote to my software projects. In any case, any kind of help is greatly appreciated to get the new release out anytime soon. Test the cvs version on any platform you can get hold of. Test the drivers with the latest database engines, as I personally can't always live on the bleeding edge. Proofread the docs and see whether they reflect the latest changes. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 |
|
From: Peter C. <cz...@ba...> - 2011-02-16 12:28:05
|
Hello, On 02/10/2011 10:59 PM, mar...@mh... wrote: > In any case, any kind of help is greatly appreciated to get the new > release out anytime soon. Test the cvs version on any platform you can > get hold of. Test the drivers with the latest database engines, as I > personally can't always live on the bleeding edge. Proofread the docs > and see whether they reflect the latest changes. > > I started testing on FreeBSD 8.1 (the current long term support release). I checked out the latest cvs version for libdbi and libdbi drivers. Libdbi: it only compiles if was configured with --disable-docs. Without this option, if openjade is missing, it fails because of that, if it's there, it still fails, because openjade does not like the document. Libdbi-drivers has the same problem with openjade. I compiled it with sqlite3 (my primary interest because of syslog-ng) and mysql5.5 (my primary db platform). Compilation/installation went fine, but running "make check" failed. Should I send the output of "make check" here (it's quite long...), or only privately? My next check will be, how it works with syslog-ng. I already see, that it compiled OK. And I'll also check it on Linux (openSUSE 11.4 RC1) Bye, -- Peter Czanik (CzP) <cz...@ba...> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/ |
|
From: Markus H. <mar...@mh...> - 2011-02-16 14:42:13
|
Hi Peter, Peter Czanik <cz...@ba...> was heard to say: > I started testing on FreeBSD 8.1 (the current long term support > release). I checked out the latest cvs version for libdbi and libdbi > drivers. > That's good as this is my main platform as well. This should make it easier for me to reproduce any problems that you run into. > Libdbi: it only compiles if was configured with --disable-docs. Without > this option, if openjade is missing, it fails because of that, if it's > there, it still fails, because openjade does not like the document. > Bootstrapping from a cvs checkout is a bit trickier than building from a tarball. We decided back then to ship the PDFs and HTMLs along with the DocBook sources, so the end-user should never need to build the docs. I'll see if I can build the docs on 8.1, but I can't recall ever having problems with this as long as the SGML toolchain is complete (including DocBook DSSSL stylesheets, an appropriate CATALOG file, and a proper $SGML_CATALOG_FILES). SGML is darn old-fashioned, but I hesitate to convert the docs to XML. You'd require Java and FOP to build PDFs then, besides XSL stylesheets and xsltproc. We could as well drop PDFs altogether and build only HTML docs with xsltproc. I'm open to suggestions here. Are xsltproc and the DocBook XSL stylesheets likely to be installed on a run-of-the-mill computer these days? > Libdbi-drivers has the same problem with openjade. I compiled it with > sqlite3 (my primary interest because of syslog-ng) and mysql5.5 (my > primary db platform). Compilation/installation went fine, but running > "make check" failed. Should I send the output of "make check" here (it's > quite long...), or only privately? > Below is the cause of the failure. Joao, are you listening? This looks like a cgreen problem to me. Is it necessary to install cgreen separately in order to make this work? Could you please look into this? --8<--- FATAL ERROR: Could not find ./bin/my_print_defaults If you compiled from source, you need to run 'make install' to copy the software into the correct location ready for operation. If you are using a binary release, you must either be at the top level of the extracted archive, or pass the --basedir option pointing to that location. --8<--- The sqlite3-specific output of the test looks fine to me. > it compiled OK. And I'll also check it on Linux (openSUSE 11.4 RC1) > Much appreciated as I don't have a SuSE system around here. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 |
|
From: João H. F. <jo...@gm...> - 2011-02-16 15:04:42
|
Hi, I am listenning. >> Libdbi-drivers has the same problem with openjade. I compiled it with >> sqlite3 (my primary interest because of syslog-ng) and mysql5.5 (my >> primary db platform). Compilation/installation went fine, but running >> "make check" failed. Should I send the output of "make check" here (it's >> quite long...), or only privately? >> Send the log to me (private). > > Below is the cause of the failure. Joao, are you listening? This looks > like a cgreen problem to me. Is it necessary to install cgreen > separately in order to make this work? Could you please look into this? > I will investigate. -- ----------------------------------------------------------- João Henrique Freitas - joaohf_at_gmail.com Campinas-SP-Brasil BSD051283 LPI 1 http://www.joaohfreitas.eti.br |
|
From: Peter C. <cz...@ba...> - 2011-02-16 15:09:05
|
On 02/16/2011 03:42 PM, Markus Hoenicka wrote:
> Hi Peter,
>
> Peter Czanik <cz...@ba...> was heard to say:
>
>> I started testing on FreeBSD 8.1 (the current long term support
>> release). I checked out the latest cvs version for libdbi and libdbi
>> drivers.
>>
>
> That's good as this is my main platform as well. This should make it
> easier for me to reproduce any problems that you run into.
>
>> Libdbi: it only compiles if was configured with --disable-docs. Without
>> this option, if openjade is missing, it fails because of that, if it's
>> there, it still fails, because openjade does not like the document.
>>
>
> Bootstrapping from a cvs checkout is a bit trickier than building from
> a tarball. We decided back then to ship the PDFs and HTMLs along with
> the DocBook sources, so the end-user should never need to build the
> docs. I'll see if I can build the docs on 8.1, but I can't recall ever
> having problems with this as long as the SGML toolchain is complete
> (including DocBook DSSSL stylesheets, an appropriate CATALOG file, and
> a proper $SGML_CATALOG_FILES).
Well, the Makefile only complained about the missing openjade, I did not
install anything else. I guess, I better wait for you here, as I don't
know these tools at all...
> SGML is darn old-fashioned, but I hesitate to convert the docs to XML.
> You'd require Java and FOP to build PDFs then, besides XSL stylesheets
> and xsltproc. We could as well drop PDFs altogether and build only
> HTML docs with xsltproc. I'm open to suggestions here. Are xsltproc
> and the DocBook XSL stylesheets likely to be installed on a
> run-of-the-mill computer these days?
No. These were parts of the default Linux desktop install about 7+ years
ago :-)
>
>> Libdbi-drivers has the same problem with openjade. I compiled it with
>> sqlite3 (my primary interest because of syslog-ng) and mysql5.5 (my
>> primary db platform). Compilation/installation went fine, but running
>> "make check" failed. Should I send the output of "make check" here (it's
>> quite long...), or only privately?
>>
>
> Below is the cause of the failure. Joao, are you listening? This looks
> like a cgreen problem to me. Is it necessary to install cgreen
> separately in order to make this work? Could you please look into this?
>
> --8<---
> FATAL ERROR: Could not find ./bin/my_print_defaults
>
> If you compiled from source, you need to run 'make install' to
> copy the software into the correct location ready for operation.
>
> If you are using a binary release, you must either be at the top
> level of the extracted archive, or pass the --basedir option
> pointing to that location.
> --8<---
Problem solved:
fb81clean# diff test_mysql.sh.old test_mysql.sh
40c40
< mysql_install_db --no-defaults --datadir=${ABSMYTMPDIR} --force
--skip-name-resolve --user=${ME}
---
> mysql_install_db --basedir=/usr/local/ --no-defaults
--datadir=${ABSMYTMPDIR} --force --skip-name-resolve --user=${ME}
Maybe some logic could be added to set "--basedir=" once
"mysql_install_db" is found.
> The sqlite3-specific output of the test looks fine to me.
And with the above fix the mysql tests also run successfully.
==================
All 2 tests passed
==================
>
>> it compiled OK. And I'll also check it on Linux (openSUSE 11.4 RC1)
>>
>
> Much appreciated as I don't have a SuSE system around here.
SuSE is my main desktop system, and I tend to use FreeBSD on servers.
And I was just asked to do some tests on Debian 6.0...
My first syslog-ng tests succeeded, sqlite3 and mysql 5.5 seem to work
OK. I'll do more tests tomorrow and add postresql to the pool, as my
colleagues reported some more problems internally which I want to verify
both with the 0.8.3 release and with the CVS version.
Bye,
--
Peter Czanik (CzP) <cz...@ba...>
BalaBit IT Security / syslog-ng upstream
http://czanik.blogs.balabit.com/
|
|
From: Markus H. <mar...@mh...> - 2011-02-16 15:23:43
|
Peter Czanik <cz...@ba...> was heard to say: >> SGML is darn old-fashioned, but I hesitate to convert the docs to XML. >> You'd require Java and FOP to build PDFs then, besides XSL stylesheets >> and xsltproc. We could as well drop PDFs altogether and build only >> HTML docs with xsltproc. I'm open to suggestions here. Are xsltproc >> and the DocBook XSL stylesheets likely to be installed on a >> run-of-the-mill computer these days? > No. These were parts of the default Linux desktop install about 7+ years > ago :-) > Are we both talking about XML/XSL here? I readily believe no one installs openjade by default these days, but I'd expect to have xsltproc around at least. I figured XML is ubiquitous these days. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 |
|
From: Matthew H. <mh...@mh...> - 2011-02-16 21:45:50
|
On Wed, Feb 16, 2011 at 01:27:28PM +0100, Peter Czanik wrote: > Libdbi: it only compiles if was configured with --disable-docs. Without > this option, if openjade is missing, it fails because of that, if it's > there, it still fails, because openjade does not like the document. > > Libdbi-drivers has the same problem with openjade. I compiled it with > sqlite3 (my primary interest because of syslog-ng) and mysql5.5 (my > primary db platform). Compilation/installation went fine, but running > "make check" failed. Should I send the output of "make check" here (it's > quite long...), or only privately? Peter, I ran into this openjade issue also. But I did not try make check. You probably need the BSD equivalent of docbook-dsssl: http://packages.debian.org/sid/docbook-dsssl Matthew. |
|
From: <mar...@mh...> - 2011-02-19 12:11:13
|
Matthew Hall writes: > I ran into this openjade issue also. > > But I did not try make check. > > You probably need the BSD equivalent of docbook-dsssl: > > http://packages.debian.org/sid/docbook-dsssl > I've checked things again on my developer box (FreeBSD 8.1). In order to transform the docs appropriately, you'll need: - jade or openjade - DocBook DSSSL stylesheets to create HTML or TeX output - TeX and JadeTeX to create PDF output from TeX Remember that if you build from a tarball, or use a prebuilt package for your favourite OS, you don't need any of these. As mentioned previously, we might as well switch the docs to Docbook XML. However, the requirements would change to: - xsltproc (the most lightweight XSL engine, but any other would do as well) - DocBook XSL stylesheets to create HTML or fo output - Java and Fop to create PDF output Feel free to suggest which requirements you think are easier to match. But remember that the stylesheets and any Java-based tools are notoriously hard to check for in configure scripts. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 |
Thanks for helping keep SourceForge clean.
X