[fink-core] HEAD buildlocks (and maybe others?) don't handle epoch

[Benjamin R. <ran...@be...>]

So I found a bug in the HEAD buildlock code that might explain some of
the weirdness we're seeing.

The stable version of squid-ssl (2.5.STABLE5) comes up as newer than the
unstable unified splitoff squid-ssl (2.5.STABLE11), so I'm putting out a
new version (from upstream) with the epoch set to 1.

The buildlock code doesn't handle epochs at all, though, so you end up
with this:

---(snip!)---
ranger$ fink install squid-unified
Information about 5897 packages read in 9 seconds.
The following package will be installed or updated:
 squid-unified
Setting runtime build-lock...
dpkg-deb -b
/sw/compile.build/root-fink-buildlock-squid-unified-2.5.stable12-1
/sw/compile.build
dpkg-deb: building package `fink-buildlock-squid-unified-2.5.stable12-1'
in
`/sw/compile.build/fink-buildlock-squid-unified-2.5.stable12-1_2006.02.26-23.14.02_darwin-powerpc.deb'.
Installing build-lock package...
/sw/bin/dpkg-lockwait -i
/sw/compile.build/fink-buildlock-squid-unified-2.5.stable12-1_2006.02.26-23.14.02_darwin-powerpc.deb
Selecting previously deselected package
fink-buildlock-squid-unified-2.5.stable12-1.
(Reading database ... 107177 files and directories currently installed.)
Unpacking fink-buildlock-squid-unified-2.5.stable12-1 (from
.../fink-buildlock-squid-unified-2.5.stable12-1_2006.02.26-23.14.02_darwin-powerpc.deb)
...
dpkg: dependency problems prevent configuration of
fink-buildlock-squid-unified-2.5.stable12-1:
 fink-buildlock-squid-unified-2.5.stable12-1 depends on squid-unified (=
2.5.stable12-1); however:
  Package squid-unified is not installed.
/sw/bin/dpkg: error processing
fink-buildlock-squid-unified-2.5.stable12-1 (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 fink-buildlock-squid-unified-2.5.stable12-1
### execution of /sw/bin/dpkg-lockwait failed, exit code 1
Can't set build lock for squid-unified (1:2.5.stable12-1)

If any of the above dpkg error messages mention conflicting packages or
missing dependencies -- for example, telling you that the package
fink-buildlock-squid-unified-1:2.5.stable12-1 conflicts with something
else -- fink has probably gotten confused by trying  to build many
packages at once. Try building just
this current package squid-unified (i.e, "fink build squid-unified").
When that has completed successfully,  you could retry whatever you did
that led to the present error.

Regardless of the cause of the lock failure, don't worry: you have not
wasted compiling time! Packages that had been completely built before
this error occurred will not have to
be recompiled.

See http://wiki.opendarwin.org/index.php/Fink:buildlocks for more
information.
/sw/bin/dpkg-lockwait -r fink-buildlock-squid-unified-2.5.stable12-1
>/dev/null
Failed: buildlock failure
---(snip!)---

Note the "fink-buildlock-squid-unified-2.5.stable12-1 depends on
squid-unified (= 2.5.stable12-1); however:"

I tried digging through the buildlock code but it's too big for me to
just do a quick hack to fix.  Any ideas how to go about making the
buildlock handle %e?

-- 
Benjamin Reed a.k.a. Ranger Rick
http://ranger.befunk.com/