[darcs-users] Announcing darcs 1.0.3rc2

[Nimrod A. Abing]

On 5/17/05, Nimrod A. Abing <nimrod.abing at gmail.com> wrote:
> On 5/16/05, Tomasz Zielonka <tomasz.zielonka at gmail.com> wrote:
> > On Mon, May 16, 2005 at 08:55:09AM +0000, Nimrod A. Abing wrote:
> > > Well... 6.2.1 is the only version of GHC I have at the moment, so I
> > > guess I have to live with those bugs until I can upgrade. I'm curious
> > > as to whether the workaround above fixes the problem (i.e. really does
> > > use unfolding threshold of 20) on 6.2.1.
> >
> > I think it does. See:
> > http://www.haskell.org//pipermail/glasgow-haskell-bugs/2005-May/005078.html
> >
> > Hmmm... this workaround is already in darcs-unstable. I'll include it in
> > 1.0.3.
> 
> Maybe use the autodetected GHC version from configure and apply the
> workaround if needed?
> 
> > > I'll try 1.0.3rc2 first and report details to you, whether or not the
> > > build succeeds.
> 
> I pulled in 1.0.3rc2 and still the build failed at the same point as
> rc1. darcs itself is built, but there is a problem building the
> documentation.
> 
> Here is the *complete* build log:
> 
> http://abing.gotdns.com/darcs/darcs-build.log
> 
> After this step:
> 
> ./preproc darcs.lhs > darcs_print.tex
> latex darcs_print.tex
> 
> latex will go into interactive mode and I have to press the enter key
> (been a while since I last did tex) at the question mark prompt.
> 
> One more thing, since I am using the Debian build system and creating
> my own debs all I do is uupdate to get a new darcs tree. The tarball
> (darcs-1.0.3rc2.tar.gz) used by uupdate is constructed as follows:
> 
> 1. unpack darcs-1.0.2.tar.gz
> 2. in darcs repository pulled from official repository, darcs diff
> --unified --from-tag=1.0.2 --to-tag=1.0.3rc2. > 1.0.2-1.0.3rc2.diff
> 3. cd to unpacked darcs-1.0.2.tar.gz directory and apply patch, some
> patches will fail. Nothing to worry because these are patches for some
> debian/* files.
> 4. move darcs-1.0.2 to darcs-1.0.3rc2
> 5. create a tarball of darcs-1.0.3rc2.
> 
> I don't know if this has any relevance, worst case would be if this
> process is leaving out some crucial files for building the docs.

Following up on this... I downloaded the tarball from the site and
used that in uupdate. This time the build went without errors. So
creating my own tarballs by patching 1.0.2 tarballs up to 1.0.3rc2
really *did* miss something crucial. I just don't know what. Anyway,
here is what diff would tell me:

nimrod at iwojima:$ diff -q darcs-1.0.2-patched-1.0.3rc2/
darcs-1.0.3rc2-from-darcs.net/
Only in darcs-1.0.3rc2-from-darcs.net/: AUTHORS
Common subdirectories: darcs-1.0.2-patched-1.0.3rc2/bugs and
darcs-1.0.3rc2-from-darcs.net/bugs
Only in darcs-1.0.3rc2-from-darcs.net/: c_context.c
Common subdirectories: darcs-1.0.2-patched-1.0.3rc2/cgi and
darcs-1.0.3rc2-from-darcs.net/cgi
Only in darcs-1.0.3rc2-from-darcs.net/: ChangeLog
Common subdirectories: darcs-1.0.2-patched-1.0.3rc2/changelog.in and
darcs-1.0.3rc2-from-darcs.net/changelog.in
Only in darcs-1.0.3rc2-from-darcs.net/: config.command
Files darcs-1.0.2-patched-1.0.3rc2/configure and
darcs-1.0.3rc2-from-darcs.net/configure differ
Only in darcs-1.0.3rc2-from-darcs.net/: darcs.1
Only in darcs-1.0.3rc2-from-darcs.net/: darcs_print.ps
Only in darcs-1.0.3rc2-from-darcs.net/: .depend
Files darcs-1.0.2-patched-1.0.3rc2/favicon.ico and
darcs-1.0.3rc2-from-darcs.net/favicon.ico differ
Common subdirectories: darcs-1.0.2-patched-1.0.3rc2/logos and
darcs-1.0.3rc2-from-darcs.net/logos
Common subdirectories: darcs-1.0.2-patched-1.0.3rc2/manual and
darcs-1.0.3rc2-from-darcs.net/manual
Common subdirectories: darcs-1.0.2-patched-1.0.3rc2/tests and
darcs-1.0.3rc2-from-darcs.net/tests
Common subdirectories: darcs-1.0.2-patched-1.0.3rc2/win32 and
darcs-1.0.3rc2-from-darcs.net/win32

Hopefully this tells you something else. I can send the full diff but
it's pretty big and I'm on dialup.
-- 
_nimrod_a_abing_

v1sw5CPJYUhw5ln3pr8OUSck6ma8u7LBw3DWNTm5g/l7DaIs7Rr4e6t5Xb4Op1en3g5RZAHC