lifelines-dev — Lifelines developers mailing list

[Lifelines-dev] lifelines questions

[David T. <dct...@gm...>]

Increasingly I am thinking that this list is a black hole.  I don't see my
message and I don't get a bounce back...  But, I'll try again...

Beyond the libraries, what are the subsystems?  Are there any defined API's?

What is CACHEEL?  Suggestions on things to be careful about or to avoid?
Subtle gotchas that come to mind?

I'm sure lots more questions will arise and I get deeper into the code.

Here's hoping that this message isn't going into a black hole.

David

[Lifelines-dev] (no subject)

[David T. <dct...@gm...>]

Is there any lifelines internals documentation?

I'm looking for internals documentation, not documentation on how to write
reports.

David

[Lifelines-dev] location of master lifelines reposiitory

[David T. <dct...@gm...>]

At lifelines.sourceforge.net, it says that the repository is CVS! Trying to
access it it, not
surprisingly, fails.

Doing a search at sourceforge, it mentions a git repository -- which is
empty.  But, there are
a number of releases available for download -- the latest is 3.0.62 and
there have been over
a dozen downloads of it this past week.

There also exists a git repository at github, which is non-empty and the
latest release for download
appears to be 3.1.1.

So, some questions --

. is this list still alive?  Is this the right place for developer
questions?  Or have the discussions
migrated elsewhere?

. is the repository at github the latest?  Or ...?

. is lifelines still being developed?  Or has it been abandoned?

Thanks.

David

[Lifelines-dev] [DEBIAN] Wrong content in docs/*.txt

[Felipe A. v. de W. (faw) <fa...@de...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello!

	I hope everybody is OK and fine. :-)

	While preparing a new Debian package of lifelines 3.0.62 I
spotted something strange in docs/*.txt, more specifically:

		docs/ll-reportmanual.txt
		docs/ll-userguide.txt


	The CVS seems to have the "correct files" but the tarballs,
both the .tar.gz and .tar.bz2 seems to have a strange "SPAM" instead
of the documentation. I also verified the md5sum and it is OK, so is
this expected?

	I did a full diff between 3.0.61.1 and 3.0.62 and it seems
that everything else is fine, the diff is quite big because of
comments inside PO files, but I'm unsure if I should just replace
the affected files, so I decided that would be great if you could
comment on this. Thanks in advance.

Kind regards,
- --
Felipe Augusto van de Wiel (faw)
"Debian. Freedom to code. Code to freedom!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiMJBYACgkQCjAO0JDlykaDZQCgvtywwy3V/ad87BMmlzFGqHt1
es4AoKhlbaSvBXawfeO8fTi1Hbshk1v9
=4PA0
-----END PGP SIGNATURE-----

[Lifelines-dev] Problems with lifelines-3.0.62-1 upgrade

[Michael <mi...@ve...>]

Greetings all. New to this list, but not to LifeLines. I've been using
it since 2005.

I just upgraded to 3.0.62-1 via the RPM (on an FC-6 system) and now
LifeLines isn't picking up the environment variables, either those set
on the system or using the -I switch.

For example: LLEDITOR is set (I can echo $LLEDITOR and get a returned
value) but LifeLines doesn't use it. Same with LLDATABASES and so on and
so forth. Nor will it pick them up if I use the documented example:
"-ILLEDITOR=foo". 

Has anybody else had this trouble with the RPM version of x.62-1? I went
looking for another RPM, but it looks like all have been distributed
from the original on SourceForge, which is where I got mine.

Thanks!


-- 
    -=Michael=-
-{Key ID:1893C6F1}-
  mi...@ve...

Re: [Lifelines-dev] lifelines release 3.0.61-2

[Felipe A. v. de W. (faw) <fe...@ca...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10-08-2007 11:39, amores perros wrote:
> LifeLines Source Release, Version 3.0.61
> http://lifelines.sourceforge.net
> -----------------------------------------------------
> 
> Changes in 3.0.61-2
>   Improved German translation
> 
> Changes in 3.0.61 (stable)
> ===========================
> - Improvements to configure finding curses
> - More strings made ready for internationalization
> 
> Changes in 3.0.60 (stable)
> ===========================
> - Minor doc tweaks, and packaging tweaks for Debian

Hey everybody,

	Just to let you know, I uploaded a new version
o lifelines to Debian "unstable" (aka sid), it already
hit the main archive and should hit the mirrors soon.

	It is the 3.0.61-2 (you will see 3.0.61-1, because
- -1 is the Debian revision), I have a small suggestion:

 * ll-index

	We added these files in docs/ and they are listed in
	Makefile.in, a make clean will remove then and they
	are not generated again, I'm locally patching it for
	the Debian package, but I think it is worth to let
	you know.


	We reduced a lot the number of differences between
the Debian package and lifelines upstream. Thanks for all
your help. :-)

	Kind regards,
- --
Felipe Augusto van de Wiel (faw)
"Debian. Freedom to code. Code to freedom!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGwjaaCjAO0JDlykYRAnRwAJ4wgbMDH1DLDh8pKBnpDEZ+w3OE3wCg0IVH
JDVd8s1oAzq95t1bBsT/OCE=
=Q4Nz
-----END PGP SIGNATURE-----

[Lifelines-dev] ncursesw/curses.h: No such file or directory

[Thomas R. <tr...@am...>]

I had this problem with LifeLines-3.0.59 and now with LifeLines-3.0.60 
-- no matter how I configure, the following occurs:

    if gcc -DSYS_CONF_DIR=\"/usr/local/etc\" -DHAVE_CONFIG_H -I. -I.
    -I../.. -I../.. -I../../intl -I../../intl -I../../src/hdrs    -g -O2
    -W -Wall -Wcast-align -Wmissing-declarations -Wmissing-prototypes
    -Wreturn-type -Wstrict-prototypes -pedantic -g -MT editvtab.o -MD
    -MP -MF ".deps/editvtab.Tpo" -c -o editvtab.o editvtab.c; \
            then mv -f ".deps/editvtab.Tpo" ".deps/editvtab.Po"; else rm
    -f ".deps/editvtab.Tpo"; exit 1; fi
    In file included from editvtab.c:33:
    ../../src/hdrs/mycurses.h:8:29: ncursesw/curses.h: No such file or
    directory
    make[3]: *** [editvtab.o] Error 1
    make[3]: Leaving directory `/usr/local/src/lifelines-3.0.60/src/gedlib'
    make[2]: *** [all-recursive] Error 1
    make[2]: Leaving directory `/usr/local/src/lifelines-3.0.60/src'
    make[1]: *** [all-recursive] Error 1
    make[1]: Leaving directory `/usr/local/src/lifelines-3.0.60'
    make: *** [all] Error 2

I am currently running LifeLines-3.0.46.1, built on this system, with no 
problems and I do have ncurses on the system (i.e., other applications 
-- including LifeLines-3.0.46.1 -- have had no problem finding it).

uname -a reports:

    Linux fubar 2.6.18 #1 Mon May 28 07:14:02 EDT 2007 i686 prescott
    i386 GNU/Linux

and gcc --version reports:

    gcc (GCC) 3.4.6

It's a Slackware 11.0 box with "everything" installed.

Any hints would be appreciated, thanks.

Re: [Lifelines-dev] index.html & new release

[amores p. <lif...@ho...>]

>From: dr.doom
>Subject: Re: [Lifelines-dev] index.html & new release Date: Sun, 03 Jun 
>2007 17:35:25 -0700

>In message <BAY...@ph...>you write:
> >
> >> >
> >> >I'll be happy to make another release - ok by you Steve?
> >
> >Except, I cannot configure & build the cvs right now.
> >
> >
> >https://sourceforge.net/tracker/index.php?func=detail&aid=1729979&group_id=852
> >&atid=100852
>
>Did you reconfigure your system?  It's saying it can't find jw.
>I know you just recently reformated the docs so only other thing I can
>imagine is that somehow your PATH got changed and now doesn't include path
>to jw.

Ha, no, I didn't change anything. I made an old redhat installation and did 
the
docs from there.

Anyway, that error did not appear when I redid the same test later,
so I guess it was something transitory, so I'm not planning to worry about
it.

_________________________________________________________________
Make every IM count. Download Messenger and join the i’m Initiative now. 
It’s free. http://im.live.com/messenger/im/home/?source=TAGHM_June07

Re: [Lifelines-dev] lifelines release & debian fixes

[Felipe A. v. de W. (faw) <fe...@ca...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/02/2007 11:52 PM, amores perros wrote:
> I was primarily for a new release for the purposes of the
> Debian fixes, so by all means, let us hold off until Felipe
> is ready to benefit from a new release :)

Hey! :-)

	I prepared preliminary packages of 3.0.59 and
everything seems to be OK, I could built twice in a row
using the '\ #' workaroung in XML, which mean that it is
generating the docs and after a distclean everything
works fine (I'm not generating the SV HTMLs).

	I just had one doubt, the ll-devguide.xml does
not generate a PDF only a HTML?  I'm also adding
ll-devguide.xml and ll-devguide.html to lifelines-doc
debian package.

	So, from my side, everything is ready, when you
roll a new version of lifelines I will check the diff
from 3.0.59, prepare the new packages and upload it to
sid (Debian unstable).

	Thanks again for all your attention and patience.

	Kind regards,

- --
Felipe Augusto van de Wiel (faw)
"Debian. Freedom to code. Code to freedom!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGY52uCjAO0JDlykYRAlVuAJ9ntt+o0XaRO7oBNFiv79G1MWObdACgrXcG
u7/zeWo4eJdnpmZSaz5vxIo=
=5oP1
-----END PGP SIGNATURE-----

Re: [Lifelines-dev] index.html & new release

[<dr...@ve...>]

In message <BAY...@ph...>you write:
>
>> >
>> >I'll be happy to make another release - ok by you Steve?
>
>Except, I cannot configure & build the cvs right now.
>
>  
>https://sourceforge.net/tracker/index.php?func=detail&aid=1729979&group_id=852
>&atid=100852

Did you reconfigure your system?  It's saying it can't find jw.
I know you just recently reformated the docs so only other thing I can
imagine is that somehow your PATH got changed and now doesn't include path 
to jw.  
>
>This is odd, as the only recent change I see in docs/Makefile.am
>is my own addition of one man page, and that doesn't look
>very suspicious.

Everything builds for me so I don't think it's the Makefile.am change
>
>But, I won't be building until I figure this out...

Well, I checked in files docs/ll-index.html and docs/ll-index.sv.html.
So I have no more changes planned.

steve
>
>_________________________________________________________________
>Don’t miss your chance to WIN $10,000 and other great prizes from Microsoft 
>Office Live http://clk.atdmt.com/MRT/go/aub0540003042mrt/direct/01/
>
>
>
>--Boundary_(ID_AznM78Znil2HJWBNLHMcWA)
>MIME-version: 1.0
>Content-type: text/plain; charset=us-ascii
>Content-transfer-encoding: 7BIT
>Content-disposition: inline
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by DB2 Express
>Download DB2 Express C - the FREE version of DB2 express and take
>control of your XML. No limits. Just data. Click to get it now.
>http://sourceforge.net/powerbar/db2/
>

Re: [Lifelines-dev] lifelines release & debian fixes

[amores p. <lif...@ho...>]

I was primarily for a new release for the purposes of the
Debian fixes, so by all means, let us hold off until Felipe
is ready to benefit from a new release :)

_________________________________________________________________
Don’t miss your chance to WIN $10,000 and other great prizes from Microsoft 
Office Live http://clk.atdmt.com/MRT/go/aub0540003042mrt/direct/01/

Re: [Lifelines-dev] Felipe's many bug reports

[Felipe A. v. de W. (faw) <fe...@ca...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/01/2007 11:13 PM, amores perros wrote:
> Felipe,
> 
> Thank you very much for pursuing these various
> matters so diligently. I hope you will be able
> to resolve at least some of the outstanding
> items on the debian lifelines issue list now.

	Thanks for all the support from lifelines-dev.
Maintaining lifelines package in Debian is a lot of fun
specially because upstream is very helpful. :-)

	I did some preliminary work on the 3.0.59, now
just the build-distclean-build and the docs test are
missing, I hope to have more information in time for the
next lifelines version.

	Kind regards,

- --
Felipe Augusto van de Wiel (faw)
"Debian. Freedom to code. Code to freedom!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGYflACjAO0JDlykYRApEWAKCLMTx7t3QSsCs59JCOj7mJBjAZLgCfS9ax
cxWHgVqkyyF4EyXJf/kXonI=
=jlmu
-----END PGP SIGNATURE-----

Re: [Lifelines-dev] index.html & new release

[Felipe A. v. de W. (faw) <fe...@ca...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/01/2007 04:24 PM, ste...@me... wrote:
> This reminds me of a patch Felipe included in an earlier mail creating
> ll-index.html and ll-index.sv.html in the docs directory.  

	Yes, this is #330483. This bug report was splited into three
small problems, the ll-index.html was the third one. We can only add
one reference to the doc database, so we changes to use a wildcard
"ll-*" and added an index page to point to these documents. (More
details in the bug itself).

 1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=330483


	I pretty much used the patch provided in the bug. :-)


> Felipe - A couple of questions:
>    I assume you wanted these two pages added to the lifelines distribuiton? 

	Yes, that would reduce the difference between lifelines upstream
and Debian, which means less patches to apply locally (only in Debian)
and hopefully it would help other users/distros.


>    Is there a reason to name them ll-index.html rather than just index.html?  

	No, probably the bug reporter just kept the pattern. Since
the file is inside the lifelines directories we could use just
index.html.


>    And finally, it seems like it would be reasonable for this file to also
>    point to the 'reports/index.html' file, as it is summary documentation 
>    for the reports.

	Of course. But, reports are optional in Debian, lifelines-reports
is another packages, so it is indexed by itself. The link would not work
unless the lifelines-reports is installed.


> Resolving this question, perhaps we should make a release and mark is as
> non-beta.

	I hope the above answers solve the questions. :-)   As I said in
another message, please, if it is possible, hold a little bit, so I can
check if everything goes well with 3.0.59.


	Kind regards,

- --
Felipe Augusto van de Wiel (faw)
"Debian. Freedom to code. Code to freedom!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGYdihCjAO0JDlykYRAv4oAJkBs00tHPGGGFycUBepaGd3bCuVfACgqqii
DgGQl1iiuhEELq1sJ9S4Q6Q=
=AY0E
-----END PGP SIGNATURE-----

Re: [Lifelines-dev] index.html & new release

[Felipe A. v. de W. (faw) <fe...@ca...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/01/2007 12:36 PM, amores perros wrote:
>> Are you planning another release? Or may I package 3.0.59?
> 
> I'll be happy to make another release - ok by you Steve?

	Ok, I'm not Steve. :-)  But...
	I would like to ask you to hold for a second. Let me
work with the 3.0.59 package (specially to check the XML docs),
perhaps we will need to patch ll-devguide.xml for Debian (and
the patch could be added upstream without break Fedora/RH).


> Elsewhere, I mentioned again the report index.html locale
> issue, and Felipe reponded with a comment about the doc pdf
> generation. I have no reason to believe these are related
> in any way at all -- have you Felipe?

	Sorry, I was totally unclear on my other message. I
don't recall any problems generating index.html (and I'm
using UTF-8 on the build area), what I tried to say is that
I didn't saw any relation with the index.html breakage you
mentioned with the already reported bug (or vice-versa).

	As I said, I have plans to prepare a test package for
lifelines 3.0.59 either today or tomorrow, so I can come back
of the last bits that I could recommend to get in before a new
release. It would be great if lifelines-dev can wait (I saw
steve message about the actual state of CVS).

	Kind regards,

- --
Felipe Augusto van de Wiel (faw)
"Debian. Freedom to code. Code to freedom!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGYdbFCjAO0JDlykYRAnvFAJ9JAL1v1layFiJh387YOkLZ/rlwKACgqRgt
COvGrzAtiR7KTA/lESA6sEE=
=nyBV
-----END PGP SIGNATURE-----

Re: [Lifelines-dev] index.html & new release

[amores p. <lif...@ho...>]

> >
> >I'll be happy to make another release - ok by you Steve?

Except, I cannot configure & build the cvs right now.

  
https://sourceforge.net/tracker/index.php?func=detail&aid=1729979&group_id=852&atid=100852

This is odd, as the only recent change I see in docs/Makefile.am
is my own addition of one man page, and that doesn't look
very suspicious.

But, I won't be building until I figure this out...

_________________________________________________________________
Don’t miss your chance to WIN $10,000 and other great prizes from Microsoft 
Office Live http://clk.atdmt.com/MRT/go/aub0540003042mrt/direct/01/

Re: [Lifelines-dev] Felipe's many bug reports

[amores p. <lif...@ho...>]

Felipe,

Thank you very much for pursuing these various
matters so diligently. I hope you will be able
to resolve at least some of the outstanding
items on the debian lifelines issue list now.

_________________________________________________________________
Don’t miss your chance to WIN $10,000 and other great prizes from Microsoft 
Office Live http://clk.atdmt.com/MRT/go/aub0540003042mrt/direct/01/

Re: [Lifelines-dev] index.html & new release

[<ste...@me...>]

In message <BAY...@ph...>you write:
>
>--Boundary_(ID_Lu3GYj86Di3HOEd5S3Kh2w)
>Content-type: text/plain; format=flowed
>Content-transfer-encoding: 8BIT
>
>>Are you planning another release? Or may I package 3.0.59?
>
>I'll be happy to make another release - ok by you Steve?
>
I have no objections but your following comment reminded me of an issue.
>
>Elsewhere, I mentioned again the report index.html locale
>issue, and Felipe reponded with a comment about the doc pdf
>generation. I have no reason to believe these are related
>in any way at all -- have you Felipe?

This reminds me of a patch Felipe included in an earlier mail creating
ll-index.html and ll-index.sv.html in the docs directory.  

Felipe - A couple of questions:
   I assume you wanted these two pages added to the lifelines distribuiton? 
   Is there a reason to name them ll-index.html rather than just index.html?  
   And finally, it seems like it would be reasonable for this file to also
   point to the 'reports/index.html' file, as it is summary documentation 
   for the reports.

Resolving this question, perhaps we should make a release and mark is as
non-beta.

steve
>
>_________________________________________________________________
>PC Magazine’s 2007 editors’ choice for best Web mail—award-winning Windows 
>Live Hotmail. 
>http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_
>HM_mini_pcmag_0507
>
>
>
>--Boundary_(ID_Lu3GYj86Di3HOEd5S3Kh2w)
>MIME-version: 1.0
>Content-type: text/plain; charset=us-ascii
>Content-transfer-encoding: 7BIT
>Content-disposition: inline
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by DB2 Express
>Download DB2 Express C - the FREE version of DB2 express and take
>control of your XML. No limits. Just data. Click to get it now.
>http://sourceforge.net/powerbar/db2/
>
>--Boundary_(ID_Lu3GYj86Di3HOEd5S3Kh2w)
>MIME-version: 1.0
>Content-type: text/plain; charset=us-ascii
>Content-transfer-encoding: 7BIT
>Content-disposition: inline
>
>_______________________________________________
>Lifelines-dev mailing list
>Lif...@li...
>https://lists.sourceforge.net/lists/listinfo/lifelines-dev
>
>--Boundary_(ID_Lu3GYj86Di3HOEd5S3Kh2w)--
>

Re: [Lifelines-dev] index.html & new release

[amores p. <lif...@ho...>]

>Are you planning another release? Or may I package 3.0.59?

I'll be happy to make another release - ok by you Steve?


Elsewhere, I mentioned again the report index.html locale
issue, and Felipe reponded with a comment about the doc pdf
generation. I have no reason to believe these are related
in any way at all -- have you Felipe?

_________________________________________________________________
PC Magazine’s 2007 editors’ choice for best Web mail—award-winning Windows 
Live Hotmail. 
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_pcmag_0507

Re: [Lifelines-dev] Debian package for lifelines 3.0.59 - built twice

[Felipe A. v. de W. (faw) <fe...@ca...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/31/2007 12:53 PM, ste...@me... wrote:
> In message <465...@ca...>you write:
>> BUG: #424543 (lifelines)
>> SUB: lifelines: FTBFS if built twice in a row
>> URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=424543
>
> I've started a new thread on this as the old one was getting so long I thought
> I would just summarize the situation (and this ends up long as well).
> 
> Not to mention I think the problem here is really
>
>> BUG: #418347 (lifelines-doc)
>> SUB: PDF documentation cannot be opened (broken PDF)
>> URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418347

	I agree. I think that with the doc bug solved, lifelines
probably will compile twice in a row smoothly.


[...]
> So there are two problems here:
> 1. On redhat - and this occurs on RHEL3, RHEL5 and FC6 basically everything
>    that is 'supported' - if a xml file has the text \# the characters are
>    not properly escaped when translating to TeX, which is an intermediate
>    format used to generate pdf's, so the pdf generation fails. 
>    I opened a bug with redhat - it's bug 241845 - we'll see what they say.

	Thanks. I used your example to report the bug in Debian. :-)


> 2. On debian, the string '\ #' causes jw to fail to generate the pdf -
>    Felipe indicated he would open a bug on that.

	Done. I did a small mistake reporting it against the wrong package
(openjade instead of docbook-utils) but I already asked for the
reassignment (and it already worked). #426967

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426967


> I believe there are no lifelines bugs on this.  Everything is working as
> designed - the html, pdf and txt documents only get generated if they are
> not uptodate or missing.  But there are underlying tool bugs with xml 
> conversion on both redhat and debian.

	Ok, that pretty much solves all our pending issues. I need
to check the ll-devguide.xml to see if it compiles ok, I will keep
the local debian patch for the '\ #' until we got an answer from
the docbook-utils maintainers.


	Are you planning another release? Or may I package 3.0.59?


> steve

	Thanks for all the help.
	Kind regards,

- --
Felipe Augusto van de Wiel (faw)
"Debian. Freedom to code. Code to freedom!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGX6Y9CjAO0JDlykYRAup+AKC9unWG7jhh+scH3G8KfqAeveTCjQCgyryO
unPRi06Ksyfq1pJfQiB1fvY=
=4cF1
-----END PGP SIGNATURE-----

Re: [Lifelines-dev] Debian package for lifelines 3.0.59

[Felipe A. v. de W. (faw) <fe...@ca...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/31/2007 10:30 AM, amores perros wrote:
[...]
> Note2: My locale is a default one with UTF-8, and the index.html
> generation breaks in a UTF-8 locale. To get that to work, I have to
> temporarily manually set my locale to a ISO-8859-1 locale.
> 
> Is there any chance this index.html/locale issue is a problem
> for the Debian build?

	No, I don't think so. It seems to be related to the
poundsign, you add/remove the space and the PDF generation
works/stops.


	Kind regards,

- --
Felipe Augusto van de Wiel (faw)
"Debian. Freedom to code. Code to freedom!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGX6DyCjAO0JDlykYRArvXAKCUTQ9uFHKFXDx/oHHhHbORydEpmgCfVi55
oYsE/Yb8GoJbVnxDTtiLAP0=
=cN+w
-----END PGP SIGNATURE-----

Re: [Lifelines-dev] Debian package for lifelines 3.0.59 - built twice

[<ste...@me...>]

In message <465...@ca...>you write:
>
>BUG: #424543 (lifelines)
>SUB: lifelines: FTBFS if built twice in a row
>URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=424543
>
I've started a new thread on this as the old one was getting so long I thought
I would just summarize the situation (and this ends up long as well).

Not to mention I think the problem here is really
> BUG: #418347 (lifelines-doc)
> SUB: PDF documentation cannot be opened (broken PDF)
> URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418347

I do not believe there a problem with lifelines makefiles or build process.
The normal cvs build process works fine,
> $ cvs -z3 up -d
> $ sh autogen.sh
> $ rm -rf bld
> $ mkdir bld
> $ cd bld
> $ ../configure
> $ make
because the html and pdf's are checked out of cvs and don't need to be
regenereated.  The problem in the 'built twice' debian bug is that
after the build it's followed with something like

$ distclean
$ make

This removes the pdf's - forcing the make to try to regenerate the pdf's.
And debian is having a problem regenerating the pdf - I'm guessing because
of the string '\ #' which is in the file - and that string is there because
on redhat the string '\#' causes a failure.

So there are two problems here:
1. On redhat - and this occurs on RHEL3, RHEL5 and FC6 basically everything
   that is 'supported' - if a xml file has the text \# the characters are
   not properly escaped when translating to TeX, which is an intermediate
   format used to generate pdf's, so the pdf generation fails. 
   I opened a bug with redhat - it's bug 241845 - we'll see what they say.

2. On debian, the string '\ #' causes jw to fail to generate the pdf -
   Felipe indicated he would open a bug on that.

I believe there are no lifelines bugs on this.  Everything is working as
designed - the html, pdf and txt documents only get generated if they are
not uptodate or missing.  But there are underlying tool bugs with xml 
conversion on both redhat and debian.

steve

Re: [Lifelines-dev] Debian package for lifelines 3.0.59

[amores p. <lif...@ho...>]

Following up on my last message,

$ make ll-userguide.html
make: `../../docs/ll-userguide.html' is up to date.


That explains why the userguides are not being generated for me,
I guess.

_________________________________________________________________
More photos, more messages, more storage—get 2GB with Windows Live Hotmail. 
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_2G_0507

Re: [Lifelines-dev] Debian package for lifelines 3.0.59

[amores p. <lif...@ho...>]

On a redhat test system,

When I do

$ cvs -z3 up -d
$ sh autogen.sh
$ rm -rf bld
$ mkdir bld
$ cd bld
$ ../configure
$ make


I only get these three files (plus Makefile) in my bld/docs dir

ll-devguide.html
ll-reportmanual.html
ll-reportmanual.pdf

(Note: this test system lacks lynx, so it did not build txt versions)


I can manually generate the ll-devguide.pdf via
$ make ll-devguide.pdf


But this suggests to me that there is something wrong with the
make rules?



(Note: I unsubscribed this email address from the dev list,
b/c I've made a new one and subscribed it, but then
I decided I should use this account to send email,
and I was going to resubscribe it, but sourceforge
seems hopelessly unresponsive again -- so I am
interested to see if this email is allowed through...)


Note2: My locale is a default one with UTF-8, and the index.html
generation breaks in a UTF-8 locale. To get that to work, I have to
temporarily manually set my locale to a ISO-8859-1 locale.

Is there any chance this index.html/locale issue is a problem
for the Debian build?

Note3: I trimmed the cc list, b/c I'm pretty sure both of you
are on the lifelines-dev list, and I suppose you don't need
multiple copies of this email.

_________________________________________________________________
PC Magazine’s 2007 editors’ choice for best Web mail—award-winning Windows 
Live Hotmail. 
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_pcmag_0507

Re: [Lifelines-dev] Debian package for lifelines 3.0.59

[Felipe A. v. de W. (faw) <fe...@ca...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/30/2007 02:30 PM, dr...@ve... wrote:
> In message <BAY...@ph...>you write:

[...]

>> It looks like you're an Admin on the bugs tracker, so I think either
>> of us could post an issue about this to the sourceforge lifelines
>> bug tracker. I think that sounds like an appropriate idea. Would you
>> care to post it?
>
> I can - but I want to figure this out first.
> I don't believe that this is a lifelines bug - per se.
> It sounds like the following is happening:
> 1. the debian build unpacks the 'sources' which include
>    docs/ll-userguide.pdf
> 2. the first build skips generation of ll-userguide.pdf because it is 
>    present.
> 3. if 'distclean' is used, the pdf is removed

	Yes, distclean is used.


> 4. the second build fails to generate the pdf
> 
> We could 'hack' around the failure by removing the pdf from the distclean
> target, but the correct behavior is for distclean to remove the pdf.
> So this isn't a distclean bug.

	Indeed. I agree that distclean should remove the pdf.


> This then goes back to the generation of the pdf.
> and those 4 lines of text in ll-userguide.mxl
>     <glossentry><glossterm>\ #</glossterm><glossdef>
>     <!-- note above has extra space between \ and # - without this 
>          conversion to pdf gets confused openjade does some tex processing...
>     -->
> If I am not mistaken, xml claims that \ and # are not special characters
> when used in this context.  So there should be nothing special about
> the sequence '\#' or '\ #'.

	Correct.


> I think there is a bug in the redhat distributed openjade pdf generation
> where '\#' doesn't get handed off the TeX properly and causes the TeX
> processing to fall on it's face, badly.  We avoided the problem by changing
> the string to '\ #' - now technically inserting the extra space is wrong,
> but visually it looks ok in the formatted manual.  

	That's my understanding of this issue.


> I'm thinking here, yes we have a minor problem in that we have inserted an
> extra space, which absolutely isn't required in the glossary term being
> formatted, but it 'looks ok'.  But it shouldn't cause the debian port to
> fail to generate the pdf document, because '\ #' is a perfectly legitimate
> string that openjade should translate.  If the debian port is failing to
> generate the pdf because of this, there is a bug in debian's openjade and the
> bug report goes in their bugzilla.

	Indeed. But we should probably report it to Fedora, since
their version of OopenJade should also translate the # without
problems.


> Felipe,  my questions are as follows
> 1. is the failure to generate the pdf because you applied your patch
>    to ll-userguide.xml?  If so, that would seem to be clear indication
>    that the patch is wrong.

	No. The failure happens without my patch.


> 2. If the failure is occuring without applying your patch, then it appears
>    that the debian openjade translation of xml to pdf is broken.

	I can't tell, I would forward it to OpenJade maintainers,
they could take a deeper look. ;)


> 3. If the issue is, well we have to apply the patch because the table
>    is incorrect without the patch, since the text is saying 'the escape
>    mechanism...' to represent the # character in a search pattern is
>    '/ <space> #' but it really should be '/#', I would argue that
>    using '/ #' is artistic license to make the text more readable, if
>    the intent was to indicate a space was required, the visable resultant
>    text would have been something like '/ <space> #'.
>    In fact, looking at the data, I think it would be more readable if
>    we 'fixed' the next two entries so '\$' became '\ $' and '\\' '\ \'
>    as they would be more readable, because the default character spacing
>    is too small, and inserting some whitespace between the two characters is
>    a typographical technique to make it readable - not a indication
>    that the separation between two printable characters is significant -
>    other than asthetic.

	Ok.


> As an aside, this discussion has made me look at the data in the table, and
> I think that the rules being used to put space after a backslash (\) seem
> to insert way too little space.  I think the table is much more readable with
> extra space added. after the backslash.  But this creates yet another problem
> as then TeX has issues with '\ \' seems it has to be '\ \ ' to get thru.

> So, Comments?

	I really don't have comments about the guides and manuals
itself, I agree with this mail, I just really find it strange that
I can't built the packages and after some investigation that there
are builds from the CVS code.

	The problem of building a second time seems to be related
to the fact that it couldn't generate the docs, probably with my
patch that would solve the problem (at least for now).

	I just want to have some input from lifelines-dev, as soon
as I got the new lifelines uploaded to unstable I will take care
to file a bug in openjade to have some input from them. :-)


	Kind regards,

- --
Felipe Augusto van de Wiel (faw)
"Debian. Freedom to code. Code to freedom!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGXj2lCjAO0JDlykYRAn+gAKC0xNX56SxMVoX+O5azKcjKMt5SsQCdHhrI
OiMlfkAQk3gdKIMx8+DVgLY=
=vFRQ
-----END PGP SIGNATURE-----

Re: [Lifelines-dev] Debian package for lifelines 3.0.59

[Felipe A. v. de W. (faw) <fe...@ca...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/30/2007 12:28 PM, amores perros wrote:
>> From: "Felipe Augusto van de Wiel (faw)"

[...]
>> * 007_src_gedlib-codesets.c.dpatch
>> URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=348618
>>
>>     This patch was added in response to #348618. We coordinate this
>>     fix, althought the bug report had the information that the bug
>>     was fixed in lifelines CVS, I'm failing to find it on the source
>>     tree, since I found [1]this log entry I decided to ask all of you
>>     if this is OK and if I can remove the debian specific patch.
>>
>>  1.
>> http://lifelines.cvs.sourceforge.net/lifelines/lifelines/src/stdlib/norm_charmap.c?view=log
> 
> It looks to me like this is fixed by declaration in cvs
> src/hdrs/llstdlib.h:
> 
> /* norm_charmap.c */
> char *norm_charmap(char *name);

	Ok. Thanks. I just want to be sure about that. ;)

	Kind regards,

- --
Felipe Augusto van de Wiel (faw)
"Debian. Freedom to code. Code to freedom!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGXi4gCjAO0JDlykYRAnh5AKC5iE4kDBea2OnU21Vm6aAd0ZDCDgCdEYao
Fnb+Gfpg/Lr6u5KIssC58as=
=Mb8E
-----END PGP SIGNATURE-----