refdb-devel — List for RefDB developers

Re: [Refdb-devel] instructions for Debian builds

[David N. <dav...@sw...>]

Hi Markus,

Markus Hoenicka wrote:

>one quick question: you mention in the installation instructions
>(install.html) that Debian users should configure the packages using
>./configure --prefix=/usr. Is this indeed the intended location for
>non-packaged software?
>

You are right.  Host-specific software should be installed in 
/usr/local.  I've amended the install page accordingly.  Thanks for the 
catch.

Regards,
David.

[Refdb-devel] instructions for Debian builds

[Markus H. <mar...@mh...>]

Hi David,

one quick question: you mention in the installation instructions
(install.html) that Debian users should configure the packages using
./configure --prefix=/usr. Is this indeed the intended location for
non-packaged software? I'm only a part-time Debian user, but I was
under the impression that /usr holds the packaged stuff, whereas
/usr/local holds your own builds. Is there an official Debian policy
in place for this issue?

regards,
Markus

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [Refdb-devel] website problems

[David N. <dav...@sw...>]

Hi Markus,

>Hi David,
>
>I've rearranged the site quite a bit. I've checked in my suggestion of
>the new structure. Feel free to fix whatever you think I broke.
>


You've broken _all_ the work I did.  I'd added an entire new application 
to the add-ons page ('vim-docbook-xml-refdb').  The old vimhelper app 
was renamed 'vim-ris'.

There were new images and I also renamed the vimhelper (now 'vim-ris') 
image files, which is why the image link on the current page is broken.

I created a new page (install.html) which had the Debian instructions.  
I re-wrote the Debian section in the downloads page.  All of this has 
disappeared.

As project leader you can, of course, feel free to ignore any or all of 
my efforts.  If you do want to revisit any of my work you can find it in 
the cvs repository.

At the very least, please correct the addons page to change vimhelper to 
vim-ris (with the corresponding updated text and image file names) and 
add the 'vim-docbk-xml-refdb' section.

Regards,
David.

Re: [Refdb-devel] website problems

[Markus H. <mar...@mh...>]

Hi David,

I've rearranged the site quite a bit. I've checked in my suggestion of
the new structure. Feel free to fix whatever you think I broke.

There'll be some more work on the weekend. I'd like to improve the
cross-linking between the pages. I'll also ponder what to do with the
add-ons page. Currently it contains the makestyle script and the Perl
client module which are not too closely related to each other. Also,
I've started moving the screenshots to a /screenshots subdirectory. I
guess I missed some of the links, so I'll have to fix them too.

Let me know what you think.

regards,
Markus

David Nebauer writes:
 > I've just uploaded my first take on extracting the install instructions 
 > to their own page.  The changes are in your queue.
 > 

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-devel] titles in place of missing authors

[Markus H. <mar...@mh...>]

Hi,

FYI: the current cvs version appears to do the right thing now for
both DocBook DSSSL and XSL. TEI is still work in progress.

regards,
Markus

Markus Hoenicka writes:
 > Hi,
 > 
 > I've started to implement support for having titles in citations and
 > bibliographies instead of missing authors. The current cvs version
 > should get it right except that the resulting title may be incorrectly
 > rendered in terms of font weight or posture. The XSL stylesheets do
 > not have any special support for this yet, and the DSSSL
 > implementation may still be incorrect.
 > 

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-devel] titles in place of missing authors

[Markus H. <mar...@mh...>]

Hi,

I've started to implement support for having titles in citations and
bibliographies instead of missing authors. The current cvs version
should get it right except that the resulting title may be incorrectly
rendered in terms of font weight or posture. The XSL stylesheets do
not have any special support for this yet, and the DSSSL
implementation may still be incorrect.

If you have some time on your hands, please test this feature to get
the formatting right and to detect the pathologic bordercases (like
missing authors in a subsequent multiple citation and so on). In order
to activate this feature, please change one of your bibliography
styles to carry an *empty* <AEMPTY> element. The logic is:

- missing <AEMPTY>: nothing will be printed in place of missing
  authors
- empty <AEMPTY>: the title will be printed instead
- <AEMPTY> containing a string: the string will be printed instead of
  the missing authors.

regards,
Markus

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [Refdb-devel] website problems

[David N. <dav...@sw...>]

Hi Markus,

Markus Hoenicka wrote:

>please go ahead. I wouldn't be too surprised if we had to go through
>several iterations.
>
>David Nebauer writes:
> > I guess what I'm proposing is a separation between download instructions 
> > and install instructions, with debian instructions going into the 
> > install page.
> > 
> > What do you think?  If I'm not totally off base here, I'd be happy to 
> > design the relevant pages.
>

I've just uploaded my first take on extracting the install instructions 
to their own page.  The changes are in your queue.

Regards,
David.

Re: [Refdb-devel] Unable to access sqlite db

[Markus H. <mar...@mh...>]

Hi David,

David Nebauer <dav...@sw...> was heard to say:

> Here is proof that there is nothing wrong with database 'experimental':
>
>
---------------------------------------------------------------------------------------------
> # pwd
> /var/lib/refdb/db
> # sqlite experimental
> SQLite version 2.8.16
> Enter ".help" for instructions
> sqlite> SELECT meta_app,meta_type,meta_dbversion from t_meta;
> refdb|risx|1

Here is the proof that there *is* something wrong :^)

I've added support for multiple UR and L1-L4 fields per dataset. This required a
change in the reference database schema which is not backwards-compatible. See
these entries in refdbd.h:

#define DB_VERSION 2 /* version tag of reference databases created with this
version */
#define MIN_DB_VERSION 2 /* minimum version tag of reference databases readable
*/

Your old databases are version 1, the current CVS version requires version 2.
You'll simply have to re-create your databases using your current RefDB
version. Sorry about the inconvenience.

regards,
Markus

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-devel] Unable to access sqlite db

[David N. <dav...@sw...>]

Hi Markus,

I'm apparently not out of the woods yet with the new debian packages.  
I'm unable to access _any_ of my previously accessible sqlite dbs.  I'm 
running refdb-cvs and the newest libdbi and libdbi drivers (pgsql, mysql 
and sqlite -- sqlite3 is not installed).

Here is the user experience:

---------------------------------------------------------------------------------------------
$ refdbc
not a RefDB database
refdbc: listdb
999:0
refdbc: selectdb experimental
not a RefDB database
refdbc: quit
$
---------------------------------------------------------------------------------------------

Here is what's occurring behind the scenes when attempting to listdb:

---------------------------------------------------------------------------------------------
root@hezmana: /home/david/tmp# refdbd -s -e 0 -l 7
dbi_driver_dir went to:

dbi is up using default driver dir
Available libdbi database drivers:
sqlite
mysql
pgsql
Requested libdbi driver found
Database directory:
/var/lib/refdb/db
application server started
share extended notes by default
use /tmp/refdbd_fifo18594 as fifo
server waiting n_max_fd=4

<!-- start 'refdbc' -->

adding client 127.0.0.1 on fd 5
server waiting n_max_fd=5
try to read from client
serving client on fd 5 with protocol version 4
012-21-75-51
send pseudo-random string to client
parent removing client on fd 5
server waiting n_max_fd=4
selectdb experimental -u david -w 083066087051103076052079126
dbi is up
localhost
david
daviduser


sqlite
/var/lib/refdb/db

refdb
connected to database server using database:
refdb
updated version file:
/var/lib/refdb/db/DB_VERSION
Main database looks ok:
refdb
localhost
david
daviduser


sqlite
/var/lib/refdb/db

refdb
connected to database server using database:
refdb

localhost
david
daviduser


sqlite
/var/lib/refdb/db

experimental
connected to database server using database:
experimental
SELECT meta_app,meta_type,meta_dbversion from t_meta
not a RefDB database
child exited with code 0
server waiting n_max_fd=4

<!-- execute 'listdb' command -->

adding client 127.0.0.1 on fd 5
server waiting n_max_fd=5
try to read from client
serving client on fd 5 with protocol version 4
102-32-57-03
send pseudo-random string to client
parent removing client on fd 5
server waiting n_max_fd=4
listdb  -u david -w 125043087036059035034120070
dbi is up
localhost
david
daviduser


sqlite
/var/lib/refdb/db

refdb
connected to database server using database:
refdb
updated version file:
/var/lib/refdb/db/DB_VERSION
Main database looks ok:
refdb
localhost
david
daviduser


sqlite
/var/lib/refdb/db

refdb
connected to database server using database:
refdb

localhost
david
daviduser


sqlite
/var/lib/refdb/db

refdb
connected to database server using database:
refdb
SELECT meta_app,meta_type,meta_dbversion from t_meta
localhost
david
daviduser


sqlite
/var/lib/refdb/db

refs_computing
connected to database server using database:
refs_computing
SELECT meta_app,meta_type,meta_dbversion from t_meta
localhost
david
daviduser


sqlite
/var/lib/refdb/db

experimental
connected to database server using database:
experimental
SELECT meta_app,meta_type,meta_dbversion from t_meta
localhost
david
daviduser


sqlite
/var/lib/refdb/db

Testcase
connected to database server using database:
Testcase
SELECT meta_app,meta_type,meta_dbversion from t_meta
An invalid or out-of-range index was passed to libdbi
command processing done, finish dialog now
child finished client on fd 5
child exited with code 0
server waiting n_max_fd=4
server exited gracefully
---------------------------------------------------------------------------------------------

Here is proof that there is nothing wrong with database 'experimental':

---------------------------------------------------------------------------------------------
# pwd
/var/lib/refdb/db
# sqlite experimental
SQLite version 2.8.16
Enter ".help" for instructions
sqlite> SELECT meta_app,meta_type,meta_dbversion from t_meta;
refdb|risx|1
sqlite> .quit
#

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

I've no idea where to go from here in troubleshooting.  Any suggestions 
gratefully appreciated.

Regards,
David.

Re: [Refdb-devel] website problems

[Markus H. <mar...@mh...>]

Hi David,

please go ahead. I wouldn't be too surprised if we had to go through
several iterations of content shuffling and menu rearrangements, but
it is important to get started.

regards,
Markus

David Nebauer writes:
 > I guess what I'm proposing is a separation between download instructions 
 > and install instructions, with debian instructions going into the 
 > install page.
 > 
 > What do you think?  If I'm not totally off base here, I'd be happy to 
 > design the relevant pages.
 > 

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [Refdb-devel] website problems

[David N. <dav...@sw...>]

David Nebauer wrote:

> I've changed that setting to iso-9959-1, re-saved the files and 
> committed them.


Keyboard dyslexia here.  That should read 'iso-8859-1'.

Regards,
David.

Re: [Refdb-devel] website problems

[David N. <dav...@sw...>]

Hi Markus,

Markus Hoenicka wrote:

>2) I don't quite see how the addons-debian.html page should be
>   officially linked to. I think it is confusing if users end up there
>   by following an obscure .deb link, but can't figure out a way to
>   find back to that page from the main page. I'm open to suggestions
>   how to handle this. I've mentioned previously that I want to extend
>   the section about refdb-mode once it works with an official RefDB
>   release. This might require a second-level menu containing entries
>   like PHP web interface, Emacs helpers, vim helpers, Perl stuff and
>   so on.
>

Frankly, I'm not happy with it either.  It's a site design problem I 
haven't resolved to my satisfaction.  The issue is that there are 
specific instructions that must be given to debian users as to how they 
make the repositories (refdb [cvs], refdb [release] and addons) 
available to debian's package management system -- essentially this 
boils down to adding an appropriate line to '/etc/apt/source.list'.  
What I don't want, however, is for debian management issues to take up 
any sizeable amount of the addons page since the majority of users will 
not be debian users.

There is also some information regarding the source files -- mainly 
about dependencies and how users should examine the output of 
'./configure --help' when building from source (untar + read 
README|INSTALL + ./configure + make + make install).

Upon reflection, what I'd like is a page devoted to the various modes of 
package installation.  There would be a section for installing from 
source (autotools-style foo.tar.gz files) and one for installing debs.  
The section on installing debs would not have all the crap that's 
currently in 'addons-debian.html'.  It should be trimmed down to the 
bare minimum and assume the reader is knowledgeable about debian package 
management.  For new/inexperienced debianites there would be a link to a 
relevant (external) debian package management tutorial.

Since one of my packages (vim-docbk-xml-refdb) has significant external 
dependencies (e.g., fop, xmllint, xpdf, etc.) that are only available 
from outside the refdb site there could also be a section on external 
dependencies.

Such a page would be a central site for information on installing refdb 
and refdb-related software.  If you do later split the addons page into 
a multi-tiered structure, each page could link to the install 
instructions page.  It could also be included on the site map.  If any 
refdb software is later made available via another installation method 
(rpm, slackware archives, etc.) then you have a single page to update 
with install instructions.

I guess what I'm proposing is a separation between download instructions 
and install instructions, with debian instructions going into the 
install page.

What do you think?  If I'm not totally off base here, I'd be happy to 
design the relevant pages.

Regards,
David.

Re: [Refdb-devel] website problems

[Markus H. <mar...@mh...>]

David Nebauer <dav...@sw...> was heard to say:

> This is what happens when you use a tool without fully understanding
> it.  This was the first time I used anything other than vim to edit
> html.  Turns out quanta defaults to saving as utf-8.  I've changed that
> setting to iso-9959-1, re-saved the files and committed them.  Let me
> know if that solves the problem.
>

:-) never stray far from your tried-and-true editor!

> As for switching to utf-8, I don't see any reason.  Where it makes no
> difference I think you should aim for the lowest common denominator.
> There are probably some holdout apps yet to fully support utf-8.
>

This also occurred to me after sending my reply. Lynx is probably the only
browser with quite a user base which might have problems, because it requires
your terminal and your fonts to be set up to use UTF-8. This is rarely the case
by default. I firmly believe that web pages should be accessible by Lynx, so
let's stick with ISO-8859-1.

regards,
Markus


-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [Refdb-devel] website problems

[David N. <dav...@sw...>]

Hi Markus,

Markus Hoenicka wrote:

>1) addons.html (and maybe the other files too) uses some UTF-8 characters,
>   but the header claims the file is ISO-8859-1. This causes display
>   problems in browsers that honor the encoding in the header.
>

This is what happens when you use a tool without fully understanding 
it.  This was the first time I used anything other than vim to edit 
html.  Turns out quanta defaults to saving as utf-8.  I've changed that 
setting to iso-9959-1, re-saved the files and committed them.  Let me 
know if that solves the problem.

As for switching to utf-8, I don't see any reason.  Where it makes no 
difference I think you should aim for the lowest common denominator.  
There are probably some holdout apps yet to fully support utf-8.

Regards,
David.

[Refdb-devel] website problems

[Markus H. <mar...@mh...>]

Hi David,

I've noticed two problems with your latest web page checkins:

1) addons.html (and maybe the other files too) uses some UTF-8 characters,
   but the header claims the file is ISO-8859-1. This causes display
   problems in browsers that honor the encoding in the header. I don't
   see a problem switching the affected or all pages to UTF-8.

2) I don't quite see how the addons-debian.html page should be
   officially linked to. I think it is confusing if users end up there
   by following an obscure .deb link, but can't figure out a way to
   find back to that page from the main page. I'm open to suggestions
   how to handle this. I've mentioned previously that I want to extend
   the section about refdb-mode once it works with an official RefDB
   release. This might require a second-level menu containing entries
   like PHP web interface, Emacs helpers, vim helpers, Perl stuff and
   so on.

regards,
Markus

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [Refdb-devel] PHP files executable

[David N. <dav...@sw...>]

Hi Markus,

Markus Hoenicka wrote:

>thanks for trying out. Please attribute this to my lack of understanding how all
>this php stuff works. I'm glad that it does work after fiddling with numerous
>Apache and PHP settings and with the scripts themselves.
>

I followed your adventures in php-land on the list (that portion of it 
that was copied to the list anyway).  If this is the only mistake you 
made then you've done well indeed.

Regards,
David.

Re: [Refdb-devel] PHP files executable

[Markus H. <mar...@mh...>]

Hi David,

thanks for trying out. Please attribute this to my lack of understanding how all
this php stuff works. I'm glad that it does work after fiddling with numerous
Apache and PHP settings and with the scripts themselves. Looks like I've
changed an unnecessary parameter too. I'll remove the line in Makefile.am which
makes the PHP files executable tonight.

regards,
Markus

David Nebauer <dav...@sw...> was heard to say:

> I experimented with the 'refdbadd.html' file in
> '/usr/share/refdb/www/'.  The "Change database" option executes the
> script 'refdbdquery.php'.  It executed correctly in firefox whether the
> php file was set executable or not.
>
> My conclusion is that PHP scripts do not need to be set executable
> (though clearly CGI perl scripts do).
>


-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [Refdb-devel] PHP files executable

[David N. <dav...@sw...>]

Hi Markus,

Markus Hoenicka wrote:

>I'm not sure as I'm not an Apache expert. I simply followed the
>instructions on the Apache web page how to get PHP scripts executed by
>Apache. The instructions suggest to make the scripts executable.
>
>See e.g. here:
>
>http://httpd.apache.org/docs/1.3/howto/cgi.html
>
>"Remember that the server does not run as you. That is, when the server
>starts up, it is running with the permissions of an unprivileged user
>- usually ``nobody'', or ``www'' - and so it will need extra
>permissions to execute files that are owned by you. Usually, the way
>to give a file sufficient permissions to be executed by ``nobody'' is
>to give everyone execute permission on the file:
>
>        chmod a+x first.pl"
>

I can't claim to be an expert either.  I'm sure the instructions are 
correct as far as they apply to CGI perl scripts.

PHP scripts, on the other hand, appear to be handled differently.  Here 
is a beginner's tutorial on PHP scripting 
<http://php.planetmirror.com/manual/en/tutorial.firstpage.php> which 
says, in part:

"Create a file named hello.php and put it in your web server's root 
directory (DOCUMENT_ROOT) with the following content:
[...]
Use your browser to access the file with your web server's URL, ending 
with the "/hello.php" file reference.
[...]
Note that the file /does not need to be executable/ or special in any 
way. The server finds out that this file needs to be interpreted by PHP 
because you used the ".php" extension, which the server is configured to 
pass on to PHP. Think of this as a normal HTML file which happens to 
have a set of special tags available to you that do a lot of interesting 
things."

Note in the last paragraph the PHP script does not have to be set 
executable.

I experimented with the 'refdbadd.html' file in 
'/usr/share/refdb/www/'.  The "Change database" option executes the 
script 'refdbdquery.php'.  It executed correctly in firefox whether the 
php file was set executable or not.

My conclusion is that PHP scripts do not need to be set executable 
(though clearly CGI perl scripts do).

Regards,
David.

[Refdb-devel] PHP files executable

[Markus H. <mar...@mh...>]

Hi David,

I'm not sure as I'm not an Apache expert. I simply followed the
instructions on the Apache web page how to get PHP scripts executed by
Apache. The instructions suggest to make the scripts executable.

See e.g. here:

http://httpd.apache.org/docs/1.3/howto/cgi.html

"Remember that the server does not run as you. That is, when the server
starts up, it is running with the permissions of an unprivileged user
- usually ``nobody'', or ``www'' - and so it will need extra
permissions to execute files that are owned by you. Usually, the way
to give a file sufficient permissions to be executed by ``nobody'' is
to give everyone execute permission on the file:

        chmod a+x first.pl"

regards,
Markus

David Nebauer writes:
 > Hi Markus,
 > 
 > The PHP files in '/usr/share/refdb/www/' are all set executable.
 > 
 > Is this necessary?  It appears to violate Debian policy -- here is the 
 > output from lintian:
 > 

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-devel] PHP files executable

[David N. <dav...@sw...>]

Hi Markus,

The PHP files in '/usr/share/refdb/www/' are all set executable.

Is this necessary?  It appears to violate Debian policy -- here is the 
output from lintian:

-------------------------------------------------------------------------------------
W: refdb: executable-not-elf-or-script ./usr/share/refdb/www/refdbadd.php
N:
N:   This executable file is not an ELF format binary, and does not start
N:   with the #! sequence that marks interpreted scripts. It might be a sh
N:   script that fails to name /bin/sh as its shell.
N:
N:   Refer to Policy Manual, section 10.4 for details.
N:
W: refdb: executable-not-elf-or-script ./usr/share/refdb/www/admin.php
W: refdb: executable-not-elf-or-script 
./usr/share/refdb/www/refdbdbquery.php
W: refdb: executable-not-elf-or-script ./usr/share/refdb/www/refdbadmin.php
W: refdb: executable-not-elf-or-script 
./usr/share/refdb/www/refdbkajsearch.php
W: refdb: executable-not-elf-or-script 
./usr/share/refdb/www/refdb-prl-del.php
W: refdb: executable-not-elf-or-script ./usr/share/refdb/www/include.php
W: refdb: executable-not-elf-or-script ./usr/share/refdb/www/login.php
W: refdb: executable-not-elf-or-script ./usr/share/refdb/www/refdbsearch.php
W: refdb: executable-not-elf-or-script ./usr/share/refdb/www/refdblogout.php
-------------------------------------------------------------------------------------

Regards,
David.

Re: [Refdb-devel] CVS build failure - refdbd

[David N. <dav...@sw...>]

Hi Markus,

>the fix is as easy as "cvs update" :-) I simply forgot to add
>refdb.css to cvs.
>  
>
Woo hoo!  After a long interval, refdb cvs builds!

Regards,
David.

Re: [Refdb-devel] CVS build failure - refdbd

[Markus H. <mar...@mh...>]

Hi David,

the fix is as easy as "cvs update" :-) I simply forgot to add
refdb.css to cvs. While being at it, I've also added INSTALL to the
distributed files in Makefile.am, so the file will actually reach the
end user.

regards,
Markus


David Nebauer writes:
 > The cvs build still fails, but it is a very pedestrian error caused by a 
 > missing file in the new phpweb stuff.  Here is the relevant portion of 
 > the build:

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-devel] libdbi debs

[Markus H. <mar...@mh...>]

Ok, drop me a line when you're done.

Markus

David Nebauer writes:
 > Hi Markus,
 > 
 > Don't post the libdbi0[-dev] debs to the libdbi site yet.  While they 
 > are usable there are a few cosmetic changes I've yet to make.
 > 
 > Regards,
 > David.
 > 
 > 


-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-devel] libdbi debs

[David N. <dav...@sw...>]

Hi Markus,

Don't post the libdbi0[-dev] debs to the libdbi site yet.  While they 
are usable there are a few cosmetic changes I've yet to make.

Regards,
David.

Re: [Refdb-devel] CVS build failure - refdbd

[David N. <dav...@sw...>]

Hi Markus,

> I've still got that pesky build failure for refdb cvs.  It's occurring 
> despite using libdbi 0.8.0 -- specifically, the debs I emailed you a 
> little while ago.

Hold the phone!  The build problem was solved by moving the dbi include 
files from '/usr/include/' to '/usr/include/dbi/'.

The cvs build still fails, but it is a very pedestrian error caused by a 
missing file in the new phpweb stuff.  Here is the relevant portion of 
the build:
-----------------------------------------------------------------------------------------------------
Making install in phpweb
make[2]: Entering directory 
`/home/david/data/computing/projects/refdb/packages/refdb/cvs/pkg/debianise/source/refdb-0.0-cvs-20050924/phpweb'
make[3]: Entering directory 
`/home/david/data/computing/projects/refdb/packages/refdb/cvs/pkg/debianise/source/refdb-0.0-cvs-20050924/phpweb'
make[3]: Nothing to be done for `install-exec-am'.
/bin/sh .././conf/mkinstalldirs 
/home/david/data/computing/projects/refdb/packages/refdb/cvs/pkg/debianise/source/refdb-0.0-cvs-20050924/debian/refdb/usr/share/refdb/www
mkdir -p -- 
/home/david/data/computing/projects/refdb/packages/refdb/cvs/pkg/debianise/source/refdb-0.0-cvs-20050924/debian/refdb/usr/share/refdb/www
chmod 1777 
/home/david/data/computing/projects/refdb/packages/refdb/cvs/pkg/debianise/source/refdb-0.0-cvs-20050924/debian/refdb/usr/share/refdb/www
chmod 755 
/home/david/data/computing/projects/refdb/packages/refdb/cvs/pkg/debianise/source/refdb-0.0-cvs-20050924/debian/refdb/usr/share/refdb/www/*.php
/bin/sh .././conf/mkinstalldirs 
/home/david/data/computing/projects/refdb/packages/refdb/cvs/pkg/debianise/source/refdb-0.0-cvs-20050924/debian/refdb/usr/share/refdb/css
mkdir -p -- 
/home/david/data/computing/projects/refdb/packages/refdb/cvs/pkg/debianise/source/refdb-0.0-cvs-20050924/debian/refdb/usr/share/refdb/css
/usr/bin/install: cannot stat `refdb.css': No such file or directory
make[3]: *** [install-data-local] Error 1
make[3]: Leaving directory 
`/home/david/data/computing/projects/refdb/packages/refdb/cvs/pkg/debianise/source/refdb-0.0-cvs-20050924/phpweb'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory 
`/home/david/data/computing/projects/refdb/packages/refdb/cvs/pkg/debianise/source/refdb-0.0-cvs-20050924/phpweb'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory 
`/home/david/data/computing/projects/refdb/packages/refdb/cvs/pkg/debianise/source/refdb-0.0-cvs-20050924'
make: *** [install] Error 2
-----------------------------------------------------------------------------------------------------

Hope this is an easy fix.

Regards,
David.