[tahoe-dev] zfec dependencies

Marc Tooley tahoe-devPOST at quake.ca
Sat Jul 24 01:04:54 UTC 2010

On Friday 23 July 2010, Greg Troxel wrote:
> Greg Troxel <gdt at ir.bbn.com> writes:
> > while packaging tahoe:
> >
> > zfec seems to depend on darcsver and setuptools_darc.  Downloading
> > code during package builds is not allowed, so I either have to
> > package those or patch them out.  It seems they really are required
> > for a good build of zfec, and thus I should package them, but I
> > wanted to ask.
> I realize now that these <python-distributions> are present as eggs
> in the zfec source, and hence not needed as separate
> <pkgsrc-packages>.
> Still, does it make sense to add darcsver to pkgsrc?  I have already
> made the package control files.

Are you using darcs-2.4.4? darcs-2.0.2 or even darcs-2.2.0 both have a 
problem on NetBSD whereby they can fail at datetime conversions. For 
more information, see [1]. That link also contains the following patch 
which fixes that specific issue:

--- src/Darcs/Patch/Info.hs.orig        2009-01-15 
14:53:59.000000000 -0800
+++ src/Darcs/Patch/Info.hs     2009-09-03 14:36:58.000000000 -0700
@@ -150,10 +150,7 @@
           t = BC.pack "TAG "
 friendly_d :: B.ByteString -> String
---friendly_d d = calendarTimeToString . readPatchDate . d
-friendly_d d = unsafePerformIO $ do
-    ct <- toCalendarTime $ toClockTime $ readPatchDate d
-    return $ calendarTimeToString ct
+friendly_d d = calendarTimeToString (readPatchDate d)
 to_xml :: PatchInfo -> Doc
 to_xml pi =

The unfortunate thing is that even after the above is corrected, there 
are other issues which necessitate the use of a later version of darcs 

I am in the middle of creating a darcs-2.4.4 pkgsrc entry. I believe the 
problem (and many others) are resolved in darcs-2.4.4 but this is based 
only on speculation.

If I am successful I'll submit it back; however, if you have already 
done this, please let me know where to get the pkgsrc entry for the new 

I believe the issue is in part due to the older ghc compiler available 
on NetBSD-i386. [2] *may* be related, but I fail to see how.


P.S. I have a pubkey here with ID 1024D/32611E25 has expired and so your 
GPG signatures are invalid. Is there a new key somewhere I can 

More information about the tahoe-dev mailing list