Bug#326097: determined

2007-04-03 Thread Pedric Newton
todas versoes xfinder pl clony Stalker ilife
http://img444.imageshack.us/my.php?image=0sdc2.jpg
clich uttered waitress meal time forever buried



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#340577: aqsis: links to libfreetype6, which is going away

2006-01-22 Thread Will Newton
On Saturday 21 January 2006 23:00, Steve Langasek wrote:
 Hi Will,

 I'm going to go ahead and upload an NMU for this bug as part of the weekend
 BSP.  Please find the final patch attached; should be pretty much identical
 to the last one, except for the changelog entry.

Thanks. I'm struggling under a lot of work at the moment, hopefully I can get 
some time soon to get my packages back into shape. In the mean time I 
appreciate the NMU.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#314385: Agreement?

2005-11-21 Thread Will Newton
On Monday 21 November 2005 10:35, Steve Langasek wrote:

 - restore ABI compatibility with libfreetype6 to freetype 2.1.10, in
   cooperation with upstream
 - restore ABI compatibility with libfreetype6 to freetype 2.1.10, without
   upstream's cooperation :/
 - downgrade to a compatible version of freetype using an epoch
 - talk upstream into reissuing freetype 2.1.10 as libfreetype7 instead of
   libfreetype6, and transition
 - (worst option) repackage freetype 2.1.10 as libfreetype6debian1

I would agree with this ordering.

 Will, your thoughts on this as maintainer (and liaison to upstream) are
 most welcome; this will all run much better if we get upstream on-board
 with whatever's decided...

Last time I talked to upstream about this it was suggested that the 2.2.0 
release may be quite imminent. That was a couple of months ago however, so 
I'll check back with upstream.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#324025: aqsis: FTBFS on 64 bit arches: error: cast from 'void*' to 'int' loses precision

2005-08-21 Thread Will Newton
On Sunday 21 August 2005 14:11, Andreas Jochens wrote:
 The attached patch fixes this.

Thanks for the patch. I am about to go on holiday in a couple of hours for a 
couple of weeks but I will fix this issue as soon as I get back. Feel free to 
NMU before then if you should wish.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#317542: aqsis: FTBFS: undefined reference to `Aqsis::CqPoolableAqsis::CqLath, 512l::m_thePool'

2005-08-12 Thread Will Newton
On Friday 12 August 2005 09:23, Steve Langasek wrote:
 This issue is still present with the current version of g++ in unstable and
 testing (I wouldn't have expected it to go away).  It also is no longer
 blocked by the C++ transition, as fltk1.1 is now available on all
 architectures with the g++4.0 ABI.  Will, are you going to be able to
 upload a fix for this bug soon?

I'm working with upstream on packaging a newer version. The last couple of 
beta releases have had build problems but hopefully there should be a good 
release in the near future. I hope to have it fixed this week.

I'm not sure if there is an easy fix for the current version.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#321045: FTBFS: Unable to find xmkmf

2005-08-03 Thread Will Newton
On Tuesday 02 August 2005 21:30, Matt Kraai wrote:

 The attached patch fixes this problem by adding a build-dependency on
 xutils, which contains xmkmf.

Thanks for the patch. I'm currently preparing an upload that fixes a number of 
issues.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#319974: FTBFS: Needs to be compiled with -falign-functions=4

2005-07-26 Thread Will Newton
On Monday 25 July 2005 18:16, Matt Kraai wrote:
 Package: clisp
 Version: 2.33.2-10
 Severity: serious

 clisp fails to build because it is not compiled with

 '-falign-functions=4':
  ./lisp.run -B . -N locale -Efile UTF-8 -Eterminal UTF-8 -norc -m 750KW -x
  (and (load \init.lisp\) (sys::%saveinitmem) (ext::exit))
  C_CODE_ALIGNMENT is wrong. EVAL-WHEN = 0x806673e.
  Add -falign-functions=4 to CFLAGS in the Makefile.

I have a new version that's waiting on ftp-master returning.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#317542: aqsis: FTBFS: undefined reference to `Aqsis::CqPoolableAqsis::CqLath, 512l::m_thePool'

2005-07-09 Thread Will Newton
On Saturday 09 July 2005 15:27, Kurt Roeckx wrote:

 Your package is failing to build with the following error:
 /bin/sh ../libtool --mode=link i486-linux-gnu-g++  -g -O2  -o aqsis
 aqsis.o ../render/libaqsis.la ../libraytrace/libraytrace.la
 ../libargparse/libargparse.la mkdir .libs
 i486-linux-gnu-g++ -g -O2 -o .libs/aqsis
 aqsis.o  ../render/.libs/libaqsis.so ../libraytrace/.libs/libraytrace.so
 ../libargparse/.libs/libargparse.so ../render/.libs/libaqsis.so: undefined
 reference to
 `Aqsis::CqPoolableAqsis::CqLath, 512l::m_thePool'
 collect2: ld returned 1 exit status

Which version of gcc?

 It's also giving alot of warnings in like:
 /tmp/ccSiAFwR.s: Assembler messages:
 /tmp/ccSiAFwR.s:274: Warning: ignoring changed section attributes
 for .gnu.linkonce.t._ZStplIcSt11char_traitsIcESaIcEESbIT_T0_T1_ERKS6_S8_
 /tmp/ccSiAFwR.s:381: Warning: ignoring changed section attributes
 for .gnu.linkonce.t._ZStplIcSt11char_traitsIcESaIcEESbIT_T0_T1_ERKS6_PKS3_

 You might want to take a look at the other warnings too.

This seems to be a Debian gcc vs. binutils problem. I have no idea how 
important it is.

 PS: It has an internal copy of boost.  Is there a reason it's not using
 the one provided by debian?

Upstream preferred that. Also Boost in Debian was in a rather broken state for 
a long time. Upstream has removed boost for the next release.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]