Bug#328104: solved itself

2005-10-25 Thread Barak Pearlmutter
this issue seems to have solved itself, in the fullness of time.


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



Bug#328597: very old package, should this be removed?

2005-09-16 Thread Barak Pearlmutter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Yes; I think it would be okay to remove oaklisp at this point.
(If I ever get around to making the upstream changes it needs to bring
it into the 2000s I'll just upload the result as a new package.)

--Barak.
==
Barak A. Pearlmutter [EMAIL PROTECTED]
 Hamilton Institute  Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
 http://www-bcl.cs.nuim.ie/~barak/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 http://mailcrypt.sourceforge.net/

iD8DBQFDKqEQLz4Gnv7CP7IRApRSAJ4pLJIch+/y394ud3u2soxJb2z/6wCePto6
j5ifkZd+7wF3/9I7qzp+3i4=
=CJvN
-END PGP SIGNATURE-


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



Bug#328104: djview in testing depends on libqt3-mt only available in unstable

2005-09-13 Thread Barak Pearlmutter
This isn't djview's fault, is it?
I'll wait, and close this bug once libqt3-mt migrates into testing.
--
Barak A. Pearlmutter [EMAIL PROTECTED]
 Hamilton Institute  Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
 http://www-bcl.cs.nuim.ie/~barak/


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



Bug#328104: djview in testing depends on libqt3-mt only available in unstable

2005-09-13 Thread Barak Pearlmutter
Sure, but there is an automated system that does the
unstable-to-testing migration.  Don't know why it failed here.

--Barak.


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



Bug#328104: djview in testing depends on libqt3-mt only available in unstable

2005-09-13 Thread Barak Pearlmutter
Yes, it probably has to do with that.
Will look into a transitional package.  But although it might solve
the multiple libdjvulibre1 vs  multiple libdjvulibre15 problem, it
probably won't solve this libqt* issue.

--Barak.


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



Bug#320582: libdjvulibre1: soname of library changed

2005-08-14 Thread Barak Pearlmutter
The upload is no problem, I have things fixed already in CVS, and they
are mostly trivial anyway.  In fact the X library stuff fixed itself.
The only thing hold me up is the m68k issue.  I have not taken the
time to dive in the build system far enough to figure out how to
either change -O3 to -O2 or specify gcc-3.4 instead of the default gcc
on only m68k.  Obviously there is something simple one can do, I just
don't know GNU automake etc well enough to just do it.

So, patch welcome, otherwise I'll get to it when I have a few hours to
page all that build stuff in.

--Barak.
--
Barak A. Pearlmutter [EMAIL PROTECTED]
 Hamilton Institute  Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
 http://www-bcl.cs.nuim.ie/~barak/


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



Bug#321107: Bug#320582: djvulibre NMU being prepared

2005-08-14 Thread Barak Pearlmutter
PS But on second thought, please go ahead and NMU with that patch.  It
should clear the issue for now, and shouldn't do any harm.  Later I'll
fix it right and upload that.  And your NMU will allow me to take my
time finding the right fix.  Which I suppose involves writing an
autoconf script to actually detect the nasty GCC bug breaking m68k and
disable -O3 or switch to GCC 3.4 when the bug is found.

--Barak.


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



Bug#321107: Bug#320582: djvulibre NMU being prepared

2005-08-14 Thread Barak Pearlmutter
Um, that patches the script configure without a corresponding patch
to configure.ac.  But the first is built periodically from the
second.  I'd rather have a more permanent solution to the problem...

--Barak.


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



Bug#320794: please recompile evince against libdjvulibre-dev (= 3.5.14-6)

2005-08-05 Thread Barak Pearlmutter
Sebastien,

Could I trouble you to recompile and dupload evince against
libdjvulibre1 (= 3.5.14-6) to deal with soname change?  Evince is the
only package that uses the lib, so that will clear the issue.

I'm not sure if the API has changed in a fashion that justifies a
chance in soname.  Upstream revs it as a matter of routine prior to a
formal release, just to be on the safe side I suppose.  I will chat
with upstream about how we can prevent this from happening again
without my introducing a gratuitous Debian incompatibility.

Thanks,

--Barak.
--
Barak A. Pearlmutter [EMAIL PROTECTED]
 Hamilton Institute  Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
 http://www-bcl.cs.nuim.ie/~barak/


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



Bug#320794: please recompile evince against libdjvulibre-dev (= 3.5.14-6)

2005-08-05 Thread Barak Pearlmutter
Problem is what does fix djvulibre mean here?

Fix it to generate the old soname, thus losing soname compatibility
with upstream?

Fix it to generate a different library name, perhaps libdjvulibre15?

Fix it by asking upstream to stop changing the soname for no reason?

Fix it by convincing anyone using the library that they need an exact
version dependency, which is what upstream recommends library users
do, and encourages by changing the soname all the time?

Okay, I will change the generated library to libdjvulibre15.

--Barak.


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



Bug#320794: please recompile evince against libdjvulibre-dev (= 3.5.14-6)

2005-08-05 Thread Barak Pearlmutter
Yes, all true.

I will upload a rev which generates libdjvulibre15.  When that comes
down the pike, please recompile evince against it.

--Barak.


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



Bug#319436: FTBFS: Does not declare class before using it

2005-07-22 Thread Barak Pearlmutter
Just to confirm: this is a GCC 4.0 issue, which I have replicated.
I will mention it to upstream; I'm sure they will want to be GCC 4.0 clean.
--
Barak A. Pearlmutter [EMAIL PROTECTED]
 Hamilton Institute  Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
 http://www-bcl.cs.nuim.ie/~barak/


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