port of crafty to alpha platform is outdated

[Eric Van Buggenhaut]

Hi,

I'm maintaining crafty, a chess game engine.

update_excuses reports that:

* crafty (17.13-6 to 18.12-4)
+ Maintainer: Eric Van Buggenhaut
+ 33 days old (needed 2 days)
+ out of date on alpha: crafty (from 18.11-1)
+ out of date on ia64: crafty (from 18.11-1)
+ Not considered

I'd like to get newer version of crafty into testing since it includes major improvements and fixes important bugs. People keep filing bugs about crafty that have been solved in the new versions.

Although crafty is non-free, could you give it a try on the auto-builders and release a fresh version before freezing Woody ? It's not a very large code and there are no complicated build-dependencies (sharutils, bzip2, g++)

Thanks for your help.

--
Eric VAN BUGGENHAUT
eri...@debian.org

--
To UNSUBSCRIBE, email to debian-alp...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Paul Slootman]

On Tue 01 Jan 2002, Eric Van Buggenhaut wrote:
>
> update_excuses reports that:
>
> * crafty (17.13-6 to 18.12-4)
> + Maintainer: Eric Van Buggenhaut
> + 33 days old (needed 2 days)
> + out of date on alpha: crafty (from 18.11-1)
> + out of date on ia64: crafty (from 18.11-1)
> + Not considered

I've just built and uploaded the alpha version.

Note that as a developer you can log in to merulo.debian.org
(an ia64 system). I've done that for a couple of my packages
before. Just use -uc and sign the changes on your own system.

Paul Slootman

[Matthew Wilcox]

On Tue, Jan 01, 2002 at 09:18:59PM +0100, Eric Van Buggenhaut wrote:
> Although crafty is non-free, could you give it a try on the
> auto-builders and release a fresh version before freezing Woody ? It's
> not a very large code and there are no complicated build-dependencies
> (sharutils, bzip2, g++)

as a debian developer, you have an account on merulo. see
http://db.debian.org/machines.cgi

--
Revolutions do not require corporate support.

[Eric Van Buggenhaut]

On Thu, Jan 03, 2002 at 03:20:03PM +0000, Matthew Wilcox wrote:
> On Tue, Jan 01, 2002 at 09:18:59PM +0100, Eric Van Buggenhaut wrote:

> > Although crafty is non-free, could you give it a try on the
> > auto-builders and release a fresh version before freezing Woody ? It's
> > not a very large code and there are no complicated build-dependencies
> > (sharutils, bzip2, g++)
>

> as a debian developer, you have an account on merulo. see
> http://db.debian.org/machines.cgi
>

Ok, done it right now. I didn't know bzip2 was installed on this
machine.

[Eric Van Buggenhaut]

On Mon, Jan 07, 2002 at 02:31:26PM +0100, Paul Slootman wrote:

> On Thu 03 Jan 2002, Eric Van Buggenhaut wrote:
> >
> > > Note that as a developer you can log in to merulo.debian.org
> > > (an ia64 system). I've done that for a couple of my packages
> > > before. Just use -uc and sign the changes on your own system.
> > >
> >

> > Oh, ok, I didn't know about this machine. I'm offline now so I can't
> > try it, but my worry is that bzip2 might not be installed on this
> > machine (that's what happened with all other architectures). What
> > should I do then ?
>
> Unpack it in your home directory, and modify PATH (and perhaps
> LD_LIBRARY_PATH) to suit before invoking the build. I did something
> similar when I needed to build isdnutils on powerpc (which need gcc-3.0
> to build, and gcc-3.0 wasn't installed. Using a different compiler is a
> bit more painful then bzip2, as the compiler refers to all sorts of hard
> path for preprocessor, libs, includes, ...)
>

I was able to install bzip2 in my home directory, but it is also
dynamically linked against /usr/lib/libbzip* and I don't know how to
add a new library path, iow, should I recompile bzip2 explicitly
specifying a new library path ?